Lesson 3 - Define Common Applications Configuration Overview

Lesson 3: Define Common Applications Configuration Overview
Lesson 3: Define Common Applications Configuration

Overview
Define Common Applications Configuration
Unauthorized reproduction or distribution prohibitedฺ Copyright© 2013, Oracle and/or its affiliatesฺ
Objectives
After completing this lesson, you should be able to:

• Understand the purpose of the common applications configurations ble
fe r a
• Describe the key concepts of common applications configurations for
an s
Procurement
n - t r
• n
Identify the critical common applications configurations for Procurement
o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 77

Common Applications Configuration Overview

Key Concepts:
• All implementation offerings contain two common groups of tasks or task
lists:
–– One that crosses product families
–– One that crosses products within the Procurement product family
• This lesson addresses the common tasks that are available in multiple
offerings, or that apply to multiple products and product families
–– The Define Common Applications Configuration task list includes these ble
common setup and implementation tasks fe r a
–– Most Oracle Fusion Functional Setup Manager (FSM) offerings include ans
n - t r
the Define Common Applications Configuration task list
a no
• Common applications implementation includes taskss of interest to all such
as: h a
) deฺ
–– Define Security c o m u i
i l ฺ G
–– Define Enterprise Structures
–– Define Help Configuration g ma dent
a s t@ Stu tasks which have a more
• Examples of other common
limited audience: ilฺa
b t h is
implementation
a
–– Configuringsreference se provided by Oracle Fusion Middleware
ฺg uobjects
Extensions e r e
for e t o
Applications
il (t licprovided
–– Features
G ens by Oracle Application Toolkit
a Oracle Fusion Applications products such as Oracle Fusion Workforce
––
Te resDeployment and Oracle Fusion Financials
M ฺ
78 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

ble
fe r a
an s
n - t r
a no
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
Setup and Maintenance > a t
s Common
Define S Applications Configuration >
a b t h i s
ฺ g ilฺ Implementation
s e Projects
e s a t o u
e r e
G il (t licens
r esa
ฺT e
M In this course, only the common configuration tasks that are considered
specifically relevant to Procurement will be discussed. Please refer to the prerequisite
courses for details on setup tasks not discussed.

Common Applications Configuration Task Groups

Before you implement Oracle Fusion Procurement components, complete the

prerequisite setup for related Oracle Fusion applications. For example:
• Users
• Enterprise and HR structures
• Security
• Common reference objects
ble
fe r a
ans
n - t r
_______________________________________________________
a no
) has eฺ
l ฺ c om uid
m ai ent G
In the following sections of this lesson,t@
g tudon reference data sharing,
we will focus
enterprise structures, security, and b s is for
aapprovals S procurement. However, the following
table describes, in generalg a
ilฺ allsthe
terms, e h
ttasks you must perform.
ฺ
sa to u
r e e mentioned here may appear in other offerings and may
Setup tasks
i l (teandetask
n slists
already beGcompleted
s a lic if other applications are implemented.
e r e
T
Mฺ Define Common Applications Configuration for Procurement
• Define Synchronization of Users and Roles from LDAP: Run a process to
populate the product tables containing user and role information with the users
and roles held in LDAP. This process is always the first implementation task but
can also run periodically to keep the product tables synchronized with
subsequent updates to LDAP.
• Define Implementation Users: Create implementation users and roles.
Provision implementation users with job and data roles.
• Define Currencies and Currency Rates: Define the currencies and currency
rates that your organization does business in.
• Define Enterprise Structures for Procurement: Configure your divisions,
business units, and legal entities for Procurement usage.
• Define Social Networking: Review options related to social networking and
update as necessary.

• Define Security for Procurement: Enable users to perform functions related to

their job roles.
• Define Automated Governance, Risk, and Performance Controls: Define the
controls that automate the analysis of data-related and address-related issues to
mitigate risk and optimize performance of an organization.
• Define Approval Management for Procurement: Define approval routing

structures and controls to match your organization's needs.
• Define Help Configuration: Define what users can see and do in a local
deployment of Oracle Fusion Applications Help.
• Define Application Toolkit Configuration: Set up Oracle Fusion Application
Toolkit features. These are common across Oracle Fusion applications. e
• Maintain Common Reference Objects: Review and manage common objects, ra
bl
for example profiles and lookups, that affect the functionality and look of ns
fe
applications. n - tra
• Define WebLogic Communication Services Configuration: a nSeto up features
such as Click to Dial.
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
s a G lic
Te re
M ฺ

Demonstration: Common Applications Configuration

Tasks
Background
This demonstration provides a high-level presentation of the Define Common

Applications Configuration for Procurement Oracle Fusion Functional Setup Manager
(FSM) tasks. This is the largest group of tasks in the Procurement offering however
most of the tasks contained within should have been completed by the Financials
ble
implementation team prior to the Procurement team starting their project.
fe r a
ans
n - t r
Steps
a no
) has eฺ
1. Navigate to the Setup and Maintenance worko
c m uid
area.
2. Click the Implementation Projects tab and
l ฺ
ai open t GXXProcurement
your
m
g tude n
Implementation Project. @
t
asgroup. S
3. Expand the Procurement task
a b t h i s
4. Expand the Define ฺ g ilฺ sApplications
Common e Configuration for Procurement task
e s a to u
group.
l ( t er nse
Gi the lDefine
5. Expand
a i ce Synchronization of Users and Roles from LDAP task group.
Te re6.sDiscuss the asterisk preceding the task group name and the Run Users and
ฺ Roles Synchronization Process task within this group.
M Click the View Reports icon for this task group and open the PDF report format
for Setup Task Lists and Tasks.
7. Note that this task belongs to the HCM family and the Global Human Resources
product which is part of the Workforce Development FSM Offering.
Note also the Y in the Required column which confirms the asterisk seen in the
project task list.
Close the Setup Task Lists and Tasks PDF.
8. Continue expanding the remainder of the task groups in the Define Common
Applications Configuration for Procurement task group.
Note that the Define Enterprise Structures for Procurement contains the majority
of tasks and most would be completed by the Financials implementation team or
may be defaulted in by the use of a Fusion Rapid Start implementation.
Note that some of these tasks are discussed in a little more detail in the
Appendix of this course as well as in the implementation guides referenced in the
resources topic in the course overview lesson.

9. Return to the Setup and Maintenance work area.

Click the Done button.
.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT

The InFusion Corporation Story

The Oracle Fusion Procurement Implementation course is based on a fictional yet

realistic enterprise that combines most all of the common aspects of Oracle's
customer base. This is the enterprise that you will be implementing:
Scenario:
• Your company, InFusion Corporation, is a multinational conglomerate that
operates in the United States (US) and the United Kingdom (UK). In the future
ble
you are expanding to other countries in Europe and around the world.
fe r a
• InFusion has purchased an Oracle Fusion solution including Oracle Fusion ans
Procurement. n - t r
n o
• InFusion Corporation has 400 plus employees and revenue a
s of $120 million.
h a ฺ and financial
) healthdecare,
• Your product line includes high technology products,
o m i
services.
a ilฺc nt Gu
• You have two distribution centers and
@ gm t u d e
four warehouses that share a common
item master in the US and thesUK.
a t S
a b h i s
t in the UK provides financing to your
• Your financial serviceslฺorganization
customers. ฺ g i s e
r e sa to u
l te of the
• You are(part
n e
sEnterprise Structure team for your implementation project for
your
G i
US e
operations.
lic
s a
Te
. re
M ฺ

InFusion Global Enterprise Model

The following figure summarizes the model that the InFusion corporation
implementation committee has designed and uses numerical values to provide a
sample representation of that structure. The model includes the following:
ble
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
This diagram illustrates the InFusion Corporation enterprise.
_______________________________________________________

This diagram was created to illustrate the InFusion Corporation Enterprise

Structure in the Oracle Demonstration Solution Services with the following limitations:
• Due to space, only some of the InFusion entities are shown. For example, only
three legal entities and four warehouses.
• Version one of the demo environment does not include a shared service center.
The one shown here is for discussion purposes.
• Version one of the demo environment only has data loaded for US1 LE1 and BU
USA1. The diagram was expanded to include future data for discussion
ble
purposes.
fe r a
ans
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT

Define Enterprise Structures Overview

One of the largest of the common applications FSM task groups is used to
configure your divisions, business units, and legal entities for Procurement
usage.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT Setup and Maintenance > Implementation Projects >
Define Common Applications Configurations for Procurement >
Define Enterprise Structures for Procurement
Some of the FSM task groups are covered in detail in the prequisite course Fusion
Applications: Introduction to Financials Implementation. This course discusses some of
those tasks as they relate to the Procurement implementation.

The Fusion Enterprise

An enterprise consists of legal entities under common control and management.
ble
fe r a
ans
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
In this section of the lesson we will discuss:

• Reference data sets
• Enterprise setup
• Legal entities
• Business units
Facilities
•
______________________________________________________

Fusion Enterprises
• When implementing Oracle Fusion Applications you operate within the context of
an enterprise that has already been created in the application for you by a
system administrator.
• An enterprise organization captures the name of the deploying enterprise and the
location of the headquarters.
• There is normally a single enterprise organization in a production environment.
Multiple enterprises are defined when the system is used to administer multiple
customer companies.
• Organization classifications define the purpose of the organization, whether it's a
department, a division, or a legal entity. e
r a bl
sfe
- t r an
n o n
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT

Define Reference Data Sharing

This section presents the key concepts related to the tasks for reference data
setup for Oracle Fusion Procurement:
• Manage Reference Data Sets
• Manage Set Assignments for Set Determinant Type
ble
fe r a
ans
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT

Reference Data Overview

Reference data sharing facilitates sharing of configuration data such as

locations, payment terms, and supplier site, across organizational divisions such
as business units.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
As illustrated in the preceding graphic, depending on the requirement (specific or

common), each business unit can maintain its data at a central location, using a set of
values either specific to it or shared by other business units.

Reference Data Partitions

You can define reference data, and then depending upon the business context,
decide how to divide the data into partitions (reference data sets) appropriate to
the organizational entities that will use the data.
ble
fe r a
ans
n - t r
a no
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b t
For an organization, you ฺ g ilฺ define
can s ereference data sets of the following types:
s a o u
• Common:
( t e re globally
Used
s e t across the organization as a common set.
–– GForil example,
l i c enat InFusion Corporation, people can reference payment terms
e a the enterprise, so you can create a single set of payment terms and share
sacross
r
ฺ Te
it across the entire enterprise.
M • Shared: Used by a few organizations that work with similar data and therefore
share the sets.
• Organization unit-specific: Unique to that organization business unit and not
shared by any other organization within the enterprise.
–– For example, at InFusion Corporation, people can reference supplier sites
across the procurement business unit, so you can create a set of supplier sites
that are shared by the requisitioning and invoicing business units serviced by the
procurement business unit.

Reference Groups
Reference data sets that share common business policies and legal rules are
treated in the same way and are classified into reference groups.
• Grouping is done on the basis of functional area and the partitioning
requirements that the reference data has in common.
• In Oracle Fusion, the reference groups are predefined in the reference groups
table and are available for selection and assignment to reference data sets.
ble
A reference group for Procurement is listed in the table below. fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT

Determinant Types
You can share the partitioned reference data based on a business context setting
called the determinant type. The determinant types available in Procurement are:
• Business Unit:: A department or organization within an enterprise.
The following table documents the association between reference data and reference
data groups with the business unit (BU) determinant.
ble
fe r a
ans
n - t r
a no
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b t
* Payments Terms on the purchase
ฺ g ilฺ sdocuments
e are determined by the procurement BU
but on the invoices they
e s aare
t o u
determined by the sold-to BU. In a centralized procurement
scenario, wheretthe
( r
e nseprocurement BU can be different from the sold-to BU, the payment
G l
terms shouldi be enabled
i ce and valid in both the procurement and the sold-to BUs.
a l
e r es
M ฺT

Sharing Supplier Site Reference Data

Oracle Fusion reference data rules lead to assigning reference data to the
relevant reference data sets depending upon the required level of sharing the
data.
• Supplier site represents the relationship between a procurement business

unit (BU) and the supplier
–– Supplier site stores terms and controls governing how transactions are
processed between the procurement BU and a specific supplier location ble
fe r a
• Procurement BU maintains supplier sites on behalf of client BUs*
an s
–– Client BUs are assigned to supplier sites to transact with the supplier
n - t r
no
–– Supplier site assignment enables the client BU to use the site
a
has eฺ
–– Avoids duplicate site maintenance and ensures consistent business execution
with the supplier across client BUs )
com Guidand invoicing
* Client BUs represent business units that performilฺrequisitioning
functions, which are serviced by a procurement
g maBU.dent
a s t@ Stu
l ฺ a b t h is
a ฺ gi use
r e s t o
e e
G il (t licens
r e sa
M ฺ Te

Demonstration: Reference Data

Background
In this demonstration, you will explore the use of reference data sets for InFusion USA
enterprises.
ble
Steps
fe r a
1. Use the "Manage Reference Data Sets" task to open the Manage Reference ans
Data Sets page. n - t r
2. Enter "USA" in the Set Code field. a no
3. Click the Search button. ) has eฺ
4. Note the following: l ฺ c om uid
– The Set Code "USA1BUSET". This m ai reference
n t G
@ g tude data set for the USA1
is the
business unit used by InFusion tProcurement.
– The other sets used by theb s isUSA
aInFusion S Inc. enterprise.
a h
e t to the Setup and Maintenance work area.
5. Click the Cancela ฺ gilฺ andureturn
button s
r e s t o
e e
G il (t licens
a
Te res
M ฺ

Define Enterprises for Procurement

Manage Locations
• Create and manage the locations relevant to your enterprise.

• A location identifies the physical addresses of a workforce structure.
• The locations that you create exist as separate structures that you can use
for reporting purposes.
ble
• You enter information about a location only once.
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT

Manage Locations
Use the Manage Locations page to review and modify existing locations, and
create new ones.
ble
fe r a
ans
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Setup and Maintenance > All Tasks > Manage Locations

Location Sets
The following figure shows how locations sets restrict access to users.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
_______________________________________________________
When you create a location, you must associate it with a set. Only those users who
have access to the set's business unit can access the location set and other associated
workforce structure sets, such as those that contain departments and jobs.
You can also associate the location to the common set so that users across your
enterprise can access the location irrespective of their business unit. When users
search for locations, they can see the locations that they have access to along with the
locations in the common set.

Demonstration: Manage Locations

Background
In this demo, you will navigate to the Manage Locations page and open an existing
location to review its settings.
ble
fe r a
Steps ans
n - t r
1. Login as Curtis.Feity
a no
has eฺ page.
2. Use the "Manage Locations" task to open the Manage Locations
)
3. Curtis has access to the China Location Set so enter
Location Set field. l ฺ c om "China
u id Location Set" in the
m ai ent G
g thetuSearch
4. Enter "Bejing" in the City field and click
@ d button.
t S
as hresults.
5. Click the Bejing link in thebsearch
a i s
6. Note the following:ฺgi
lฺ se t
– This locatione u means other workforce structures (for example,
sisaactive.toThat
r
(te can
departments) e it.
suse
i l e n
s
G location
– This
a lic is not associated with any inventory organization. That means the
Te re location will be available for selection in purchase documents
across all inventory organizations.
M ฺ – This is the location's main address. As you learned earlier in this lesson, a
location can have multiple addresses.
7. Add another address to this location by first clicking the Edit button and then
click Correct.
8. On the Edit Location page click the Add Another Address button and then
click the Copy Main Address button.
9. In the Other Address window enter "No. 9 Guang Hua Road" into the Address
Line 1 field.
10. Enter "7th Floor" into the Address Line 2 field.
11. Click the OK button.
12. Click the Submit button, Yes and OK to the confirmation messages, and then
click Done to return to the Setup and Maintenance work area.
13. Sign out.
Define Legal Entities for Procurement

ble
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT .
• A legal entity is a recognized party with rights and responsibilities given by
legislation.
• Legal entities have the right to own property, the right to trade, the
responsibility to repay debt, and the responsibility to 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.
In the diagram above there are two legal entities for InFusion USA Inc. which
reflect different local jurisdiction reporting.
Legal Entities Overview

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 a separate legal identity and therefore conducts aspects of your
business for the following reasons:
• Facilitating local compliance
ble
• Complying with corporate taxation within local jurisdictions fe r a
ans
• Preparing for acquisitions or disposals of parts of the enterprise
n - t r
• n
Isolating one area of the business from risks in another area. For example,
o
a
) has eฺ
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. l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
_______________________________________________________
The Role of your Legal Entity
The contracting party on any transaction is always the legal entity.
Individual legal entities:

• Own the assets of the enterprise
• Record sales and pay taxes on those sales
• Make purchases and incur expenses

• Perform other transactions
Legal entities must comply with the regulations of jurisdictions in which they register. To
support local reporting requirements, legal reporting units are created and registered.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Legal Entity Considerations

Oracle Fusion Applications support the modeling of your legal entities. If you
make purchases from or sell to other legal entities, define these other legal
entities in your customer and supplier registers, which are part of the Oracle
Fusion Trading Community Architecture.
• Legal entities that trade with each other are both represented as legal
entities and also as customers and suppliers in your customer and supplier
registers.
Legal entity relationships are used to determine which transactions are ble
•
intercompany and require intercompany accounting. fe r a
ans
• Legal entities can be identified as legal employers and therefore, are
n - t r
no
available for use in Oracle Fusion Human Capital Management (HCM)
a
has eฺ
applications.T he employees employed by the legal employer can be
assigned as users. )
l ฺ c om uid
a i nt G
m
There are several decisions that need togbe considered de Decision
in creating your legal
entities. Some of these are outlined t @
on the
s is S t u
following pages.
b a
g i l ฺa e th
e s aฺ to us
l ( t er nse
a Gi lice
e r es
M ฺT
Legal Entity in Transactions

Importance of a Legal Entity in Transactions
ble
fe r a
an s
n - t r
a no
) has eฺ
l ฺ c om uid
m ai ent G
Assets and liabilities of the enterprise @ g tudby individual legal entities.
are owned
t S a movement in value or
as thathrepresent
Enter legal entities on transactions
a b i s
obligation.
ฺ g ilฺ se t
r e sa to u
(te ensofea purchase order:
For example,ilthe creation
s a G l ic
e r e• Creates an obligation for the legal entity that books the order to receive the
T goods on the acknowledged date, and an obligation of the purchaser to receive
Mฺ and pay for those goods.
• Provides under contract law in most countries, that 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.
Legal Entity and Business Units

Legal Entity and its Relationship to Business Units
• A business unit that serves your enterprise as a shared service center can
process transactions on behalf of many legal entities.
• The Oracle Fusion Procurement applications rely on deriving the legal
entity information from the business unit.
ble
fe r a
In some cases, the transaction legal entity is inferred from other reference entities that
ans
are themselves linked to a single legal entity.
n - t r
•
a no
For example, a payables invoice has an explicit legal entity field.
• The accounts payables department can process supplier
) hasinvoices
e ฺ on behalf of
one or many business units. m
co Guid
In some cases, your legal entity is inferred froma i l ฺ
your businesst unit that is processing
g m e n
the transaction.
s t @ Stud
l ฺ a ba this
a ฺ gi use
r e s t o
e e
G il (t licens
r e sa
Te
Mฺ
Legal Entity and Divisions

ble
fe r a
an s
n - t r
a no
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
Legal Entityiland
e se
(teits Relationship
n to Divisions
G l i c
a division is an area of management responsibility that can correspond
• sThe
r e
ฺ Te
to a collection of legal entities.
M • Aggregate financial results for divisions by legal entity or by combining
parts of multiple legal entities.
• Define date-effective hierarchies for the segment that represents the
management entity in the chart of accounts to facilitate the aggregation
and reporting by division.
Legal Entity and Ledgers

ble
fe r a
ans
n - t r
a no
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
e n se
(teits Relationship
Legal Entityiland to Ledgers
G li c
a legal entities
• sMap to specific ledgers using the Oracle Fusion General
r e
ฺ Te
Ledger Accounting Configuration Manager.
M • Within a ledger, optionally map a legal entity to one or more balancing
segment values.
Legal Entity and Intercompany Transactions

ble
fe r a
t r a ns
Use Oracle Fusion Intercompany functionality to automatically create
intercompany entries across your balancing segments. n on-
s a
• Intercompany transaction processing updates the accounting
) a
h eฺbalances within the
enterprise's groups of legal entities.
l ฺ c om uid
• Invoices or journals are created as needed
m ai to record
e n t G
the intercompany payable
or receivable. g
@ Stud
s t
a forhiyour
• Limit the number of trading
ฺ a bpairs
t s enterprise by setting up intercompany
ฺ l
gi uthen
organizations and assigning
s e to your authorized legal entities.
e
• Define processing
a
s optionst o and intercompany accounts to use when creating
e r e
(t transactions
intercompany
G ilaccounts
c e ns derivedand to assist in consolidation elimination entries.
s
These
a li are and automatically entered on your intercompany
e r e transactions based on legal entities assigned to your intercompany
M ฺT organizations.
Intracompany trading is also supported.
For example, you can track assets and liabilities that move between your departments
within your legal entities by creating departmental level intercompany organizations.
Legal Entity and Legal Reporting Units

ble
fe r a
ans
n - t r
a no
) has eฺ
l ฺ c om uid
m ai ent G
Legal Reporting Units
@ g tud
t
s is S legal reporting units are created
• To support local reportingarequirements,
and registered. l ฺ a b th
g i e
• When you first e s aฺ taolegal
create us entity, the Oracle Fusion Legal Entity
Configurator
l ( t er automatically
n se creates one legal reporting unit for that legal
G
entityi with laic e
registration.
r e sa
M ฺ Te
For more detailed information on legal reporting units click Help, from Functional
Setup select the Financials offering, and in the Search box enter legal reporting units.
Demonstration: Creating a Legal Entity

Background
You are implementing the enterprise structure for your organization. In this
demonstration you are creating a legal entity and a legal entity registration. Define a
legal entity for each registered company or other entity recognized in law for which you
want to record assets, liabilities, and income, pay transaction taxes, or perform
intercompany trading. The legal entity registration is the record of a party's identity
related details with the appropriate government or legal authorities for the purpose of ble
claiming and ensuring legal and or commercial rights and responsibilities. fe r a
an s
n - t r
a no
Steps ) has eฺ
l ฺ c om uid
Legal Entity: m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se tproject is required because you select a scope
Note: Working within an implementation
value within an implementation
e u The scope value is the legal entity that you will
sa toproject.
r se for your implementation project.
ework nwithin
create or select(tto
i l e
1. Use
s a lic Legal Entities task list within your implementation project to
Gthe Define
e r e start.
T Note: The Scope Selection: Legal Entity message opens with a choice to
Mฺ Select and Add or Create New.
2. Select the Create New button.
3. From the Manage Legal Entities page select the Create icon.
4. Accept the default Country, United States.
5. Enter the following:
Name = "XXInFusion USA West"
Legal Entity Identifier = "XXUS0033"
6. Optionally enter the following:
Start Date (When the start date is blank the legal entity is effective from the
creation date.)
End Date
Payroll statutory unit = No
Legal employer = No

Legal Address = select "500 Oracle Parkway,REDWOOD CITY, CALIFORNIA
94065"
Place of Registration = "Sacramento, CA"
EIN or TIN = 999-01-0000
Registration Number = 5551212

8. Click the Save and Close button. Continue with the following steps.
Legal Entity Registration:

1. Select and Add to select the scope value as your "XXInFusion USA West" legal
entity. e
2. A legal entity registration with the same name as that of the legal entity will be era
bl
created by default.
a n sf
To verify this, locate the Manage Legal Entity Registrations task and
o n -trthen
select Go to Task.
a n
3. To create another registration for the legal entity select
) h aGos to ฺTask for the
Define Legal Entities task list within your implementation
o e
m uidproject.
l ฺ c
m ai ent G
g tudto open the Manage
4. Use the Manage Legal Entity Registrations
@
Registrations page. t
as his S
Click the Create icon. ฺab t
ฺ g il s e
e a to u
sselect
Jurisdiction
( t r
e nse"California Income Tax"
=
l
Gi lAddress
Registered
i e = select "500 Oracle Parkway,REDWOOD CITY,
c94065"
a
CALIFORNIA
Te resRegistered Name = "XXInFusion USA West"
M ฺ Registration Number = 5551212
6. Click the Save and Close button.
Define Business Units for Procurement

This section presents the key concepts related to the tasks for business unit
• Assign Business Unit Function
• Manage Service Provider Relationships
• View Service Clients
ble
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Manage Business Units

A business unit is a unit of an enterprise that performs one or many business

functions that can be rolled up in a management hierarchy. A business unit can
process transactions on behalf of many legal entities.
ble
fe r a
ans
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Oracle Fusion Accounting Hub facilitates independent balance sheet rollups for
legal and management reporting by offering four 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.
For Oracle Fusion applications that generate transactions that are recorded in the
general ledger, you 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 required for your business units with business
functions that produce financial transactions. e
r a bl
s fe
- t r an
n o n
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Business Units Overview

In Oracle Fusion Applications, 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.
ble
fe r a
The Oracle Fusion Applications business unit model: ans
n - t r
• Allows for flexible implementation
a no
) h s transactions
• Provides a consistent entity for controlling and reportingaon
eฺ
• Anchors the sharing of sets of reference data across
o m d
applications
i
a
Business units process transactions using reference Guthat reflect your business
ilฺcdatantsets
@ gmto country.
rules and policies and can differ from country
t u de With Oracle Fusion Application
functionality, you can choose to share t
as referenceSdata, such as payment terms and
a b h i s
ฺ
manage its own data setadepending s e tor you can choose to have each business unit
gilฺ uunits,
transaction types, across business
on the level at which you wish to enforce common
policies. r e s t o
e e
G il (t licens
User e sa
business units in the following ways:
e
ฺ T • Management reporting
M
• Processing of transactions
• Security of transactional data
• Reference data definition and sharing
Business Unit Considerations

Implementation Key Considerations
ble
fe r a
an s
n - t r
a no
) h as ฺ
General Business Requirements m uide
l ฺ c o
• What reporting do you need by business
m ai unit? n t G
e and business unit roll-
• How will you structure your ledgers,
@ g legal
t u dentities
ups? t
as his S
a b t
lฺ departments
• How can you set up
ฺ g iyour s e or business unit accounts to achieve
departmental e s a
hierarchiest u
o that report accurately on your lines of business?
e r e
l (t icedo
• Whatireporting
G nsyou need to support the managers of your business
sunits,
a and the l executives who measure them?
e e
r • How often are business unit results aggregated?
ฺ T
M • What level of reporting detail is required across business units?
Procurement Business Requirements

• What service provider model do you need?
Business Unit Security

• Business units are used by a number of Oracle Fusion Applications to

implement data security.
• You assign data roles to your users to give them access to data in
business units and permit them to perform specific functions on this data.
ble
fe r a
ans
n - t r
a no
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
asgenerated S when the business unit is created.
• Data roles are automatically
a b t h i s
• Business function ฺ g ilฺ sdata
specific e roles will be generated when business
s a o u
functions are
( t e reassigned.
s e t
• These
G c enmust still be granted through Oracle Identity Manager
il dataliroles
a
(OIM).
Te res
M ฺ
_______________________________________________________
For example, if a payables invoicing business function is enabled, then it is clear that
there are employees in this business unit that perform the function of payables
invoicing, and need access to the payables invoicing functionality.
Therefore, based on the correspondence between the business function and the job
roles, appropriate data roles are generated automatically. Use Human Capital
Management security profiles to administer security for employees in business units.
Business Functions Overview

A business unit can perform many business functions in Oracle Fusion

Applications.
• Business Unit Usage: 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.
• Business Unit Fucntion: A business function logically indicates a presence of a
department in the business unit with people performing tasks associated with
these business functions. ble
fe r a
• Business Unit Departments: A business unit can have many departments
an s
performing various business functions.
n - t r
• a no
Business Unit as Structure: Optionally, you can define a hierarchy of divisions,
represent your enterprise structure. ) has eฺ

business units, and departments as a tree over HCM organization units to
ฺ c om uid
Note: This hierarchy definition is not required in the setup of your applications,
l
but is a recommended best practice. m ai ent G
@ g tud
• Business Unit Transactions:
a t
s isa business
When S function produces financial
transactions, a business
l b thbe assigned to a primary ledger, and a default
ฺaunit must
legal entity. ฺ g i s e
–– Each business e s aunit o
posts
t utransactions to a single primary ledger, but it can
t e r e
G c e ns for many legal entities.
il (transactions
process
s a li
r e
ฺ Te
M
Prior to Oracle Fusion Applications, operating units in Oracle EBusiness Suite
were assumed to perform all business functions, while in Oracle PeopleSoft , each
business unit had one specific business function. Oracle Fusion Applications blends
these two models and allows defining business units with one or many business
functions.
Business Unit Hierarchy Example

For example, your InFusion America Company provides:

• Air quality monitoring systems through the division InFusion Air Systems
• Customer financing through the division InFusion Financial Services
The InFusion Air Systems division further segments the business into the System
Components and Installation Services subdivisions which are divided by
business units:
• System Components by products: Air Compressors and Air Transmission ble
fe r a
• Installation Services by services: Electrical and Mechanical
ans
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Business Units in the Procure to Pay Flow

Configure business units for the following procure to pay transactions.
Procurement Business Unit

• Is a business unit with the Procurement business function.
• Establishes a relationship with a supplier through the creation of a site, which
maintains internal controls for how procure to pay transactions are executed with
the supplier. ble
fe r a
• Manages, owns, and is responsible for purchasing transactions.
an s
n - t r
Requisitioning Business Unit a no
has eฺ
• Is a business unit with the Requisitioning business)function.
• Manages and owns requisitioning transactions.l ฺ c om uid
m ai ent G
@ g tud
Sold-to Business Unit
t
as his S
a b
ฺ Payablest Invoicing business function.
ฺ
• Is a business unit withg ilthe s e
e a to u
sinvoicing
• Responsible
( t r
e nse transactions.
for
• Assumes
l
Gi thelicliability
e for the purchases made on behalf of a client business unit.
es a
T e r
Mฺ
ble
fe r a
ans
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
Setup and Maintenance > Define Business Units > Assign Business Unit Business
e r e
M ฺT Function
Example
The figure provides an example of business function assignment. The Business Unit
USA1 Business Unit performs the requisitioning, procurement, and invoicing business
functions. USA1 Business Unit is enabled as a Procurement business unit, a
Requisitioning business unit, and a Sold-to business unit.
Service Provider Model

Shared service centers are supported in two ways.

• Service provider model: Allows a business unit to act as a service provider to
client business units, so that the personnel in a shared service center can
process transactions on behalf of client business units.
• Business unit security: Allows shared service center personnel to process
transactions for other business units. e
r a bl
Service Provider Model
s fe
- t r an
no
Use the service provider model to centralize the procurement business function. Define
n
a
)
clients of a business unit with the Procurement business function.has eฺ
business units with Requisitioning and Payables Invoicing business functions as
l ฺ c om uid
m ai ent G
The following figure illustrates a scenario where
@ g business
t u d unit BU 1 provides
t S 2 performs Requisitioning and
bas tThe
procurement services for business unit BU 2. BU
a
Payables Invoicing businesslฺfunctions. h isservice provider relationship is defined
g i e
with BU 1 as a service a
e s ฺ
provider
t o us
for BU 2.
l ( t er nse
a Gi lice
e r es
M ฺT
Service Provider Model Example

The following figure depicts an example of service provider setup where business
unit USA1 Business Unit is its own procurement service provider.
ble
fe r a
ans
n - t r
a no
) has eฺ
l ฺ c om uid
Setup and Maintenance > Define Businessm aiUnitse>nManage
t G Service Provider
g tud
Relationships
@
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Business Unit Scope in FSM Tasks

Define Business Unit Configuration

• Sets the context of the FSM Task List
• Sets the context for Export and Import tasks
• Used for Business Unit related setup in Define Business Units for
Procurement task group
- Configure Procurement Business Function
- Configure Requisitioning Business Function
ble
• Used for Business Unit related setup in Purchasing Configuration task fe r a
group an s
- Configure Procurement Business Function n - t r
- Configure Requisitioning Business Function n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Setting Business Unit Scope for FSM Tasks

• When defining or maintaining business units, the scope value is the business
unit. Once you create, or select and add the business unit, it will appear in the
Business Unit drop down list, in the Basic Information region of the
implementation project.
• The business unit (scope value) that you want to work with must be selected
from the Basic Information region, prior to selecting any task.
• You create a new business unit (scope value) by clicking the Create New button.
Demonstration: Defining Business Units

Background
In this demonstration, you will define and maintain business units, and service provider
relationships as part of implementing the enterprise structure for the organization.
Steps
ble
1. In your XXProcurement Implementation project click Go To Task for the Define
fe r a
Business Units for Procurement task.
t r a ns
2. The Implementation Project page opens for the Define Business n
o - for
Units
Procurement task group. n
a region of the
Open the Business Unit drop down list in the Basic Information a s
Implementation Project page. m ) h deฺ
Click the Create New Business Unit list item.
i l ฺ co Gui
3. On the Manage Business Units page
a theeCreate
mclick n t icon.
g
@into the tuNamed
4. Enter "XXInFusion Manufacturing" s t
a his S field.
a b t
5. Select the referencegdata
ฺ ilฺ setsbye opening the Default Set list and select the
ENTERPRISE s
e a
set.
t o u
e r e
l (tSave
6. Click ithe
G c e nsClose button.
and
a the Business
7.sFrom li Unit drop down list, identify the business unit that you will
r e
ฺ Te work with.
Select and add the business unit that you created.
M Click the Select and Add Business Unit list item.
8. The Business Units search window opens.
Enter the desired information into the Name field. Enter "XXInFusion".
Click the Search button.
9. Click the XXInFusion Manufacturing row header.
Click the Save and Close button.
10. Select the Assign Business Unit Business Function task to assign business
functions for your selected business unit.
Click the Go to Task icon.
11. Use the Assign Business Functions page to assign all business functions that
this business unit will perform.
Billing and Revenue Management = Enabled
12. Business functions that generate financial transactions will require a primary
ledger and a default legal entity.
Note that the required legal entity must be assigned to the ledger as a requisite,
before it will display as available in this step.
Open the Primary Ledger list and select the InFusion USA PL list item.
13. Continue assigning business unit functions:
Customer Payments = Enabled
Payables Invoicing = Enabled

Procurement = Enabled
Receiving = Enabled
Note that XXInFusion Manufacturing has been selected as the business unit
(scope value).
15. Create a new business unit that will serve as a service client business unit, ble
XXInFusion Services. fe r a
The service provider business unit, XXInFusion Manufacturing, will provide the an s
procurement business function to XXInFusion Services. n - t r
XXInFusion Services will have the requisitioning business function.
a no
has eฺ
Open the Business Unit list and click the Create New Business Unit list item.
)
16. On the Manage Business Units page click the Create
l ฺ c om uicon.id
i G
17. Enter "XXInFusion Services" into the Name
g ma field. e n t
18. Select the reference data set byt@
s tudDefault Set list and select the
opening the
S
ENTERPRISE set.
l ฺ a ba this
19. Click the Save andฺg i button.
Close s e
e s a t u
oProject page, select and add the new business unit.
e r
20. On the Implementatione
G l (tBusiness
Openithe
c e ns Unit list and click the Select and Add Business Unit list
s a
item. li
er e
T 21. Select the newly created "XXInFusion Services" on the Manage Business Units
Mฺ window.
23. Your new business unit should now show in the Business Unit field. If not, open
the Business Unit list and click the XXInFusion Services list item.
24. Assign the requisitioning business function to the new business unit.
Select the Assign Business Unit Business Function task and click the Go to Task
icon.
25. Assign business unit functions:
Billing and Revenue Management = Enabled
Requisitioning = Enabled
26. Select the same Primary Ledger and Default Legal Entity as for XXInFusion
Manufacturing.
28. You will now define the service provider relationship.

Begin by selecting the service client business unit XXInFusion Services.
Confirm that the Business Unit scope value is set to the requisitioning business
unit.
Select the Manage Service Provider Relationships task and click the Go to Task
icon.
29. Click the Add Row button to add the business unit that will process requisitions
on behalf of InFusion Services.
30. Search for the service provider business unit.
Enter Enter "XXInFusion Manufacturing" into the Name field and click the Search
button.
31. Click the XXInFusion Manufacturing list item. ble
fe r a
32. Click the Done button. s
33. Click the Save and Close button. - t r an
no n
34. View the service client for XXInFusion Manufacturing. a
XXInFusion Manufacturing. ) has eฺ
Open the Business Unit list and select the service provider business unit
l ฺ c om uid
35. Select the View Service Clients task anda i thenGo
click t Gto Task icon.
Note that XXInfusion Services is listed m de client of XXInFusion
g as atuservice
t @
Manufacturing.
a b as his S
36. Click the Done button.ilฺ
g e t
ฺ u s
a demonstration
This concludessthis of defining and maintaining business units,
and service r e
provider t o
relationships.
i l (te ense
s a G lic
Tere
Mฺ
Define Facilities for Procurement

This section presents the key concepts related to the tasks for Fusion facilities
• Manage Inventory Organizations
ble
fe r a
an s
n - t r
a no
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
_______________________________________________________
r e sa to u
i l (te ense
a
The other
s
G ic Define Facilties list are only required when performing a Oracle
tasks in lthe
r e Materials Management and Logistics implementation:
Fusion
e
M ฺT • Manage Facility Shifts
• Manage Facility Workday Patterns
• Manage Facility Schedules
• Manage Facility Schedule Exceptions
Manage Inventory Organizations Overview

Inventory organizations are used to:

• Control the availability of attributes for items and item security
• Associate inventory organizations with a business unit or legal entity as
required
ble
fe r a
ans
n - t r
a no
_______________________________________________________
) has eฺ
l ฺ c om uid
m ai ent G
Manage Inventory Organizations Overview @ g tud
t
as his S
a b
ฺ g ilฺ se t
An inventory organization
e saorisstore u or physical entity in the enterprise that is used to
a logical
t o
store definitionstof
( ritems
e nse and transact items. Configure inventory organizations
l
Gi or distribution
to describe distinct entities
i ce within the company such as manufacturing facilities,
a
warehouses, l centers.
e r es
M ฺT
Inventory Organization Usage

You select the following usages in the inventory organization's properties:

• Item management
• Item and inventory management
ble
fe r a
an s
n - t r
a no
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to >uAll Tasks > Manage Inventory Organizations
Setup and Maintenance
i l (te ense
sa
G lic
e r e
M ฺ TItem Management
• Inventory organizations used for item management, which are the same as item
organizations, store only definitions of items.
• Use inventory organizations for item management when the storage or
movement of inventory does not need to be physically or financially tracked.
For example, in a retail implementation you can create an inventory organization
for item management to store the names of items that are listed by and sold
through each retail outlet, while a different system tracks physical inventory and
transactions.
• If it is necessary in the future, you can change an inventory organization's usage
from item management to item and inventory management in the inventory
organization's properties.
Item and Inventory Management

• Inventory organizations used for item and inventory management store and
transact items, in addition to item definitions.
• An inventory organization used for item and inventory management is associated
with one business unit, one legal entity, and one primary ledger.
• Use inventory organizations for item and inventory management when the
storage or movement of inventory needs to be physically and financially tracked.
• Inventory organizations used for item and inventory management can represent
facilities such as manufacturing centers, warehouses, or distribution centers.
• You cannot change an inventory organization's use from item and inventory
management to item management.
ble
fe r a
ans
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Demonstration: Manage Inventory Organizations

Background
In this demo, you will navigate to the Manage Inventory Organizations page and open
an existing inventory organization to review its settings.
ble
Steps
fe r a
1. Use the "Manage Inventory Organizations" task to open the Manage Inventory an s
Organizations page. n - t r
2. Enter or select the "USA1 Business Unit" in the Business Unit field. a no
3. Click the Search button. ) has eฺ
c o m uid
4. In the Search Results region select the "001"
a l ฺ
i nt G Organizations and click the Edit
icon.
@ gm tude
5. In the Basic Information Region
b a st notei s S following:
the
– The Seattle Warehouse
i l ฺ a has
e t h
Usage set as "Item and Inventory management"
g usLegal Entity are required Basic Information fields
– Name, Business
e saฺ Unit,
– Code is a rrequired fieldt o
and
for Location Address
l e nse
(tNext
6. Click
G i
the
l i cebutton.
a
Te re7.sNote the following in the General Information region of the Manage Inventory
Organization Parameters page:
M ฺ – Schedule, Item Master Organization, Starting Revision, and Locator
Control are required fields
8. Click the Cancel button.
9. Click the Done button.
Define Security for Procurement

This section presents the key concepts related to the tasks for function and data
security in support of Procurement implementation:
• Viewing security details such as role definitions and the roles provisioned
to users
• Differentiating between provisioning a user with a job role versus a data
role
ble
• Determining the usefulness for your enterprise of Human Capital fe r a
Management (HCM) security profiles, role provisioning rules, and ans
extending the security reference implementation n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Security Key Concepts

In Oracle Fusion Applications:

• Role-based Access Control (RBAC): Grant function and data access to users
through the roles assigned to them, not to the users directly.
• Function Security: Provide users with access to pages in application user
interfaces and controls the actions that can be performed on those pages.
• Data Security: Allow or restrict access to data in pages depending on policies,
conditions, masking, and encryption.
ble
• Privacy: Secures data that should not be available to other individuals and fe r a
organizations, or data whose exposure and use is under the owner's control. an s
n - t r
•
a no
Access Provisioning and Identity Management: Processes for managing user
identities, user accounts, role assignments, and enterprise role definitions.
) h as ฺ
• Segregation of Duties Policies: Prevent or detect unintentional e errors and
c om and
willful fraud by separating activities such aslฺapproving u idprocessing results.
a i nt G
• Enforcement across Tools, Technologies, g m dData e Transformations, and
t
Access Methods: Coordinatestransactional @ t u
S and analytical security across all
components of a deployment. b a i s
g i l ฺa e th
• Enforcement across
e s aฺ the t o us
Information Life Cycle: Protect data in transit and at
( t r phases
rest acrossethe
s e of a deployment from installation to archive and purge.
l
Gi Reference
• Security
n
ce Implementation: Provides a baseline set of roles, policies,
a l i
Te resHuman Capital Management (HCM) security profiles, and templates that match
the business needs of most enterprises.
M ฺ
Role-Based Access Control

An enterprise needs to control: Who can do what on which functions or sets of

data under what conditions?
ble
fe r a
ans
n - t r
a no
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
To understandi l te Fusion
(Oraclee n se security ask the question “Who can do What on Which
a G
set ofsdata?" lic
e r e
M ฺ T • Who: The who is the user. A user's access is based on the definition of the roles
provisioned to the user.
–– Note that access is defined as entitlement, which consists of privileges .
• What: The what are the abstract operations or entitlement.
• Which: The which represents the resources being accessed. For example, view
and edit are actions, and task flows or rows in data tables are resources.
Types of Security Roles

Three types of roles can be provisioned to users to match the user's function and
position in an enterprise. These enterprise roles, also called external roles, are:
• Job Role: Specific to a job, and controls access to functions through inherited
duty roles that carry the entitlement necessary for performing specific tasks
associated with the duties of the job, such as access for a procurement manager.
• Abstract Role: Like a job role, but not specific to a particular job, and controls
common access, such as access for all employees or contingent workers.
ble
• Data Role: Specific to a job within a dimension of data, and augments the
fe r a
inherited abstract, duty, or job roles with entitlement to access specific data, such
an s
as access for a procurement manager in a particular business unit.
n - t r
n o
A fourth type of role is the duty role, also called application role. Duty roles cannot be
a
) has eฺ
provisioned directly to users, but are inherited by enterprise roles to control access to
applications. Duty roles may carry both function and data security grants.
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
ble
fe r a
ans
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Security Role Hierarchy

Role definitions consist of a role hierarchy. The following setup tasks manage
role hierarchies.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Procurement Job and Abstract Roles

Requester Roles:
• Procurement Requester
• Procurement Preparer
• Advanced Procurement Requester
Procurement Agent Roles:

ble
• Buyer
fe r a
• Category Manager ans
n - t r
• Procurement Manager
n o
a
• Procurement Contracts Administrator
) has eฺ
• Procurement Catalog Administrator
l ฺ c om uid
• Procurement Applications Administrator ai t G
m
g tude n
• Supplier Administrator t @
a b as his S
Sourcing Roles: ฺ g ilฺ se t
e t o u
saCollaborator
r
• Sourcing Project
(te ense
i l
s
Suppliera G
User
lic
Roles:
e r e
M ฺ T • Supplier Bidder
• Supplier Accounts Receivable Specialist
• Supplier Customer Service Representative
• Supplier Demand Planner
• Supplier Sales Representative
• Supplier Self Service Administrator
• Supplier Self Service Clerk
Function and Data Security

Functions and data are inaccessible to users unless they are provisioned with the
roles necessary to gain access.
Function Security
• “Who can do What on Which set of data?"
• Consists of privileges unconditionally granted to a role and used to control
access to: ble
- A page or a specific widget fe r a
- Functionality within a page, including services, screens, and flows. an s
n - t r
Data Security
a no
• “Who can do What on Which set of data?"
) has eฺ
• Consists of privileges conditionally granted as data
c o m security
u id policies carried by
l ฺ
ai en(HCM)
roles, or granted as Human Capital Management t G security profiles, and
used to control access to data: m
g tud
- Within a business object such t @
s ibusiness
as a S unit
- Based on user profile aba s
g ilฺ se th
- Based on privacyฺpolicies
e samight give
t o u
For example, a job rrole
(te enpages,se butview access to the functions needed to access
procurementilapplication a data role that inherits the job role gives view
accessato G
s lic data within a business unit, such as the data role
the procurement
r e
Procurement
e Manager - US which inherits the job role Procurement Manager for
ฺ Tperforming procurement duties against the US business unit.
M
Some data, such as some setup and transaction data, is not secured, in which case
access to a user interface page gives unrestricted access to the data that is accessible
from that page.
ble
fe r a
ans
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT An example of delegated administration is having different IT security manager users
manage users, roles and role assignments within specific Oracle Identity Management
(OIM) organizations instead of having one IT security manager user manage all users
and roles across all OIM organizations.
For an overview of how the various integrated products contribute to security, see
Security Components: How They Fit Together in the Oracle Fusion Application Security
Guide.
Access Provisioning and Identity Management

Access provisioning and identity management involves:

• Creating and managing user identities: Includes specifying the name and
other attributes of a user identity.
• Creating and linking user accounts to user identities: Linking to a Human
Capital Management (HCM) person or a Supplier contact.
• Managing user access control through user role assignment: Assigning a
role manually to a user or automatically through role provisioning rules.
bl e
• Managing security on workflow approvals and delegated administrationfof e r a
n s
to sales roles, rather than having the IT security manager approve n -
such
traaccess.
approvals: Includes having the owner of a sales line of business approve access
a no
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
s a G lic
Te re
M ฺ
Security Reference Implementation

The security reference implementation is a baseline set of predefined security

definitions.
• Abstract, job, and duty roles in hierarchies that streamline provisioning access
to users.
• Data role templates that generate data roles when enterprise structures are
defined.
• Data security policies that specify actions allowed on data under certain
ble
conditions
fe r a
• Segregation of duties policies that control risk through integration with the ans
Governance, Risk, and Compliance Controls (GRCC) product. n - t r
no
– Predefined duty roles carry no inherent segregation of duties risk.
a
) has eฺ
c om uid
_______________________________________________________
l ฺ
m ai ent G
@ g tud
The details of the security reference t S are presented in the security
asimplementation
a b h i s
t and can be viewed using the tasks available
reference manual (SRM) for ieach
ฺ g lฺ offering,
s e
for managing roles, templates,
a to u and security policies.
e s
l ( t er nse
Giand actions
All functions
a l i ce in Oracle Fusion Applications that need to be secured are
e r es by the security reference implementation. It should not be necessary to create
covered
M ฺ Tnew duty roles, except in cases where functions are being customized or new functions
are being added.
In cases where the predefined security reference implementation does not adequately
represent the needs of your enterprise, you can make changes. For example, a
predefined job role may be too narrowly defined. You can create a new job role and give
it a role hierarchy of fewer or different duty roles than a similar predefined job role, and
provision your newly created job role to users who should have broader access.
The security reference implementation in Oracle Fusion Applications provides a

complete, predefined security implementation that is applicable to the needs of midsized
(generally between 250 and 10,000 employees), horizontal enterprises and can be
changed or scaled to accommodate expansion into vertical industries such as health
care, insurance, automobiles, or food manufacturing.
Defining Data Security

Data security controls access to data by the following means:

• Data Security Policy: Grants access to roles by means of entitlement.
• Data Role: Applies data security policies with conditions to users provisioned
with the role.
• Data Role Template: Defines the data roles generated based on enterprise
setup of data dimensions such as business unit.
• HCM Security Profile: Defines data security conditions on instances of object ble
types such as person records, positions, and document types without requiring fe r a
users to enter SQL code. an s
n - t r
•
a no
Masking: Hides private data on non-production database instances.
) h as ฺ authorization
• Encryption: Scrambles data to prevent users without decryption
from reading secured data.
l ฺ c om uide
m ai ent G
@ g tud
t
as his S
b
_______________________________________________________
a
ฺ g ilฺ se t
r e sa to u
Depending on the
l ( t e nsethe Define Data Security activity can include tasks such as
offering,
Gi lice
the following:
a
e r e• sManage Data Access Sets for managing a set of access privileges to one or
M ฺT more ledgers or ledger sets
• Manage Segment Security for managing balancing or management segment
values to secure data within a ledger
• Manage Role Templates for managing data role templates to update or create
new data roles
• Manage Data Security Policies for managing access to the database resources
of an enterprise
• Manage Encryption Keys for managing encryption keys held in Oracle Wallet to
secure Personally Identifiable Information (PII) attributes
Data Security Policies

A data security policy is a statement in a natural language, such as English, that

typically defines the grant by which a role secures business objects. The grant
records the following:
• Table or View: Logical business objects or dashboards
• Entitlement: Actions expressed by privileges
• Condition: Readable WHERE clause identifying entire data object, object
instance, or object instance set
ble
Data security policies articulate the security requirement "Who can do What on Which fe r a
n s
set of data."
n - tra
For example, purchasing managers can view purchase order disbursements n o for their
business unit. Use the Manage Data Security Policies task to s a
modify data security
policies. h a
) deฺ
c o m ui
i l ฺ G
Data security policies that use job or duty roles g mareferdtoedatant security entitlement. For
example, the data security policy for s t@
the tu Manager job role refers to the
Procurement
S
view action on PO disbursements a
abas the s
hi security entitlement.
data
i l ฺ e t
s a ฺg us
e r e e t o
i l t
In the following(figure, a
nuser
s provisioned with the Marketing Analyst job role can view
sales partyG data for
l i c e
sales account team resources in the user's management chain
based a
sas defined for the Sales Party Review Duty role, which the Marketing Analyst job
einherits.
e r
role
M ฺT
The duty roles inherited by the job role can be moved and job roles reassembled
without having to modify the data security.
In the following figure, data security policies are defined for a data role in addition to the
data security policies defined for the base role that the data role inherits.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
As a security guideline, data security policies based on user session context should
entitle a duty role. This keeps both function and data security policies at the duty role
level, thus reducing errors.
You use a data role when the data dimension cannot be derived from the current user
session. For example, you cannot know the business unit of a user is authorized to use
the user's session context. You use a data security policy against a duty role if you can
derive the data dimension from a user session context. For example a data security
policy can entitle a user to update a project that the user is a Project Team Member of.
Data Role Templates

Data role templates generate data roles based on enterprise setup. Changes to
data role templates generate new or changed data roles.
The following attributes define a data role template:

• Template Name and Description
• Template Group ID: Aids in searching for templates
ble
• Base Roles: Determines the job and abstract roles inherited by the generated
fe r a
data role
t r a ns
• Data Dimension: Expresses stripes of data. For example, territorial
n o n-or
geographic information you use to partition enterprise data such a as a business
unit. s
ha eฺ
– Dimension value: A specific stripe of data, suchm as) a US business unit, or a
c
reference data set used in reference data sharing. o u i d
a ilฺ nt G
• Data Role Naming Rule: Determines
@ gm how the e
t u d names of the generated data
roles are constructed, such assat concatenation
S of base role and data dimension.
b a i s
• Data Security Policies:
g i l th to a business object such as an invoice,
ฺaGrantseaccess
with an entitlement,
s s
aฺ suchtoasuview.
t e
er nse
l (
a Gi lice
Te res _______________________________________________________
M ฺ
Use the Manage Role Templates task to create or change data role templates, or
generate data roles from role templates.
If you add a dimension value to your enterprise that is used by a data role template, you
must regenerate roles from that data role template to create a data role for the new
dimension.
If you add a base role to an existing data role template, you can generate a new set of
data roles. If the naming rule is unchanged, existing data roles are overwritten.
If you remove a base role from a data role template and regenerate data roles, a
resulting invalid role list gives you the option to delete or disable the data roles that
would be changed by that removal.
Related Reference: For information on working with data role templates, see the
Oracle Fusion Middleware Administrator's Guide for Authorization Policy Manager
(Oracle Fusion Applications Edition).
ble
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Data Role and HCM Security Profiles

• A data role is a type of job or abstract role.

Not all job or abstract roles have corresponding data roles, but if a data role
exists, provision the data role to the user, not the underlying job or abstract role.
• A data role carries the function security entitlement inherited from the role
hierarchies and data security entitlement conditionally granted on each
object and condition.
• Define data roles based on the data security requirements of the
enterprise. ble
For control and performance reasons, data roles commonly limit access within fe r a
tools, applications, or areas of a deployment such as departments or cost ans
n - t r
centers.
a no
) has eฺ
l ฺ c om uid
ai ent G
_______________________________________________________
m
@ g tud
t
as his S
ฺ a b t
ฺ g ileither s e
Data roles are created using
e s a to u role templates or by associating HCM
data
( t r job
security profilesewith a
s e or abstract role to define an HCM data role.
• Use G il Manage
the
l i c enRole Templates task to manage the templates that generate
e a roles.
sdata
r
M ฺ Te • Use the Manage Data Roles and Security Profiles task to create and maintain
HCM data roles in Oracle Fusion Human Capital Management (HCM), which
uses HCM security profiles, not data role templates, to define the data security
condition.
Defining Users Overview

When business unit and legal employer have been defined as part of setting up
enterprise structures, you define users by using the Manage Users task, or
automatically in Human Capital Management (HCM) when creating person
records .
The identity of an enterprise user consists of identifying information about a user.

• HR attributes: Represent relatively static and well understood information, such
ble
as first and last name, title, and job function.
fe r a
• Roles: Define the user's purpose and responsibilities. an s
n - t r
•
devices such as laptops or access cards. a no
Resources: Define identifying assets, such as application accounts or physical
) h as ฺ
• Relationships: Define identifying connections, such as organizational
transactions (for example, approvals) l ฺ c om uide
m ai andepartners
The difference between users, identities, workers, n t G is as follows:
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
s a G lic
e r e
M ฺT
ble
fe r a
ans
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
_______________________________________________________
In Oracle Fusion Applications, identities and users correspond one to one, but not all
identities correspond to a user, and not all users are provisioned with an identity. Some
identities stored in HCM and Trading Community Model may not be provisioned to user
accounts and therefore are not synchronized with Oracle Identity Management (IDM).
For example, a contact for a prospective customer is an identity in Trading Community
Model but may not be provisioned with a user account in IDM. Some users stored in the
Lightweight Directory Access Protocol (LDAP) store may not be provisioned with
identities. For example, system user accounts used to run Web services to integrate
third party services with Oracle Fusion Applications are not associated with a person
record in HCM or Trading Community Model. Some identifying credentials such as
name, department, e-mail address, manager, and location are stored with user data in
the LDAP store.
User accounts for some identities that are not employees, such as partner contacts,
may be created in a later transaction using an identity that is already created. Supplier
contacts are created in the Supplier Model, not HCM. Once supplier users are setup,
Supplier Model can be used by internal users to maintain supplier user accounts or
supplier users can maintain their accounts in Supplier Portal.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Demonstration: User Role Assignment

Background
In this demonstration, you will explore the use of Oracle Identity Manager (OIM) to
review and assigning roles to an existing Fusion user.
ble
Steps
fe r a
1. Sign on as prc_impl. ans
n - t r
page. a no
2. Use the "Manage Jobs and Roles" task to open the Oracle Identity Manager
3. Select Users in the Search pane. ) has eฺ

Enter "may.gee" in the search field and clickฺthe
l c om id
searchuicon.
i G
4. Click the May Gee link in the Search g ma dpane.
Results e nt
5. A tab opens with details for a s
this @ Click
tuser. S tuthe Roles tab for May Gee.
b thi s
6. Note the following: gilฺa e
– The roles "ALL
e s ฺ
aUSERS"
t o us "Employee" are automatically provisioned when
and
the employee
l ( t er is created.
n se all been manually provisioned. For example, Buyer and
– The
G i other e
roles have
licManager.
s a
Procurement
Te re – Some roles inherit other roles. For example, Buyer.
M ฺ 7. Close the Oracle Identify Manger page and return to the Setup and
Maintenance work area.
Provisioning Users with Roles

Provision users with roles:

• Automatically, using role provisioning rules
• Manually, using delegated administration:
- Users such as line managers and human resource specialists can provision
roles manually to other users.
- Users can request roles for themselves
• For both automatic and manual role provisioning, you create a role mapping to
ble
identify when a user becomes eligible for a role.
fe r a
an s
n - t r
The following tasks provision users with roles:
a no
• Role Provisioning Rules: Manage HCM Role Provisioning
) has eฺRules task
• Role Provisioning: Manage Users task based
c mHCMuiRole
oon d Provisioning Rules
l ฺ
ai ent G
m
g tud
Security guidelines: t @
s is S
b a
• Avoid having users entitled
g i l ฺ a to
e th roles from being the same users who are
provision
e s aฺ to us
defining those roles.
l ( er memberships
• Maintain trole
n seRole Provisioning
through role provisioning rules.
- The
G iManage
l i e
HCM
c to users based on assignment Rules task lets you define rules for
e s a
provisioning roles attribute values or CRM party
r
Te criteria.
Mฺ - Supplier Portal provisioning rules apply to users provisioned through the
Supplier application.
• Provision to users only those job roles that are not inherited by data roles you
could provision instead.
The Provision Roles to Implementation Users task also provisions roles, but provisions
roles only as an initial task when getting started and preparing an implementation user
for enterprise structure setup.
Role Provisioning Events

New Identities
As with new hire, supplier, or partner contact creation, trigger user and role provisioning
events. In addition to user creation tasks, other tasks, such as Promote Worker Transfer
Worker, or user account creation for supplier or partner contacts, result in role
provisioning and recalculation based on role provisioning rules. Deactivating or
terminating an identity triggers revocation of some roles to end all role assignments, but
may provision new roles needed for activities such as pay stub review.
ble
fe r a
Automatically Provisioned Roles
t r a ns
A role is provisioned to a user automatically when at least one of the user's
n o n-assignments
satisfies the conditions specified in the relevant role-mapping definition. a
a s
m ) h deฺ
Deprovisioning Roles
i l ฺ co Gui
Automatically provisioned roles are deprovisioned g ma automatically
d e n t as soon as a user no
@ t u
st all ofisManually
longer satisfies the role-mapping conditions. Suser'sprovisioned roles are
deprovisioned automatically only a b a
when h the work relationships are
i l ฺ e t
s a ฺg us users retain manually provisioned roles until they
terminated; in all other circumstances,
are deprovisioned manually.
e r e e t o
G il (t licens
r e sa of Duties (SOD)
Segregation
e checks occur when roles are assigned to users, if Oracle Governance, Risk and
ฺ TThese
M Compliance Controls (GRCC) is provisioned in your deployment and the Governance,
Risk and Compliance feature choice is enabled for implementation projects of the
offering. The SOD checks are based on Oracle Application Access Controls Governor
(AACG) policies, and violations can be viewed, managed, remediated using Define
Automated Governance, Risk, and Performance Controls tasks.
Use Oracle Identity Management (OIM) to configure audits of provisioning events.
Security Reference Resources

Related Resources:
ble
fe r a
an s
Oracle Fusion Applications Procurement Security Reference Manual
n - t r
Oracle Fusion Applications Common Implementation Guide a no
Oracle Fusion Applications Security Guide
) has eฺ
Oracle Fusion Middleware User's Guide for Oracle ฺIdentity
l c om Manager
uid
i G
Oracle Fusion Middleware Authorization Policy g maManager e n t
Administrator's Guide (Oracle
Fusion Applications Edition)
s t @ Stud
Oracle Fusion Applications Workforce
l ฺ a ba Deployment
t h is Implementation Guide
g i e
Oracle Application Access
e s aฺ Controls
t o usGovernor Users Guide
l ( t er nse
i lice
Glisted
NOTE:
e aThe documents are available in the Technology Documentation Library,
syou can access
T e r
which from:
M ฺ http://www.oracle.com/technetwork/indexes/documentation/index.html
(http://www.oracle.com/technetwork/indexes/documentation/index.html)
Related Courses:
Fusion Applications: Security Fundamentals
Define Approval Management for Procurement

This section describes the tasks for approval management setup:

• Configuring approval policies
• Defining approval groups
ble
fe r a
ans
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Approval Management Foundation

Workflow
• An automated process in which tasks are passed from a user, a group of
users, or the application to another user or group for consideration or
action. The tasks are routed in a logical sequence to achieve an end result.
• A workflow human task is anything that requires attention or action from
users. Examples of tasks include approving a requisition or purchasing
documents.
ble
• For workflows, Oracle Fusion Applications uses the approval management
fe r a
extensions of the human workflow services from Oracle SOA Suite, as well
an s
as the Oracle BPM Worklist application.
n - t r
a no
Oracle SOA Suite: ) has eฺ
• Is a comprehensive software suite used to build,
l ฺ c om
deploy, id manage service-
uand
i G
oriented architectures (SOA).
g ma dent
• Provides a human workflow service s tu all interactions with users or
t@ thatShandles
groups in business processes a
ab e thi s
i l ฺ
Approval management:
s a ฺg us
e r e e t o
i l t
• Controls(workflows
n sfor business objects such as purchase orders.
e
G youlitoc define complex, multistage task routing rules
• Enables
s a
e• Integrates with the setup in Oracle Fusion Human Capital Management to derive
T e r
Mฺ approvers based on the supervisory hierarchy
Oracle BPM Worklist provides the user interface for:
• Users to access procurement setup tasks assigned to them and perform actions
based on their roles in the workflow
• Implementers to perform approval management setup and to define who should
act on which types of transactions under what conditions
Approval Management Overview

ble
fe r a
To set up approval management, use the following setup tasks from the Setup
ans
and Maintenance work area, which take you to Oracle BPM Worklist.
n - t r
• a no
Manage Approval Groups: Optionally create and maintain sets of users who
has eฺ
can act on workflow tasks, for example a chain of approvers for expense reports.
)
• Manage Task Configurations: Define approval
l ฺ c om
policies id determine how and
uthat
when tasks are routed. For example, youacan i specify
n t G
that expenses under a
certain amount should be automatically m
g approved de and not sent to any approver.
t @ t u
a b as his S
ฺ g ilฺ se t
To access these e a tasks
ssetup t o uyou need the BPM Worklist Administration Duty
r
(te enfor
role, which is predefined sethe Application Implementation Consultant job role.
i l
s a G lic
e r e
M ฺT
Approval Management Key Concepts

• Stages
• List Builders
• Rule Sets and Rules
Stages e
r a bl
• Stages organize approval flows in logical categories within a task. For example,
within a contract approval task, there can be one stage for contract header n s fe
approval and another for line level approval. n - tra
• Each task has at least one stage. a no
• The available stages and their flow (serial or parallel) ) astheirฺ specific order are
hand
predefined.
l ฺ c om uide
m ai ent G
@ g tud
List Builders t
as his S
a b
ฺ g ilฺ se t
e
A list builder is a mechanism
u
sa ttoo determine the task assignees, usually approvers, for
example based ( t
one r
going s
up ethe supervisory hierarchy. The following list builders are
G i l c e n
based on structures li in Oracle Fusion Human Capital Management (HCM), which must
saup appropriately.
e
berset
M ฺ Te • Supervisory: The hierarchy of employees, with defined job roles, and their
managers. For example, Joe Smith, administration assistant, reports to Alex
Park, manager, who reports to Anna Lee, senior manager.
• Job Level: The supervisory hierarchy with job levels in consideration. The
approval list is generated based on the starting participant specified in a rule and
continuing until an approver with a sufficient job level is found. For example, Joe
Smith, administration assistant (job level 1), reports to Alex Park, manager (job
level 2), who reports to who reports to Anna Lee, senior manager (job level 2),
who reports to Jane Brown, director (job level 3).
• Position: The hierarchy of job positions.
Other list builders include:
• Approval Group: A set of specific users.
• Resource: A specific user or application role.
Rule Sets and Rules

• A rule set is collection of related rules to map out the policies and routing within
a stage. For example, for a stage for contract approval, there can be one rule set
for legal approval and another for management approval.
• In each rule, you define a condition and specify the routing using a list builder.
Rule sets are predefined for each stage with these characteristics:
• Flow: Serial or parallel, and specific order, for stages with multiple rule sets.
• Business object level: Header or line.
• Voting regime: Consensus approval, majority approval, and so on, for rule sets
that route to a group of users.
ble
fe r a
ans
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Approval Management Example

ble
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
This figure shows an example of the flow of stages and rule sets for an expense
approval task. There are four predefined stages, each with one predefined rule set
except the pre-approval stage, which has two rule sets. The rule sets are:
• Requester FYI: The person submitting an expense report receives an FYI
notification.
• Exception Consensus: For extraordinary expenses over a certain amount, a set
of users must first approve. Approvals are based on an Approval Group list
builder and are routed in parallel to all members of a group.
• Header Hierarchy and Line Hierarchy: With serial routing based on a
Supervisory list builder, approvers approve the expense report header or lines.
What you can do in Oracle BPM Worklist is add and edit the rules within rule sets,
to define the conditions and routing. Also, you can choose not to use predefined rule
sets. For example, if the Exception Consensus is not necessary for your purposes, you
can disable it.
ble
fe r a
ans
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Task Configurations Event Driven Tab

Use the Event Driven tab in Oracle BPM Worklist to define expiration and
escalation policies, as well as other settings for the task.
• Expiration and Escalation Policy: Configure when tasks expire, are escalated,
or renewed. Expired tasks are automatically rejected. For example, you can
define the expiration policy so that if no one acts upon an expense report in two
weeks, then it expires and the requester needs to resubmit it.
ble
fe r a
an s
n - t r
a no
• Notification Settings: Send notifications based on task
s for example to
hastatus,
approvers when the task is assigned to them. If the m )task hasd ฺ with the FYI
erules
o i
onuthe rule conditions. You
a ilฺc based
response type, then notifications are also sent
t G
nor both. For example, you can
can use these notification settings, the
g mFYI rules,
d e
delete the notifications in the Notification
s tu section if you prefer to use the
t@ SSettings
a
ab based
FYI rules to send notifications s
hion certain criteria, not just task status.
i l ฺ e t
s a ฺg us
e r e e t o
G il (t licens
a
Te res
M ฺ
• Task Access: Control who can access the task and perform what actions. You
generally do not need to adjust the predefined settings.
ble
fe r a
ans
n - t r
a no
• Likewise, you generally do not need to adjust the other a
h s on this page
settings
unless you have a specific business reason.
o m )
i d eฺ
a ilฺc nt Gu
@ gm tude
b a st is S
g i l ฺa e th
e s aฺ to us
l ( t er nse
a Gi lice
Te res
M ฺ
Task Configurations Data Driven Tab

Use the Data Driven tab in Oracle BPM Worklist to define rules that determine
routing.
• Select the rule set within the appropriate stage
• You can add, edit, or delete rules
• Select the Ignore this participant check box if you do not need to use this
rule set
ble
Do not use the Add variable button. fe r a
an s
n - t r
a no
_______________________________________________________
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
s is S
Each rule consists of an if and thenacomponent.
l a b thone condition to determine when the rule is
ฺ at least
• The if component contains
g i e
applied.
e s aฺ to us
l (
• For multiple t erconditions
n se within a rule, you use the and or operators.
G i lic e
s a
ethen component defines what happens if the conditions are met. This component
e
The
r
M ฺT consists of:
• List builder and related attributes: Define how task assignees are derived. For
example, if you select a Job Level list builder you also define how many levels of
approvals are needed.
• Response type: Indicate if the assignees are required to address the task or if
they are just to receive an FYI notification.
• Automatic action setting: Allows you to set an automatic action on tasks, for
example to automatically approve or reject.
ble
fe r a
ans
n - t r
a no
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
For example,ilthis e n seapproval rule set is in the header stage. Within this rule
(terequisition
set, theafirst
s ic with a condition for an amount less than $50,000. The
Grule isldefined
r e uses the Supervisory list builder but based on the Auto Action Enabled and
routing
e
M ฺ TAuto Action fields, the requisition would be automatically approved.
ble
fe r a
an s
n - t r
a no
) has eฺ
l ฺ c om uid
The second rule in this rule set is for an amountaati or overt $50,000.
G The routing uses
the Supervisory list builder and has a fixedg m
name asdthe n
e top, or final, participant, so the
task essentially goes back to that approver t @ if
s is S no t u
one else approves.
b a
g i l ฺa e th
e s aฺ to us
At least one( t r in asrule
erule e set must evaluate to true. If multiple rules within a rule
i l e n
set can beG
s a true, then licthese rules must use the same list builder.
e r e
M ฺT
Demonstration: Manage Task Configurations

Background
Use the Oracle BPM Worklist work area accessed using the Manage Task
Configurations for Procurement task to review approval policies. In the Tasks to be
configured pane, review the predefined requisition approval task and review its details.
There are two approval tasks used in Oracle Fusion Procurement: ble
fe r a
• DocumentApproval: All procurement documents
ans
• ReqApproval: All requisitions n - t r
a no
Steps ) has eฺ
l
1. Use the "Manage Task Configurations for Procurement" ฺ c om utask
id to open the Oracle
i G
BPM Worklist work area. g ma dent
2. From the Task Configuration s t@click S
tab
u
thet "ReqApproval" task in the Tasks to be
configured pane.
a
ab e thi s
i l ฺ
3. You could make s a ฺg inuthe
changes
s Event Driven or Data Driven tabs.
e
er Driven
Click the tEvent t o
e tab if it is not already open.
l (
i policies n s
Note
a Gthe l i ce selected for Assignment and Routing Policy.
e r e4.sClick the Data Driven tab.
M ฺ T 5. Note that you can select list builder rulesets and conditions here.
Select "HeaderHierarchyRules" from the Select Ruleset list.
6. Note the following:
– The first rule allows for requisition self approval for amounts under $50,000.
– The second rule indicates that the supervisory hierarchy will be used for
amounts equal or greater than $50,000.
Expand both rules to view the IF/THEN logic.
7. You can make changes to the rules in edit mode by clicking the Edit icon. While
in edit mode the following actions are available:
– Use the Save icon in the toolbar. Your changes are retained even if you sign
out, but are not yet in effect.
– To discard all changes, saved or not, use the Reset icon.
– Click the Commit task icon to deploy your saved changes so that they are in
effect.
8. With the "HeaderHierarchyRules" ruleset still selected click the Edit icon.
9. Expand the "Requisition Self Approval under 50K" IF/THEN rule.

10. Change the amount for the IF clause to 30000.
Important!: Click the Reset icon.
11. Expand the "Requisition Self Approval under 50K" IF/THEN rule to verify that the
rule was reset to 50000.

12. Close the Oracle BPM Worklist work area and return to Setup and Maintenance.
If the task is not predefined as rule-based, then the behavior does not need to be
changed, and you get a message stating that you cannot edit the task. Technical
administrators can still edit the task in Oracle JDeveloper.
ble
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Manage Approval Groups

Use the Approval Groups tab in Oracle BPM Worklist to define sets of users that
can be selected for an Approval Group list builder. Tasks would be routed to the
specified group of users. For example:
• You have a special, ongoing project that involves a wide range of employees.
You can create an approval group of the managers involved, who must approve
expenses related to the project.
• You have certain categories of requisitions that require pre-approval from a
select group of people. You can create an approval group containing the users ble
who must all approve such requisitions in parallel before additional approvals can fe r a
be made. ans
n - t r
Approval Groups
a no
• Can be nested within other approval groups.
) has eฺ
• Are stored at the server level and not shared across
l ฺ c om domains.
uid For example, you
cannot use the same group for Financialsaand i Procurement.
n t G
g m e
Types of Approval Groups
s t @ Stud
• Static: You select specificbusers
a a tohinclude
is in the group and specify the flow of
tasks from one user l ฺ
gtoi another. t
eIf the group is used in a rule set that is
a ฺ u
sparalleltrouting,s
predefined with
e r e e o then the task is passed to all users in the group
G il (t licens
at the same time.
r e sa
M ฺ Te
• Dynamic: You use a custom Java class coded by technical administrators to

generate the approval group at run time.
Demonstration: Manage Approval Groups

Background
Use the Oracle BPM Worklist work area accessed using the Manage Approval Groups
for Procurement task to review approval groups. In the Groups pane review the
Category Servers group .
Steps ble
fe r a
1. Use the "Manage Approval Groups for Procurement" task to open the Oracle
an s
BPM Worklist work area.
n - t r
2. The Approval Groups tab of the Oracle BPM Worklist work area opens. a no
Click the Category Servers group.
) has eฺ
Note that for InFusion, all Purchasing documents
l ฺ c omwill selfuiapprove.
d Any
i t G
requisitions for the category "servers" willago to tiffany.irving
n will be routed to theby the
as indicated
Members diagram. All other requisitions g moverd$50,000
e
requester's supervisor. a s t@ Stu
l ฺ a b t h is
3. The Add icon is used
a ฺ gito adduasnewe group but note the drop down arrow to the
right of the icon.
r s
edropdown toarrow.
l ( e
Click the tAdd
ns e
4. UseG i c e
li in the Members region to add additional approvers to the
e s a the controls
Category Servers group.
Te r
ฺ Click the Add icon.
M 5. The Add to Group window opens.
6. Enter calvin.roth for the user to add.
Click the OK button.
7. Note that calvin.roth was added to the approval group.
8. Click the Reset button.
9. Close the Oracle BPM Worklist work area and return to Setup and Maintenance.
Approval Management Resources

Related Resources:
• Oracle Fusion Middleware Modeling and Implementation Guide for Oracle
Business Process Management
• Oracle Fusion Applications Common Implementation Guide
• Whitepaper: Setting up Document Approvals: Oracle Fusion Procurement
ble
fe r a
ans
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Common Applications Quiz

For this lesson, you should now be able to answer...
ble
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Common Applications: Question 1

A client business unit is serviced by one or more requisitioning business units.

1. True
2. False
ble
fe r a
ans
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT

The business unit that establishes a relationship with a supplier through the
creation of a supplier site is the:
1. Procurement business unit
2. Requisitioning business unit
3. Sold-to business unit
ble
4. Client business unit
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT

In the context of workflow, a task:

1. Always results in an approval of something.
2. Is anything that users or groups of users act on as part of a business
process flow.
3. Refers to a setup activity performed in the Setup and Maintenance work
area. ble
fe r a
4. All of these.
ans
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT

An approval group can be used to have multiple approvers act on the same task
in parallel.
1. True
2. False
ble
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
Common Applications Quiz Answers

A client business unit is serviced by one or more requisitioning business units.
2. False. A client business unit is serviced by one or more procurement business units.
The business unit that establishes a relationship with a supplier through the e
creation of a supplier site is the: r a bl
s fe
- t r an
1. Procurement business unit
no n
a
) has eฺ
l ฺ c om uid
In the context of workflow, a task:
m ai ent G
@ g tud
t
asof users S
2. Is anything that users or groupsฺ a b t h i s act on as part of a business process
g i l e
flow.
e s aฺ to us
A task can resultteinrsomething
e getting rejected, or an employee appraisal completed, so
l ( n s
a
scopesof
Gi accurate.
1 is not entirely
workflow.li
ce Answer 3 is not the correct definition of a task within the
e r e
T
Mฺ
An approval group can be used to have multiple approvers act on the same task
in parallel.
1. True. Even though the setup UI lays out the approval group in a serial manner, the
approval group can be used for parallel approvals.
Define Common Applications Configuration Highlights

In this lesson, you should have learned how to:

• Learned about the common applications configurations
• List the key concepts of common configurations for Procurement
• Describe the major common configuration tasks for Procurement
ble
fe r a
an s
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT
ble
fe r a
ans
n - t r
n o
a
) has eฺ
l ฺ c om uid
m ai ent G
@ g tud
t
as his S
a b
ฺ g ilฺ se t
r e sa to u
i l (te ense
sa
G lic
e r e
M ฺT

Lesson 3 - Define Common Applications Configuration Overview

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lesson 3 - Define Common Applications Configuration Overview

Uploaded by

Copyright:

Available Formats

Lesson 3: Define Common Applications Configuration Overview

Lesson 3: Define Common Applications Configuration

After completing this lesson, you should be able to:

Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 77

Common Applications Configuration Overview

78 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 79

Common Applications Configuration Task Groups

Before you implement Oracle Fusion Procurement components, complete the

80 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

• Define Security for Procurement: Enable users to perform functions related to

• Define Approval Management for Procurement: Define approval routing

Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 81

Demonstration: Common Applications Configuration

This demonstration provides a high-level presentation of the Define Common

82 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

9. Return to the Setup and Maintenance work area.

Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 83

The InFusion Corporation Story

The Oracle Fusion Procurement Implementation course is based on a fictional yet

84 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

InFusion Global Enterprise Model

This diagram illustrates the InFusion Corporation enterprise.

Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 85

This diagram was created to illustrate the InFusion Corporation Enterprise

86 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Define Enterprise Structures Overview

Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 87

The Fusion Enterprise

An enterprise consists of legal entities under common control and management.

In this section of the lesson we will discuss:

88 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 89

Define Reference Data Sharing

90 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Reference Data Overview

Reference data sharing facilitates sharing of configuration data such as

As illustrated in the preceding graphic, depending on the requirement (specific or

Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 91

Reference Data Partitions

92 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 93

94 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Sharing Supplier Site Reference Data

• Supplier site represents the relationship between a procurement business

Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 95

Demonstration: Reference Data

96 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Define Enterprises for Procurement

• Create and manage the locations relevant to your enterprise.

Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 97

Setup and Maintenance > All Tasks > Manage Locations

98 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 99

Demonstration: Manage Locations

Define Legal Entities for Procurement

Legal Entities Overview

The Role of your Legal Entity

The contracting party on any transaction is always the legal entity.

Individual legal entities:

• Make purchases and incur expenses

Legal Entity Considerations

Legal Entity in Transactions