Multiple Organization Access Control (MOAC) is the ability to
access multiple operating units from a single application responsibility. Security
policies are attached to synonyms. Attaching security policy to synonyms makes
the synonym to be multi-org enabled. MOAC is an optional functionality. This functionality can not be implemented if
_ALL tables are used. If customizations
are using views (in 11i) R12 upgrade takes care of modifying all multi-org views
to synonym and security policies will take care of multiple operating unit
environment.
For Example:
In 11i
A table is in AR schema named
RA_CUSTOMER_TRX_ALL and a synonym named RA_CUSTOMER_TRX_ALL is created in APPS
schema, referring to AR.RA_CUSTOMER_TRX_ALL. A view RA_CUSTOMER_TRX is created
in APPS schema with CLIENT_INFO.
In R12
Table RA_CUSTOMER_TRX_ALL is in
AR schema and a synonym RA_CUSTOMER_TRX_ALL is created in APPS schema referring
AR.RA_CUSTOMER_TRX_ALL. Another synonym RA_CUSTOMER_TRX is created in APPS
schema referring RA_CUSTOMER_TRX_ALL. Using MO_GLOBAL.ORG_SECURITY package a
Row Level Security (RLS) is applied to RA_CUSTOMER_TRX synonym in APPS. Based
on MOAC setup oracle RLS will be applied dynamically to enforce filtering of
org_ids based on responsibility setup.
Based on the list provided
(output of the tool) MOAC is applicable for following objects. Depending on how we implement MOAC we may
have to change the referencing objects one way or other. Based on our study, implementing MOAC will
have lesser effort than not implementing MOAC.
Only object reference will change as column names are same between both
tables there may not be any changes to join conditions.
Access multi org using MOAC
|
Access multi org not using MOAC
|
AP_AE_HEADERS
|
AP_AE_HEADERS_ALL
|
AP_BANK_ACCOUNTS
|
AP_BANK_ACCOUNTS_ALL
|
AP_BANK_ACCOUNT_USES
|
AP_BANK_ACCOUNT_USES_ALL
|
AP_CHECKS
|
AP_CHECKS_ALL
|
AP_TAX_CODES
|
AP_TAX_CODES_ALL
|
AP_HOLDS
|
AP_HOLDS_ALL
|
AP_INVOICES
|
AP_INVOICES_ALL
|
AP_INVOICE_DISTRIBUTIONS
|
AP_INVOICE_DISTRIBUTIONS_ALL
|
AR_BATCHES
|
AR_BATCH_SOURCES_ALL
|
AR_BATCH_SOURCES
|
AR_BATCHES_ALL
|
AR_CASH_RECEIPTS
|
AR_CASH_RECEIPTS_ALL
|
AR_VAT_TAX_ALL_B
|
|
AR_PAYMENT_SCHEDULES
|
AR_PAYMENT_SCHEDULES_ALL
|
HZ_CUST_SITE_USES
|
HZ_CUST_SITE_USES_ALL
|
PO_ACCRUAL_ACCOUNTS_TEMP
|
PO_ACCRUAL_ACCOUNTS_TEMP_ALL
|
PO_ACCRUAL_WRITE_OFFS
|
PO_ACCRUAL_WRITE_OFFS_ALL
|
PO_DISTRIBUTIONS
|
PO_DISTRIBUTIONS_ALL
|
PO_HEADERS
|
PO_HEADERS_ALL
|
PO_LINES
|
PO_LINES_ALL
|
PO_LINE_LOCATIONS
|
PO_LINES_
LOCATIONS _ALL
|
PO_REQUISITIONS_INTERFACE
|
PO_REQUISITIONS_INTERFACE_ALL
|
PO_REQUISITION_HEADERS
|
PO_REQUISITIONS_HEADERS_ALL
|
PO_REQUISITION_LINES
|
PO_REQUISITIONS_LINES_ALL
|
PO_REQ_DISTRIBUTIONS
|
PO_REQ_DISTRIBUTIONS_ALL
|
PO_SYSTEM_PARAMETERS
|
PO_SYSTEM_PARAMETERS
_ALL
|
RA_CUSTOMER_TRX
|
RA_CUSTOMER_TRX_ALL
|
RA_CUSTOMER_TRX_LINES
|
RA_CUSTOMER_TRX_LINES_ALL
|
RA_BATCH_SOURCES
|
RA_BATCH_SOURCES_ALL
|
RA_CUST_TRX_TYPES
|
RA_CUST_TRX_TYPES_ALL
|
OE_ORDER_HEADERS
|
OE_ORDER_HEADERS_ALL
|
OE_ORDER_LINES
|
OE_ORDER_LINES_ALL
|
No comments:
Post a Comment
Thanks for your comments submitted.,will review and Post soon! by admin.