4/14/2017 APPS R12Setups and Implementation: Configuring MOAC
0 More Next Blog» Create Blog Sign In
APPS R12Setups and Implementation
T h u r s d a y, M a y 3 , 2 0 1 2 Search This Blog
Search
Configuring MOAC
About Me Blog Archive
Configuring MOAC ► 2013 (1)
▼ 2012 (3)
▼ May (3)
Step 1 – Define Security Profile Accounting
Vins
Navigation Path: US HRMS Manager responsibility > Security > Profile For Oracle
(Functional Receivable
a. Enter a unique name for the security profile. Consultant) : s
b. Restrict access by a discrete list of organizations by selecting 'Secure R12 | FUSION
organizations by organization hierarchy and/or organization list for the Configuring
I have experience MOAC
Security Type'. of working in
c. Check the Exclude Business Group check box to remove the business group R12
Database
Accounting
in the list of organizations. programming,Codin Flow:
d. Use the Classification field to limit the LOV in the Organization Name field. g and Impl using
For example, if you select the Classification to Operating Unit, only different
► 2009 (2)
Operating Units would display for the LOV in the 'Organization Name' field. languages. From
e. In the organization name field, select the Operating Unit for which you want last 7 years working
on Oracle Apps‐R12
access. Repeat this step until you have included all organizations that you
and FUSION CRM
need access. applications on
Setups(Financials&C
Step 2 – Run concurrent program – Security List RM) and
Implementation
Maintenance Projects.Experience
d in one 4 Life
Navigation Path: US HRMS Manager responsibility > Security > Profile Cycle of
a. Run for one named security profile to prevent disturbing other security profile Implementation. I
setups. have a keen
interest in Oracle
Financials and CRM.
Lull before the
Step 3 – Run concurrent program – Security List storm is almost
Maintenance over and FUSION
CRM is out to be
the #1 in market as
SAAS and on‐
Step 4 – Assign MO: Security Profile premise solution.
Navigation Path: System Administrator responsibility > Profile > System View my complete
profile
a. Assign the security profile to MO: Security Profile profile option for your
responsibility or user.
Considerations
1. MO: Security Profile takes precedence over MO:Operating Unit. If MO:Security Profile is
set, that is what will be used. If MO:Security Profile is not set, then MO:Operating Unit
will be used.
2. Setting MO: Default Operating Unit is optional
Note: If the profile option 'MO: Security Profile' is set and gives access to multiple
Operating Units, then the profile value 'MO: Default Operating Unit' if set is validated
against the list of Operating Units in 'MO: Security Profile'. 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.
3. If the profile option 'MO: Security Profile' is set and gives access to one Operating Unit,
the default Operating Unit will return this value even if 'MO: Default Operating Unit' is set
to a different value.
http://vinsappsr12setupsandimplblog.blogspot.in/2012/05/configuringmoac.html 1/2
4/14/2017 APPS R12Setups and Implementation: Configuring MOAC
4. If the profile option 'MO: Security Profile' is not set, then 'MO: Operating Unit' value is
used as the default Operating Unit even if 'MO: Default Operating Unit' profile is set to a
different value.
5. MultiOrg User Preferences to Restrict Operating Units User can prefer to restrict the
list of Operating units appearing in LOVs using MultiOrg Preferences Page (Form
Function FNDMOPREFS) Endusers can have preferred operating units which would
represent a subset of operating units assigned to their security profile. i.e. Let's say a
security profile that has 10 operating units assigned and assign it to the user or his/her
responsibility and user only deals with 5 of them on a daily basis and he doesn't’t want
his work space cluttered with extraneous operating units. The user could set up MultiOrg
preferences to restrict the list of OUs.
6. The profile option 'HR: Security Profile' takes precedence over 'MO: Security Profile'.
MOAC and Concurrent Programs/Reports
While submitting a Concurrent Program/report we need to select one operating unit we have
access to from given list of Operating Units. 'Submit Request' form will allow us to select a
Operating Unit. Basically this 'MultiOrg Reporting' is allowing you to report on data from one
operating unit at time from list of accessible operating units from a single application
responsibility.
Operating Unit in 'Submit Request' from will enable based on Concurrent Program Category
defined in 'Define Concurrent Programs' window.
Posted by Vins (Functional Consultant) : R12 | FUSION at 7:32 AM
No comments:
Post a Comment
Enter your comment...
Comment as: Select profile...
Publish
Preview
Newer Post Home Older Post
Subscribe to: Post Comments (Atom)
Simple theme. Theme images by johnwoodcock. Powered by Blogger.
http://vinsappsr12setupsandimplblog.blogspot.in/2012/05/configuringmoac.html 2/2
