Académique Documents
Professionnel Documents
Culture Documents
Applications Cloud
Understanding Enterprise
Structures
Authors: Kathryn Wohnoutka, Asra Alim, Marilyn Crawford, Alison Firth, Daniela Kantorova, Barbara Snyder, Megan Wallace
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by
intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast,
modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or
decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to
us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following
notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/
or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation
and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating
system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions
applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in
any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle
Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or
registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of
Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation
and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle
Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products,
or services.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=docacc
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Applications Cloud
Understanding Enterprise Structures
Contents
Preface i
1 Enterprise Structures 1
Enterprise Structures: Overview ................................................................................................................................ 1
Enterprise Structures Business Process Model: Explained ........................................................................................ 3
Using Single or Multiple Classifications for an Organization: Points to Consider ......................................................... 6
Configuration Workbench: Explained ......................................................................................................................... 6
Global Enterprise Configuration: Points to Consider .................................................................................................. 7
Modeling Your Enterprise Structure in Oracle Fusion: Example ................................................................................. 8
2 Enterprises 11
Enterprise: Explained ............................................................................................................................................... 11
4 Legal Entities 15
Legal Entities: Explained ......................................................................................................................................... 15
Legal Entity in Oracle Fusion: Points to Consider .................................................................................................... 16
What's a payroll statutory unit? .............................................................................................................................. 19
What's a legal employer? ....................................................................................................................................... 19
What's a tax reporting unit? ................................................................................................................................... 19
Planning Legal Reporting Units: Points to Consider ................................................................................................ 19
Designing an Enterprise Configuration: Example ..................................................................................................... 20
Oracle Applications Cloud
Understanding Enterprise Structures
8 Facilities 49
Item Master Organization: Explained ....................................................................................................................... 49
Item Organization: Explained ................................................................................................................................... 50
Inventory Organization: Critical Choices .................................................................................................................. 50
Cost Organization: Explained .................................................................................................................................. 52
Oracle Applications Cloud
Understanding Enterprise Structures
9 Reference Data 53
Reference Data Sets and Sharing Methods: Explained ........................................................................................... 53
What reference data objects can be shared across business units? ....................................................................... 54
What reference data objects can be shared across asset books? .......................................................................... 56
What reference data objects can be shared across cost organizations? ................................................................. 57
What reference data objects can be shared across project units? .......................................................................... 58
Items and Supplier Site Reference Data Sharing: Explained .................................................................................... 58
Preface
This Preface introduces information sources available to help you use Oracle Applications.
Note
If you don't see any help icons on your page, click the Show Help button in the global area. Not all pages have
help icons.
• Oracle Applications Help, and select Documentation Library from the Navigator menu.
• http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://
www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
i
Oracle Applications Cloud Preface
Understanding Enterprise Structures
• Click your user name in the global area of Oracle Applications Help, and select Send Feedback to Oracle.
ii
Oracle Applications Cloud Chapter 1
Understanding Enterprise Structures Enterprise Structures
1 Enterprise Structures
• Industry
• Business unit requirements for autonomy
• Business and accounting policies
• Business functions performed by business units and optionally, centralized in shared service centers
• Locations of facilities
Every enterprise has three fundamental structures, legal, managerial, and functional, that describe its operations and provide
a basis for reporting.
In Oracle Fusion, these structures are implemented using the chart of accounts and organization hierarchies. Although many
alternative hierarchies can be implemented and used for reporting, you are likely to have one primary structure that organizes
your business into divisions, business units, and departments aligned by your strategic objectives.
Legal Structure
The figure above shows a typical group of legal entities, operating various business and functional organizations. Your ability
to buy and sell, own, and employ comes from your charter in the legal system. A corporation is:
1
Oracle Applications Cloud Chapter 1
Understanding Enterprise Structures Enterprise Structures
There are many other kinds of legal entities, such as sole proprietorships, partnerships, and government agencies.
A legally recognized entity can own and trade assets and employ people in the jurisdiction in which it is registered. When
granted these privileges, legal entities are also assigned responsibilities to:
• Account for themselves to the public through statutory and external reporting.
• Comply with legislation and regulations.
• Pay income and transaction taxes.
• Process value added tax (VAT) collection on behalf of the taxing authority.
Many large enterprises isolate risk and optimize taxes by incorporating subsidiaries. They create legal entities to facilitate legal
compliance, segregate operations, optimize taxes, complete contractual relationships, and isolate risk. Enterprises use legal
entities to establish their enterprise's identity under the laws of each country in which their enterprise operates.
In the figure above:
For example, a group might have a separate company for each business in the United States (US), but have their United
Kingdom (UK) legal entity represent all businesses in that country.
The divisions are linked across the cards so that a business can appear on some or all of the cards. For example, the air
quality monitoring systems business might be operated by the US, UK, and France companies. The list of business divisions
is on the Business Axis.
Each company's card is also horizontally striped by functional groups, such as the sales team and the finance team. This
functional list is called the Functional Axis. The overall image suggests that information might, at a minimum, be tracked
by company, business, division, and function in a group environment. In Oracle Fusion Applications, the legal structure is
implemented using legal entities.
Management Structure
Successfully managing multiple businesses requires that you segregate them by their strategic objectives, and measure their
results. Although related to your legal structure, the business organizational hierarchies do not need to be reflected directly in
the legal structure of the enterprise. The management structure can include divisions, subdivisions, lines of business, strategic
business units, profit, and cost centers. In the figure above, the management structure is shown on the Business Axis. In
Oracle Fusion Applications, the management structure is implemented using divisions and business units as well as being
reflected in the chart of accounts.
Functional Structure
Straddling the legal and business organizations is a functional organization structured around people and their competencies.
For example, sales, manufacturing, and service teams are functional organizations. This functional structure is represented
by the Functional Axis in the figure above. You reflect the efforts and expenses of your functional organizations directly on
the income statement. Organizations must manage and report revenues, cost of sales, and functional expenses such as
research and development (R&D) and selling, general, and administrative (SG&A) expenses. In Oracle Fusion Applications,
the functional structure is implemented using departments and organizations, including sales, marketing, project, cost, and
inventory organizations.
2
Oracle Applications Cloud Chapter 1
Understanding Enterprise Structures Enterprise Structures
• Set Up Enterprise Structures business process, which consist of implementation activities that span many product
families.
• Information Technology, a second Business Process Model which contains the Set Up Information Technology
Management business process.
• Define Reference Data Sharing, which is one of the activities in this business process and is important in the
implementation of the enterprise structures. This activity creates the mechanism to share reference data sets across
multiple ledgers, business units, and warehouses, reducing the administrative burden and decreasing the time
needed to implement.
3
Oracle Applications Cloud Chapter 1
Understanding Enterprise Structures Enterprise Structures
The following figure and chart describes the Business Process Model structures and activities.
Define Enterprise Define the enterprise to get the name of the deploying
enterprise and the location of the headquarters.
4
Oracle Applications Cloud Chapter 1
Understanding Enterprise Structures Enterprise Structures
Define Legal Jurisdictions and Authorities Define information for governing bodies that operate
within a jurisdiction.
Define Legal Entities Define legal entities and legal reporting units for business
activities handled by the Oracle Fusion Applications.
Define Chart of Accounts Define chart of accounts including hierarchies and values
to enable tracking of financial transactions and reporting
at legal entity, cost center, account, and other segment
levels.
Define Ledgers Define the primary accounting ledger and any secondary
ledgers that provide an alternative accounting
representation of the financial data.
Define Reference Data Sharing Define how reference data in the applications is
partitioned and shared.
5
Oracle Applications Cloud Chapter 1
Understanding Enterprise Structures Enterprise Structures
Note
There are product specific implementation activities that are not listed here and depend on the applications you
are implementing. For example, you can implement Define Enterprise Structures for Human Capital Management,
Project Management, and Sales Management.
Related Topics
• Modeling Your Financial Reporting Structure in Oracle Fusion: Example
6
Oracle Applications Cloud Chapter 1
Understanding Enterprise Structures Enterprise Structures
• Enterprise Configuration
• Business Unit Management
• Security Structure
• Compliance Requirements
Enterprise Configuration
• What is the level of configuration needed to achieve the reporting and accounting requirements?
• What components of your enterprise do you need to report on separately?
• Which components can be represented by building a hierarchy of values to provide reporting at both detail and
summary levels?
• Where are you on the spectrum of centralization versus decentralization?
Security Structure
• What level of security and access is allowed?
• Are business unit managers and the people that report to them secured to transactions within their own business
unit?
• Are the transactions for their business unit largely performed by a corporate department or shared service center?
Compliance Requirements
• How do you comply with your corporate external reporting requirements and local statutory reporting requirements?
• Do you tend to prefer a corporate first or an autonomous local approach?
• Where are you on a spectrum of centralization, very centralized or decentralized?
7
Oracle Applications Cloud Chapter 1
Understanding Enterprise Structures Enterprise Structures
Scenario
InFusion Corporation has 400 plus employees and revenue of $120 million. Your product line includes all the components to
build and maintain air quality monitoring (AQM) systems for homes and businesses. You also provide financial services to your
customers through a separate division.
8
Oracle Applications Cloud Chapter 1
Understanding Enterprise Structures Enterprise Structures
The upper part of the figure illustrates a legal company organization for companies in various political regions held by a public
company. They enter into transactions initiated by two business divisions, Air Quality Control and Financial Services.
The lower part of the figure illustrates the management structure, which reflects the two businesses, Air Quality Management
and Financial Services in strategic business units. The corporate administration is centralized and serves both businesses and
all companies.
Regional managers have direct reporting lines to worldwide business managers, and dotted line responsibility to Regional
Vice Presidents serving as general managers.
The Corporate Services strategic business unit provides common administrative, payroll, and procurement services.
The companies that enter into the transactions on behalf of the strategic business units are linked to the strategic business
units by double-headed arrows. Other facts:
9
Oracle Applications Cloud Chapter 1
Understanding Enterprise Structures Enterprise Structures
• The holding company enters into transactions on behalf of both divisions and the corporate headquarters.
• Each company accounts for itself in the Oracle Fusion General Ledger.
• The companies in the same jurisdiction share the ledger using balancing segments.
10
Oracle Applications Cloud Chapter 2
Understanding Enterprise Structures Enterprises
2 Enterprises
Enterprise: Explained
An enterprise is a collection of legal entities under common control and management.
Enterprise Defined
When implementing Oracle Fusion Applications you operate within the context of an enterprise that has already been created
in the application for you. This is either a predefined enterprise or an enterprise that has been created in the application by
a system administrator. An enterprise organization captures the name of the deploying enterprise and the location of the
headquarters. In Oracle Fusion Applications, an organization classified as an enterprise is defined before defining any other
organizations in the HCM Common Organization Model. All other organizations are defined as belonging to an enterprise.
11
Oracle Applications Cloud Chapter 2
Understanding Enterprise Structures Enterprises
12
Oracle Applications Cloud Chapter 3
Understanding Enterprise Structures Jurisdictions and Legal Authorities
Jurisdictions: Explained
Jurisdiction is a physical territory such as a group of countries, country, state, county, or parish where a particular piece of
legislation applies. French Labor Law, Singapore Transactions Tax Law, and US Income Tax Laws are examples of particular
legislation that apply to legal entities operating in different countries' jurisdictions. Judicial authority may be exercised within a
jurisdiction.
Types of jurisdictions are:
• Identifying Jurisdiction
Identifying Jurisdiction
For each legal entity, select an identifying jurisdiction. An identifying jurisdiction is your first jurisdiction you must register
with to be allowed to do business in a country. If there is more than one jurisdiction that a legal entity needs to register with
to commence business, select one as the identifying jurisdiction. Typically the identifying jurisdiction is the one you use to
uniquely identify your legal entity.
Income tax jurisdictions and transaction tax jurisdictions do not represent the same jurisdiction. Although in some countries,
the two jurisdictions are defined at the same geopolitical level, such as a country, and share the same legal authority, they are
two distinct jurisdictions.
13
Oracle Applications Cloud Chapter 3
Understanding Enterprise Structures Jurisdictions and Legal Authorities
Payroll-related information, such as elements, is organized by legislative data groups. Each legislative data group:
• Is associated with a legislative code, currency, and its own cost allocation key flexfield structure.
• Is a boundary that can share the same set up and still comply with the local laws.
• Can span many jurisdictions as long as they are within one country.
• Can contain many legal entities that act as payroll statutory units.
14
Oracle Applications Cloud Chapter 4
Understanding Enterprise Structures Legal Entities
4 Legal Entities
• Own property
• Trade
• Repay debt
• Account for themselves to regulators, taxation authorities, and owners according to rules specified in the relevant
legislation
Their rights and responsibilities may be enforced through the judicial system. Define a legal entity for each registered company
or other entity recognized in law for which you want to record assets, liabilities, expenses and income, pay transaction taxes,
or perform intercompany trading.
A legal entity has responsibility for elements of your enterprise for the following reasons:
• Isolating one area of the business from risks in another area. For example, your enterprise develops property and
also leases properties. You could operate the property development business as a separate legal entity to limit risk to
your leasing business.
Legal entities must comply with the regulations of jurisdictions, in which they register. Europe now allows for companies to
register in one member country and do business in all member countries, and the US allows for companies to register in one
state and do business in all states. To support local reporting requirements, legal reporting units are created and registered.
15
Oracle Applications Cloud Chapter 4
Understanding Enterprise Structures Legal Entities
You are required to publish specific and periodic disclosures of your legal entities' operations based on different jurisdictions'
requirements. Certain annual or more frequent accounting reports are referred to as statutory or external reporting. These
reports must be filed with specified national and regulatory authorities. For example, in the United States (US), your publicly
owned entities (corporations) are required to file quarterly and annual reports, as well as other periodic reports, with the
Securities and Exchange Commission (SEC), who enforces statutory reporting requirements for public corporations.
Individual entities privately held or held by public companies do not have to file separately. In other countries, your individual
entities do have to file in their own name, as well as at the public group level. Disclosure requirements are diverse. For
example, your local entities may have to file locally to comply with local regulations in a local currency, as well as being
included in your enterprise's reporting requirements in different currency.
A legal entity can represent all or part of your enterprise's management framework. For example, if you operate in a large
country such as the United Kingdom or Germany, you might incorporate each division in the country as a separate legal
entity. In a smaller country, for example Austria, you might use a single legal entity to host all of your business operations
across divisions.
• Legal entity and its relationship to worker assignments and legal employer
16
Oracle Applications Cloud Chapter 4
Understanding Enterprise Structures Legal Entities
most countries, damages can be sought for both actual losses, putting the injured party in the same state as if they had not
entered into the contract, and what is called loss of bargain, or the profit that would have made on a transaction.
In another example, if you revalued your inventory in a warehouse to account for raw material price increases, the revaluation
and revaluation reserves must be reflected in your legal entity's accounts. In Oracle Fusion Applications, your inventory within
an inventory organization is managed by a single business unit and belongs to one legal entity.
2. Balance transactions that cross legal entity boundaries through intercompany transactions.
3. Decide which balancing segments correspond to each legal entity and assign them in Oracle Fusion General
Ledger Accounting Configuration Manager. Once you assign one balancing segment value in a ledger, then all
your balancing segment values must be assigned. This recommended best practice facilitates reporting on assets,
liabilities, and income by legal entity.
Represent your legal entities by at least one balancing segment value. You may represent it by two or three balancing
segment values if more granular reporting is required. For example, if your legal entity operates in multiple jurisdictions in
Europe, you might define balancing segment values and map them to legal reporting units. You can represent a legal entity
with more than one balancing segment value. Do not use a single balancing segment value to represent more than one legal
entity.
In Oracle Fusion General Ledger, there are three balancing segments. You can use separate balancing segments to represent
your divisions or strategic business units to enable management reporting at the balance sheet level for each division or
business unit. For example, use this solution to empower your business unit and divisional managers to track and assume
responsibility for their asset utilization or return on investment. Using multiple balancing segments is also useful when you
know at the time of implementation that you are disposing of a part of a legal entity and need to isolate the assets and
liabilities for that entity.
17
Oracle Applications Cloud Chapter 4
Understanding Enterprise Structures Legal Entities
Important
Implementing multiple balancing segments requires every journal entry that is not balanced by division or business
unit, to generate balancing lines. Also, you cannot change to multiple balancing segments easily after you have
begun to use the ledger because your historical data is not balanced by the new multiple balancing segments.
Restating historical data must be done at that point.
If your enterprise regularly spins off businesses or if they hold managers of those businesses accountable for
utilization of assets, it make be useful to identify the business with a balancing segment value. If you decided
to account for each legal entity in a separate ledger, there is no requirement to identify the legal entity with a
balancing segment value within the ledger.
Tip
While transactions that cross balancing segments don't necessarily cross legal entity boundaries, all transactions
that cross legal entity boundaries must cross balancing segments. If you make an acquisition or are preparing
to dispose of a portion of your enterprise, you may want to account for that part of the enterprise in its own
balancing segment even if it is not a separate legal entity. If you do not map legal entities sharing the same ledger
to balancing segments, you are not be able to distinguish them using the intercompany functionality or track their
individual equity.
Tip
In the Oracle Fusion Supply Chain applications, model intercompany relationships using business units, from
which legal entities are inferred.
Legal Entity and Its Relationship to Worker Assignments and Legal Employer
Legal entities that employ people are called legal employers in the Oracle Fusion Legal Entity Configurator. You must enter
legal employers on worker assignments in Oracle Fusion HCM.
18
Oracle Applications Cloud Chapter 4
Understanding Enterprise Structures Legal Entities
also mark these legal reporting units as tax reporting units, if the legal entity must pay taxes as a result of establishing a place
of business within the jurisdiction.
Related Topics
• Creating Legal Entities in the Enterprise Structures Configurator: Points to Consider
19
Oracle Applications Cloud Chapter 4
Understanding Enterprise Structures Legal Entities
Scenario
InFusion Corporation is a multinational enterprise in the high technology industry with product lines that include all the
components that are required to build and maintain air quality monitoring (AQM) systems for homes and businesses. Its
primary locations are in the US and the UK, but it has smaller outlets in France, Saudi Arabia, and the United Arab Emirates
(UAE).
Enterprise Details
In the US, InFusion employs 400 people and has company revenue of $120 million. Outside the US, InFusion employs 200
people and has revenue of $60 million.
Analysis
InFusion requires three divisions.
• Saudi Arabia and the UAE are covered by the Middle East division.
InFusion requires legal entities with legal employers, payroll statutory units, tax reporting units, and legislative data groups for
the US, UK, France, Saudi Arabia, and UAE, in order to employ and pay its workers in those countries.
InFusion requires a number of departments across the enterprise for each area of business, such as sales and marketing, and
a number of cost centers to track and report on the costs of those departments.
Infusion has general managers responsible for business units within each country. Those business units may share reference
data. Some reference data can be defined within a reference data set that multiple business units may subscribe to. Business
units are also required for financial purposes. Financial transactions are always processed within a business unit.
20
Oracle Applications Cloud Chapter 4
Understanding Enterprise Structures Legal Entities
Related Topics
• Enterprise Structures: Overview
21
Oracle Applications Cloud Chapter 4
Understanding Enterprise Structures Legal Entities
22
Oracle Applications Cloud Chapter 5
Understanding Enterprise Structures Management Reporting Structures
Divisions
A division refers to a business oriented subdivision within an enterprise, in which each division organizes itself differently to
deliver products and services or address different markets. A division can operate in one or more countries, and can be
comprised of many companies or parts of different companies that are represented by business units.
A division is a profit center or grouping of profit and cost centers, where the division manager is responsible for attaining
business goals including profit goals. A division can be responsible for a share of the company's existing product lines or for
a separate business. Managers of divisions may also have return on investment goals requiring tracking of the assets and
liabilities of the division. The division manager generally reports to a top corporate executive.
By definition a division can be represented in the chart of accounts. Companies may choose to represent product lines,
brands, or geographies as their divisions: their choice represents the primary organizing principle of the enterprise. This may
coincide with the management segment used in segment reporting.
Oracle Fusion Applications supports a qualified management segment and recommends that you use this segment to
represent your hierarchy of business units and divisions. If managers of divisions have return on investment goals, make the
management segment a balancing segment. Oracle Fusion applications allows up to three balancing segments. The values of
the management segment can be comprised of business units that roll up in a hierarchy to report by division.
Historically, divisions were implemented as a node in a hierarchy of segment values. For example, Oracle E-Business Suite
has only one balancing segment, and often the division and legal entity are combined into a single segment where each value
stands for both division and legal entity.
23
Oracle Applications Cloud Chapter 5
Understanding Enterprise Structures Management Reporting Structures
objectives, a level of autonomy, and responsibility for its profit and loss. Roll business units up into divisions if you structure
your chart of accounts with this type of hierarchy.
In Oracle Fusion Applications:
• Assign your business units to one primary ledger. For example, if a business unit is processing payables invoices
they will need to post to a particular ledger. This assignment is mandatory for your business units with business
functions that produce financial transactions.
• Use business unit as a securing mechanism for transactions. For example, if you run your export business separately
from your domestic sales business, secure the export business data to prevent access by the domestic sales
employees. To accomplish this security, set up the export business and domestic sales business as two separate
business units.
The Oracle Fusion Applications business unit model provides the following advantages:
• Allows for flexible implementation
• A consistent entity that controls and reports on transactions
• Sharing sets of reference data across applications
Business units process transactions using reference data sets that reflect your business rules and policies and can differ from
country to country. With Oracle Fusion Application functionality, you can choose to share reference data, such as payment
terms and transaction types, across business units, or you can choose to have each business unit manage its own set
depending on the level at which you wish to enforce common policies.
In countries where gapless and chronological sequencing of documents is required for subledger transactions, define your
business units in alignment with your legal entities to ensure the uniqueness of sequencing.
In summary, use business units in the following ways:
• Management reporting
• Processing of transactions
• Security of transactional data
• Reference data definition and sharing
Related Topics
• Reference Data Sets and Sharing Methods: Explained
24
Oracle Applications Cloud Chapter 5
Understanding Enterprise Structures Management Reporting Structures
Business Functions
A business function represents a business process, or an activity that can be performed by people working within a business
unit and describes how a business unit is used. The following business functions exist in Oracle Fusion applications:
Note
This hierarchy definition is not required in the setup of your applications, but is a recommended best practice.
Your enterprise procedures can require a manager of a business unit to have responsibility for their profit and loss statement.
In such cases, any segment that allows the identification of associated revenue and costs can be used as a profit center
identification. The segment can be qualified as a cost center segment.
However, there are cases where a business unit is performing only general and administrative functions, in which case your
manager's financial goals are limited to cost containment or recovering of service costs. For example, if a shared service
center at the corporate office provides services for more commercially-oriented business units, it does not show a profit and
therefore, only tracks its costs.
In other cases, where your managers have a responsibility for the assets of the business unit, a balance sheet can be
produced. The recommended best practice to produce a balance sheet is to setup the business unit as a balancing segment
in the chart of accounts. The business unit balancing segment can roll up to divisions or other entities to represent your
enterprise structure.
When a business function produces financial transactions, a business unit must be assigned to a primary ledger, and a
default legal entity. Each business unit can post transactions to a single primary ledger, but it can process transactions for
many legal entities.
25
Oracle Applications Cloud Chapter 5
Understanding Enterprise Structures Management Reporting Structures
The following business functions generate financial transactions and will require a primary ledger and a default legal entity:
• Air quality monitoring systems through your division InFusion Air Systems
• Customer financing through your division InFusion Financial Services
The InFusion Air Systems division further segments your business into the System Components and Installation Services
subdivisions. Your subdivisions are divided by business units:
26
Oracle Applications Cloud Chapter 5
Understanding Enterprise Structures Management Reporting Structures
Oracle Fusion applications facilitates independent balance sheet rollups for legal and management reporting by offering
up to three balancing segments. Hierarchies created using the management segment can provide the divisional results.
For example, it is possible to define management segment values to correspond to business units, and arrange them in a
hierarchy where the higher nodes correspond to divisions and subdivisions, as in the Infusion US Division example above.
• Procurement
◦ Processes requisitions and negotiates supplier terms for client business units
• Payables Payment
◦ Services business units that enable the Payables Invoicing business function
• Customer Payments
◦ Services business units that enable the Billing and Revenue Management business function.
◦ Processes payments for the transactions of client business units assigned the Billing and Revenue
Management business function.
This functionality is used to frame service level agreements and drive security. The service provider relationships provides you
with a clear record of how your business operations are centralized. For other centralized processing, business unit security
27
Oracle Applications Cloud Chapter 5
Understanding Enterprise Structures Management Reporting Structures
is used (known in Oracle EBS as Multi-Org Access Control). This means that users who work in a shared service center have
the ability to get access and process transactions on behalf of many business units.
Related Topics
• Centralized Payment Processing Across Business Units: Explained
General Properties
General property options include the default reference data set to be used for any new reference data object associated with
the project unit. You can override the default set for each reference data object. The method of project number creation,
either manual or automatic, and daily or weekly full time equivalent hours for reporting purposes, are also included in general
properties.
Set Assignments
You assign sets to project units to determine how reference data is shared across different lines of business in a company. A
project unit is a set determinant for the following objects.
• Project definition, which includes set-enabled reference data for the project definition such as class code, financial
plan type, project role, and project status.
• Project transaction types, which include set-enabled reference data for project transactions such as project
expenditure type and project work type.
Set assignment configuration includes the following options for each project unit.
• Reference set value: By default, the set for each reference data object is from the default set specified for the project
unit.
28
Oracle Applications Cloud Chapter 5
Understanding Enterprise Structures Management Reporting Structures
• Reference data objects: For the project definition and project transaction types.
Project Setup
Each business unit that you enable requires implementing project setup options for the following areas:
• Project and task owning organizations are associated with the business unit to restrict these organizations in project
creation flow.
Important
To own projects or tasks, an organization must be classified as project and task owning organization,
belong to the hierarchy associated with the business unit, and be active on the system date. The project
type class must be permitted to use the organization to create projects.
• Project expenditure organizations are associated with the business unit to restrict which organizations can incur
costs on the project.
29
Oracle Applications Cloud Chapter 5
Understanding Enterprise Structures Management Reporting Structures
• Project costing establishes calendar, asset, overtime, and processing options for project-related costs.
• Project units are associated with business units to restrict the business units that can handle project transactions.
When a project unit isn't associated with a business unit, any business unit in your enterprise can process project
transactions.
• Cross-charge transaction options define conversion rate and date types and cross-charge transaction processing
methods.
• Customer contract management defines business function properties, such as currency conversion, cross-charge
transaction, and billing options, for each contract business unit.
Note
A project can be associated with only one business unit.
• Project accounting definition, including set-enabled reference data such as project type.
• Project and contract billing, including set-enabled reference data such as invoice format.
• Project rates, including set-enabled reference data such as rate schedules.
30
Oracle Applications Cloud Chapter 5
Understanding Enterprise Structures Management Reporting Structures
Scenario
Your company, InFusion Corporation, is a multinational conglomerate that operates in the United States (US) and the United
Kingdom (UK). InFusion has purchased an Oracle Fusion enterprise resource planning (ERP) solution including Oracle Fusion
General Ledger and all of the Oracle Fusion subledgers. You are chairing a committee to discuss creation of a model for your
global enterprise structure including both your US and UK operations.
InFusion Corporation
InFusion Corporation has 400 plus employees and revenue of $120 million. Your product line includes all the components to
build and maintain air quality monitoring (AQM) systems for homes and businesses. You have two distribution centers and
three warehouses that share a common item master in the US and UK. Your financial services organization provides funding
to your customers for the start up costs of these systems.
Analysis
The following are elements you need to consider in creating your business units for your global enterprise structure.
• At which level do you track profit and loss (revenue and expenses) and strategic objectives?
• Do you require balance sheet for your management entities? Is capital utilization reported on the level of business
units?
• Do you use business units and balancing segments to represent your businesses and divisions?
• Do you secure data by a segment representing each department or legal entity or both to produce useful, but
confidential management reports?
31
Oracle Applications Cloud Chapter 5
Understanding Enterprise Structures Management Reporting Structures
• Is your procurement centralized, or do individual business units perform the procurement function?
• Can your business units process transactions on behalf of many legal entities?
• How do you want to represent your business units and divisions in the chart of accounts?
• InFusion America Inc. has BU 1: US Systems and BU 4: Corporate Processing Shared Service Center
Business Units 1, 2, and 3 record the transactions of their respective legal entities. Business Unit 4 processes the
corporate level transactions, including payable, procurement and human resource functions for the entire enterprise. The
implementation of BU 4 reduces administrative costs, provides consistent enforcement of company policies, and improves
efficiency across the organization.
32
Oracle Applications Cloud Chapter 6
Understanding Enterprise Structures Financial Reporting Structures
33
Oracle Applications Cloud Chapter 6
Understanding Enterprise Structures Financial Reporting Structures
ledger is designed to serve as a repository of management data for a certain level of management. For example,
a subsidiary's general ledger is designed to provide the upper management enough data to supervise operations,
such as daily sales, without invoice details or inventory without part number details.
• A primary ledger and a secondary ledger, where one is a thick general ledger and the other a thin general ledger,
provides dual representation for reporting requirements that require more than one ledger.
34
Oracle Applications Cloud Chapter 6
Understanding Enterprise Structures Financial Reporting Structures
One example of an industry that frequently uses a thick general ledger is electronic manufacturers. Detail on the revenue line
is tagged by sales channel. Product is structured differently to provide detail on the cost of goods sold line, including your
bill of materials costs. The general ledger is used to compare and contrast both revenue and cost of goods sold for margin
analysis.
Other Considerations
Consider implementing a thick ledger if there are business requirements to do any of the following:
• Track entered currency balances at the level of an operational dimension or segment of your chart of accounts, such
as by department or cost center
• Generate financial allocations at the level of an operational dimension or segment
• Report using multiple layered and versioned hierarchies of the operational dimension or segment from your general
ledger
Consider implementing a thin ledger in addition to a thick ledger, if there are additional requirements for:
• Minimal disclosure to the authorities in addition to the requirements listed above. For example, in some European
countries, fiscal authorities examine ledgers at the detailed account level.
• Fiscal only adjustments, allocations, and revaluations, which don't impact the thick general ledger.
The important consideration in determining if a thick ledger is the primary or secondary ledger is your reporting needs. Other
considerations include how the values for an operational dimension or segment are derived and the amount of resources
used in reconciling your different ledgers. If values for the operational dimension are always entered by the user like other
segments of the accounting flexfield, then a thick primary ledger is the better choice.
However, if values for the operational dimension or segment are automatically derived from other attributes on the
transactions in your subledger accounting rules, rather than entered in the user interface, then use a thick secondary ledger.
This decision affects the amount of:
• Storage and maintenance needed for both the general ledger and subledger accounting entries
• System resources required to perform additional posting
• In summary, you have:
◦ Minimum demand on storage, maintenance, and system resources with the use of a thin ledger
◦ Greater demand on storage, maintenance, and system resources with the use of a thick ledger
◦ Greatest demand on storage, maintenance and system resources with the use of both thick and thin ledgers
Note
Generally speaking, there is a trade-off between the volume of journals and balances created and
maintained versus system resource demands. Actual performance depends on a wide range of factors
including hardware and network considerations, transaction volume, and data retention policies.
Summary
The factors you need to consider in your decision to use a thick or thin general ledger for your organization, are your:
• Downstream EPM system and its capabilities
• Business intelligence system and its capabilities
• Subledger systems and their capabilities and characteristics, including heterogeneity
• General ledger reporting systems and their capabilities
35
Oracle Applications Cloud Chapter 6
Understanding Enterprise Structures Financial Reporting Structures
• Maintenance required for the thick or thin distributions and record keeping
• Maintenance required to update value sets for the chart of accounts segments
• Preferences of the product that serves as a source of truth
• Level at which to report profitability including gross margin analysis
• Industry and business complexity
Chart of Accounts
The chart of accounts defines the number and attributes of various segments, including:
• Order of segments
• Width of segments
• Prompts
36
Oracle Applications Cloud Chapter 6
Understanding Enterprise Structures Financial Reporting Structures
Segments
A chart of accounts segment is a component of the account combination. Each segment has a value set attached to it to
provide formatting and validation of the set of values used with that segment. The combination of segments creates the
account combination used for recording and reporting financial transactions. Examples of segments that may be found in a
chart of accounts are company, cost center, department, division, region, account, product, program, and location.
Caution
You must use Independent validation only for the Accounting Key Flexfield value sets. Other validations prevent
you from using the full chart of accounts functionality, such as data security, reporting, and account hierarchy
integration. Dependent values sets are not supported.
Segment Labels
Segment labels identify certain segments in your chart of accounts and assign special functionality to those segments.
Segment labels were referred to as flexfield qualifiers in Oracle E-Business Suite. Here are the segment labels that are
available to use with the chart of accounts.
• Balancing: Ensures that all journals balance for each balancing segment value or combination of multiple balancing
segment values to use in trial balance reporting. The three balancing segment labels are: primary, second, and third
balancing. The primary balancing segment label is required.
• Cost Center: Facilitates grouping of natural accounts by functional cost types, accommodating tracking of specific
business expenses across natural accounts. As cost centers combine expenses and headcount data into costs,
they are useful for detailed analysis and reporting. Cost centers are optional, but required if you are accounting for
depreciation, additions, and other transactions in Oracle Fusion Assets, and for storing expense approval limits in
Oracle Fusion Expense Management.
• Natural Account: Determines the account type (asset, liability, expense, revenue, or equity) and other information
specific to the segment value. The natural account segment label is required.
• Management: Optionally, denotes the segment that has management responsibility, such as the department, cost
center, or line of business. Also can be attached to the same segment as one of the balancing segments to make
legal entity reporting more granular.
• Intercompany: Optionally, assigns the segment to be used in intercompany balancing functionality.
Note
All segments have a segment qualifier that enables posting for each value. The predefined setting is Yes to post.
37
Oracle Applications Cloud Chapter 6
Understanding Enterprise Structures Financial Reporting Structures
Account Combinations
An account combination is a completed code of segment values that uniquely identifies an account in the chart of accounts,
for example 01-2900-500-123, might represent InFusion America (company)-Monitor Sales (division)-Revenue (account)-Air
Filters (product).
Rules
The chart of accounts uses two different types of rules to control functionality.
• Security rules: Prohibit certain users from accessing specific segment values. For example, you can create a
security rule that grants a user access only to his or her department.
• Cross-validation rules: Control the account combinations that can be created during data entry. For example, you
may decide that sales cost centers 600 to 699 should enter amounts only to product sales accounts 4000 to 4999.
38
Oracle Applications Cloud Chapter 6
Understanding Enterprise Structures Financial Reporting Structures
process often includes determining financial, legal, and management reporting requirements and examining consolidation
considerations.
• Ledgers: The main record-keeping structure. A ledger records the transactional balances by defining a chart of
accounts with a consistent calendar and currency, and accounting rules, implemented in an accounting method.
The ledger is associated with the subledger transactions for the business units that are assigned to it, and provides
context and accounting for them.
• Balancing Segments: Use these chart of accounts element to represent and track both legal and management
entities. The primary balancing segment is used to represents your legal entities. The Second and Third balancing
segments are used to implement management reporting and analysis. Balancing segments provide automatic
balancing functionality by legal entity for journal entries, including intercompany and intracompany entries, suspense
posting, and rounding imbalances.
39
Oracle Applications Cloud Chapter 6
Understanding Enterprise Structures Financial Reporting Structures
• Cost Centers: The component that aggregates elements of natural expenses to identify functional costs. A cost
center can be the smallest segment of an organization for which costs are collected and reported. Not all cost
centers represent organizations. A manager is assigned responsibility for cost control and is assigned both a
department and a cost center; in which case the cost center and department might be identified with each other.
However, a finance department manager might have separate cost centers for finance cost and audit costs and a
Research and Development department manager might have separate cost centers for research and development.
Cost centers are represented by segment values in the chart of accounts that indicate the functional areas of your
business, such as accounting, facilities, shipping, or human resources. You might keep track of functional areas at
a detailed level, but produce summary reports that group cost centers into one or more departments. Cost center
values are also used by Oracle Fusion Assets to assist the managers in tracking locations and accounting for assets
assigned to their departments.
• Accounts: The code in the chart of accounts that uniquely identifies each type of transactions recorded in the ledger
and subledgers. The account segment is mapped to a dimension in the GL Balances Cube to enable reporting and
inquiry. This functionality uses Oracle Fusion Business Intelligence to analyze and drill into expense and revenue
transactions.
• Representing Legal Entities in the Chart of Accounts: Legal entity is the term used in Oracle Fusion Applications for
registered companies and other organizations recognized in law as having a legal existence and as parties with given
rights and responsibilities.
Legal entities are created in the applications and then assigned balancing segment values, sometimes called
company codes in your ledgers during accounting configuration.
• Representing Business Units in the Chart of Accounts: A business unit (BU) is part of an enterprise managed
by a manager with profit and loss responsibility. The business unit is generally tracked in the chart of accounts.
A business unit can be represented by a single ledger. For example, in countries where you need document
sequencing for unique transaction sequencing within a legal entity, you can have a single ledger with a single
business unit and legal entity.
A business unit can also be identified in the chart of accounts as a:
◦ Management segment value
40
Oracle Applications Cloud Chapter 6
Understanding Enterprise Structures Financial Reporting Structures
• Representing Departments in the Chart of Accounts: A department is an organizational structure with one or more
operational objectives or responsibilities that exist independently of its manager and that has one or more employees
assigned to it. The manager of a department is typically responsible for business deliverables, personnel resource
management, competency management, and occasionally, for cost control and asset tracking.
In Oracle Fusion Applications, departments can be set up in Oracle Fusion Human Capital Management (HCM). If
desired, they can also be represented by a unique segment in the chart of accounts or a group of cost center values.
Scenario
Your company, InFusion Corporation, is a multinational conglomerate that operates in the United States (US) and the United
Kingdom (UK). InFusion has purchased an Oracle Fusion enterprise resource planning (ERP) solution including Oracle Fusion
General Ledger and all of the Oracle Fusion subledgers. You are chairing a committee to discuss creation of a model for your
global financial reporting structure including your chart of accounts for both your US and UK operations.
InFusion Corporation
InFusion Corporation has 400 plus employees and revenue of $120 million. Your product line includes all the components to
build and maintain air quality monitoring (AQM) systems for homes and businesses. You have two distribution centers and
three warehouses that share a common item master in the US and UK. Your financial services organization provides funding
to your customers for the start up costs of these systems.
Analysis
The following are elements you need to consider in creating your model for your financial reporting structure.
• Your company is required to report using US Generally Accepted Accounting Principles (GAAP) standards and UK
Statements of Standard Accounting Practice and Financial Reporting Standards. How many ledgers do you need to
achieve proper statutory reporting?
• Your financial services line of business has a different year end. Do you need a different calendar? Your financial
services entity must report with average balance sheets. This feature of Oracle Fusion General Ledger provides you
with the ability to track average and end-of-day balances, report average balance sheets, and create custom reports
using both standard and average balances.
• Your corporate management requires reports showing total organizational performance with drill down capability to
the supporting details. Do you need multiple balancing segment hierarchies to achieve proper rollup of balances for
reporting requirements?
• Legal entity balancing options: Do you need to produce financial statements by one or more than one legal entity?
Can you record multiple legal entities in one ledger or do you require multiple ledgers? Are you upgrading to Oracle
Fusion Applications or a new install? If an upgrade, is your current financial reporting structure meeting your reporting
needs?
41
Oracle Applications Cloud Chapter 6
Understanding Enterprise Structures Financial Reporting Structures
• Data security is controlled by balancing segment values using Oracle Fusion General Ledger data access sets
• Segments required for cost centers with hierarchical rollups to departments providing reporting at both the detail
(cost center) and summary (department) level.
42
Oracle Applications Cloud Chapter 6
Understanding Enterprise Structures Financial Reporting Structures
• Accounts configured to provide drill down capability to the subledger transactions, enabling analysis of data.
43
Oracle Applications Cloud Chapter 6
Understanding Enterprise Structures Financial Reporting Structures
Currencies for Reporting US Dollar (USD) US Dollar (USD) Great Britain Pounds
Sterling (GBP)
US Dollar (USD)
Note
In the chart of accounts, cost centers, with hierarchical rollups, represent business units. InFusion Corporation is
also a legal entity but is not discussed in this example.
44
Oracle Applications Cloud Chapter 7
Understanding Enterprise Structures Cost Centers and Departments
Cost Centers
A cost center also represents the destination or function of an expense as opposed to the nature of the expense which
is represented by the natural account. For example, a sales cost center indicates that the expense goes to the sales
department.
A cost center is generally attached to a single legal entity. To identify the cost centers within a chart of accounts structure use
one of these two methods:
• Assign a cost center value in the value set for each cost center. For example, assign cost center values of PL04 and
G3J1 to your manufacturing teams in the US and India. These unique cost center values allow easy aggregation of
cost centers in hierarchies (trees) even if the cost centers are in different ledgers. However, this approach requires
defining more cost center values.
• Assign a balancing segment value with a standardized cost center value to create a combination of segment values
to represent the cost center. For example, assign the balancing segment values of 001 and 013 with cost center
PL04 to represent your manufacturing teams in the US and India. This creates 001-PL04 and 013-PL04 as the cost
center reporting values. The cost center value of PL04 has a consistent meaning. This method requires fewer cost
center values to be defined. However, it prevents construction of cost center hierarchies using trees where only
cost center values are used to report results for a single legal entity. You must specify a balancing segment value in
combination with the cost center values to report on a single legal entity.
Departments
A department is an organization with one or more operational objectives or responsibilities that exist independently of its
manager. For example, although the manager may change, the objectives do not change. Departments have one or more
workers assigned to them.
A manager of a department is typically responsible for:
Note
The manager of a sales department may also be responsible for meeting the revenue targets.
The financial performance of departments is generally tracked through one or more cost centers. In Oracle Fusion
Applications, departments are defined and classified as Department organizations. Oracle Fusion Human Capital
Management (HCM) assigns workers to departments, and tracks the headcount at the departmental level.
The granularity of cost centers and their relationship to departments varies across implementations. Cost center and
department configuration may be unrelated, identical, or consist of many cost centers tracking the costs of one department.
45
Oracle Applications Cloud Chapter 7
Understanding Enterprise Structures Cost Centers and Departments
Project Organization
Classify departments as a project owning organization to enable associating them with projects or tasks. The project
association is one of the key drivers for project access security.
In addition, you must classify departments as project expenditure organizations to enable associating them to project
expenditure items. Both project owning organizations and project expenditure organizations can be used by Oracle Fusion
Subledger Accounting to derive accounts for posting Oracle Fusion Projects accounting entries to Oracle Fusion General
Ledger.
46
Oracle Applications Cloud Chapter 7
Understanding Enterprise Structures Cost Centers and Departments
information to them. Each department is represented in the chart of accounts by more than one cost center, allowing for
granular as well as hierarchical reporting.
Cost Organization
Oracle Fusion Costing uses a cost organization to represent a single physical inventory facility or group of inventory storage
centers, for example, inventory organizations. This cost organization can roll up to a manager with responsibility for the cost
center in the financial reports.
A cost organization can represent a costing department. Consider this relationship when determining the setup of
departments in HCM. There are no system dependencies requiring these two entities, cost organization and costing
department, be set up in the same way.
47
Oracle Applications Cloud Chapter 7
Understanding Enterprise Structures Cost Centers and Departments
48
Oracle Applications Cloud Chapter 8
Understanding Enterprise Structures Facilities
8 Facilities
• Include an item and its definition of form, fit, and function only once in the item master
• Separate the item master organization from organizations that store and transact items
49
Oracle Applications Cloud Chapter 8
Understanding Enterprise Structures Facilities
Note
Oracle Fusion allows multiple item masters, however, use this capability cautiously. If you acquire a company,
there may be value in allowing the old item master to exist for a transition period. If you manage your subsidiaries
as separate businesses, there may be reduced value in a single item master.
Note
• Items belong to an item organization.
• Item attributes that are associated with financial and accounting information are hidden from the item if it exists
within the item organization.
• Item organizations can be changed by administrators to an inventory organization by updating the necessary
attributes. There is no difference in the way items are treated in these two types of organizations except that
there cannot be any financial transactions in the downstream applications for items that are assigned to an item
organization.
Note
Currently, Oracle Fusion Applications do not include manufacturing capabilities, so setup your manufacturing
facilities outside of Oracle Fusion applications.
50
Oracle Applications Cloud Chapter 8
Understanding Enterprise Structures Facilities
51
Oracle Applications Cloud Chapter 8
Understanding Enterprise Structures Facilities
The figure below illustrates the inventory owned by InFusion Air Quality legal entity. The InFusion Air Quality legal entity
is associated with the Air Compressors business unit, which is associated with the two Air Compressors inventory
organizations. Therefore, InFusion Air Quality legal entity owns the entire inventory in both the Dallas and Atlanta locations.
Note
A cost organization generally represents a costing department. Take costing departments into consideration when
determining the setup of departments in Oracle Fusion Human Capital Management (HCM). There are no system
dependencies on cost organizations and costing departments requiring the same setup.
52
Oracle Applications Cloud Chapter 9
Understanding Enterprise Structures Reference Data
9 Reference Data
• Assignment to one set only, no common values allowed. The simplest form of sharing reference data that allows
assigning a reference data object instance to one and only one set. For example, Asset Prorate Conventions are
defined and assigned to only one reference data set. This set can be shared across multiple asset books, but all the
values are contained only in this one set.
• Assignment to one set only, with common values. The most commonly used method of sharing reference data
that allows defining reference data object instance across all sets. For example, Receivables Transaction Types are
assigned to a common set that is available to all the business units without the need to be explicitly assigned the
transaction types to each business unit. In addition, you can assign a business unit specific set of transaction types.
At transaction entry, the list of values for transaction types includes transaction types from the set assigned to the
business unit, as well as transaction types assigned to the common set that is shared across all business units.
• Assignment to multiple sets, no common values allowed. The method of sharing reference data that allows a
reference data object instance to be assigned to multiple sets. For instance, Payables Payment Terms use this
method. It means that each payment term can be assigned to one or more than one set. For example, you assign
the payment term Net 30 to several sets, but the payment term Net 15 is assigned to only your corporate business
53
Oracle Applications Cloud Chapter 9
Understanding Enterprise Structures Reference Data
unit specific set. At transaction entry, the list of values for payment terms consists of only one set of data; the set
that is assigned to the transaction's business unit.
Note
Oracle Fusion Applications contains a reference data set called Enterprise. Define any reference data that affects
your entire enterprise in this set.
Trading Community Model Customer Account Relationship Assignment to one set only, with
common values
Trading Community Model Customer Account Site Assignment to one set only, with
common values
Trading Community Model Sales Person Assignment to one set only, with
common values
Opportunity Management Sales Method Group Assignment to one set only, with
common values
54
Oracle Applications Cloud Chapter 9
Understanding Enterprise Structures Reference Data
55
Oracle Applications Cloud Chapter 9
Understanding Enterprise Structures Reference Data
Fusion Order Management Hold Codes Assignment to one set only, with
common values
Fusion Order Management Orchestration Process Assignment to one set only, with
common values
56
Oracle Applications Cloud Chapter 9
Understanding Enterprise Structures Reference Data
57
Oracle Applications Cloud Chapter 9
Understanding Enterprise Structures Reference Data
Items
If you share your items across warehouses or manufacturing facilities, you can access them through a common item
master. Configure one or multiple item masters for your enterprise, based your enterprise structure. A single item master
is recommended because it provides simpler and more efficient maintenance. However, in rare cases, it may be beneficial
to keep multiple item masters. For example, if you acquire another enterprise and need to continue to operate your lines of
business separately, maintaining a second item master might be the best decision.
Suppliers Sites
You can approve particular suppliers to supply specified commodities and authorize your business units to buy from those
suppliers when the need arises. For example, you might be a household cleaning products manufacturer and need dyes,
plastics, and perfumes to make your products. You purchase from a central supplier 70% of your perfume supplies with an
additional supplier, in reserve, from whom you purchase the remaining 30%. At the same time, each of your business units
purchases plastics and dyes from the same supplier, but from different local supplier sites to save transportation costs.
To implement business unit specific supplier sites, Oracle Fusion Procurement supports a method for defining suppliers sites
as owned and managed by the business unit responsible for negotiating the supplier terms. Your other business units that
have a service provider relationship defined with your procurement business unit subscribe to the supplier sites using the
58
Oracle Applications Cloud Chapter 9
Understanding Enterprise Structures Reference Data
supplier site assignments feature. In addition, Procurement allows sharing of the following procurement data objects across
business units:
• Catalog content, such as agreements, smart forms, public shopping lists, and content zones
59
Oracle Applications Cloud Chapter 9
Understanding Enterprise Structures Reference Data
60
Oracle Applications Cloud Chapter 10
Understanding Enterprise Structures Shared Service Centers
Security
The setup of business units provides you with a powerful security construct by creating relationships between the functions
your users can perform and the data they can process. This security model is appropriate in a business environment where
local business units are solely responsible for managing all aspects of the finance and administration functions.
In Oracle Fusion applications, the business functions your business unit performs are evident in the user interface for setting
up business units. To accommodate shared services, use business unit security to expand the relationship between functions
and data. A user can have access to many business units. This is the core of your shared service architecture.
For example, you take orders in many businesses. Your orders are segregated by business unit. However, all of these orders
are managed from a shared service order desk in an outsourcing environment by your users who have access to multiple
business units.
Benefits
In summary, large, medium, and small enterprises benefit from implementing share service centers. Examples of functional
areas where shared service centers are generally implemented include procurement, disbursement, collections, order
management, and human resources. The advantages of deploying these shared service centers are the following:
• Reduce and consolidate the number of control points and variations in processes, mitigating the risk of error.
• Increase corporate compliance to local and international requirements, providing more efficient reporting.
• Implement standard business practices, ensuring consistency across the entire enterprise and conformity to
corporate objectives.
• Establish global processes and accessibility to data, improving managerial reporting and analysis.
• Provide quick and efficient incorporation of new business units, decreasing startup costs.
• Establish the right balance of centralized and decentralized functions, improving decision making.
61
Oracle Applications Cloud Chapter 10
Understanding Enterprise Structures Shared Service Centers
• Permit business units to concentrate on their core competencies, improving overall corporate profits.
Procurement Example
The Oracle Fusion Procurement product family has taken advantage of the service provide model by defining outsourcing of
the procurement business function. Define your business units with requisitioning and payables invoicing business functions
as clients of your business unit with the procurement business function. Your business unit responsible for the procurement
business function takes care of supplier negotiations, supplier site maintenance, and purchase order processing on behalf of
your client business units. Subscribe your client business units to the supplier sites maintained by the service providers, using
a new procurement feature for supplier site assignment.
In the InFusion example below, business unit four (BU4) serves as a service provider to the other three business units (BU1,
BU2, and BU3.) BU4 provides the corporate administration, procurement, and human resources (HR) business functions,
thus providing cost savings and other benefits to the entire InFusion enterprise.
62
Oracle Applications Cloud Glossary
Understanding Enterprise Structures
Glossary
assignment
A set of information, including job, position, pay, compensation, managers, working hours, and work location, that defines a
worker's or nonworker's role in a legal employer.
balancing segment
A chart of accounts segment used to automatically balance all journal entries for each value of this segment.
business function
A business process or an activity that can be performed by people working within a business unit. Describes how a business
unit is used.
business unit
A unit of an enterprise that performs one or many business functions that can be rolled up in a management hierarchy.
chart of accounts
The account structure your organization uses to record transactions and maintain account balances.
cost center
A unit of activity or a group of employees used to assign costs for accounting purposes.
cost organization
A grouping of inventory organizations that indicates legal and financial ownership of inventory, and which establishes common
costing and accounting policies.
cost profile
Defines the cost accounting policies for items, such as the cost method and valuation structure.
department
A division of a business enterprise dealing with a particular area of activity.
determinant
A value that specifies the use of a reference data set in a particular business context.
division
A business-oriented subdivision within an enterprise. Each division is organized to deliver products and services or address
different markets.
63
Oracle Applications Cloud Glossary
Understanding Enterprise Structures
document sequence
A unique number that is automatically or manually assigned to a created and saved document.
employment terms
A set of information about a nonworker's or employee's job, position, pay, compensation, working hours, and work location
that all assignments associated with the employment terms inherit.
flexfield
A grouping of extensible data fields called segments, where each segment is used for capturing additional information.
inventory organization
An organization that tracks inventory transactions and balances, and can manufacture or distribute products.
item organization
Item definition where inventory balances are not stored and movement of inventory is not tracked in the applications. Item
attributes that carry financial and accounting information are hidden.
legal authority
A government or legal body that is charged with powers such as the power to make laws, levy and collect fees and taxes,
and remit financial appropriations for a given jurisdiction.
legal employer
A legal entity that employs people.
legal entity
An entity identified and given rights and responsibilities under commercial law through the registration with country's
appropriate authority.
line of business
Set of one or more highly related products which service a particular customer transaction or business need. Refers to an
internal corporate business unit.
64
Oracle Applications Cloud Glossary
Understanding Enterprise Structures
manufacturing facilities
Employed in the making of goods for sale such as a factory or plant.
natural account
Categorizes account segment values by account type, asset, liability, expense, revenue, or equity, and sets posting,
budgeting, and other options.
organization
A unit of an enterprise that provides the framework for performing legal, management, and financial control and reporting.
Organizations can represent departments, sections, divisions, business units, companies, contractors, and other internal
or external units of the enterprise. Organization can be classified as project and task owning organizations, and project
expenditure organizations in Project Financial Management applications.
primary ledger
Main record-keeping ledger.
project type
Controls basic project configuration options, such as burdening, billing, and capitalization options, and class categories that
are inherited by each project associated with the project type.
project unit
An operational subset of an enterprise, such as a line of business, that conducts business operations using projects, and
needs to enforce consistent project planning, management, analysis, and reporting.
65
Oracle Applications Cloud Glossary
Understanding Enterprise Structures
registration
The record of a party's identity related details with the appropriate government or legal authorities for the purpose of claiming
and ensuring legal and or commercial rights and responsibilities.
set
Classified and grouped reference data that organizational entities share.
storage facilities
Commercial building for storage of goods such as a warehouse.
tree
Information or data organized into a hierarchy with one or more root nodes connected to branches of nodes. A tree must
have a structure where each node corresponds to data from one or more data sources.
value set
A set of valid values against which values entered by an end user are validated. The set may be tree structured (hierarchical).
work relationship
An association between a person and a legal employer, where the worker type determines whether the relationship is a
nonworker, contingent worker, or employee work relationship.
66