Beruflich Dokumente
Kultur Dokumente
Collect Revenue Recognition Information imports Revenue Recognition details from Receivables
module to Costing module.
COGS Accounting From RMA Perspective(How to interpret COGSDIAG.sql, Not To
a bug, Known Issues and Recommended Patches) (Doc ID 1528307.1) Bottom
Purpose
Scope Yes
Details No
1. Summary of RMA Accounting:
2. COGSDIAG.sql:
3. Standard Functionality: Document Details
Recently Viewed
SCOPE Why Are There Values in the Deferred COGS Account
After Running ''Generate COGS Recognition'' ?
[1566921.1]
This document is for functional and technical
users of Oracle Cost Management module who COGS Recognition Getting Delayed Beyond The Date
would want to understand the COGS dataflow When Revenue Recognition Are Run [1515832.1]
and its accounting entries related to various No COGS Recognition When RMA Receipt has same Date
as Shipment [1377080.1]
RMA scenarios.
R12 Is There Any Standard Reports To Identify How
DETAILS Much Revenue Recognized And/Or Deferred In AR
Invoices [1113667.1]
Show More
Note:-
Potentially_unmatched_flag becomes
NULL and COGS transaction created in
Mtl_material_transactions (MMT) and
Cst_cogs_events (CCE) tables.
2. COGSDIAG.sql:
How to Interpret:
C. The TRANSACTION_DATE in
MTL_MATERIAL_TRANSACTIONS table
for COGS transaction depends on the
LAST_EVENT_DATE in
CST_REVENUE_RECOGNITION_LINES
table.
D. The SO_ISSUE_ACCOUNT_TYPE
column in
MTL_MATERIAL_TRANSACTIONS table
decides whether DCOGS (Deferred Cost of
Goods Sold) or COGS (Cost of Goods Sold)
account is used.
Refer to:
E. Event Types:
3. Standard Functionality:
Reference :
With
the Patch.14374856:R12.ONT.B (Order
Management Patch), a new System Parameter
"Source Line for deriving COGS account
on referenced RMA is introduced.
Reference:
5. Recommended Patches:
R12.0:
Patch.12779598:R12.BOM.A CSTRCMVB.
pls 120.37.12000000.51
R12.1.X:
Patch.14180892:R12.BOM.C CSTRCMVB.
pls 120.45.12010000.48
Patch.14656876:R12.BOM.C CSTRCMVB.
pls 120.45.12010000.64
Important Note:-
Attachments
Cst_Revenue_Cogs_Match_Lines
Cst_Cogs_Events
Cst_Revenue_Recognition_Lines
Action:
Action:
In case of DOCGS balance exists for
any SO line, verify the data in COGS,
Extract headers, Lines if all the events
of the particular sales order line are
recognized.
Cross check if Balance nullified
grouping by Ref_order_number (In
case of generate COGS process ran
for SO and its RMA together, COGS
event will not be generated, but
original SO DCOGS entry itself will
be revered by RMA)
Run the programs listed in the
sequence of operations section in the
same order and re-verify the data.
If the balance still exists, raise a
service request with OPM finance
team along with the
OPMDOCGSData extract.
===========================
===========================
===========================
===========
===========================
===========================
===========================
===========
TABLES impacted
1:SO_ISSUE,
2:RMA_RECEIPT,
3:COGS_RECOGNITION_EVENT,
4:COGS_REC_PERCENT_ADJUST
MENT,
5:COGS_REC_QTY_ADJUSTMEN
T,
6:RMA_RECEIPT_PLACEHOLDER
,
----
Costing tables also used
cst_cogs_events
cst_revenue_cogs_match_lines
Goal
Solution
1. COGS Data Flow
2. Diagnostics
3. Video Recording for the COGS Workflow
References
Troubleshooting Steps
Goal
Solution
1. COGS Data flow
Note:
1. In the above and below flow, We have assumed that the Cost Manager has picked
up all uncosted Sales order issues and costed them (costed_flag in
mtl_material_transactions should be NULL).
2. If the Sales order issue transactions/ RMA Return transactions remain uncosted, then
The Record Order Management Transactions concurrent program can be executed,
which picks up these transactions and inserts rows in Cogs events and Cogs Revenue
Matching Tables to enable remaining programs (Collect Revenue Recognition
Information and Generate COGS Recognition) to complete.
This process is not mandatory if the transactions are already costed.
1.Cst_cogs_events.COGS_Percentage = '0'.
2. (i) Cst_cogs_events.Mmt_Transaction_id will be the Transaction Id in
Mtl_Material_Transactions Table for Sales Order Issue Transaction.
(ii) Cst_cogs_events.costed = Mtl_Material_Transactions.costed_flag will be NULL
when the sales order transaction is costed
3.Cst_cogs_events.Event Type = '1'[Event Type '1' signifies Sales Order Issue].
4. In cst_revenue_cogs_match_lines Table, Deferred_COGS_Acct_id and COGS_Acct_id,
Unit_cost and Original_shipped_Qty gets populated.
Note: Oe_order_lines_all.Invoice_Interface_Status_Code =
'Yes'.[Invoice_Interface_Status_Code 'Yes' signifies Standard Sales Order and
Invoice_Interface_Status_Code 'Not_Eligible' signifies Ship Only Lines].
1.Cst_revenue_recognition_lines.Potentially_unmatched_flag = 'Y'
2.Cst_revenue_recognition_lines.Revenue_recognition_percent = '1' [Revenue
Recognition percentage of 1 signifies 100%]
Accounting Impact:
Accounting Entries:-
Staging transactions:-
Inventory Account (Destination) is debited and Inventory Account (Source) is credited.
Accounting Entries:-
COGS Recognition:
COGS Account is Debited and DCOGS Account is Credited.
2. DIAGNOSTICS
COGS_Diagnose.sql
1. Execute COGS_Diagnose.sql for any Sales Order you wish to troubleshoot using 'Run
Script' command (or) run individual queries as per requirement.
2. The SQL returns rows for all tables related to COGS Recognition from OM, AR, Inventory
and Costing.
COGS Recognition
You can also download the below Zip files if you are not able to view the videos/ video
controls properly
- Sales_Order.zip
- Revenue_Recognition.zip COGS.zip