Beruflich Dokumente
Kultur Dokumente
North America:
(866) 627-3315
International:
+1-706-679-4880
Other Global Toll Free:
Doc ID: 1148600.1
2009 Oracle Corporation Proprietary and Confidential
Objectives
To provide an overview of OPM with SLA
To describe the basic flow and the processes involved
in OPM with SLA
To describe the basic troubleshooting information
used in OPM Financials with SLA
What is SLA
SLA, or Subledger Accounting, is an intermediate step
between subledger products and the Oracle General Ledger
Ledger
Payables
Subledger
Accounting
Receivables
Subledger
Accounting
OPM
Subledger
Accounting
General
General
Ledger
Ledger
Description
Account Derivation Rule
Line Type
SLA- Structure
Journal Line
Types (JLT)
INV, IVA
Account Derivation
Rules (ADR for INV
with Conditions)
Event Classes
and Event
Types
Journal Entry
Descriptions
Sources
Transaction Objects
Preprocessor
creates
accounting events
MAC processes
transactions
and creates journals
10
SOURCE
EVENT
SUBEVENT
Shipping
Shipping
(OMSO)
Order
Management
Internal Order
Shipments
Customer
Returns(RMA)
11
EVENT ENTITY
EVENT CLASSES
EVENT TYPES
Shipping
Shipping
Internal Order
Shipments
(OMSO)
Order
Management
Customer
Returns(RMA)
12
SLA Setup
13
Key Takeaways:
Do not modify seeded ADRs.
Create custom ADRs
Define custom ADRs for
rules such as AAC, AAP,
DCOGS depending on your
business needs
14
15
16
17
18
Discrete
All the seeded SLA entities
(SLAM,AAD,JLD,ADR) can be
used
SLA uses distributions created
Presence of Transaction
Distribution GL account as
rule Source
Familiarity of entering
accounting information for
entities
OPM
A custom SLA,AAD,JLD,ADR
is always needed
Seeded Source Transaction
account not of use since
Transaction account does not
get derived
All accounts need to be
specified in the Custom ADR
19
Calculate
Cost
OPM Accounting
Preprocessor
Prelim Cost
Update
Incorrect
journals?
Yes
Create Accounting
(Draft Mode)
Review Journal
Entries
Make
changes
No
Final inventory
close
Final Cost
Update
OPM Accounting
Preprocessor
Create Accounting
(Final Mode)
Export to GL
20
Basic Process
Calculate Cost
Cost Rollup, Actual Costing or Lot Costing
Cost Update
For standard and actual costing, this creates the cost records to be used by
the subledger
Create Accounting
Creates the Subledger Accounting records which are later on fed to the General Ledger
21
22
23
24
25
26
Create Accounting
Reads the data that was generated by the OPM Preprocessor
Applies the rules that were set up for the events
Creates records in Subledger Accounting tables:
XLA_AE_HEADERS: SLA table stores subledger journal entries. There
is a one-to-many relationship between accounting events and journal
entry headers.
XLA_AE_LINES:SLA table stores the subledger journal entry lines.
There is a one-to-many relationship between subledger journal entry
headers and subledger journal entry lines.
XLA_DISTRIBUTION_LINKS: SLA table stores the link between
transactions and Subledger journal entry lines.
27
28
30
31
Sample data
GMF_XLA_EXTRACT_HEADERS
GMF_XLA_EXTRACT_LINES
32
33
34
35
FND logfile
-- debug log for Accounting Program
-- Please refer to Doc ID 1213193.1 OPM Financials (GMF) Trouble
shooting Guide for details on how to obtain these
36
Notes of interest
OPM Oracle Process Manufacturing SLA Subledger Accounting Setup (Doc ID 822303.1)
What Transaction Types Are Supported/Read by the OPM Preprocessor?
(Doc ID 970043.1)
What Values Can Column OPM_COSTED_FLAG Contain? (Doc ID 1051052.1)
R12: OPM-SLA Is There a Script to Undo a Final Create Accounting Run
(Doc ID 1170426.1)
For OPM, Can Create Accounting Be Run Successfully Using The SLA Seed Data?
(Doc ID 602068.1)
OPM: A Case Study on Migration from MAC to SLA (Doc ID 1308953.1)
R12 SLA : How Can I Set Up to Use 'Item Category' Value to Derive Account Number?
(Doc ID 1078837.1)
-- contains sample custom source including sample code
37
Exchange Knowledge
Resolve Issues
Gain Expertise
2.
3.
4.
39
40
41
42
THANK YOU
43
Find and use the name of the form, report, or concurrent program whenever possible.
Doc Id 121916.1
2.
Use exact error strings and the name of the code to get the best search results. For
example, 'ORA-1400: mandatory (NOT NULL) column'.
3.
Refine your search results to fit the situation and narrow your results. On the right side
of the search results, you'll see a number of Refine Search options. Here you may
narrow the search results by Product Category, Task/Intent, Document Type, and
Updated (date range).
4.
Avoid entering full sentences with punctuation that describe your issue, and remove
unnecessary words and characters that may unintentionally restrict search results from
being returned. This includes words similar to "the", "and", and with" and symbols like
number(#), dashes(-), colons(:), semi-colons(;), etc.
5.
44
45
45