11/28/2017 Document 1565831.

DCOGS Balance Diagnostics (Doc ID 1565831.1)

APPLIES TO:

Oracle Order Management - Version 12.1.1 and later

Oracle Receivables - Version 12.1.1 and later
Oracle Cost Management - Version 12.1.1 and later
Information in this document applies to any platform.
NOTE : The script contained in the attachment section is being updated periodically. Please download it from My Oracle
Support every time you need to run it in order to have the latest version.

MAIN CONTENT

Abstract

Purpose of this diagnostic (DCOGSDiag.sql) is to identify the sales orders which constitute the Deferred COGS account balance.

This will help to get the detailed transaction details for Sales Order/s from sub ledgers like Order Management, Account
Receivables, Inventory and Cost Management at the Organization level.

OBJECTIVE

To collect the information of the sales order(s) which are at different stages of their life cycle in one spreadsheet at one go.

This will help in:

Lesser time for data collection.
Faster diagnosis of the issue.
Easy collaboration across different modules like Order Management, Accounts Receivables, Inventory and Cost
Management.

History

Date Created : 01-Jul-2013

Authors:

Suhas Basidoni

Amrish Kothari

Devaraju Holenarasipur

Details

SEQUENCE OF OPERATIONS

Create and Book the Sales order.

Pick Release the SO and Ship Confirm.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=hapi6pbde_575&id=1565831.1 1/6
11/28/2017 Document 1565831.1
Perform the Sales order Issue transaction.
Review sales order issue transactions and Source and destination transactions in the Material Transactions form.
Run the Workflow Background Process request from Order Management (OM) Responsibility.
Create the Invoice with the Auto invoice request from Accounts receivables responsibility(AR).
Check the Invoice in AR.
Recognize the revenue in AR.
After recognizing the revenue, accept it.
Run the following three Programs from Cost Management SLA.
Record Order Management Transactions.
Collect Revenue Recognition Information.
Generate COGS Recognition

DATA FLOW CHART

Functional Data Flow

R.O.M.T = Record Order Management Transactions

C.R.R.I = Collect Revenue Recognition Information
G.C.R.E = Generate Cogs Recognition Events

Table-level Data Flow

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=hapi6pbde_575&id=1565831.1 2/6
11/28/2017 Document 1565831.1

SCRIPT OUTPUT

The output of DCOGSDiag.Sql is an excel file with multiple worksheets. Each worksheet represents sales order information at
different levels.
The script should be run preferably in SQL*Plus via APPS user login.

Input Parameters:

Organization Code (Ex. M1)

Period Start Date (DD-MON-YYYY) (Ex. 01-JUN-2013)
Period End Date (DD-MON-YYYY) (Ex. 30-JUN-2013)

The output file DCOGSData.xls is created under /usr/tmp directory in the database server

HOW TO READ DCOGSDATA.XLS

Sheet #1 - OE Data

The first worksheet OE Data

in the output shows the information about all the sales orders created based on the script
parameters of period and inventory organization.

The highlighted columns in the output indicate that these are the important columns to be verified from COGS perspective. If
the column SHIPPING_INTERFACED_FLAG is set to Y, then it indicates whether a line has been interfaced to shipping or not.
LINE_CATEGORY_CODE column indicates whether the line is a normal sales order line or an RMA line.

Similarly, the columns OE_INTERFACED_FLAG and INV_INTERFACED_FLAG from shipping tables indicate whether the
Interface trip stop program is run or not. If both flags are set to Yes, that means the Interface trip stop program has been run
successfully and SO ISSUE transaction must have been completed. The column INVOICE_INTERFACE_STATUS_CODE,
indicates whether the order line data is sent to AR invoicing interface tables or not. If it is set to Yes and invoice quantity is
non zero, that means the line is interfaced to AR invoice interface tables.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=hapi6pbde_575&id=1565831.1 3/6
11/28/2017 Document 1565831.1
Action:

Why the Sales order issue transaction didnt triggered.

Whether it is stuck in Inventory temp table? If Yes, these needs to be processed.

Sheet #2 - OE Not Invoiced

The Second worksheet OE Not Invoiced shows all the sales order lines that are NOT invoiced.

Action:

Review the highlighted columns from Sheet 1 and check what is the issue. Is the line is interfaced to shipping. If so
whether the ITS is run. If ITS is run, check whether the delivery detail lines are properly interfaced to OM and
Inventory.
Check whether the invoicing activity has been completed successfully.

If further analysis is required, get the HTMomse12(Note: 133464.1) output for the specific order and verify.

Sheet #3 - AR Interface

The worksheet named AR Interface shows all the sales orders/lines are stuck in the AR invoice interface tables.

Action:

To understand the issue further, get the HTMomse output for the sales order number shown in this worksheet. ( Refer
to the Note 133464.1)
The information of HTMomse output can be obtained by running the concurrent request, Diagnostics OM Order
informationfrom the order management responsibility. Get the issue resolved from OM and AR stand point.

Sheet #4 - In OE, Not In AR

The worksheet named In OE, Not In AR shows all the sales orders/lines which are closed and invoicing is complete from OM
side, however Invoices are not created in receivables base invoice tables.

Action:

To understand the issue further, get the HTMomse output for the sales order number shown in this worksheet. Based on
the review analysis, request for datafix from OM/AR team.

Sheet #5 - AR Data

This excel sheet namely AR Data output shows number of sales order(s) which are moved from Order management to
Accounts Receivables module. These are the valid sales records for which revenue recognition needs to be done.

Action:

Perform Revenue Accounting from AR responsibility.

Check whether it completes normal. If not, need to check with the Accounts Receivables support for the error
mentioned in the log file.

Sheet #6 - AR Distributions

The worksheet named AR Distributions provides the data of those sales orders for which Revenue recognition have
happened. Data to this script output will mainly captured from the table RA_CUST_TRX_LINE_GL_DIST_ALL.

Columns which are important and to be checked are:

Percent: If this column value is showing 100 it does mean that, revenue is recognized fully for the concerned sales
order. If percent shown is other than 100 then it is case of Partial revenue recognition.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=hapi6pbde_575&id=1565831.1 4/6
11/28/2017 Document 1565831.1
Amount & Accounted Amount: If the revenue recognition is happened fully, then these amounts will match.

Action:

Confirm the revenue recognition percentage.

Run the Generate COGS Recognition Events concurrent program and check with the Accounts Receivables Support team
for the error mentioned in the log file.

Sheet #7 - COGS Data

The worksheet named COGS Data will present the records which are cogs recognized. Data in this worksheet is captured
from 3 tables.

Cst_Revenue_Cogs_Match_Lines
Cst_Cogs_Events
Cst_Revenue_Recognition_Lines

Important columns to be checked:

COGS_PERCENTAGE: For the cogs recognition transaction COGS Percentage will be 1

POTENTIALLY_UNMATCHED_FLAG: Will be null if Generate COGS Recognition events program is run successfully. If it is
Y then only Collect Revnue Recognition program has been run from AR Responsibility , but Generate COGS Recognition
Events program has not been run. If the status is P then these are unprocessed records.

Action:

Need to upgrade the below mentioned file versions by applying latest released patch.
$BOM_TOP CSTRCMVB.pls
$BOM_TOP CSTRCMVS.pls
$AR_TOP ARCGSRVB.pls
Datafix will be provided based on the data to make Potentially_Unmatched_Flag to Y and run the Generate COGS
Recognition events program again.
If for certain reasons, records have not been inserted into Cst_Revenue_Recognition_Lines table then check with
Accounts Receivables support team.

Sheet #8 - MMT Data

The worksheet named MMT Data will present the entire Inventory transactions for the sales orders from
Mtl_material_transactions table.

Action:

Check the each line of the Mtl_Material_Transactions table corresponding to Sales order issue transactions and compare
with the COGS transactions.

Sheet #9 - MTA Data

The worksheet named MTA Data will present the entire Inventory transactions distributions for the sales orders from
Mtl_Transaction_Accounts table. These are the corresponding material accounting distributions for the sales order related
transactions. Further drill down is possible based on the INV_SUB_LEDGER_ID column till GL.

Action:

Please check the transaction details with the help of other reports like
Cogs Revenue Matching report
Material Account Distribution Report

ADDITIONAL INFORM ATION

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=hapi6pbde_575&id=1565831.1 5/6
11/28/2017 Document 1565831.1
Following are the important Concurrent Requests:

Workflow Background Process request from Order Management (OM).

Create the Invoice with the Auto invoice request from Receivables(AR).
Record Order Management Transactions.
Collect Revenue Recognition Information.
Generate COGS Recognition
Cost Manager
Create Accounting AR and Cost Management

Few Important files which will ensure smooth functioning of COGS functionality. It is recommended to have the highest
available versions:

CSTRCMVB.pls
CSTRCMVS.pls
ARCGSRVB.pls

Other useful reports:

Cogs Revenue Matching Report

Material Account Distribution Report
Account Analysis Sub_ledger Detailed Report - 180 Characters
Trial Balance Report (DCOGS Account)

Summary

This analyzer should help to identify the various aspects of the Sales Order related transactions which causes DCOGS Balance.

Note:

For Release below 12.1.3, review file= dcogs_v1-R1206.sql

REFERENCES

NOTE:733275.1 - CSTPACIN.COST_INV_TXN:Failure in procedure CST_RevenueCogsMatch_PVT.Process_RmaReceipt()

NOTE:1307906.1 - COGS Dataflow and Diagnostics [Video]
BUG:13632989 - COGS DEFFERED ACCOUNT IS NOT RECOGNIZED FOR THE INTERCOMPANY TRANSACTIONS
BUG:20952706 - COGS RECOGNITION EVENT DOES NOT HAVE MATERIAL DISTRIBUTION
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=hapi6pbde_575&id=1565831.1 6/6