Professional Documents
Culture Documents
Oracle E-Business Suite Release 12 Highlights
Oracle E-Business Suite Release 12 Highlights
o Recei$ts ? #d4!stments
7na$$lied, a$$lied
Both de%its ? credits
o ,isc. 'ash Recei$ts
Both de%its ? credits
#s 1e kno1 =Aie1 #cco!ntin> is a re$ort aainst distri%!tions to see the acco!ntin
information.
54
R12 Head Lines
Ho1 -aya%les #cco!ntin ha$$en in 11i
We kno1 acco!ntin data enerated and stored in =#cco!ntin Events> ta%les $rior to transfer
to <L in -aya%le. 2nce Transaction et com$leted it 1as need to r!n the ='reate #cco!ntin>
$rocess 1hich %asically $o$!late data into acco!ntin events ta%les.Then the act!al line
information move takes $lace from acco!ntin events ta%le to <eneral Leder Ta%les.The
e(istin 11i acco!ntin -rocess is can %e %est !nderstood %y fi!re %elo1.
S!%leder to Leder Re$ortin in 11i
/t means com$lete, final acco!ntin only availa%le in the <L
#ll de%its and credits
#ll 4o!rnal entries
#ll %alances
55
R12 Head Lines
The only iss!es in $re R12 versions 1as to link s!mmari&ed acco!ntin data 1ith so!rce details.
Ho1 it is resolved in Release 12 S!%leder #cco!ntin
#ll s!% leder acco!ntin data enerated and stored in shared SL# ta%les $rior to transfer to <L
, and this is achieved %y r!nnin ='reate #cco!ntin> to $o$!late SL# ta%les)Aery very similar
to -aya%le events*. 2nce this can %e done , !ser can =Aie1 #cco!ntin> only after ='reate
#cco!ntin> is r!n and com$leted s!ccessf!lly.
Transferrin #cco!ntin information from #-6#R to <L in R12
The 'reate #cco!ntin $rocess has similar o$tions, yo! can create acco!ntin in Final or .raft
mode and if Final mode is selected, the Transfer to <L $arameter can %e !sed to a!tomatically
transfer the acco!ntin created %y the corres$ondin r!n. When the 'reate #cco!ntin $rocess
transfers the 4o!rnal entries to <L it only transfers the acco!ntin created %y the $rocess that
calls it. /f there is acco!ntin created %y the online o$tion L Final or a $revio!s 'reate
#cco!ntin $roram that 1as not transferred, that acco!ntin 1ill not %e transferred. The
Transfer Xo!rnal Entries to <L $roram needs to %e ran se$arately to transfer any acco!ntin
created online or created %y a $revio!s 'reate #cco!ntin $rocess that did not transfer the
entries.
/s61as link an iss!e in 11iB
Ges, From .istri%!tions to SL#
'reate #cco!ntin $rocess
#$$lies acco!ntin r!les
Loads SL# ta%les, <L ta%les
'reates detailed data $er acco!ntin r!les,stores in SL# =distri%!tion links> ta%le
SL# .istri%!tion Links Ta%le
,!st 4oin thro!h to et tr!e .istri%!tion LLO SL# 4o!rnals matches
Holds finest ran!larity of acco!ntin data
,!lti$le distri%!tions may %e areated into a fe1 SL# 4o!rnal lines
and Final $ict!re looks like"
56
R12 Head Lines
SL# Iey attri%!te "Somethin called Event ,odel B What is all a%o!tB
Event ,odel are %asically definition of the s!% leder transaction ty$es and there life cycle.
/t has three levels
Event Entity" Hihest level, often 1 $er s!% leder a$$lication
Event 'lass" classifies transaction ty$es for acco!ntin r!le $!r$oses
Event Ty$e" for each transaction ty$e, defines $ossi%le actions 1ith acco!ntin
sinificance.
/t is very im$ortant that a$$lications m!st tell SL# 1hen an event has occ!rred.When a !ser
r!ns the SL# 'reate #cco!ntin $roram, it $rocesses all events 1ith the a$$ro$riate stat!s
1e have notice some of event classes in -aya%le and Receiva%le.
-aya%les
o /nvoice
o .e%it ,emo
o -re$ayment
o -ayments
o Ref!nds
Receiva%les
o /nvoice
o .e$osit
o Recei$t
o Bill Receiva%le
and ty$ical event Ty$es are like
#- /nvoice Events
o Aalidated
o #d4!sted
57
R12 Head Lines
o 'ancelled
#R Recei$t Events
o 'reated
o #$$lied
o 7na$$lied
o 7$dated
o Reversed
R12 SL# vis3[3vis #+ of 11i
For more details o thro!h the %elo1 to$ics "
7nderstandin <lo%al #cco!ntin Enine ) -rod!ct #+*
7nderstandin <lo%al #cco!ntin Enine 3 .!al $ostin, Ta%les, Re$orts
R12 SL#" From -rod!ct #cco!ntin to S!%leder #cco!ntin
R12 SL#" #naly&in S!% leder #cco!ntin
We have already seen oracle ne1 2racle S!% leder #cco!ntin re$laces the <lo%al #cco!ntin
Enine, 1hich normally !sed for E!ro$ean ? Reional Locali&ations need in earlier versions. SL#
itself e(tends the #+ enine f!nctionality %y $rovidin c!stomi&a%le acco!ntin r!les via a
fle(i%le
/s SL# a clone of #+B
Ges, almost the f!nctionality 1as derived from there itself, lets see vis3[3vis to !$take some of
the f!nctionality in these t1o $rod!cts.
0ot only f!nctionality, some of the re$orts re$laces the corres$ondin re$orts of the <lo%al
#cco!ntin Enine.
58
R12 Head Lines
The ood is that %oth the <lo%al #cco!ntin Enine)#+* and 2racle S!%leder #cco!ntin)SL#*
enerate acco!ntin from a com$iled definition of acco!ntin r!les defined %y !sers. 2racle
S!%leder #cco!ntin f!rther maintains version control on the r!les ena%lin !sers to modify
the r!les 1hile maintainin a!dita%ility.
/ntercom$any
0e1 feat!es centrali&ed $rocessin, a tiht interation 1ith Receiva%les ? -aya%les alon 1ith
nicly co!$led 1ith fle(i%le a$$roval r!les makes a %rand ne1 #(advanced*</S .0e1
Reconciliation Tools is yet another that makes settlement $roress easy.
Read for ,ore details
R12 =#</S>"
What makes =#dvancedB>
/n 2racle R12 </S ,od!le, seems some of the old feat!res and f!nctionality have %een reatly
enhanced 1ith addition of some more ne1 feat!res introd!ced. The $oint 1hich sho!ld %e
noted here is, R11i </S et ne1 name commonly kno1n as =#dvanced <lo%al /ntercom$any
System> in short 8#</S5. The difference is the $refi( 8#5, therefore 1ill take a close
microsco$ic vie1 on feat!re that makes 11i </S into #dvanced </S of R12.
Here are the candidate feat!res"
#%ility to create invoices )#R and #-*
2racle #dvanced <lo%al /ntercom$any System can create invoices in $aya%les and receiva%les
s!% leder from intercom$any transactions.
7sin 2racle #dvanced <lo%al /ntercom$any System !ser can enter transactions for m!lti$le
reci$ients 1ithin a sinle %atch. This allo1s !ser to s!%mit intercom$any transactions from one
initiator to one or more reci$ients in a sinle %atch.
-roration of transaction distri%!tion amo!nts
When !ser allocates more than one distri%!tion acco!nt in a %atch that has m!lti$le reci$ient
transactions, 2racle #dvanced <lo%al /ntercom$any System can a!tomatically $rorate the
distri%!tion amo!nts %ased on the reci$ient transaction amo!nts. The $roration of amo!nts is
also !sed %y 2racle #dvanced <lo%al /ntercom$any System to ad4!st the distri%!tion amo!nts
in the %atch 1hen a reci$ient transaction is deleted or it is re4ected.
59
R12 Head Lines
7$load Transaction Batches created in E(cel
This 1as a missin link in the earlier version, as earlier $rod!ct does not have ca$a%ility to !se
direct !$load f!nctionality, rather than interfacin thro!h 2$en </S interface. /n Release 12
#./ is heavily !sed in this mod!le, 1hich is re$lacement of e(ternal interation for #</S System
!sin %y mean of ,icrosoft %ased E(cel s$readsheet. 0o1 fle(i%ility is $rovided to !ser that can
enerate s$readsheet tem$lates that have feat!res of intercom$any entry $aes and !sin the
tem$lates the !ser can enter transactions in the s$readsheet and !$load them into 2racle
#dvanced <lo%al /ntercom$any System. The ood thin has fo!nd the standard tem$lates can
%e c!stomi&ed %y removin or addin the entry fields from a list of availa%le fields. This
feat!re is !sed to create a tem$late that contains only the entry fields that are im$ortant for
the %!siness. The re9!ired fields cannot %e removed from the tem$late. 2nce the tem$lates
are enerated, !ser can save them in their local com$!ter to re!se them in the f!t!re. This
fi!re descri%e the o$tions availa%le in %oth the versions.
,!lti$le reci$ients S!$$ort
Reversal of %atch6transaction
This chaned feat!re ena%les a !ser to reverse a 1hole %atch or an individ!al transaction in a
%atch. When the !ser reverses a %atch or a transaction, a ne1 reversal %atch is created, 1hich
dis$lays the references to the oriinal transaction. 2ne $oint to %e noticed is that ne1 %atch is
s!%mitted a!tomatically immediately after it is created. 0ot %oth the $arties )Sender
6receiver*, its only !sers 1ith access to the initiator orani&ation can reverse its %atches or
transactions. The set !$ is there 1here a !ser can choose a reversal method determinin if the
ne1 %atch 1ill %e created 1ith o$$osite sins, or 1ith s1itched de%its and credits.
.escri$tive fle(field s!$$ort
/n #</S descri$tive fle(fields is s!$$orted on the %atch and also on individ!al transactions
1ithin the %atch. .escri$tive fle(fields allo1 !ser to enter any additional information s$ecific
to the nat!re of %!siness, in the %atch and in the transactions. /m$ortant to note that these
.FF can %e !sed %y sender. The !ser can enter descri$tive fle(field information for the
reci$ient in the Reci$ient #cco!ntin section.
60
R12 Head Lines
Fle(i%le #$$roval R!les and Workflo1 0otifications
/n R12, #</S very similar to other mod!le, home $ae dis$lays notifications a%o!t a$$roval or
re4ection stat!ses of intercom$any transactions. Go! sho!ld note that notifications can %e sent
to the !sers via email. The r!les for a$$rovals and notifications can %e c!stomi&ed !sin 2racle
#$$roval ,anaement Enine )#,E*, 1hich allo1s the !ser to add e(tra a$$roval r!les and
hierarchies to s!it their %!siness needs.
.oc!ment attachment
The !ser can attach the doc!ments for the %atch as 1ell as for each of the transaction. When
!ser s!%mits the %atch, the doc!ments are transferred to res$ective reci$ients.
Transaction sec!rity
/ntercom$any transactions entry $aes incor$orate vario!s sec!rity feat!res. The !ser can
enter transactions only for those intercom$any orani&ations that are assined to the !ser.
2ther sec!rity feat!res incl!de minim!m transaction amo!nt, control amo!nt and f!nction
sec!rity.
For e(am$le"
/ntercom$any acco!ntant $rocesses intercom$any transactions for many intercom$any
orani&ations in the enter$rise.What is different %et1een these t1o is "
R11i 3 Each res$onsi%ility has only one s!%sidiary assined, therefore a !ser can initiate
intercom$any transactions for one s!%sidiary from each res$onsi%ility
R12 U the !ser can initiate intercom$any transactions for many tradin $artners 1itho!t
chanin res$onsi%ility
/ntercom$any -eriods
The ne1 /ntercom$any calendar ives the !ser the o$tion to control intercom$any transaction
$rocessin %y $eriods stat!s.
What is o%served in this f!nctionality can %e %est descri%e as"
/f a !ser 1ants to control intercom$any c!t3off dates, then the !ser can choose 1hich <eneral
Leder calendar 1ill %e !sed to control transaction entry %y intercom$any $eriod stat!s.
/ntercom$any 'alendar $revents !sers from enterin transactions in closed $eriods and from
closin the $eriod if o$en transactions e(ist for the $eriod !ser 1ants to close. When the !ser
tries to close <eneral Leder acco!ntin $eriod, or 2racle -aya%les $eriod or 2racle
Receiva%les $eriod 1hile /ntercom$any -eriod is still o$en, the 1arnin messae can %e
dis$layed informin !ser a%o!t the stat!s of intercom$any $eriod.
Set!$ -rofile 2$tions
/n #</S there is no $rofile o$tions that means these three as %elo1 intercom$any $rofile
o$tions !sed in R11i are o%solete in this release.
61
R12 Head Lines
/ntercom$any" -rotect Receiver 0at!ral #cco!nt
ntercom$any" S!%sidiary
/ntercom$any" 7se #!tomatic Transaction
/ntercom$any Reconciliation and Re$ortin
There are t1o ne1 re$orts avai%le in +,L -!%lisher format
/ntercom$any Transaction S!mmary re$ort
/ntercom$any #cco!nt .etails re$ort.
These re$orts re$lace re$orts that 1ere availa%le in the <lo%al /ntercom$any System )</S* in
Release 11i.
The ne1 re$orts offer all of the f!nctionality of the o%solete re$orts $l!s additional %enefits.
# %it on these 2 re$orts"
1*/ntercom$any Transaction S!mmary re$ort re$laces the /ntercom$any Transaction .etail
re$ort and 7na$$roved Transaction Listin re$ort.
The $!r$soe of this re$ort is to ive !ser a clear overvie1 of intercom$any transactions and
their stat!ses, there so that day3to3day tasks and s$eeds !$ $eriod close activities.
This re$ort also $rovides s!$$ortin doc!mentation for intercom$any reconciliation and hel$s
kee$ intercom$any in %alance %y !ncoverin any $otential discre$ancies.
2* /ntercom$any #cco!nt .etails re$ort re$laces the Transaction #ctivity S!mmary re$ort
This ne1 re$ort $rovides a detailed listin of all acco!ntin lines for intercom$any %atches,
ro!$ed %y transaction.
The re$ort is divided into t1o sections"
one section for o!t%o!nd %atches
one section in%o!nd transactions.
The o!t%o!nd section sho1s transactions initiated %y the orani&ations to 1hich the !ser has
an access, the in%o!nd section sho1s transactions received %y these orani&ations. The !ser
can choose 1hether to incl!de in%o!nd, o!t%o!nd, or %oth sections in the re$ort.
The !ser can r!n the re$ort for one or many orani&ations to 1hich the !ser is iven the
access.
7ser can select 1hat $arameters like initiator, Reci$ient, <L .ate rane, Batch 0!m%er rane,
Transaction Stat!s, '!rrency, Batch Ty$e, /nvoice 0!m%er, and many more to r!n the re$ort
%y. 7ser can r!n the re$ort %y ranes of initiator and reci$ient acco!nts to see 1hat
transactions make !$ their %alances.
62
R12 Head Lines