Multi-Org Access Control

Multi Org Concept:

Multi-Org: Multiple organization functionality in Oracle Applications. It enables operation of one or more organizations in a single instance.

 Benefits:

• Improve efficiency 
• Easily access data from different operating units 
• Improve Shared Services operations
• Provide more information for decision making by giving a Global consolidated view of data across operating units. 
  Ex: In Oracle Purchasing, users can now view global consolidated requisition demands for each supplier.  With this view, users are armed with the information to negotiate purchase discounts.
• Reduce Costs by cutting down processing time 

 MOAC functioning in various responsibilities :

 On using MOAC feature, user would be able to select desired OU from the LOV defined in the security profile.  

MULTI ORG Reporting:

Run reports for multiple operating units from a single responsibility.

BENEFITS

• Reduce processing time
• Improve efficiency
• Run reports for multiple operating units without switching responsibilities 

 

• Users can easily run reports for single or multiple operating units without having to switch application responsibilities.
• Users can quickly view global consolidated information for decision making purposes because manual consolidation of data is not required. This leads to increased efficiency at the Shared Service Centers time is not taken up with manual consolidation tasks and also, errors are avoided.

Multi-Organization Structure in Oracle Apps

What is Multi-Org?

Multi-Org is a server-side (applications and database) enhancement that enables multiple business units in an enterprise to use a single installation of Oracle Applications products while keeping transaction data separate and secure. 
The Multi-Org enhancement uses native database views to build a security layer on top of a single installation of Oracle Applications. In Oracle Applications the following products support Multi-Org capabilities: 

• Cash Management
• Order Management, Shipping Execution and Release Management
• Payables
• Property Manager
• Projects
• Purchasing
• Receivables
• Sales Compensation
• Sales and Marketing
• Service

Basic Business Needs:

The Multi-Org enhancement to Oracle Applications provides features necessary to satisfy the following basic business needs. You should be able to:

• Use a single installation of any Oracle Applications product to support any number of business units, even if those business units use different sets of books.
• Support any number of business units within a single installation of Oracle Applications.
• Secure access to data so that users can access only information that is relevant to them.
• Procure products from an operating unit that uses one set of book, but receive them from another operating unit using a different Ledgers.
• Sell products from an operating unit that uses one Ledgers, but ship them from another operating unit using a different Ledgers, automatically recording the appropriate inter-company sales by posting inter-company accounts payable and accounts receivable invoices.
• Report at any level of the organizational structure.

Organization Model:

The Multi-Org model provides a hierarchy that dictates how transactions flow through different business units and how those business units interact. You define the organizations and the relationships between them. 

Business Group

This is an Organization that represents the consolidated enterprise, a major division, or an operation company and has no accounting impact. The Business Group partitions Human Resources information and the Purchasing Approval Hierarchy. If you request a list of employees (in any module) you will see only those employees in the Business Group of which your Operating Unit is a part. Multiple Legal Entities can relate to a single Business Group. You must have at least one Business Group. 

Ledgers

A Ledger is a financial reporting entity that shares the  four Cs: a particular chart of accounts (accounting flexfield structure), functional currency, accounting convention and financial accounting calendar. The Ledger concept is similar in a Multi-Org environment. General Ledger secures transaction information (journal entries, balances) by Ledgers. When you use General Ledger, you choose a responsibility that specifies a Ledgers. You then see information only for that Ledgers.

Legal Entity

A legal entity represents a legal company for which you prepare fiscal or tax reports. You assign tax identifiers and other legal entity information to these types of organizations. Future enhancements will include greater functionality at this organization level.

Operating Unit

An operating unit represents an organization that uses any Oracle subledger application, for example, Order Management, Payables. It may be a sales office, a division, or a department. An operating unit is associated with a legal entity. Information is secured by operating unit for these applications. Each user sees information only for their operating unit. Responsibilities are linked to a specific operating unit by the MO: Operating Unit profile option.

Balancing Entity

This is an entity for which you prepare a balance sheet, represented as a balancing segment value in the Accounting Flexfield structure. There can be multiple balancing entities within the same operating unit structure and each of these must balance within itself. All required inter-company entries will be automatically created within the Ledgers to ensure companies can never be out of balance. A balancing segment could be a company or a division, for example.

Inventory Organization 

An inventory organization represents an organization for which you track inventory transactions and balances, and manufactures or distributes products. Examples include manufacturing plants, warehouses, distribution centers, and sales offices. The following products and functions secure information by inventory organization: Inventory, Bills of Material, Engineering, Work in Process, Master Scheduling/MRP, Capacity, and purchasing receiving functions. To run any of these products or functions, you must choose an organization that is classified as an inventory organization.

Sample Organization Structure:

Convert to Multi-Org:

After defining at least one operating unit, use ADADMIN to convert to Multi-Org. This step only needs to be perform one time. After ADADMIN is run, the Seed Data Replication program copies the applicable setup data delivered with Oracle Applications for each defined operating unit. 

Run ADADMIN to Convert to Multiple Org

When you select the adadmin option, Convert to Multiple Organization architecture, the Multi-Org switch is automatically turned on; a flag called multi_org_flag, is set to Y. The seed data replication program is then executed and processes according to the value of the multi_org_flag. 

Run Seed Data Replication 

Seed data is replicated under the following circumstances:

Submit the Replicate Seed Data concurrent request using the System Administrator responsibility.

The seed data replication program works in two modes:

All organizations: This mode applies when the seed data replication program is executed without an operating unit context.

Single organization: This mode applies when the seed data replication program is executed within the context of a particular operating unit (or Org_ID).

Perform Setups Unique to Each Operating Unit

Many setups must be repeated for each operating unit. For example:

• Supplier sites
• Customer addresses
• System options (System, Financial, Purchasing, Payables, etc.)
• Payment terms
• Tax names
• Price lists, discounts and quantity price breaks

Adding to the Organization Structure:

The Multi-Org enhancement allows you to add organizations at any time. 

E-Business Suite - Shared Entities

What are Shared Entities?

Shared entities are not formally defined within any single product's user guide. While you implement multiple products, you will find that the same entity is referenced by multiple products. 

• Shared entities enable one-time definition of an object and the use of that object across several products. 
• Shared entities are “owned” by a single product for table purposes only. 

Application Object Library (AOL)

Currencies: This must be enabled in AOL if you are performing a multicurrency implementation.

Languages: Languages that you are planning to deploy must be enabled in AOL.

Users: AOL provides the functionality of user creation. A user must have a username and the username must be assigned one or more responsibilities.

Responsibilities: Users are assigned responsibilities. The responsibility provides access to a particular module in the eBusiness Suite.

Menus: Responsibilities have menus associated to them. The menus determine the functions available to a user as well as what actions the users can perform.

Ledgers provides Oracle with a means to collect and quantify financial data. There are four primary elements to a Ledger:

Units of Measure 
Owner: Inventory
Units of Measure are the way that we quantify items. They are grouped into units of measure with similar characteristics by Unit of Measure Classes such as quantity, weight, time and volume.  The values defined in the Units of Measure window provide the list of values available in Unit of Measure fields in other applications windows.
Units of Measure are not inventory organization–specific


Items
Owner: Inventory
Items are parts that you buy or sell, or with which you transact. 
You choose whether to have centralized or decentralized control of your items through a variety of item attributes (such as description, lead time, unit of measure, lot control, saleable versus purchasable, and so on). 


Suppliers
Owner: Purchasing
Set up suppliers to record information about individuals and companies from whom you purchase goods and services. You can also enter employees whom you reimburse for expense reports. When you enter a supplier that conducts business from multiple locations, you store supplier information only once, and enter supplier sites for each location. You can designate supplier sites as pay sites, purchasing sites, RFQ only sites, or procurement card sites. 


Employees
Owner: Human Resources
Human Resources establishes employees to track personnel information such as skills, benefits, jobs, and statuses. After the employees are defined in the system, they can also be used for approval activities, processing expense transaction,s and the assigning of fixed assets.


Locations
Owner: Human Resources
Locations have various usages assigned to them, such as:
Bill to (where suppliers send invoices)  
Ship to (where suppliers send products)  
Office (identifies a business address where employees are located)


Organizations
Owner: Human Resources
An organization may be a physical site or it can represent a collection of sites sharing certain characteristics. These characteristics are used to define business structures within the Oracle e-Business environment: 
Legal Entity: The business units where fiscal or tax reports are prepared
Operating Unit: The level at which ERP transaction data is secured
Inventory Organization: A business unit such as a plant, warehouse, division, and so on
Expenditure/Event Organization: The unit that allows you to own events, incur expenditures, and hold budgets for projects

Oracle : E-Business Suite Intro

Oracle E-Business Suite is a comprehensive set of enterprise-wide business applications that runs entirely on the Internet. You can implement either one module or the entire suite. Oracle E-Business Suite helps an enterprise make smarter decisions with better information, share unified information across the enterprise, reduce IT expenses, and help run business more efficiently.

•  Automate key internal business processes
•  Extend automation and collaborate with your trading partners
•  Drive continuous improvement with real-time intelligence

Some of the Oracle Product Families are:

• Oracle Financials
• Customer Relationship Management Suite
• Project Management Product Suite
• Supply Chain Planning and Management Suite
• Manufacturing – Discrete and Process and Order Management
• Human Capital Management (HRMS, Payroll)

Architecture:

E-Business Suite has five principles that drive its Business Architecture. That architecture is driven around supporting and fulfilling business needs. Those principles are as follows:

1.E-Business Suite is built on a “modern foundation.” What this means is that Oracle is putting all of its new development into open, scalable standards. These standards include using Java/J2EE, HTML, Javascript, Internet-accessibility, and centralized management.

2.E-Business Suite is the first complete e-Business system. The E-Business Suite provides a complete enterprise-wide manufacturing, supply chain management, financial, project, human resource management, marketing, sales and service process solution. Because of that completeness, it is able to deliver a 360 degree view of the company.

3.EBS provides its completeness in a fully end-to-end integrated package. This is crucial to understanding the architecture. EBS integration is engineered into the product. It is not realized through systems integration/customizations.

4.It is fully globalized EBS is accessible via global networks. It accommodates multiple languages and currencies. It supports international features like flexible date formats and multiple radix support. And it has accounting and business localizations built into it.

5.It brings considerable tools to the implementation task. These tools include a rapid installation tool, patch application tools, and a host of configuration files and customizable help files to allow the customer to configure the system to meet their needs and they help to significantly reduce implementation time.

Technical Architecture:

The technical architecture is a direct response to the business needs. In supporting the business needs, four architectural modes to support the users have been developed. Those four architectural modes are accessed and controlled through the Personal Home Page (PHP) or Portal.

Forms-based users are typically people involved in the transactional operations of the organization. They are typically full-time users who need and demand a robust, full-featured interface.

Self-service users are typically infrequent users that want their interface with EBS to be as simple and quick as possible. Most users fall in this category.

Business intelligence users are typically senior executives who want an easy to use interface that can be used to reveal critical business information. By utilizing a browser, the business intelligence products eliminate the need for the users to learn a new system. If they are familiar with browsing, they know the basics of the business intelligence interface.

Finally, mobile users cover a surprisingly large range of users whose jobs are likely to keep them away from a readily available, network-connected computer. These users can range from sales people to inventory folks. By utilizing the mobile interface, they are able to send and receive information at points where it is important and convenient for them

Basic Technical Architecture of Oracle EBS

A tier is a logical grouping of services, potentially spread across more than one physical machine. Oracle E-Business Suite consists of a three tier architecture. The diagram represents the basic technical architecture of  E-Business Suite.

Desktop/Client tier: This tier provides the user interface. This tier could consist of a desktop computer, laptop or mobile devices like PDAs, and so on. This tier is mainly involved in capturing and displaying information to the user.

Application tier: This tier is responsible for holding all the application logic. It supports and manages various Applications components, and is sometimes known as the middle tier.

Database tier: This tier is responsible for storing and retrieving the application data. It supports and manages the Oracle database.