R12 Head Lines

Release 12 Oracle E-Business Financials

R12, Financial track is one of BEST release ever. We have already seen some reat f!nctionality like" # sin le res$onsi%ility to access and transact on m!lti$le or ani&ations # sin le led er to mana e m!lti$le c!rrencies Led er sets to mana e acco!ntin $rocesses across led ers 'entrali&ed r!les en ines for ta(, acco!ntin and inter com$any # se$arate and sim$le $ayment creation and delivery sol!tion 'entrali&ed tradin $artners )s!$$liers, %anks, first $arty le al entities* Sim$lified re$ortin via +,L -!%lisher and .B/ 0ettin across tradin $artners Here are some of feat!res"

Oracle Payable:
Fe1 Feat!res like invoice Lines, Line level a$$rovals, ,atchin to a -2 shi$ment or recei$t, S!$$liers in T'# makes a com$lete ne1 look. Read in details" Read for more details Welcome to R12 #cco!nt -aya%le" #s 1e learnt d!rin Release 12, the E3B!siness S!ite has co!$le of ne1 $rod!cts like S!%led er #cco!ntin , E3B!siness Ta( th!s si nificant chan es have %een o%served in #cco!nt -aya%le data mod!le as some of f!nctionality is shared %y some other $rod!cts. Th!s it is im$ortant to !nderstand 1hat is ne1. / 1o!ld like to %riefly o!tline the details of some of ne1 chan es and !nderlyin im$act on the o%4ects. ,ore details can %e fo!nd in R12 release doc!ments $!%lished %y 2racle a month a o. Let5s have a dissection vie1 of R12 $aya%le, 1ith some of its core o%4ects S!$$liers" We have seen in 11i S!$$liers defined in #-. S!$$lier contacts re$licated for each s!$$lier site.

R12 Head Lines Where as in R12 S!$$lier %ecomes as T'# -arty. S!$$liers Sites as T'# -arty Site for each distinct address. 'ontacts for each s!$$lier6address , it means Sin le s!$$lier address and contact can %e levera ed %y m!lti$le sites, for each 27 o # sin le chan e to an address can %e seen instantly %y all 27s o 0o lon er need to man!ally 8$!sh5 !$dates across 27s.This can %e %est !nderstood %y the fi !re %elo1.

Then the 9!estion is 1hat 1ill ha$$en if any one can come from e(istin financial $rod!cts. The /m$act from !$ rade can s!mmari&e as" 1. When 1e !$ rade s!$$lier ta%les re$laced 1ith %ack1ard com$ati%le vie1s. 2. 2ne $arty site for each distinct s!$$lier site address 'o!ntry and address line1 are re9!ired, this is %eca!se creation of s!$$liers in -arty in T'# data model 1o!ld re9!ires 'o!ntry and address information, %!t it also !nderstood if there is no co!ntry or address line 1 s$ecified for a s!$$lier site in cases 1hen !$ rades takes $lace,

R12 Head Lines -aya%les derives the co!ntry %ased on the most fre9!ently !sed o$eratin !nit of the S!$$lier5s historical transactions. :. Em$loyee as s!$$liers" address 02T mi rated to $arty site in T'# remains in 2racle HR for data sec!rity reasons. #s 1e kno1 in 11i em$loyees are $art of internal s!$$lier5s record in order for 2racle -aya%les to create $ayments for their e($ense re$orts. Em$loyees defined in 2racle H!man Reso!rces and associated 1ith an 2racle -aya%les s!$$lier record have e(istin $arty information. .!rin the !$ rade, 2racle -aya%les !$dates the e(istin $arty information to have a $arty !sa e of s!$$lier %!t it does not mi rate the em$loyee address to the $arty site in T'#, they remain in 2racle H!man Reso!rces for data sec!rity reasons. ;. 7tili&e T'# -arty relationshi$s for franchise or s!%sidiary and its $arent com$any. /nvoice: Till 11i version, 1e have seen invoices" Had only distri%!tions line. #llocation of frei ht and s$ecial char es are ca$t!red at the distri%!tion level only Ta( and $ayment and -ro4ect acco!ntin -ayment 1as ca$t!red thro! h lo%al .escri$tive Fle(fields.

B!t in R12, 1. /nvoice Lines as a ne1 additional line accommodated in /nvoice data model.

Beca!se of introd!ction of invoice line there is si nificant im$rovement of data flo1 1ith n other oracle mod!les like Fi(ed #sset 3 #sset Trackin B!siness Ta( 3 Ta( line -ayment 3 -ayment S!%Led er #cco!ntin 3 #cco!ntin

R12 Head Lines

2. #llocate frei ht and s$ecial char es are ca$t!red to the lines on the invoice :. /nvoice distri%!tions created at the ma(im!m level of detail similar to 11i. ;. 'ore f!nctionality The im$act 1ith 7$ rade can %e s!mmari&ed as" 1. 2ne invoice line for every distri%!tion in 11i 2. S!% Led er #cco!ntin re9!ires that -aya%les transform the invoice distri%!tions to %e stored at the ma(im!m level of detail :. <lo%al .escri$tive Fle(fields mi rated to named col!mns. That5s means f!nctional testin is more re9!ired 1hile !$ rade takes $lace. Banks and Bank .etails 0o1 a days cor$orate treas!ry role has %een reatly enhanced th!s $ickin !$ a lo%al %ank as $artner for all %ankin need is demand of time in lo%al 1orkin model. The recent co!$le of years have seen drastic increase in ac9!isition and mer er of com$any th!s lo%al 1orkin as 1ell as lo%al instance et $o$!larity in ER- arena, and this is one of reason of the reason %ank data model has %een si nificant chan es from 11 to 11i and 11i to R12. /nternal Bank #cco!nts /n 11i yo! mi ht have o%served, internal Banks defined in #- and that is shared %y #-6#R6'E, -ayroll and Treas!ry and they are %ank acco!nts often re$licated in m!lti$le 27s Where as in R12, Bank and Branch %ecome $art of T'# -arties. /nternal Bank #cco!nt in 'ash ,ana ement 1hich is o1ned %y a Le al Entity. Here the 2$eratin !nits have ranted !sa e ri hts.

S!$$liers Bank #cco!nts /n 11i R12 S!$$liers, Banks and Branches are defined as -arties in T'# S!$$lier )$arty5s* $ayment information and all $ayment instr!ments )Bank #cco!nts, 'redit 'ards* moved into 2racle -ayments. Banks6Branches defined in #Bank acco!nts often re$licated in m!lti$le 27s Before

R12 Head Lines

The ty$ical data model for %ank can %e s!mmari&ed as"

/m$act of 7$ rade 1. With 7$ rade %anks and %ranches mi rated to T'# $arties 2. Banks mer ed if the follo1in attri%!tes are all the same" a. Bank 0!m%er %. /nstit!tion ty$e c. 'o!ntry d. Bank admin email e. Bank name alt f. Ta( $ayer /. . Ta( reference n!m%er h. .escri$tion, Effective dates :. Bank acco!nts, %ank acco!nt !ses are mi rated into cash mana ement. ;. Transactions are stam$ed 1ith the %ank acco!nt !ses identifiers as $art of the !$ rade /nte ration 1ith 2racle E3B!siness Ta( /n 11i

R12 Head Lines /n R12 # ne1 mod!le eB!sinessTa( determines ta( %ased on facts a%o!t each transaction, this is reason 1hy 2racle has introd!ced additional line information at invoice level. The mod!le =e%!siness Ta(> set and confi !re Ta( r!les 1hich can %e vie1ed Ta( attri%!tes collected in fields on key entities 'onfi !re ta( r!les once $er re ime and share 1ith yo!r le al entities

2racle standard f!nctionality 1as %ased o!t of 7ser 1hich determines ta( %y assi nin Ta( 'odes at line level of invoice and Ta( r!les 1as controlled at !nderline code. There 1as lo%al descri$tive fle( fields 1ere ca$t!red for co!ntry3s$ecific ta( attri%!tes. ,ore im$ortant at most of the set!$ $erformed at 27 level.

/m$act of 7$ rade 1. -aya%les Ta( set!$, Ta( 'ode defa!ltin r!les defined $er 27 are mi rated to eB!siness Ta(. 2. 27s mi rated to ta( content o1ner in R12 :. Ta( information in ta( codes are transformed to Re ime3Rate flo1. ;. E3B!siness Ta( takes information from the #- invoice lines and creates s!mmary and detail ta( lines in the E3B!siness Ta( re$ository. ,!lti 2r #ccess 'ontrol ,2#' is ne1 enhancement to the ,!lti$le 2r ani&ations feat!re of 2racle #$$lications. This feat!re ena%les !ser to access data from one or many 2$eratin 7nits 1hile 1ithin a set iven res$onsi%ility. .!e to this chan e, all $rocessin and some Re$ortin in 2racle -aya%les is availa%le across 2$eratin 7nits from a sin le #$$lications res$onsi%ility. Hence yo! can isolate yo!r transaction data %y 2$eratin !nit for sec!rity and local level com$liance 1hile still ena%lin shared Service centre $rocessin . .ata sec!rity is maintained !sin the ,!lti$le 2r ani&ations Sec!rity -rofile, defined in 2racle HR,S, 1hich s$ecifies a list of o$eratin !nits and determines the data access $rivile es for a !ser. /m$act of 7$ rade R12 7$ rade does not a!tomatically create sec!rity $rofiles, th!s is im$ortant if any one 1ant to !se ,!lti$le 2r ani&ations #ccess 'ontrol, the first thin s is to define sec!rity $rofiles, then link them to res$ective res$onsi%ilities or !sers. Reference" .etails can %e fo!nd more on R12 R'. doc!ments, from 2racle site.

R12 " S!$$liers ? Tradin 'omm!nity #rchitect!re" /n earlier $ost, 1e have seen s!$$lier has %een moved into T'# model. 'om$arin to 11i version, three ne1 #- ta%les containin s!$$lier !ni9!e data %een introd!ced. They have the links to T'# ta%les"

R12 Head Lines

#-@S7--L/ERS #-@S7--L/ER@S/TES@#LL #-@S7--L/ER@'20T#'TS

#nd more im$ortant 1e !nderstood three old -2 Aendors ta%les o%solete, %y Aie1s $rovided for %ack1ard com$ati%ility Here is data model .This 1ill really hel$s yo! to !nderstand 1hile desi nin inte ration 1ith EBS R12.

Le al Entity ? Le al Entity #rchitect!re

R12 Head Lines

Release 12" Le al Entity !$take We are 1ell a1are of some of 2racle E3B!siness S!ite R12 #rchitect!ral chan es in the Financials section like" Le al Entity Led er Sets #cco!ntin En ine )SL#* Transaction Based Ta(es)E3Ta(* /nter3com$any #cco!ntin )#</S* ,!lti32r ani&ation #ccess 'ontrol ),2#'*

Let5s !$take to Le al Entity" Financial %ooks defined as =# Le al Entity is an entity identified thro! h the re istration 1ith the le al a!thority.> That5s means,/n this com$liance 1orld and in 2racle system it corres$onds closely and defined as the system =Le al Entity> corres$onds 1ith an inde$endently identifia%le =le al $erson> a $!%lic com$any, a $rivate %!siness or limited $artnershi$, a tr!st, a not3for3$rofit, a overnment or a non3 overnment or ani&ation )0<2* 3 that can o$erate as if it 1ere a real $erson in cond!ctin %!siness transactions. What is meant for 1ith LEB 'an et the ri ht to" o 21n $ro$erty 1eather its is assets or inventory or receiva%le o Trade )%orro1, sell, %!y, inc!r e($enses, em$loy* #nd the res$onsi%ility to" o Re$ay de%t )lia%ilities, e9!ity* o -ay Ta(es o #cco!nt for themselves )le al re$orts, a!dits*

0ote for R11i 1ith res$ect to R12 Release 11i <RE6LEs 1ill %e !$ raded as Release 12 Le al Entities. Release 11i 2$eratin 7nits and /nventory or s 1ill %e !$ raded as Esta%lishments. 2ne Le al Entity can have several esta%lishments. /n Release 12 there is no s$ecific link %et1een 2$eratin 7nits and Le al Entities 1here as in R11 it 1as. The Le al Entity is linked to a Led er and the 2$eratin !nit is also linked to a Led er.

R12 Head Lines

Every Release 12 transaction m!st %e associated 1ith %oth an 2$eratin 7nit and a Le al Entity. The Le al Entity is also re9!ired for e3B!siness Ta( to esta%lish 1hich ta(es 1ill %e a$$lica%le to the transaction.

The 0e1 ,odel called LEA (Le al Entity #rchitect!re*> Le al Entity architect!re, 1hich is ne1 in this release, $rovides !sers 1ith the a%ility to model an enter$rise5s le al or ani&ational str!ct!re and define r!les and attri%!tes s$ecific to le al entities. Bank #cco!nt 1hether its is remittance %ank or internal %ank is no1 o1ned %y the Le al Entity instead of 2$eratin 7nit, and can %e !sed %y any of the 2$eratin 7nits sharin the same Led er as that Le al Entity.

#s marked )dotted red line* in a%ove fi !re the relationshi$ %et1een le al Entity and 2$eratin 7nit is no more active. This conce$t allo1s 2$eratin 7nits to %e overned %y more than one 4!risdiction, %!t the acco!ntin is still $erformed in a sin le led er. ,!lti$le Le al Entities can %e associated 1ith a sin le Led er, allo1in the LEs to share the same led er and chart of acco!nts, calendar and c!rrency. Each LE $oints to one Led er. ,!lti$le 2$eratin 7nits can also %e associated 1ith a sin le Led er. Each 27 $oints to only on Led er. Take a noteC in R12 EBS m!lti$le le al entities can %e associated 1ith a sin le Led er, allo1in the LEs to share the same led er and chart of acco!nts, calendar and c!rrency. Each LE $oints to one Led er. ,!lti$le 2$eratin 7nits can also %e associated 1ith a sin le Led er. Each 27 $oints to only on Led er. Where it affects" =,ost of the Financial #$$lication -rod!cts> Cash Management (Bank) #s disc!ssed in earlier, in Release 12 Bank #cco!nts are o1ned %y Le al Entities and can %e accessed %y m!lti$le 2$eratin 7nits.

R12 Head Lines #s 1e kno1 in 11i the Bank #cco!nts 1ere 2$eratin 7nit S$ecific. For all /nternal Banks sho!ld %e assi ned to a Le al Entity.

Receiva%les" 0o1 all RE' activity m!st have a le al o1ner, so Le al Entity is stam$ed on every transaction. Receiva%les activity s!ch as transaction 1hether credit memo or de%it memo or invoice m!st have stam$s on it and recei$t header 1ith the Le al Entity information. Beca!se there can %e m!lti$le le al entities !sin the same led er, it may %e necessary for the !ser to assi n the LE. Each transaction can only %elon to one Le al Entity, so 1hen m!lti$le le al entities e(ist, either the system or the !ser 1ill assi n the LE. Transaction

The defa!ltin hierarchy for a transaction comes from the set!$ of the Transaction Ty$e and Transaction Batch So!rce. Receiva%les 1ill look first to the Transaction ty$e. /f a LE has not %een assi ned, then Receiva%les 1ill look to the Batch So!rce. The assi nment of the LE to the Transaction Ty$e and Transaction Batch So!rce is o$tion, so if Receiva%les cannot find a defa!lt LE, then it is !$ to the !ser to $rovide the LE val!e. Recei$ts

The LE defa!ltin for recei$ts 1orks differently than transactions. Let5s look at ho1 defa!ltin occ!rs for the Recei$t Header. #s 1e kno1 , internal Bank #cco!nts is not o1ned %y le al entities instead of o$eratin !nits, so LE defa!lts from internal )remittance* %ank acco!nt. The Recei$t ,ethod in Receiva%les has the %ank acco!nt assi nment, 1hich determines 1hat %ank acco!nt ets assi ned to the recei$t. Take a note in version 11 the recei$t ,ethod 1as called the -ayment ,ethod. 0o1 in Release 12 this feat!red 1ith same name =-ayment ,ethod> no1 !sed %y ne1 a$$lication called 2racle -ayments. Therefore in #R, yo! 1ill no1 see a Recei$t ,ethod, 1hich is $art of recei$t set!$C and -ayment ,ethod, 1hich is $art of -ayments set!$. 2nce the %ank acco!nt is assi ned to a recei$t header, this information can %e !sed to find the a$$ro$riate LE. Beca!se the LE comes from only one so!rce, the %ank acco!nt, there is no s$ecial set!$ to %e $erformed in Receiva%les. .efa!ltin of the sin le LE al1ays occ!rs, so the !ser does not need to assi n or !$date LE on recei$ts. Ho1 LE affects recei$ts and there a$$lications and ref!nds We seen the recei$ts inherit the LE from the %ank acco!nt 1eather its is man!al, #!tomatic, Lock%o( and -ost D!ick 'ash -ro rams. There is no 1ay that !ser can chan e the val!e.

10

R12 Head Lines Recei$t a$$lication across Le al Entities is allo1ed if the recei$t and transactions are in same 27 and S!% Led ers #cco!ntin 1ill $erformed %y inter3com$any acco!ntin for cross3LE recei$t a$$lications or cross3LE recei$t clearin . SL# 1ill create inter3com$any acco!ntin as lon as LE is set!$ as one of the ''/. )#cco!nt 'ode 'om%ination* se ment derivation so!rces in SL#. -aya%le /nvoices and -ayments indicate the o$eratin !nit and the le al entity o1ner of the transaction. The le al entity can %e !sed as selection criteria 1hen $re$arin $ay r!ns. -ro4ects #s 1e kno1 in 11i in EBS maintains the defa!lt le al conte(t on the 2$eratin 7nit. There is not m!ch im$act in -ro4ects model. Earlier in 11i 1e !sed to consider the Le al Entity of the 2$eratin 7nit as the Le al Entity of the -ro4ects Transactions. 0o1 the Le al Entity attached at the .efa!lt Le al 'onte(t of the 2$eratin 7nit is the Le al Entity of the -ro4ects Transactions. So the Le al Entity of the -ro4ects e($endit!re transactions 1ill %e the Le al Entity attached at the .efa!lt Le al 'onte(t of the E($endit!re 2$eratin 7nit and the Le al Entity of the -ro4ect 1ill %e the Le al Entity attached at the .efa!lt Le al 'onte(t of the -ro4ect o1nin o$eratin !nit. LE and T'# Le al Entity is still de$endent on T'#. # $arty )s!$$lier, c!stomer, %ank, st!dent etc* is an entity that can enter into %!siness relationshi$s. #s 1e kno1 the 2racle T'#5s model s!$$orts fo!r ty$es of $arties" or ani&ation, $erson, ro!$, and $arty relationshi$. 7nder the T'# model, -arties )incl!din Le al Entities* e(ist 4!st once in o!r E3%!siness S!ite system for sin le maintenance and consistency. Le al Entities 1ill %e stored in T'# as -arties of $arty ty$e 82R<#0/E#T/205. # Le al -rofile, containin s$ecific Le al Entity attri%!tes, 1ill %e associated to the T'# -arty. /n addition, other T'# com$onents 1ill %e !sed for #ddresses, 'ontacts, -arty /nformation, etc. Where to do the set!$ There sho!ld %e no conf!sion. ,ay %e , some may think if this is 4!st e(tension of <RE6LE from old version , then Why this re9!ired to do set !$ from %oth #S, and HR in R12B /n R12 ,it is se$arate the le al entity from the <RE 1hich is a HR or ani&ation. We did not link the 2 entities to ether as they serve 2 different $!r$oses alto ether. The HR model does not look at the ne1 Le al Entity model. /t contin!es to !se the <RE6LE as a le al entity. So the HR re9!irement can %e achieved !sin the HR or ani&ation of ty$e <RE6LE. Therefore, Le al Entities do have to %e set !$ in %oth #S, and HR in R12.

11

R12 Head Lines Ho$e this so!nd interestin for ne1 chan e in Financial #rchitect!re. ,ore details a%o!t LE" Ho1 do / define my Le al EntitiesB

/n the real 1orld a Le al Entity )LE* can enter into contracts, o1n cash )%ank acco!nts*, em$loy $eo$le, $ay ta(es, %e s!ed and similar. /n 2racle Financials Release 12, a 1hole ne1 $rod!ctC Le al Entity 'onfi !rator, 1as created to mana e them. We allo1 yo! to define yo!r real 1orld Le al Entities and then ma$ them to the E3B!siness S!ite o%4ects and str!ct!res. Transactions are stam$ed 1ith an o1nin )first $arty* Le al Entity and that 1ill %e !sed to drive ta(, acco!ntin , intercom$any and Le al Re$ortin . So let5s look at the relationshi$s LE have to other E3B!siness s!ite o%4ects. 13 #cco!ntin Str!ct!res /n the <eneral Led er Set 7$ a Le al Entity can %e ma$$ed to # Sin le Led er 2ne or more Balancin Se ment Aal!es )aka 'om$any 'ode* 1ithin a led er.

2 3 2$eratin 7nit There is no e($licit ma$$in of Le al Entity to an 27, the relationshi$ is derived from the led er assi ned to the 27 and the Le al Entity ma$$in s to led ers as detailed a%ove. So ho1 mi ht yo! set !$ yo!r LE in relation to yo!r other set !$ in financialsB There are t1o im$lementation models 1" ,any LE are ma$$ed to the Balancin Se ment Aal!e )BSA, aka 'om$any code* 1ithin a Led er, so m!lti$le LE are acco!nted for in a led er. #n 27 1ill have one Led er assi ned so transactions for many LE are $rocessed and acco!nted in a sin le 27 1"1"1 # sin le LE is ma$$ed to a Led er #n 27 1ill have one Led er assi ned Therefore an 27 only has one LE )that means it is easy to derive the LE iven the 27*

So 1hat model sho!ld yo! !seB That de$ends 1here the LE are re istered. The 1" , model is recommended and $referred in the 7S, the 1"1"1 model is recommended for most non 7S re ions ,!lti32r #ccess 'ontrols ,!lti32r #ccess 'ontrol feat!re allo1s yo! to enter $rocess data and enerate re$orts from a sin le res$onsi%ility.

12

R12 Head Lines

For ,ore details" ,2#' " From ,!lti32r F.To ,!lti3#ccess

This ne1 Feat!re in R12, ena%les com$anies that have im$lemented or im$lementin shared services o$eratin model to efficiently $rocess %!siness transactions %y allo1in them to access, $rocess and re$ort on data for an !nlimited n!m%er of o$eratin !nits 1ithin a sin le a$$lications res$onsi%ility. 7sers are no lon er re9!ired to s1itch a$$lications res$onsi%ilities 1hen $rocessin transactions for m!lti$le o$eratin !nits.

.ata sec!rity is maintained !sin sec!rity $rofiles that determine the data access $rivile es associated to res$onsi%ilities ranted to a !ser. Beca!se of this yo! can $erform m!lti$le tasks across o$eratin !nits 1itho!t chan in res$onsi%ilities, the sim$le case can %e %est descri%ed as dia ram in the left, 1here : !ser from three difference 275s re9!ired three se$arate res$onsi%ility to $erform the task. ,2#' Benefits.. ,!lti32r #ccess 'ontrol feat!re allo1s yo! to enter, $rocess data and enerate re$orts from a sin le res$onsi%ility This is achieved %y $rovidin the 2$eratin 7nit field on the forms6$a es and 1hile r!nnin the conc!rrent $rocesses To Set this feat!re yo! need to define the sec!rity $rofile containin o$eratin !nits and set it at ,2" Sec!rity -rofile Go! can defa!lt the 2$eratin 7nit on forms6$a es %y settin the ,2" .efa!lt 2$eratin 7nit $rofile

What are the ne1 chan es from Multi Organizati n (Multi Org) t Multi!le Organizati n Access C ntr l (MOAC)" #s disc!ssed a%ove, sec!rity -rofiles for data sec!rity o ,2" Sec!rity -rofile o List of o$eratin !nits for a res$onsi%ility 27 field on 7/ o all transactions

13

R12 Head Lines o set!$ data s$ecific to 27, like transaction ty$e Enhanced ,!lti32r Re$ortin and -rocessin Led er6Led er Set $arameter on acco!ntin re$orts and $rocesses 27 $arameter on other standard re$orts and $rocesses o For e(am$le" s!%mit the -aya%les 2$en /nterface /m$ort 1627 $aram n!ll to im$ort all records across all 27s

Where and ho1 to define a sec!rity $rofileB 7sin 2racle HR,S, yo! can define yo!r sec!rity $rofile !sin t1o forms" The Sec!rity -rofile form The <lo%al Sec!rity -rofile form that is sho1n here.

The Sec!rity -rofile Form allo1s yo! to select o$eratin !nits from only one B!siness <ro!$. The <lo%al Sec!rity $rofile Form allo1s yo! to select o$eratin !nits from m!lti$le B!siness <ro!$s. The decision on 1hich form to !se is really !$ to yo! and de$ends on yo!r HR im$lementation and ho1 yo! 1ant to $artition data. #ll yo! need to do is enter a name, and select the Sec!rity Ty$e called =Sec!re or ani&ations %y or ani&ation hierarchy and6or or ani&ation list>. This allo1s yo! to assi n m!lti$le 27s. When assi nin o$eratin !nits, first select classification 2$eratin 7nit, and then select the or ani&ation or 2$eratin 7nit name. Go! can assi n as many o$eratin !nits as yo! 1ant.

#-3#R nettin This is !sed to offset -aya%le ? Receiva%les and other f!nctionality like tradin -artner #$$roval.

14

R12 Head Lines Read for ,ore" R12 " Settin !$ for #-6#R 0ettin " 2racle -!rchasin Go! enter $!rchasin doc!ments %y o$eratin !nit. These incl!de standard and %lanket a reement $!rchase orders, re9!isitions, RFD5s and 9!otes. Go! assi n a -2 shi$ment to an inventory or ani&ation, any inventory or ani&ation in the same set of %ooks as the -25s o$eratin !nit. Go! enter recei$ts %y inventory or ani&ation.

#cco!nt -aya%le Go! set!$ one defa!lt lia%ility acco!nt %y o$eratin !nit. Go! enter invoices in one o$eratin !nit at a time. Go! r!n $ayment r!ns in one o$eratin !nit at a time. Go! can consolidate s!$$lier invoices on one $ayment only 1ithin an o$eratin !nit. Go! set!$ %ank acco!nts and associated cash acco!nts 1ithin an o$eratin !nit. Go! select invoices for $ayment on one $ayment r!n for one %ank acco!nt %ased on $ay ro!$, $riority, amo!nt, c!rrency, or $ayment method )i.e. check, electronic* 1ithin an o$eratin !nit.

-26#-" Go! set!$ s!$$liers for the entire data%ase instance %!t addresses for each o$eratin !nit. Go! mer e s!$$liers and addresses 1ithin an o$eratin !nit. Go! re$ort s!$$lier6c!stomer nettin 1ithin an o$eratin !nit.

/n Finance, transaction mana ement $rocessin is one of la%or intensive task in ER-, as it re9!ires e(tensive data entry , chance are very very hi h for d!$lication6re3entry. #s 1e kno1 -roc!re to -ay life cycle start itself from contract mana ement till makin $ayment. #s 1e kno1 the efficient -roc!re to $ay $rocess have these s!% $rocessesC 'ontract ,ana ement -!rchase Re9!isitions -!rchase 2rders #cco!nts -aya%le 3 ,ana in invoice S!$$lier -ayment

/n real %!siness 1orld, many times 1hen system is r!nnin e(ternal6internal a!ditor are more interested in scr!tiny of"

15

R12 Head Lines

<oods received 6 invoices received /nacc!rate or d!$licate vendor ? material master records .iscre$ancies in $ayment terms .elays 6 lon $rocessin times .etect d!$licate vendor 7n!s!ally lar e or small $ayments 7na!thori&ed chan es made to invoices .etect .!$licate invoice .etect .!$licate $ayment #$$roval stat!s

Therefore, it is /n ho!se /S.6Finance /T or im$lementin com$any res$onsi%ility is to $rovide s!ch kind of adhoc re$ortin for a!ditor so that they can satisfy the a!dit re9!irement. # 8-2-5 9!ery that made #!ditors ha$$y /t 1as %ro! ht %y /S. team, as $art year end a!dit for a ER- system 1hich 1ent live : month %ack. /t 1as a one of re9!irement to dis$lay data for a $artic!lar -2 1hich covers data from there all H five $hases, means a $artic!lar -2 line consist of" 1. 2. :. ;. H. Re9!isition .etail -!rchase 2rder .etails Receivin .etails /nvoicin .etail -ayment .etails

Therefore tho! ht to share this 9!ery, ho$e this 1o!ld %e reat hel$ 1ho have s!ch kind of adhoc re9!irement from daily life. Here is 9!ery" SELE'T #.2R<@/. =2R< /.>, E.AE0.2R@0#,E =AE0.2R 0#,E>, 7--ER)E.AE0.2R@TG-E@L22I7-@'2.E* =AE0.2R TG-E>, F.AE0.2R@S/TE@'2.E =AE0.2R S/TE>, F.#..RESS@L/0E1 =#..RESS>, F.'/TG ='/TG>, F.'270TRG ='270TRG>, T2@'H#R)TR70')..'RE#T/20@.#TE** =-2 .#TE>, ..SE<,E0T1 =-2 07,BER>, ..TG-E@L22I7-@'2.E =-2 TG-E>, '.D7#0T/TG@2R.ERE. =DTG 2R.ERE.>, '.D7#0T/TG@'#0'ELLE. =DTG '#0'#LLE.>, <./TE,@.ES'R/-T/20 =/TE, .ES'R/-T/20>, <.70/T@-R/'E =70/T -R/'E>, )0AL)'.D7#0T/TG@2R.ERE.,J*30AL)'.D7#0T/TG@'#0'ELLE.,J**K0AL)<.70/T@-R/'E,J* =-2 Line #mo!nt>, )SELE'T .E'2.E)-H.#--R2AE.@FL#<, 8G5, 8#$$roved5* FR2, -2.-2@HE#.ERS@#LL -H

16

R12 Head Lines WHERE -H.-2@HE#.ER@/. L ..-2@HE#.ER@/.* =-2 ST#T7S>, #./0A2/'E@TG-E@L22I7-@'2.E =/0A2/'E TG-E>, #./0A2/'E@#,270T =/0A2/'E #,270T>, T2@'H#R)TR70')#./0A2/'E@.#TE** =/0A2/'E .#TE>, #./0A2/'E@07, =/0A2/'E 07,BER>, )SELE'T .E'2.E)+.,#T'H@ST#T7S@FL#<, 8#5, 8#$$roved5* FR2, #-.#-@/0A2/'E@./STR/B7T/20S@#LL + WHERE +./0A2/'E@./STR/B7T/20@/. L B./0A2/'E@./STR/B7T/20@/.*>/nvoice #$$rovedB>, #.#,270T@-#/., H.#,270T, /.'HE'I@07,BER ='HED7E 07,BER>, T2@'H#R)TR70')/.'HE'I@.#TE** =-#G,E0T .#TE> FR2, #-.#-@/0A2/'ES@#LL #, #-.#-@/0A2/'E@./STR/B7T/20S@#LL B, -2.-2@./STR/B7T/20S@#LL ', -2.-2@HE#.ERS@#LL ., -2.-2@AE0.2RS E, -2.-2@AE0.2R@S/TES@#LL F, -2.-2@L/0ES@#LL <, #-.#-@/0A2/'E@-#G,E0TS@#LL H, #-.#-@'HE'IS@#LL / WHERE #./0A2/'E@/. L B./0A2/'E@/. #0. B.-2@./STR/B7T/20@/. L '. -2@./STR/B7T/20@/. )M* #0. '.-2@HE#.ER@/. L ..-2@HE#.ER@/. )M* #0. E.AE0.2R@/. )M* L ..AE0.2R@/. #0. F.AE0.2R@S/TE@/. )M* L ..AE0.2R@S/TE@/. #0. ..-2@HE#.ER@/. L <.-2@HE#.ER@/. #0. '.-2@L/0E@/. L <.-2@L/0E@/. #0. #./0A2/'E@/. L H./0A2/'E@/. #0. H.'HE'I@/. L /.'HE'I@/. #0. F.AE0.2R@S/TE@/. L /.AE0.2R@S/TE@/. #0. '.-2@HE#.ER@/. /S 02T 07LL #0. #.-#G,E0T@ST#T7S@FL#< L 8G5 #0. ..TG-E@L22I7-@'2.E NL 8BL#0IET5C The im$ortant section 1hich covers in the 9!ery o!t$!t is as" 1. /nformation for S!$$lier

2.-!rchase 2rder details

:. Receivin /tems .etails

17

R12 Head Lines

;. /nvoice #etails

H. -ayment #etails

R12 : Setting up for AP/AR Netting #-6#R 0ettin a!tomatically com$ares -aya%les to Receiva%les and creates the a$$ro$riate transaction in each system to net s!$$lier invoices and c!stomer invoices. With this f!nctionality, # receiva%les !ser can Aie1 netted recei$t details directly from the recei$t 'reate 0ettin # reements and 0ettin Batches

With this f!nctionality, there is si nificant increase in !ser $rod!ctivity and effectiveness %eca!se of ti ht inte ration and a!tomation. Go! can access the $rocess via" 0avi ation" Recei$ts O 0ettin O 0ettin Batch 0avi ation" Recei$ts O 0ettin O 0ettin # reement Recei$ts O Recei$ts O #ction ,en! " #-6#R 0ettin #fter D!eryin a netted recei$t, the !ser can see more details a%o!t the %atch %y selectin #-6#R 0ettin from the #ction men!. This la!nches the #-6#R 0ettin %atch 1indo1. 0etted Recei$ts are created a!tomatically %y the #-6#R 0ettin $rocess and cannot %e !$dated %y the !ser from the Recei$ts Work%ench

#s 1e have seen 'ontra char in has %een re$laced %y #-6#R 0ettin , lets take a set!$ 1alk tho! h to !se this f!nctionality.

18

R12 Head Lines 1. .efine netting c ntr l acc unt )0*Set!$OFinancialsOFle( fieldOkeyOval!es 2. 'reate bank )0*Set!$O$aymentOBank and Bank Branches Go! sho!ld note, -ayment doc!ment is not re9!ired for nettin %ank acco!nt. :. <o t recei$ables res! nsibility% recei!t class de&initi n & rm )0*Set!$ORecei$tsORecei$t class D!ery the 8#-6#R 0ettin 5 recei$t class 1hich is a seeded one.

;. #ttach yo!r %ank acco!nt in this recei$t class.

19

R12 Head Lines H. <o t system !ti ns% transacti n and cust mer tabbed regi n% there enable 'All ( !ayment & )nrelated *ransacti ns+ check b ,

P. 'reate nettin a reement )0*Recei$tsO0ettin O0ettin # reement

20

R12 Head Lines Q. Enter an /nvoice in -aya%les, validate and r!n create acco!ntin . R. Enter a transaction in receiva%les. S. 'reate 0ettin Batch )0*Recei$ts O0ettin O0ettin Batch

1J. D!ery yo!r nettin %atch and see the stat!s as 'om$lete. also click on vie1 re$ort icon on ri ht side" Click n run !ush butt n% y u can see the &inal netting re! rt" 11" - t $ie(.re/uest.&ind Go! can see : conc!rrent re9!est $ro rams 'reate 0ettin %atch Settle nettin %atch 0ettin .ata E(tract

12. 0o1 g t recei!ts and /uery the AP0A1 netting recei!t" 1:. 0o1 - t * ls .$ie( Acc unting% yo! can see 0ettin control acco!nt )defined in first ste$ a* de%ited and receiva%le acco!nt credited. 1;. 0o1 o to $aya%les and 9!ery yo!r invoice n!m%er and click the ta% vie1 $ayments. Go! can see the $ayment details and co$y the doc!ment n!m%er. 1H. D!ery y ur c !ied !ayment d cument number" What yo! can see the $ayment ty$e as 0ettin . 1P. 'lick acti ns butt n and enable the check b , create acc unting" 1Q" - t t ls.$ie( acc unting "2 u can see the acc unting entry

21

R12 Head Lines 'redit 'ard f!nctionality 1ithin i3e($ense /s yo!r com$any is in $rocess of ena%lin credit card f!nctionality 1ithin 2racle /nternet E($enseB /f ans1er is yesF /t means, once the credit card f!nctionality is ena%led in i3E($ense, then its allo1s !sers to select o$en credit card transactions and incl!de them in their e($ense re$ort. The only $re3 re9!isite for yo!r or ani&ation 1o!ld make an a reement 1ith the credit card com$any to im$ort an electronic file of credit card transactions that s!mmari&es em$loyees5 e($enses for a $eriod. 2nce the electronic file is im$orted and validated, em$loyees 1o!ld %e a%le to see their credit card transactions and then select them for e($ensin on their e($ense re$ort. #,E+ )#merican E($ress* 'or$orate card is most $o$!lar one normally com$anies $rovidin there em$loyee 1ho have re9!irement to fre9!ent travel or other similar re9!irement. #merican E($ress 'or$orate Service does $rovide these services to there cor$orate c!stomer" 1. 2. :. ;. H. P. Q. R. S. IR6I-312JH 'ard mem%er Listin Re$ort IR31PJJ 'or$orate E($ress 'ash Billed .ata IR6I-31:JJ ,onthly )'yclic* # in #nalysis IR6I-31:J1 /nterim # in #nalysis IR6I-311JJ /nd!stry S!mmary IR31J22 ,onthly )'yclic* Billed Reconciliation .ata IR31J2H .aily 7n%illed Reconciliation .ata IR31JQ2 Line /tem .etail IR31JQH Line /tem .etail3.aily 7n%illed

2nce yo!r com$any is decided, to o for #,E+ 'or$orate 'ard, then Finanace /T6ER- team tries to find o!t the 1ay to do inte ration 1ithin 2racle.From the a%ove mentions list 2racle does only $rovide the direct inte ration for /tems TQ, 1hich is IR31J2H .aily !n%illed Reconciliation .ata. /tem TR, S are treated as level : data, and im$ortant to kno1 these kinds of data is not c!rrently s!$$orted in 2racle. Level : transaction data refers to the detailed transactions that constit!te a sin le transaction line on the credit card statement. For e(am$le, a sin le hotel transaction can contain the detailed transactions of room char e, meals, and room service. 0ot only #me(m there are fe1 more for 1hich 2racle does s!$$ort credit card transactions data file formats in EBS" #merican E($ress IR31J2H format )file name is 'ard .aily .ata Feed* .iner5s 'l!% Standard .ata File format )file name is TR#0S..#T* ,aster 'ard 'ommon .ata Format, version 2.J ,aster 'ard 'ommon .ata Format, version :.J Aisa A'F; format 7S Bank Aisa format Bank of #merica Aisa TS2 format

22

R12 Head Lines What is offered as a feat!re in EBS S!ite"

1. /m$ort 'redit 'ard *ransacti ns: As disc!ssed a%ove, if em$loyees in yo!r com$any
!se cor$orate credit cards, yo! can set !$ /nternet E($enses to ena%le !sers to a!tomatically im$ort credit card char es from the card iss!er into an e($ense re$ort. Em$loyees can also cate ori&e each char e as either B!siness or -ersonal and, de$endin on yo!r im$lementation, $lace items in dis$!te. Fle(i%le 'redit 'ard -ayment and Reim%!rsement Set!$" /nternet E($enses s!$$orts several different scenarios for $ayin the credit card com$any and reim%!rsin em$loyees for cor$orate credit card char es. Go! can set !$ yo!r system to indicate ho1 $ayment m!st %e remitted to the card iss!er. Go!r choices are" from yo!r or ani&ation from the em$loyee from %oth yo!r or ani&ation and the em$loyee

2.

0e(t 1ill share some set!$ activity to ena%le this f!nctionality. Three key 'E ta%les no1 as" 'E@B#0I@#''270TS for %ank acco!nts 'E@B#0I@#''T@7SES@#LL for acco!nt !ses %y 2$eratin 7nits ? Le al Entities 'E@<L@#''270TS@''/. for %ank acco!nt !se acco!ntin data

Within T'# model, here is vario!s attri%!tes ho1 they fits inside the model.

23

R12 Head Lines

R12 : Suppliers & Trading Community Architecture Earlier 1e have seen s!$$lier has %een moved into T'# model. 'om$arin to 11i version, three ne1 #- ta%les containin s!$$lier !ni9!e data %een introd!ced. They have the links to T'# ta%les"

24

R12 Head Lines

#-@S7--L/ERS #-@S7--L/ER@S/TES@#LL #-@S7--L/ER@'20T#'TS

#nd more im$ortant 1e !nderstood three old -2 Aendors ta%les o%solete, %y Aie1s $rovided for %ack1ard com$ati%ility Here is data model .This 1ill really hel$s to !nderstand 1hile desi nin inte ration 1ith EBS R12.

Hey did yo! notice there is one thin that kee$ chan in since last 2 releases Fthe %ank. We have seen there 1as once from $re 1J.( to 11i 1hen s!$$lier %ank se$arated from s!$$liers data and no1 its a ain in R12 1hen it %ecome $art of T'#.This time , %eca!se of chan in %!siness need and hi h demand of lo%al $artners 1orkin model. 0ot only yo!r com$anies is o$eratin lo%ally, yo!r $artner too o$eratin lo%al, and then 1hy not !se them. /n ty$ical

25

R12 Head Lines %!siness cost model, if cor$orate office is !sin 'iti%ank for $ayroll for 7S# o$eration then 1hy not 'iti%ank Sin a$ore %ranch is !sed for $ayroll for Sin a$ore if they are o$eratin there. So!nd %it lo1F1hy.. #s 1e a1are the key messa e of R12 1hile release 1as. Think <lo%ally 3 !sin %!siness intelli ence and analysis tools Work <lo%ally 3 !sin the lo%al ca$a%ilities of the a$$lications ,ana e <lo%ally 3 !sin the latest system architect!re and middle1are

so 1hat , think lo%ally and 1ork lo%ally is factor drivin for the chan es .This release have 1itness the reat chan es ever into the %ank model. 0o1 the %ank acco!nts is attached to yo!r le al entity level rather than 2$eratin 7nit in 1hich c!rrent and e(istin versions 2ffers. This makes %ank 1ith stron ca$a%ility to $ay across o$eratin !nits. ,ore over its im$ortant to !nderstand %anks acco!nts can %e shared %y a$$lications and can %e desi ned for !se %y -aya%les, Receiva%les and -ayroll. What is ne1 in R12 for Bank These chan es make easier and more relia%le %y Sin le access $oint Sin le Le al Entity o1nershi$ 7sa e ri hts ranted to one or more 2r ani&ations o Reconciliation o$tion defined at Bank #cco!nt level o ,ore fle(i%ility and control

Take a looks of some of the releases Release 1J.P character61J.Q 0'# to 11i Ho1 1J.( s!$$lier %anks are ma$$ed to 11i Bank 0ame $o@vendor@sites.%ank@n!m%er LO a$@%ank@%ranches.%ank@name $o@vendor@sites.%ank@n!m%er LO a$@%ank@%ranches.%ank@n!m%er Bank 0!m%er $o@vendor@sites.%ank@n!m LO a$@%ank@%ranches.%ank@n!m $o@vendor@sites.%ank@n!m LO a$@%ank@%ranches.%ank@%ranch@name Bank #cco!nt 0ame $o@vendor@sites@all.%ank@acco!nt@name LO a$@%ank@acco!nts@all.%ank@acco!nt@name Bank #cco!nt 0!m%er $o@vendor@sites@all.%ank@acco!nt@n!m LO a$@%ank@acco!nts@all.%ank@acco!nt@n!m

Release 11i These are ta%les 1hich hold the %ank details irres$ective of s!$$lier or internal %anks. a$@%ank@%ranches a$@%ank@acco!nts@all

26

R12 Head Lines 'om$arin the 11i As R12 /f 1e com$are the %ank 1ith 11i vs R12, 1e can notice the %ank 1as !tili&ed into three different $laces , finance ,$ayroll and treas!ry, 1hich re9!ires alto ether a different set!$. /t 1as one of the %i iss!es 1ith inte ration as$ect, as si nificant $ro%lem 1as reco ni&ed once the E($ense mana ement and $ayroll !ses same %ank for the res$ective $erson. There 1as a common 9!estion6conf!sion %et1een the /nte ration E(istence %et1een Bank .ata in #cco!nts -aya%le and Bank .ata /n -ayroll B #s disc!ssed a%ove , yo! kno1 most of release of 11i family of oracle #$$lication does not have inte ration %et1een HR and #- for %ank acco!nt data. We have notice in 11i there 1as f!nctionality in 1hich -aya%les in 1hich 1e 1ill create an em$loyee ty$e s!$$lier from HR data and it 1ill contain name and address info %!t not %ank information. The reason for this is that HR6-ayroll does not store the %ank information in a standard 1ay that makes the inte ration $ossi%le. So no1 r12 this 1as 1ell taken care and inte ration is %!ilt. There are $lans !nder 1ay for all %ank acco!nt data models in the vario!s $rod!cts to %e consolidated in the ne1 T'# architect!re. The 'ash ,ana ement team is 1orkin on this $ro4ect. -aya%les and HR6-ayroll are 1orkin so that the event!al idea 1ill %e that yo! can set !$ %ank acco!nts in one $lace and then indicate the !sa e )$ay, e($ense reim%!rsement, etc*. For !nderstandin it is com$arison %et1een 11i and release 12, 1here T'# comm!nity take cares of every thin s.

27

R12 Head Lines Release 12 , 1hat is ne1 than

Bank #cco!nts 1ill %e stored in a ne1 ta%le called 'E@B#0I@#''270TS and 1ill %e located at a Bank Branch. The ne1 ta%le 1hich hold the %ank information are as"

1. 'E@B#0I@#''270T"stores %ank acco!nt attri%!tes 2. 'E@B#0I@#''T@7SES@#LL " This stores the %ank acco!nt !se attri%!tes s$ecific to
2$eratin 7nit )#R, #-* and Le al Entity )Treas!ry*.

3. 'E@<L@#''270TS@''/. "The acco!ntin data $ertainin to the %ank acco!nt !se 1ill
%e stored in the ta%le. This ne1 data model allo1s the %ank and %ank %ranch entities to %e defined se$arately allo1in !sers to esta%lish a hierarchical relationshi$ %et1een them. ,issin link %et1een S!$$lier #nd S!$$lier BanksB Go! sho!ld kno1 The link %et1een -2@AE0.2RS and HE@-#RT/ES is -2@AE0.2RS.$arty@id. The link %et1een -2@AE0.2R@S/TES@#LL and HE@-#RTG@S/TES is -2@AE0.2R@S/TES@#LL.$arty@site@id. When a S!$$lier is created Record 1ill %e /nserted in HE@-#RT/ES. When the S!$$lier Site is created Record 1ill %e /nserted in HE@-#RTG@S/TES. When #ddress is created it 1ill %e stored in HE@L2'#T/20S When a %ank /s 'reated, the %ankin information 1ill %e stored in

/BG@E+T@B#0I@#''270TS /BG@E+T@B#0I@#''270TS.B#0I@id L h&@$aties.$arty@id When the Bank is assi ned to Aendors then it 1ill %e !$dated in HE@'2.E@#SS/<0,E0TS.

HE@'2.E@#SS/<0,E0TS.o1ner@ta%le@id L /BG@E+T@B#0I@#''270TS.%ranch@id. /nternal Bank #cco!nts ? S!$$lier and '!stomer Bank #cco!nts in R12

28

R12 Head Lines /nternal Bank #cco!nts /n Release 12, each internal %ank acco!nt is assi ned to a Le al Entity. #ny or all o$eratin !nits associated 1ith that le al entity are $ermitted to !se that %ank acco!nt. S!$$lier and '!stomer Bank #cco!nts /n Release 12 $rovides a centrali&ed re$ository for s!$$liers5 and c!stomers5 %ank acco!nt and credit card information. #ll data is stored in one, sec!re $lace, $rovidin shared service centers and collection de$artment5s consistent information that they need. /n 2racle s!$$lier can %e entered from three different $laces. These are the Set!$ re9!ired to $erform for a s!$$liers. S!$$lier #cco!nts Ta(es -ayments Term .ate Basis .!e .ate Basis /nvoice '!rrency Holds

/n 2racle these are the im$ortant feat!res thro! h the screen" Enter S!$$liers Enter em$loyees as S!$$liers ,er e d!$licate S!$$liers

S!$$lier .ata Entry

2ther .etails 'lassification /nformation )Si nificant for ty$e and em$loyee name* -arent s!%sidiary relationshi$ S!$$lier %ank information #$$ro$riate <L acco!nts information Record ta( information

29

R12 Head Lines

Hold conditions to s!$$lier site )rather than on individ!al invoices*

#nd these are the o$tional field Ta( $ayer /. A#T re istration n!m%er /nactive date )to $revent invoice6-2 entry after a certain date*

/m$ortant Ta%le that holds s!$$lier -2@AE0.2RS " this hold a s!$$liers information

Some im$ortant col!mns" o

SE<,E0T1 U SGSTE, <E0ER#TE. 2R ,#07#LLG E0TERE. 07,BER F2R S7--L/ER )-2@70/D7E@/.E0T/F/ER@'20TR2L* o AE0.2R@/. U SGSTE, <E0ER#TE. 70/D7E 07,BER o 'RE./T ST#T7S U<22.6-22R o 2R<#0/E#T/20@TG-E@L22I7-@'2.E o AE0.2R@TG-E@L22I7-@'2.E U AE0.2R6E,-L2GEE )E,-L2GEE@/.* o 20E@T/,E@FL#< -2@AE0.2R@S/TES@#LL " This hold corres$ondin site information 'ontains .etails of the site like F!ll #ddress6Work of site and its link 1ith vendor@id./m$ortant col!mns incl!des" o -7R'H#S/0<@S/TE@FL#<, AE0.2R@S/TE@'2.E, RFD@20LG@S/TE@FL#<, -#G@S/TE@FL#<,H2L.@#LL@-#G,E0TS@FL#<, H2L.@F7T7RE@-#G,E0TS@FL#<, H2L.@70,#T'HE.@/0A2/'ES@FL#< -2@AE0.2R@'20T#'TS " This hold s!$$lier contact information for res$ective sites.

Ho1 they connected These are ty$ically connected as"

Take a note Se ment1 is holdin s!$$liers 0!m%er. D!ick 9!ery for ne1 %a%ies

30

R12 Head Lines select K from $o@vendors 1here se ment1 L 81JJ18C select K from $o@vendor@sites $vs, $o@vendors $ov 1here $ov.se ment1 L 81JJ1V and $ov.vendor@id L $vs.vendor@idC select K from $o@vendor@contacts $vc, $o@vendor@sites $vs, $o@vendors $ov 1here $ov.se ment1 L 81JJ1V and $ov.vendor@id L $vs.vendor@id and $vs.AE0.2R@S/TE@/. L $vc.vendor@site@idC S!$$lier /nterface Ges, that 1as one of the enhancement in oracle 11.H.1J release. -rior to that version, there 1as no interface or -!%lic e(ist for s!$$lliers, th!s it 1as a tricky to handle s!$$lier. #s 1e have disc!ssed a%ove of #- availa%ility . /f yo! are havin 11.H.1JM version, and if yo! have re9!irement to create s!$$lier from yo!r le acy data than !se S!$$lier /nterface, life 1ill %e easier. What do yo! say. Ho1 1e start This consists in 2 ste$s $rocess" Ste$ 1: -o$!late the ne1 interface ta%les 1ith data. This can %e done via SDLKLoader or ty$ically !sed to load data in a ta%le. #-@S7--L/ERS@/0T #-@S7--L/ER@S/TES@/0T #-@S7-@S/TE@'20T#'T@/0T

Ste$ 2"R!n the S!$$lier 2$en /nterface Re9!est Set )F0.RSS7B1QJ:* #lternatively, r!n the individ!al im$ort $ro rams to load one ta%le at a time S!$$lier 2$en /nterface /m$ort )#-+S7/,-* S!$$lier Sites 2$en /nterface /m$ort )#-+SS/,-* S!$$lier Site 'ontacts 2$en /nterface /m$ort )#-+S'/,-*

Some im$ortant notes for s!$$liers /nterface When yo! load the data it sho!ld %e 80EW5 initially. #fter the S!$$lier Sites 2$en /nterface is r!n the stat!s ets chan ed to -R2'ESSE.56WREXE'TE.5.

31

R12 Head Lines The entire flo1 can %e sho1n as"

# 0ote 1ith R12 for S!$$liers #s 1e kno1 in R12 S!$$lier is $art of T'# , th!s the link %et1een -2@AE0.2RS and HE@-#RT/ES is -2@AE0.2RS.$arty@id. The link %et1een -2@AE0.2R@S/TES@#LL and HE@-#RTG@S/TES is -2@AE0.2R@S/TES@#LL.$arty@site@id. When a S!$$lier is created Record 1ill %e /nserted in HE@-#RT/ES. When the S!$$lier Site is created Record 1ill %e /nserted in HE@-#RTG@S/TES. When #ddress is created it 1ill %e stored in HE@L2'#T/20S. .o yo! kno1, there are many defa!lt val!e 1hich can %e controlled at set !$ level. Here is the e($lanation %ased o!t of close microsco$ic vie1 of defa!lt val!es of #cco!nt -aya%le.

32

R12 Head Lines

33

R12 Head Lines .o 1e have any <eneral Set!$ Hierarchy for .efa!lt val!esBBB Ges , 1e have a <eneral Set!$ Hierarchy for .efa!lt val!es, 1hich can %e ty$ically descri%ed as"

D!ick To!r for #cco!nt -aya%le #- takes care of all $ayments in 2racle #$$lications. This mod!le has active interaction 1ith -!rchasin and <eneral Led er mod!les. The different f!nctionality of the -aya%les mod!le are" Set !$ S!$$lier. Enter, revie1 and #$$rove invoices. -ay invoices and reconcile $ayments to %ank a6c. Enter and a$$ly $re3$ayments. 'reate 4o!rnal entries for $ostin to <L.

#n to$ level overvie1 of the mod!le can %e iven as "

1.Enter S!$$liers This ste$ consist of set !$ as 1ell as maintenance of e(istin one..!rin the set!$, 1e need to do set!$ for S!$$lier #cco!nts Ta(es -ayments Term .ate Basis .!e .ate Basis /nvoice '!rrency Holds

34

R12 Head Lines /m$ortantly the other feat!res in this area consist is " Enter em$loyees as S!$$liers " this is for mana in and controllin E($ense re$ort ,er e d!$licate S!$$liers

2./nvoices This consist Set!$ forC .istri%!tion Set Ta( Set!$ tolerance, matchin o$tions

:. #$$rove invoice This re9!ired set !$ for r!le, so that a$$roval and validation $rocess can validate %ased on some $arameter. ;.-ayments This re9!ires set !$ for $ayment related de$endency 1hich incl!de C Format Bank Bank acco!nt B!ild $ro ram -ayment ,ethods o ,an!al o D!ick 'heck o #!tomatic 'heck

Take a note in man!al and D!ick check, yo! have to sim$ly enter $ayment details and correlate to invoices. #!tomatic check is a$$lica%le for %atch $ayments. H. 'reate Xo!rnal entries Ty$ical flo1 for creatin Xo!rnal entries is s!mmari&ed as"

35

R12 Head Lines

#nd here is final note of acco!ntin Entries of #- " .!rin /nvoicin o E($enses #6' .r to vendor lia%ility .!rin -ayment o Aendor lia%ility #6' .r to 'ash6Bank #6'

F#nd, This is Fo!r R!le of -aya%les Go! m!st have a vendor to do anythin Every /nvoice m!st %e f!lly 'har ed o!t %efore $aid or $ostin to <L. #ll -ayments m!st have an invoice Every /nvoice m!st r!n thro! h a$$roval $rocess.

Ho$e this is a %rief overvie1 of the -aya%le %!siness flo1, 1ill disc!ss ? share some more in ne(t co!$le of $ost.Till then kee$ 1atchin this s$ace.

='ontra 'har in > to =R12 #-6#R 0ettin >"

1. '!stomer #B' raise an order to yo!r com$any and yo!r have made shi$ment of oods they have re9!ested and yo! have raised an invoice of + amo!nt, that yo! are e($ectin the money sho!ld %e $aid %y c!stomer. 2. Same time , yo! have some taken some services to the same c!stomer 1hich is a vendor in yo!r -aya%le, and no1 yo! have lia%ility to $ay the amo!nt G, yo! received a ainst -2. What the %!siness demand here is =0et off yo!r s!$$lier %alance in #- )-aya%les* 1ith c!stomer %alance in #R )Receiva%les*>

36

R12 Head Lines These kinds of %!siness scenario al1ays e(ist, s$ecially if yo! are dealin 1ith client 1hose line of %!siness is either #irlines or 'ar o or Healthcare domain. S!ch events are al1ays there, therefore desi nin , confi !rin and identifyin s!ch need is foremost im$ortant ste$ 1hile im$lementin ER-. What 1e seen after 11.H.S , 1here similar kind of f!nctionality 2racle has offered in term of ='ontra 'har in > 1hich initially limited in E!ro$ean Locali&ation and on and after 11.H.1J, the same f!nctionality have %een standardi&e and incor$orated in the $rod!ct. 'ontra 'har in 'ontra 'har in allo1s yo! to select c!stomer and s!$$liers thro! h the screen and net their %alances. This 1ill s!%mit t1o re9!ests !sed to $o$!late the Receiva%les and -aya%les Transaction /nterface. This credit memos can then %e im$orted thro! h the standard invoice im$ort in #R and #-.The %ase F!nctionality that c!rrently e(ist in 11.H.1J are" 7se the 'ontra 'har in 1indo1 to $hysically match the c!stomer to the s!$$lier and allocate an amo!nt for contra char in #!tomatically $o$!late the #R and #- /nvoice /nterface ta%les to create credit memos for the so!rce 'ontra /m$ort the invoices o in #R 1ith the S!%mit /nvoice /m$ort 1indo1, !sin the so!rce 'ontra o in #- 1ith the #!to /nvoice /m$ort -ro ram on the R!n #!to /nvoice 1indo1, !sin the so!rce 'ontra 7se the standard f!nctionality to $ost the im$orted credit memos to 2racle <eneral Led er 7se the 'ontra 0ettin Re$ort o to re$ort on the netted contra char in transactions o to check that the contra char in has %een carried o!t s!ccessf!lly in 2racle Receiva%les and 2racle -aya%les

Ho1 to make 'ontra 'har in Feat!re ena%led Follo1 the %elo1 mentioned ste$s and yo! sho!ld %e a%le to !se the contra char in f!nctionality. 1..efine doc!ment se9!ences, assi n the doc!ment se9!ence to 'ontra doc!ment cate ory. Go! can assi n a !ni9!e doc!ment se9!ence to each invoice and $ayment doc!ment in yo!r -aya%les system so yo! have a !ni9!e identifier for each doc!ment. # doc!ment cate ory is a set of doc!ments )invoices or $ayments* that share similar characteristics. Go! can assi n a sin le doc!ment se9!ence to one or more doc!ment cate ories. 7se assi nment 1indo1 in System administrator res$onsi%ility to attach the doc!ment cate ory 1ith the doc!ment se9!ence created for contra char in invoices.

2. Set!$ -aya%les 'ontra So!rce. # look!$ is any $redefined val!e that 1as not defined in a set!$ 1indo1.

37

R12 Head Lines :. Set!$ !ser $rofile for #- Res$onsi%ility, incl!din the follo1in " Ta(" #llo1 2verride of Ta( 'ode )Ges* Ta(" #llo1 2verride of '!stomer E(em$tion )Ges* Se9!ential 0!m%erin )-artially 7sed* X<" 'ontra 3 /ncl!de F!t!re .ated -ayment in S!$$lier Balance )Ges*

;..efine .oc!ment 'ate ory called 8'ontra5. H. .efine -aya%les Look!$ for 8'ontra5. # look!$ is any $redefined val!e that 1as not defined in a set!$ 1indo1. 7se the 2racle -aya%les Look!$s 1indo1 to revie1 and maintain sets of val!es, or look!$s, that yo! !se in -aya%les. 7se the 2racle -aya%les Look!$s 1indo1 to create a ne1 -aya%les look!$ for contra char in . This 0e1 'ontra Look!$ 'ode 1ill %e !sed as a so!rce 1hen the 'ontra 'har in 'redit memos are created. P. #ssi n a 8'ontra 'har in 5 ,en! to 8#-@0#A/<#TE@<7/12V main men!,1hich tied to #Res$onsi%ility. To attach the 'ontra 'har in Form to the E(istin -aya%les Res$onsi%ility, attach X<@'20TR#@'H#R<E@<7/ S!% ,en! to #-@0#A/<#TE@<7/12 ,ain ,en!. 0avi ation -ath" System #dministrator res$onsi%ility" #$$lication" ,en! Form Q. Havin created the ne1 form 8'ontra 'har in 5, enter 'ontra 'har in Transactions, then 8S!%mit 'ontra transaction. What5s ne1 in Release 12 When a tradin $artner is %oth a c!stomer and a s!$$lier, an a reement may %e made to offset o$en receiva%les5 a ainst o$en $aya%les5 items. 0ettin # reements add tradin $artner terms as 1ell as de$loyin com$any controls. # selection $ro ram a!tomatically $!lls information from 2racle Receiva%les and 2racle -aya%les takin into consideration disco!nts, late fees, and 1ithholdin ta(es $rior to determinin the final nettin amo!nt. # revie1 $rocess and tradin $artner a$$roval afford f!rther verification to s!$$ort the nettin event. The matchin of o$en receiva%les and o$en $aya%les is a!tomated. Go! are no1 a%le to determine 1hether yo! or yo!r tradin $artner has a reater %alance o!tstandin and !$date yo!r %ooks, collect $ayments or make $ayments accordin ly.

38

R12 Head Lines

Benefits" #-6#R 0ettin $rovides for the a%ility to =collect> on yo!r receiva%les %alances 1ith the amo!nt o1ed for yo!r $!rchases %y offsettin one a ainst the other.This 1ill Red!ce %ank 'har es , Fe1er Transactions to -rocess and th!s si nificant 'ash flo1 /m$rovement. From 11i to R12 R12 0ettin sol!tion re$laces : sol!tions)FA,XE,/</* in 11i. /n R12 the 'ontra 'har e f!nctionality has %een o$timi&ed and therefore chan ed into the #-6#R 0ettin f!nctionality. /n the -aya%les mod!le as 1ell as the Receiva%les mod!le, there is a 0ettin s!%men!. S! -aya%les" -ayments 3O Entry 3O 0ettin Receiva%les" Recei$ts 3O 0ettin

ested Readin 2racle Financials 'ommon 'o!ntry Feat!res !ser !ide.

39

R12 Head Lines

<eneral Led er: 0e1 Feat!res like " Eliminate #cco!ntin Errors %y $rovidin #lternate #cco!nts Re$lace .isa%led #cco!nts, /ntrod!ction for .efinition #ccess Sets, /ntrod!cin Led er Sets in $lace of S2B Read for ,ore" R12 3 2racle <eneral Led er 3 0e1 and enhanced feat!res"

Here are some of the ne1 feat!res of <eneral Led er in R12. #cco!ntin Set!$ ,ana er The led er is a %asic conce$t in Release 12. The led er re$laces the 11i conce$t of a set of %ooks. /t re$resents an acco!ntin re$resentation for one or more le al entities or for a %!siness need s!ch as consolidation or mana ement re$ortin . 'om$anies can no1 clearly and efficiently model its le al entities and their acco!ntin re$resentations in Release 12. This seems to %e a ma4or area in ettin s!ccess of the shared service center and sin le instance initiatives 1here many or all le al entities of an enter$rise are acco!nted for in a sin le instance, and data, set!$, and $rocessin m!st %e effectively sec!red %!t also $ossi%ly shared. 0o1, le al Entities can %e ma$$ed to entire Led ers or if yo! acco!nt for more than one le al entity 1ithin a led er, yo! can ma$ a le al entity to %alancin se ments 1ithin a led er. While a set of %ooks is defined %y : '5s, 1. chart of acco!nts 2. f!nctional c!rrency :. acco!ntin calendar, The addition in this list the led er is defined %y a ;th '" the acco!ntin method, This ;th ' allo1s yo! to assi n and mana e a s$ecific acco!ntin method for each led er. Therefore, 1hen a le al entity is s!%4ect to m!lti$le re$ortin re9!irements, se$arate led ers can %e !sed to record the acco!ntin information. #cco!ntin Set!$ ,ana er is a ne1 feat!re that allo1s yo! to set !$ yo!r common financial set!$ com$onents from a central location. What is #cco!ntin Set!$ ,ana er #cco!ntin Set!$ ,ana er is a ne1 feat!re that streamlines the set!$ and im$lementation of 2racle Financial #$$lications. The #cco!ntin Set!$ ,ana er 1ill facilitate the set!$ re9!ired for sim!ltaneo!s acco!ntin for m!lti$le re$ortin re9!irements.

40

R12 Head Lines With the #cco!ntin Set!$ ,ana er, yo! can $erform and maintain the follo1in common set!$ com$onents from a central location" Le al Entities Led ers, $rimary and secondary 2$eratin 7nits, 1hich are assi ned to $rimary led ers Re$ortin '!rrencies, 1hich is an enhanced feat!re S!%led er #cco!ntin 2$tions. This is 1here yo! define the acco!ntin methods for each le al entity s!%led er transaction and associate them to the led er 1here the acco!ntin 1ill %e stored. /ntercom$any #cco!nts and Balancin R!les #cco!ntin and Re$ortin Se9!encin Both /ntercom$any and Se9!encin

Here are the some more details a%o!t s!%led ers S!%led er #cco!ntin )SL#* #s disc!ssed in co!$le of earlier $ost <L is inte rated 1ith SL# to ena%le a !nified $rocess to acco!nt for s!%led er transactions and $ost data to <L, and to $rovide a consistent vie1 1hen drillin do1n from <L to s!%led er transactions.

Enhanced Forei n '!rrency -rocessin %y Re$ortin ,ade easy <L has added ne1 feat!res and enhanced e(istin feat!res to s!$$ort forei n c!rrency $rocessin , they are mainly as" /n R12, ,R' feat!re is enhanced 1ith a feat!re call Re$ortin '!rrencies. That mean it 1ill no1 s!$$ort m!lti$le c!rrency re$resentations of data from any so!rce, incl!din e(ternal systems, 2racle or non32racle s!%led ers, and 2racle <eneral Led er 4o!rnals and %alances. The second one is in re$ortin to vie1 %alances vie1 %alances that 1ere entered in yo!r led er c!rrency se$arate from those %alances that 1ere entered and converted to the led er c!rrency.The chan e in R12 is that %alances entered in the led er c!rrency are maintained se$arately from %alances converted to the led er c!rrency for !se in Re$ortin and #nalysis.

41

R12 Head Lines

Here5s an e(am$le. #ss!me 1e have a led er and the led er c!rrency is 7S.. / enter and $ost t1o 4o!rnalsC one in 1,JJJ 7S .ollars, and another in HJJ British -o!nds that ets converted to 12JJ 7S .ollars. /n Release 11i, / can revie1 the HJJ <B- and the 12JJ 7S. that res!lts from convertin the HJJ <B-, and the total 22JJ 7S. 1hich is the 7S. %alance in the 'ash #cco!nt. The Y22JJ is the s!m of the Y1JJJ entered in 7S. and the Y12JJ converted from the HJJ British -o!nds. Ho1ever, / vie1 that a 1JJJ 7S. 1ere entered directly in 7S.. /n Release 12, / can vie1 the 1JJJ 7S. %y $erformin an acco!nt in9!iry on the 'ash acco!nt for %alances entered only in the led er c!rrency. The amo!nts entered in forei n c!rrencies that 1ere converted to the led er c!rrency 1ill not %e incl!ded in the %alance. 2f co!rse, if / 1ant to retrieve all %alances in 7S., %oth the entered as 1ell and the converted, / can still do that in Release 12.

'reatin forei n c!rrency rec!rrin 4o!rnals /n Release 11i, yo! co!ld define rec!rrin 4o!rnals !sin the f!nctional c!rrency or ST#T c!rrency. 0o1 in Release 12, yo! can create rec!rrin 4o!rnals !sin forei n c!rrencies. This is $artic!larly !sef!l if yo! need to create forei n c!rrency 4o!rnals that are rec!rrin in nat!re. For e(am$le, ass!me a s!%sidiary that !ses a different c!rrency from its $arent %orro1s money from the $arent. The s!%sidiary can no1 enerate a rec!rrin entry to record monthly interest $aya%le to the $arent com$any in the $arent5s c!rrency. .ata #ccess to ,!lti$le Le al Entities and Led ers Go! no lon er have to constantly s1itch res$onsi%ilities in order to access the data in a different led er. Go! can access m!lti$le led ers from a sin le res$onsi%ility as lon as all led ers share the same chart of acco!nts and calendar. Sim!ltaneo!s 2$enin and 'losin of -eriods for ,!lti$le Led ers

42

R12 Head Lines Go! no lon er have to o$en and close $eriods for each led er se$arately. Go! can no1 o$en and close $eriods across m!lti$le led ers sim!ltaneo!sly %y s!%mittin 2$en and 'lose -eriods $ro rams from the S!%mit Re9!est form. Sim!ltaneo!s '!rrency Translation of ,!lti$le Led ers Go! can r!n the Translation $ro ram for m!lti$le led ers sim!ltaneo!sly, if yo! are mana in m!lti$le led ers. Financial Re$ortin for ,!lti$le Led ers 0o1 1ith this feat!re yo! can r!n Financial Statement <enerator )FS<* re$orts for m!lti$le led ers sim!ltaneo!sly. This is !sef!l if yo! mana e m!lti$le led ers and 1ant to r!n a %alance sheet or income statement re$ort for all of yo!r led ers at the same time. 'ross3Led er and Forei n '!rrency #llocations Go! are a%le to allocate financial data from one or more led ers to a different tar et led er. This ena%les yo! to $erform cross3led er allocations, 1hich is !sef!l for $!r$oses s!ch as allocatin cor$orate or re ional e($enses to local s!%sidiaries 1hen each entity has its o1n led er Streamlined #!tomatic -ostin Go! can no1 share #!to-ost 'riteria sets across m!lti$le led ers that share the same chart of acco!nts and calendar and !se the #!to-ost 'riteria sets to $ost 4o!rnals across m!lti$le led ers sim!ltaneo!sly. Streamlined #!toReversal 'riteria Set!$ /nte rated We%3%ased #!toReversal 'riteria Sets can also %e shared across led ers to reverse 4o!rnals across m!lti$le led ers. This is enhanced %y inte rated We%3%ased S$readsheet /nterface. Xo!rnal 'o$y 0o1 1e can no1 co$y entire 4o!rnal %atches. Go! can co$y 4o!rnal %atches 1ith any stat!s. The system 1ill create a ne1 4o!rnal %atch containin the same 4o!rnal entries.Go! may also chan e the %atch name, $eriod, and6or effective date 1hile co$yin the 4o!rnal %atch. #fter co$yin the 4o!rnal %atch, yo! may modify the !n$osted 4o!rnals in the same manner as any man!ally created 4o!rnals. Streamlined 'onsolidation ,a$$in s Go! are a%le to define 'hart of #cco!nts ,a$$in s )formerly kno1n as 'onsolidation ,a$$in s* %et1een t1o charts of acco!nts. Therefore, if yo! have m!lti$le 'onsolidation .efinitions for $arent and s!%sidiary led ers that share the same chart of acco!nts $air, and their ma$$in r!les are the same, yo! only have to define a sin le 'hart of #cco!nts ,a$$in . The enhancement in R12 allo1s yo! to define ma$$in s %et1een charts of acco!nts instead of %et1een sets of %ooks, so that they can %e shared across m!lti$le 'onsolidation .efinitions.

43

R12 Head Lines Therefore, if yo! have m!lti$le 'onsolidation .efinitions for $arent and s!%sidiary led ers that share the same chart of acco!nts $air, and their ma$$in r!les are the same, yo! only have to define a sin le 'hart of #cco!nts ,a$$in . Go! can also sec!re access to chart of acco!nts ma$$in s !sin definition access set sec!rity. This allo1s yo! to sec!re 1hich !sers can vie1, modify, and6or !se chart of acco!nt ma$$in s in consolidation definitions. Re$lacement for .isa%led #cco!nts 0ormally 1hen an acco!nt is disa%led, yo! can $revent transactions that incl!de the acco!nt from errorin d!rin 4o!rnal im$ort %y definin a re$lacement acco!nt for the disa%led acco!nt. Xo!rnal im$ort re$laces the disa%led acco!nt 1ith the re$lacement acco!nt and contin!e the 4o!rnal im$ort $rocess if the re$lacement acco!nt is valid. This im$roves $rocessin efficiency %y $reventin the 4o!rnal im$ort $rocess from errorin and ena%lin the s!ccessf!l creation of the 4o!rnal 1ith minimal !ser intervention 1hen an acco!nt has %een disa%led. .ata #ccess Sec!rity for Le al Entities and Led ers /n R12, since yo! can access m!lti$le le al entities and led ers 1hen yo! lo into 2racle <eneral Led er !sin a sin le res$onsi%ility, 2racle <eneral Led er $rovides yo! 1ith fle(i%le 1ays to sec!re yo!r data %y le al entity, led er, or even %alancin se ment val!es or mana ement se ment val!es. Go! are a%le to control 1hether a !ser can only vie1 data, or 1hether they can also enter and modify data for a le al entity, led er, %alancin se ment val!e or mana ement se ment val!e. ,ana ement Re$ortin and Sec!rity This can %e %est !nderstood as"Go! can desi nate any se ment )e(ce$t the nat!ral acco!nt se ment* of yo!r chart of acco!nts to %e yo!r mana ement se ment and !se 2racle <L sec!rity model to sec!re the mana ement se ment for re$ortin and entry of mana ement ad4!stments. -revent Reversal of Xo!rnals 1ith Fro&en So!rces Go! can no lon er reverse 4o!rnals from fro&en so!rces defined in the 4o!rnal so!rces form. /f the 4o!rnal is created from a fro&en so!rce, the 4o!rnal cannot %e modified even if the so!rce is s!%se9!ently !nfro&en in the f!t!re. This $rovides streamlined data reconciliation 1ith s!%systems. 0ot %ein a%le to reverse 4o!rnals that ori inated in s!%led ers 1ill ens!re that the acco!nt %alances 1ill al1ays tie o!t 1ith <eneral Led er. /f yo! need to reverse a s!%led er 4o!rnal, then yo! sho!ld do so in S!%led er #cco!ntin or the s!%led er a$$lication. -revent Reversal of 7n$osted Xo!rnals Go! also can no lon er reverse !n$osted 4o!rnals. This ens!res data inte rity and %etter a!dita%ility. /n the $ast 1hen 1e allo1ed yo! to reverse !n$osted 4o!rnals, there 1as a risk that the ori inal 4o!rnal co!ld %e deleted so yo! co!ld end !$ reversin somethin that didn5t e(ist. 0o1, all reversals can %e tied %ack to the ori inal $osted 4o!rnal.

44

R12 Head Lines /nte rated We%3%ased S$readsheet /nterface Thro! h the inte ration 1ith We% #./, !sers can no1 levera e s$readsheet f!nctionality in 2racle <eneral Led er via a 1e%3%ased interface. The s$readsheet interface can %e conveniently la!nched from a <L res$onsi%ility. 7sin the Xo!rnal Wi&ard, 1e can levera e s$readsheet f!nctionality to create act!al, %!d et, or enc!m%rance 4o!rnals. Go! can take advanta e of s$readsheet data entry shortc!ts s!ch as co$yin and $astin or dra in and dro$$in ran es of cells, or even !sin form!las to calc!late 4o!rnal line amo!nts. Go! can then !$load yo!r 4o!rnals to 2racle <eneral Led er. Before !$loadin , yo! can save and distri%!te yo!r 4o!rnal 1orksheets for a$$roval. We can also im$ort data from te(t files into s$readsheets, 1here it can %e f!rther modified %efore !$loadin to 2racle. This f!nctionality is !sef!l 1hen mi ratin data from le acy systems, or from any so!rce that can $rod!ce delimited files. 7sin the B!d et Wi&ard, yo! can do1nload %!d et amo!nts to a s$readsheet, modify the amo!nts, and then !$load them %ack. Go! can also choose to do1nload the act!al amo!nts to com$are it 1ith the %!d et amo!nt. B!d et Wi&ard also allo1s yo! to $lot ra$hs and do a ra$hical com$arison on the amo!nts. B!d et Wi&ard also $rovides %!d et notes. Go! can add descri$tions to acco!nts and amo!nts in yo!r %!d et and e($lain yo!r %!d et 1ithin the %!d et 1orksheet, avoidin the cl!tter of e(ternal doc!mentation. 'ontrol #cco!nts Go! are a%le to control data entry to an acco!nt %y ens!rin it only contains data from a s$ecified 4o!rnal so!rce and to $revent !sers from enterin data for the acco!nt either in other 4o!rnal so!rces or man!ally 1ithin eneral led er. Sec!rity for .efinitions Go! can sec!re yo!r set!$ and definitions %y rantin s$ecific $rivile es to !sers to vie1, modify, and6or e(ec!te a definition. This ena%les yo! to control 1hich of yo!r !sers can vie1 a definition, %!t not modify or e(ec!te it, or e(ec!te a definition 1itho!t modifyin it, or vice versa. Follo1in is a list of definitions that have this sec!rity availa%le for" 1. 2. :. ;. H. P. Q. R. S. 1J. 11. 12. 1:. 1;. ,ass#llocation and ,assB!d et Form!las FS< Re$orts and 'om$onents #cco!ntin 'alendars Transaction 'alendars #!to-ost 'riteria Sets #!oReversal 'riteria Sets B!d et 2r ani&ations 'hart of #cco!nts ,a$$in s 'onsolidation .efinitions 'onsolidation Sets Elimination Sets Led er Sets Rec!rrin Xo!rnals and B!d et Form!las Rate Ty$es

45

R12 Head Lines 1H. Reval!ations Se9!ence for Re$ortin ,aintainin t1o se9!nces have %een introd!ced, acco!ntin and re$ortin se9!encin . For more details on Xo!rnal Line Reconciliation: Xo!rnal Line Reconciliation ena%les yo! to reconcile 4o!rnal lines that sho!ld net to &ero, s!ch as s!s$ense acco!nts, or $ayroll and ta( $aya%le acco!nts for co!ntries, s!ch as 0or1ay, <ermany, or France. /n R12, 1e5ve made many im$rovements to intercom$any acco!ntin . R11i5s <lo%al /ntercom$any System )</S* has %een re$laced 1ith an e(citin ne1 $rod!ct called #dvanced <lo%al /ntercom$any System )#</S*. We also e(tended intercom$any %alancin s!$$ort to incl!de enc!m%rance 4o!rnals. Enhanced /ntercom$any Some of the <L Standard Re$orts converted into +,L -!%lisher 2racle <eneral Led er5s #cco!nt #nalysis, <eneral Xo!rnals and Trial Balance standard re$orts are no1 inte rated 1ith +,L -!%lisher.

R12 " Se9!ence in <L made Le al 'om$liance Easy"

/n R12, to cater the need for le al com$liance some other co!nties like #sia, Latin #merica, and E!ro$e ,t1o Xo!rnal Se9!encin o$tions have %een $rovided. These are acco!ntin and re$ortin se9!ence, in reality there is %it difference in these t1o terms. #cco!ntin Se9!ence This is se9!ence !sed in <L 4o!rnals 1hen $osted in <L ,Se9!ence s!%led er 4o!rnals 1hen com$leted in S!%led er #cco!ntin . What 1e have seen in Release 11i, 1e had doc!ment se9!encin that se9!entially n!m%ered doc!ments !$on creation. #cco!ntin Se9!encin 1ill a!tomatically assi n a se9!ence n!m%er to <L 4o!rnal entries that are $osted in <L. There5s also an o$tion to se9!ence s!%led er 4o!rnals 1hen they are com$leted in SL# #cco!ntin . Re$ortin Se9!ence This se9!ence is !sed in <L Xo!rnals 1hen yo! close a <L -eriod.Se9!ence s!% led er Xo!rnals 1hen yo! com$lete the acco!ntin in SL# .This is one of re$lacement of #cco!ntin En ine )#+* le al se9!encin and /talian Xo!rnal Book commonly kno1n Li%ro <iornale. These t1o Se9!ences can %e assi n m!t!ally e(cl!sive se9!ences %ased on" Led ers or Re$ortin '!rrencies Xo!rnal so!rces

46

R12 Head Lines

Xo!rnal cate ories Balance ty$es

The %enefit of !sin these se9!nces are s!mmari&ed " a* Le al 'om$liance made easy" The one %i est advanta e of it 1ill no1 addresses %!siness re9!irements in many co!ntries, s!ch as E!ro$e ? #sia. Therefore its allo1s fiscal a!thorities to verify the com$leteness of a com$any5s acco!ntin records. %*Fle(i%ility et enhanced"With this it $rovides reater fle(i%ility in choosin different 4o!rnal se9!encin o$tions, as mention a%ove, these can %e %ased o!t of these different criteria, s!ch as %y led ers, re$ortin c!rrencies, 4o!rnal so!rces, 4o!rnal cate ories, and %alance ty$es. c*0o Locali&ation Re9!ired" Someho1 related to )a* disc!ssed a%ove, earlier it the local re$ortin need 1as catered %y locali&ation , 1hich no1 is $art of <L activity. Where to .efine the the se9!ence. Go! can define the acco!ntin se9!ence in the conte(t of a led er in #cco!ntin Set!$ ,ana er.There is another 1ay ie #cco!ntin Se9!encin men! f!nction 1hich 1e can create and mana e o!r se9!encin r!les.

47

R12 Head Lines

For #cco!ntin Se9!ences 1hich is internally a $ostin event, the <L 4o!rnals are se9!enced 1hen they are $osted in <L and S!%led er 4o!rnals are se9!enced 1hen com$leted in SL#. For Re$ortin Se9!ences )$eriod close event*, <L 4o!rnals and s!%led er 4o!rnals are se9!enced 1hen a <L $eriod is closed.Go! can see %oth can %e a$$ear in the Xo!rnal screen as %elo1.

48

R12 Head Lines

R12 Led er: Read for more details R12 3 2racle <eneral Led er 3 0e1 and enhanced feat!res

S!%led er #cco!ntin R!le %ased acco!ntin en ine, toolset ? re$ository s!$$ortin #LL 2racle E3B!siness S!ite mod!les. Read for ,ore details" R12 SL#" From -rod!ct #cco!ntin to S!%led er #cco!ntin

,ost of !s are 1ell a1are that in Release 12 of 2racle #$$lications, S!%led er #cco!ntin )SL#* has %een introd!ced, 1hich is a R!le3%ased acco!ntin en ine, toolset ? re$ository 1hich is s!$$ortin most of 2racle %!siness S!ite mod!les. #s 1e kno1 driver for introd!ction this is to have an o$tion of allo1in m!lti$le acco!ntin re$resentations for a sin le %!siness event, resolvin conflicts %et1een cor$orate and local fiscal acco!ntin re9!irements. The

49

R12 Head Lines F!nctionality is someho1 very similar to <lo%al acco!ntin en ine, 1hich oracle does offer for E!ro$ean re$ortin 0eed. So What is S!%led er #cco!ntin B Z SL# is an intermediate ste$ %et1een s!%led er $rod!cts and the 2racle <eneral Led er Z Xo!rnal entries are created in S!%led er #cco!ntin and then transferred to 2racle <eneral Led er Z Each s!%led er transaction that re9!ires acco!ntin is re$resented %y a com$lete and %alanced s!%led er 4o!rnal entry stored in a common data model /s this ,od!le or 1hatB /t is ood to kno1 ,s!% led er #cco!ntin is a Service, not an #$$lication . The hi h $oints of SL# 1o!ld %e" There are no SL# res$onsi%ilities 7sers do not lo in to SL# SL# is a service $rovided to 2racle #$$lications SL# forms and $ro rams are em%edded 1ithin standard 2racle #$$lication res$onsi%ilities SL# $rovides the follo1in services to 2racle #$$lications <eneration and stora e of detailed acco!ntin entries Stora e of s!%led er %alances )e. . third $arty control acco!nt %alances* S!%led er acco!ntin entries S!%led er re$ortin )e. . S!%led er 4o!rnal re$orts, o$en acco!nt %alances listin *

What oracle a$$lication ,od!le takin services for SL#B ,ost of mod!les 1hich need acco!ntin entry 1ith finance !ses service of SL# ,od!les. This ne1 -rod!ct has these many ne1 f!nctionality s!ch as" Xo!rnal Entry Set!$ and se9!encin .ate Effective #$$lication acco!ntin .efinitions ,!lti$le #cco!ntin Re$resentation ,!lti3$eriod #cco!ntin S!mmari&ation 2$tions .raft and online acco!ntin Re$lacement for disa%led acco!nts -rocess cate ory #cco!ntin Transaction acco!nt B!ilder #ccr!al Reversal #cco!ntin #cco!nted and <ain6Loss #mo!nt calc!lations #$$lication #cco!ntin .efinition Loader Enhanced Re$ortin '!rrency F!nctionality

The overall advanta e of SL# can %e s!mmari&ed %y oracle as %elo1"

50

R12 Head Lines

<L Flo1 1ith S!%led er3Level Secondary Led er Lets take a case , 1ith a scenario 1ith %asic Finance mod!le, yo! can find ho1 ti htly acco!ntin model is se$arated 1ith transaction model in release 12.

51

R12 Head Lines

This is the ty$ical flo1 1ithin one $rod!ct 1ith SL# can %e %est descri%ed as"

52

R12 Head Lines

R12 SL#" #naly&in S!%led er #cco!ntin

#s 1e disc!ssedt s!%led er acco!ntin 1e !nderstood 1ith this ne1 feat!re" #ll acco!ntin $erformed %efore transfer to the <L. and this is achieved %y !ser set!$ 1ho can do %y defina%le acco!ntin r!les.

#t the data level, it5s a %i chan e for all the s!%led ers, tho! h there is a first eneration chan es 1e have noticed sometime 1hen 11i -aya%les 1here conce$t of =#cco!ntin Events > introd!ced first time and acco!ntin $erformed at s!%led er level first %efore movin into <L. The same idea has %een incor$orated in ne1 s!% led er acco!ntin model , indeed a 1as a real need %eca!se of some !neven f!nctionality likes" /nconsistencies in #cco!ntin <eneration like S!mmary vs. .etail .irect to <eneral Led er vs. 2$en /nterface /nconsistent .rilldo1n from <eneral Led er #lso it has %een seen inconsistent ,echanisms for controllin #cco!ntin as certain o$tions has %een !sed in e(istin version" o fle( %!ilder o #cco!nt <enerator o #!tomatic 2ffsets

What is s!% led er mean for a non finance $ersonB # ne1 transactional a$$lication that enerates acco!ntin im$act 7sed to store detailed information not needed for a eneral led er S!% led ers $ost s!mmari&ed activity to a eneral led er $eriodically to maintain centrali&ed acco!nt %alances for the com$any

With these acco!ntin at this level the res$ective s!% led ers ? <eneral Led er is tied o!t, as %elo1.

53

R12 Head Lines

Ho1 Receiva%les #cco!ntin ha$$en in 11i #s 1e kno1 the final acco!ntin data not enerated $rior to transfer to <L as only distri%!tion level information is $assed to <L. /n 11i , 1e kno1 three distinct distri%!tions ta%les for invoices 6 'redit ,emos 6 .e%it ,emos have to ca$t!re acco!ntin class ? amo!nts information %!t not de%its ? credits. 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 a ainst 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 Led er Ta%les.The e(istin 11i acco!ntin -rocess is can %e %est !nderstood %y fi !re %elo1.

S!%led er to Led er 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!%led er #cco!ntin #ll s!% led er 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 $ro ram that 1as not transferred, that acco!ntin 1ill not %e transferred. The Transfer Xo!rnal Entries to <L $ro ram 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 a re ated 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!% led er transaction ty$es and there life cycle. /t has three levels Event Entity" Hi hest level, often 1 $er s!% led er 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 si nificance.

/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 $ro ram, 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 En ine ) -rod!ct #+* 7nderstandin <lo%al #cco!ntin En ine 3 .!al $ostin , Ta%les, Re$orts R12 SL#" From -rod!ct #cco!ntin to S!%led er #cco!ntin R12 SL#" #naly&in S!% led er #cco!ntin

We have already seen oracle ne1 2racle S!% led er #cco!ntin re$laces the <lo%al #cco!ntin En ine, 1hich normally !sed for E!ro$ean ? Re ional Locali&ations need in earlier versions. SL# itself e(tends the #+ en ine 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 En ine.

58

R12 Head Lines

The ood is that %oth the <lo%al #cco!ntin En ine)#+* and 2racle S!%led er #cco!ntin )SL#* enerate acco!ntin from a com$iled definition of acco!ntin r!les defined %y !sers. 2racle S!%led er #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 ti ht inte ration 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 $ro ress 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!% led er from intercom$any transactions. 7sin 2racle #dvanced <lo%al /ntercom$any System !ser can enter transactions for m!lti$le reci$ients 1ithin a sin le %atch. This allo1s !ser to s!%mit intercom$any transactions from one initiator to one or more reci$ients in a sin le %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 inte ration 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 $a es 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 chan ed 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 ori inal 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 or ani&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 si ns, 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 $a e 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 ,ana ement En ine )#,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 $a es incor$orate vario!s sec!rity feat!res. The !ser can enter transactions only for those intercom$any or ani&ations that are assi ned 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 or ani&ations in the enter$rise.What is different %et1een these t1o is " R11i 3 Each res$onsi%ility has only one s!%sidiary assi ned, 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 chan in 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 Led er 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 Led er acco!ntin $eriod, or 2racle -aya%les $eriod or 2racle Receiva%les $eriod 1hile /ntercom$any -eriod is still o$en, the 1arnin messa e 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 or ani&ations to 1hich the !ser has an access, the in%o!nd section sho1s transactions received %y these or ani&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 or ani&ations to 1hich the !ser is iven the access. 7ser can select 1hat $arameters like initiator, Reci$ient, <L .ate ran e, Batch 0!m%er ran e, 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 ran es of initiator and reci$ient acco!nts to see 1hat transactions make !$ their %alances.

62

R12 Head Lines

# note on =1ec nciliati n !r cess Reconciliation $rocess is a!tomated to easily reconcile intercom$any receiva%les and intercom$any $aya%les acco!nt %alances. The $rocess hel$s !ser to identify acco!nt %alances difference and to research the ca!se of difference. The reconciliation $rocess s!$$orts drilldo1n to <eneral Led er 4o!rnal details and s!%led er transaction details to investi ate the reason of %alance difference. The !nderline re$ort have ca$a%lity to sho1" .etails %y Reconciliation S!mmary .etails Reconciliation S!mmary %y So!rce .etails Reconciliation S!mmary %y Xo!rnals

Cash Managment #s %ank .ata ,odel has %een chan ed and moved at a centrali&ed $lace 1hich et associated 1ith le al entity association. Bank statement reconciliation %ecome easier %y more !ser friendly $arameter.2ther Feat!res like centrali&ed Balances ? /nterest,/nterest 'alc!lator,Bank #cco!nt Transfers makes a com$lete different look. Read the %elo1 to$ics for ,ore details" R12 " Bank ? Tradin 'omm!nity #rchitect!re)T'#*

Three key 'E ta%les no1 as" 'E@B#0I@#''270TS for %ank acco!nts 'E@B#0I@#''T@7SES@#LL for acco!nt !ses %y 2$eratin 7nits ? Le al Entities 'E@<L@#''270TS@''/. for %ank acco!nt !se acco!ntin data

Within T'# model, here is vario!s attri%!tes ho1 they fits inside the model.

63

R12 Head Lines

R12 " EBS Bankin ,odel in demandin and 'han in World

Hey did yo! notice there is one thin that kee$ chan in since last 2 releases Fthe %ank. We have seen there 1as once from $re 1J.( to 11i 1hen s!$$lier %ank se$arated from s!$$liers data and no1 its a ain in R12 1hen it %ecome $art of T'#.This time , %eca!se of chan in %!siness need and hi h demand of lo%al $artners 1orkin model. 0ot only yo!r com$any is

64

R12 Head Lines o$eratin lo%ally,yo!r $artner too o$eratin lo%al,then 1hy not !se them. /n ty$ical %!siness cost model, if cor$orate office is !sin 'iti%ank for $ayroll for 7S# o$eration then 1hy not 'iti%ank Sin a$ore %ranch is !sed for $ayroll for Sin a$ore if they are o$eratin there. So!nd %it lo1F1hy .. #s 1e a1are the key messa e of R12 1hile release 1as . Think <lo%ally 3 !sin %!siness intelli ence and analysis tools Work <lo%ally 3 !sin the lo%al ca$a%ilities of the a$$lications ,ana e <lo%ally 3 !sin the latest system architect!re and middle1are

so 1hat , think lo%ally and 1ork lo%ally is factor drivin for the chan es .This release have 1itness the reat chan es ever into the %ank model. 0o1 the %ank acco!nts is attached to yo!r le al entity level rather than 2$eratin 7nit in 1hich c!rrent and e(istin versions 2ffers. This makes %ank 1ith stron ca$a%ility to $ay across o$eratin !nits. ,ore over its im$ortant to !nderstand %anks acco!nts can %e shared %y a$$lications and can %e desi ned for !se %y -aya%les, Receiva%les and -ayroll. What is ne1 in R12 for Bank These chan es make easier and more relia%le %y Sin le access $oint Sin le Le al Entity o1nershi$ 7sa e ri hts ranted to one or more 2r ani&ations o Reconciliation o$tion defined at Bank #cco!nt level o ,ore fle(i%ility and control

Take a looks of some of the releases Release 1J.P character61J.Q 0'# to 11i Ho1 1J.( s!$$lier %anks are ma$$ed to 11i Bank 0ame $o@vendor@sites.%ank@n!m%er LO a$@%ank@%ranches.%ank@name $o@vendor@sites.%ank@n!m%er LO a$@%ank@%ranches.%ank@n!m%er Bank 0!m%er $o@vendor@sites.%ank@n!m LO a$@%ank@%ranches.%ank@n!m $o@vendor@sites.%ank@n!m LO a$@%ank@%ranches.%ank@%ranch@name Bank #cco!nt 0ame $o@vendor@sites@all.%ank@acco!nt@name LO a$@%ank@acco!nts@all.%ank@acco!nt@name Bank #cco!nt 0!m%er $o@vendor@sites@all.%ank@acco!nt@n!m LO a$@%ank@acco!nts@all.%ank@acco!nt@n!m

Release 11i These are ta%les 1hich hold the %ank details irres$ective of s!$$lier or internal %anks. a$@%ank@%ranches a$@%ank@acco!nts@all

65

R12 Head Lines 'om$arin the 11i As R12 /f 1e com$are the %ank 1ith 11i vs R12, 1e can notice the %ank 1as !tili&ed into three different $laces , finance ,$ayroll and treas!ry, 1hich re9!ires alto ether a different set!$. /t 1as one of the %i iss!es 1ith inte ration as$ect, as si nificant $ro%lem 1as reco ni&ed once the E($ense mana ement and $ayroll !ses same %ank for the res$ective $erson. There 1as a common 9!estion6conf!sion %et1een the /nte ration E(istence %et1een Bank .ata in #cco!nts -aya%le and Bank .ata /n -ayroll B #s disc!ssed a%ove , yo! kno1 most of release of 11i family of oracle #$$lication does not have inte ration %et1een HR and #- for %ank acco!nt data. We have notice in 11i there 1as f!nctionality in 1hich -aya%les in 1hich 1e 1ill create an em$loyee ty$e s!$$lier from HR data and it 1ill contain name and address info %!t not %ank information. The reason for this is that HR6-ayroll does not store the %ank information in a standard 1ay that makes the inte ration $ossi%le. So no1 r12 this 1as 1ell taken care and inte ration is %!ilt. There are $lans !nder 1ay for all %ank acco!nt data models in the vario!s $rod!cts to %e consolidated in the ne1 T'# architect!re. The 'ash ,ana ement team is 1orkin on this $ro4ect. -aya%les and HR6-ayroll are 1orkin so that the event!al idea 1ill %e that yo! can set !$ %ank acco!nts in one $lace and then indicate the !sa e )$ay, e($ense reim%!rsement, etc*. For !nderstandin it is com$arison %et1een 11i and release 12 , 1here T'# comm!nity take cares of every thin s.

66

R12 Head Lines Release 12 , 1hat is ne1 than

Bank #cco!nts 1ill %e stored in a ne1 ta%le called 'E@B#0I@#''270TS and 1ill %e located at a Bank Branch. The ne1 ta%le 1hich hold the %ank information are as"

1. 'E@B#0I@#''270T"stores %ank acco!nt attri%!tes 2. 'E@B#0I@#''T@7SES@#LL " This stores the %ank acco!nt !se attri%!tes s$ecific to
2$eratin 7nit )#R, #-* and Le al Entity )Treas!ry*.

3. 'E@<L@#''270TS@''/. "The acco!ntin data $ertainin to the %ank acco!nt !se 1ill
%e stored in the ta%le. This ne1 data model allo1s the %ank and %ank %ranch entities to %e defined se$arately allo1in !sers to esta%lish a hierarchical relationshi$ %et1een them. ,issin link %et1een S!$$lier #nd S!$$lier BanksB Go! sho!ld kno1 The link %et1een -2@AE0.2RS and HE@-#RT/ES is -2@AE0.2RS.$arty@id. The link %et1een -2@AE0.2R@S/TES@#LL and HE@-#RTG@S/TES is -2@AE0.2R@S/TES@#LL.$arty@site@id. When a S!$$lier is created Record 1ill %e /nserted in HE@-#RT/ES. When the S!$$lier Site is created Record 1ill %e /nserted in HE@-#RTG@S/TES. When #ddress is created it 1ill %e stored in HE@L2'#T/20S When a %ank /s 'reated, the %ankin information 1ill %e stored in

/BG@E+T@B#0I@#''270TS /BG@E+T@B#0I@#''270TS.B#0I@id L h&@$aties.$arty@id When the Bank is assi ned to Aendors then it 1ill %e !$dated in HE@'2.E@#SS/<0,E0TS.

HE@'2.E@#SS/<0,E0TS.o1ner@ta%le@id L /BG@E+T@B#0I@#''270TS.%ranch@id. /nternal Bank #cco!nts ? S!$$lier and '!stomer Bank #cco!nts in R12

67

R12 Head Lines /nternal Bank #cco!nts /n Release 12, each internal %ank acco!nt is assi ned to a Le al Entity. #ny or all o$eratin !nits associated 1ith that le al entity are $ermitted to !se that %ank acco!nt. S!$$lier and '!stomer Bank #cco!nts /n Release 12 $rovides a centrali&ed re$ository for s!$$liers5 and c!stomers5 %ank acco!nt and credit card information. #ll data is stored in one, sec!re $lace, $rovidin shared service centers and collection de$artments consistent information that they need. -ayment 'entral En ine for -ayment .is%!rsement and F!nds 'a$t!re,Sec!re Re$ository for 'redit 'ards and '!stomer6S!$$lier Bank #cco!nts Read for more details for technical covera e" Ino1 the 'han es %eca!se of R12 2racle -ayment ,od!le )F!nd .is%!rsement* in EBS

#s 1e kno1 , f!nd dis%!rsement f!nctionality has %een moved from 2racle $aya%les to ne1 -ayment mod!le, 1hich $rovides these f!nctionality likeC 'reation ? validation of $ayments # re ation of $ayments into files Format ? transmission of files

1here as selection ? a$$roval of invoices remains in -aya%les itself. /t is very im$ortant to !nderstand some of im$ortant chan es im$act 1hile !$ radin 11i to r12 to some of the c!stom re$orts if they are %ased o!t of R11i1J version schema model.

7nderstand some of the chan es %eca!se of F!nds .is%!rsement )2racle -ayment* Some of the im$ortant chan es can %e s!mmari&ed as"

68

R12 Head Lines

Balancin To S!$$ort /ntercom$any ? /ntracom$any Transaction, the difference can %e %est !nderstood as" 11i" Balancin Xo!rnal Entries enerated at $ostin time %y the <eneral Led er -ostin ro!tine /n R12, the Balancin Ro!tine" <enerates %alancin acco!ntin entries for s!%led er 4o!rnal entries at time acco!ntin is created <enerates %alancin 4o!rnal entries at $ostin time for all other 4o!rnals 'entrali&ed Balancin Ro!tine 2racle Receiva%les Release 12 " What5s 0e1 in 2racle Receiva%les

of the E3B!siness S!ite is also called the = <lo%al B!siness Release >, as it has n!mero!s enhancements desi ned to make it easier to do %!siness on a lo%al %asis. # more fle(i%le, centrali&ed lo%al acco!ntin str!ct!re has %een introd!ced 1hich makes it easier to o$erate %et1een and across o$eratin !nits and le al entities. 2verall, R12 contains 1R ne1 mod!les and 2;;: enhancements to e(istin f!nctionality. 2racle5s Release 12 )R12* of their E3B!siness S!ite contin!es to e(tend the f!nctionality of the Receiva%les arena , in addition to incor$orated ne1 financial architect!re and ne1 $rod!cts , 2racle Receiva%les is no1 very nat!red $rod!ct.#s $art of this $ost, 1e 1ill look at 2racle5s ne1est6enhanced offerin s in 2racle Receiva%les. Reven!e Reco nition /n R12 reven!e reco nition is %ased on R!les and Events, and they are" Time3Based Reven!e Reco nition o Rata%ly 2ver Time o 7$on E($iration of 'ontin encies Event3Based Reven!e Reco nition o -ayment o '!stomer #cce$tance R!le3Based Reven!e Reco nition o -ayment Term Thresholds o Ref!nd -olicy Thresholds o '!stomer 'redit 1orthiness

69

R12 Head Lines

Lets take a 9!ick look on some of the ne1 chan es" .aily Reven!e Reco nition o Reven!e distri%!tion over f!ll as 1ell as $artial acco!ntin $eriods. o F!lfills strin ent acco!ntin standards o #cc!racy to the n!m%er of days in the acco!ntin $eriod. Enhanced Reven!e 'ontin encies " o F!lly S!$$orts 7S <##- and /#S o 7ser defina%le contin encies o 7ser defina%le defa!ltin r!les for contin encies assi nment o S!$$orts $arent3child )e. . -rod!ct and Service* relationshi$ o /nte ration 1ith 2rder ,ana ement and Service 'ontracts o 7ser /nterface as 1ell as -ro rammin /nterface )#-/* s!$$ort o #ccess control thro! h seeded Reven!e ,ana ers Res$onsi%ility .eferred Reven!e ,ana ement

Event3Based Reven!e ,ana ement in 2racle Receiva%les allo1s !sers to define reven!e deferral reasons or contin encies and corres$ondin reven!e reco nition events. /n Release 12, reven!e contin encies for c!stomer acce$tance that are a$$lied to oods sold in 2rder ,ana ement are no1 a$$lied to services sold to cover those oods. Reven!e is deferred for service ordered in %oth 2rder ,ana ement and Service 'ontracts. #cce$tance contin encies associated 1ith an item instance are a!tomatically a$$lied to service reven!e associated 1ith the item instance 1hen it is covered in a Service 'ontract as a 'overed -rod!ct. Reven!e for services on other covered levels, s!%scri$tions and !sa e is not im$acted %y contin encies a$$lied to oods associated 1ith those services. <lo%al #rchitect!re #s 1e kno1, 1ith in lo%al architect!re , these ne1 thin s has %een introd!ced. S!% led er #cco!ntin 3 Xo!rnal 'reation takes $lace $rior to <L. Bank ,odel 3 This !nified model ena%les to $ark c!stomer Bank as 1ell as /nternal %ank information into there ne1 model, so that 1orkin ca$ital cash flo1 sho!ld %e enhanced.

70

R12 Head Lines

EB!siness Ta( 3 2racle E3B!siness Ta( is a ne1 $rod!ct that !niformly delivers ta( services to all 2racle EB!siness S!ite %!siness flo1s. /n Release 12, Receiva%les is enhanced to s!$$ort inte ration 1ith the E3B!siness Ta( $rod!ct. /ntercom$any 3 This is enhanced %y a!tomatic %alancin ,

,2#' 'ontrol

This enhance yo! %y ena%lin and $erformin tasks across o$eratin 7nits )27s*, 1here yo! have access to 1itho!t chan in res$onsi%ilities. #s 1e kno1 , ,2#' ena%les com$anies that have im$lemented a Shared Services o$eratin model to efficiently $rocess %!siness transactions %y allo1in them to access, $rocess, and re$ort on data for an !nlimited n!m%er of o$eratin !nits 1ithin a sin le a$$lications res$onsi%ility. /n n!tshell, once ,2#' is ena%led, then yo! can" -erform Set!$s for any 27 Enter invoices across 27s Receive 'ash for any 27 ,ana e '!stomer 'redit across all 27 R!n re$orts across 27s

71

R12 Head Lines Beca!se of this reatly enhanced Role %ased sec!rity o$tions, the a%ility to access m!lti$le o$eratin !nits 1ith a sin le res$onsi%ility can sim$lify S2+ com$liance monitorin from finance controller side. Line Level 'ash #$$lications The Line Level 'ash #$$lications sol!tion allo1s the a$$lication of recei$ts to s$ecific transaction items s!ch as individ!al lines, ro!$s of lines, or ta( or frei ht %!ckets. From the recei$t 1ork%ench, yo! are a%le choose 1hether to allocate cash to the entire transaction or to a$$ly amo!nts a ainst s$ecific items accordin to the c!stomer remittance. #$$ly to s$ecific lines or ro!$s of lines /ndicate 1hen ta(, frei ht or finance char es only are $aid ,ake chan es as needed Easily vie1 activity a ainst recei$ts Ino1 1hat historical activity affects yo!r recei$t See 1hat $rior activity affects a ne1 a$$lication

Enhanced '!stomer Screen We have seen 11i '!stomer standard forms makes easier %y sim$le navi ation. This times there is clearer se$aration of the $arty and acco!nt layers, 1hich makes a consist ant look and feel. ,ore over f!ll %ack1ard com$ati%ility 1ith 11i 7/ Bill -resentment #rchitect!re has %een $rovided. The #R 'reate '!stomer $a e in R12 has eliminated the navi ation to se$arate 1indo1s. 0o1, !sers can s$ecify the follo1in on a sin le $a e" '!stomer /nformation #cco!nt .etails #ddress #cco!nt Site .etails B!siness -!r$ose

Ref!nds

72

R12 Head Lines 2racle Receiva%les is f!lly inte rated 1ith 2racle -aya%les to deliver a seamless, a!tomated $rocess to enerate check and %ank acco!nt transfer ref!nds for eli i%le recei$ts and credit memos. Late 'har es #s 1e kno1 oracle receiva%les delivers enhanced Late 'har es f!nctionality ena%lin the creation of standard late char e $olicies that can %e assi ned to c!stomer acco!nts or acco!nt sites.Fle(i%le $olicy confi !rations incl!de m!lti$le interest calc!lation form!las, transaction and acco!nt %alance thresholds, and c!rrency3level rate set!$s. With ne1 chan es these are the enhanced f!nctionality" E($anded assessment and calc!lation ca$a%ilities Tiered char e sched!les -enalty char e calc!lation /nte ration 1ith Balance For1ard Billin 'entrali&ed set!$ and maintenance of late char e $olicies 'alc!lation $erformed inde$endent of .!nnin and Statement $rocessin

73

R12 Head Lines

#R3#- 0ettin The matchin of o$en receiva%les and o$en $aya%les is a!tomated. Balance For1ard Billin This makes easy transaction $rocessin . Balance For1ard Billin is an enhanced version of the e(istin consolidated %illin f!nctionality for ind!stries 1here c!stomers are %illed for all their acco!nt activity on a re !lar, cyclical %asis. Balance For1ard Billin $rovides the a%ility to set!$ cycle3%ased %illin at the acco!nt or acco!nt site levels, ena%le event %ased %illin , and levera e !ser confi !ra%le %illin formats $rovided %y 2racle Bill -resentment #rchitect!re. # ty$ical case can %e %est !nderstood as -ayment Term defa!lts from Site $rofile if Bill Level L Site from #cco!nt $rofile if Bill Level L #cco!nt Billin .ate derived from transaction date and %illin cycle .!e .ate derived from %illin date and $ayment term 2$tionally select non3Balance For1ard term if 2verride Terms L Ges

74

R12 Head Lines

3i,ed Assets:
Release 12" P 0e1 and 'han ed Feat!re in =2racle #ssets>

Here are the si( ne1 and 'han ed feat!res for 2racle #ssets in Release 12 . S!% Led er #cco!ntin #rchitect!re Enhanced ,ass #dditions for Le acy conversions #!tomatic -re$aration of ,ass #dditions Fle(i%le Re$ortin !sin +,L $!%lisher #!tomatic de$reciation roll%ack Enhanced f!nctionality for Ener y ind!stry

Fi(ed #ssets tied 1ith SL#)S!% Led er acco!ntin * #s 1e have disc!ssed =2racle S!% ed er #cco!ntin > is a r!les3%ased en ine for eneratin acco!ntin entries %ased on so!rce transactions from #LL 2racle #$$lications. Therefore Fi(ed #sset mod!le does inte rated 1ith s!ch f!nctionality to cater the asset acco!ntin at led er level. With this feat!re" 2racle #ssets is f!lly inte rated 1ith SL#, 1hich is a common acco!ntin $latform for S!% Led ers. '!stomers can !se the seeded #cco!nt .erivation definitions or modify them as re9!ired. 'ontin!e to s!$$ort #cco!nt <enerator f!nctionality for e(istin #sset Books.

75

R12 Head Lines

0e1 SL# #cco!ntin re$ort and online acco!nt in9!iry.

What yo! 1ill notice create Xo!rnal Entries )F#-2ST* $rocess feedin into the <L@/0TERF#'E ta%le is no more e(ist .This is re$laced 1ith the 'reate #cco!ntin U #ssets $rocess )F##''-B*. With this re$lacement, the some of hi h $oint in term of %enefits are" /t leads to faster closin s" Since there is no re9!irement of havin to close the $eriod, acco!ntin can %e created for F# transactions and sent to <L on a contin!al %asis thro! ho!t the $eriod. There is no need to 1ait !ntil the end of the month to r!n 'reate #cco!ntin in order to et the data to <L.

This can %e %est !nderstood as this e(am$le, if yo! do a lar e amo!nt of asset additions on the first day of the month, yo! can r!n 'reate #cco!ntin and et all the 'ost and 'ost 'learin lines over to <L at the close of %!siness that day. Enhancements have %een made to the F#@,#SS@#../T/20S ta%le. 0o1 1ith this enhanced feat!re, 1e can $o$!late the val!es for the ne1 attri%!tes directly in the F# ,ass #dditions interface ta%le rather than acce$tin defa!lt val!es from the asset cate ory. Le acy conversion can %e com$letely a!tomated.These are ne1 adds3on" #sset Life .e$reciation ,ethod -rorate 'onvention Bon!s R!le 'eilin 0ame .e$reciation Limit -l!s others

What it is !nderstood, is that We% #./ has also %een !$ raded to incl!de the ne1 #ttri%!tes. 0e1 col!mns in the #sset #dditions We%#di #dditional attri%!te can %e !sed to $o$!late val!es directly there%y eliminatin the need to override the defa!lts from the #sset 'ate ory

0e1 #!tomatic -re$aration of ,ass #dditions This ne1 feat!re consists of defa!lt r!les and -!%lic #-/s that can %e !sed %y c!stomers to com$lete the $re$aration of mass addition lines a!tomatically. o #!to $o$!late re9!ired fields s!ch as E($ense #cco!nt, #sset 'ate ory etc. o #void man!al intervention d!rin the ,ass #dditions $re$are $rocess o #void c!stomi&ation and !se $!%lic #-/s to effect c!stom %!siness lo ic. #ssets no1 !ses Fle(i%le Re$ortin !sin +,L $!%lisher o ,a4or #sset Transaction re$orts have %een modified to s!$$ort +,L $!%lisher. o 7sers can modify or !se ne1 tem$lates to vie1 re$ort o!t$!t.

Fle(ia%le Re$ortin into +,L -!%lisher Thirteen asset re$orts have %een converted in +,L -!%lisher %ased re$ort.

76

R12 Head Lines

#sset Transfers Re$ort Transaction History Re$ort #sset Reclassification Re$ort ,ass #dditions 'reate Re$ort 'ost #d4!stment Re$ort 'ost S!mmary Re$ort '/- S!mmary Re$ort Reserve S!mmary Xo!rnal Entry Reserve Led er #sset #dditions Re$ort '/- 'a$itali&ation Re$ort ,ass #dditions -ostin #sset Retirements

#!tomatic .e$reciation Roll%ack .e$reciation is rolled %ack a!tomatically %y the system 1hen any transaction is $erformed on an asset if the follo1in conditions are met" .e$reciation has %een $rocessed in that $eriod The $eriod is not closed

That mean, it is no lon er re9!ired to r!n de$reciation roll%ack $ro ram man!ally as 1e have seen in release 11i. .e$reciation roll%ack is e(ec!ted only on select assets as re9!ired and not on the entire #sset Book this enhances $erformance of the $ro ram. Since release 11i, !sers have %een a%le to r!n de$reciation for an asset %ook 1itho!t closin the $eriod. /f additional ad4!stments are re9!ired in the c!rrent $eriod, then the !ser s!%mits a $rocess to roll %ack de$reciation for the entire %ook, $erforms the necessary ad4!stment)s* and then res!%mits the de$reciation $ro ram. /n Release 12 the intermediate man!al ste$ of rollin %ack de$reciation for the entire %ook in order to $rocess f!rther ad4!stments on selected assets is no lon er necessary. #s %efore !sers may s!%mit de$reciation for the entire %ook $rior to closin the $eriod. /f it %ecomes necessary to $rocess financial ad4!stments on one or more assets, the !ser may $roceed 1ith the transaction normally via the asset 1ork%ench or mass transactions. 2racle #ssets a!tomatically rolls %ack the de$reciation on 4!st the selected assets )instead of the 1hole %ook* and allo1s the transaction)s* to %e $rocessed normally. The asset)s* for 1hich de$reciation 1as rolled %ack is a!tomatically $icked !$ d!rin the ne(t de$reciation r!n or at the time that the de$reciation $eriod is finally closed. Enhanced f!nctionality for Ener y /nd!stry #s $er R'. , this can %e !nderstood asC Ener y 7nits of -rod!ction ,ethod for <ro!$ #ssets

77

R12 Head Lines /n the oil ? as ind!stry, asset $ro$erties may incl!de fields, leases and 1ells. These assets are ty$ically associated 1ith !nits of $rod!ction )72-* and are de$reciated !sin a s$ecial 72de$reciation method. 8Ener y5 assets are enerally str!ct!red into t1o levels, ro!$ and mem%er assets, 1here the ro!$ asset is a collection of several mem%ers. #llo1 -rod!ction method for <ro!$ #ssets #llo1 -rod!ction !$load to <ro!$ #ssets Ener y Strai ht line ,ethod

This feat!re is !sed in oil ? as ind!stry, 1here non3$rod!cin assets are de$reciated !sin the ener y strai ht3line method %ased on the asset5s net %ook val!e. #ssets that de$reciate !sin the ener y strai ht3line method may either de$reciate at the mem%er asset level or ro!$ asset level. 0et Book Aal!e 6 Remainin Life #./3 273 2$eratin 7nit T'#3 R'.3 LE3 Le al Entity SL#3S!% Led er #cco!ntin ,2#' M1C

For more information read oracle R12 doc!mentation li%rary htt$"66do1nload31est.oracle.com6docs6cd6B:;SHP@J16c!rrent6html6docset.html

78