Standalone Fusion Sourcing Implementation
Oracle Fusion Sourcing Release 11
ORACLE WHITE PAPER
|
MAY 2016
Disclaimer
The following is intended to outline our general product direction. It is intended for information
purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any
material, code, or functionality, and should not be relied upon in maki
making
ng purchasing decisions. The
development, release, and timing of any features or functionality described for Oracle’s products
remains at the sole discretion of Oracle.
STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCI
SOURCING RELEASE 11
Table of Contents
Disclaimer
1
Executive Overview
1
Introduction
1
Implementation Using Rapid Implementation Task List
2
Prepare for Implementation
2
Set Up the Enterprise
8
Provision Users
16
Set Up Purchasing Categories
21
Complete Procurement Setup
31
Setup for Sourcing Activities
33
Implementation Using Full Implementation Task List
35
Prepare for Implementation
35
Set Up the Enterprise
45
Provision Users
54
Set Up Purchasing Categories
61
Complete Procurement Setup
71
Setup for Sourcing Activities
79
Conclusion
STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCI
SOURCING RELEASE 11
81
Executive Overview
Oracle Fusion Sourcing is the next generation application for smarter negotiation and rapid and
immediate savings realization. It is an integral part of the Oracle Fusion Procurement Applications and
is generally implemented with other Fusion Procurement p
products
roducts like Oracle Fusion Purchasing and
Oracle Fusion Supplier Portal. However, organizations may not be in a position to undertake adoption
of the entire suite by completely replacing their existing application portfolio. But organizations can
successfully
lly pursue coexistence strategies by selective adoption of Fusion Applications that
complement their existing solutions. Oracle Fusion Sourcing can be easily implemented as standalone
and makes an excellent candidate for such coexistence strategies. Compan
Companies
ies can benefit from next
generation functionality and superior user experience by choosing to implement Oracle Fusion
Sourcing.
Introduction
This whitepaper describes a simplified approach of how to implement Oracle Fusion Sourcing as a
standalone application
ation using minimum required setup steps. It assumes a fresh installation of Oracle
Ora
Fusion Sourcing Release 11.
One of the two implementation task lists can be used to implement Oracle Fusion Sourcing. The full
implementation task list includes a comprehen
comprehensive list of setup steps while the rapid implementation
task list only includes tasks that are mandatory or commonly used by most companies. If your
company has simple setup requirements and wants to get ready to run sourcing events quickly
quickly,, you
can choose the rapid implementation task list that streamlines the setup by combining setup steps and
providing defaults for setup data.
For both rapid and full implementation task lists, iimplementation
mplementation steps are broadly organized into the
following activities.
» Prepare for implementation
» Set up the enterprise
» Provision users
» Set up purchasing categories
» Complete procurement setup
» Setup for sourcing activities
1 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCI
SOURCING RELEASE 11
Implementation Using Rapid Implementation Task List
Prepare for Implementation
To get started with Oracle Fusion Sourcing implementation, you need access to Oracle Identity Manager (OIM),
Oracle Authorization Policy Manager (APM), and Oracle Fusion Applications URLs
URLs.
A fresh installation of Fusion Applications comes with an administrator us
user
er who can prepare the implementation
and provision new implementation users. Log in as the administrator user and perform the following steps.
Figure 1. Process flow to prepare for implementation
From Navigator, select Setup and Maintenance. On the Offerings page, select Procurement to download information
documents like the Offering Content Guide in various formats.
Offerings are application solution sets representing one or more business processe
processes
s and activities that you typically
provision and implement as a unit. However, an offering must be provisioned if you want to enable it for
implementation. For example, if Procurement offering is provisioned for implementation, it is indicated as
Provisioned in the Administration section.
2 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCI
SOURCING RELEASE 11
Figure 2. Select Procurement offering
Configure Offerings
In the Administration section, click Configure to configure offerings. All Procurement offerings and opt
options
ions are
displayed on the Configure: Procurement page and are available for configuration.
To implement standalone Fusion Sourcing with minimum setup necessary to run a negotiation event, Procurement
must be provisioned, and Procurement and Sourcing must b
be enabled for implementation. Purchasing is a separate
option under Procurement and it is not required to enable it for standalone Fusion Sourcing implementation.
Figure 3. Configure offerings
3 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCI
SOURCING RELEASE 11
To select features for Procurement, click the Edit icon in the Features column. This whitepaper assumes a basic
minimum implementation without the necessity to process requisitions or define master items. Therefore, the
following checkboxes which are checked by default are unchecked and this configuration is saved.
» Requisitions
» Master Items
Figure 4. Select features
Create Implementation Project
An implementation project enables efficient planning, configuration, implementation, deployment, ongoing
maintenance and reporting around various implementation tasks. Once an implementation project is created, it will
auto-generate
generate sequential task lists, including prerequisites, and addre
address
ss dependencies to give full visibility to end-toend
end setup requirements for your selected offerings.
Back on the Setup and Maintenance page, click
lick the Implementation Projects button. Create an implementation
project for standalone sourcing. Enter project name and description, and click Next to select offerings to implement.
Figure 5.. Enter basic information for implementation project
4 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCI
SOURCING RELEASE 11
Check Procurement and Sourcing checkboxes in the Include column. Save and open the project.
Figure 6.. Select offerings to implement for implementation project
For rapid implementation, you need to select and add the ‘Define Procurement Configuration for Rapid
Implementation’
plementation’ task list and delete the original ‘Procurement’ task list.
Figure 7.. Select and add rapid implementation task list
In the Procurement rapid implementation task list, you can delete th
the
e following task lists that are not needed for
standalone Sourcing implementation:
» Define Enterprise Structure Configuration for Procurement Rapid Implementation Including Purchasing
5 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCI
SOURCING RELEASE 11
» Define Purchasing Configuration for Rapid Implementation
ice Configuration for Rapid Implementation
» Define Self Service
» Define Supplier Qualification Configuration for Rapid Implementation
» Define Procurement Contract Terms Configuration
» Define Invoicing and Payments Configuration for Rapid Implementation
The remaining task lists are
re the ones that will be used for standalone Sourcing implementation.
Figure 8.. Rapid implementation task lists for standalone Sourcing implementation
Note: The rapid implementation task list for Procurement
rocurement and Sourcing contains other common steps that will be
useful depending upon the coverage of your implementation. This whitepaper assumes a simpler installation, and
only describes minimum necessary steps.
Run User and Roles Synchronization Process
During implementation, any existing information about users, roles, and roles provisioned to users must be copied
from the LDAP (Lightweight Directory Access Protocol) directory to the Oracle Fusion Applications tables. Once the
Oracle Fusion Applications
cations tables are initialized with this information, the data is maintained automatically by
concurrent processing. Run the 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 be run as needed to keep the product tables
synchronized with subsequent updates to LDAP.
Task:: Run User and Roles Synchronization Process
6 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCI
SOURCING RELEASE 11
Figure 9.. Run User and Roles Synchronization Process task
Create Implementation User
To start an Oracle Fusion Applications implementation, log in as the administration user and set up one or more
initial users.
Task: Create Implementation Users
Figure 10. Create Implementation Users task
Create Implementation Users task opens Oracle Identity Manager. You need an administrator user who has the IT
Security Manager job role in order to create an implementation user
user. This administrator user can create an
implementation user with Application Implementation Manager job role or the Application Implementation Consultant
job role by using the ‘Provision Roles to Implementation Use
Users’
rs’ task. The Application Implementation Consultant job
role inherits permissions from all product-specific
specific application administrators and has the necessary ‘View All’ access
to all secured objects. Implementation users
sers who have this job role will typicall
typically have access to set up basic
enterprise structure needed to implement offerings.
If you plan to use the same implementation user to set up the basic enterprise structure as well, you do not need to
create any additional users. Alternatively, you may want to distribute the responsibilities for setting up the basic
enterprise structure to multiple people and create one or more implementation users.
For this whitepaper, the same implementation user will perform the IT Security Manager and the Application
Implementation
ementation Consultant roles. This is the implementation user who will execute implementation tasks.
Oracle Identity Manager – Delegated Administration > Action: Create User
7 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCI
SOURCING RELEASE 11
Figure 11. Create implementation user
Assign the following roles to the implementation user:
» Application Implementation Consultant
» IT Security Manager
Figure 12. Assign roles to implementation user
Set Up the Enterprise
An enterprise consists of legal entities under common control and management. Oracle Fusion Applications are
implemented within the context of an enterprise that has already been created in the application. An enterprise
organization captures the name of the
he deploying enterprise and the location of the headquarters.
The following enterprise setup steps can now be performed by the implementation user.
8 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCI
SOURCING RELEASE 11
Figure 13. Process flow to set up the enterprise
Log in as the implementation user created in the previous steps. From Navigator, select Setup and Maintenance,
then search and access the implementation project.
Access the task list and locate the next set of tasks.
Create Location
A location identifies
es physical addresses of a workforce structure, such as a department or a job. Create locations
relevant to your enterprise. These are different locations where people work.
Task: Manage Locations
9 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCI
SOURCING RELEASE 11
Figure 14. Manage Locations task
Create a new location. If you have not defined a location set, the common set can be used.
10 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 15. Create location
Create Legal Address
Create the address a legal
al entity uses to register with a legal authority. Legal entities can use different addresses for
different authorities and hence, may have more than one registered address. Legal address is required for creating
a legal entity.
Task: Manage Legal Addresses
11 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 16. Manage Legal Addresses task
Create a new legal address.
Figure 17. Create legal address
12 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Create Legal Entity
Create a new legal entity. Define a legal entity for each registered company or other entity recognized in law for
which you want to conduct business activities.
Task: Manage Legal Entity
Figure 18. Manage Legal Entity task
Legal entity is required when creating employees (users) in order to identify their legal employer. Enter the legal
address created in the earlier step.
Figure 19. Create legal entity
13 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Manage Enterprise HCM Information
The enterprise has Human Capital Management (HCM) information such as enterprise name and employment
model. You can update them by editing the enterprise setup.
Each legal entity is a legal employer and mustt have a defined employment model in order to create users. During
user creation, the employment model of the enterprise is used if the employment model of the legal entity is not
defined. Therefore, if you use the same employment model for all your legal entities, you can just define the
employment model once on the enterprise level.
The two-tier
tier employment model comprises two types of entities, work relationships and assignments. In the threethree
tier employment model, employment terms are considered as the tthird
hird tier to express employment possibilities.
When you update the employment model, you can select from three two
two-tier options:
» Single Assignment
» Single Assignment with Contract
» Multiple Assignments
For more information on selecting employment model for yyour enterprise, refer to the Workforce Structures:
Organization chapter of the Implementing Talent Management Base documentation.
Task: Manage Enterprise HCM Information
Figure 20. Manage Enterprise HCM Information task
14 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Update the seeded name ‘Setup Enterprise’ to the actual enterprise name and select the employment model. The
employment model is required for selecting a leg
legal employer when creating users.
Figure 21. Manage enterprise HCM information
Configure Basic Enterprise Structure for Procurement
A business unit is a unit of an enterprise that performs one or many business functions which can be rolled up in a
management hierarchy. It processes transactions on behalf of the legal entities. The business unit is used as a
securing mechanism for transactions and also to implement data security. For standalone Fus
Fusion Sourcing
implementation, a business unit must be created that will perform the procurement business function. Employees
will need to be assigned job roles and data access to this procurement business unit in order to perform
procurement and sourcing functions.
In the rapid implementation list, there is a setup process that you can run to set up a business unit and define the
basic enterprise structure. The process will set up UOMs, an item organization, and a procurement business unit.
Therefore, you willll not need to go to different tasks to set them up.
Task:: Configure Basic Enterprise Structure for Procurement
15 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 22.. Configure Basic Enterprise Structure for Procurement task
Enter the name and select the currency of the procurement business unit, then submit the process.
Figure 23.. Configure basic enterprise structure for procurement
Provision Users
The enterprise and business units need to have employees as users. Creating and provisioning users with the
necessary roles to carry out procurement and sourcing related functions will enable them to execute transactions for
the business unit.
16 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 24. Process flow to provision users
Create User for Procurement
Create procurement users who will run the negotiations and perform sourcing related tasks.
Task: Manage Users
Figure 25. Manage Users task
Enter detailed information for the user.
17 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 26. Create user
Assign Job Roles
After the procurement users are created, you need to assign job roles to them.
Task: Manage Job Roles
18 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 27. Manage Job Roles task
Manage Job Roles task opens Oracle Identity Manager. You can assign job roles to procurement u
users.
Oracle Identity Manager – Delegated Administration > Action: Advanced Search - Users
Search for the procurement users and assign the following roles to them:
» Employee
» Category Manager
» Supplier Administrator
Figure 28. Assign job roles
19 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Create Procurement Agent
Configure procurement agent access to information, such as purchasing documents, suppliers, approved supplier
list entries, and business intelligence spend data. For users to have access to relevant information according to their
job roles, they need to be defined as procurement agents for the business units. This gives them access to various
actions and also defines their access level to other agents’ documents.
Task: Manage Procurement Agents
Figure 29. Manage Procurement Agents task
When you only need to implement the Sourcing functionality, create procurement agents who can manage
negotiations and manage suppliers.
20 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 30. Create procurement agent
Set Up Purchasing Categories
Purchasing categories represent the classification of products and servi
services to be used in procurement. To define
purchasing categories, you need to set up the category flexfield structure. For more information on flexfields, refer to
the Define Applications Core Configuration chapter of the Implementing Procurement documentation.
21 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 31.. Process flow to set up purchasing categories
Create Value Sets for Item Categories
Create a value set for use in item category flexfield.
Task: Manage Product and Child Value Sets
Figure 32.. Manage Product and Child Value Sets task
22 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Create a value set in Item Catalogs module.
Figure 33. Create value set
Once the value set is created, click Manage Values to create values for the category value set.
Figure 34. Create values
23 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Define Key Flexfield for Item Categories
Create key flexfield for item categories. Flexfield structures can be created as part of the Item Catalogs module.
Task: Manage Key Flexfield for Catalogs
Figure 35. Manage Key Flexfield for Catalogs task
There are three steps to create the key flexfield. Each step begins on the Manage Key Flexfield for Catalogs page.
The first step is to create a flexfield structure. Find the Item Categories flexfie
flexfield
ld and click Manage Structures.
Figure 36. Manage key flexfield for catalogs
24 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Create a key flexfield structure.
Figure 37. Create key flexfield structure
Add a segment to the key flexfield structure and associate the value set created earlier to the segment.
Figure 38. Create key flexfield segment
This example shows a single segment
ment item categories structure. You can define more than one segment depending
upon the organization and industry needs to create a desired category structure.
The second step is to create a flexfield structure instance. Find the Item Categories flexfield and click Manage
Structures Instances, then click Create on segment instances.
25 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 39. Create key flexfield structure instance
The third step is to deploy the flexfield. Find the Item Categorie
Categories flexfield and click Deploy Flexfield.
Figure 40. Deploy flexfield
Create Category Catalog and Add Categories
Create a category catalog for the purchasing function in order to create categories to be used in negotiations.
26 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Task: Manage Catalogs
Figure 41. Manage Catalogs task
Create a basic catalog for purchasing categories. Enter Catalog Name and Description. Select Catalog Structure
value to be the flexfield structure instance that was defined in an earlier step. Set Catalog Content to ‘Categories
only’ since items are not defined in this implementation.
27 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 42. Create catalog
To add categories to catalog, find the catalog that was created and click Edit. Switch to Category Hierarchy and then
click Create Category. This is required for the Category LOV.
Create a category and add it as the default category. This is required when assigning the default catalog for
purchasing in the next step.
28 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 43. Create default category
Assign Default Catalog
Specify the default catalog for purchasing functional area.
Task: Manage Default Catalogs
29 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 44. Manage Default Catalogs task
Assign the catalog created before to the Purchasing functional area. This is required for selecting purchasing
categories when defining negotiation
tion lines during negotiation creation.
30 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 45. Assign default catalog to Purchasing
Complete Procurement Setup
Complete the necessary setup for initializing procurement related functionality.
Figure 46.. Process flow to complete procurement setup
Manage Supplier User Roles
Specify roles that can be provisioned to supplier users.
Task: Manage Supplier User Roles
31 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 47. Manage Supplier User Roles task
For standalone Fusion Sourcing, the following supplier roles are recommended:
» Supplier Bidder – A sales representative from a potential supplier responsible for responding to requests for
quote, requests for proposal, requests for information and reverse auctions.
» Supplier Self Service Administrator - Manages the profile information for the supplier company. Primary tasks
include updating supplier contact information and admini
administering
stering user accounts to grant employees access to the
buying organization's application.
» Supplier Self Service Clerk - Updates the profile information for the supplier company. Primary tasks include
updating supplier contact information and requesting use
userr accounts to grant employees access to the buying
organization's application.
32 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 48. Manage supplier user roles
Set Sourcing Offering to Implemented
On Configure Offerings page, set the implementation
entation status of the Sourcing offering to ‘Implemented’. This is
required for creating supplier user accounts in supplier portal.
Figure 49. Set Sourcing offering to implemented
Setup for Sourcing Activities
Once the procurement setup is completed, additional setup for sourcing activities can be performed before category
managers begin to conduct negotiations. The following setup steps are not required and they can be completed at a
later time. You can refer to the Implementing Procurement documentation for details.
Define Sourcing Configuration
The implementation user can optionally perform the sourcing relate
related
d tasks based on the functionality required by
your organization.
33 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
In the Define Sourcing Configuration for Rapid Implementation task list, go to the following task
task.
» Manage Negotiation Styles
Define Negotiation Tools
The implementation user can define public templates that are accessible by all category managers. The public
negotiation templates can be used to standardize company policies or best prac
practices.
In the Define Sourcing Configuration for Rapid Implementation task list, go to the following task.
» Manage Negotiation Templates
In addition, category managers can define public and private templates themselves to streamline sourcing document
creation. The setup links are available under Tasks in the Negotiations work area.
Register Suppliers
Supplier administrators can register suppliers and create supplier contacts. They can also create user accounts for
supplier contacts in order to access supplier portal and respond to negotiations. Besides, suppliers can use the self
service registration to register themselves directly. For more informatio
information
n on configuring the registration, you can
refer to the Configure Supplier Registration chapter in the Implementing Procurement documentation.
Log in as a supplier administrator.
or. From Navigator, click Suppliers under Procurement, and then click Register
Supplier under Tasks in the Suppliers work area. Enter the registration and company details for the supplier, and
then create contacts and user accounts for the contacts. The su
supplier
pplier roles that are set up before can be selected
for the supplier contacts.
Besides registering suppliers in the Suppliers work area, new supplier records can be imported from external
systems as well. You can refer to the Supplier Import chapter in the Implementing Procurement documentation for
details.
This concludes the implementation using the rapid implementation task list. If you have other setup requirements,
you can go to the corresponding tasks in the task list. Otherwise, the setup is complete and category managers can
begin to conduct negotiations.
34 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Implementation Using Full Implementation Task List
Prepare for Implementation
To get started with Oracle Fusion Sourcing implementation, you need access to Oracle Identity Manager (OIM),
Oracle Authorization Policy Manager (APM), and Or
Oracle Fusion Applications URLs.
A fresh installation of Fusion Applications comes with an administrator user who can prepare tthe
he implementation
and provision new implementation users. Log in as the administrator user and perform the following steps.
Figure 50.. Process flow to prepare for implementation
From Navigator, select
ect Setup and Maintenance. On the Offerings page, select Procurement to download information
documents like the Offering Content Guide in various formats.
Offerings are application solution sets representing one or more business processes and activities th
that
at you typically
provision and implement as a unit. However, an offering must be provisioned if you want to enable it for
implementation. For example, if Procurement offering is provisioned for implementation, it is indicated as
Provisioned in the Administration section.
35 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 51. Select Procurement offering
Configure Offerings
In the Administration section, click Configure to configure offerings. All Procurement offerings and options are
displayed on the Configure: Procurement page and are available for configuration.
To implement standalone Fusion Sourcing with minimum setup necessary to run a negotiation event, Procurement
must be provisioned, and Procurement and Sourcing must be enabled for impl
implementation. Purchasing is a separate
option under Procurement and it is not required to enable it for standalone Fusion Sourcing implementation.
Figure 52. Configure offerings
36 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
To select features for Procurement, click
lick the Edit icon in the Feature
Features column. This whitepaper assumes a basic
minimum implementation without the necessity to process requisitions or define master items. Therefore, the
following checkboxes which are checked by default are un
unchecked and this configuration is saved.
» Requisitions
» Master Items
Figure 53. Select features
Create Implementation Project
An implementation project enables efficient planning, configuration, implementation, deployment, ongoing
maintenance and reporting around various implementation tasks. Once an implementation project is created, it will
auto-generate
generate sequential task lists, including prerequisites, and address dependencies to g
give
ive full visibility to end-toend
end setup requirements for your selected offerings.
Back on the Setup and Maintenance page, click
lick the Implementation Projects button.. Create an implementation
project for standalone sourcing. Enter project name and description
description, and click
lick Next to select offerings to implement.
37 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 54.. Enter basic information for implementation project
Check Procurement and Sourcing checkboxes in the Include column. Save and open the project.
Figure 55.. Select offerings to implement for implementation project
You can see and access the task list to implement Procurement. The task list is generated based on the tasks that
are relevant to the offerings and options that you selected, that is, Procurement and Sourcing.
Note: The automatically generated task list for Procurement and Sourcing contains additional steps that will be
useful depending upon the coverage of your implement
implementation.
ation. This whitepaper assumes a simpler installation, and
only describes minimum necessary steps.
Run User and Roles Synchronization Process
During implementation, any existing information about users, roles, and roles provisioned to users must be copied
from the LDAP (Lightweight Directory Access Protocol) directory to the Oracle Fusion Applications tables. Once the
Oracle Fusion Applications tables are initialized with this information, the data is maintained automatically by
concurrent processing. Run the 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 be run as needed to keep the product tables
synchronized with subsequent
nt updates to LDAP.
38 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Task: Run User and Roles Synchronization Process
Figure 56. Run User and Roles Synchronization Process task
Create Implementation User
To start an Oracle Fusion Applications implementation,
lementation, log in as the administration user and set up one or more
initial users.
Task: Create Implementation Users
39 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 57. Create Implementation Users task
Create Implementation Users task opens Oracle Identity Manager. You need an administrator user who has the IT
Security Manager job role in order to create
te an implementation user
user. This administrator user can create an
implementation user with Application Implementation
plementation Manager job role or the Application Implementation Consultant
job role by using the ‘Provision Roles to Implementation Users’ task. The Application Implementation Consultant job
role inherits permissions from all product-specific
specific application a
administrators
dministrators and has the necessary ‘View All’ access
to all secured objects. Implementation users
sers who have this job role will typically have access to set up basic
enterprise structure needed to implement offerings.
If you plan to use the same implementation user to set up the basic enterprise structure as well, you do not need to
create any additional users. Alternatively, you may want to distribute the responsibilities for setting up the basic
enterprise structure to multiple people and create one or mor
more implementation users.
For this whitepaper, the same user will perform the IT Security Manager and the Application Implementation
Consultant roles. This is the implementation user who will execute implementation tasks.
Oracle Identity Manager – Delegated Administration > Action: Create User
40 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 58. Create implementation user
Assign the following roles
oles to the implementation user:
» Application Implementation Consultant
» IT Security Manager
Figure 59. Assign roles to implementation user
Create Data Role for Implementation User
Create a data role based on the Human Capital Management Application Administrator job role to view all security
securit
profiles so the implementation user will be able to perform all required Human Capital Management (HCM) setup
steps.. The HCM user who has this job role will be able to create procurement users in a later step.. For details on
HCM data roles, refer to the Creating HCM Data Roles chapter of the Oracle Human Capital Management Cloud
Securing Oracle HCM Cloud documentation.
Task:: Create Data Role for Implementation Users
41 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 60.. Create Data Role for Implementation Users task
On the Manage Data Roles and Security Profiles page, search for the predefined Human Capital Management
Application Administration Role.
Figure 61. Manage data roles and security profiles
42 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Edit and assign data role security criteria for this role. Create a view all HCM data role for each security criteria.
Select the following values for each security
curity profile from the dropdown choice lists:
» View All Organizations
» View All Positions
» View All Legislative Data Groups
» View All Workers
» View All Document Types
» View All Payrolls
» View All Payroll Flows
43 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 62. Assign data role security criteria
44 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Provision ‘View All’ HCM Data Role
Log into Oracle Identity
ty Manager. Provision ‘View All’ HCM data role by assigning the Human Capital Management
Application Administrator role to the created implementation user.
Set Up the Enterprise
An enterprise consists of legal entities under common control and management. Oracle Fusion Applications are
implemented within the context of an enterprise that has already been created in the application. An enterprise
organization captures the name of the deploying enterprise and the location of the headquarters.
The following enterprise setup steps can now be performed by the implementation user.
Figure 63. Process flow to set up the enterprise
Log in as the implementation user created in the previous steps. From Navigator, select Setup and Maintenance,
Maintenanc
then search and access the implementation project.
Access the task list and locate the next set of tasks.
Create Location
A location identifies physical addresses of a workforce structure, such as a department or a job. Create locations
relevant to your
our enterprise. These are different locations where people work.
Task: Manage Locations
45 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 64. Manage Locations task
Create a new location. If you have not defined a location set, the common se
set can be used.
46 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 65. Create location
Create Legal Address
Create the address a legal entity uses to register with a legal authority. Legal entities can use different addresses for
different authorities and hence, may have more than one registered address. Legal address is required for creating
a legal entity.
Task: Manage Legal Addresses
47 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 66. Manage Legal Addresses task
Create a new legal address.
Figure 67. Create legal address
48 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Create Legal Entity
Create a new legal entity. Define a legal entity for each registered company or other entity recognized in law for
which you want to conduct business activities.
Task: Manage Legal Entity
Figure 68. Manage Legal Entity task
Legal entity is required when creating employees (users) in order to identify their leg
legal
al employer. Enter the legal
address created in the earlier step.
Figure 69. Create legal entity
49 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Manage Enterprise HCM Information
The enterprise has HCM information such as enterprise name and emp
employment model. You can update them by
editing the enterprise setup.
Each legal entity is a legal employer and must have a defined employment model in order to create users. During
user creation, the employment model of the enterprise is used if the employ
employment
ment model of the legal entity is not
defined. Therefore, if you use the same employment model for all your legal entities, you can just define the
employment model once on the enterprise level
level.
The two-tier
tier employment model comprises two types of entities, work relationships and assignments. In the threethree
tier employment model, employment terms are considered as the third tier to express employment possibilities.
When you update the employment model, you can select from three two
two-tier options:
» Single Assignment
» Single Contract – Single Assignment
» Multiple Assignment
For more information on selecting employment model for your enterprise, refer to the Workforce Structures:
Organization chapter of the Implementing Talent Management Base documentation.
Task: Manage Enterprise HCM Information
Figure 70. Manage Enterprise HCM Information task
50 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Update the seeded name ‘Setup Enterprise’ to the actual enterprise name and select the employment model. The
employment model is required for selecting a legal employer when creating users.
Figure 71. Manage enterprise HCM information
Create Business Unit
A business unit is a unit of an enterprise that performs one or many business functions which can be rolled up in a
management hierarchy. It processes transactions on behalf of the legal entities. The business unit is used a
as
sa
securing mechanism for transactions and also to implement data security. For standalone Fusion Sourcing
implementation, a business unit must be created that will perform the procurement business function. Employees
will need to be assigned job roles and
d data access to this procurement business unit in order to perform
procurement and sourcing functions.
Task: Manage Business Unit
51 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 72. Manage Business Unit task
Create Business Unit. Select the location created in the earlier step and a default reference data set. If you have not
defined a reference data set, the common set can be used.
Figure 73. Create business unit
Assign Procurement
ent Business Function to Business Unit
After creating a business unit, you need to assign the procurement business function to it.
Task: Assign Business Unit Business Function
52 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 74. Assign Business
ness Unit Business Function task
Select the procurement
rocurement business function to enable it for the business unit.
Figure 75.. Assign procurement business function to business unit
53 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Provision Users
The enterprise and business units need to have
ave employees as users. Creating and provisioning users with the
necessary roles to carry out procurement and sourcing related functions will enable them to execute transactions for
the business unit.
Figure 76. Process flow to provision users
Create Role Mapping
A user's access to data and functions depends on the user's roles. Users have one or more roles that enable them
to perform the tasks required by theirr jobs or positions. Roles must be provisioned to users; otherwise, users have
no access to data or functions. For this, first a role mapping will be created between the role and a set of conditions
based on assignment attributes such as department, job
job, and
nd person type. This role mapping defines whether a role
can be provisioned to a user, and by which method – manual or automatic.
To enable a role to be provisioned to users either automatically or manually, the conditions set in the role mapping
must be satisfied
atisfied for that role. To define users for sourcing, you will create role mappings for an HCM super user
who can hire employees, and procurement users who will perform procurement and sourcing related functions.
Task: Manage HCM Role Provisioning Rules
54 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 77.. Manage HCM Role Provisioning Rules task
Create a role mapping with the following roles and provision methods:
(Autoprovision)
» Human Capital Management Application Administrator (Autop
» Employee (Requestable, Autoprovision)
equestable)
» Category Manager (Requestable, Self-requestable)
Self-requestable)
» Sourcing Project Collaborator (Requestable, Self
equestable)
» Supplier Administrator (Requestable, Self-requestable)
55 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 78. Create role mapping
Human Capital Management Application Administra
Administrator and Employee roles are autoprovisioned
provisioned based on applicable
set of conditions in the work assignment. Users such as human resource (HR) specialists and line managers can
provision roles manually to other users.
ers. If a role is set as ‘Self
‘Self-requestable’,, users can request provisioning of this
role for themselves.
Create First HCM User
Create the first HCM user who has the Human Capital Management Application Administrator role
role. The HCM
M user
can later define employees as users for procurement.
Task: Manage Users
56 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 79. Manage Users task
Create user for the employee who is the HCM App
Application Administrator and autoprovision roles to the user. Verify
that the user is granted Employee and Human Capital Management Application Administrator roles.
57 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 80. Create user
Create User for Procurement
Log into the application as the HCM Applications Administrator. Use the navigator to access Manage Users page.
Navigator > Manager Resources > Manage Users: Create User
58 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 81. Go to Manage Users page
Create users and provision the following roles for these procurement users:
» Employee
» Category Manager
» Supplier Administrator
After procurement users are created, log in as the implementation user and continue the setup process. From
Navigator, select Setup and Maintenance,, then search and access the implementation project. Access the task list
and locate the next set of tasks.
Create Procurement Agent
Configure procurement agent access to information, such as purchasing documents, suppliers, approved supplier
list entries, and business intelligence spend data. For users to have access to relevant information according to their
job roles, they need to be defined as procurement agents for the business units. This gives them access to various
actions and also defines their access level to other agents’ documents.
Task: Manage Procurement Agents
59 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 82. Manage Procurement Agents task
When you only need to implement the Sourcing functionality, create procurement agents who can manage
negotiations and manage suppliers.
60 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 83. Create procurement agent
Set Up Purchasing Categories
Purchasing categories represent the classification of products and services to be used in procurement. To define
purchasing categories, you need to set up the category flexfield structure. For more information on flexfields, refer to
the Define Applications Core Configuration chapter of the Implementing Procurement documentation.
61 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 84.. Process flow to set up purchasing categories
Create Value Sets for Item Categories
Create a value set for use in item category flexfield.
Task: Manage Product and Child Value Sets
Figure 85.. Manage Product and Child Value Sets task
62 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Create a value set in Item Catalogs module.
Figure 86. Create value set
Once the value set is created, click Manage Values to create values for the category value set.
Figure 87. Create values
63 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Define Key Flexfield for Item Categories
Create key flexfield for item categories. Flexfield struc
structures
tures can be created as part of the Item Catalogs module.
Task: Manage Key Flexfield for Catalogs
Figure 88. Manage Key Flexfield for Catalogs task
There are three steps to create the key flexfield
flexfield.. Each step begins on the Manage Key Flexfield for Catalogs page.
The first step is to create a flexfield structure. Find the Item Categories flexfield and click Manage Structures.
Figure 89. Manage key flexfield for catalogs
Create a key flexfield structure.
64 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 90. Create key flexfield structure
Add a segment to the key flexfield structure and associate the value set created earlier to the segment.
Figure 91. Create key flexfield segment
This example shows a single segment item categories structure. You can define more than one segment depending
upon the organization and industry
try needs to create a desired category structure.
The second step is to create a flexfield structure instance. Find the Item Categories flexfield and click Manage
Structures Instances, then click Create on segment instances.
65 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 92. Create key flexfield structure instance
The third step is to deploy the flexfield. Find the Item Categories flexfield and click Deploy Flexfield.
Figure 93. Deploy flexfield
Create Category Catalog and Add Categories
Create a category catalog for the purchasing function in order to create categories to be used in negotiations.
66 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Task: Manage Catalogs
Figure 94. Manage Catalogs task
Create a basic catalog for purchasing categories. Enter Catalog Name and Description. Select Catalog Structure
value to be the flexfield structure instance that was defined in an earlie
earlier step. Set Catalog Content
ntent to ‘Categories
only’ since items are not defined in this implementation.
67 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 95. Create catalog
To add categories to catalog, find
d the catalog that was created and click Edit. Switch to Category Hierarchy and then
click Create Category. This is required for the Category LOV.
Create a category and add it as the default category.
ategory. This is required when assigning the default catalog for
purchasing in the next step.
68 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 96. Create default category
Assign Default Catalog
Specify the default catalog for purchasing functional area
area.
Task: Manage Default Catalogs
69 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 97. Manage Default Catalogs task
Assign the catalog created before to the Purchasing functional area. This is required for selecting purchasing
categories when defining negotiation lines during negotia
negotiation creation.
70 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 98. Assign default catalog to Purchasing
Complete Procurement Setup
Complete the necessary setup for initializing procurement related functionality.
71 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 99.. Process flow to complete procurement setup
Create Units of Measure
Create units of measure to be used in negotiation lines.
Task: Manage Units of Measure
Figure 100. Manage Units of Measure task
72 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
First, create a UOM class. Click Manage UOM Classes.
Figure 101. Create UOM class
Then, add the UOMs for the UOM Class.
Figure 102. Create units of measure
Manage Supplier User Roles
Specify roles that can be provisioned to supplier users.
Task: Manage Supplier User Roles
73 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 103. Manage Supplier User Roles task
For standalone Fusion Sourcing, the following supplier roles are recommended:
responding
ponding to requests for
» Supplier Bidder – A sales representative from a potential supplier responsible for res
quote, requests for proposal, requests for information and reverse auctions.
» Supplier Self Service Administrator - Manages the profile information for the supplier company. Primary tasks
include updating supplier contact information and administering user accounts to grant employees access to the
buying organization's application.
» Supplier Self Service Clerk - Updates the profile information for the supplier company. Primary tasks include
updating supplier contact information and req
requesting
uesting user accounts to grant employees access to the buying
organization's application.
74 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 104. Manage supplier user roles
Create Item Organization
Item organization is an organization that contains
ontains the definitions of items and is used when the storage or movement
of inventory does not need to be physically or financially tracked. In Fusion Sourcing, this organization is used for
business unit transactions and is required to be defined, even iiff the organization does not have any items. This is
required for setting up business function of the business unit in the next step.
Note: If you need to define organizations that store and transact items for inventory management, you need to
define inventory
ory organizations instead. To create inventory organizations, you need to define a ledger first and use
the Manage Inventory Organizations task.
Task: Manage Item Organizations
75 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 105. Manage Item Organizations task
Enter the item organization details.
Figure 106. Create item organization
76 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Configure Procurement Business Function
Configure the procurement business function for the business unit to specify procurement document control,
document defaults, and related settings.
Task:: Configure Procurement Business Function
Figure 107.. Configure Procurement Business Function task
Use the
e item organization created in the previous step as the inventory organization
organization, and specify the currency for the
procurement business unit. You can also configure the sourcing related options in the Sourcing section.
77 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 108. Configure procurement business function
Set Sourcing Offering to Implemented
On Configure Offerings page, set the implementation stat
status of the Sourcing offering to ‘Implemented’.. This is
required for creating supplier user accounts
ccounts in supplier portal.
78 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Figure 109. Set Sourcing offering to implemented
Setup for Sourcing Activities
Once the procurement setup is completed, additional setup for sourcing activities can be p
performed
erformed before category
managers begin to conduct negotiations. The following setup steps are not required and they can be completed at a
later time. You can refer to the Implementing
lementing Procurement documentation for details.
Define Sourcing Configuration
The implementation user can optionally perform the following sourcing related tasks based on the functionality
required by your organization.
In the Define Common Procurement Configuration
onfiguration task list, go to the following tasks.
» Manage Sourcing Negotiation Approvals
» Manage Sourcing Negotiation Award Approvals
» Manage Procurement Document Numbering
For more information on approvals, refer to the Setting Up Document Approvals in Oracle Fusion Procurement white
paper.
In the Define Sourcing
g Configuration task list, go to the following tasks.
» Manage Negotiation Styles
» Manage Sourcing Lookups
» Manage Supplier Questions
» Manage Cost Factors
» Manage Sourcing Descriptive Flexfields
» Manage Sourcing Notifications
» Configure Negotiation Award Outbound Service
79 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Define Negotiation Tools
The implementation
mplementation user can define public reusable lists and templates that are accessible by all category
managers. The public attribute lists, cost factor lists, and negotiation templates can be used to standardize company
policies or best practices.
In the Define Sourcing Configuration task list, go to the following tasks.
» Manage Attribute Lists
» Manage Cost Factor Lists
» Manage Negotiation Templates
In addition, category managers can define public
ublic and private reusable lists and templates themselves to streamline
sourcing document creation. The setup links are available under Tasks in the Negotiations work area.
Register Suppliers
Supplier administrators can register suppliers and create supplier
ier contacts. They can also create user accounts for
supplier contacts in order to access supplier portal and respond to negotiations. Besides, suppliers can use the self
service registration to register themselves directly. For more information on configu
configuring
ring the registration, you can
refer to the Configure Supplier Registration chapter in the Implementing Procurement documentation.
Log in as a supplier administrator.
dministrator. From Navigator, click Suppliers under Procurement, and then click
lick Register
Supplier under Tasks in the Suppliers work area. Enter the registration and company
mpany details for the supplier, and
then create
reate contacts and user accounts for the contac
contacts.
ts. The supplier roles that are set up before can be selected
for the supplier contacts.
Besides registering suppliers in the Suppliers work area, new supplier records can be imported from external
systems as well. You can refer to the Supplier Import chap
chapter in the Implementing Procurement documentation for
details.
This concludes the implementation using the full implementation task list. If you have other setup requirements,
requirements you
can go to the corresponding tasks in the task list. Otherwise, the setup is complete and category managers can
begin to conduct negotiations.
80 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Conclusion
Oracle Fusion Sourcing can be implemented as a standalone application with minimum setup steps to run in a
coexistence model with existing applications. Companies can ffurther
urther reduce the number of setup steps and the
amount of implementation time by using the
he rapid implementation task list that leverages system defaults and setup
process. On the other hand, they can extend the ssetup
etup to include additional functionality like maintaining master
items, requisitions and creation of purchasing documents.
81 | STANDALONE FUSION SOURCING IMPLEMENTATION – ORACLE FUSION SOURCING RELEASE 11
Oracle Corporation, World Headquarters
Worldwide Inquiries
500 Oracle Parkway
Phone: +1.650.506.7000
Redwood Shores, CA 94065, USA
Fax: +1.650.506.7200
CONNECT W ITH US
blogs.oracle.com/oracle
facebook.com/oracle
twitter.com/oracle
oracle.com
Copyright © 2015
2015, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the
contents hereof are subject to change without notice. This document is not warranted to be error-free,
error
nor subject to any other
warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations
ob
are
formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
a
means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license
licens and
are tradema
trademarks
rks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0615
Standalone Fusion Sour
Sourcing Implementation – Oracle Fusion Sourcing Release 11
May 2016