Sie sind auf Seite 1von 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 driven by the Primary Ledger and FA is driven by the Asset book, there is no interaction
between these two modules and Operating unit/Legal Entity/ Inventory Organisation.....which every one knows.
Since the above is the standard design of oracle, the Multi org related profile options also does not affect those
modules, which is why we never set value for the MO:Operating unit profile option for Fixed Asset module and
General Ledger Module ...
Now lets focus only on General Ledger Module ...
If you are performing a drill down activity for a particular journal in General Ledger module, the system will drill
down to the previous level and find the base transaction and display the same to the user, irrespective of which
organisation (operating unit) that transaction belong to. In short there is no operating unit level distinction that
takes place in GL to prevent drill down to restricted operating units alone ...
My contention is that, it is incorrect to Ignore the relevance of MO:operating unit profile option at the General
Ledger for the following reasons .....
1) Users of the application are at different levels, i.e. ranging from super user to end user, based on their 'level'
the roles and responsibilities to be handled is determined. Users belonging to every operating unit will have
access to the General Ledger responsibility as well, however due to the natural behavior of the Module, those
users would be able to review journals of other operating units as well...
At the subledger level, data divergence is taken care by the MO:Operating unit, since most of the subledgers
function at Operating unit Level
Example User A belongs to Operating unit B, he has access to three responsibilities .. Payables Responsibility,
Receivables Responsibility and General Ledger responsibility .....
User A cannot access other operating unit data from Payables and Receivables responsibility, since they are
controlled by MO:Operating unit profile option ....
However User A can use General Ledger responsibility to access data pertaining to other operating units ...
2) General Ledger has the capability of restricting the data that can be viewed through configuring, Data access
sets, security rules, cross validation rules etc .... however none of these features restrict data by Operating
unit ...
For example,
Assume we have a Multi Org structure as below ....
Ledger A => Legal Entity AA => Operating unit AAA and AAB
If i intend to use Data access set,
I can only create a BSV segment value restriction, whereas both the operating units (AAA and AAB) comes
under a single BSV Value, hence by restricting the Single BSV value at LE level, i would restrict the data
related to both the operating units and not one ...
If i intend to use Cross Validation Rules and Security Rules,
operating unit data is not recorded at the Accounting Flexfield/Chart of Accounts level, it is a multi org
component, hence
if you cannot ascertain which value to restrict, you cannot make use of Cross Validation Rules and Security

3) If the MO:Operating unit profile option value holds good at the General Ledger level, it could be used to
restrict the drilldown capabilities only to the value stated in the profile option. Hence a General Ledger user who
is supposed to access data pertaining to a single operating unit cannot drill down to transactions pertaining to
different operating unit.

Friends, can you share your view on this as well ....