In-depth research on multi org design in mo_global-EBS R12 (2)

This is the second article on multi-organization access.Anil
PassiMulti
Org R12

We all know that in Oracle
The Multi org model in Release 12 is changed. It is called multi org Access Control (MOAC ). I will tell you the reason for this change and how it will affect you. I will also tell you how to avoid affecting your existing settings at all [if you do not want to use
MOAC-multi-organization access control]

If you are not familiar with multiple organizations in EBS R12, You can first look at EBS
Multi org basics. It will explain how the current multi-organization model works in R12.

See the link for multi-organization access control in R12: whitepaper on user group site

Reasons for such changes in business
-----------------------------------------
Four years ago, I was asked to design a payable invoice scanner with the following requirements:
1.My customers have more than 100 legal entities (legal entities) and organizational units (organization units ).
2.They want to collect all paper notes payable in a central place. more effectively, they only have one address for all legal entities/organizational units.
3.All tickets are scanned in this center.
4.Scanned Images are input to the system by a Bangalore team through a queue

In this way, there are some problems:
--------------------------
The scanned ticket should first be sorted by operating uint.
Why?This is because every ou has a different responsibility for "payables clerk". This poor inspector should select responsibility based on the ou to which the entry ticket belongs.
Moreover, you cannot forcibly ask the supplier to transfer the account to your system in XML format, therefore, the recorder must ensure that each paper ticket is entered into the correct organization/ou.

How Does Oracle EBS Release 12 save it?
In R12, the recorder is no longer a "poor Recorder", because he no longer has to change his responsibilities based on different legal entities. This is the power of Oracle EBS R12 design, it meets the needs of today's shared service solutions.

Does this mean that all ou can be accessed due to the input responsibilities?
If your business needs this, you can do this in R12. You can assign the node or operating unit list at the organization level to your responsibilities, or, now you can assign multiple operating units to one role, which can be indicated by the organization level or organization list.

This sounds like HR security profiles. Let's take a look at the link to Oracle.
HRMS security profiles?
Yes. In fact, the multi-org model in R12 uses security profiles. If you read the above link, you will have a clearer understanding of the security profile in HRMS.

This means that a security profile will be attached to the role as a profile option?
Yes.

What if I don't want to implement this enhancement? Does this damage my existing multi org settings?
Oracle has some advantages when upgrading. Unless you have enabled the security profile feature, your multi-org will work the same way as previous versions of R12.

Will the multi-organization access control in R12 still fill the org_id column?
Of course, each piece of data is still bound to a separate Org.

Can we reuse security profiles defined for HRMS?
I suggest you maintain the independence of Multi-org security profile and HRMS security profile. HR security profiles also cater to the current trend and different HR-related attributes to maintain a certain position, but we know that this time multi-org will win.

Now let's go back to cope with the input. How do they specify a correct ou for each ticket when entering a ticket?
This is achieved by entering the ou item value in the window. In versions earlier than R12, this item is hidden, however, this value can be entered in all forms that use multi-organization Security Configuration.

In R12, will the user enter an additional item?
Not all. If you want to, you can specify a default ou based on your responsibilities, which is also implemented in profile.
This progile name is [I do not know yet], but it does exist, so I just said.

So we have two new Profile options?
Yes. One is the surity profile used for the append, and the other is used for the default Org.

What will happen after dbms_client_info.set_client_info (101) is run?
This will become a redundant feature. In R12, we use the package mo_global, which already exists in 11.5.10, And if you open it, you will find that it uses row-level security control. technically speaking, I thinkDbms_client_info.set_client_infoIt will continue to work, but if you enable the multiorg security feature, this will produce incalculable results.

How will this affect my customization?
Statement 1:-If you perform hard encoding on client-Info, it is obvious that you will not be able to continue working.
Statement 2:-Similarly, if you used fnd_profile.org_id, it would not work.
If you decide not to enable multi-organization access control (Multi org Access Control)Then the above two statements are not valid.