*LeAnn*

目前的公司現況為  

ORG =APPLE BG  è Business Group & HR ORG

ORG =APPLE A  è OU

現在又新增了二個 OU

ORG è APPLE B  = OU

ORG è APPLE C  = OU

結果因為 ”MO: Security Profile” Profile Site Level 設定為APPLE BG 則在個別的OU都可以看到所有OU的資料

就算你去設定 “MO: Operating Unit” 在各個Responsibility Level 也沒用

因為在R12中  系統會先去參照”MO: Security Profile” 設定 再去看 “MO: Operating Unit” 設定

對應資料要區分開這個問題

這二個OU必須要有屬於他們各自己Business Group  èAPPLE B & APPLE C

ORG è APPLE B  = OU & Business Group

ORG è APPLE C  = OU & Business Group

接著設定 ”MO: Security Profile” 在各個Responsibility Level 選取各自屬於的Business Group

則 各個OU 就只能看到各個OU中的資料了!

---------------------------------------------------------------------------------------------

一但設定好了之後  再進到Organization 查看 APPLE B & APPLE C 竟然查詢不到

爬了一下文  原來是要設定Profile : HR:Cross Business Group  è Yes

這樣  你又可以從Organization 中看到APPLE B & APPLE C 這二個ORG了

註1：”MO: Security Profile” Profile Site Level 不可為空值

以下為我的參考文件~

Profile : HR:Cross Business Group

Oracle Human Resources - Version: 10 and later   [Release: 10 and later ]
Oracle Human Resources - Version: 10 and later    [Release: 10 and later]

Oracle Human Resources Shared Install
PERWSDOH - Define Organization Hierarchy
What is proper setup of Cross Business Group Access for global?

organization hierarchy

Steps followed in Vision Database being used as an example:

CBGA Setup steps (Example only--using Vision Data):

1. Vision responsibilities:

Project Billing Super User, Progress S&L - Progress Master business group

2. Change profile option HR: Cross Business Group to 'Yes' at the site level.
Note: this changes the Business Group in System Implementation window to All.

3. Using Projects, Vision Services (USA) responsibility, create a Global
Security profile called 'GLOBAL'.

Note: Enable the View All Records checkbox in order to save the record.

3. Assign the 'GLOBAL' global security profile to the HR: Security Profile
profile option for the responsibility Projects, Vision Services (USA).

4. Using Projects, Vision Services (USA) responsibility, create a Global
Organization Hierarchy, starting with any organization as the top organization
and including organization across business groups. Vision has one called
Global
that includes organization from both Vision Corporation and Progress Master
business groups.

5. Assign the Global Organization Hierarchy in the System Implementation
window for Reporting, Project Setup and Expend/Costing hierarchies. Vision
setup assigns the Global hierarchy.

6. Assign Provider and Receiver controls in both business groups. (Only needed
if you're going to be doing Intercompany/Cross-Charge transactions)

7. Enable Cross-charge in the Multi-National Project and Task options for
projects and tasks to which customer will cross-charge. Example used was
Project 100000 and Task 1 in Progress Master


Additionally, once a global security profile is created and tied to the proper
Projects responsibility, you will be able to open the form and create a global
organization hierarchy. Then tie that organization hierarchy to the
implementation options.

MOAC

1.  Multi-Org Access Control, or MOAC, enables users to access multiple operating units from a single application responsibility.

2.  Operating unit security will be preserved such that companies can effectively implement security and shared services at the same time.

3.  Enhanced Multi-Org Reporting provides the ability to process and report critical financial information at different levels of the enterprise.

Prior to Release 12, each responsibility could access only one operating unit.  Therefore,
users who had to manage multiple operating units had to log in and log out of multiple
responsibilities to perform their tasks. In Release 12, users can perform tasks for multiple
operating units without changing responsibilities and its achieved by setting up MO: Security profile.

Usage Example:
In 11i, If a company had three operating units Belgium, Holland, and Denmark,
the company would have to create three responsibilities, one for each operating unit. 
And users, who had to enter invoices into all 3 operating units, had to log into each one
of the EMEA responsibilities separately. 
With Multi-Org Access Control in R12, each application responsibility can access multiple
operating units. The company can create a single EMEA responsibility for all three operating
units and users would only have to log in once to perform tasks such as: entering payables
invoices, viewing consolidated requisitions, performing collections, and processing receiving
and drop shipments.

It is required to set up either the MO: Operating Unit or MO: Security Profile profile option for
each application responsibility to use Multiple Organizations context sensitive applications.
If the MO: Security Profile is set, then the MO: Operating Unit profile is ignored.

Data security is maintained using security profiles that are defined for a list of operating units
and determine the data access privileges for a user When drilling down on balances
from Oracle General Ledger, General Ledger ignores the operating unit profile setting to
allow you to drill down to your subledger details, regardless of which operating unit originated
the transaction.

The OU field visible for all relevant transactions and relevant setups. 
On data entry, the system will derive the OU, when possible.  E.g.
if user enters a PO default invoice, the supplier site determines OU.



 

Setups

1.  Create Security Profile

2.  Run Security List Maintenance program

3.  Setup profile option MO: Security Profile

4.  Setup profile option MO: Default Operating Unit

Note: If a responsibility has to access only one operating unit, then set the profile option -
MO: Operating Unit. If a responsibility has to access multiple operating units, then define
a security profile with multiple operating units assigned and assign it to the
MO: Security Profile profile option