Sei sulla pagina 1di 79

Subledger Accounting

Why SLA?
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 ver! basic accounting
attributes li"e entered a#ount accounted a#ount $ate %urrenc! code etc and the
co#ple& attributes li"e Ledger %ode %o#bination I$ 'eriods etc. A(ter deriving
these accounting attributes the transactions are then inter(aced to GL (ro# SLA.
)hus in R12 no sub ledgers (A' 'O 'A etc) inter(aces the transactions directl! to
GL but all the transactions are inter(aced to GL in (ollo*ing 2 steps+
1. Sub ledgers inter(ace the data to SLA.
2. SLA derives the accounting in(or#ation and inter(aces the data to GL.
SLA gives the (le&ibilit! to #anage the entire accounting rule at one place *hich
acts as a single source o( truth (or GL.
Note: )here is no separate responsibilit! to access SLA setup or the vie* the
transactions generated b! SLA. Rather *e can access SLA setup and revie*
accounted transactions *ith e&tended #enus attached to each sub ledger #odule.
,enu to access the SLA accounted transactions
,enu to access the SLA Setup
what exactly does SLA do?
SLA is a #odule *hich no* sits bet*een the SubLedgers li"e A'-AR etc and the
General Ledger. .ave a loo" at this diagra# belo*. As !ou *ill notice SLA can
act as a #ediator bet*een the subledgers and Oracle General Ledger.
/e(ore *e progress so#e ter#inologies o( R12 #ust be revisited. In 11i *e had
set o( boo"s and in R12 *e call the# Ledgers. Li"e*ise in R12 *e also have
secondar! ledgers and reporting ledgers. .ence (ro# 11i perspective thin" o(
Ledger as Set o( /oo"s. As (or Subledger a Subledger is nothing but a #odule li"e
A'-AR-'O-Inventor! etc.
In the diagra# belo* the second scenario is e&plained *hereb! let0s sa! that
pa!ables #odule generates a charge account seg#ent co#bination (or an invoice
distribution line as A./.%.$. In such case i( SLA #odule is not custo#i1ed then
the ver! sa#e A./.%.$ co#bination *ill be passed to Oracle General Ledger via
the SLA. And be(ore !ou *onder... 2es SLA #odule has its o*n set o( tables to
capture these accounting entries.
'lease see the i#age belo*.
In the i#age above SLA passes to GL *hatever value is (ed b! the Subledger in
this case A./.%.$
)here are cases *here SLA #odule can alter or #assage the %%I$ or code
co#bination that is generated in Subledger be(ore trans(erring the sa#e to Oracle
General Leger. )his scenario is e&plained *hereb! let0s sa! that pa!ables #odule
generates a charge account seg#ent co#bination (or an invoice distribution line as
A./.%.$. In such case i( SLA #odule is custo#i1ed then the A./.%.$ code
co#bination o( 'a!ables can be passed to Oracle General Ledger via the SLA as
A./1.%1.$ instead.
)he #ost i#portant application ho*ever o( the SLA is its abilit! to create shado*
3ournals that contain di((erent values or di((ering credit-debit entries (or the
transactions. )his is the #ain reason *h! SLA #odule *as invented-designed. Let
us ta"e an e&a#ple. 4or co#pan! 5Apps24usion 675 it #ight have operations in
4rance *hich is 5Apps24usion 4rance5. 8ith 67 being the parent co#pan! the
4rench co#pan! has to do accounting 3ournals in (or#ats that can be reported as
per 4rench legislation and also as per 67 legislation. 4or e&a#ple in 4rance an
inventor! ite# is accounted as e&pense *hereas in 67 the inventor! ite# is
accounted as an asset. In the e&a#ple belo* A./.%.$ is never passed to the GL.
Instead to GL A./1.%1.$ is passed to the 'ri#ar! Ledger 4RA9%: and
A2./2.%.$ is passed to the Secondar! Ledger 67. )he picture belo* sho*s the
role that SLA pla!s in such scenario.
)here(ore in this article !ou have learnt the di((erent usages o( Subledger
accounting.
How does SLA works?
1. Register sub ledger transactions in SLA.
A(ter validating - approving - costing the transaction in the respective
#odule the sub ledger calls SLA A'I to create a re(erence o( the validated
transaction in SLA. )his re(erence is "no*n as :;:9). :vents are created
b! calling the public A'I <&la=events=pub=p"g.create=events> provided b!
SLA. It is up to the sub ledgers on ho* to call the A'I. 4or e&a#ple Oracle
'ro3ects call this A'I (ro# concurrent progra# <'R%+ Generate %ost
Accounting :vents> and Oracle 'a!ables calls this A'I *hile user creates
accounting (or the Invoice.
8hile calling &la=events=pub=p"g.create=events oracle passes a unique id
and event class (8ill discuss in ne&t step). 6nique I$ can be an invoice id or
a po=distribution id or an e&penditure=ite#=id etc. As soon as the sub ledger
generates event in SLA SLA returns unique event=id. )his event=id *ill
then act as a re(erence to all the accounting entries generated b! the SLA.
Once event is success(ull! created in SLA #eans that the transaction is
registered in SLA (or accounting.
)a"ing the e&a#ple o( Oracle 'ro3ects in 11i *here a(ter costing the
transaction user need to run the ?'R%+ Inter(ace %ost to General Ledger@
(ollo*ed b! ?Aournal I#port@ (ollo*ed b! ?'R%+ )iebac" process@. /ut in
R12 user onl! need to run <'R%+ Generate %ost Accounting :vents> *hich
*ill register events in SLA and therea(ter SLA *ill ta"e care o( accounting
the transaction and inter(acing it to GL. )here is no tiebac" process in R12
as there is one to one re(erence o( event id bet*een SLA and sub ledger
tables.
2. How does SLA understand whether uniue id is in!oice id or a
"o#distribution id or an ex"enditure#ite$#id as SLA uses sa$e table to
store all the identi%ier?

In step 1 *e discussed that *hile creating the event *e also need to pass
event class. )his event class is used to distinguish bet*een the t!pes o(
transaction passed (or processing. )o understand this better *e *ill go thru
the seeded oracle in(or#ation.
Na!igation:
Responsibilit!+ 'ro3ects ;ision Services (6SA)
,enu+ Setup B Subledger Accounting B Accounting ,ethods /uilder B
:vents B :vent ,odel

)his screen sho*s the hierarchical structure o( di((erent transactions that can
be inter(aced to SLA. /ecause the above screen shot is (ro# Oracle 'ro3ects
responsibilit! thus it sho*s onl! the pro3ects related transactions. In the
entit! screen *e see onl! those transactions that can be inter(aced to the GL
that@s *h! *e do not see Invoice as one o( the entit! as Invoices are not
directl! inter(aced to GL (ro# 'A but the! are routed thru AR.
Identi(iers are the unique I$ that is passed to SLA (ro# sub ledgers. 'er the
screenshot Oracle is passing e&penditure=Ite#=id (or entit!
?:C':9$I)6R:@. <Identi(ier %olu#n> (ield under Identi(ier *indo* tells
*hat colu#n in SLA table should store e&penditure=ite#=id. )he identi(ier
colu#ns that can be used are SO6R%:=I$=I9)=1 to D
SO6R%:=I$=$A):=1 to D SO6R%:=I$=%.AR=1 to D these values and
colu#ns are present in table CLA=)RA9SA%)IO9=:9)I)I:S.
:vent %lass *indo* displa!s the di((erent "ind o( e&penditure transactions
that can be inter(aced to GL. )his level o( hierarch! is "no*n as :vent class
*hich is (urther classi(ied into :vent )!pes. In 'A *e have di((erent event
t!pes li"e Labor %ost ,isc %ost 6sage %ost Supplier %ost etc. 4urther *e
could classi(! Supplier %ost as :&pense Report and Invoices as Oracle
'ro3ects can inter(aces onl! these 2 transactions (ro# A'.
&. 'ased on the identi%iers and e!ent class( how SLA creates accounting
lines?
A(ter registering the event in SLA *e can create accounting entries b!
running e&ecutable C$O$):C:. )his e&ecutable is provided b! SLA and
is used b! all the sub ledgers *ith di((erent concurrent progra# na#es.
Around 1EF concurrent progra#s are uses the sa#e e&ecutable (or e&a#ple
in 'ro3ects it is used *ith na#e <'R%+ %reate Accounting>. )his e&ecutable
does the (ollo*ing+
a. Gather in(or#ation (ro# base tables in sub ledgers.
b. $erive the accounting attributes based on the data (etched (ro# sub
ledgers.
c. $erive code co#bination id based on the business rules.
d. %reate 3ournal lines based on the seeded Aournal de(inition.
e. %reate lines in CLA=A:=.:A$:RS and CLA=A:=LI9:S.
)ntities * )!ent +lass * )!ent ,y"es
In this section !ou understand so#e o( the basics (abrics-ter#inolog! used in SLA
i.e. :ntities :vent %lasses and :vent )!pes. It is i#portant (or !ou to understand
the variables *ithin SLA engine *hich in(luence *hether an accounting entr!
needs to be generated (or a speci(ic event *ithin subledger li"e 'a!ables or
Receivables. 4or e&a#ple in 'rocure#ent there #a! be a need to generate
accounting *henever a 'urchase Order is encu#bered. In case o( SLA the activit!
o( 5:ncu#brance5 against a 'urchase Order is "no*n as :vent )!pe.
Li"e*ise *hen a 'a!ables Invoice is ;alidated then !ou #a! *ant to create an
accounting entr!. In this case the 5Invoice ;alidation5 is an 5:vent )!pe5. And
!our accounting rules (or Invoice ;alidation *ill be attached against this speci(ic
5:vent )!pe5.
4or 'a!ables an I9;OI%: transaction and a 'A2,:9) transactions are "no*n
as :ntities *ithin SLA.
:ntities can be subdivided into various 5:vent %lasses5 (or e&a#ple %redit ,e#o
$ebit ,e#o :&pense Reports Invoices etc. 4urther to this against the :vent
classes *e de(ine :vent )!pes (or e&a#ple *henever !our Invoice is validated or
cancelled or ad3usted !ou #a! *ant so#e speci(ic accounts in the General Ledger
to be i#pacted. :vent t!pes are there(ore the t!pes-list o( events against
transactions *hich !ou *ish to account (or in General Ledger.
)his is e&plained in the diagra# belo*.
:ach entit! is identi(ied b! unique identi(ier or pri#ar! "e! (ro# the underl!ing
tables.
-ournal Line .e%inition
)he Aournal Line $e(inition 5de(ines5 ho* the entire 3ournal is built. )o create an!
3ournal one o( the "e! things is to get the %%I$ or the code co#bination o(
seg#ents. SLA needs to "no* *here this %%I$ *ill be co#ing (ro#. 2ou also
need to "no* *hether this %%I$ *ill be debit or this %%I$ *ill go into credit.
)here(ore !ou not 3ust require the %%I$ but !ou also need to decide *hether a
speci(ic %%I$ *ill be debited or credited. In SLA the 5Aournal Line )!pe5 *ill
speci(! *hether the accounting entr! is credit or debit. Also !ou can then 5attach
so#ething called an A$R to this Aournal Line )!pe5. )he A$R returns the (inal
code co#bination. )here(ore Aournal Line t!pe *ill leverage the AL)GA$R to
"no* *hich %%I$ is crediting and *hich %%I$ is debiting in the 3ournal.
4or each and ever! application there is a co#bination o( event class and event
t!pe. $epending upon the co#bination o( event class and event t!pe the
accounting gets triggered. )he standard SLA out o( the bo& (ro# Oracle #eets
!our require#ent b! HFI. 4or e&a#ple !ou can (etch the standard accounting (ro#
pa!ables or receivables options. .o*ever *here these standard seeded accounting
do not su((ice !ou can go and #odi(! SLA to #eet !our business needs.
)here is so#ething called as Aournal :ntr! $escription. 8hen a transaction is
trans(erred as a 3ournal then ever! 3ournal has credit-debit and description. )he
3ournal has description at header and also at line level. )he A:$ allo*s !ou to
generate the description o( the Aournal at both header and line level. 4or e&a#ple
!ou #a! *ant %usto#er 9a#e or %usto#er 9u#ber in the 3ournal description (or
a 3ournal that is initiated (ro# Oracle Receivables #odule. 6sing A:$ in SLA !ou
can build header or line level descriptions.
)he i#age belo* describes the end result 3ournal that is produced b! SLA
In -L, Aournal Line )!pe !ou can speci(! *hether the entr! is (or credit or debit
side. )he Aournal Line )!pe also provides options to do accounting (or Gain-Loss
o( 4oreign currenc! transactions. 4urther to that !ou can speci(! i( SLA should
#erge the 3ournal lines that have sa#e %%I$.
A.R J 8e speci(! ho* the account co#bination #ust be generated. 8e tell the
s!ste# ho* *e *ant the %%I$ should be built and trans(erred to the general
ledger. 2ou can either trans(er the standard account as calculated *ithin
Subledger(A' or AR or 'A etc) or the account generated (ro# Subledger can be
#odi(ied or replaced via A$R con(iguration *ithin SLA.
4urther to this *hen de(ining A$R !ou can speci(! the conditions under *hich a
speci(ic seg#ent or %%I$ is returned. )hese conditions are li"e I4 %onditions.
It is good to re#e#ber that the 5Aournal Line $e(initionKA:$GAL)GA$R5
)his is visible (ro# the screenshot as sho*n belo*
2ou *ill notice that t*o 5Aournal Line )!pes5 have been attached to this Aournal
Line $e(inition. )he (irst 3ournal line t!pe assign#ent creates a credit line in the
3ournal and the second 3ournal line t!pe assign#ent creates a debit line in the
3ournal.
/! no* !ou *ould have understood the signi(icance o( Aournal Line $e(inition.
.o*ever !ou #ight be *ondering ho* this Aournal Line $e(inition gets associated
*ith a Subledger transaction. 4or e&a#ple ho* does Oracle :J/usiness Suite
decide *hich speci(ic Aournal Line $e(inition should be used *hen a speci(ic event
ta"es place against an invoice in Oracle 'a!ables. In other *ords ho* *ill SLA
decide ho* the Aournal *ill be constructed *hen an invoice is validated *ithin
'a!ables. 8e *ill learn this via AA$ in ne&t part o( the article using Application
Accounting $e(initions.
As *e have seen in the 'art D o( SLA the Application Accounting de(inition is
used to decide t*o things
a. 8hen a speci(ic event *ithin Subledger e&a#ple 'a!ables or Receivables
beco#es eligible (or Accounting
b. .o* the 3ournal is constructed.
.o*ever each 'ri#ar! Ledger L11i equivalent o( pri#ar! set o( boo"M and also
each secondar! ledger should be able to generate Aournals as per their respective
legislator require#ents (or all the #odules i#ple#ented. )his is *here 5Subledger
Accounting ,ethod5 LSLA/M co#es into the pla!. I( !ou recollect (ro# previous
article Application Accounting $e(inition is connected to onl! one #odule li"e
'a!ables or Receivables etc. .o*ever a LedgerL11i SO/ equivalentM needs
accounting entries to be processed across #an! #odules. .ence SLA, provides
an u#brella to 3oin accounting entries (ro# various #odules so that the! can be
channelled through to Oracle General Ledger. In other *ords a SLA, is a
collection o( accounting de(initions (or various #odules in Oracle Apps. A SLA,
is then attached to the LedgerL11i equivalent o( Set O( /oo"sM.
)here(ore the (lo* o( accounting entries appears as sho*n belo*
)he (lo* represented in si#ple equation appears as belo*
Ledger $e(ined in GLJJBSLA,JJBAA$JJB L:vent %lass and :vent )!peMJJ
BLiabilit! LinesJJBLA:$GAL)GA$RM
Ledger $e(ined in GLJJBSLA,JJBAA$JJB L:vent %lass and :vent )!peMJJ
B:&pense LinesJJBLA:$GAL)GA$RM
In order to assign the SLA, to a ledger go to the General Ledger Super 6ser
responsibilit! and clic" on #enu as sho*n belo*.
%lic" on update against the ledger
Attach the SLA, to this ledger
2ou can also #odi(! the SLA accounting options using the t*o screenshots as
sho*n belo*
0!erall SLA .iagra$
)he overall (lo* o( the SLA can there(ore be depicted as sho*n in i#age belo*.
Overall *hen !ou create ne* de(initions in SLA !ou can (ollo* the botto# up
#odel. )he parallel (lo* on top as sho*n in i#age belo* is to ensure both a
%redit and $ebit line gets created (or a Aournal.
+reating -ournal Line .e%inition
In this section *e *ill create a Aournal Line $e(inition. 2ou *ill basicall! appl!
the steps learnt thus (ar into practical i#ple#entation.
.o*ever to create a Aournal Line $e(inition *e need to create the (ollo*ing
1. Aournal :ntr! $escription (or 3ournal line description
2. Aournal Line )!pe to #ainl! de(ine credit or debit
N. Account $erivation Rules (or %%I$ used in 3ournal line
)here(ore t!picall! t*o set o( A:$AL) and A$R@s are required *ith one set each
(or %redit line and the other set (or the debit line.
In this article *e *ill create these three co#ponents.
Go to a subledger li"e 'a!ables and *ithin the SLA #enu as sho*n belo* !ou
can open the Aournal :nt! $escription screen. %lic" on 9e* to create a ne* A:$.
%reate a ne* Aournal :ntr! $escription na#ed A9IL=A:$. 8e *ill use this (or
generating the Aournal Line $escription (or both the credit and the debit lines.
)he 3ournal line description can be constructed b! clic"ing on $etails button. )he
description o( the 3ournal line can be a static te&t or d!na#ic te&t based on
database sources *ithin SLA or the co#bination o( the t*o.
.ere *e are using the Supplier 9a#e to construct the 3ournal line description.
In addition to the d!na#ic 3ournal line te&t SLA allo*s !ou to put conditions.
4or e&a#ple I4 %O9$I)IO91K)R6: then Aournal Line $escription should be
abcd :LS: I4 %O9$I)IO92K)R6: then Aournal Line $escription should be
de(g. %lic" on condition button to de(ine the condition
A(ter de(ining the Aournal :ntr! description no* *e can create Aournal Line )!pe
na#ed A9IL=AL)=%R:$I) (or the credit line o( the 3ournal.
Speci(! the )rans(er to GL in Su##ar! or $etail #ode. Also speci(! ,erge as
e&plain in i#age belo*
6se the 'a!ables setup option as source to build condition (or AL)
In this e&a#ple *e *ant to build a condition (or <Aournal Line )!pe> eligibilit!
depending upon *hether in the 'a!ables Options Screen has Auto#atic O((set
,ethod is set to 9one or /alancing or Account. In the above condition *e have
placed an OR condition.
2ou can (or e&a#ple also build a condition based on Invoice $istribution t!pe as
sho*n belo*.
9e&t *e need to de(ine the Account $erivation Rule
.ere *e are creating an account derivation rule (or the credit line.
An A$R can either return a (ull %%I$ or a speci(ic seg#ent. )he values can be
sourced either staticall! or (ro# e&isting seeded d!na#ic sources in SLA. )hese
seeded sources are #apped to database tables.
8e are stating that this speci(ic A$R na#ed A9IL=LIA/ILI)2=A$R *ill return
a constant value in co#pan! seg#ent
In the above i#age !ou *ill see that the value (or %o#pan! seg#ent can be
derived (ro# the corresponding value set.
As belo* it is also possible (or the speci(ic A$R to return a (ull seg#ent
co#bination. In (act !ou can speci(! conditions *ithin an A$R. 8hen
%O9$I)IO91K)R6: then seg#ent co#bonation a.b.c.d is returned or *hen
%O9$I)IO92K)R6: then d.e.(.g co#bination is returned (or !our account.
4or the debit side *e are sa!ing that the Account seg#ent #ust al*a!s be ODPF
)he conditions can be de(ined. /ut conditions as evaluated as per the priorit!.
4inall! *e create a Aournal Line $e(inition.
.ere ever!thing hangs together AL)AL$A$RKAournal Line $e(nition
As sho*n belo* *e are sa!ing that the %%I$ (or the %redit Line o( the 3ournal
*ill be calculated (ro# A9IL=LIA/ILI)2=A$R
And the %%I$ (or the debit line *ill be calculated b! the %%I$ value in Invoice
$istribution line *ith the speci(ic seg#ent (ro# Account seg#ent being replaced
as per A9IL=:C':9S:=A$R.
4or e&a#ple i( the %%I$ in A'=I9;OI%:=$IS)RI/6)IO9 equates
A./.%.$.:.4 then !our 3ournal line debit entr! *ill be A./.ODPF.$.:.4
+reating A""lication Accounting .e%inition * AA.
In the previous section o( this SLA !ou have learnt creation o( the Aournal Line
$e(inition. 9o* it is ti#e to create AA$ *hich is 5Application Accounting
$e(inition5.
)he purpose o( AA$ in SLA is to dictate *hich 5Aournal Line $e(inition5 #ust be
used *hen a speci(ic event ta"es place against a speci(ic t!pe o( transaction in a
speci(ic #odule li"e 'a!ables or Receivables. I( !ou recollect the 5Aournal Line
$e(inition5 de(inition creates a %redit Line and the $ebit Line o( a Aournal.
Oracle ships out o( the bo& an AA$ (or ever! si#pl! #odule-application that uses
SLA. .ence (or each application li"e A'AR'A'O etc there *ill e&ist an e&isting
AA$ in the Subledger ,odules. .o*ever (or this e&a#ple *e *ill create a ne*
AA$ (or 'a!ables.
In the previous article !ou created a Aournal Line $e(inition that is responsible (or
constructing a Aournal. .o*ever in AA$ screen !ou *ill speci(! *hen the Aournal
Line $e(inition *ill be used. In this case as per the i#age belo* *e are stating
that 3ournal line de(inition A9IL=AL$ should be used (or creating 3ournal
*henever an! event occurs against an Invoice in 'a!ables.
2ou can also clic" on 5.eader Assign#ent5 button in AA$ to attached 5Aournal
:ntr! $escription5 LA:$M *hich dictates ho* the Aournal .eader description *ill
be constructed. I( !ou recollect in Aournal :ntr! $escription *e concatenate static
te&t and d!na#ic content (ro# SLA SourcesL#apped to $/ colu#ns or pl-sql
(unctionsM so as to construct a description (or Aournal Line or Aournal header.
In this article *e have seen that AA$ is created (or each #odule. .o*ever in an!
i#ple#entation there is a need to per(or# accounting (or all the #odules.
5A''S246SIO9 675 #ight be running 'a!ables and Receivables and also 'ro3ect
Accounting. .ence *e need to create a SLA,JSubledger Accounting ,ethod.
6sing AA$ *e speci(! the Aournal creation rules per #odule. In SLA, *e speci(!
ho* the Aournals #ust be built (or the entire organi1ation 5A''S246SIO9 675
across 'a!ables and Receivables and 'ro3ect Accounting. )he co#pan!
5A''S246SIO9 675 *ill have a legal entit! in 67 and hence the SLA, *ill be
attached to the 67 Legal :ntit!.
+reate Subledger Accounting /ethod
In previous section *e have seen that in SLA the 5Application Accounting
$e(inition5 is created (or each #odule in :J/usiness Suite. .o*ever in an!
i#ple#entation there is a need to per(or# accounting across various di((erent
#odules. 4or e&a#ple a co#pan! na#ed 5A''S246SIO9 675 #ight be running
'a!ables and Receivables and also 'ro3ect Accounting. .ence *e need to create a
SLA, LSubledger Accounting ,ethodM that *ill ta"e care o( generating the
Accounting 3ournal lines (or each o( the #odule. .ence a SLA, is nothing but a
grouping o( all the AA$0s possibl! (or a given chart o( account.
6sing AA$ *e speci(! the Aournal creation rules per #odule. In SLA, *e speci(!
the applications-#odules (or *hich the Aournals #ust be built (or the entire
organi1ation such as 5A''S246SIO9 675 across 'a!ables and Receivables and
'ro3ect Accounting. )he decision o( *hether the 3ournal #ust be created is
delegated to the AA$. As (or ho* the 3ournal is constructed and ho* the accounts
are derived is delegated to the Aournal Line $e(inition.
)he co#pan! such as 5A''S246SIO9 675 *ill have a legal entit! in 67 and
hence the SLA, *ill be attached to the 67 Legal :ntit!.
In the i#age belo* *e are creating a SLA, na#ed A9IL=SLA, and attaching
the AA$ na#ed A9IL='A2A/L:S. )his is a si#plistic e&a#ple because in
realit! !ou *ill have the AA$0s o( other applications li"e Receivables 'ro3ect
Accounting 4i&ed Assets etc attached to the SLA, as *ell.
1n the abo!e i$age( click on Accounting Setu"s( and here you can attach
the SLA/ to a Ledger. ,o re$ind you( in R22( the Ledger is eui!alent
o% set o% books in 22i.
,esting and ex"laination o% SLA +on%ig
In this article *e *ill test the con(iguration to see the results o( the con(iguration
per(or#ed. 8e *ill also e&plain the results o( the test.
Our SLA setup *as done (or 'a!ables hence *e *ill create an Invoice in 'a!ables
and chec" the accounting entries to reconcile those against our SLA setup.
I( !ou recollect *e created an AA$ na#ed A9IL='A2/L:S *hich is attached to
Oracle 'a!ables #odule. )his AA$ *ill invo"e AL$ na#ed A9IL=AL$ to build
the 3ournal lines *hen an event ta"es place against the 'a!ables invoice.
In the i#age belo* *e are creating an Invoice (ro# 'a!ables responsibilit! and
ensuring its invoice line distribution account is F1J11FJE1FFJFFFFJFFF.
9e&t *e clic" on Actions button and validate the invoice and create accounting
entries.
9o* chec" the accounting generated b! clic"ing on #enu title ReportsQQ;ie*
Accounting as sho*n in the i#age belo*.
2ou *ill notice that the $ebit entr! o( 1FFF is charged to F1J11FJODPFJFFFFJFFF
instead o( being charged to F1J11FJE1FFJFFFFJFFF in the Invoice $istribution Line
o( 'a!ables. 'lease note that the third seg#ents value o( E1FF (ro# Invoice
$istribution has been replaced b! ODPF (ro# A$R na#ed A9IL=:C':9S:=A$R
as sho*n belo*.
)he co#plete logic is described a(ter this i#age.
9o* let us revisit ho* the credit line in the 3ournal has been built. )!picall! %ode
%o#bination (or the credit-liabilit! accounting entr! o( the invoice line is pic"ed
(ro# 'a!ables Options setup o( the operating unit. .o*ever in this case in SLA
*e have hard coded the credit account to be F1.FFF.222F.FFFF.FFF. )his *as done
b! de(ining A9IL=LIA/ILI2=A$R as sho*n belo*. In this case the A$R returns
the co#plete %%I$ because the Output )!pe radio button is set to 4le&(ield.
.ence the SLA has generated the sa#e %redit entr! %%I$ (or the invoice as
sho*n in i#age belo*
9eedless to sa! that the A9IL=LIA/ILI)2=A$R *as attached to the Aournal Line
)!peKA9IL=AL)=%R:$I).
'e%ore we see the ste"s %or custo$i3ation o% SLA( let us %irst do so$e
uestions and answers
4uestion * I can custo#i1e the account generator in 'rocure#ent and 4i&ed
Assets. $o I reall! ever need to custo#i1e <Subledger Accounting> in such casesR
Answer* )he preJcon(igured SLA b! Oracle *ill use the accounts generated in
respective #odules as the source. The seeded ADR's will in most cases return the
very same accounts that are generated in the respective modules. :((ectivel!
5garbage in garbage out5 or !ou can sa! 5qualit! o( the account that goes into
SLA and the sa#e qualit! accounts are then sent to General Ledger5. )he #essage
(ro# seeded SLA in #ost cases is <8hat !ou (eed to SLA *ill also be (ed into the
Oracle General Ledger>. )here(ore i( !ou have alread! custo#i1ed the account
generation *or"(lo* in the respective #odule then !ou do not require
custo#i1ation in SLA. In (act the custo#i1ations on the seeded SLA
con(igurations #ust be "ept to bare #ini#u#. Although SLA provides !ou *ith
abilit! to override accounting de(inition ho*ever the #ain reason (or creation o(
SLA *as to i#ple#ent #ultiple shado* accountings against ledgers.
4uestion * I( all the respective #odules can generate accounting properl! then
*h! is SLA reall! neededR
Answer * 8ell the #ain reason behind creation o( SLA itsel( *as to create
shado* 3ournals (or secondar! ledger. 'lease see the 'art 1 in this series o( articles.
9o* let us ta"e the e&a#ple (or custo#i1ation o( an e&isting SLA de(inition preJ
seeded b! Oracle in R12. In this e&a#ple a SLA, na#ed
S)A9$AR$=A%%R6AL is attached to the Ledger LSet O( /oo" equivalent o( 11i
M. As !ou *ill notice (ro# the i#age belo* #an! #odules such as Leasing Loans
%ash ,anage#ent 'a!ables etc are attached to this SLA,. .o*ever *e are
interested in #odi(!ing 3ust the 'a!ables piece o( this SLA,. %reate a cop! o( this
SLA, as sho*n in the i#age belo*. 8e *ill create a SLA, na#ed
A9IL=SLA,==S)A9$AR$=A%%R6AL *hich happens to be the e&act cop! o(
SLA, na#ed S)A9$AR$=A%%R6AL.
9o* create ne* entr! (or 'a!ables *ithin the copied SLA, i.e. ne* SLA, *ill
be 5 A9IL=SLA,==S)A9$AR$=A%%R6AL5
9o* !ou have created a ne* SLA,. In this SLA, end date the AA$ assign#ent
o( 'a!ables and add a ne* entr! (or 'a!ables. 9ote that *e still have AA$ na#ed
5Accrual /asis5 attached. .o*ever a(ter *e cop! the 5Accrual /asis5 into a
custo# AA$ *e *ill then return to this screen in order to replace 5Accrual /asis5
b! custo# AA$. %lic" on 5Application Accounting $e(inition5 button.
9o* clic" on cop! and this ti#e *e *ill cop! the AA$ de(inition na#ed
<Accrual /asis> to create a ne* AA$ na#ed A9IL=S)$='A2A/L:S=S)$.
)he ne* AA$ *ill be called A9IL=S)$='A2A/L:S=S)$ as sho*n belo*.
%lic" on button labelled $one to co#plete the %op! operation (or the AA$.
9o* this ne* AA$ has been created. /e(ore *e custo#i1e this AA$ *e need to
ensure that this AA$ has been attached to the custo# SLA, that *e created in
Step 1 o( this article.
9o* bac" to the SLA, screen (or the custo# SLA, (or 'a!ables AA$
assign#ent record *e attach the custo# AA$ to 'a!ables. 'lease note that the
'a!ables entr! that is attached to custo# AA$ na#ed <Accrual /asis> has no*
been end dated as sho*n in i#age belo*.
9o* go bac" to AA$ b! clic"ing on Application Accounting $e(inition button as
per the i#age above.
4ollo* the instructions as per i#ages belo*
9o* cop! the Aournal Line $e(inition itsel(. )he i#age belo* sho*s ho* the
custo#-copied 3ournal line de(inition *ill be #odi(ied. Our idea here is to attach a
custo# A$R (or the generation o( an account.
)he na#e o( the copied AL$ *ill appear as belo*.
Attach the custo# A$R as sho*n belo*
And no* attach !our custo# Aournal Line $e(inition to the custo# AA$.
)his co#pletes the c!cle (or custo#i1ation o( the preJseeded SLA con(iguration.

Potrebbero piacerti anche