Oracle R12
During Setup Of (MOAC) On production server when i am trying to Attach my business group with security profile ... i can not fine my new business group on this form |
Administrator
|
Can you send me a screeenshot , or a screen path. 2014-09-22 13:34 GMT+03:00 Afnan Ahmed [via Erman Arslan's Oracle Forum] <[hidden email]>: Oracle R12 Erman Arslan, MBA Oracle Certified Expert Certified Exadata Administrator Certified Linux Administrator Blog: ermanarslan.blogspot.com Forum: http://ermanarslan.blogspot.com/p/forum.html
M: 05301567803 |
In reply to this post by Afnan Ahmed
|
Administrator
|
Hi Afnan,
The issue is functional, normally not in my scope but I will try to help. Please check the following and check your actions for implementing the MOAC Setup. Reference: http://www.jadeglobal.com/blog/multi-organizations-access-control-moac Following are the basic steps to be performed in order to enable MOAC feature: Define Security Profiles (using form function ‘Define Global Security Profile’) Enter a unique name for the security profile. To restrict access by discrete list of organizations, select ‘Secure organizations by organization hierarchy and/or organization list for the Security Type’. Check the Exclude Business Group check box to remove the business group in the list of organizations. Use the Classification field to limit the list of values (LOV) in the Organization Name field. For example, if you select the classification to Operating Unit, only operating units will display in the LOV. In the organization name field, select the Operating Unit for which you want access. enable MOAC feature Repeat until you have included all organizations to which you need access. Run the concurrent program “Security List Maintenance Program” from the standard request submission form. The “Security List Maintenance Program” can be run for a single named security profile to prevent impact to other security profiles. Assign appropriate security to the profile option “MO: Security Profile” for your users and responsibilities Navigate to the “System Administrator” responsibility > System Profile Options Assign the security profiles to MO: Security Profile for your responsibilities and/or users. Security List Maintenance Program Assign a value for profile option “MO: Default Operating Unit” (Optional) Navigate to System Administrator Responsibility > System Profile Options Assign a default operating unit to “MO: Default Operating Unit” profile option for your responsibilities and/or user. Assign MO: Operating Unit (Mandatory for only Single Org or if MO: Security Profile is not defined) Navigate to System Administrator Responsibility > System Profile Options Assign the Operating unit to MO: Operating Unit profile option for your responsibility or user. Note – From the above screen shots we can conclude that user with purchasing responsibility will be able to access data from two Operating Units Vision Operations and Vision Services. |
Free forum by Nabble | Edit this page |