Oracle EBS R12 – Multi-Oracle Access Control – MOAC


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”.

Oracle-R-12 MOAC1

Oracle-R-12 MOAC2

For example, you could assign the security profile to the ZZ_PAYABLES.. Responsibility to allow that responsibility to process invoices across all (specified as per user need) 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. you need to run a concurrent request called

“Run Security List Maintenance”

from HR which will make those security profiles available and allow one to assign them to a responsibility via a profile option called MO: Security Profile.

you can define an operating unit using the Accounting Setup Manager in Oracle General Ledger or Organization Definition form in Oracle HRMS or Inventory. 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.

Global Security Profile

Oracle-R-12 MOAC3

you 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.



 

Distinction between configuration, personalization, and extensibility.


Distinction between configuration, personalization, and extensibility.

Configuration provides setup and administrative choices using the native features of the product. Some configuration examples include:

  • Profile Options
  • User-defined fields (Flexfield)
  • Function Security Setup
  • Data Security Setup
  • and a lot more….

Personalization enables you to declaratively tailor the UI look-and-feel, layout or visibility of page content to suit a business need or a user preference. Some personalization examples include:

  • Tailor the order in which table columns are displayed.
  • Tailor a query result.
  • Tailor the color scheme of the UI.
  • Folder Forms
  • Forms Personalization
  • Oracle Application Framework (OAF)

Extensibility is about extending the functionality of an application beyond what can be done through personalization. Some extensibility examples include:

  • Add new functional flows
  • Extend or override existing business logic
  • Using Oracle Forms Developer, Oracle JDeveloper and Oracle Workflow