APPLIES TO:

MAIN CONTENT

Purpose

 Script showing how to perform administrative tasks including health checks

Requirements

 N/V

Configuring

 N/V

Instructions

 Inculded in each step

Script

 Attched

Sample Output

Enter the Main Content

 
Costing Scripts Brown Bag

COGS

Margin_Analysis_Report_Queries.sql

COGSDIAG.SQL

WIP Costing

Inventory Period Closing Activity Test

Job.sql

CstCheck.sql

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 Release 11.

Output;

Report started at Date/Time; The date and time the CstCheck.sql was run

Database Name and Created Date

Oracle RDBMS/Tools Version(s)

NLS Parameter Settings

Profile Option Values

Organization Structure; Costing information by organization

Organization Accounts; Accounts set up in Organization Parameters

Cost group Accounts; Accounts set up by Cost Group

Interorg Parameters; Setup in Shipping Networks form

Wip Parameters; Displayed by organization

Package Versions; Costing Package versions

Checking Product Tops;

Product Reports Directory; Costing reports file versions

Product Forms Directory; Costing forms file versions

Product Resource Directory;

Product Workflow Files; Costing workflow file versions

Product ODF Files; Costing ODF file versions

Product Pro*C Files; Pro*C file version

Invalid Objects

[top]

Costing_hook.sql?

Description: Collector script, to review costing hooks. A file will be spooled with name hook.txt.

Output;

Instance name and date of run;

CSTPSCHK PACKAGE SPEC; Package spec for standard cost hook.

CSTPSCHK PACKAGE BODY; Package body for standard cost hook

CSTPACHK PACKAGE SPEC; Package spec for transaction cost hook

CSTPACKH PACKAGE BODY; Package body for transaction cost hook

Accruals Setup Diagnostics Test

Description: This diagnostic test will collect and diagnose setup data related to Accruals and Accounting Reports. This test should be used proactively to check the setup of the accruals. It can also be used reactively to help resolve existing accruals issues. Error and warning messages, followed by suggested actions, identify possible problem areas. The Accruals Setup Diagnostics Test available through the Self Surface Diagnostic program. (See Note 251052.1 for instructions)

Output:

System Information

Application Information

Related Product Installation Status

Purchasing and Financials Options

Purchasing Periods

General Ledger Periods

Payables Periods

Inventory Periods for Current Operation Unit

Accounts by Inventory Organization for Current Operation Unit

Open Purchase Order Information

Account Numbers used as the Accrual Account on Purchase Orders

Purchasing Records in the GL_INTERFACE table

Unposted Journals in General Ledger with a Source of Purchasing

Table Indexes

Accounting Specific File Versions and Object Statuses

[top]

Expense_accrual.sql

Description: Collector script, to verify by organization if accruals are set up as on-line.

Output;

Organization ID;

Expense Accrual Code; Accrual option for expense items

Inventory Accrual Code; Accrual option for inventory items

Accrual Code Combination Id; Unique identifier of the Receipt accrual General Ledger account

[top]

Online_accrual_PO.txt

Description: Collector script for issues related to on-line accruals. The file Online_accrual_PO.txt have five scripts that have to be ran individually. Required inputs are Organization ID and sample POs. The following are additional requirements needed when providing the output of the script:

(1) Provide version of $PO_TOP/reports/US/POXACREC.rdf

(2) Provide versions of rvtac.opc and rvacj.lpc in executable $PO_TOP/bin/RVCTP

(3) Provide log file and report output and highlight the problem in the same.

(4) Identify sample PO Numbers associated with the problem reported and run scripts given below for couple of them.

(5) Run following statements for sample POs identified in step 4 and provide output.

org_id is the Operating unit id which can be obtained from the applications using the navigation path;

help->Diagnostics->Examine

Block- $profile$

field - ORG_ID

Before running the queries operating unit context has to be set

PROMPT Script needs following values as input:

(If this is not set, then it is possible that query 2 would not return rows)

PROMPT org_id => operating_unit_id

SET line pages 9999

SET line 300

exec apps.fnd_client_info.set_org_context ('&org_id');

Output;

query #1; PO_HEADER_ID and PO_NUM

query #2; Using the PO_HEADER_ID from the output of query #1, will provide the PO accounting information.

query #3; Using the PO_HEADER_ID from the output of query #1, will provide the receiving transaction information.

query #4; Using the PO_HEADER_ID from the output of query #1, will provide the receiving accounting entries.

query #5; File versions

[top]

Period_end_accrual_ininvoiced_report.txt

Description: Collector script for issues related to Period End Accrual and Uninvoiced Receipts Report for organization that are not on-line accruals. The file Online_accrual_PO.txt have five scripts that have to be ran individually. Required inputs are Organization ID and sample POs. The following are additional requirements needed when providing the output of the script:

(1) Provide version of $PO_TOP/reports/US/POXPORRA.rdf

(2) Provide versions of rvcac.opc and rvacj.lpc in executable $PO_TOP/bin/RVCACR

(3) Provide log file and report output and highlight the problem in the same.

(4) Identify sample PO Numbers associated with the problem reported and run scripts given below for couple of them.

(5) Run following statements for sample POs identified in step 4 and provide output.

org_id is the Operating unit id that can be obtained from the applications using the navigation path;

help->Diagnostics->Examine

Block- $profile$

field - ORG_ID.

Before running the queries operating unit context has to be set

PROMPT Script needs following values as input:

(If this is not set, then it is possible that query 2 would not return rows)

PROMPT org_id => operating_unit_id

SET line pages 9999

SET line 300

exec apps.fnd_client_info.set_org_context ('&org_id');

Output;

query #1; PO_HEADER_ID and PO_NUM

query #2; Using the PO_HEADER_ID from the output of query #1, will provide the PO accounting information.

query #3; Using the PO_DISTRIBUTION_ID from the output of querry#2, will provide the invoice information

query #4; Using the PO_HEADER_ID from the output of query #1, will provide the receiving transaction information.

Query #5; File versions

[top]

Accrual.txt?

Description: Collector script for issue with the Accrual Reconciliation report. Required input Organization Id, Set of Books Id(Navigation path to get set of Books_ID, Setup >Organizations > Set of Books > Choose), From GL Date and To GL Date. A file will be spooled with name info.lst

Output;

Different Accrual Accounts; Accrual Account Ids when accrue is set at receipt

Values from RRSL; Receiving accounting information for receiving transactions

Values from MTA; Inventory accounting information

The data from AP side; Data from Accounts Payable

Data from Accounts Payable that has transferred to GL

Values from WTA; WIP accounting information

Mismatch in amount in PAWO and PART for PO transactions; Mismatch between PO Write Offs and part for POs

mismatch in accrual code or tqty in POWO and PART for PO transactions;

Missing in PART for PO transactions;

Missing in PAWO for PO transactions; PO Accrual Write Offs for PO txns.

Mismatch in amount in POWO and PART for AP transactions;

Mismatch in accrual code or txn quantity in POWO and PART for AP transactions

Missing in PART for AP transactions;

Missing in PAWO for AP transactions;

Total Written Off amount for PO transactions;

Total Written Off amount for INV transactions;

Total Written Off amount for WIP transactions;

Total Written Off amount from PART;

[top]

purchasing_drill_down.sql?

Description: Diagnostic for Drill down problems in Purchasing journals. This will create a spool file with purch_je_header_<>. There is an input requirement of je_header_id. The je_header_id can be obtained from journal inquiry screen navigation path; General Ledger > Journals > Inquiry > Journal, At the journal inquiry go to Diagnostics -> Examine -> Block : Header -> Field : JE_HEADER_ID.

Output;

Instance name and date of run;

Value from GL drill down view;

Value from RRSL (Purchsasing sub Ledger);

Value from GL;

Duplicate GLIR(GL_IMPORT_REFERENCES) If this query gives output then the drill down may give duplicate records;

Referenc3 (PO_DISTRIBUTION_ID) null in RRSL, this is a data corruption in Receiving sub ledger;

RCV_TRANSACTION_ID null RRSL, This is a data corruption in Receiving sub ledger;

Missing RCV_SHIPMENT_HEADERS, This is a data corruption in Receiving Transactions;

Missing PO_Vendors, This is a data corruption in PO tables;

Missing PO_Vendor SITE, This is a data corruption in PO tables;

Missing PO Distribution, This is a data corruption in PO tables;

Missing PO Headers, This is a data corruption in PO tables;

Missing PO Line Location, This is a data corruption in PO tables;

Missing PO Lines, This is a data corruption in PO tables;

Missing gl import reference_5, This is a data corruption in GL import references table;

Inventory Period Closing Activity Test

Description: This diagnostic test checks all mandatory and recommended requirements necessary to allow a successful Inventory period close. Required Input; Organization Id and Inventory Period name available from a list of values. The Inventory Period Closing Activity Test is available through the Self Surface Diagnostic program.(See Note 206576.1 for instructions)

Output;

Input Parameters

Application Information

Inventory Related Product Patchset Level

Period Information

Organization Information

Unprocessed Material Transactions; Pending Material Transactions, values for Error Code and Error Explanation,

Uncosted Material Transactions; Uncosted Material Transactions, Types of Errors

Pending WIP costing transactions; Pending Resource Transactions, Values for Processing Phase and Process Status

Uncosted WSM transactions; Uncosted WSM Transactions, Values for Status and Costed Flag

Pending WSM interface transactions; Pending transactions in the Interface table for lot based WIP Lot Transactions.

Pending Receiving Interface Transactions; Unprocessed purchasing transactions.

Pending Interface Material Transactions; Pending material transactions in the interface table.

Pending Shop Floor Move Transactions; Pending move transactions

Unprocessed Shipping Transactions; Unprocessed Shipping Transactions

Material Transactions not in GL Batches;

WIP Transactions not in GL Batch;

Transaction Interface Manager; Inventory Interface Manager Setup

Cost Manager;

Concurrent Requests for Cost Manger in phase running or pending

Concurrent Requests for Cost Manager (max. latest 5 requests)

Lot Move Transactions Manager;

Concurrent Requests for Manager: Lot Move Transactions in phase running or pending

Concurrent Requests for Manager: Lot Move Transactions (max. latest 5 requests)

[top]

BDEperiodClose.sql

Description: Collection script for identifying any pending or uncosted transactions that may prevent or are recommended for closing an Inventory Period. The transactions are identified by organization and period. Required input Organization Id and Period Id available from a list of Values. A file will be spooled name of the .lst.

Output;

UNPROCESSED MATERIAL; Pending material transactions

UNCOSTED MATERIAL; Uncosted material transactions

PENDING WIP COSTING; Pending resource transactions

UNCOSTED WSM TRANSACTIONS; Uncosted Lot Base Job transactions

PENDING WSM INTERFACE; Pending transactions in the Interface table for lot based WIP Lot Transactions.

PENDING RECEIVEING; Unprocessed purchasing transactions.

PENDING MATERIAL; Pending material transactions in the interface table.

PENDING SHOP FLOOR MOVE; Pending move transactions

PENDING TRANSACTIONS; Pending shipping transactions

[top]

cmlwmx.sql

Description: Collection script for transactions that are costed in error in the MTL_MATERIAL_TRANSACTIONS table. The output will be spooled with file name data.lst.

Output;

Organization Parameters; Org. Parameters with erred costed transactions

Get org_acct_periods data; Org. Account Period data for orgs. with erred costed transactions

MMT data; Data of erred cost transactions

WE Data; WIP Entity data for WIP material transaction that are costed in error

WDJ Data; WIP Discrete Job data for WIP material transaction that are costed in error

WFS Data; Work Flow Schedule data for Flow material txns. that are costed in error

WRS Data; Repetitive Schedule data for Repetitive Schedule material txns that are costed in error

WAC Data; WIP Accounting Class data for WIP material txns. that are cost in error

Item cost data; Item Cost Data for WIP material txns. that are costed in error

WPB (wip_period_balances) Data; WIP Period Balance information for WIP material txns. that are cost in error

WCTI (wip_cost_txn_interface) Data; Pending Resource transactions in status error

MMTA data; Allocation data for transactions in error

[top]

Txn.sql

Description: Collector script for a specific item in a specific organization. Required input organization_id and inventory_item_id. The output will be spooled into a file named diag.lst.

Output:

Get org parameters; Organization parameters for inputted oraganization_id

Get currency info for org; Organization currency information

Inter Organization Parameters; Organization Inter-org parameters from

MMT (mtl_material_transactions) data; Material transactions

CQL data; Average cost information by cost layer

CLCD data; Detailed cost information by element and level

MCTCD data; Transaction cost by element and level

MCACD data; Transaction actual cost, prior cost, and new cost

MTA data; Accounting information for each transaction

CIC Data; Item cost control information by cost type

CICD Data; Detailed item cost information by cost type

MOQ Data; On hand quantity by Subinventory and Cost Group

MSE data; Organizations Subinventory data

MS Data; Incoming shipment and receiving Supply Information

Purge data; Details of transaction purges by organization

[top]

err_txn.sql

Description: Collection script for transactions that are costed in error in a perpetual costing organization. The output will be spooled with file name diagnose.lst.

Output:

Org parameters; Organization Parameters for organizations with erred costed transactions

Cost group accounts; Cost Group Accounts for organizations with erred costed transactions

Acct periods in orgs with error; Account Periods for organizations with erred costed transactions

Inter-org parameters; Inter-org parameters for organizations with erred costed transactions

MMT Error code and explanation; Error Code and Error explanation for organizations with erred costed transactions

Erring txns MMT; Material transaction information for erred transactions

MMTT stuck records; Pending Material transactions linked to erred costed transactions

Get cst quantity layers; Item average cost information by cost layer for erred costed transactions

Get clcd; Detailed item average cost information by cost layer for erred costed transactions

Associated txn details for inter-org and backflush; Data of erred, Direct org transfer, intransit transactions.

MCTCD data; Cost of erred, direct org transfer, intransit transaction

MCACD data; Cost of erred, direct org transfer, intransit transactions

MTA (mtl_transaction_accounts) data; Accounting information for direct org transfer, intransit txns costed in error

Get cst item costs; Item cost information by cost layer for erred costed transactions

wcti (wip_cost_txn_interface) errors; Error Message and error column of erred pending resource transactions from

wcti (wip_cost_txn_interface) error txns; Data from erred pending resource transactions,

File versions; File versions of costing processes

MMT (mtl_material_transactions) uncosted count; Count of un-costed transactions

wcti count; Count of pending resource/overhead transactions

cost manager and worker requests that have not completed; List of cost manager and worker requests that have not completed

Invalid db objects; List of invalid data base objects

MSE data; Organizations Subinventory data, for organization with an erred cost txn.

[top]

Period_close_reconsiliation.sql

Description: Script collects costing information by organization that may cause discrepancies during the reconciliation at Period Close for average or fifo or lifo costing organizations.. Organization_id and default cost group for the organization are required inputs when running the collector script and a spooled output file basic_info.lst is created.

Output:

Get org parameters;Organization Parameters for specified organizations

Get org_acct_periods data; Inventory Period information for specified organization

Get mtl_period_summary_data; Inventory value for each subinventory in an organization.

Get mtl_perclose_dtls data; Period end quantities, costs, and values by subinventory, item, and cost group for an organization under Average Costing.

get interorg parameters; Inter-org parameters for specified

Mismatch between MMT and MOQ

Description: Discrepancies between the MTL_MATERIAL_TRANSACTIONS and the MATERIAL_ONHAND_QUANTITY table can cause reports to not reconcile.

Output: FromNote 291005.1

;Discrepancies by Organization_id, Subinventory, Item_id and quantity.

From Note 279205.1; If a mismatch between MMT and MOQ is found from note 291005.1 a Bug would then be logged with the inventory group following the instructions inNote 279205.1

Back Dated Transactions

Description: Oracle allows customers to back date transactions for their business needs. Customers need to understand that back dating transactions can affect balances when doing reconciliation if the back dated transactions are not costed in order. The cost cut off field in the organization parameters can be utilized to insure that back dated transactions are costed in order.

Output: Note 291005.1

;Organization_Id required input, if back dated transactions output will include period and count of transactions. If back dated transactions have cause reports to not reconcile no data fix can be provided.

[top]

Stdpc.sql

Description: Organizations with a Standard Costing method can utilize this script to collect inventory period balances. Organization_id is required input and spooled file stdpc.lst is created.

Output:

MTA per close value;Inventory value by Subinventory and period from MTL_TRANSACTION_ACCOUNTS table

MPS Data; Inventory value by Subinventory and period from MTL_PERIOD_SUMMARY table

purge data; Details of transaction purges by organization

[top]

Account_Info.sql

Description: Collector script for a particular account for issues where there are discrepancies between GL and Inventory. Required input acct_id (acct_id = REFRENCE_ACCOUNT and can be found through; Help Diagnostics > Examine) and sob_id (sob_id = SET_OF_BOOKS_ID and can be found through Navigation path; PO responsibility > Setup > Organization > Set of Books > Choose, Help > Diagnostics > Examine) A file will be spooled With the name glinv.lst.

Output:

MTA data; Inventory accounting information, the sum of the base_transaction_value by organization, account_line type and gl_batch_id.

WTA data; WIP accounting information, the sum of the base_transaction_value by organization, account_line type and gl_batch_id.

MTA DATA period wise; ; Inventory accounting information by period, the sum of the base_transaction_value by organization, account_line type and gl_batch_id.

WTA DATA period wise; WIP accounting information by period, the sum of the base_transaction_value by organization, account_line type and gl_batch_id.

RRSL data period wise; Receiving account information, sum of the sub ledger credit and sub ledger debit by period.

GL INTERFACE; Data collected from the GL_INTERFACE table, the sum of the account credit and account debit by gl_batch and Period.

GL INTERFACE; Data collected from the GL_INTERFACE table, the sum of the account credit and account debit by gl_batch and Period.

GL JE LINES; Sum of the account credit and account debit by org in GL, by gl_batch and journal category.

GL value for the account for the sob;

GL value for the account in all sobs;

GL Balances for Account;

PADDED_CONCATENDATED_SEGMENTS;

 [top]

Receiving_inspection.txt

Description: The receiving _inspection.txt script is a collector for collecting data impacting receiving inspection account. Required input when running the script is the organization_id and the receiving_insp_account_id, the receiving_insp_account_id can be found through the applications by navigating to: PO > Setup > Organization > Receiving Options, using Help > Diagnostics > Examine query the RECEIVING_ACCOUNT_ID. The file will automatically spool an output file name info_of_rcv.lst.

Output:

MP data and RP data; Organization parameter information

MTA DATA period wise; Base sum, receiving account transaction value by period and organization.

WTA DATA period wise for OSP and Direct Item transactions; Value of WIP, OSP and Direct Item transactions by receiving inspection account and period.

WTA DATA period wise for NON-OSP (If the customer has charged the OSP resource manually); Value of WIP for manually charged OSP transactions by receiving inspection account and period.

RRSL data period wise; Receiving accounting information

GL Interface Value for Inventory Source; Data collection from the GL_INTERFACE table for records with a receiving inspection account and sourcing is from inventory.

Interface Value for NON Inventory Source: Data collection from the GL_INTERFACE table for records with a receiving inspection account and sourcing is not inventory.

GL VALUE; Summation of credits and debits by period and category for Journal entries.

Account supplied by the Customer; The account code combination for the account_id that was inputted when running the receiving_inspection.txt. Value which receiving value report would be showing now;

The destination_type_code, source_document_code and value that will used when running the receiving value report.

Value which receiving value report would be showing for document PO if tax and currency rate for the match option is incorporated in the report;

Check if the expense destination POs are also accrued at receipt; Collector script, to verify if accruals are set up as on-line.

This SQL will give the scenarios where the Ratio value of 'RECEIVE' is not equal to ratio value of 'DELIVER' for receiving inspection account in RRSL and MTA. RRSL is the RCV_RECEIVING_SUB_LEDGER table, MTA is the MTL_TRANSACTION_ACCOUNTS table

This SQL will give the scenarios where the Ratio value of 'RECEIVE' is not equal to ratio value of 'DELIVER' for receiving inspection account in RRSL and WTA. RRSL is the RCV_RECEIVING_SUB_LEDGER table, WTA is the WIP_TRANSACTION_ACCOUNTS table

The following SQL give details of transactions which have got wrong accounting in RRSL. It might also get the details of the transactions for which the po price or tax was changed after returning to vendor all the qty and the accounting may be correct. So we will have to look into details of these transactions to confirm whether the transactions really have problem. RRSL is the RCV_RECEIVING_SUB_LEDGER table

The following SQL give details of the Delivery or correct transaction that has got wrong accounting in MTA. It might also get the details of the transactions to confirm if these transactions really have a problem for which the po price or tax was changed after returning to vendor all the qty and the accounting may be correct. So we will have to look into details of these transactions. MTA is theMTL_TRANSACTION_ACCOUNTS table

The following SQL give details of the Delivery or correct transaction that has got wrong accounting in WTA. It might also get the details of the transactions for which the po price or tax was changed after returning to vendor all the qty and the accounting may be correct. So we will have to look into details of these transactions to confirm whether the transactions really have problem. The WTA is WIP_TRANSACTION_ACCOUNTS table

The following SQL would give all those instances where there is value in receiving inspection account but there is no record in mtl_supply. Comparing records in the RCV_TRANSACTIONS table

The RECEIVE transactions which does not have accounting in RRSL. RRSL is the RCV_RECEIVING_SUB_LEDGER

The deliver transactions to inventory which do not have MTA. MTA is the MTL_TRANSACTION_ACCOUNTS table

The deliver transactions to SHOP FLOOR which do not have WTA. WTA is the WIP_TRANSACTION_ACCOUNTS table

 [top]

Inv_drill_down.sql?

Description: The inv_drill_down.sql is a collector script for issues with the Drilling down in the Inventory journals. This will create a spool file with inv_je_header_<> Customer needs to give input as je_header_id and organization_id. The je_header_id can be obtained from the journal inquiry screen, at the journal inquiry go to Diagnostics -> Examine -> Block : Header -> Field : JE_HEADER_ID

Output;

Organization Parameters; Org parameter for the specified organization

Value from GL drill down view of MTA(Inventory Sub Ledger;

Value from GL drill down view of WTA (wip sub ledger);

GL_JE_HEADERS;

GL_IMPORT_REFERENCES;

Value from GL;

Value from GL period wise;

Duplicate GLIR If this query gives output then the drill down may give duplicate records;

MTA Values for the GL batch id;

MTA Value for the GL batch id period wise;

WTA Values for Gl batch id;

WTA Value for the GL batch id period wise;

Instance name and date of run;

Job.sql

Description: The Job.sql is a collector script to gather details and costing information of a specific Job. Required input when running the script is the organization_id and the wip_entity_id. A spooled output file job.lst is created.

Output:

org parameters; Org parameters for the specified organization

wip parameters; WIP parameters for the specified organization

acct periods; Inventory Account information by period for the organization specified.

currency info; Currency information for organization specified

we data; Job information from WIP_ENTITIES table

wdj data; Job information from WIP_DISCRETE_JOBS table

wfs data;Job information from WIP_FLOW_SCHEDULES table

wac data; WIP accounting information for the specified Job

mmt data; Material transactions information for the specified Job

mta data; Material Accounting information for the specified Job

mctcd data; Transactions cost by element and level for the specified Job

mcacd data; Transactions actual cost, prior cost, and new cost information by element and by level.

wt data; WIP resource transactions information for specified Job

wta data; Accounting information for each resource transaction

wcti data; Pending resource transactions for the specified Job

wpb data; Summary charges for the specified Job by period

wro; Material requirements and issued for the specified Job

wrocd; Material costs earned by and relieved from the job in an average costing organization.

wo; Information about the operations for a specified job and completed quantity

wor; Information about the resource requirements associated with the job

woo; Stores information about resource-based and departmental overhead costs for jobs in an average costing organization.

ccs; Snapshot information of completions by operation used for calculating assembly completions and returns in an average costing environment.

[top]

Margin_Analysis_Report_Queries.sql

Description: A group of queries that provided detailed information for a specific Sales order number that is not displaying correctly in the Margin Analysis Report.

Output;

Header_id; Header_id of Sales Order number.

MMT data; Data of Sales Order transaction in the MTL_MATERIAL_TRANSACTIONS table.

MTA Data; Data of Sales Order transaction in the MTL_TRANSACTION_ACCOUNTS table.

OOLA Data; Data of Sales Order transaction in the OE_ORDER_LINES_ALL table.

OOHA Data; Data of Sales Order transaction in the OE_ORDER_HEADERS_ALL table.

RCTLA Data; Data of Sales Order transaction in the RA_CUSTOMER_TRX_LINES_ALL table.

RCTA DATA; Data of Sales Order transaction in the RA_CUSTOMER_TRX_ALL table.

RCTLGD Data; Data of Sales Order transaction in the RA_CUST_TRX_LINES_GL_DIST_ALL table.

CMS Data; Data of Sales Order transaction in the CST_MARGIN_SUMMARY table.

CMB Data; Data of Sales Order transaction in the CST_MARGIN_BUILD table.

MSI Data; Data of Sales Order item in the MTL_SYSTEM_ITEMS table.

PKG Data; Data of package CSTPRMGL.

CRCML Data; Data of Sales Order transaction in the CST_REVENUE_COGS_MATCH_LINES table.

CCE Data; Data of Sales Order transaction in the CST_COGS_EVENTS table.

CRRL Data; Data of Sales Order transaction in the CST_REVENUE_RECOGNITION_LINES table.

MTA_CCE Data; Data of Sales Order transaction in the MTL_TRANSACTION_ACCOUNTS table.

[top]

COGSDIAG.SQL

Description: The COGSDIAG.SQL is a collector script to gather detailed information on COGS and COGS Recognition transactions for a specific Sales Order. Required input when running the script is the 'Sales Order Number', a list of HEADER_IDs will be provided to select from. A spooled output file cogs.lst is created. .

Output:

Sales Order Header Data; Sales Order information

Sales Order Line Data; Sales Order Line information

MTL_MATERIAL_TRANSACTIONS Data; Data of the Sales Order transaction in the MTL_MATERIAL_TRANSACTIONS table

MTL_TRANSACTION_ACCOUNTS Data; Data of the Sales Order transaction in the MTL_TRANSACTION_ACCOUNTS table

CST_COGS_EVENTS Data; Data of the Sales Order transaction in the CST_COGS_EVENTS table

CST_REVENUE_COGS_MATCH_LINES Data; Data of the Sales Order transaction in the CST_REVENUE_COGS_MATCH_LINES table

CST_REVENUE_RECOGNITION_LINES Data; Data of the Sales Order transaction in the CST_REVENUE_RECOGNITION_LINES table

COGS Related packages versions; Package versions of COGS related files

MTL_TRANSACTIONS_INTERFACE DATA; Data of the Sales Order transaction in the MTL_TRANSACTIONS_INTERFACE table

RA_CUSTOMER_TRX_ALL Data; Data of the Sales Order transaction in the RA_CUSTOMER_TRX_ALL table

RA_CUSTOMER_TRX_LINES_ALL DATA; Data of the Sales Order transaction in the RA_CUSTOMER_TRX_LINES_ALL table

RA_CUST_TRX_LINE_GL_DIST_ALL DATA; Data of the Sales Order transaction in the RA_CUST_TRX_LINE_GL_DIST_ALL DATA table

[top]

REFERENCES