R12 Multi-Org Access Control - Setups

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 10

R12 Multi-Org Access Control - Setups

Written on Feb-9-09 2:20am - Not yet published to a wikizine


From:  realworldoracleapps.blogspot.com

Multi-Org Access Control Setup:

•Responsibility: Human Resources


•Navigation: Security > Profile
In Release 12, when you define your security profile in HR using the Security profile form or the
Global Security profile form, you must:
•Assign all of the operating units that you want a responsibility to access. Run a concurrent request
called “Run Security List Maintenance” from HR which makes those security profile available and
allows you to assign them to a responsibility via a profile option called MO: Security Profile.

Multi-Org Access Control – Setup – Create Operating Unit:


•Responsibility: General LedgerNavigation: Accounting Setup Manager > Financials : Accounting
Setup : Accounting Setup Manager

•Responsibility: Human Resources:Navigation: Work Structures : Organization > Description


In Release 12, you can define your operating units in two places. You can continue to define them in
the Oracle HRMS Organization Form or you can define them in the new Accounting Setup Manager
feature in General Ledger.

The Accounting Setup Manager streamlines the setup and implementation of Oracle Financial
Applications. It centralizes the setup and maintenance of common financial components, such as
legal entities, operating units, and ledgers. So when you create an accounting setup, assign a legal
entity and create the ledgers that will perform the accounting for that legal entity, you can also define
and assign the relevant operating units. By leveraging Accounting Setup Manager to define your
OUs, you can streamline your setup.

In R12, is instead of attaching an OU to a LE, you assign it to a default legal context. All Release 11i
HR Organizations classified as “Operating Units” will be preserved in Release 12. If operating units
are assigned to a set of books, then they will be associated to a primary ledger in an accounting
setup. You will be able view all operating units assigned to an upgraded primary ledger using
Accounting Setup Manager.
Multi-Org Access Control – setup Define Security Profile:
•Responsibility: Human Resources
•Navigation: Security : Profile or
•Navigation: Security : Global
Using Oracle HRMS, you can define your security profile using two forms:
•The Security Profile form, which allows you to select operating units from only one Business Group
•The Global Security Profile form, which allows you to select operating units from multiple Business
Groups

Enter a name, and select the Security Type called “Secure organizations by organization hierarchy
and/or organization list”. This allows you to assign multiple OUs.

When assigning operating units, first select classification Operating Unit, and then select the
organization or Operating Unit name. You can assign multiple operating units.

Multi-Org Access Control – Setup – Run System List Maintenance:

•Once the security profile has been created, run the Security List Maintenance program.
–This ensures that all of the security profiles that you created are available for assignment to your
responsibilities.

Multi-Org Access Control – Setup – System Profile Options:

•The MO Security Profile controls the list of operating units that a responsibility or user can access. If
you set the security profile at the responsibility level, then all users using that responsibility will have
access to only the operating units available in the security profile. If you set the security profile at the
user level, then the user will have access to only those operating units, irrespective of application
responsibility that they log into.

•The MO: Default Operating Unit is optional and allows you to specify a default operating unit that
defaults when you open different subledger application pages. Because you can access multiple
operating units, you may want to set up a default one instead of forcing users to constantly have to
choose one. User Preferences allows you to specify a default operating unit at the user level. Use
the MO: Default Operating Unit profile option to set the operating unit context or default operating
unit when accessing an applications.

•The last profile option is for backwards compatibility and to support products that do not use
Multiple Organizations. The release 11i setting was for this is preserved during upgrade. The
Release 11i MO: Operating Unit profile option is supported in Release 12 as not all customers of
Oracle products require multiple organizations.

Implementation Considerations:

•Oracle HRMS
–Define operating units
–Set up Multi-Org Security Profiles
•Accounting Setup Manager
–Define operating units
–View all operating units assigned to the primary ledger
•Oracle E-Business Suite Products that Use Operating Units
–Process data across multiple operating unitsusing Multi-Org Access Control

R12 Multi-Org Access Control - features and benefits


Written on Feb-9-09 2:15am - Not yet published to a wikizine
From:  realworldoracleapps.blogspot.com

Multi-Org Access Control - Description:

In 11i, when users had to enter or process data for multiple operating units, they had to login to
different responsibilities because each responsibility could only access one operating unit. So if
there were a centralized payment processing center where users processed payments for multiple
organizations, they would have to keep logging in and out of different responsibilities to process
payments for a different organization or operating unit.

Now in Release 12, Multi-Org Access Control enables companies that have implemented a Shared
Services operating model to efficiently process business transactions by allowing users to access,
process, and report on data for an unlimited number of operating units within a single application’s
responsibility.

This increases the productivity of Shared Service Centers as users no longer have to switch
application responsibilities when processing transactions for multiple operating units. Data security
and access privileges are still maintained using security profiles that will now support multiple
operating units.

Multi-Org Access Control - Example:

For example, if you have three operating units in the center you were managing, such as a Belgium
Operating Unit, a Holland Operating Unit, and a Denmark operating unit, in 11i you needed to define
three different responsibilities. If you had one user who processed payables invoices across all three
operating units, then you would need to assign the three responsibilities to that user and then the
user would need to log in and out of each responsibility to process invoices.

In Release 12, you can create a Security Profile and assign as many operating units as you want to
that security profile. So in this example, you could assign all three operating units to the same
security profile. Then, you can tie that security profile to a single responsibility using a profile option
called MO: Security Profile. For example, you could assign the security profile to the EMEA
Payables responsibility to allow that responsibility to process invoices across all three operating
units.

Processing payables invoices is just one example, with Multi-Org Access Control, you can efficiently
perform other processes, such as processing receivables invoices, viewing consolidated
requisitions, performing collections using Advanced Collections, and process receiving and drop
shipments.

MOAC - Benefits:

•Improve Efficiency
–Process data across multiple OUs from one responsibility
–Process transactions more efficiently for companies that have centralized business functions or
operate Shared Service Centers
•Obtain better information for decision making
–Obtain a global consolidated view of information
–View information, such as supplier sites and customer sites across multiple OUs
•Reduce Costs
–Speed data entry
–Reduce setup and maintenance of many responsibilities
Multi-Org Access Control Process Summary:

Each Financials product team has implemented MOAC to best suit their business process flows. For
example, in AP, there’s a new operating unit field on their Invoice Workbench. The OU list of values
reads from the Security Profile assigned to the responsibility to determine which OUs should be
displayed in the LOV. In general, when a user logs in to a responsibility and opens an application,
the application will determine which operating units can be accessed and used for processing. The
user can then view or process transactions for multiple operating units.

Oracle E-Business Tax (eBTax):


consists of a tax knowledge base, a variety of tax services that respond to specific tax events, a set
of repositories (for tax content and tax recording) that allow customers to manage their local tax
compliance needs in a proactive manner, as well as the ability to integrate with external tax content
providers through a single integration point.

Advanced Global Intercompany System:


•Addresses the Top Barrier to a Fast Close
•Generates subledger invoices
•Controls transaction entry with Intercompany Calendar
•Has a Fully Configurable Approval Rules
•Has a Flexible Security Model
•Has a Centrally defined Intercompany Accounts

Centralized Banking:
•Bank account is now associated with the LE instead of the Operating Unit
•A single bank account serves multiple Operating Units
•Any and all Operating Units associated with a ledger can be permitted to use the bank account
•There is a centralized Credit Card Model
•There is Credit Card Encryption
•The Supplier & Customer Banks are in TCA

Multi-Dimensional Analysis & Reporting:


•In product row/column UI or within a Spreadsheet
•You can create the following reports & graphs:
– Historical
– Current
– Projected data
•You can analyze performance:
– Detect trends
– Define
– Variance
– Thresholds
•Receive auto-alerts

Financial Consolidation Hub:


R12 includes interactive spreadsheet reporting with live drill down to transactions

XML Publisher:
Enables you to format, manage, and deliver documents
•Meets business requirements such as:
-Removes complexity
-Reduces maintenance cost
-Reduces TCO
•Integrated with: R9 CRM, ESA, FMS, HCM, and SCM

New Standard Reports:


•Uses XML Publisher
•835 Templates are available
•Merges custom templates and data extracts at run-time
•Delivers output in PDF, HTML, RTF, Excel (HTML), or text for use with EFT and EDI transmissions
•98 Global reports have been replaced with 19 Extracts, 86 Templates

Other new features:

•Live AR-Inventory. Revenue-COGS Match


•Deferred COGS and Revenue Automation
•Advanced collection, Dunning, Loans
•Invoice Lines
•Suppliers in TCA: one setup per partner
•Supplier, users invoice self service
•Straight through processing (STP) at banks
•Per diems, approval enhancements
•Expense Bar Codes
•Self Service receipt matched invoices
•Real time contract T&Cs in PO, AP
•Asset Automatic Depreciation Rollback

R12 Financials Overview and new features at a glance (PART 1)


Written on Feb-9-09 1:48am - Not yet published to a wikizine
From:  realworldoracleapps.blogspot.com
Why R12:

Release 12 is defined as “The Global Business Release.” Global is not just a geographic
perspective, but also a comprehensive perspective; release 12 functionality spans across both
industries and business functions.
•Flexible, centralized, global accounting structure
•300+ enhancements to best practice business processes
•Comprehensive governance, risk and compliance platform
•Truly integrated performance management
•Real-time profitability analysis
•Unified financial and operational analytic applications
•Integration with core industry applications
•Self-service report formats and publicationSuperior ownership experience

New architecture and benefits:

The major components of the new architecture include:


•Multi-Org Access Control
•Ledger and Ledger Sets
•Subledger Accounting
•Tax Engine
•Intercompany
•Bank Model

Benefits of the new architecture include:


•Maintain 1 Ledger with 1 OU for each Company (LE)
-Get privacy for each company’s data
-Manage each company’s national and local compliance
•Combine many companies’ ledgers in a set
-Share GL services and workload
-Get combined data
•Use MOAC to enable access to many OUs
-Process in and report across many Companies’ Operating Units

MOAC: Multi-Org Access Control:


MOAC provides role based access to Operating Units, and allows you to perform multiple tasks
across operating units without changing responsibilities.

Subledger Accounting:
Subledger accounting provides centralized rules and a common repository, and global control of
your accounts. Features include:
•Accounting Rules
-SarBox & 8th Dir.
-User Editable
•Subledger Daybooks (Journals)
•Subledger Balancing
•Reports, inquiries, open items, et cetera
•Multiple Representations
•Common Posting to GL Ledgers
•Real time or Periodic

Benefits of subledger accounting are:


•Faster, Easier Reconciliation
•Corporate Rules = Accounting Standardization
•Local Rules = Improved Local Compliance
•Automate “Apples to Apples” Adjustments
•Improved Audit- ability
•Improved Internal Control

Ledger:

•One Repository of Financial Truth


•Implements the 4 C’s:
–Chart of Accounts
–Currency
–Calendar
–Accounting Convention
•Example:
–The balance on Creditors (COA)
–is 4.2M Eur (Currency)
–on March 31, 2006 (Calendar)
–according to IAS/IFRS definitions (Accounting Convention)

Ledger Sets:
Ledger sets provide global information at a glance. Ledger sets share a chart of accounts and a
calendar. The key benefits to many Ledgers in one set are:
•Decision-driving business information always available
•Simpler processing and General Ledger management
•Data and definitions that can be shared and secured

Ledger Architecture:
Typical Ledger Sets:
•All IAS/IFRS or US GAAP ledgers
•26 Subs in 1 country
•35 countries in 1 region

Legal Organization:
Legal Entities (Les) such as Parent companies, own or control subsidiaries. There are no group
entities
•LEs pay the taxes and therefore need tax registrations
•Trade between LEs needs intercompany
•LEs own the money and bank accounts
•LEs file the accounts and take care of accounting
•LEs comply with whatever needs compliance: “legal” in LE

Enhanced Legal Support:


•Did not replace GRE/LE - employer
•Added TCA parties for the Authorities
•Added a Legal Entity Configurator
•Introduced the following new terms:
-Jurisdiction: A legislative category and territory, has legal rules
-Legal Authority: Legal body who enforces legislation, collects fees / taxes, etc
-Legal Function: Functions that companies are required to perform (e.g. produce yearly report, pay
taxes, etc.)
-Legal Associations: Mapping companies to Ledgers, BSVs, OUs and other system entities

Examples of using Legal Entities:


•Accounting Setup Manager: Assign books, bookkeeping rules and currency management to your
registered companies
•EBusiness Tax: Have your registered companies calculate, file, and pay the transaction taxes they
owe
•Intercompany: Do business between and across your registered companies with full legal
documentation
•Bank Model: Have your registered companies use their money to pay their bills, etc.

You might also like