RMA COGS.pdf

Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 1


Future Advisor Webcasts

Day, Date, 2004 time p.m. ET Teleconference Access: North America: xxxx International: xxxx Password: Advisor

Upcoming live webcasts and recent recordings.. VOICE STREAMING ENABLED Teleconference Access: US & Canada: (866) 627-3315 Toll Number: +1-706-758-7972 Global Toll-Free: 1148600.1 Password: Oracle CST VCP Webcast Calendar/Archive Doc ID 837233.1 Oracle Webcast Schedule/Archive Doc Id: 740966.1

What Cost Management advisor webcast topics do YOU want to see presented in 2013? Click here to let us know.

Presenter

Presentation Notes

AW template - silent preview slide (15min before)

https://communities.oracle.com/portal/server.pt/community/view_discussion_topic/216?threadid=512649�

<Insert Picture Here>

COGS Accounting from RMA Perspective Ramya Balasubramanian, Software Engineer Devaraju Holenarasipur, Sr. Principal software Engineer


The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

Safe Harbor Statement

Presenter

Presentation Notes

AW template - silent preview slide (5 min before)

<Insert Picture Here>

COGS Accounting from RMA Perspective Ramya Balasubramanian, Software Engineer Devaraju Holenarasipur, Sr. Principal software Engineer

Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Confidential – Oracle Internal

6

AGENDA

• Presentation and Demo approximately 60 - 75 minutes

• Q&A Session maximum 15 minutes Web attendees can ask questions via Q&A panel Phone attendees can ask questions via Q&A panel or phone


7

Q&A panel

type your question here 1

Send your question

3

Who to ask? 2


8

your question pops-up here


9

ATTENTION – AUDIO INFORMATION

Voice streaming/Audio broadcast is available. For full audio access, please join the telephone conference.

Teleconference Connect details:

1. Conference ID: 2. International dial in: +44 (0) 1452 562 665 3. List with national toll free numbers is available in Note 1354453.1

Note: You can view this info anytime using WebEx menu from your WebEx-Session : Select ‘Communicate’ --> ‘Join Teleconference’.


10

Program Agenda

Introduction to Revenue COGS matching

COGS Dataflow

RMA – Setup & Flow

Various RMA Scenarios and their Accounting Entries

Summary Of RMA Accounting

Troubleshooting - Revenue COGS Diagnostics

Not a bug Scenario

Recommended Patches

Q & A

Presenter

Presentation Notes

Here is the agenda for today’s session.


11

Introduction to Revenue COGS Matching

COGS should be recognized only when the revenue is actually earned. Till the time the revenue is earned, COGS is deferred.

The Basic Principal is that COGS and Revenue should be recognized

in the same Period and in the same Ratio At any given point in time, the ratio of deferred COGS to COGS should

be same as the ratio of deferred Revenue to Revenue.


12

Deferred COGS DATA flow

SO Header

SO Line

Pick Release

Invoicing & Rev. Recognition

Ship Confirm

R.O.M.T

C.R.R.I

G.C.R.E

OE_ORDER_HEADERS_ALL

CST_COGS_EVENTS & CST_REVENUE_COGS_MATCH_LINES

MTL_MATERIAL_TRANSACTIONS

WSH_DELIVERY_DETAILS &

MTL_MATERIAL_TRANSACTIONS

OE_ORDER_LINES_ALL

CST_COGS_EVENTS & MTL_MATERIAL_TRANSACTIONS

CST_REVENUE_RECOGNITION_LINES

RA_CUSTOMER_TRX_ALL,

RA_CUSTOMER_TRX_LINES_ALL & RA_CUST_TRX_LINE_GL_DIST_ALL

Presenter

Presentation Notes

This diagram shows the dataflow and the tables impacted from OM, AR and Cost management during the rev and cogs recognition process. R.O.M.T = Record Order Management Transactions C.R.R.I = Collect Revenue Recognition Information This Program is implemented by AR. G.C.R.E = Generate Cogs Recognition Events This program creates COGS recognition events by comparing the percentage in CRRL to the percentage in CST_COGS_EVENTS (CCE) for each period using CST_REVENUE_COGS_MATCH_LINES (CRCML) to match the shipment lines to the invoice lines. Creates COGS Recognition events (accounting only transactions) in material transactions table (MMT), which will actually transfer the amount from DCOGS to COGS account. Incase of RMA, events will be created against original Sales Order Line.


13

Understanding Return Material Authorization

Process Flow for Return Material Authorization.

Presenter

Presentation Notes

An RMA is an approval from the supplier for the customer to return inventory for credit, replacement, or repair. The system creates an authorization number for the supplier to track the return of the inventory. There are several flows available in the RMA flow. For e.g. you can accept the return and process a credit for the customer. You can accept the return for replacement, and enter a replacement order instead of issuing a credit.


14

Setup required for RMA flow 1. Item Setup

2 Transaction type – Return flow

Presenter

Presentation Notes

Define the item in the item master organization that need to be active… Inventory Tab Ensure the inventory item, stockable and transactable flags are enabled. Order Management tab Ensure, Customer Ordered, Customer Orders Enabled, OE Transactable and returnable flags are enabled. Invoicing Tab Ensure Invoiceable Item and Invoice Enabled flags are enabled. Assign the item to the receiving organization.


15

Case -1- Referenced RMA

Order Book SO Issue Rev Rec Cogs Rec RMA

(Referenced)

Oe_order_lines_all


16

Case – 1 – Referenced RMA Mtl_Material_Transactions

Mtl_Transaction_accounts


17

Case – 1 – Referenced RMA

17

If the SO Issue and RMA happens on the same day, following accounting entries are created.

Debit Credit SO ISSUE DCOGS INV COGS Rec COGS DCOGS RMA INV DCOGS DOGS COGS If the SO Issue and RMA happens on different day, only one accounting entry is created. Debit Credit RMA INV COGS Reference:- ER14559549 - COGS ACCOUNT GENERATED DIFFERENTLY BASED ON COGS EVENT DATE


18

Case -2- Un Referenced RMA

Order Book SO Issue Rev Rec Cogs Rec RMA (Un

Referenced)

Oe_order_lines_all – Sales Order issue


19


Oe_order_lines_all – Unreferenced RMA


20


Mtl_Material_Transactions – SOI & Cogs Recognition

Mtl_Transaction_Accounts – SOI & Cogs Recognition


21


Mtl_Material_Transactions – RMA Receipt

Mtl_Transaction_Accounts – RMA Receipt


22


22

In case of Un Referenced RMA, RMA accounting hits only COGS account Debit Credit

SO ISSUE DCOGS INV COGS COGS DCOGS RMA INV COGS

Queries: SQL> select reference_line_id "om_line_id“ from oe_order_lines_all where line_id=&rma_line_id; SQL> select trx_source_line_id “rma_line_id“ from mtl_material_transactions where transaction_id=&transaction_id; /* Use RMA Receipt */


23

Case -3- SOI and RMA Qty same

SO Issue Quantity =1 and RMA Quantity=1

Debit Credit Sales Order Issue DCOGS Inventory RMA INV DCOGS

Order Book SO Issue Rev Rec RMA

(Referenced) COGS Rec


24



25


There will be a COGS transaction line in MMT for 0 Quantity. Hence there will not be any Distributions created in MTA.


26


26

CST_COGS_EVENTS


27

Case – 4- Referenced RMA with Item cost Variation

In Standard Costing Organization Item cost at the time of sales order issue is 10 and Item cost at

the time of RMA is 12. Debit Credit Sales Order Issue DCOGS(1 Qty) Inventory(1 Qty @ $10) COGS recognition COGS (1 Qty) DCOGS (1 Qty @$10) RMA INV(1Qty@ $12 ) DCOGS (1Qty @ $10) DCOGS(1 Qty) COGS (1Qty @ $10)

Order Book SO Issue Rev Rec COGS Rec RMA

(Referenced)


28

Case – 4- Referenced RMA with Item cost Variation Mtl_Material_Transactions – @Sales Order Issue

Mtl_Material_Transactions @ RMA


29


Mtl_Transaction_accounts


30


In Case of Average costing, FIFO, LIFO, the Sales Order Issue is hit at the current Average cost. RMA cost will be decided based on whether it is referenced or unreferenced

Eg. Current avg cost as on 11-JAN - $10, Then SO ISSUE - $10 Current avg cost as on 15-JAN - $15 If a Referenced RMA is done on 15-JAN – Treated as Cost Owned Transaction- $10 If an Unreferenced RMA is done on 15-JAN- Treated as Cost Derived transaction - $15

30


31

Case – 5- SO Issue and Partial RMA

Sales order = 3Qty (spilt into 2 and 1). RMA for 1 qty. Debit Credit Sales Order Issue DCOGS(3 qty) Inventory(3 qty) RMA INV (1qty) DCOGS (1qty) COGS recognition COGS (2 qty) DCOGS (2 qty)

Order Book SO Issue Rev Rec RMA

(Referenced) COGS Rec

Presenter

Presentation Notes

In this flow, you split the detail line into 2 and 1 qty during the ship confirmation process. These are the accounting entries created for this flow.


32

Case – 5- SOI and Partial RMA Mtl_Material_transactions

Mtl_transaction_accounts

SOI is for 3 qty, RMA for 1 Qty and COGS Recog done for 2 Qty (3-1)

Presenter

Presentation Notes

Cogs Quantity Calculation:- SO Issue is done for 2 qty and 1 qty Cogs dr. 2 Qty and Dcogs cr. 2 qty. [3 qty(SO) -1qty (RMA)= 2qty]


33

Case-6- Ship Only Order Type and RMA

Ship Only Item attributes for OM and Invoicing:

Order Book(Ship

Only ) SO Issue COGS Rec RMA

(Referenced)

Presenter

Presentation Notes

For such items, Under order management tab, the shippable falg is enabled Under invoicing tab, the invoiceable and invoice enabled flag is disabled


34

Case-6- Ship Only Order Type and RMA In the order line choose the item type as ship only


35

Case-6- Ship Only Order Type and RMA

Transaction details

Presenter

Presentation Notes

This is how the transaction is seen from the UI. SO ISSUE is done for 1 qty, followed by COGS recognition of 1 qty and finally RMA receipt is done for 1 qty


36

Case-6- Ship Only Order Type and RMA SO ISSUE:

COGS Recognition:

RMA:

Reversal Entries:

Presenter

Presentation Notes

These are the accounting entries During SO ISSUE, DCOGS a/c gets debited and INV acct gets credited. On COGS recognition, COGS gets debited and DCOGS gets credited During RMA transaction, you have INV getting debited and DCOGS gets credited. Also there will be a reversal entries generated DCOGS gets debited and cogs gets credited.


37

Case-6- Ship Only Order Type and RMA Debit Credit Sales Order Issue DCOGS Inventory COGS recognition COGS DCOGS RMA INV DCOGS DCOGS COGS In case of Ship Only Orders, once the line is closed, it insert a line in CRRL table with Potentially_unmatched_flag as ‘U’. Once the Generate COGS rec program is run Potentially_unmatched_flag becomes ‘NULL’ and COGS trx is created in MMT and CCE tables.

Presenter

Presentation Notes

In case of Ship Only Orders, once the line is closed, it insert a line in CRRL table with Potentially_unmatched_flag as ‘U’. Once the Generate COGS rec program is run Potentially_unmatched_flag becomes ‘NULL’ and COGS trx created in MMT and CCE tables.


38

Case 7 – Referenced RMA in ATO flow(100% Rev Rec)

Create Config Item

Create Final

Assembly Ship

Confirm Revenue

Rec Cogs Rec

RMA Receipt

(Ref)

ATO (Parent Assembly)

Optional Class1 Optional Class 2

Item1 Item 2 Item 3 Item 4

Presenter

Presentation Notes

This is the typical ATO Flow. You can create a configuration item by choosing the option items from the available option classes. You can open a work order and once the work order is complete you have the configuration item available for shipping.


39


Order Line Details(OE_ORDER_LINES_ALL):

Presenter

Presentation Notes

These are the line detail from OE_ORDER_LINES_ALL table. The first line shows the MODEL line, the second line shows the configuration item. This is the item that gets shipped to the customer. The line 2.1 shows the return line . Basically when the customer return, you receive the shipped configuration item back from the customers.


40


Note: COGS recognition and RMA transactions are created across periods.

Mtl_Material_Transactions

Presenter

Presentation Notes

The MMT table shows the SO issue transaction is done for 1 qty. Please note the COGS recognition and RMA receipt is done across periods.


41

Case 7 – Referenced RMA in ATO flow(100% Rev Rec) Sales Order Issue: Transaction Type Debit Credit Sales Order Issue DCOGS Inventory

Presenter

Presentation Notes

During the SO ISSUE transaction, DCOGS gets debited and INV valuation account gets credited. Here you see many lines, because of the various cost elements defined for the item.


42


COGS Recognition:

Transaction Type Debit Credit Cogs Recognition COGS DCOGS

Presenter

Presentation Notes

During the COGS recognition, COGS account gets debited and DCOGS gets credited.


43


RMA Receipt:

Transaction Type Debit Credit RMA Receipt INV COGS

Presenter

Presentation Notes

During the RMA receipt, INV valuation account gets debited and COGS account gets credited.


44

Case 7 – Referenced RMA in ATO flow(100% Rev Rec) Summary of Accounting Entries: Transaction Type Debit Credit Sales Order Issue(period 1) DCOGS Inventory COGS recognition(period 1) COGS DCOGS RMA (period 2) INV COGS Note: The accounting entries are created in the same way irrespective of the item type.

Cst_Cogs_Events

Event Type Description 1 Sales Order Issue

2 RMA

3 COGS recognition

6 RMA Place holder

Presenter

Presentation Notes

These are the typical entries in cst_cogs_events table. These are the event_type_id’s which are created in CCE table. Please note at the code level, there is no difference in the way accounting entries are created for ATO item type.


45

Case 8 - Referenced RMA in ATO flow(50% Rev rec)

Setups to perform 50% rev recognition: Account Receivables(N)-> Setup-> Transactions-> Accounting Rules Define accounting rule for 50% deferral.

Config ATO Item

Ship Confirm

50% Rev Rec Cogs Rec

RMA Receipt

(Ref)

Presenter

Presentation Notes

This is the variation of the previous ATO flow. The revenue recognition is done for 50%. Typically this is the setup done to create 50% revenue recognition. Here we have defined an Accounting rule for 50%. The schedule is created across 2 periods at 50 percent. Please note the deferred revenue flag is enabled.


46

Case 8 - Referenced RMA in ATO flow(50% Rev rec) Order Management Super User(N)-> Setup-> Transaction Types In the line type workflow, under finance tab, choose the above

accounting rule

Presenter

Presentation Notes

The accounting rule needs to be linked to the transaction type that is defined for the standard order line type.


47

Case 8 - Referenced RMA in ATO flow(50% Rev rec)

Summary of Accounting Entries:

Debit Credit Sales Order Issue DCOGS Inventory COGS recognition COGS (50%) DCOGS (50%) RMA INV (50%) DCOGS (50%) COGS (50%)

Presenter

Presentation Notes

These are the accounting entries generated. The revenue recognition is done for 50%, hence cogs recognition is created for 50%. The RMA receipt shows the inv is debited and COGS gets credited. Also you see the DCOGS ac still remains as credited at 50%


48

Case 9 – SO ISSUE and RMA across periods

Sales Order issue and RMA Line Details

Oe_Order_lines_all

Order Book SO ISSUE Rev Rec Cogs Rec

RMA Receipt (Referenced)


49

Case 9 – SO ISSUE and RMA across periods Mtl_Material_Transactions

Note:- 1.Sales order issue for 3 Quantities created on 31-Dec-2012 . 2.Ran Revenue Recognition on 31-Dec-2012. 3.RMA Receipt for 1 Quantity created on 02-Jan-2013. 4.Ran Collect Revenue recognition and Generate cogs on 03-Jan-2013.


50

Case 9 – SO ISSUE and RMA across periods Cst_Cogs_Events

Cst_Revenue_Recognition_lines


51

Case 9 – SO ISSUE and RMA across periods

Mtl_Transaction_Accounts

Reference:- ER 12548020


52

Case 9 – SO ISSUE and RMA across periods Summary of Accounting Entries: Debit Credit Sales Order Issue DCOGS ( 3 Qty) Inventory ( 3 Qty) RMA INV ( 1 Qty) DCOGS ( 1 Qty) COGS recognition COGS (3 Qty) DCOGS (3 Qty) DCOGS (3 Qty) COGS (3 Qty)


53

Summary of RMA Accounting Case 1: Referenced RMA (SOI-> Rev Rec-> COGS rec-> Ref RMA)

Transaction Type (Done on the same Day)

Debit Credit

SO ISSUE DCOGS INV

COGS Rec COGS DCOGS

RMA INV DCOGS

DCOGS COGS

Transaction Type (Done on a different day)

Debit Credit

SO ISSUE DCOGS INV

COGS Rec COGS DCOGS

RMA INV COGS

Case 2: Unreferenced RMA (SOI-> Rev Rec-> COGS rec->Un Ref RMA)

Transaction Type Debit Credit SO ISSUE DCOGS INV

COGS Rec COGS DCOGS

RMA INV COGS

Case 3: SOI and RMA quantity are same. (SOI-> Rev Rec->Ref RMA-> COGS Rec)


RMA INV DCOGS

COGS Rec No Accounting No Accounting

Presenter

Presentation Notes

Oracle workflow architecture includes workflow development client,oracle database server,Application server and browser client. Development client: The development client is a Windows PC. This tier is used to create and modify Oracle Workflow process definitions, and to save and load flat files containing Oracle Workflow process definitions and XML definitions for Business Event System objects. Oracle Database The server tier is the Oracle Database that hosts the business application integrated with Oracle Workflow, the Workflow Engine, Business Event System, Notification System, and directory service. The Business Event System leverages the Advanced Queuing feature within the Oracle Database. Directory Services of Oracle Server maintains user and role information. Application Server The application server is the middle tier environment outside of the database. This environment includes ancillary services such as the Oracle HTTP Server as the Web server, and Oracle Workflow service components that run in the middle tier, such as agent listeners and notification mailers that generates email notifications in workflow. End-User Client The end-user client is the workstation or PC that an end user uses to perform daily tasks. This client includes browser support for accessing Oracle Workflow Web pages, as well as for accessing the Oracle Workflow Manager component. The end-user client also includes a mail client application for reviewing and responding to notifications by e-mail. It also includes workflow monitor which is a web page that enables users to monitor their workflow processes. The Notification System: Routes notifications to a role, which can be a single user or group of users Enables users to receive and respond to notifications using an e-mail application or Web browser of choice Sends e-mail notifications and processes e-mail responses using the JavaMail API Allows any users with access to the Internet to be included in a workflow process Provides access to the Worklist from Oracle E-Business Suite through the Worklist web pages Enables users to drill down from a notification in the Worklist web pages to any URL or Oracle E-Business Suite form to respond to the notification


54

Summary of RMA Accounting Case4: Referenced RMA with Item Cost Variation (SOI-> Rev Rec-> COGS rec-> Ref RMA) SO and RMA quantity: 1 Item Cost at the time of sales order is $10 Item Cost at the time of RMA is $12

Transaction Type Debit Credit

SO ISSUE DCOGS(1 Qty @ $10) INV (1 Qty @ $10)

COGS Rec COGS(1 Qty) DCOGS(1 Qty @ $10)

RMA INV (1 Qty @ $12) DCOGS(1 Qty @ $10)

DCOGS(1 Qty @ $10) COGS(1 Qty @ $10)

Case 5: SOI and Partial RMA (SOI-> Rev Rec-> Ref RMA-> COGS Rec) SOI for 3 Quantity and RMA for 1 Qty.

Transaction Type Debit Credit SO ISSUE DCOGS(3 Qty) INV(3 Qty) RMA INV(1 Qty) DCOGS(1 Qty) COGS Rec COGS(3-1 = 2 Qty) DCOGS(2 Qty)

Case 6: Ship Only Order Type and RMA (SOI -Ship Only-> Rev Rec-> COGS Rec-> Ref RMA)


COGS Rec COGS DCOGS

RMA INV DCOGS

DCOGS COGS

Case 7: Referenced RMA in ATO Flow(100% Rev Rec) (Create Config ATO Item->Book Order->Auto Create Assembly-> SOI-> Rev Rec -> Cogs Rec-> Ref RMA SOI and COGS in Period 1 RMA in Period 2


COGS Rec COGS DCOGS

RMA INV COGS

Presenter

Presentation Notes



55

Summary of RMA Accounting Case8:Referenced RMA in ATO Flow(50% Rev Rec) (Create Config ATO Item->Book Order->Auto Create Assembly-> SOI-> Rev Rec(50%) -> Cogs Rec-> Ref RMA

Transaction Type

Debit Credit

SO ISSUE DCOGS INV

COGS Rec COGS(50%) DCOGS

RMA INV DCOGS(50%) COGS(50%)

Case 9: SOI and RMA across periods (SOI -> Rev Rec->Ref RMA-> COGS Rec SOI for 3 quantity RMA for 1 quantity SOI in Period 1 and RMA & COGS in Period 2

Transaction Type

Debit Credit

SO ISSUE DOCGS(3 Qty) INV(3 Qty) RMA INV(1 Qty) DCOGS(1 Qty) COGS Rec

COGS( 3 Qty)

DCOGS(3 Qty)

DCOGS(3 Qty)

COGS(3 Qty)

Entries need to be for 1 Qty. - ER: 12548020

Presenter

Presentation Notes



56

Debugging COGS issues COGSDIAG.sql --------------------- Execute COGSDIAG.sql for any Sales Order you wish to troubleshoot

using 'Run Script' command (or) run individual queries as per requirement. The SQL returns rows for all tables related to COGS Recognition from

OM, AR, Inventory and Costing. View a Sample Output here - Sample Output Reference: MOS DOC ID: 1307906.1- COGS Dataflow and Diagnostics

Presenter

Presentation Notes

In order to debug COGS related issues, dev has provided COGSDIAG.sql. This is a collector script which gather detailed information on COGS and COGS Recognition transactions for a specific Sales order.


57

COGS Diagnostics – How to Interpret 1. Check the Creation date and Transaction Date 2. Check COGS_PERCENTAGE and PRIOR_COGS_PERCENTAGE columns in cst_cogs_events Table.

Transaction_Type Cogs_percentage Prior_cogs_percentage No COGS recognition

SO Issue 0 0 RMA 0 0 Full COGS Recognition

SO Issue 0 0 COGS Recognition 1 0 RMA 1 1 Partial COGS recognition - across Periods

SO Issue(Period 1) 0 0 COGS (Period 1) .25 0 COGS (Period 2) .50 0.25 RMA (Period 2) .50 .50

Presenter

Presentation Notes

Check the Creation date and Transaction Date of Sales Order Issue, Revenue Recognition, RMA Receipt and COGS transaction.


58

3. The Transaction_date in mtl_material_transactions table for COGS transaction depends on last_event_date in cst_revenue_recognition_lines(CRRL) table.

- When Collect Revenue Recognition Information program is run, inserts a line in CRRL table. This is populated by AR code.

- This is nothing but the Revenue Recognition date. This can be checked from ra_cust_trx_line_gl_dist_all table. Column name - GL_Date.

COGS Diagnostics – How to Interpret

Presenter

Presentation Notes

The transaction date in MMTfor COGS recognition depends upon the last_event_date in CRRL table. When you run the collect revenue recog information program, it inserts a record into CRRL table. This is nothing but the revenue recognition date and the same can be checked from RA_CUST_TRX_LINE_GL_DIST_ALL table’s GL_DATE column.


59

COGS Diagnostics – How to Interpret 4. SO_ISSUE_ACCOUNT_TYPE column in MMT decides whether DCOGS/COGS account to be hit.

– Above column is populated by inventory Code. – If its value is 2, then it indicates that the sales order issue is done in R12,

so DCOGS comes into picture. – If its value 1 then it indicates that the sales order issue is done in 11i. So

Cogs account is hit.

Reference:- Bug 13576673 - COGS RECOGNITION LINES NOT GENERATED AND DEFERRED COGS BALANCE IN GL INCREASES

Presenter

Presentation Notes

SO_ISSUE_ACCOUNT_TYPE column in MMT, decides whether DCOGS/COGS account is hit.


60

COGS Diagnostics – How to Interpret 5. Event Types:

Event Type Code Meaning

1 Sales Order Issue

2 RMA

3 COGS Recognition

4 COGS Recognition % Adj

5 COGS Recognition Qty Adj

6 RMA Place Holder

Presenter

Presentation Notes

The chart shows various event types defined in CST cogs events tables. For e.g. 1 means sales order Issue.


61

COGS Diagnostics – How to Interpret Event Type 6 and 2: Scenario1: SO ISSUE =10 qty RMA =3 qty Event Type 6 – Event qty is 10 Event Type 2 – Event qty as -3 COGS Rec for (10-3) =7 Scenario2: SO ISSUE =10 qty RMA =3 qty Event Type 6 – Event qty is 10 Event Type 2 – Event qty as -3 RMA for 4 qty Event Type 6 – Event qty is 7 (10-3) Event Type 2 – Event qty as - 4

Presenter

Presentation Notes

We shall explain Event type 6 and Event Type 2 with these examples. In the scenario, SO issue is done for 10qty, RMA for 3qty


62

COGS Diagnostics – How to Interpret Event Type 4-> COGS Rec % Adj (SO ISSUE-COGS-RMA) SO ISSUE is done, RMA is created with 0% COGS - This means the collect revenue and generate cogs programs are not run yet. - To correct the backdated cogs trx, adjustment event 4 is created. Event Type 5-> COGS Rec Qty Adj(SO ISSUE-RMA-REV and COGS) SO ISSUE is done in the month of Jan. Rev rec and cogs rec is done on Apr. In Feb RMA is created and it is stuck in MTI. In order to adjust this backdated RMA, event type 5 is created.

Presenter

Presentation Notes

Typically Event Type 4 happen when RMA is created with 0% COGS. This means the collect revenue and generate cogs programs are not run yet. To correct the back dated cogs transactions , adjustement event 4 is created. Event type generally happens during this type of scenarios..SO ISSUE is done In the month of JAN. Rev recog and COGS recog is done in the month of APR, In Feb RMA is created but for some reasons the transaction is stuck in MTI. In order to adjust such back dated RMA transactions, event type 5 is created.


63

Not a Bug

1.Distribution does not get created for Cogs Recognition: a. When the SO ISSUE qty and RMA Qty are equal and are in same or different period. [SO ISSUE > RMA > Cogs ] b. When the Item costs is "ZERO" In CRCML table, check the new_cost. It will be "Null". c. when both the cogs % and Prior Cogs % are same(0 or any value) in cst_cogs_events Table.

Presenter

Presentation Notes

These are some of the Not a bug scenarios. Firstly the distribution is not created for COGS recognition…This happens during these 3 scenarios.


64

Not a Bug 2.Manual AR invoices linked to SO are not considered for COGS recog: Only invoices created through Auto invoice program are getting considered for COGS recognition.

This is not a bug, the matching between AR invoice and Sales Order

shipment is controlled by OM, if the AR invoice is not from OM, the link between AR and INV is not maintained.

Reference :- Bug 14823225 - MANUAL AR INVOICES LINKED TO SALES ORDER

ARE NOT CONSIDERED FOR COGS RECOGNITION

Presenter

Presentation Notes

Manual AR invoices linked to SO are not considered for COGS recog. Only invoices created through the auto invoice program are considered for COGS recognition.


65

Recommended Patches: Recommended to Apply the following Patches: R 12.0: CSTRCMVB.pls 120.37.12000000.51 - Patch 12779598:R12.BOM.A R 12.1.X: 14180892:R12.BOM.C - CSTRCMVB.pls 120.45.12010000.48

14656876:R12.BOM.C - CSTRCMVB.pls 120.45.12010000.64* Note:-

*Patch 14656876:R12.BOM.C has some issue with Dependencies. Hence, its recommended to first apply Patch 14180892:R12.BOM.C and then apply 14656876:R12.BOM.C inorder to upgrade CSTRCMVB.pls


66

References Oracle® Cost Management User's Guide Release 12.1 DOC ID1528307.1, COGS Accounting From RMA Perspective


67

• To ask a question on the phone line, select *1 on your phone.

• To ask a question online, use the Q&A area at the top.

• Your question will be read aloud in the order received.

• Question can also be asked on the My Oracle Support Communities

Presenter

Presentation Notes

We hope everyone found the presentation valueable. We’ll open our Q&A in just a moment, so please use the chat feature or phone line, at this time to let us know you have a question. _________ could you give instructions on how to ask a question from the phone lines. While we are pausing I want to remind you that this is recorded and you will be receiving the links for repay and download along with a PPT of the presentation. Lets see our first question.


68

Collaborate with a large network of your industry peers, support professionals, and Oracle experts to exchange information, ask questions & get answers. Find out how your peers are using Oracle technologies and services to better meet their support and business needs.

• Exchange Knowledge

• Resolve Issues

• Gain Expertise

Visit My Oracle Communities

Visit the My Oracle Support Community now!!

1. Log into My Oracle Support.

2. Select the Community tab.

3. Select the Enter Here button.

4. Select the Community Name link under the E-Business Suite section of the My Communities Menu on the left side of the window.

https://metalink.oracle.com/�


69

Cost Management Advisor Webcast Calendar (Doc ID 1167580.1)


70

Over five exciting days, trade ideas with more than 5,000 like-minded attendees, network with Oracle Corporation and more than 250 top third-party providers in the Exhibitor Showcase and choose from nearly 1,000 educational sessions to attend. COLLABORATE provides the best opportunity to explore how you can get the most out of your existing products and learn about others that you can integrate into your environment.

April 7-11, 2013 Denver, CO http://collaborate.oaug.org

Date/Time Session Session Details Track Sun. Apr. 7 2:30 pm - 3:30 pm 12975 Oracle E-Business: Take Control of Workflow with Workflow

Analyzer! Financial Modules

Sun. Apr. 7 3:45 pm - 4:45 pm 12978 EBS Upgrades: Save time and money on your upgrade from

11.5.10 to 12.1.3 Application Strategy and Services

Mon. Apr. 8 11:00 am - 12:00 pm

12969 Get Proactive: Best Practices for a Faster, Smoother Oracle E-Business Suite Period Close

Financial Modules

Mon. Apr. 8 5:00 pm - 6:00 pm 12976 EBS Meet the Experts: Bring your questions, we will have

experts, answers and resources to help you. Financial Modules

Tue. Apr. 9 2:00 pm - 3:00 pm 12973 EVERYTHING EBS PATCHING! Application Strategy

and Services

Wed. Apr. 10 8:15 am - 9:15 am 12974 Oracle E-Business: Oracle Payables: Have a smoother

accounting period close Oracle E-Business Suite

Wed. Apr. 10 3:00 pm - 4:00 pm 12972 432.1 Get Proactive: Finding answers faster through MOS and

communities. Financial Modules

Not an OAUG member? Register today at www.oaug.org

http://collaborate.oaug.org/�


71

THANK YOU


72

Are You Ready To Get Proactive?

Avoid the unexpected Don’t leave value on the table Lower overall organizational costs through preventative maintenance Reduce risks and maximize uptime Achieve resolution faster Streamline and simplify your daily operations Get even more through connection

Discover more about Get Proactive https://support.oracle.com/CSP/main/article?cmd=show

&type=ATT&id=1385165.1:DISCOVER

ACT Get Proactive Access proactive capabilities available for your products

by visiting the product pages at My Oracle Support; Article ID 432.1

Contact the Get Proactive team today for help getting started

[email protected]

Presenter

Presentation Notes

Script The Proactive Capabilities Portfolio is included in your Premier Support agreement. Exploring how to “Get Proactive” is important because you can lower your organization’s costs by preventing problems. Getting Proactive also reduces risks and maximizes uptime. When problems do occur, you can get faster resolutions. Avoiding problems is even faster. Proactive tools help you determine which patches you need and avoid conflicts. Upgrade advisors help you through the process step-by-step. Discussions in My Oracle Support Community let you hear what other customers say about patches and give you lessons learned from their experience that can help you avoid problems Oracle customers have reported value-added outcomes including up to 25% fewer problems, 40% faster problem resolution, and dramatically streamlined upgrades. To learn more, explore KM Note 432.1, you’ll discover more about the getting proactive, including product specific pages that link you to tools and capabilities. You can also search “Get Proactive” in My Oracle Support to view the product specific knowledge, tools, and communities. Avoid the unexpected, like unnecessary fire drills, by getting proactive. If you have Questions, contact the Proactive team via email: [email protected]

mailto:[email protected]?subject=Oracle Support: Get Proactive Inquiry�

Documents

RMA COGS.pdf