skip to main |
skip to sidebar
Multi-Org Preferences allows one to control the list of operating units they have access to. A system administrator may create a security profile that has 10 operating units assigned and assign it to one's responsibility. One can set up Multi-Org preferences to restrict the list of operating units one would access at the user level. The user has complete control over this and can change it at anytime.
Most modules have added the Preferences user interface to their responsibility menus. If one does not see it, one can add that function to a menu. To enable and display Preferences in a menu, add the function: FNDMOPREFS to your menu definition.
The Multi-org Preferences pages shows the user name that the user is logged in as, the responsibility name, and the Security Profile that you are currently assigned to as defined by the MO: Security Profile profile option. The Default Operating Unit region is where one can select a default operating unit. The List of values will display all operating units assigned to the security profile. The next region called Preferred Operating Units is where one would select the subset of operating units one wants to work with.
Multi-Org or multiple organization access (MOAC) is basically the ability to access multiple operating units from a single application responsibility. In Release 11i, when one had to enter or process data for multiple operating units, one had to login to different responsibilities because each responsibility could only access one operating unit. If one was managing Payables for Sweden, Norway and Finland one needed to define three different responsibilities. In Release 12, one would create a Security Profile and assign as many operating units as you required. One can tie that security profile to a single responsibility using a profile option called MO: Security Profile. For example, you could assign the security profile to the EMEA Payables responsibility to allow that responsibility to process invoices across all three operating units.
In Release 12, define a security profile in HR using the Security profile form or the Global Security profile form, and assign all of the operating units that one would want a responsibility to access. The one needs to run a concurrent request called “Run Security List Maintenance” from HR which will make those security profile available and allow one to assign them to a responsibility via a profile option called MO: Security Profile.
One can define an operating unit using the Accounting Setup Manager in Oracle General Ledger or Organization Definition form in Oracle HRMS or Inventory. We shall discuss about Accounting Setup Manager in a future blog post. An operating unit is then attached to a default legal context (as compared to Legal Entity in Release 11i)
Define a security profile using either of the two forms: Security Profile form or the Global Security Profile Form that is shown below. Both forms look almost identical where Security Profile Form allows one to select operating units from only one Business Group where as Global Security profile Form allows one to select operating units from multiple Business Groups.
One can define another profile option called MO: Default Operating Unit which is optional and allows one to specify a default operating unit that will be the default when you open different subledger application forms.
The blog author got this e-mail from the Oracle Applications User Group last week:
" I hope this email finds you doing well. I wanted to check with you to make sure you know about the Meeting of the Members event at Collaborate. You were nominated for Member of the Year, and we will be announcing the winner there. It will be held on Wednesday, April 18th from 12:30 until 2:00. (Lunch will be provided there). I have attached a flyer with further details......."
It would be great to meet some of the readers of this blog at the Collaborate07-Technology and Applications Forum for the Oracle Community, April 15-19, 2007, in Las Vegas , Nevada.
