Written by David Haimes
Multiple Organizations Access Control or MOAC (pronounced MOW-ACK) to use the seemingly obligatory acronym, is a powerful, yet simple to implement feature available in R12.
Implementors spend a lot of time figuring out how to configure their Legal Entities, Ledgers and Operating Units. There are a number of options some restrictions, depending on what features you want to implement and where you are. See my earlier posts on Legal Entities and Operating Units for details on that. However it is worth remembering that change is the Status Quo (No, not the band of rocking all over the world fame - it's latin, look it up) and flexibility is important, what was the optimal way to organize your transaction processing yesterday may not be right today. Many companies are creating shared service centers to centralize processing of financial transactions and a single user may process transactions on behalf of many different Operating Units(OU).
So MOAC allows you to create a security group which can contain many operating units and assign that to the User's responsibility. All the forms that process OU striped data now allow you to pick an OU to work in from a list that contains all the OU you have access to. You will also find all the OU based reports have a parameter added for OU.
The Set Up is straighforward. You can define a security profile in the HR Security Profile form, adding Operating Units to it, then you must run Security List Maintenance program before you can assign the security profile to the profile option MO: Security Profile for a responsibility.
When considering R12 this is one of the quick wins that can be achieved after upgrade and I also noticed it mentioned by the PPM team in an interview on itssafeature too which prompted me to get a post out about it.