Professional Documents
Culture Documents
April 2013
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 making purchasing decisions. The development, release,
and timing of any features or functionality described for Oracles products remains at the sole discretion
of Oracle.
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 products 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 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. Companies can benefit from advantages of using next
generation functionality and new intuitive Fusion UI 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 using minimum required setup steps. This whitepaper assumes a
fresh installation of Oracle Fusion Sourcing Release 7. The information in this document can
also be used by customers implementing Oracle Fusion Sourcing Services in the Oracle
Cloud. Implementation steps are broadly organized into following activities.
Provision users
Getting Started:
From the Getting Started with Oracle Fusion Applications page, select Procurement to navigate to the
Offering where information documents like the Offering Content Guide can be downloaded in various
formats like PDF, XML or XLS.
Configure Offerings
From the Tasks, select Configure Offerings. Offerings are application solution sets representing one or
more business processes and activities that you typically provision and implement as a unit. All
offerings and options are displayed on the Configure Offerings page and are available for
configuration. However an offering must be provisioned if you want to enable it for implementation.
The Provisioned column indicates whether or not an offering is provisioned for implementation.
For implementing standalone Fusion Sourcing with minimum setup necessary to run a negotiation
event, Procurement must be provisioned. Procurement and Sourcing must be selected for
implementation.
Select Feature Choices: Click on the Edit icon in the Select Feature Choices column for
Procurement. This whitepaper assumes a basic minimum implementation without 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
Check Procurement and Sourcing checkboxes in the Include column. Save and open project.
In the table, 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.
The automatically generated task list for Procurement and Sourcing contains additional steps that will be useful depending upon
the coverage of your implementation. This whitepaper assumes a simpler installation, and only describes minimum necessary
steps. You can access the generated task list with minimum setup steps on My Oracle Support https://support.oracle.com.
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, it can be 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 on an as needed basis to keep
the product tables synchronized with subsequent updates to LDAP.
Oracle Identity Manager Delegated Administration Action: Create User. This is the
implementation user who will execute implementation tasks.
IT Security Manager
10
11
On the Manage Data Roles and Security Profiles page, search for the Human Capital Management
Application Administration Role (Predefined).
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 profile from the dropdown choicelist.
12
13
Log in as the implementation user created in the previous steps. From Navigator ToolsSetup and
Maintenance search and access the implementation project.
Access the task list and locate the next tasks.
14
Create Location
A location identifies 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
15
16
17
Legal entity is required when creating employees (users) to identify their legal employer.
Single Assignment
Multiple Assignments
By default, every enterprise uses the two-tier single-assignment employment model. You can select a
different employment model for the enterprise or for individual legal employers. For more information
on selecting employment model for your enterprise, find the topic in Fusion Learning Center, or see
help topics using the user assistance panels in the application.
Task: Manage Legal Entity HCM Information
Select Scope as Manage Legal Entity HCM Information.
18
19
Enter employment model this step is required when creating HCM user, for selecting a legal
employer for the user.
20
Create Business Unit. Select a location and a default reference data set. If you have not defined a
reference data set, the common set can be used.
21
22
Provision Users
The enterprise and the business units need to define employees as users. Creation and provisioning of
users with necessary roles to carry out procurement and sourcing related functions will enable them to
execute transactions for the business unit.
23
24
HCM application administrator and employee role is auto-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. If a role is set as Self requestable users can request
provisioning of this role for self.
25
Create user for the employee who is the HCM Administrator and auto-provision roles for the HCM
user and verify that the user was granted Employee and Human Capital Management Application
Administrator roles.
26
Create users and provision the following roles for these procurement users:
27
Employee
Buyer
Supplier Administrator
Category Manager
28
Manage Value Sets and Define Key Flexfields for Item Categories
Create a Value Set for use in category flexfield. Flexfield structures can be created as part of the Oracle
Middleware Extensions for Applications module.
Task: Manage Value Sets
29
30
Create Flex Field Structure: Find the flexfield Item categories and Manage Structures.
31
Add a segment to the item categories structure: Create Key Flex field Structure
This example shows a single segment item categories structure. You can define more than one
segments depending upon the organization and industry needs to create a desired category structure.
Create Structure Instance
Create structure instance for item category flexfield: Create segment instances for item category
flexfield.
Task: Define Common Procurement Configuration > Define Basic Catalogs > Manage Key Flexfields
for Catalogs.
Find the flexfield and click Manage Structure Instances button, then click Create on segment instances.
32
Deploy Flexfield
Deploy item category flexfield. Task: Define Common Procurement Configuration > Define Basic
Catalogs > Manage Key Flexfields for Catalogs.
Find the Item Flexfield key flexfield and click Deploy button.
Once the flexfield is deployed, values can be created for the category value set. Add values to the value
sets: Task: Manage Value Sets > Search for PO Item Category and Manage Values.
33
Enter Catalog Name and Description. Select Catalog Structure value to be the Flex Field Structure that
was defined for Category in earlier step. Set catalog content to Categories Only since items are not
defined in this implementation. Save and Close.
Add categories to catalog.
Task: Manage Catalogs.
Find the catalog that was created, then click Edit button. Switch to Category Hierarchy then click Add.
This is required for Category LOV. This action opens a new browser tab.
34
Create and add a Default Category. This step is required when assigning default catalog for Purchasing
in next step.
35
36
37
38
39
40
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 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 requesting user accounts to
grant employees access to the buying organization's application.
41
42
Note: When defining inventory organization, the Usage should be specified as Item Management. For
usage as Inventory Management, Ledger needs to be defined.
43
Configure the procurement business function for the procurement business unit to specify
procurement document control, document defaults, numbering and related settings. Associate an
inventory organization for this procurement business unit.
44
Sourcing Implemented
Set offerings status to "Implemented" Configure Offerings. This is required for creating supplier user
accounts for supplier portal.
45
Create Suppliers
Log in as Supplier Administrator. Navigator > Procurement > Suppliers
Create Negotiations
Log in as a Category Manager. Through Navigator > Procurement > Negotiations
46
Conclusion
Oracle Fusion Sourcing can be implemented as a standalone application with minimum setup steps to
run in a coexistence model with existing applications. Setup can be extended to include additional
functionality like maintaining Master Items, Requisitions and Creation of Purchasing Documents.
47
April 2013
Author: Poornima Bhilegaonkar
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, nor subject to any other warranties or conditions, whether expressed orally or implied in
Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.
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 are formed either directly or indirectly by this document. This
document may not be reproduced or transmitted in any form or by any 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.
Worldwide Inquiries:
Phone: +1.650.506.7000
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and
Fax: +1.650.506.7200
are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are
trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. 0113
oracle.com