Sie sind auf Seite 1von 8

Oracle Financials

MOAC in Concurrent Programs/Reporting


A new field "Operating Unit Mode" is added in the Define Concurrent Programs in the OA Framework pages. The user can query the program or report based on an operating unit by updating the "Operating Unit Mode" field with one of the following values:
y y y y

Single Multiple Empty

The default value is Empty. The multiple organizations context is automatically initialized by the concurrent program if the "Operating Unit Mode" is set to either Single or Multiple. The user can also select a value from the Operating Unit field's LOV in Request form when the mode is Single. The value of the "Operating Unit Mode" must be Single for a majority of the existing operating unit context sensitive reports. Example: Invoice Register report. In case of Multiple, Operating Unit field in Request page will be disabled, it indicates that CP will run for all user accessible OUs. You can also define Operating Unit field as a input parameter for CP. In this case you can run CP for selected OU or for all. Example: Invoice Validation report. **You should not change "Operating Unit Mode" of any reports which are owned by Oracle. Use this option for user defined reports only. Navigation Path: System Administrator->Concurrent->Programs Here select Request tab. There u can see "Operating Unit Mode".

Query to check this option from back-end: SELECT concurrent_program_name, multi_org_category FROM fnd_concurrent_programs WHERE concurrent_program_name = '--CP short name'; Ex: 'APXINRIR' S-Single M-Multiple null-Empty You might also like:
How to transfer data from Subledger to GL?
LinkWithin

Defaulting Operating Unit in MOAC

1.If the profile option 'MO: Security Profile' is set and gives access to multiple Operating Units, then the profile value of 'MO: Default Operating Unit' will be defaulted, if this value is validated against the list of Operating Units in 'MO: Security Profile'. i.e. 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. 2.If the profile option 'MO: Security Profile' is set and gives access to one Operating Unit, then default Operating Unit will return this value even if 'MO: Default Operating Unit' is set to a different value. 3.If the profile option 'MO: Security Profile' is not set, then 'MO: Operating Unit' value will be used as the default Operating Unit even if 'MO: Default Operating Unit' profile is set to a different value.
MOAC in Concurrent Programs/Reporting

Create XML Publisher Report Using Oracle Reports(RDF)

Explain Request Groups and Request Sets in Concurrent ...

Create Complex PO and Invoice With Retainage

LinkWithin

MOAC functions
MO_GLOBAL Package MOAC functionality is provided through the MO_GLOBAL package (AFMOGBLB.pls). Following are some of the more important functions and procedures in the package. Init() This is generally called by forms and reports to setup the list of orgs that can be accessed. It calls the set_org_access procedure, which in turn calls populate_orgs. This inserts the orgs a user is allowed to access in a global temporary table -- MO_GLOB_ORG_ACCESS_TMP. The table is populated based on the MO: Security Profile and MO: Operating Unit profile option values. Org_security() This returns a sql predicate (where clause) that controls which records can be accessed. Example: EXISTS (SELECT 1 FROM mo_glob_org_access_tmp oa WHERE oa.organization_id = org_id) This is used in dbms_rls.add_policy to add the vpd security to synonyms. Check_access() Checks to see if an org can be accessed by a user. If access mode is M (Multiple), see if the org_id is in mo_glob_org_access_tmp.

Multi-org: Begin FND_GLOBAL.apps_initialize( l_user_id, -- User id l_resp_id, -- Responsibility Id 200); -- Application Id MO_GLOBAL.init('SQLAP'); End; You might also like:
What is Tolerance in Payables and How to define Tolerances?

Export data from Excel to Table using custom Web ADI ...

Setup user as a worker to access Purchase Order form.

Create XML Publisher Report Using Oracle Reports(RDF)

LinkWithin

Posted by Contact: highbrow.admin@gmail.com at 8:23 PM 0 comments Labels: MOAC

R12 Multi-Org Access Control (MOAC)


'Multi-Org Access Control' popularly known as 'MOAC' in short form is a enhanced feature in Release 12. MOAC will enable users to access secured data in one or more Operating Units from a single responsibility. End-Users can access/transact data within several operating units based on Security Profile attached to a responsibility. i.e. End-Users can access/transact data on multiple Operating units by accessing one operating unit at a time without changing a responsibility. This Provides flexibility for end-users to work conveniently with multiple Operating Units in shared service Environments with single responsibility. Profile Options which take major Role in MOAC MO: Security Profile MO: Default Operating Unit(Optional) MO: Operating Unit(Mandatory for only Single Org or if MO: Security Profile is not defined)

MOAC Configuration 1. Define Operating Units Navigation Path: 2.Define Security Profile Navigation Path: HRMS Management responsibility->Security Security Profile: Allows you to assign multiple operating units for the same business group. Global Security Profile: Allows you to assign multiple operating units across business groups.

Choose a Security Profile menu item.

1.Enter a unique name for the security profile. 2.There are 4 security types:

y y

View all organizations generally the application will not let you save a new security profile with this setting because it automatically seeds one and there is no point to create another. Secure organizations by organization hierarchy and/or organization list This lets you define a hierarchy to be accessed and to exclude operating units from that hierarchy or include them from outside the hierarchy. You can also just list operating units without designating a hierarchy. Secure organizations by single operating unit In this case the operating unit will be determined using the operating unit specified in the MO:Operating Unit profile option. Secure organizations by operating unit and inventory organizations Here the operating unit will also be determined using the operating unit specified in the MO:Operating Unit profile option.

To restrict access by discrete list of organizations, select 'Secure organizations by organization hierarchy and/or organization list for the Security Type'. 3.Check the Exclude Business Group check box to remove the business group in the list of organizations. 4.Use the Classification field to limit the LOV in the Organization Name field. For example, if you select the Classification to Operating Unit, only Operating Units would display for the LOV in the 'Organization Name' field. 5.In the organization name field, select the Operating Unit for which you want access. Repeat this step until you have included all organizations that you need access. Seeded Security Profiles 1. One for each business group that allows access to each org in the business group. This has the same name as the business group. Since this allows access within a business group, it is in the security profile form. 2. One that allows access to all orgs. This is named like Global Vision. Since it allows access across business groups, it is in the global security profile form. So if you want to allow access to all organizations or all organizations in one business group, you can use one of the seeded security profiles. 3.Run concurrent program "Security List Maintenance Program" from the standard request submission form. The "Security List Maintenance Program" could be preferably run for one named security profile to prevent disturbing other security profile setup. 4.Assign MO: Security Profile Navigate to System Administrator Responsibility->System Profile OptionsAssign the security profile to MO: Security Profile profile option for your responsibility or user. 5.Assign MO: Default Operating Unit(Optional) Navigate to System Administrator Responsibility->System Profile Options Assign the default Operating unit to MO: Default Operating Unit profile option for your responsibility or user.

6.Assign MO: Operating Unit(Mandatory for only Single Org or if MO: Security Profile is not defined) Navigate to System Administrator Responsibility->System Profile OptionsAssign the Operating unit to MO: Operating Unit profile option for your responsibility or user.

If both 'MO: Security Profile' and 'MO: Operating Unit' are defined at a responsibility level then 'MO: Operating Unit' will be ignored and 'MO: Security Profile' will be effective. Now you can see multiple operating units in below MOAC enabled form

You might also like:


What is Payment Terms and How to define Payment Terms? Export data from Excel to Table using custom Web ADI ...

MOAC Basic
-Multi-Org Access Control feature allows you to enter, process data and generate reports from a single responsibility. -This is achieved by providing the Operating Unit field on the forms/pages and while running the concurrent processes. -To Set this feature you need to define the security profile containing operating units and set it at MO: Security Profile. -You can default the Operating Unit on forms/pages by setting the MO: Default Operating Unit profile. 1)Business Group (Which dealt with HRMS Module) It is the Higest level in the ORG structure. 2)Legal Entity ( Dealt with Tax entities, Govt reporting authorities) 3)Set of Books ( Dealt with 4 C's that is Chart of Account, Currencies and Calender, Accounting Convention) 4)Operating Unit (Dealt with 5 sub ledger modules by name AP/AR/GL/PO/OM 5)Inventory Organization (Dealt with INV/BOM/WIP/MS_MRP)

LinkWithin