PON SourcingStandaloneImplementation Whitepaper 01152014 PDF

An Oracle White Paper
April 2013
Standalone Fusion Sourcing Implementation

Oracle Fusion Sourcing
Standalone Fusion Sourcing Implementation
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 Oracle’s products remains at the sole discretion
of Oracle.
Standalone FusionSourcing Implementation
Executive Overview ........................................................................... 1

Introduction ....................................................................................... 1
Prepare for Implementation ............................................................... 2
Configure Offerings ....................................................................... 4
Create Implementation Project ...................................................... 5
Run Users and Roles Synchronization Process ............................. 8
Create Implementation User .......................................................... 9
Create Data Role for Implementation Users ................................ 11
Provision "View All" HCM Data Role ............................................ 13
Setup the Enterprise ........................................................................ 13
Create Location ........................................................................... 15
Create Legal Address .................................................................. 16
Create Legal Entity ...................................................................... 17
Update Employment Model ......................................................... 18
Create Business Unit ................................................................... 20
Assign Procurement Business Function to Business Unit ............ 21
Rename Setup Enterprise ........................................................... 22
Provision Users ............................................................................... 23
Create Role Mapping ................................................................... 23
Create First HCM User ................................................................ 26
Create User for Procurement ....................................................... 27
Create Procurement Agent .......................................................... 28
Setup Purchasing Categories .......................................................... 29
Manage Value Sets and Define Key Flex Fields for Item Categories29
Create Category Catalog and Add Categories ............................. 34
Assign Default Catalog for Purchasing Functional Area ............... 36
Complete Procurement Setup ......................................................... 37
Specify Supplier Numbering ........................................................ 37
Create Payment Terms................................................................ 38
Create Units of Measure .............................................................. 39
Manage Supplier User Roles ....................................................... 40

Configure Supplier Registration ................................................... 42
Create Inventory Organization ..................................................... 42
Configure Procurement Business Function .................................. 44
Sourcing Implemented ................................................................. 45
Setup for Sourcing Activities ............................................................ 46
Sourcing Related Setup ............................................................... 46
Create Suppliers .......................................................................... 46
Create Negotiations ..................................................................... 46
Conclusion ...................................................................................... 47
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.
 Prepare for implementation

 Set up the enterprise
 Provision users
 Set up purchasing categories
 Complete setup for procurement
 Set up for sourcing activities
1
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.
If you do not know the URLs, contact the person who installed the systems at your company. When
the Oracle Fusion Applications provisioning process completes, these URLs are shown on the
summary page.
A fresh installation of Fusion Applications comes with a default login for Fusion Applications
Administrator called FAADMIN. This is the super user that has all necessary roles to perform
installation and provisioning of implementation users. You can use this login to access the application.
However, for actual user names and passwords specified during installation and provisioning you
should contact the person who installed the Fusion Applications.
Figure 1 Process flow for preparing for implementation
Log into the application as FAADMIN.

From Navigator select ToolsSetup and Maintenance
2
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.
Figure 2 Select Procurement Offering
3
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.
Figure 3 Configure Offerings
4
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
Figure 4 Select Feature Choices
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, sequential task lists, including prerequisites, and address
dependencies to give full visibility to end-to-end setup requirements for your selected offerings.
Select Manage Implementation Projects from Tasks. Create Implementation Project for Standalone
Sourcing.
5
Figure 5 Manage Implementation Project
Click on Next to select offerings to implement.
Figure 6 Create Implementation Project: Standalone Sourcing
6
Check Procurement and Sourcing checkboxes in the Include column. Save and open project.
Figure 7 Select Offerings to Implement for the Implementation 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.
7
Run Users and Roles Synchronization Process

Task: Run Users and Roles Synchronization Process
Figure 8 Task: Run Users 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, 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.
8
Create Implementation User

To start an Oracle Fusion Applications implementation, you must set up one or more initial users
using the super user that was created during installation and provisioning of the Oracle Fusion
Applications environment, or using the initial administrator user provided by Oracle for Oracle Cloud
Application Services implementations.
Task: Create Implementation Users.
Figure 9 Create Implementation User
Create Implementation User task opens Oracle Identity Manager.

Create an implementation user with the IT Security Manager job role and provision the user. This user
can now create an implementation user with Application Implementation 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 application administrators and has the necessary ‘View All’ access to all secured
objects. These users will typically have access to set up basic enterprise structure needed to implement
offerings.
If you plan to use the Oracle Fusion Applications super user to set up the basic enterprise structure as
well, then you do not need to create any additional users. Alternatively you might want to distribute the
responsibilities for setting up the basic enterprise structure to multiple people and create one or more
implementation users.
For sake of this whitepaper the same user will execute the IT Security Manager and Application
Implementation Consultant roles.
9
Oracle Identity Manager – Delegated Administration  Action: Create User. This is the
implementation user who will execute implementation tasks.
Figure 10 OIM Delegated Administration: Create User
Assign the following roles to the implementation user.

 Application Implementation Consultant
 IT Security Manager
10
Create Data Role for Implementation Users

Create a data role based on the Human Capital Management Application Administrator job role to
view all security profiles so a single user will be able to perform all required Human Capital
Management setup steps.
Task: Create Data Role for Implementation Users.
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.
 View All Organizations
 View All Positions
 View All Countries
 View All Legislative Data Groups
 View All Workers
 View All Document Types
 View All Payrolls
 View All Payroll Flows
12
Provision "View All" HCM Data Role

Log into Oracle Identity Manager. Provision "View All" HCM data role to the created implementation
users. Assign the Human Capital Management Application Administrator role to the implementation
user you created earlier.
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.
13
Log in as the implementation user created in the previous steps. From Navigator  ToolsSetup 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
Figure 11 Manage Locations Task
Create location, review and then submit.
15
Figure 12 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
Figure 13 Manage Legal Addresses
16
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 14 Manage Legal Entity Task
17
Legal entity is required when creating employees (users) to identify their legal employer.
Figure 15 Create Legal Entity
Update Employment Model

A legal entity is a legal employer and must have a defined employment model. Verify that the legal
entity has an employment model configured. The two-tier employment model comprises of two types
of entities, work relationships and assignments. In the three-tier employment model, employment
terms are considered as the third tier to express employment possibilities.
When you configure the employment model for the enterprise or legal employer (when you create or
update the enterprise or legal employer), you can select from three two-tier options:
 Single Assignment
 Single Assignment with Contract
 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
Select and add the legal entity and update it.
19
Enter employment model – this step is required when creating HCM user, for selecting a legal
employer for the user.
Figure 16 Update Employment Model
Create Business Unit

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. 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 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.
Task: Manage Business Units
Figure 17 Select Scope Manage Business Units
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.
Figure 18 Create Business Unit
Assign Procurement Business Function to Business Unit

Task: Assign Business Unit Business Function
Figure 19 Assign Procurement Business Function to Business Unit
21
Rename Setup Enterprise

Update the seeded name “Setup Enterprise” to the actual enterprise name. The enterprise setup steps
are complete.
Task: Manage Enterprise HCM Information
Figure 20 Rename Enterprise
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.
Figure 21 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 their jobs or positions. Roles must be provisioned to
users; otherwise, users have no access to data or functions. For this, first a role mapping needs to be
created between the role and a set of conditions based on assignment attributes such as department,
job and person type. This role mapping defines whether a role can be provisioned for 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 for that role. For defining users for sourcing, we first need to create role
mappings for an HCM super user who can hire employees, and procurement users who will perform
procurement and sourcing related functions.
23
Task: Manage HCM Role Provisioning Rules
Figure 22 Task: Manage HCM Role Provisioning Rules
Manage Role Mappings > Create Role Mapping

 Human Capital Management Applications Administrator (Auto Provision)
 Employee (Auto Provision, Requestable)
 Buyer (Requestable, Self Requestable)
 Category Manager (Requestable, Self Requestable)
 Supplier Administrator (Requestable, Self Requestable)
24
Figure 23 Create Role Mapping
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 First HCM User

Create the first HCM user who has Human Capital Management Application Administrator role who
can later define employees as users for procurement. Task: Manage Users
Figure 24 Manage Users
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.
Figure 25 Create User
26
Create User for Procurement

Log in to the application as the HCM Applications Administrator. Use the navigator to access Manage
Users page.
Navigator > Manager Resources > Manage Users: Create User
Figure 26 Navigator > Manage Users
Create users and provision the following roles for these procurement users:
 Employee
 Buyer
 Supplier Administrator
 Category Manager
27
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.
When implementing only the Sourcing functionality, agents should be allowed to manage negotiations
and manage suppliers.
Task: Manage Procurement Agents
Figure 27 Create Procurement Agent
28
Setup Purchasing Categories

Setup the category flexfield structure to define purchasing categories.
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
Figure 28 Manage Value Sets
Create Value Set for Purchasing Category
Figure 29 Create Value Set
29
Define Key Flexfields for Catalogs
Define flexfield structure for item categories.

Task: Manage Key Flexfields for Catalogs
Figure 30 Task: Manage Key Flexfields
30
Create Flex Field Structure: Find the flexfield Item categories and Manage Structures.
Figure 31 Manage Key Flexfield for Catalogs
Figure 32 Create Key Flexfield Structure
31
Create Flex Field Structure Segment
Add a segment to the item categories structure: Create Key Flex field Structure
Figure 33 Create Key Flexfield Segment
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.
Figure 34 Create Key Flexfield Structure Instance
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.
Figure 35 Deploy Flexfield
Create Values
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.
Figure 36 Create Values
33
Create Category Catalog and Add Categories

Create a category catalog which can be later used for the purchasing function to create categories to be
used in negotiations:
Task: Create Catalog
Create a basic catalog for purchasing categories.
Figure 37 Create Catalog
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
Figure 38 Task: Manage Catalogs
Create and add a Default Category. This step is required when assigning default catalog for Purchasing
in next step.
Figure 39 Create Catalog and Add Default Category
35
Assign Default Catalog for Purchasing Functional Area

Specify default catalog values: Task: Manage Default Catalogs.
Assign default catalog to the Purchasing functional area. This is required for selecting purchasing
categories for negotiation lines when creating a negotiation.
Figure 40 Assign Default Catalog to Purchasing
36
Complete Procurement Setup

Complete the necessary setup for initializing procurement related functionality.
Figure 41 Process flow for completing procurement related functional setup
Specify Supplier Numbering

Define and maintain setup components prior to creating suppliers including lookups, category
hierarchy, and supplier numbering. Task: Specify Supplier Numbering
Figure 42 Task: Specify supplier numbering
37
Create Payment Terms

Task: Manage Payment Terms
Figure 43 Task: Manage Payment Terms
Figure 44 Manage Payment Terms
38
Figure 45 Create Payment Terms
Create Units of Measure

Create Units of Measure Class: Task: Create Units of Measure
Click on Manage UOM Class
Figure 46 Create Units of Measure
39
Figure 47 Manage Units of Measure
Manage Supplier User Roles

Specify roles that can be provisioned to supplier users.
Task: Manage Supplier User Roles
Figure 48 Task: Manage Supplier User Roles
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.
Figure 49 Add Supplier User Roles
41
Configure Supplier Registration

Configure what information you want to capture from potential suppliers when they register online or
when internal users create supplier registration requests. The Configure Supplier Registration page
enables a procurement business unit (BU) to select which optional profile components to capture on
registrations, which can include; address information, business classifications, product category
offerings, and bank account details. The components can be enabled for internal users and supplier
users. Internal users are authenticated users in the buying organization. Supplier users are prospective
suppliers accessing the Supplier Registration flow. Only components selected for internal users can
then be selected for supplier users.
Figure 50 Configure Supplier Registration
Create Inventory Organization

Create an Inventory Organization. This is an organization that tracks inventory transactions and
balances, and can manufacture or distribute products. In Fusion Sourcing, this organization is used for
business unit transactions and is required to be defined, even if the organization will not perform any
inventory management function. This is required for setting up business unit business function.
(Configure Procurement Business Function)
Task: Manage Inventory Organizations
42
Note: When defining inventory organization, the Usage should be specified as Item Management. For
usage as Inventory Management, Ledger needs to be defined.
Figure 51 Task: Manage Inventory Organizations
Figure 52 Create Inventory Organizations
43
Configure Procurement Business Function

Task: Configure Procurement Business Function
Select Scope: Select and Add Procurement BU.
Figure 53 Task: Configure Business Unit Business Function
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.
Figure 54 Configure Procurement Business Function
44
Sourcing Implemented
Set offerings status to "Implemented" – Configure Offerings. This is required for creating supplier user
accounts for supplier portal.
Figure 55 Sourcing Implemented
45
Setup for Sourcing Activities

Once the setup is completed, category managers can prepare for beginning sourcing activities by
creating cost factors, negotiation styles and templates. Supplier administrators can create suppliers and
supplier contacts and create user accounts for supplier contacts for accessing supplier portal and
submit responses to negotiations.
Sourcing Related Setup

From Navigator  ToolsSetup and Maintenance
Setup Cost Factors
Setup Negotiation Styles
Log in as a Category Manager. Through Navigator > Procurement > Negotiations

Create Negotiation Templates – These are templates that can be created and maintained and later
applied for specific negotiation events.
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
Standalone Fusion Sourcing Implementation Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
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
law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any
Oracle Corporation
liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This
World Headquarters
document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our
500 Oracle Parkway
prior written permission.
Redwood Shores, CA 94065
U.S.A.
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

PON SourcingStandaloneImplementation Whitepaper 01152014 PDF

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

PON SourcingStandaloneImplementation Whitepaper 01152014 PDF

Uploaded by

Copyright:

Available Formats

An Oracle White Paper

Standalone Fusion Sourcing Implementation

Executive Overview ........................................................................... 1

Manage Supplier User Roles ....................................................... 40

 Prepare for implementation

Prepare for Implementation

Figure 1 Process flow for preparing for implementation

Log into the application as FAADMIN.

Figure 2 Select Procurement Offering

Figure 3 Configure Offerings

Figure 4 Select Feature Choices

Create Implementation Project

Figure 5 Manage Implementation Project

Click on Next to select offerings to implement.

Figure 6 Create Implementation Project: Standalone Sourcing

Figure 7 Select Offerings to Implement for the Implementation Project

Run Users and Roles Synchronization Process

Figure 8 Task: Run Users and Roles Synchronization Process

Create Implementation User

Task: Create Implementation Users.

Figure 9 Create Implementation User

Create Implementation User task opens Oracle Identity Manager.

Figure 10 OIM Delegated Administration: Create User

Assign the following roles to the implementation user.

Create Data Role for Implementation Users

Provision "View All" HCM Data Role

Set Up the Enterprise

Figure 11 Manage Locations Task

Create location, review and then submit.

Figure 12 Create Location

Create Legal Address

Figure 13 Manage Legal Addresses

Create Legal Entity

Figure 14 Manage Legal Entity Task

Figure 15 Create Legal Entity

Update Employment Model

Select and add the legal entity and update it.

Figure 16 Update Employment Model

Create Business Unit

Figure 17 Select Scope Manage Business Units

Figure 18 Create Business Unit

Assign Procurement Business Function to Business Unit

Figure 19 Assign Procurement Business Function to Business Unit

Rename Setup Enterprise

Figure 20 Rename Enterprise

Figure 21 Provision Users

Create Role Mapping

Task: Manage HCM Role Provisioning Rules

Figure 22 Task: Manage HCM Role Provisioning Rules

Manage Role Mappings > Create Role Mapping

Figure 23 Create Role Mapping

Create First HCM User

Figure 24 Manage Users

Figure 25 Create User

Create User for Procurement

Figure 26 Navigator > Manage Users

Create Procurement Agent

Configure procurement agent access to information, such as purchasing documents, suppliers,

Figure 27 Create Procurement Agent

Setup Purchasing Categories

Figure 28 Manage Value Sets

Create Value Set for Purchasing Category

Figure 29 Create Value Set