Multi Org Access Control In R12

If you are not familiar with Multi Org Structure read my previous article on that.

In R12 One responsibilty can be tied to multiple operating Units, which is not availabe in the prior releases...

In 11.5.X,

• Profile 'MO: Operating Unit' will restrict data access for a single Operating Unit.
• To transact data in operating units, for each operating unit we need to have one Responsibility with profile 'MO: Operating Unit' defined.
• Multi-Org views are used to filter records for a single Operating Unit.
  

From R12 onwards,

• Profile 'MO: Security Profile' will ensure access to multiple operating units from single responsibility.
• End-Users will select a Operating Unit and start entering the transaction.
• List of Operating units accessible to End-user from a single responsibility is determined by 'Security Profile' defined at responsibility level/User level using Profile
  option 'MO: Security Profile'. This profile option will default in Operating Unit field of a transaction form.

• If the profile option 'MO: Security Profile' is set and gives access to multiple Operating Units, then the profile value 'MO: Default Operating Unit' if set is validated against the list of Operating Units in 'MO: Security Profile'.
• If the Operating Unit is included in the security profile then it is returned as the default value. Otherwise there is no Operating Unit default.
• Also, if the Profile Option 'MO: Default Operating Unit' is not set, then there is no default Operating Unit.
• If the profile option 'MO: Security Profile' is set and gives access to one Operating Unit, the default Operating Unit will return this value even if 'MO: Default Operating Unit' is set to a different value.
• If the profile option 'MO: Security Profile' is not set, then 'MO: Operating Unit' value is used as the default Operating Unit even if 'MO: Default Operating Unit' profile is set to a different value.
  
  Metalink Note 414003.1 gives a detailed description on this new feature