oracle standard cost,Standard Cost Update Performance

最新推荐文章于 2022-11-30 19:27:32 发布

小瓮同学

最新推荐文章于 2022-11-30 19:27:32 发布

阅读量251

点赞数

文章标签： oracle standard cost

本文档详细介绍了Oracle Cost Management 11.5.10中标准成本更新程序运行缓慢的问题及其解决方案。问题主要表现为该程序在不同组织中执行时间过长。解决办法包括清理不需要的成本类型、删除负成本类型记录、定期清除成本更新历史、检查并优化性能问题表、截断临时表以及确保使用最新版本的程序文件。此外，还提供了一些补丁信息以提升11.5.10版本的标准成本更新程序性能。

摘要由CSDN通过智能技术生成

Oracle ERP 11.5.8,The Standard Cost Update Report is running for long time for different organizations.[@more@]

Applies to:Oracle Cost Management - Version: 11.5.10

This problem can occur on any platform.

SymptomsIn Oracle Cost Management 11.5.10, Standard Cost Update program takes a long time to complete.

Cause

Following are the scripts in the Standard cost update program which are expensive:

This can be found out by checking the TKPROF file of the Standard cost update:

1) insert into cst_std_cost_adj_values

2) insert into cst_std_cost_adj_temp

3) insert into WIP_SCRAP_VALUES

Solution

For Standard cost update performance issues on 11.5.10 :

These are the pre-requisite or Pro-active actions which needs to be done before any standard cost update is run:

1. Purge the cost types that you do not need.

2. Delete the negative cost_type_id from the cst_item_costs and cst_item_cost_details tables. The negative cost_type_id is created whenever a cost update is aborted, so you may want to periodically check for negative cost_type_id records and delete them.

The following Scripts can be used to identify the same :

Select * from Cst_item_costs where cost_type_id <0

Select * from Cst_item_cost_details where cost_type_id <0

3. Periodically purge the cost update history. This clears out some of the tables and benefits the performance. Obtain a count on tables where the trace file indicates a performance issue. Performance issues arise when tables have large amounts of records.

4. Check the count of rows contained in the following tables. If the number of rows in Cst_item_costs and Cst_item_cost_details table are huge, then it is one of the most probable reasons that standard cost update program takes more time to complete.

5. Truncate temporary tables, i.e., cst_std_cost_adj_temp. These tables grow if cost update is run with the CST debug profile set to Full.

The following tables can be truncated for performance. Be sure there are no cost processes running when truncating these tables:

CST_LOW_LEVEL_CODES

CST_STD_COST_ADJ_TEMP

BOM_LISTS

CST_ROLLUP_DELETE_TEMP

BOM_SMALL_EXPL_TEMP

CST_LISTS

BOM_EXPLOSION_TEMP

CST_EXPLOSION_TEMP

6. Verify that you have the latest versions of the following files:

Aall files are found at the following path: $BOM_TOP/bin/CMCICU

cmcicu.opp

cmlccu.ppc

cmlicu.ppc

cmliru.ppc

cmlutl.ppc

cmlwcu.ppc

CSTPUPDB.pls

CSTPUPDS.pls

cmlwru.ppc

7. For 11i, Run Gather Schema Stats for the CST_ITEM_COSTS and CST_ITEM_COST_DETAILS tables.

==================================

After completing the above tasks, Search for the patches available. Following is the indicative list of patches available. The patches contained in this note contain the highest version patches available to date. Any new patches released after this needs to be found out through MetaLink by searching for the corresponding files.

On 11.5.10 the following patches are available.

Base version of cmlicu.ppc in $BOM_TOP/bin/CMCICU should be 110.26.

File version upgraded...

1) $BOM_TOP/src/cmcicu.opc 115.26.115100.10

2) $BOM_TOP/src/cmlwru.lpc 115.32.115100.13

3) $BOM_TOP/patch/115/import/US/cst5520835.ldt 115.0.115100.3

and

File version upgraded...

$BOM_TOP/patch/115/sql/CSTVIVTB.pls 115.25.115100.16

$BOM_TOP/src/cmliru.lpc 115.23.115100.11

( This patch can be specifically used for standard cost adjustments for intransit quantities)

File version upgraded...