SLA DROP SHIP SALES ORDER ISSUE USES ORG PARM'S DEFERRED COGS ACCOUNT
Last updated on DECEMBER 01, 2017
Applies to:Oracle Cost Management - Version 12.0.4 and later
Information in this document applies to any platform.
How the Oraganization Parameter Deferred Cost Account is used for ALL Sales Order Issue transactions.
Need more details on on HOW, WHEN and WHAT uses the deferred COGS account for each of the respective transaction types.
Is it the OM: Default Account Generator workflow?
Is it the Cost Manager?
Is it the SLA?
Is it the CSTRCMCR3 Generate COGS Recognition Events program?
Which STANDARD SLA ADR caused the distribution to debit the deferred COGS account?
Even before running the SLA - Create Accounting, the material distribution already showed the deferred COGS account,
so is it the Cost Manager and the Cost Transaction Worker that uses the deferred COGS account debit
Sales Order Issue is transaction_type_id = 33, transaction_action_id = 1 and transaction_source_type_id =2. This is the transaction that transformed debit to deferred COGS instead of COGS.
ID 10008 is the COGS Recognition transaction.
So for SO Issue, ID=33, how does it change from COGS to DCOGS?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms