2020/5/18 Document 1928724.

Copyright (c) 2020, Oracle. All rights reserved. Oracle Confidential.

Data Collection Scripts and Process Flow for Periodic Average Costing ( PAC IPAC ) - Cost
Management (Doc ID 1928724.1)

In this Document

Goal
Solution
1. Common Resolution for PAC/IPAC Issues
2. PAC/IPAC Process/Setup
3. Identify whether customer is working with Localizations or not
3.1 Confirm via SQL Script:
3.2 Via Application:
3.3 Via Log File:
3.4 Via Database Objects:
4. Review the latest Patches released for PAC/IPAC
4.1 Release 11.5.10.2 (Minimum Patch Set)
4.2 Release 12.0.X: None
4.3 Release 12.1.X (Descending creation date):
4.4 Release 12.2.X: None
4.5 For issues with IPAC:
5. Resolving PAC/IPAC Performance Issues
5.1 Proceed Running Gather Schema Statistics
5.2 Review the following Document
6. Identify File Name and File Version for PAC/IPAC Processes
7. Is the Issue still happening? then proceed with the following Actions
7.1 For issues related to PAC/IPAC Processes
7.2 For issues related to PAC/IPAC Performance Issues
7.3 For issues related to Errors at PAC/IPAC Log Files
References

APPLIES TO:

Oracle Cost Management - Version 11.5.10.2 to 12.2.5 [Release 11.5 to 12.2]

Information in this document applies to any platform.
Cost Management-> Periodic Costing -> Periodic Cost -> Periodic Acquisition Cost Processor (CMCACQ, CMCPAM)
Cost Management-> Periodic Costing -> Periodic Cost -> Periodic Acquisition Cost Adjustment Processor (CSTPACAP)
Cost Management-> Periodic Costing -> Reports -> Periodic Absorption Cost Processor (CST_INTERORG_TRANSFER)

---

Phase 1-4 (all cost groups)

Phase 1: Periodic Acquisition Cost Process
Phase 2: Copy Prior Period Balance
Phase 3: BOM Explosion
Phase 4: WIP Processor
Phase 7: Absorption Cost Process (all cost groups)
Phase 5: Periodic Cost Processor
Phase 6: Periodic Distribution Processor
Cost Management-> Periodic Costing -> Periodic Cost -> Periodic Cost Processor (CMCPAW)
Cost Management-> Periodic Costing -> Periodic Cost -> Periodic Cost Distribution Processor (CSTPDPPC)

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xu7ae1hb3_4&id=1928724.1 1/13
2020/5/18 Document 1928724.1

**** Checked on Relevance on 04-FEB-2019 ****

GOAL

PAC

Periodic Average Costing is an option that enables customers to value inventory on a periodic basis.
Periodic Costing is relevant for customers with fiscal inventory reporting requirement as it is invoice-based and allows you
to include additional invoiced charges in the cost of the item.
Periodic Costing is also used by customers who want invoice-price based valuation of their inventory to set standards or to
update their perpetual costs.
An approach to inventory valuation in which variable costs and a portion of fixed costs are assigned to each unit of
production. (APICS Dictionary, 2003

SOLUTION

1. Common Resolution for PAC/IPAC Issues

Setup Issues
* (Version 11.5.10.2 to 12.1.3) CMCPAW Periodic Actual Cost Worker raises
CSTPPINV.COST_INV_TXN:CSTPPINV.COST_INV_TXN: (50): ORA-01403: No Data Found (Doc ID 1456553.1)
* (Version 12.1.1 and later) CMCPAW Periodic Actual Cost Worker Err CSTPPACQ.acq_cost_processor ORA-06508
Could Not Find Program Unit (Doc ID 1594479.1)
* (Version 11.5.10 and later) CSTPDPPC Periodic Cost Distributions Processor raises Error
CSTPAPBR.create_acct_lines : 60:ORA-01403 (Doc ID 1390817.1)
Code Issues
* (Version 12.0.0 to 12.1.2) Periodic Period End Process Error CSTPALPC.dyn_proc_call : Error Calling Package
(Doc ID 1170383.1)
* (Version 12.1.1 to 12.1.3) Cstppacq.Get_acq_cost(45):Ora-01403: No Data Found Error In Cst_pac_worker
(Doc ID 1331182.1)
* (Version 11.5.10.0 to 11.5.10.3) PERIODIC ABSORPTION COST PROCESS ERRS WITH
CSTPPACQ.GET_ACQ_COST(45): (Doc ID 734473.1)
* (Version 11.5.10.2) Periodic Actual Cost Worker End With ORA-01654 Error (Doc ID 1084997.1)

* (Version 12.0.0) CSTPDPPC - Periodic Cost Distributions Processor Errs With CSTPAPBR.create_acct_lines :
60:ORA-01403 (Doc ID 791314.1)
* (Version 12.0.4 and later) CSTPDPPC Periodic Cost Distributions Processor Fails
'CSTPDPPC.dyn_proc_call...30005There are no accounts defined for the category, for the cost type, cost group and
legal entity.' (Doc ID 1321523.1)
* (Version 11.5.10.0 to 11.5.10.3) CSTPDPPC Periodic Cost Distributions CSTPALPC.create_dist_entry No
Accounts Defined (Doc ID 420713.1)
* (Version 12.1.1 and later) Get CST_COGSGEN_PHASE3_NOTRUN Error When Trying to Close Periodic
Accounting Periods for Period Dates (Doc ID 1295205.1)
* (Version 12.1.1) Periodic Cost Distributions Processor interorg/intercompany transfer Err
CSTPAPBR.create_acct_lines ORA-01403 (Doc ID 1356237.1)
* (Version 12.1.1 and later) CMCPAW Periodic Actual Cost Worker Performance Issue
CSTPPACQ.get_charge_allocs ORA-30036 (Doc ID 1292481.1)
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xu7ae1hb3_4&id=1928724.1 2/13
2020/5/18 Document 1928724.1

* (Version 12.1.1 to 12.1.3) CMCPAW Periodic Actual Cost Worker raised the following error message
CSTPPACQ.get_acq_cost ORA-01422 exact fetch (Doc ID 1331498.1)
* (Version 12.2 and later) "30011An Invalid Account Is Associated With The Item Being Transacted" for a
Residual Qty Receipt/Issue transaction (Doc ID 1671242.1)

2. PAC/IPAC Process/Setup

There are three principal objectives of Periodic Costing:

To capture actual acquisition costs based on supplier invoiced amounts plus other direct procurement charges required by
national legislation or company policy
To capture actual transaction costs using fully absorbed resource and overhead rates
To average inventory costs over a prescribed period, rather than on a transactional basis
Customers having Inventory organizations that are the same fiscal Entity (have the same tax inscription number) need to
have the same average cost (legal requirement).
This means that to calculate the average cost of an item that belongs to more than one inventory organization, the
periodic average cost calculation has to Work across all organizations belonging to the Fiscal Cost Group.
The inventory organizations belonging to the same Fiscal Cost Group will then share the costing structure and accounts.

IPAC

Customers in countries like Brazil, Taiwan, Korea use IPAC (PACP) as the basis for their fiscal reporting and need an
accurate absorption of costs in their periodic cost calculation process IPAC(PACP) provides an enhanced periodic costing
process over the standard PAC by ensuring a more accurate absorption of costs in PAC calculation:
Internal movements of goods between organizations belonging to different cost groups are valued iteratively to absorb the
costs between the cost groups appropriately
New hierarchy ‘Absorption Hierarchy’ is introduced that determines right sequence of items to process to ensure
appropriate absorption of child items costs into parent item
Rework jobs are processed in correct sequence to minimize variance.

Figure 2 PAC Business Process Flow

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xu7ae1hb3_4&id=1928724.1 3/13
2020/5/18 Document 1928724.1

Figure 3 PAC Process

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xu7ae1hb3_4&id=1928724.1 4/13
2020/5/18 Document 1928724.1

Note: Run PAC processors in below (correct) order :

1.Pac acquisition cost process;
2.Pac acquisition cost process adjustment;(option)
3.pac cost process;
4.pac cost distribution processor;(option)

Figure 4 PAC Setup

Figure 5 PAC Setup FLow

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xu7ae1hb3_4&id=1928724.1 5/13
2020/5/18 Document 1928724.1

3. Identify whether customer is working with Localizations or not

Following are different actions to be completed in order to know whether customer is working with Localizations:

3.1 Confirm via SQL Script:

Please peform the following queries to check on localized objects:

For Release 11.5.X

SELECT OWNER,TABLE_NAME,STATUS
FROM ALL_TABLES
WHERE TABLE_NAME LIKE 'BS_AC%'

If the result shows: BSACAPBR.create_acct_lines, customer is using localizations.

For Release 12.0.X, 12.1.X, 12.2.X

SELECT OWNER,TABLE_NAME,STATUS
FROM ALL_TABLES
WHERE TABLE_NAME LIKE 'CLL_F032%'

If the result shows: CLL_F032_APBR.create_acct_lines, customer is using localizations.

If there is any localized code, the output will return any table/object name starting with "CLL%" for R12 or 'BS%' for
R11i.

3.2 Via Application:

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xu7ae1hb3_4&id=1928724.1 6/13
2020/5/18 Document 1928724.1

Please, check if PAC Accounting Library is set as PAC Brazil or US GAAP. Any other value, is considered
Localizations/Customizations. (Ej. CEB-PAC, CLL-PAC Brazil).

To verify if you are using a core or localized accounting library go to:

Go to Periodic costing -> Setup -> Org Cost Group / Cost Type Associations -> Accounting Options

On Accounting Library field > invoke LOV. There are two Accounting Libraries associated to Core PAC.

US GAAP
PAC Brazil

3.3 Via Log File:

Please, review the Log File Output

Ej: CSTPDPPC module: Periodic Cost Distributions Processor's Log File. From here we can identify the following information

Processing Transaction : A0000000

Calling Package CLL_F032_APBR_PKG.create_acct_lines ...
BEGIN CLL_F032_APBR_PKG.create_acct_lines(:I_LEGAL_ENTITY, :I_COST_TYPE_ID,
:I_COST_GROUP_ID, :I_PERIOD_ID, :I_TRANSACTION_ID, :I_EVENT_TYPE_ID, :I_TXN_TYPE_FLAG,
:O_ERR_NUM, :O_ERR_CODE, :O_ERR_MSG); END;
CLL_F032_APBR_PKG.Create_acct_lines <<
i_transaction_id: A0000000
Event type: 17
Create_wip_lines <<
Transaction type: 17
CSTPALBR.dyn_proc_call : Error Calling Package
CSTPDPPC.dyn_proc_call : Error Calling Package
30012Accounting entries cannot be created because there are no transactions cost details available.

3.4 Via Database Objects:

Database objects starting/having *REC, BS, CLL, BS_AC* are owned by Consulting/Localizations Team. Please run the
following queries for checking

select table_name, trigger_name from all_triggers where table_name like 'BS%';

Or

select table_name, trigger_name from all_triggers where table_name like 'CLL%';

If the queries return any row, then the objects are associated

If the queries return any row, then the objects are associated to any PAC process, customer is using Localizations.

Also, Table such as BS_AC_SUBINVENTORY_LAYERS, and database objects such as : BSACCSLS.pls BSACCSLB.pls ,
BSACAPBR, CLLACCSLS.pls, CLLPCULI.sql, CLLVPCGB.pls, CLLVPCGS.pls, are *NOT*core.

Note: If PAC process log files show process names starting "CLL" for R12 or 'BS' for R11i, PAC process has a localized
code. In this case, please create a Service Request using (Product if 1671 > Country (Ej.Brazil > Periodic Costing or
Costing Issues)). Cost Management does not own any localized code, database object. All CLL, BS localized code,
processes, modules are owned by Localizations Team.

Note2: Always attempt to reproduce issues using Core Periodic Average Costing processes. If customer reproduces
the reported issue when executing Core Processes, Global Cost Management Support Team will assist promptly.

4. Review the latest Patches released for PAC/IPAC

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xu7ae1hb3_4&id=1928724.1 7/13
2020/5/18 Document 1928724.1

4.1 Release 11.5.10.2 (Minimum Patch Set)

Patch.7555553 CONSOLIDATED PATCH FOR PAC/PACP in 11.5.10

Note: This is a consolidated patch containing all the 20 bug fixes released over the time.Therefore, it is required to
verify the respective bug fixes by looking at the list of included patch list in the ARU definition.

4.2 Release 12.0.X: None

4.3 Release 12.1.X (Descending creation date):

Patch.20222005:R12.BOM.C IPV POSTED TO MATERIAL COST ELEMENT INSTEAD OF OUTSIDE PROCESSING COST
ELEMENT
CSTPACQB.pls 120.22.12010000.16

Patch.20179846:R12.BOM.C THE ERV ACCOUNTING ERROR IN THE PO RETURN TO VENDOR TRANSACTION FOR PAC
CSTAPPRB.pls 120.15.12010000.20

Patch.19820541:R12.BOM.C BALANCE IS NOT ACCOUNTED AS WIP VARIANCE FOR WIP JOB CLOSE TRANSACTION
CSTPWCLB.pls 120.4.12010000.2

Patch.19878796:R12.BOM.C PERIODIC ACCRUAL REBUILD RECONCILIATION REPORT (XML) IN ERROR

CSTRACRR_XML.xml 120.0.12010000.2

Patch.18849980:R12.BOM.C RTV TRANSACTION WITH VARIANCE VALUE MISSING ACCOUNTING IN PAC

CSTAPBRB.pls 120.48.12010000.26

Patch.18882415:R12.BOM.C PERIODIC ACTUAL COST WORKER LOGFILE SHOWS MANY MESSAGES

CSTPINVB.pls 120.27.12010000.14

Patch.18750175:R12.BOM.C PAC: EXPENCE NON-STANDARD DISCRETE JOB HAVE ERROR VALUE WHEN JOB CLOSE
VARIANC
CSTPWMTB.pls 120.8.12010000.3

Patch.18696918:R12.BOM.C 30011AN INVALID ACCOUNT IS ASSOCIATED WITH THE ITEM BEING TRANSACTED
CSTALBRB.pls 120.6.12010000.4
CSTALPCB.pls 120.11.12010000.7

Patch.15926694:R12.BOM.C PERIODIC COST DISTRIBUTIONS PROCESSOR WITH POOR PERFORMANCE

CSTALPCB.pls 120.11.12010000.5

Patch.20978917:R12.BOM.C PAC DRILLDOWN PAC RECEIVING/ACCRUAL JOURNAL GET UNLIMITED DUPLICATE DATA
cstcxla.odf 120.67.12010000.44

Patch.16757110:R12.BOM.C EXTREME NEGATIVE BALANCE IN WIP_PAC_PERIOD_BALANCES TABLE

CSTPWROB.pls 120.10.12010000.6
CSTPWASB.pls 120.33.12010000.19

Patch.17338365:R12.BOM.C PERIODIC COGS REVENUE COGS MATCHING REPORT OUTPUT IS INCORRECT

CSTRCMVB.pls 120.45.12010000.72

Patch.17438958:R12.BOM.C MISSING INVENTORY DISTRIBUTIONS IN PAC

CSTVIIPB.pls 120.51.12010000.16

Patch.17389595:R12.BOM.C SEVERAL INVENTORY TRANSACTIONS NOT COSTED IN PAC (COST MANAGEMENT)

CSTFDPCC.fmb 120.17.12010000.8

Patch.16558430:R12.BOM.C PAC: ITEM COST VARIANCE AMOUNT IS INCORRECT

CSTVIIPB.pls - 120.51.12010000.15
CSTRITPB.pls - 120.52.12010000.17

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xu7ae1hb3_4&id=1928724.1 8/13
2020/5/18 Document 1928724.1

Patch.16594567:R12.BOM.C ISSUE WITH PERIOD CLOSE RECONCILIATION REPORT(XML) AFTER PATCH 10167016
CSTRPCRE_XML.xml 120.0.12010000.5
CSTRPCRE_XML.rtf 120.1.12010000.7
CSTRPCREB.pls 120.2.12010000.2
CSTRPCRES.pls 120.0.12010000.2

4.4 Release 12.2.X: None

4.5 For issues with IPAC:

Please be sure the latest version of file CSTVITPB.pls is applied

For 12.1.3 (Descending creation date)

Patch.19199048:R12.BOM.C IPAC WRONG CALCULATION on variance when scrap existed

CSTVITPB.pls 120.7.12010000.12
CSTVITPS.pls 120.2.12010000.1

Patch.17558429:R12.BOM.C HUGE VARIANCE OCCURS IN WIP PAC PERIOD BALANCES

CSTPWROB.pls 120.10.12010000.6

5. Resolving PAC/IPAC Performance Issues

Please proceed with the following steps in a Test Environment where issue is replicated:

5.1 Proceed Running Gather Schema Statistics

5.1.1 Connect to System Administrator Responsibility.

5.1.2 Go to Concurrent > Requests.
5.1.3 Run the Gather Schema Statistics concurrent with the following parameters:
5.1.4 Schema Name = BOM, Estimate Percentage = 90, accept all other parameters.
5.1.5 Also perform Step# 3 for the XLA, INV, WIP, PO Schemas.
5.1.6 In most of the cases, gathering statistics once a month with a sample size of 30% is enough for E-Business
Suite.
5.1.7 Please for more information review, Concurrent Processing - How To Gather Statistics On Oracle Applications
Release 11i and/or Release 12 - Concurrent Process,Temp Tables, Manually (Doc ID 419728.1)
5.1.8 Re-run the process and verify the performance issue is resolved.
5.1.9 In case the problem is resolved, then migrate the solution as appropriate to other environments.

5.2 Review the following Document

5.2.1 PAC Cleanup Script to Improve Performance (Doc ID 407099.1)

In case the previous Actions did not resolve the issue please proceed with Step# 4, in order to confirm you are
currently in the latest File Version for the Process with performance Issues.

6. Identify File Name and File Version for PAC/IPAC Processes

6.1 To find the related File Name please review the following Document:

Costing Programs and related Files (Doc ID 1314276.1)

6.2 To find the File Version:

A) You can use the commands like the following: Replace the $XX_TOP/filename with the location found from
Previous point

strings -a $XX_TOP/filename |grep '$Header'

B) Run Diagnostic Apps Check concurrent program.

Diagnostics Apps Check (Doc ID 838707.1)

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xu7ae1hb3_4&id=1928724.1 9/13
2020/5/18 Document 1928724.1

C) Generate the CstCheck.sql output. Please review.

Data Collection Scripts for Cost Management (Doc ID 378348.1)

6.3 Once the File Version(s) has been identified, find the latest File(s) Version. Please use the MOS>Patches &
Updates>Search for finding the latest Patch for specific File Name and Release.

6.3.1 Access to MOS>Patches & Updates>Search

6.3.2 Select Product or Family (Advanced) option and enter the required information. Following is an example
when searching patches via MOS>Patches & Updates, the following values were entered for finding the latest Patch and
File Version for File Name = CSTRCMVB.pls

Product is: Oracle Bills of Material

Release is: Applications R12.1
Platform is: HP-UX Itanium
Includes File (Applications Only): CSTRCMVB.pls

Observation: File Version is a hidden column, in order to add the File Version Column, please go to
View>Columns>Manage Columns.., select File Version and move the column name to the Visible Columns Section (Or
you could do View>Columns>Show All, to display all columns). After this, you might order by File Version in Sort
Descending, with this you will have the latest Patch released from Development Team.

6.4 If not on the latest File(s) Version, download and apply the latest patch into the Test Instance. Please review the
following information for analyzing the impact of applying a Patch:

6.4.1 R11i / R12 : Patch Wizard Utility [Video] (Doc ID 976188.1)

6.4.2 Patch Wizard FAQ [Video] (Doc ID 976688.1)

6.5 Once the Patch has been applied, re-test the process.

7. Is the Issue still happening? then proceed with the following Actions

In case you completed all the previous steps and the issue is still happening, then continue logging an SR and provide
the following information based in the specific situation:

7.1 For issues related to PAC/IPAC Processes

7.1.1 Upload a fresh output of CstCheck.sql which will confirm your File Version is the latest one released from
Development.

Description: Cost Collector Script, shows cost setup by organization, File versions, invalid objects. Customer name is
a required input and can be any name and is used for the name of the report. The output will be spooled as file
name CstDiag.txt. For release 12 Provide the output of the collector script Cstcheck Release 12, for release 11
Provide the output of Cstcheck.sql Release 11.

7.1.2 Provide FND Log Messages

Set profile option as follows:

MRP: Debug Mode --> YES

CST: Cost update debug level: full
FND: Debug Log Enabled --> Yes
FND: Debug Log Module --> %
FND: Debug Log Level --> statement
FND: Message Level Threshold= 'Debug Low'

Run the "Periodic Acquisition Cost Processor","PAC average cost processor" for the issue period and provide us
with

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xu7ae1hb3_4&id=1928724.1 10/13
2020/5/18 Document 1928724.1

A) Upload the Log File of the process with the problem.

B) Upload the following query output in a xls file with column headers

SELECT log_sequence, module,message_text

FROM fnd_log_messages
WHERE transaction_context_id in (select transaction_context_id
FROM fnd_log_transaction_context
WHERE transaction_id = &request_id)
ORDER BY log_sequence;

For all the concurrent requests("Periodic Actual Cost Worker") launched.

7.1.3 Confirm, via Service Request, if you are currently utilizing either IPAC or Core PAC.

7.1.4 Upload following PAC/IPAC scripts:

Required Scripts for general issues

pac_setup_12+.sql
Description: This script spools the PAC setup information to a file pac_setup.lst. Script should be run from sql
prompt.
Collect data from PAC tables to review PAC setup for a specific item into a child and master organizations.
User can review categories, cost group, accounts, period status, processes status, cost item, current onhand
and invalid objects.
Need to enter with the following parameters: None

pac_setup_11510.sql
Description: This script spools the PAC setup information to a file pac_setup.lst. Script should be run from sql
prompt.
Collect data from PAC tables to review PAC setup for a specific item into a child and master organizations.
User can review categories, cost group, accounts, period status, processes status, cost item, current onhand
and invalid objects.
Need to enter with the following parameters: None

pac_txn_4_item.sql
Description: Collector script for a specific for a problematic item. The output will be spooled into a file named
pac_inv_txns.lst
Need to enter with the following Parameters:
&pac_cost_type_id
&pac_cost_group_id
&item_id

Required Scripts for PO related Issues

pac_po_data.sql
Description: Collector script for a particular Purchase Order in question. Provide the queries in excel sheet.
Need to enter with the following Parameters:
&po_number
&operating__unit_id

pac_po_data_4_adj.sql
Description: Collector script to generate PO information for Periodic Acquisition Cost Adjustment Processor.
The output will be spooled into a file named pac_po_data_4_adj.lst
Need to enter with the following Parameters:
Transaction Date of the PCU Transaction between &from_date and &to_date
&pac_cost_group_id
&cost_type_id

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xu7ae1hb3_4&id=1928724.1 11/13
2020/5/18 Document 1928724.1

PAC_po_details_lcm_enabled.sql
Description: Collector script for a particular Purchase Order which LCM Flag enabled. The output will be
spooled into a file named pac_po_details_lcm_enabled.lst
Need to enter with the following Parameters:
&po_number
&po_header_id
&pac_cost_group_id
&pac_cost_type_id

Required Scripts for WIP related Issues

pac_job_data.sql
Description: Collector script for a specific Job ID. The output will be spooled into a file named
pac_job_data.lst
Need to enter with the following Parameters:
&pac_cost_type_id
&cost_group_id
&job_id
&org_id

7.2 For issues related to PAC/IPAC Performance Issues

7.2.1 Upload a fresh output of CstCheck.sql which will confirm your File Version is the latest one released from
Development.

Description: Cost Collector Script, shows cost setup by organization, File versions, invalid objects. Customer name is
a required input and can be any name and is used for the name of the report. The output will be spooled as file
name CstDiag.txt. For release 12 Provide the output of the collector script Cstcheck Release 12, for release 11
Provide the output of Cstcheck.sql Release 11.

7.2.2 Provide the following information related to Gather Schema Statistics

* Frequency (monthly/weekly/daily/etc.):
* Method (per table/schema/all schemas):
* Tool (COE_STATS/FND_STATS/DBMS_STATS/ANALYZE):
* Estimate percentage used:
* Last time stats were gathered:

7.2.3 Generate and Upload TKPROF Trace File for the process with Performance issue. For more information about
generating TKPROF Trace File, review the following Document:

How To Trace a Concurrent Request And Generate TKPROF File (Doc ID 453527.1)

7.2.4 Generate and Upload Explain Plan. For more information review the following Document:

SQLT Diagnostic Tool (Doc ID 215187.1)

7.2.5 Upload the Log File of the Process having the Performance Issue.

7.3 For issues related to Errors at PAC/IPAC Log Files

7.3.1 Upload a fresh output of CstCheck.sql which will confirm your File Version is the latest one released from
Development.

Description: Cost Collector Script, shows cost setup by organization, File versions, invalid objects. Customer name is
a required input and can be any name and is used for the name of the report. The output will be spooled as file
name CstDiag.txt. For release 12 Provide the output of the collector script Cstcheck Release 12, for release 11
Provide the output of Cstcheck.sql Release 11.

7.3.2 Upload Log File with the Error.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xu7ae1hb3_4&id=1928724.1 12/13
2020/5/18 Document 1928724.1

Still Having Questions?

Please, to discuss this information further with Oracle experts and industry peers, we encourage you to review, join or
start a discussion in the My Oracle Support Cost Management - EBS (MOSC) Community.

To provide feedback on this note, click on the Rate this document link.

REFERENCES

NOTE:1665376.1 - How to Resolve Performance Issues in Cost Management

NOTE:1324701.1 - HOW TO IDENTIFY PAC SETUP ISSUES

NOTE:559123.1 - FAQ Periodic Average Cost and Periodic Absorption CostingOSTING (PAC/PACP/IPAC) Interorg
Transactions in PAC
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=xu7ae1hb3_4&id=1928724.1 13/13