R12:How MOAC enviornment is setup programmatically

Pre-requisites for understanding how MOAC works in R12 are (Although these are not mandatory but knowledge of these would definitely help),

1. Setting ORG context prior to R12 version
Prior to R12, if you want to set ORG context in Oracle apps on any multi org table then following need to be done,

a. Create the table
b. Create a view on the table with following condition

WHERE NVL (org_id,
NVL (TO_NUMBER (DECODE (SUBSTRB (USERENV ('CLIENT_INFO'), 1, 1),
' ', NULL,
SUBSTRB (USERENV ('CLIENT_INFO'), 1,
10)
)
),
-99
)
) =
NVL (TO_NUMBER (DECODE (SUBSTRB (USERENV ('CLIENT_INFO'), 1, 1),
' ', NULL,
SUBSTRB (USERENV ('CLIENT_INFO'), 1, 10)
)
),
-99
);

As an example, let us consider the PO_HEADERS_ALL table. This is owned by PO schema having records for every operating unit. To implement Org security, a view has been created on top of it i.e. PO_HEADERS and is being owned by APPS schema.

If you see the content of this view, you would see the view has been created by accessing the value of CLIENT_INFO session field value which is being set by respective applications like PO, AP using DBMS_APPLICATION_INFO.SET_CLIENT_INFO API.

So, if you want to give the access only for US operating unit (lets assume the ORG_ID to be 100) then you set

begin
dbms_application_info.set_client_info(100);
end;

If you query PO_HEADERS after the above statement is executed in your session then you would see all the POs only for operating unit 100. This is to secure the data as per the user access,

You can also use FND_CLIENT_INFO.SET_ORG_CONTEXT API to set the ORG context which ultimately uses the above to set the ORG context.

begin
fnd_client_info.set_org_context(100);
end;

This is how all the applications (PO, AP etc) set the CLIENT_INFO field and set the ORG_CONTEXT prior to R12.


2. RLS (Row level security)

RLS feature was introduced in Oracle since Oracle 8i. The prime feature of RLS is implementing row level security while reading / inserting / deleting the data from the Database. In brief, you can use RLS to restrict data based on user permissions / privileges.


How MOAC works in R12
In R12, Oracle applications use RLS feature to implement MOAC.

Now going back to our same example- PO_HEADERS_ALL table.
In R12 these tables are still owned by PO schema but what changed is the view now no longer exist in R12. In R12, the multi org based views have been replaced with SYNONYMS in APPS.
So, for PO_HEADERS_ALL you now would see PO_HEADERS synonym in APPS schema pointing to APPS.PO_HEADERS_ALL table.

Now if you query the following in R12 APPS DB,

SELECT * FROM DBA_POLICIES WHERE OBJECT_NAME='PO_HEADERS'

You would see the following,

As seen in the picture above, whenever you query PO_HEADERS in R12, the DB is going to apply the policy defined on this synonym which in turn would call MO_GLOBAL.ORG_SECURITY API. This API returns the predicates which would be automatically applied to the query by Oracle DB.
If you check the content of this API, you would see that it basically prepares the where condition for the ORG_ID to which user has access to, which is being read from the TEMP table MO_GLOB_ORG_ACCESS_TMP.
MO_GLOBAL.INIT API is there in "prior to R12" releases but it was not being used in the RLS and there is no policy defined on the multi-org enabled tables / views.

The temp table is populated when you set user / org context.

Prior to R12, FND_CLIENT_INFO.SET_ORG_CONTEXT is used to set the ORG context
This would set the ORG Context and then the multi org related views can be accessed which would return records only for that operating unit.


But from R12, following is used to set the org context

--Use FND_GLOBAL.APPS_INITIALIZE API to set the user environment
--Use MO_GLOBAL.INIT to populate the temp table MO_GLOB_ORG_ACCESS_TMP based on the responsibilities to which the user has access to and which would then be used by the RLS security policy.

After you set these up, if you query PO_HEADERS synonym then Oracle DB would automatically add the predicate (the list of operating units to which user has access to) to the query and would only return rows for the operating units to which user has access to.

For e.g. run the following in R12,
(Refer my earlier post on "how to setup MOAC in R12" to see the operating units that OPERATIONS user has access to)

begin

FND_GLOBAL.APPS_INITIALIZE(1318 ---user 'OPERATIONS'
,20639 ---responsibility "Payables Manager"
,200 ---Application "Oracle Payable"
);

MO_GLOBAL.INIT('SQLAP');


end;

Then query the temp table,
select * from MO_GLOB_ORG_ACCESS_TMP

Now the query returns the list of operating units to which OPERATIONS user has access to. And if you query from PO_HEADERS, you would see result from these operating units.

Summary:
A. Oracle uses RLS to implement MOAC in R12
B. All multi-org tables now have synonym in APPS
C. The synonyms now have a policy defined which can be found in DBA_POLICIES
D. To setup multi-org context in R12 from the back end programmatically,
1. Call FND_GLOBAL.APPS_INITIALIZE
2. Call MO_GLOBAL.INIT

R12: Setting up MOAC (Multi Org Access Control) in R12

Prior to R12, end users use to toggle / switch / change responsibilities in order to do transactions (like invoice / payment processing in AP) in different operating unit. This is a very time consuming and inefficient way of recording transactions when you have 100s of operating units specially Internet based organizations who have world wide operations in almost all the countries.

To address this, a new feature in R12 has been introduced in which user can switch between operating units within a responsibility something similar to "Change Organization" feature in inventory. Prior to R12, user would have to switch responsibilities in order to enter transactions in respective operating units (tagged to the responsibility).

To enable this feature, Oracle has provided MOAC (Multi Org Access Control) in R12 to achieve this functionality.
Most of the setup steps for this is similar to setting up of HR Security. So, if you know how to set HR security then setting MOAC is just a piece of cake.

Do the following setups as part of MOAC setup-

Step 1. Create Organization Hierarchy-
Navigate to Human Resource responsibility > Define Organization Hierarchy

Create an Organization Hierarchy as shown below. Here I have named it as "XXTech Vision". This is my Org hierarchy name.
This has following heirarchy,

Organization name (This would show-up all Organizations in the current business group):
Vision Corporation
--Vision Services
--Vision Leasing
--Vision Utilities



Once you set this up, you can see how your hierarchy looks like in the Organization Diagrammer as shown below,



Step 2- Create HR Security Profile as shown below (Navigation - Human Resources responsibility > Security > Profile)
Enter the values as shown in the below picture.




Step 3- The final step of the setup is to attach the HR security profile just created to the "MO:Security Profile" profile for the responsibility to which you want to have the MOAC functionality as shown in the below picture,




Step 4- Run "Security List Maintenance" concurrent request,
This process maintains the list of employees, organizations, positions, payrolls and applicants that security profile holders have access to. Schedule this request to run every night during quite hours if possible. If it is run when the users are logged in then users may experience unexpected results while doing transactions like additional employees / OUs may become visible or previously visible employees may no longer be visible for a brief period of time. Once the process completes then everything would work normal. If it does not run due to some reason then this can be manually run as shown in the picture,




Step 5- Test the setup
Now navigate to "Payables Manager" responsibility > Invoices Workbench > Click on the LOV of OU > It would show up all the organizations (setup as operating units that were part of the security profile > organization hierarchy as shown in the below picture,




Summary:
With this new feature in R12, it can be seen that users just need to select the operating unit within same responsibility to do the transactions without leaving the responsibility and thus tremendously improve the processing efficiency.

R12: Getting list of operating units user has access to in R12

With the introduction of MOAC feature in R12, now user can access multiple operating units in subledgers without leaving the current responsibility. Sometimes we need to find out what operating units are accessible from a responsibility for an application (like AP, PO etc) for investigation / debugging purpose.

I have found two ways to get those details,

1. By setting MOAC enviornment from backend in PL/SQL and get the list of operating units from the temp table MO_GLOB_ORG_ACCESS_TMP,
For e.g.- If you want to see what operating units can be accessbile from OPERATIONS user through "Payables Manager" responsibility then run the below anonymous block,

--This sets the User enviornment---

begin

FND_GLOBAL.APPS_INITIALIZE(1318 ---user 'OPERATIONS'
,20639 ---responsibility "Payables Manager"
,200 ---Application "Oracle Payable"
);

MO_GLOBAL.INIT('SQLAP'); --This will initialize MOAC for AP application

end;

Then querying below would give all the operating units user has access to,

select * from MO_GLOB_ORG_ACCESS_TMP

The downside of this script that you should have access privilege to execute FND_GLOBAL.APPS_INITIALIZE AND MO_GLOBAL.INIT

2.
If you do not then alternate method is to write a query which would read HR security profile, HR Org hierarchy, FND profile etc and get you the list of OUs. Following query can be used for that which would give the list of OUs accessible from "Payables Manager" responsibility,

SELECT distinct B.PROFILE_OPTION_VALUE,C.RESPONSIBILITY_NAME,d.SECURITY_PROFILE_NAME, d1.name ou_name
FROM FND_PROFILE_OPTIONS_VL A
, fnd_profile_option_values b
, fnd_responsibility_vl c
, per_security_profiles_v d
, per_organization_structures a1
, PER_ORG_STRUCTURE_VERSIONS b1
, per_org_structure_elements_v c1
, hr_operating_units d1
WHERE A.user_PROFILE_OPTION_NAME LIKE 'MO%Security%'
and d.ORGANIZATION_STRUCTURE_ID = a1.ORGANIZATION_STRUCTURE_ID
and a.PROFILE_OPTION_ID=b.PROFILE_OPTION_ID
and TO_NUMBER(b.LEVEL_VALUE)=c.RESPONSIBILITY_ID
and d.SECURITY_PROFILE_ID = b.PROFILE_OPTION_VALUE
AND upper(c.RESPONSIBILITY_NAME) like 'PAYABLES MANAGER'
and a1.ORGANIZATION_STRUCTURE_ID = b1.ORGANIZATION_STRUCTURE_ID
and b1.ORG_STRUCTURE_VERSION_ID= c1.ORG_STRUCTURE_VERSION_ID
and (d1.organization_id = c1.ORGANIZATION_ID_CHILD
or d1.organization_id = c1.ORGANIZATION_ID_parent)
UNION ALL
SELECT B.PROFILE_OPTION_VALUE,C.RESPONSIBILITY_NAME,d.SECURITY_PROFILE_NAME, d1.name ou_name
FROM FND_PROFILE_OPTIONS_VL A
, fnd_profile_option_values b
, fnd_responsibility_vl c
, per_security_profiles_v d
,PER_SECURITY_ORGANIZATIONS_V c1
, hr_operating_units d1
WHERE A.user_PROFILE_OPTION_NAME LIKE 'MO%Security%'
and a.PROFILE_OPTION_ID=b.PROFILE_OPTION_ID
and TO_NUMBER(b.LEVEL_VALUE)=c.RESPONSIBILITY_ID
and d.SECURITY_PROFILE_ID = b.PROFILE_OPTION_VALUE
AND upper(c.RESPONSIBILITY_NAME) like 'PAYABLES MANAGER'
AND c1.SECURITY_PROFILE_ID = d.SECURITY_PROFILE_ID
and c1.ORGANIZATION_ID = d1.ORGANIZATION_ID