Академический Документы
Профессиональный Документы
Культура Документы
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
Upcoming Webcasts:
November 13, 2012: Analyzing Discrepancies in the Output of Period Close Reconciliation Report (Doc Id 1167580.1) December 11, 2012: Custom SLA Setup Of Cost Management Events (Doc Id 1167580.1)
For complete details on Cost Management Webcast Events, please see Note 1167580.1. For complete details on All Other upcoming Oracle Advisor Webcast Events, please Note 740966.1. Do you have any requests for future Cost Management Advisor Webcast Events? Please email your suggestions to bonnie.barstad@oracle.com, subject: Topics of Interest.
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
Inventory - SLA- Gl Reconciliation Diagnostics Presenters: Suhas Basidoni , Amrish Kothari Date: 10-Oct-2012
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
Inventory - SLA- Gl Reconciliation Diagnostics Presenters: Suhas Basidoni , Amrish Kothari Date: 10-Oct-2012
Inventory-SLA-GL Reconciliation Approach of InventorySLA-GL reconciliation for Discrete Manufacturing customers. This will be applicable for R12 customers using Standard and/or Average Costing. Suitable for Oracle seeded Account Derivation Rules (ADR). The scripts mentioned are not applicable for Periodic Costing System (PAC).
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
Approach to Inventory Reconciliation A. Transactions Costing. 1. All Material /WIP transactions should be costed. This is the primary step in the process of Inventory Period close and ultimately in Reconciliation. If there are any errors in the respective tables or Cost worker errors those need to be resolved. To check for these errors, diagnostics scripts are available, Please refer to the Note 603657.1. Period Close Pending Transactions Report also can be submitted for ascertaining the pending transactions.
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
2. Run Create Accounting-Cost Management program. After checking, all the transactions for the concerned Inventory period are costed, Create Accounting-Cost Management concurrent request should be run to transfer all the transactions to GL. This concurrent completed. request should get successfully
For request parameters and the explanations for each of the parameters also the scripts associated, please refer to the Note 755943.1
10
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
11
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
Once Create Accounting-Cost Management concurrent request is completed successfully, Inventory period should be closed. While closing the Inventory Period, a report will get triggered called as "Period Close Reconciliation Report". This report is used to create summarized transaction records. It displays the differences between accounted value and inventory in the Discrepancy column.
12
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
Pending Transactions
13
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
B. Periodic /Regular Checks Check the Backdated Transactions. Timely closing of Inventory period will prevent the backdated transactions which will have its impact on Inventory valuation at the sub-ledger level as well as in the Gl. This is the primary factor which creates a difference in Sub-ledger and Gl. Pl refer to the Note 361597.1 for more discussion on Backdated transactions.
16
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
There is mismatch in quantities in different sub-ledger tables like Mtl_material_transactions(MMT) and Mtl_On_Hand_Quantities(MOQ). This can also lead to sub-ledger level difference and discrepancy in Period close reconciliation report. For MMT-MOQ mismatch and the resolution thereof need to refer to the Note 279205.1 In average costing Environment, there can be MMTCQL mismatch, pl refer to the Note 378348.1 which provides txn.sql to identify MMT-CQL mismatch.
17
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
C. Sub-Ledger Accounting (SLA) Checks Cost Management SLA pre-check required to be carried
out at regular intervals.
Common Issues:
Data with Negative Ledger_id in GL tables. Multiple posting issues. In GL Deleted from SLA.
Please refer to the Note 883557.1 by Oracle SLA Team. This note explains diagnostics and Data fix to resolve the above mentioned issues.
18
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
19
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
20
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
Batch Drilldown
From GL, drilldown using Batch Name provided in the Create Accounting Run.
21
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
INV_SLA_RECON.Txt
This output will gather data from the Inventory tables like Mtl_Transaction_Accounts and Wip_Transaction_Accounts and SLA tables.
SLA_GL_RECON.txt
INV_SLA_RECON.TXT
23
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
2. Data Mismatch in GL and SLA (Data Exists in GL tables but not in SLA)
============================================================= Inventory organizations using Periodic Average costing will not transfer the data through Create accounting. Manual GL Adjustments within General Ledger not coming through SLA mode.
24
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
2. Transactions mismatch bottom up approach (Exists in WTA but not in SLA tables) ===============================================================
Create Accounting did not run or resulted in error
3. Transactions mismatch top down approach (Exists in SLA tables but not in MTA) ===============================================================
This could be the rarest case as base sub-ledgers like Inventory do not have the data whereas SLA has data
4. Transactions mismatch top down approach (Exists in SLA tables but not in WTA) ===============================================================
This could be the rarest case as base sub-ledgers like WIP do not have the data whereas SLA has data
25
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
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
26
Confidential Oracle Internal Copyright 2012, Oracle and/or its affiliates. All rights reserved.
26
Visit the My Oracle Support Community now!! 1. 2. 3. 4. Log into My Oracle Support. Select the Community tab. Select the Enter Here button. Select the Community Name link under the E-Business Suite section of the My Communities Menu on the left side of the window.
27
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
27
28
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
28
Avoid the unexpected Dont 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
29
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
29
THANK YOU
30
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
30
31
Copyright 2012, Oracle and/or its affiliates. All rights reserved. Confidential Oracle Internal
31