Multiple Organization Access Control

-



Setting Up Multiple Organization Access Control 


You can assign operating units to a security profile and then assign the security profile
to responsibilities or users. If multiple operating units are assigned to the security
profile, then a user can access data for multiple operating units from a single
responsibility. This ensures that users can only access, process, and report on data for
the operating units they have access to. You can limit users to information relevant to
their organization. For example, you can limit accounts payables clerks to enter invoices
associated exclusively with their operating unit.
Your responsibility determines which operating units you can access when you use
Oracle Applications. If you only want a responsibility to access only one operating unit,
then set the MO: Operating Unit profile option. If you want a responsibility to access
multiple operating units, then set the MO: Security Profile option and assign multiple
operating units to it. You can also set the MO: Default Operating Unit profile option to
specify a default operating unit that will default in transaction entry pages.
You can run your reports at the ledger level, or operating unit level. If you run reports
at the ledger level, then the report will submit data for all operating units assigned to
that ledger that you have access to as defined by the MO: Security Profile option. 

Reference:

Oracle E-Business Suite Multiple Organizations Implementation Guide


Example: Setting Up Multi Org Access Control for OM Responsibility:


The Security Profile Form allows you to group together Operating Units

Define the security profile for the Order Management Responsibility:
1. HRMS Manager> Security> Profile
2. Verify Security Profile is defined for the OM Responsibility.
3. If the Security Profile is not yet setup, enter it and attach operating units.
4. Save.


The Security List Maintenance Program Must be run each time you add or change Security Profiles.

 


There are three Profile Options you need to be aware related to Multi-Org that should be set at Responsibility Level.


- The R12 profile option 'MO: Security Profile' is always evaluated first.
- The pre- R12 option 'MO: Operating Unit' still works in R12. It's just a secondary priority being evaluated after 'MO: Security Profile'.
- The R12 profile option 'MO: Default Operating Unit' sets the default operating unit for transactions when running under a Security Profile.

Many R12 application modules do not work with 'MO: Security Profile' set for a given responsibility.

- They must use 'MO: Operating Unit'
- Some even require all three profile options set.

Examples:
     - CRM Modules
     - Certain GL Drilldown Functions
(Trial and error determination of setups, no clear direction) 



Now check Operating Units field in order screen.

Vision Operation defaults as operating unit  in the form per profile option setting for 'MO: Default Operating Unit' at responsibility level.



Comments

Post a Comment

Popular posts from this blog

Invoice Price Variance Process Accounting

-
Image
Invoice Price Variance Process Accounting: Note: Below Working and results are only applicable where Purchase Orders and Invoice are not routed through LCM Module. For LCM Enabled Items IPVs are routed and transferred to Inventory directly from LCM. Invoice Price Variance is variance between the invoice price and the purchase price for all inventory and work in process related invoice distributions. Payables records invoice price variances when the invoices are matched, approved, and posted. This Article covers the detail Accounting for Oracle Invoice Price Variance Process and also its effect on item Unit Cost in Inventory. Let's Put up a scenario here. We will be receiving an item in Inventory which has currently no On Hand Balance or Unit Cost in Inventory. We Booked a Purchase Order for Quantity 100 at Unit Price of BDT 10 . We did the Receipt of the booked Quantity 100 at 01-August-2014 and receipt delivery was made on same date with all quantity acce...
Read more

Query to Find Out Move Order Number for Work Order with Transacted Quantity

-
Query to Find Out Move Order Number for Work Order with Transacted Quantity: There could be scenarios where for some reason you need to know Move Order number for Work Order Material Line which has be transacted. Once quantity is transacted, no record exists for that move order number to be found. The below query can be used to find out All Move Order Numbers generated for that relevant Work Order. SELECT a.REQUEST_NUMBER, mmt.TRANSACTION_SOURCE_ID, mmt.TRANSACTION_SOURCE_NAME, mmt.* FROM mtl_material_transactions mmt, mtl_txn_request_lines b, mtl_txn_request_headers a, wip_entities w WHERE --mmt.transaction_id = 55356941 --AND mmt.move_order_line_id = b.line_id AND b.header_id = a.header_id and mmt.TRANSACTION_SOURCE_ID = w.WIP_ENTITY_ID and w.WIP_ENTITY_NAME = ' WO30683'       "Change Work Order Number to Relevant Work Order"  Special Thanks to Waqas Munir (PwC Pakistan)  
Read more

DISALLOW USER TO CANCEL PO LINE IF QUANTITY RECEIVED

-
In Oracle EBS R12, currently system allow user to Cancel PO Line even if quantity is received against the PO Line (Partial/Full). Oracle explains this functionality in following note: WHY DOES APPLICATION ALLOW You TO CANCEL A PO LINE WHEN FULLY RECEIVED? (Doc ID 93690.1) For few businesses scenario is not same and admin needs to restrict user to cancel PO Lines against which there is received quantity. Following personalizations on Purchase Order Entry Form helps to serve the business need. PERSONALIZATION 01 Seq Description 10 SMA-LOCK CANCEL PURCHASE LINE BUTTON IF RECEIPT EXISTS Condition Triger Event WHEN-NEW-ITEM-INSTANCE Triger Object PO_DOCON_CONTROL.ACTION Condition :PO_LINES.TOTAL_QUANTITY_RECEIVED is not Null and :PO_LINES.TOTAL_QUANTITY_RECEIVED >0 Actions Seq 10 Type Property Object Type Item Target Obj...
Read more