7/26/2019 MO Operating Unit Has No Relevance in General Ledger

1/2

Hi All,

in the list of base financials modules i.e. GL, AP, AR, CM and FA, only GL and FA are modules that are not Multi

org specific, GL id drien by the Primary Ledger and FA is drien by the Asset boo!, there is no interaction

bet"een these t"o modules and #perating unit$Legal %ntity$ &nentory #rganisation....."hich eery one !no"s.

'ince the aboe is the standard design of oracle, the Multi org related profile options also does not affect those

modules, "hich is "hy "e neer set alue for the M#(#perating unit profile option for Fi)ed Asset module andGeneral Ledger Module ...

*o" lets focus only on General Ledger Module ...

&f you are performing a drill do"n actiity for a particular +ournal in General Ledger module, the system "ill drill

do"n to the preious leel and find the base transaction and display the same to the user, irrespectie of "hich

organisation operating unit- that transaction belong to. &n short there is no operating unit leel distinction that

ta!es place in GL to preent drill do"n to restricted operating units alone ...

My contention is that, it is incorrect to &gnore the releance of M#(operating unit profile option at the General

Ledger for the follo"ing reasons .....

- /sers of the application are at different leels, i.e. ranging from super user to end user, based on their 0leel0

the roles and responsibilities to be handled is determined. /sers belonging to eery operating unit "ill haeaccess to the General Ledger responsibility as "ell, ho"eer due to the natural behaior of the Module, those

users "ould be able to reie" +ournals of other operating units as "ell...

At the subledger leel, data diergence is ta!en care by the M#(#perating unit, since most of the subledgers

function at #perating unit Leel

%)ample 1

/ser A belongs to #perating unit 2, he has access to three responsibilities .. Payables Responsibility,

Receiables Responsibility and General Ledger responsibility .....

/ser A cannot access other operating unit data from Payables and Receiables responsibility, since they are

controlled by M#(#perating unit profile option ....

Ho"eer /ser A can use General Ledger responsibility to access data pertaining to other operating units ...

3- General Ledger has the capability of restricting the data that can be ie"ed through configuring, 4ata accesssets, security rules, cross alidation rules etc .... ho"eer none of these features restrict data by #perating

unit ...

For e)ample,

Assume "e hae a Multi #rg structure as belo" ....

Ledger A 56 Legal %ntity AA 56 #perating unit AAA and AA2

&f i intend to use 4ata access set,

& can only create a 2'7 segment alue restriction, "hereas both the operating units AAA and AA2- comes

under a single 2'7 7alue, hence by restricting the 'ingle 2'7 alue at L% leel, i "ould restrict the data

related to both the operating units and not one ...

&f i intend to use Cross 7alidation Rules and 'ecurity Rules,

operating unit data is not recorded at the Accounting Fle)field$Chart of Accounts leel, it is a multi org

component, hence

if you cannot ascertain "hich alue to restrict, you cannot ma!e use of Cross 7alidation Rules and 'ecurity

Rules.

7/26/2019 MO Operating Unit Has No Relevance in General Ledger

2/2

8- &f the M#(#perating unit profile option alue holds good at the General Ledger leel, it could be used to

restrict the drilldo"n capabilities only to the alue stated in the profile option. Hence a General Ledger user "ho

is supposed to access data pertaining to a single operating unit cannot drill do"n to transactions pertaining to

different operating unit.

Friends, can you share your ie" on this as "ell ....

Regards,

&ru!sha