转载出处：http://blog.csdn.net/pan_tian/article/details/7774715
MOAC的实现原理-VPD技术
MOAC的实现是通过Oracle数据库的VPD(Virtual Private Database)技术来实现的。VPD技术提供了数据库对象（表，同义词，视图）行级别访问的控制。使用VPD技术可以有效地限制用户获取数据的范围。
Secooler 的一篇文章 使用Oracle VPD（Virtual Private Database）限制用户获取数据的范围 讲VPD，里边的例子非常容易理解.
- --1.Create Data
- create table t (x number);
- insert into t values (1);
- insert into t values (2);
- insert into t values (10001);
- insert into t values (10002);
- commit;
- select * from t;
- output:
- 1
- 2
- 10001
- 10002
-
- --2.Create VPD FUNCTION
- CREATE OR REPLACE FUNCTION f_limited_query_t (s_schema IN VARCHAR2,
- s_object IN VARCHAR2)
- RETURN VARCHAR2
- AS
- BEGIN
- RETURN 'X <= 10000';
- END;
-
-
- --3.Register VPD Policy.
- BEGIN
- DBMS_RLS.add_policy (object_schema => 'APPS',
- object_name => 'T',
- policy_name => 'POLICY_LIMITED_QUERY_T',
- function_schema => 'APPS',
- policy_function => 'F_LIMITED_QUERY_T');
- END;
-
-
- select * from t;
- output:
- 1
- 2
对于上边例子，我们对表T使用了VPD技术，引入了表限制Function f_limited_query_t，这样我们通过function限制了对表的查询，查询结果只返回小于10000的数字。
如何查看我们是否对某张表使用了VPD技术
SELECT * FROM DBA_POLICIES WHERE object_name = 'T';
查询结果中，其中Pakcage + Function就是我们对于表所加的限制。
那么Oracle EBS是如何使用VPD技术来实现多组织的
R12里,以PO表为例，PO_HEADERS_ALL是基础表(PO/APPS Scehma)，PO_HEADERS是PO_HEADERS_ALL对应的Synonym对象(Apps Schema),我们对PO_HEADERS应用VPD技术.MO_GLOBAL-Dive into R12 Multi Org Design 有较为详细的说明，
In pre Release 12, you would have had following methodology for PO_HEADERS_ALLa. A table is created in PO Schema, named PO_HEADERS_ALLb. A synonym named PO_HEADERS_ALL is created in APPS schema, referring to PO.PO_HEADERS_ALLc. Create a view PO_HEADERS in APPS schema, as "select * from po_headers_all where org_id=client_info"
But now in R12, following will happena. A table is created in PO Schema, named PO_HEADERS_ALLb. A synonym named PO_HEADERS_ALL is created in APPS schema, referring to PO.PO_HEADERS_ALLc. Another synonym named PO_HEADERS is created in APPS, referring to PO_HEADERS_ALLd. A Row Level security is applied to PO_HEADERS, using package function MO_GLOBAL.ORG_SECURITY.This can be double-checked by running SQL select * from all_policies where object_name='PO_HEADERS'e. The effect of this policy is that,whenever you access PO_HEADERS, Oracle RLS will dynamically append WHERE CLAUSE similar to belowSELECT * FROM PO_HEADERS WHERE EXISTS (SELECT 1 FROM mo_glob_org_access_tmp oa WHERE oa.organization_id = org_id)
可以看到，我们对表PO_HEADERS加了MO_GLOBAL.ORG_SECURITY限制，MO_GLOBAL.ORG_SECURITY的作用实际上就是根据你关于MOAC Profiles的设置，然后转换为相应Where条件(组织过滤)，再进行查询。
对于VPD表的查询
对于VPD表，简单的查询一般是不返回记录的，如果想查到记录，需要设置一下上下文先
--普通查询VPD表
select * from PO_HEADERS;--No Output
--Single OU Mode
BEGIN execute mo_global.set_policy_context('S',204); --204为ORG_ID,S表示Single Org ContextEND;select * from PO_HEADERS;--会输出OU：204下边的所有PO
--Multiple OU Mode(simulate login to a specific responsibility)
a. Call fnd_global.apps_initialize(userid,resp_id,resp_appl_id);
b. call MO_GLOBAL.INIT(p_appl_short_name);This will read the MO profile option values for your responsibility/user, and will initialize the Multi Org Access.
c.select * from po_headers
MOAC API
What is the purpose of MO_GLOBAL.ORG_SECURITY?
The purpose of Row-Level-Security is to hide certain data[based on some conditions]. RLS does so by appending a where clause to the secured object.1. MO_GLOBAL.ORG_SECURITY is a function that returns a predicate for the WHERE CLAUSE2. The where clause will be appended to Table/Synonym/View for which Multi Org Row Level security is enabled
What is the purpose of MO_GLOBAL.SET_POLICY_CONTEXT ?
This procedure has two parameters p_access_mode Pass a value "S" in case you want your current session to work against Single ORG_ID Pass a value of "M" in case you want your current session to work against multiple ORG_ID's p_org_id Only applicable if p_access_mode is passed value of "S"
MOAC相关的查询语句
Security Profile Definiation
- SELECT *
- FROM per_security_profiles
- WHERE security_profile_name = 'PTIAN_SECURITY_PROFILE';
check Organization which are related to a profile
- select PPO.*
- from PER_SECURITY_PROFILES PPR,
- PER_SECURITY_ORGANIZATIONS PPO
- where PPR.security_profile_id = PPO.security_profile_id
- and security_profile_name like '%PTIAN_SECURITY_PROFILE%';
- set long 10000
- set pagesize 500
- set linesize 160
- column SHORT_NAME format a30
- column NAME format a40
- column LEVEL_SET format a15
- column CONTEXT format a30
- column VALUE format a40
- select p.profile_option_name SHORT_NAME,
- n.user_profile_option_name NAME,
- decode(v.level_id,
- 10001, 'Site',
- 10002, 'Application',
- 10003, 'Responsibility',
- 10004, 'User',
- 10005, 'Server',
- 10006, 'Org',
- 10007, decode(to_char(v.level_value2), '-1', 'Responsibility',
- decode(to_char(v.level_value), '-1', 'Server',
- 'Server+Resp')),
- 'UnDef') LEVEL_SET,
- decode(to_char(v.level_id),
- '10001', '',
- '10002', app.application_short_name,
- '10003', rsp.responsibility_key,
- '10004', usr.user_name,
- '10005', svr.node_name,
- '10006', org.name,
- '10007', decode(to_char(v.level_value2), '-1', rsp.responsibility_key,
- decode(to_char(v.level_value), '-1',
- (select node_name from fnd_nodes
- where node_id = v.level_value2),
- (select node_name from fnd_nodes
- where node_id = v.level_value2)||'-'||rsp.responsibility_key)),
- 'UnDef') "CONTEXT",
- v.profile_option_value VALUE
- from fnd_profile_options p,
- fnd_profile_option_values v,
- fnd_profile_options_tl n,
- fnd_user usr,
- fnd_application app,
- fnd_responsibility rsp,
- fnd_nodes svr,
- hr_operating_units org
- where p.profile_option_id = v.profile_option_id (+)
- and p.profile_option_name = n.profile_option_name
- and upper(p.profile_option_name) in ( select profile_option_name
- from fnd_profile_options_tl
- where upper(user_profile_option_name)
- like upper('%MO: Security Profile%'))
- and usr.user_id (+) = v.level_value
- and rsp.application_id (+) = v.level_value_application_id
- and rsp.responsibility_id (+) = v.level_value
- and app.application_id (+) = v.level_value
- and svr.node_id (+) = v.level_value
- and org.organization_id (+) = v.level_value
- order BY short_name, user_profile_option_name, level_id, level_set;
支持MOAC功能的Form开发步骤
这部分摘自:http://bbs.erp100.com/thread-103395-1-1.html
在R12版本中，OU的控制采取了MOAC的方式，使用户的操作得到了改善。
而如果客户化的Form能够支持MOAC的功能，需要在界面上提供当前用户可以选择的OU字段供用户选择。
功能展示如下图：
这样在Form的开发过程中需要如下的开发步骤：
1,PRE-FORM 触发器初始化MOAC配置环境
添加如下代码：
MO_GLOBAL.init(‘ONT’);
— global.mo_ou_count
— global.mo_default_org_id
— global.mo_default_ou_name
IF l_default_org_id IS NOT NULL THEN — default org id not null
MO_GLOBAL.SET_POLICY_CONTEXT(‘S’,l_default_org_id);
ELSE
MO_GLOBAL.SET_POLICY_CONTEXT(‘M’,null);
END IF; — default org id not null
这段代码的作用是根据预制文件的设置，初始化OU的信息，将用户可以访问的OU信息插入到mo_glob_org_access_tmp表中，
同时将默认的OU ID、OU Name和OU Count分别写到global.mo_default_org_id, global.mo_default_org_id, global.mo_default_ou_name
具体细节可以查看数据库包：mo_global
2,WHEN-CREATE-RECORD触发器中拷贝OU默认值
在此触发器中将默认的OU ID和OU Name拷贝给Form界面上对应的自动，实现创建记录的时候默认带出默认OU信息。
copy(name_in(‘global.mo_default_org_id’),’’);
copy(name_in(‘global.mo_default_ou_name’),’’);
3,创建OU的LOV
Form界面上的OU 名称字段创建一个LOV，LOV对应记录组的SQL语句如下：
SELECT hr.organization_id organization_id, hr.NAME organization_name
FROM hr_operating_units hr
WHERE mo_global.check_access(hr.organization_id) = ‘Y’
ORDER BY organization_name
其它没有特殊的步骤。
MindMap
参考：
Oracle Applications Multiple Organizations Implementation Guide
EBS R12 MOAC(Multi-Org Access Control)原理探索
MO_GLOBAL-Dive into R12 Multi Org Design
FAQ - Multiple Organizations Architechure (Multi-Org) (Doc ID 165042.1)
Note 745420.1 -How To Setup And Check MO / MOAC Setup In APPS Instance At R12 Level - Precedence of MO - MOAC Profile Options
Best Practices for Securing the E-Business Suite [ID 189367.1]
Best Practices For Securing Oracle E-Business Suite Release 12 [ID 403537.1]
Understanding and Using HRMS Security in Oracle HRMS [ID 394083.1]
Security List Maintenance for All Profiles Is Excluding Employees [ID 755410.1]
Effect Of Security List Maintenance Concurrent Request within the Oracle HRMS Module [ID 457629.1]
