You can notice that the new field “Operating Unit” which
is new field in R12 and by default is in disabled mode:-
With the introduction of multi-org access control in release
12, an applications responsibility
can access multiple operating units. Some concurrent programs have been enhanced to process multiple operating units simultaneously, while for other requests the operating unit must be specified when you run the program.
can access multiple operating units. Some concurrent programs have been enhanced to process multiple operating units simultaneously, while for other requests the operating unit must be specified when you run the program.
To support this, concurrent programs are defined with an
operating unit mode of 'S' for single operating unit or 'M'(concurrent program
will be in this mode by default) for multiple operating units. If the
'Operating Unit Mode' is not set for the concurrent program it will fail.
The “Operating Unit” field/parameter is known as “Reporting
Context” in MOAC(Multi Org Access Control) terminology.
For a concurrent program though there may be a need to only
run for Single Operating Unit, though the Responsibility has access to Multiple
Operating Units’ data based on the “MO: Security Profile” profile option.
Running a particular concurrent program for only a Single
Operating Unit can be achieved by a simple update statement or from the
front-end application:-
--Execute
the following update statement in the database for the particular concurrent
program you want set to run for "Single Operating Unit"
UPDATE fnd_concurrent_programs
SET
multi_org_category = 'S'
WHERE concurrent_program_name =
'<your program
name>';
Now we will see how we can achieve from the Oracle Applications
front-end.
1. Login into application with System
Administration responsibility (NOT System
Administrator)
2. Navigate: Concurrent -> Programs
Administrator)
2. Navigate: Concurrent -> Programs
3. Query for
short name of the concurrent program
4. Click on
Update pencil icon of your program
5. Under 'Update Concurrent Program' region, select Request
tab
6. Under 'Request Setting' region, select 'Single' from the drop down of 'Operating Unit
Mode' field
7. Save changes by clicking on 'Apply' button
6. Under 'Request Setting' region, select 'Single' from the drop down of 'Operating Unit
Mode' field
7. Save changes by clicking on 'Apply' button
8. Change
responsibility to the responsibility where the “Concurrent Program” can be run,
in
this example
“TESTOU” is assigned to “AR Super User” responsibility
9. Select the “Concurrent Program” from the “SRS Window”, now
you can see that “Operating
Unit” field is enabled and you can see the
Operating Units in the LOV
10. This particular selected Operating Unit value can be
accessed using the standard MOAC API: MO_GLOBAL.get_current_org_id
Note:- The return value for the “Operating Unit” reporting
context is corresponding “ORG_ID” for the selected “Operating Unit Name”
Good Info about MOAC and impact on Concurrent Programs
ReplyDeleteOracle Ebs Pro(For Oracle Ebs Professionals): How To Enable The Moac Parameter “Operating Unit” For A Concurrent Program In Oracle Ebs R12 >>>>> Download Now
Delete>>>>> Download Full
Oracle Ebs Pro(For Oracle Ebs Professionals): How To Enable The Moac Parameter “Operating Unit” For A Concurrent Program In Oracle Ebs R12 >>>>> Download LINK
>>>>> Download Now
Oracle Ebs Pro(For Oracle Ebs Professionals): How To Enable The Moac Parameter “Operating Unit” For A Concurrent Program In Oracle Ebs R12 >>>>> Download Full
>>>>> Download LINK NT
I got the requirement,earlier we used to run a report in two different operating units and in that report in after parameter form and before report they initialized mo_global.set_policy_context('S',:p_org_id),Here :p_org_id is the parameter which is passing from the profile option,So it worked fine as they ran from different ou's,But now they would like to run from one responsibility to which they have created a security profile and added two ou's to that security profile Please help me how we can make it work ,as earlier user is not passing any org_id bu it is impacting by default and now also they wont like to pass any org_id but it needs to work..
ReplyDeleteThanks in advance
Thanks for this! Much Appreciated...
ReplyDeleteThanks Sireesh Vishnubhatla!
ReplyDeleteGreat Example also for MOAC Concept.
Thank you so much for the post sir, its very useful! Can you please help me fetching this org id from back end with a query. I mean like by doing this we can fetch the data by selecting operating unit when ever we run the conc request right! so, now i wanted to get this org id from back end by quering it. Please help.
ReplyDelete@Swathi , For querying the org_id, you can use fnd_global.org_id
ReplyDeleteGreat Info, but falls short of describing how the parameter is created on the Concurrent Program.
ReplyDeleteOracle Ebs Pro(For Oracle Ebs Professionals): How To Enable The Moac Parameter “Operating Unit” For A Concurrent Program In Oracle Ebs R12 >>>>> Download Now
ReplyDelete>>>>> Download Full
Oracle Ebs Pro(For Oracle Ebs Professionals): How To Enable The Moac Parameter “Operating Unit” For A Concurrent Program In Oracle Ebs R12 >>>>> Download LINK
>>>>> Download Now
Oracle Ebs Pro(For Oracle Ebs Professionals): How To Enable The Moac Parameter “Operating Unit” For A Concurrent Program In Oracle Ebs R12 >>>>> Download Full
>>>>> Download LINK rs