R12 SLA - Subledger Accounting Explained Part 1

Written by Puneet Vishnoi

Sunday, 22 June 2008 14:27

Please find first in the series of articles on R12 Subledger Accounting from Puneet Vishnoi.

Puneet is a freelance consultant in Europe. Prior to freelancing, he was one of the key
developers in Oracle Corporation for Oracle Projects Accounting and Oracle Grants
Applications.
Puneet has designed numerous critical solutions in Oracle Applications R12 and 11i. He has
vast experience in new R12 General Ledger Architecture. Puneet Vishnoi also happens to be
an excellent troubleshooter, resolving various business critical issues when he was in Oracle
Corporation.

This article is Part-1 of Subledger Accounting.

Why SLA and what does it do?

Oracle Sub Ledger accounting (SLA) is accounting hub in Oracle Application Release 12
(R12). It is used to derive all attributes required to account a transaction in Oracle General
Ledger. In R12, SLA is used to derive the very basic accounting attributes like entered amount,
accounted amount, Date, Currency code etc and the complex attributes like Ledger, Code
Combination ID, Periods etc. After deriving these accounting attributes the transactions are then
interfaced to GL from SLA. Thus in R12 no sub ledgers (AP, PO, PA etc) interfaces the
transactions directly to GL, but all the transactions are interfaced to GL in following 2 steps:
1. Sub ledgers interface the data to SLA.
2. SLA derives the accounting information and interfaces the data to GL.

SLA gives the flexibility to manage the entire accounting rule at one place, which acts as a
single source of truth for GL.

Note: There is no separate responsibility to access SLA setup or the view the transactions
generated by SLA. Rather we can access SLA setup and review accounted transactions with
extended menus attached to each sub ledger module.

Menu to access the SLA accounted transactions.

Menu to access the SLA Setup.

1/2
R12 SLA - Subledger Accounting Explained Part 1

Written by Puneet Vishnoi

Sunday, 22 June 2008 14:27

How
1.How
calls
as
While
(Will
Taking
run
Tieback
which
and
2. does
Register
provided
call
Payables
After
EVENT.
this
SLA
the API
by SLA
validating
calls
API
interfacing
id
will
the
‘PRC: sub
Events
SLA.
from
expenditure_item_id
unique
generated
registered
discuss
calling
event_id.
in
by SLA
in
process’.
between
registerto
example
expenditure_item_id
event
understand
In step does
class
1
Navigation: we
Responsibility:
Menu: Setup is /works?
this ledger
create
approving
concurrent
It
Interface
>SLA
this API
are
isof
itSubledger
to
SLA
discussed
used But
events
GL. up
in
and transactions
created
while
aThere
to
reference
Oracle
Cost
understand
better
Projects,to as R12
in the
/soon
sub
SLA program
user
costing
SLA
to
distinguish
we that
will
Vision by
sub
xla_events_pub_pkg.create_events,
thenext
This
SLA.
for step).
etc.
accounting.
event_id
OnceAsUnique
event
willcreates
ascalling
ID
then
is
Projects
is
ledger
General
no
and
usesonly the
canin
ledgers
of “PRC:
the
tieback
whether
while
go thru SLA.
transaction
the
validated
accounting
thereafter
tables.
same
between
creating
Services
Accounting the
> in
need on
successfully
act
sub
be
Ledger’
11i Generate
aspublic
an how
ledger
ainvoice
process
to
where
unique
table
seeded
the
the
(USA) run
SLA to
API
transaction
followed
to
types
Accounting id
event in
reference
oracle
created
“PRC:for
call
after
in
will
store
is
oracleof
we Cost
the
“xla_events_pub_pkg.create_events”
generates
id
R12, the
the
takerespective
toAccounting
passes
or
in
costing
by aInvoice.
Generate
invoice
all as API.
SLA,
allinthe
‘Journal
transaction
Methods care
the
information.
also there
id
need SLA.
the
Builder For
of
or module,
po_distribution
event Cost example
This
aidentifier?
means
unique Events”
accounting
in SLA,
that
atransaction
accounting
Import’
is
passed
to one reference
idfor
andthe
SLA
id
Accounting
to Oracle
and
sub
>entries
or
event
followed
oneuser
the
po_distribution
>pass event
Events Oracle
ledger
is
returnsProjects
referenceknown
transaction
an class
transaction
by
Events”
need
processing.
class.
Event id‘PRC:
This is
toof
or
To
Modal an

This
SLA.
the
directly
3.
a.
b.
c.
d.
e. projects
screen
Because
Based
XDODTEXE.
differentinterfaced
Identifiers
is
Identifier
columns
SOURCE_ID_CHAR_1
passing
interfaced
Event
Supplier
Oracle
executable
After
Gather
Derive
Create that
on shows
related
window
Class
Types.arethe
the
registering the
concurrent
for
does
This GL,
XLA_TRANSACTION_ENTITIES.to
above
the
transactions.
GL
that’s
hierarchical
expenditure_Item_id
Projects
Cost
to can
the
window
GL.
In
etc. tells
be
incan
PA unique
This used
what
Further
we
identifiers
example
the
information
the
code from
to
executable
accounting
journal
lines program
from
combination
lines screen
IDwhy
are
4base
interfaces
displays
level
havewe
following:
event
in of PA
column
these
that weshot
but
In
different
the
could itstructure
do
hierarchy
andonly
Projects
in names.
SLA,
is
attributes
based
XLA_AE_HEADERS id the
they
isnot
SOURCE_ID_INT_1
for
is values
entity
passed
in SLA
different
eventthese entity
from
classify
provided
we
tables
based
on thebased event
is is
Around
on can
used
in
seeded
and are
2see
kindof
known
class,
by Oracle
screen
routed
Invoice
different
‘EXPENDITURE’.
and
table
to SLA
columns
should
transactions
Supplier
types
create
sub
on
the SLA
with
160of
howas Projects
from
tothru
we as
4,
expenditure
like
name Event
Cost
SLA transactions
see
are
Labor
concurrent
and
accounting
ledgers.
the data
business
Journal
XLA_AE_LINES. is one
AR.
store
sub
from
as only
responsibility
of
class,
“PRC:
used
fetched
rules.
definition. Cost,the
those
SOURCE_ID_DATE_1
present
“Identifier
ledgers.
Expense
AP.
creates entity
that
transactions
which
programs
entries
by Misc
Create
fromall the
subby transactions
can
Report
is as
expenditure_item_id.
inPer
Column”
table
the
Cost,
accounting thus
Invoices
be
further
that
Accounting”.
are
sub
running
uses itexecutable
Usage
and
can interfaced
screenshot
field
to
lines?
ledgers
ledgers. shows
4, that
The are
under
classified
the Invoices
beCost,
This
with
same only
can
not
to
asbe
identifier
Oracle
into

2/2