Implementing Procurement
Implementing Procurement
Implementing Procurement
Cloud
Implementing Procurement
20B
Oracle Procurement Cloud
Implementing Procurement
20B
Part Number F27737-03
Copyright © 2011, 2020, Oracle and/or its aliates.
Authors: Joe Kolb, Vic Mitchell, Richard D. Sears, Charles Frakes, Eric Bell, Sathyan Nagarajan, Santosh Mall
Contributors: Essan Ni Jirman, Tina Brand, P. S. G. V. Sekhar, Suzanne Kinkead, Barbara Snyder, Srinivas Vellikad, Megan Wallace, Kathryn
Wohnoutka, Jacqueline Wood, Pramod Singh
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by
intellectual property laws. Except as expressly permied in your license agreement or allowed by law, you may not use, copy, reproduce, translate,
broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering,
disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you nd any errors, please report
them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then
the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or
activated on delivered hardware, and modications of such programs) and Oracle computer documentation or other Oracle data delivered to or
accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to
the applicable Federal Acquisition Regulation and agency-specic supplemental regulations. As such, the use, reproduction, duplication, release,
display, disclosure, modication, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system,
integrated software, any programs embedded, installed or activated on delivered hardware, and modications of such programs), ii) Oracle computer
documentation and/or iii) other Oracle data, is subject to the rights and limitations specied in the license contained in the applicable contract. The
terms governing the U.S. Government's use of Oracle cloud services are dened by the applicable contract for such services. No other rights are
granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use
in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in
dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe
use. Oracle Corporation and its aliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its aliates. Other names may be trademarks of their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks
or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle
Corporation and its aliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and
services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its aliates will not be responsible
for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable
agreement between you and Oracle.
Oracle Procurement Cloud
Implementing Procurement
Contents
Preface i
1 Overview 1
Implement Procurement .............................................................................................................................................................. 1
Purchase and Activation of Oracle Cloud Application Services .......................................................................................... 2
4 Implementation Users 13
Overview of Implementation Users ......................................................................................................................................... 13
Preface
This preface introduces information sources that can help you use the application.
Help
Use help icons to access help in the application. If you don't see any help icons on your page, click your user image
or name in the global header and select Show Help Icons. Not all pages have help icons. You can also access the Oracle
Help Center to nd guides and videos.
Watch: This video tutorial shows you how to nd and use help.
You can also read about it instead.
Additional Resources
• Community: Use Oracle Cloud Customer Connect to get information from experts at Oracle, the partner
community, and other users.
Conventions
The following table explains the text conventions used in this guide.
Convention Meaning
boldface Boldface type indicates user interface elements, navigation paths, or values you enter or select.
monospace Monospace type indicates le, folder, and directory names, code examples, commands, and URLs.
i
Oracle Procurement Cloud Preface
Implementing Procurement
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website.
Videos included in this guide are provided as a media alternative for text-based help topics also available in this guide.
Contacting Oracle
ii
Oracle Procurement Cloud Chapter 1
Implementing Procurement Overview
1 Overview
Implement Procurement
To start an implementation of Oracle Procurement Cloud, you must be assigned the Application Implementation
Consultant role (ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB), and you must opt into the
Procurement oering, plus any other oerings that are applicable to your business requirements. Refer to the Oracle
Applications Cloud: Using Functional Setup Manager guide to manage the opt-in and setup of your oerings.
Procurement Oering
Use the Procurement oering to manage all aspects of the procurement process, such as creating requisitions and
purchase orders, sourcing goods and services, and qualifying suppliers.
This table lists some of the primary functional areas of the Procurement oering. For the full list of functional areas and
features in the oering, use the Associated Features report that you review when you plan the implementation of your
oering.
Purchasing Categories Congure catalogs and category hierarchies, and assign items to the catalog.
Procurement Foundation Dene components that are common across procurement processes, including payment
terms, carriers, hazard classes, and freight terms.
Purchasing Foundation Congure key setup options related to your purchasing process.
Self Service Procurement Determine how you will manage procurement catalog content and align requisition entry to
your organization's business strategy.
Procurement Contracts Review and update seings that control how you create and manage enterprise contracts with
suppliers.
1
Oracle Procurement Cloud Chapter 1
Implementing Procurement Overview
Related Topics
• Oracle Applications Cloud Using Functional Setup Manager
• Plan Your Implementation
Purchasing and activating any Oracle Cloud service is described in the Oracle Cloud: Geing Started with Oracle Cloud
guide. Many administrative tasks are covered in the Oracle Cloud: Managing and Monitoring Oracle Cloud guide. All of
the following references in this section point to one of these guides.
Note: Not everything in these guides is relevant to Oracle Cloud Application Services, for example details
about Oracle Java Cloud Service and Oracle Database Cloud Service.
Service Verication
• The administrator who was identied during the activation process:
2
Oracle Procurement Cloud Chapter 1
Implementing Procurement Overview
◦ Veries that the service is activated. Refer to the Oracle Cloud: Geing Started with Oracle Cloud guide.
◦ Manages and monitors the service. Refer to the Oracle Cloud: Managing and Monitoring Oracle Cloud
guide.
◦ Optionally create initial administrator and implementation users before enterprise structures setup.
• Alternatively, the administrator sets up enterprise structures and then creates service users, including
functional implementors.
• Functional implementors perform conguration and setup steps.
• Developers can add features to extend the application.
3
Oracle Procurement Cloud Chapter 1
Implementing Procurement Overview
4
Oracle Procurement Cloud Chapter 2
Implementing Procurement Geing Started with a Procurement Rapid Implementation
Dene Enterprise Structure for Two versions of this task list are provided. One is for rapid implementations where the
Procurement Rapid Implementation Purchasing optional module is included. The other is for implementations when Purchasing is
excluded. Select the one which applies for your implementation, and remove the version which
doesn't apply.
In the version including Purchasing, you can use spreadsheet upload utilities for business
units, legal entities, chart of accounts, banking structures, and more.
5
Oracle Procurement Cloud Chapter 2
Implementing Procurement Geing Started with a Procurement Rapid Implementation
Congure Basic Enterprise Structure Use this task to run an automated process that performs several enterprise structure setup
for Procurement tasks.
Dene Procurement Security Use this task list for all rapid implementations. Use it to dene application users, assign them
Conguration for Rapid roles, and dene procurement agents.
Implementation
Use the following task lists to congure the applicable optional modules for your rapid implementation:
• Dene Purchasing Conguration for Rapid Implementation
• Dene Self-Service Procurement Conguration for Rapid Implementation
• Dene Supplier Portal Conguration for Rapid Implementation
• Dene Sourcing Conguration for Rapid Implementation
• Dene Supplier Qualication Conguration for Rapid Implementation
• Dene Procurement Contract Terms Conguration for Rapid Implementation
• Dene Invoicing and Payments Conguration for Rapid Implementation
6
Oracle Procurement Cloud Chapter 2
Implementing Procurement Geing Started with a Procurement Rapid Implementation
Task Structures
Create Chart of Accounts, Ledger, Chart of accounts, accounting calendar, ledgers and ledger conguration.
Legal Entities, and Business Units in
Spreadsheet Legal addresses, legal entity and legal entity registrations, assigning legal entities to ledgers.
Business units, assigning business functions to business units, and more.
Find the two versions of the Dene Enterprise Structure for Procurement Rapid Implementation task lists in the Setup
and Maintenance work area. They are under the Dene Procurement Conguration for Rapid Implementation task list.
To create a procurement rapid implementation task list, see the topic: Geing Started with Your Procurement Rapid
Implementation: Procedure.
To submit the process, rst enter two input parameters: Centralized Procurement Business Unit Name, and Currency.
7
Oracle Procurement Cloud Chapter 2
Implementing Procurement Geing Started with a Procurement Rapid Implementation
When you submit the process, the following enterprise structure setup tasks are congured automatically, based on
existing enterprise structures set up for the organization:
• Creates a new business unit with the procurement business function, and congures it as a service provider for
all other business units in the organization.
• Congures each business unit with the requisitioning business function.
• Creates an item organization, which is the master inventory organization.
• Creates one inventory organization for each of the other business units.
• Congures the inventory organization parameters and receiving parameters for each inventory organization
created.
• Creates a workday shift, paern and schedule.
• For the procurement business unit, creates a common content zone and catalog. Provides users in all
requisitioning business units access to all agreements and master items while creating requisitions.
• Creates most commonly used units of measure and their standard conversions.
Find the Congure Basic Enterprise Structure for Procurement task in the Setup and Maintenance work area. The task
is under the Dene Common Procurement Conguration Rapid Implementation task list. To create a procurement rapid
implementation task list, see the topic: Geing Started with Your Procurement Rapid Implementation: Procedure.
Tasks
The following tasks are associated with dening Supplier Portal conguration using the rapid implementation approach:
1. *Manage Supplier User Roles
2. *Manage Supplier User Role Usages
3. *Congure Supplier Registration
* Required task
Note: Refer to the Oracle Fusion Applications Procurement Implementation Guide for additional details on
tasks in the Dene Supplier Portal Conguration task list.
8
Oracle Procurement Cloud Chapter 2
Implementing Procurement Geing Started with a Procurement Rapid Implementation
9
Oracle Procurement Cloud Chapter 2
Implementing Procurement Geing Started with a Procurement Rapid Implementation
10
Oracle Procurement Cloud Chapter 3
Implementing Procurement Synchronization of Users and Roles from LDAP
Once the Oracle Fusion Applications tables are initialized with this information, it's maintained automatically.
11
Oracle Procurement Cloud Chapter 3
Implementing Procurement Synchronization of Users and Roles from LDAP
12
Oracle Procurement Cloud Chapter 4
Implementing Procurement Implementation Users
4 Implementation Users
Related Topics
• Implementation Users
13
Oracle Procurement Cloud Chapter 4
Implementing Procurement Implementation Users
14
Oracle Procurement Cloud Chapter 5
Implementing Procurement Currencies and Currency Rates
Currencies
Considerations for Dening Currencies
When creating or editing currencies, consider these points relevant to entering the currency code, date range, or symbol
for the currency.
Currency Codes
You can't change a currency code after you enable the currency, even if you later disable that currency.
Date Ranges
You can enter transactions denominated in the currency only for the dates within the specied range. If you don't enter
a start date, then the currency is valid immediately. If you don't enter an end date, then the currency is valid indenitely.
Symbols
Some applications support displaying currency symbols. You may enter the symbol associated with a currency so that it
appears along with the amount.
Derivation Type
The Euro currency derivation type is used only for the Euro, and the Euro derived derivation type identies national
currencies of EMU member states. All other currencies don't have derivation types.
Derivation Factor
The derivation factor is the xed conversion rate by which you multiply one Euro to derive the equivalent EMU currency
amount. The Euro currency itself must not have a derivation factor.
15
Oracle Procurement Cloud Chapter 5
Implementing Procurement Currencies and Currency Rates
You can use dierent rate types for dierent business needs. During journal entry, the conversion rate is provided
automatically based on the selected conversion rate type and currency, unless the rate type is User. For User rate types,
you must enter a conversion rate. You can dene additional rate types as needed. Set your most frequently used rate
type as the default. Conversion rate types can't be deleted.
Assign conversion rate types to automatically populate the associated rate for your period average and period end
rates for the ledger. For example, you can assign the conversion rate type of Spot to populate period average rates, and
16
Oracle Procurement Cloud Chapter 5
Implementing Procurement Currencies and Currency Rates
the conversion rate type of Corporate to populate period end rates. Period average and period end rates are used in
translation of account balances.
Conversion rate types are used to automatically assign a rate when you perform the following accounting functions:
Action Results
Selected When you enter a daily rate to convert currency A to currency B, the inverse rate of currency
B to currency A is automatically calculated and entered in the adjacent column. If either rate is
changed, the application automatically recalculates the other rate.
You can update the application calculated inverse rate, but once you do, the related rate is
updated. The option enforces the inverse relationship is maintained but doesn't prevent you
from updating the rates.
Not Selected The inverse rate is calculated, but you can change the rate and update the daily rates table
without the corresponding rate being updated.
17
Oracle Procurement Cloud Chapter 5
Implementing Procurement Currencies and Currency Rates
currency is populated automatically based on the currency denition. Add or delete contra currencies in the Contra
Currencies region of the Rate Types page.
For example, if you have daily rates dened for the pivot currency, USD to the contra currency, EUR, and USD to another
contra currency, CAD, the application automatically creates the rates between EUR to CAD and CAD to EUR. You don't
have to manually dene the EUR to CAD and CAD to EUR rates.
Select the Allow Cross Rates Override check box to permit your users to override application generated cross rates. If
you accept the default of not selected, the application generated cross rates cannot be overridden.
Related Topics
• What's the dierence between calendar and scal period naming
Scenario
You are the general ledger accountant for Vision US Inc. You are entering a journal entry to capture three transactions
that were transacted in three dierent foreign currencies.
• Canadian Dollar CAD: A stable currency
• Mexican Peso MXP: A uctuating currency
18
Oracle Procurement Cloud Chapter 5
Implementing Procurement Currencies and Currency Rates
You enter two journal lines with accounts and amounts for each foreign currency transaction. Based on your company
procedures, you select the rate type to populate the rate for Corporate and Spot rate types from your daily rates table.
You manually enter the current rate for the User rate type.
The following table lists the currency, the rate type that you select, and the reasons for the rate type selection.
Your company doesn't currently use the Fixed rate type. From January 1, 1999, the conversion rate of the French franc
FRF against the Euro EUR was a xed rate of 1 EUR to 6.55957 FRF. Your French operations were started in 2007, so you
maintain all your French business records in the Euro.
Daily Rates
19
Oracle Procurement Cloud Chapter 5
Implementing Procurement Currencies and Currency Rates
Related Topics
• Guidelines for Using Desktop Integrated Excel Workbooks
20
Oracle Procurement Cloud Chapter 5
Implementing Procurement Currencies and Currency Rates
Use the Currency Rates Manager page to create, edit, and review currency rate types, daily rates, and historical
rates.
3. Click the Daily Rates tab.
Use the Daily Rates tab to review and enter currency rates.
4. Click the From Currency list. Select the GBP - Pound Sterling list item.
5. Click the To Currency list. Select the USD - US Dollar list item.
6. Enter the dates for the daily rates that you are changing. Enter today's date.
7. Click the Rate Type list. Select the Spot list item.
8. Click the Search buon.
9. Click in the Rate eld. Enter the new rate of 1.7 in the Rate eld.
10. Click in the Inverse Rate eld. Enter the new inverse rate of 0.58822 in the Inverse Rate eld.
11. Click the Save buon.
Related Topics
• Guidelines for Using Desktop Integrated Excel Workbooks
21
Oracle Procurement Cloud Chapter 5
Implementing Procurement Currencies and Currency Rates
22
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Overview
Oracle Fusion Applications have been designed to ensure your enterprise can be modeled to meet legal and
management objectives. The decisions about your implementation of Oracle Fusion Applications are aected by your:
• Industry
• Business unit requirements for autonomy
• Business and accounting policies
• Business functions performed by business units and optionally, centralized in shared service centers
• Locations of facilities
Every enterprise has three fundamental structures that describe its operations and provide a basis for reporting.
• Legal
• Managerial
• Functional
In Oracle Fusion, these structures are implemented using the chart of accounts and organization hierarchies. Many
alternative hierarchies can be implemented and used for reporting. You are likely to have one primary structure that
organizes your business into:
• Divisions
• Business Units
• Departments
23
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
This gure illustrates a grid with Business Axis, representing the enterprise division, Legal Axis representing the
companies, and the Functional Axis representing the business functions.
Business Axis
Business Divisions
A B C
A1 A2 A3 A.. B1 B2 B3 B.. C1 C2 C3 C..
Service Teams
R & D Teams
Selling Support Teams
Finance Team
HR Team
IT Team
Management
Legal Structure
The gure illustrates a typical group of legal entities, operating various business and functional organizations. Your
ability to buy and sell, own, and employ comes from your charter in the legal system. A corporation is:
24
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Many other kinds of legal entities exist, such as sole proprietorships, partnerships, and government agencies.
A legally recognized entity can own and trade assets and employ people in the jurisdiction in which the entity is
registered. When granted these privileges, legal entities are also assigned responsibilities to:
• Account for themselves to the public through statutory and external reporting.
• Comply with legislation and regulations.
• Pay income and transaction taxes.
• Process value added tax (VAT) collection on behalf of the taxing authority.
Many large enterprises isolate risk and optimize taxes by incorporating subsidiaries. They create legal entities to
facilitate legal compliance, segregate operations, optimize taxes, complete contractual relationships, and isolate risk.
Enterprises use legal entities to establish their enterprise's identity within the laws of each country in which their
enterprise operates.
For example, a group might have a separate company for each business in the United States (US), but have its United
Kingdom (UK) legal entity represent all businesses in that country.
The divisions are linked across the cards so that a business can appear on some or all of the cards. For example, the
air quality monitoring systems business might be operated by the US, UK, and France companies. The list of business
divisions is on the Business Axis.
Each company's card is also horizontally striped by functional groups, such as the sales team and the nance team.
This functional list is called the Functional Axis. The overall image suggests that information might, at a minimum, be
tracked by company, business, division, and function in a group environment. In Oracle Fusion Applications, the legal
structure is implemented using legal entities.
Management Structure
Successfully managing multiple businesses requires that you segregate them by their strategic objectives, and measure
their results. Although related to your legal structure, the business organizational hierarchies don't have to be reected
directly in the legal structure of the enterprise. The management structure can include divisions, subdivisions, lines of
business, strategic business units, prot, and cost centers. In the gure, the management structure is shown on the
Business Axis. In Oracle Fusion Applications, the management structure is implemented using divisions and business
units as well as being reected in the chart of accounts.
Functional Structure
Straddling the legal and business organizations is a functional organization structured around people and their
competencies. For example, sales, manufacturing, and service teams are functional organizations. This functional
25
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
structure is represented by the Functional Axis in the gure. You reect the eorts and expenses of your functional
organizations directly on the income statement. Organizations must manage and report revenues, cost of sales, and
functional expenses such as research and development and selling, general, and administrative expenses. In Oracle
Fusion Applications, the functional structure is implemented using departments and organizations, including sales,
marketing, project, cost, and inventory organizations.
26
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
The following gure and tablet describe the Business Process Model structures and activities.
Activities
Define Enterprise
Define Ledgers
Define Facilities
Information Technology
Set Up Information
Define Reference Data Sharing
Technology Management
Dene Enterprise Dene the enterprise to get the name of the deploying enterprise and the location of the
headquarters.
Dene Enterprise Structures Dene enterprise structures to represent an organization with one or more legal entities.
Dene organizations to represent each area of business within the enterprise.
27
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Dene Legal Jurisdictions and Dene information for governing bodies that operate within a jurisdiction.
Authorities
Dene Legal Entities Dene legal entities and legal reporting units for business activities handled by the Oracle
Fusion Applications.
Dene Business Units Dene business units of an enterprise to perform one or many business functions that can be
rolled up in a management hierarchy. A business unit can process transactions on behalf of
many legal entities. Normally, it has a manager, strategic objectives, a level of autonomy, and
responsibility for its prot and loss.
Dene Financial Reporting Structures Dene nancial reporting structures, including organization structures, charts of accounts,
organizational hierarchies, calendars, currencies and rates, ledgers, and document sequences
which are used in organizing the nancial data of a company.
Dene Chart of Accounts Dene chart of accounts including hierarchies and values to enable tracking of nancial
transactions and reporting at legal entity, cost center, account, and other segment levels.
Dene Ledgers Dene the primary accounting ledger and any secondary ledgers that provide an alternative
accounting representation of the nancial data.
Dene Accounting Congurations Dene the accounting conguration that serves as a framework for how nancial records are
maintained for an organization.
Dene Facilities Dene your manufacturing and storage facilities as Inventory Organizations if Oracle Fusion
tracks inventory balances there and Item Organizations if Oracle Fusion only tracks the items
used in the facility but not the balances.
Dene Reference Data Sharing Dene how reference data in the applications is partitioned and shared.
Note: Some product-specic implementation activities aren't listed here and depend on the applications
you're implementing. For example, you can implement Dene Enterprise Structures for Human Capital
Management, Project Management, and Sales Management.
• Enterprise Conguration
• Business Unit Management
28
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Security Structure
• Compliance Requirements
Enterprise Conguration
• What is the level of conguration needed to achieve the reporting and accounting requirements?
• What components of your enterprise do you need to report on separately?
• Which components can be represented by building a hierarchy of values to provide reporting at both detail and
summary levels?
• Where are you on the spectrum of centralization versus decentralization?
Security Structure
• What level of security and access is allowed?
• Are business unit managers and the people that report to them secured to transactions within their own
business unit?
• Are the transactions for their business unit largely performed by a corporate department or shared service
center?
Compliance Requirements
• How do you comply with your corporate external reporting requirements and local statutory reporting
requirements?
• Do you tend to prefer a corporate rst or an autonomous local approach?
• Where are you on a spectrum of centralization, very centralized or decentralized?
29
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Scenario
Your company, InFusion Corporation, is a multinational conglomerate that operates in the United States (US) and the
United Kingdom (UK). InFusion has purchased an Oracle Fusion Enterprise Resource Planning (ERP) solution including
Oracle Fusion General Ledger and all of the Oracle Fusion subledgers. You are chairing a commiee to discuss creation
of a model for your global enterprise structure including both your US and UK operations.
InFusion Corporation
InFusion Corporation has 400 plus employees and revenue of 120 million US dollars. Your product line includes all
the components to build and maintain air quality monitoring applications for homes and businesses. You have two
distribution centers and three warehouses that share a common item master in the US and UK. Your nancial services
organization provides funding to your customers for the initial costs of these applications.
Analysis
The following are elements you must consider in creating your model for your global enterprise structure.
• Your company is required to report using US Generally Accepted Accounting Principles (GAAP) standards and
UK Statements of Standard Accounting Practice and Financial Reporting Standards. How many ledgers do you
want to achieve proper statutory reporting?
• Your managers need reports that show prot and loss (revenue and expenses) for their lines of business. Do
you use business units and balancing segments to represent your divisions and businesses? Do you secure
data by two segments in your chart of accounts which represents each department and legal entity? Or do you
use one segment that represents both to produce useful, but condential management reports?
• Your corporate management requires reports showing total organizational performance with drill-down
capability to the supporting details. Do you need multiple balancing segment hierarchies to achieve proper
rollup of balances for reporting requirements?
• Your company has all administrative, account payables, procurement, and Human Resources functions
performed at their corporate headquarters. Do you need one or more business units in which to perform all
these functions? How is your shared service center congured?
30
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Consolidation of results for application components, installations, and maintenance product lines across the
enterprise
• All UK general and administrative costs processed at the UK headquarters
• US Systems' general and administrative costs processed at US Corporate headquarters
• US Financial Services maintains its own payables and receivables departments
InFusion Corporation
InFusion Financial
InFusion UK Systems Ltd.
Services Inc.
InFusion America Inc. Primary Ledger (GBP)
Primary Ledger
Primary Ledger (USD) with Reporting Currency
(USD)
Standard, Jan - Dec (USD)
Average Balancing
Standard, Jan - Dec
May-April
BU 1 BU 2 BU 3
US Systems Fin Services UK Systems
BU 4
Corporate Administration, Procurement, and HR Shared Services Center
US LE 2 UK LE 4
US LE 1 US LE 3
Bal Seg 201, Bal Seg 103, 301,
Bal Seg 101 Bal Seg 102
202, 203 302, 303
US Distribution UK Distribution
Center Center
Common Item
Master
31
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
In this chart, the green globe stands for required and gold globe stands for optional setup. The following statements
expand on the data in the chart.
• The enterprise is required because it serves as an umbrella for the entire implementation. All organizations are
created within an enterprise.
• Legal entities are also required. They can be optionally mapped to balancing segment values or represented
by ledgers. Mapping balancing segment values to legal entities is required if you plan to use the intercompany
functionality. The InFusion Corporation is a legal entity but isn't discussed in this example.
• At least one ledger is required in an implementation in which you record your accounting transactions.
• Business units are also required because nancial transactions are processed in business units.
• A shared service center is optional, but if used, must be a business unit.
• Divisions are optional and can be represented with a hierarchy of cost centers or by a second balancing
segment value.
• Departments are required because they track your employees.
• Optionally, add an item master organization and inventory organizations if you're tracking your inventory
transactions in Oracle Fusion Applications.
32
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Note: Some Oracle Fusion Human Capital Management implementations don't require recording accounting
transactions and therefore, don't require a ledger.
Accounting Calendar Period Names Dimension Member Name in Accounting Period Name
Even if case sensitivity is enabled in an aggregate storage outline for which duplicate member names is enabled, do not
use matching dimension names with only case dierences. For example, do not:
• Name two dimensions Product and product.
• Use quotation marks or brackets.
• Use tabs in dimension, member, or alias names.
33
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Restricted Characters
The following table lists the characters that are restricted and can’t be used in dimension, member, or alias names.
Character Meaning
& ampersand
@ at sign
\ backslash
{} brace
, comma
= equal sign
() parentheses
. period
+ plus sign
_ underscore
For the accounting calendar period names, you can use a hyphen or an underscore in the
middle of an accounting calendar period name. For example: Jan-15 or Adj_Dec-15 can be used
successfully.
34
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Character Meaning
| vertical bar
Other Restrictions
• Don't place spaces at the beginning or end of names. Essbase ignores such spaces.
• Don't use the following types of words as dimension or member names:
The following table lists additional words that should not be used.
DYNAMIC EMPTYPARM EQ
GE GEN GENRANGE
GROUP GT ID
IDERROR INTEGER LE
35
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
LT MBR MBRNAME
MUL MULOP NE
OR PAREN PARENPARM
SKIPNONE SKIPZERO TO
36
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
This gure illustrates the process to congure your enterprise using the Enterprise Structures Congurator.
Determine
Divisions
Position Usage
Define
Legal Entities Enterprise-Level
Attributes
Define Contextual
Business Units
Attributes
Reference Data
Sets
Business Unit
Set Assignment
Assign Reference
Data Sets to
Locations
To be able to use the Enterprise Structures Congurator, you must select the Enterprise Structures Guided Flow feature
for your oerings on the Congure Oerings page in the Setup and Maintenance work area. If you don't select this
feature, then you must set up your enterprise structure using individual tasks provided elsewhere in the oerings, and
you can't create multiple congurations to compare dierent scenarios.
37
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
make an initial recommendation. You can either accept the recommendation, or you can answer additional questions
about how you manage people in your enterprise, and then make a selection. After you select whether to use jobs or
positions, you are prompted to set up a descriptive exeld structure for jobs, and for positions if applicable. Descriptive
exelds enable you to get more information when you create jobs and positions.
Review Conguration
You can view a result of the interview process prior to loading the conguration. The review results, show the divisions,
legal entities, business units, reference data sets, and the management reporting structure that the application will
create when you load the conguration.
Load Conguration
You can load only one conguration. When you load a conguration, the application creates the divisions, legal entities,
business units, and so on. After you load the conguration, you then use individual tasks to edit, add, and delete
enterprise structures.
Scenario
InFusion Corporation is a multinational enterprise in the high technology industry with product lines that include all
the components that are required to build and maintain air quality monitoring systems for homes and businesses.
Its primary locations are in the US and the UK, but it has smaller outlets in France, Saudi Arabia, and the United Arab
Emirates (UAE).
Enterprise Details
In the US, InFusion employs 400 people and has company revenue of 120 million US dollars. Outside the US, InFusion
employs 200 people and has revenue of 60 million US dollars.
38
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Analysis
InFusion requires three divisions.
InFusion requires legal entities with legal employers, payroll statutory units, tax reporting units, and legislative data
groups for the US, UK, France, Saudi Arabia, and UAE, to employ and pay its workers in those countries.
InFusion requires a number of departments across the enterprise for each area of business, such as sales and
marketing, and a number of cost centers to track and report on the costs of those departments.
InFusion has general managers responsible for business units within each country. Those business units may share
reference data. Some reference data can be dened within a reference data set that multiple business units may
subscribe to. Business units are also required for nancial purposes. Financial transactions are always processed within
a business unit.
39
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
This gure illustrates the enterprise conguration that results from the analysis of InFusion Corporation.
InFusion
Corporation
Extensions for
Localization
Support
- UAE
- Saudi Arabia
US UK France
Tax Reporting Tax Reporting Tax Reporting
Unit Unit Unit
Legal Legal Legal
Entity Entity Entity
Legislative Legislative Legislative
Data Group Data Group Data Group
Divisions
Managing multiple businesses requires that you segregate them by their strategic objectives and measure their results.
40
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Responsibility to reach objectives can be delegated along the management structure. Although related to your legal
structure, the business organizational hierarchies don't reect directly the legal structure of the enterprise. The
management entities and structure can include:
These organizations can be included in many alternative hierarchies and used for reporting, as long as they have
representation in the chart of accounts.
Divisions
A division refers to a business-oriented subdivision within an enterprise, in which each division organizes itself
dierently to deliver products and services or address dierent markets. A division can operate in one or more
countries, and can be many companies or parts of dierent companies that are represented by business units.
A division is a prot center or grouping of prot and cost centers, where the division manager is responsible for
achieving business goals including prots. A division can be responsible for a share of the company's existing product
lines or for a separate business. Managers of divisions may also have return on investment goals requiring tracking of
the assets and liabilities of the division. The division manager generally reports to a corporate executive.
By denition a division can be represented in the chart of accounts. Companies can use product lines, brands, or
geographies as their divisions: their choice represents the primary organizing principle of the enterprise.
Historically, divisions were implemented as a node in a hierarchy of segment values. For example, Oracle E-Business
Suite has only one balancing segment, and often the division and legal entity are combined into a single segment where
each value stands for both division and legal entity.
Overview
A legal entity is a recognized party with rights and responsibilities given by legislation.
Legal entities have the following rights and responsibilities to:
• Own property
• Trade
• Repay debt
• Account for themselves to regulators, taxation authorities, and owners according to rules specied in the
relevant legislation
Their rights and responsibilities may be enforced through the judicial system. Dene a legal entity for each registered
company or other entity recognized in law for which you want to record assets, liabilities, expenses and income, pay
transaction taxes, or perform intercompany trading.
41
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
A legal entity has responsibility for elements of your enterprise for the following reasons:
• Facilitating local compliance
• Minimizing the enterprise's tax liability
• Preparing for acquisitions or disposals of parts of the enterprise
• Isolating one area of the business from risks in another area. For example, your enterprise develops property
and also leases properties. You could operate the property development business as a separate legal entity to
limit risk to your leasing business.
Legal entities must comply with the regulations of jurisdictions, in which they register. Europe now allows for companies
to register in one member country and do business in all member countries, and the US allows for companies to register
in one state and do business in all states. To support local reporting requirements, legal reporting units are created and
registered.
You are required to publish specic and periodic disclosures of your legal entities' operations based on dierent
jurisdictions' requirements. Certain annual or more frequent accounting reports are referred to as statutory or external
reporting. These reports must be led with specied national and regulatory authorities. For example, in the United
States (US), your publicly owned entities (corporations) are required to le quarterly and annual reports, as well as other
periodic reports, with the Securities and Exchange Commission (SEC), which enforces statutory reporting requirements
for public corporations.
Individual entities privately held or held by public companies don't have to le separately. In other countries, your
individual entities do have to le in their own name, as well as at the public group level. Disclosure requirements are
diverse. For example, your local entities may have to le locally to comply with local regulations in a local currency, as
well as being included in your enterprise's reporting requirements in dierent currency.
A legal entity can represent all or part of your enterprise's management framework. For example, if you operate in a
large country such as the United Kingdom or Germany, you might incorporate each division in the country as a separate
legal entity. In a smaller country, for example Austria, you might use a single legal entity to host all of your business
operations across divisions.
42
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
by Country page, which contains a matrix of the countries that you identied, your enterprise, and the divisions that you
created. You select the check boxes where your enterprise and divisions intersect with the countries to identify the legal
entities that you want the application to create. The enterprise is included for situations where your enterprise operates
in a country, acts on behalf of several divisions within the enterprise, and is a legal employer in a country. If you select
the enterprise for a country, the application creates a country holding company.
The application automatically creates the legal entities that you select, and identies them as payroll statutory units and
legal employers. For each country that you indicated that your enterprise operates in, and for each country that you
created a location for, the application also automatically creates a legislative data group.
Any legal entities that you create automatically cannot be deleted from the Create Legal Entities page within the
Enterprise Structures Congurator. You must return to the Map Divisions by Country page and deselect the legal
entities that you no longer want.
Enterprise
InFusion Corporation
Division Division
InFusion Lighting InFusion Security
Japan US UK India
This table represents the selections that InFusion Corporation makes when specifying which legal entities to create on
the Map Divisions by Country page.
Japan No Yes No
US No Yes No
UK No No Yes
43
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
India No No Yes
Based on the selections made in the preceding table, the ESC creates the following four legal entities:
Related Topics
• Guidelines for Using Desktop Integrated Excel Workbooks
When your legal entities are trading with each other, represent them as legal entities and as customers and suppliers in
your customer and supplier registers. Use legal entity relationships to determine which transactions are intercompany
and require intercompany accounting. Your legal entities can be identied as legal employers and therefore, are
available for use in Human Capital Management (HCM) applications.
Several decisions you should consider when you create legal entities.
44
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
In another example, if you revalued your inventory in a warehouse to account for raw material price increases, the
revaluation and revaluation reserves must be reected in your legal entity's accounts. In Oracle Fusion Applications,
your inventory within an inventory organization is managed by a single business unit and belongs to one legal entity.
45
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
in Europe, you might dene balancing segment values and map them to legal reporting units. You can represent a legal
entity with more than one balancing segment value. Do not use a single balancing segment value to represent more
than one legal entity.
In Oracle Fusion General Ledger, there are three balancing segments. You can use separate balancing segments to
represent your divisions or strategic business units to enable management reporting at the balance sheet level for each.
This solution is used to empower your business unit and divisional managers to track and assume responsibility for
their asset utilization or return on investment. Using multiple balancing segments is also useful when you know at the
time of implementation that you're disposing of a part of a legal entity and want to isolate the assets and liabilities for
that entity.
Implementing multiple balancing segments requires every journal entry that isn't balanced by division or business unit,
to generate balancing lines. You can't change to multiple balancing segments after you begin using the ledger because
your historical data isn't balanced by the new balancing segments. Restating historical data must be done at that point.
If your enterprise regularly spins o businesses or holds managers accountable for utilization of assets, identify the
business with a balancing segment value. If you account for each legal entity in a separate ledger, no requirement exists
to identify the legal entity with a balancing segment value.
While transactions that cross balancing segments don't necessarily cross legal entity boundaries, all transactions that
cross legal entity boundaries must cross balancing segments. If you make an acquisition or are preparing to dispose of
a portion of your enterprise, you may want to account for that part of the enterprise in its own balancing segment even
if the portion isn't a separate legal entity. If you don't map legal entities sharing the same ledger to balancing segments,
you can't distinguish them using intercompany functionality or track individual equity.
Tip: In the Oracle Fusion Supply Chain applications, you can model intercompany relationships using
business units, from which legal entities are derived.
Legal Entity and Its Relationship to Worker Assignments and Legal Employer
Legal entities that employ people are called legal employers in the Oracle Fusion Legal Entity Congurator. You must
enter legal employers on worker assignments in Oracle Fusion HCM.
46
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Business Units
A business unit is a unit of an enterprise that performs one or many business functions that can be rolled up in a
management hierarchy. A business unit can process transactions on behalf of many legal entities. Normally, it has a
manager, strategic objectives, a level of autonomy, and responsibility for its prot and loss. Roll business units up into
divisions if you structure your chart of accounts with this type of hierarchy.
In Oracle Fusion Applications you do the following:
• Assign your business units to one primary ledger. For example, if a business unit is processing payables
invoices, then it must post to a particular ledger. This assignment is required for your business units with
business functions that produce nancial transactions.
• Use a business unit as a securing mechanism for transactions. For example, if you run your export business
separately from your domestic sales business, then secure the export business data to prevent access by the
domestic sales employees. To accomplish this security, set up the export business and domestic sales business
as two separate business units.
The Oracle Fusion Applications business unit model provides the following advantages:
• Enables exible implementation
• Provides consistent entity that controls and reports on transactions
• Shares sets of reference data across applications
Business units process transactions using reference data sets that reect your business rules and policies and can dier
from country to country. With Oracle Fusion Application functionality, you can share reference data, such as payment
terms and transaction types, across business units, or you can have each business unit manage its own set depending
on the level at which you want to enforce common policies.
47
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
be assigned to users manually using the Security Console, or automatically using provisioning rules. Business Units can
be assigned to users using the Manage Data Access for Users task found in Setup and Maintenance.
• Country
• Country and Division
• Country and business function
• Division
• Division and legal entity
• Division and business function
• Business function
• Legal entity
• Business function and legal entity
Select the option that best meets your business requirements, but consider the following:
• If you use Oracle Fusion Financials, the legal entity option is recommended because of the manner in which
nancial transactions are processed.
• The business unit level that you select determines how the application automatically creates reference data
sets.
After you select a business unit level, the application generates a list of business units, and you select the ones you
want the application to create. If you select a level that has two components, such as country and division, then
the application displays a table listing both components. You select the check boxes at the intersections of the two
components.
The business units listed by the application are suggestions only, and are meant to simplify the process to create
business units. You aren't required to select all of the business units suggested. When you navigate to the next page in
the ESC guided ow, the Manage Business Units page, you can't delete any of the business units created automatically.
You must return to the Create Business Units page and deselect any business units that you no longer want.
48
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Enterprise
InFusion Corporation
Division Division
InFusion Lighting InFusion Security
The following table lists the options for business unit levels and the resulting business units that the application
suggests for InFusion Corporation.
Country • US
• UK
• Japan
• India
49
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Sales: India
50
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Your enterprise can determine that certain aspects of your corporate policy can aect all business units. The remaining
aspects are at the discretion of the business unit manager to implement. This allows your enterprise to balance
autonomy and control for each business unit. For example, your enterprise holds business unit managers accountable
for their prot and loss, but manages working capital requirements at a corporate level. In such a case, you can let
managers dene their own sales methods, but dene payment terms centrally. In this example:
• Each business unit has its own reference data set for sales methods.
• One central reference data set for payment terms is assigned to all business units.
The reference data sharing is especially valuable for lowering the cost of seing up new business units. For example,
your enterprise operates in the hospitality industry. You are adding a new business unit to track your new spa services.
The hospitality divisional reference data set can be assigned to the new business unit to quickly set up data for this
entity component. You can establish other business unit reference data in a business unit-specic reference data set as
needed.
• Assignment to one set only, no common values allowed. This method is the simplest form of sharing reference
data that allows assigning a reference data object instance to one and only one set. For example, Asset Prorate
Conventions are dened and assigned to only one reference data set. This set can be shared across multiple
asset books, but all the values are contained only in this one set.
• Assignment to one set only, with common values. This method is the most commonly used method of sharing
reference data that allows dening reference data object instance across all sets. For example, Receivables
Transaction Types are assigned to a common set that's available to all the business units. You need not
explicitly assign the transaction types to each business unit. In addition, you can assign a business unit-specic
set of transaction types. At transaction entry, the list of values for transaction types includes the following:
• Assignment to multiple sets, no common values allowed. The method of sharing reference data that allows
a reference data object instance to be assigned to multiple sets. For instance, Payables Payment Terms use
this method. It means that each payment term can be assigned to one or more than one set. For example,
you assign the payment term Net 30 to several sets, but assign Net 15 to a set specic only to your business
unit. At transaction entry, the list of values for payment terms consists of only the set that's assigned to the
transaction's business unit.
Note: Oracle Fusion Applications contains a reference data set called Enterprise. Dene any reference data
that aects your entire enterprise in this set. Also update the data set going forward as you create new
reference data items.
51
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Other types of reference data can be specic to certain business units, so you can restrict the use of the data to those
business units. In this case, you can create sets specically for this type of data, and assign the sets to the business
units.
52
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Enterprise
InFusion Corporation
Division Division
InFusion Lighting InFusion Security
When deciding how to create business units, InFusion decides to create them using the country and business function
level. Therefore, they created the following business units:
• Sales_Japan
• Marketing_Japan
• Sales_US
• Sales_UK
• Marketing_India
• Sales_India
Because locations, departments, and grades are specic to each business unit, InFusion does not want to share these
types of reference data across business units. They create a reference data set for each business unit so that data
of those types can be set up separately. Because the jobs in the Sales business function are the same across many
locations, InFusion decides to create one additional set called Jobs. They override the set assignment for the Jobs
reference data group and assign it to the Jobs set. Based on these requirements, they create the following sets:
• Sales_Japan_Set
• Mktg_Japan_Set
• Sales_US_Set
• Sales_UK_Set
• Mktg_India_Set
• Sales_India_Set
• Grades_Set
53
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
The following table describes the default set assignment and the set assignment overrides for each business unit in
InFusion:
Sales_Japan Sales_ Japan_Set for grades, departments, Jobs set for jobs
and locations
Sales_India Sales_ India_Set for grades, departments, Jobs set for jobs
and locations
When seing up grades, departments, and locations for the business units, InFusion assigns the data to the default set
for each business unit. When seing up jobs, they assign the Jobs set and assign the Common Set to any jobs that may
be used throughout the entire organization.
When using grades, departments, and locations at the transaction level, users can select data from the set that
corresponds to the business unit they enter on the transaction, and any data assigned to the Common Set. For example,
for transactions for the Marketing_Japan business unit, grades, locations, and departments from the Mktg_Japan_Set is
available to select, as well as from the Common Set.
When using jobs at the transaction level, users can select jobs from the Jobs set and from the Common Set when they
enter a sales business unit on the transaction. For example, when a manager hires an employee for the Sales_India
business unit, the list of jobs is ltered to show jobs from the Jobs and Common sets.
The following gure illustrates what sets of jobs can be accessed when a manager creates an assignment for a worker.
54
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Common Set
The Common set is a predened set that enables you to share reference data across business units. When you select
set-enabled data at the transaction level, the list of values includes data in the:
• Common set
• Set associated with the data type for the business unit on the transaction
For example, when you create an assignment, the list of values for grades includes grade in the:
• Common set
• Set that is assigned to grades for the business unit in which you creating the assignment
55
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Positions oer a well-dened space independent of the person performing the job.
• Jobs are a space dened by the person.
• A job can be dened globally in the Common Set, whereas a position is dened within one business unit.
• You can update the job and department of a position at any time. For example, if you hire someone into a new
role and want to transfer the position to another department.
During implementation, one of the earliest decisions is whether to use jobs or a combination of jobs and positions. The
determinants for this decision are:
Mining Positions
Utilities Positions
Manufacturing Positions
Construction Jobs
Information Jobs
56
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Management of People
Consider the following scenarios how industries manage their employee turnover:
• Scenario 1: Replace employees by rehiring to the same role.
• Scenario 2: Replace headcount but the manager uses the headcount in a dierent job.
• Scenario 3: Rehire employees to the same position, but the manager requests reallocation of budget to a
dierent post.
The following table displays suggestions of what the industry should use, either jobs or positions, in these three
scenarios:
57
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Related Topics
• How Grades and Grade Rates Work with Jobs, Positions, Assignments, Compensation, and Payroll
Examples of Positions
Positions are typically used by industries that use detailed approval rules, which perform detailed budgeting and
maintain headcounts, or have high turnover rates.
Retail Industry
ABC Corporation has high turnovers. It loses approximately 5% of its cashiers monthly. The job of the cashier includes
three positions: front line cashier, service desk cashier, and layaway cashier. Each job is cross-trained to take over
another cashier's position. When one cashier leaves from any of the positions, another existing cashier from the
front line, service desk or layaway can assist where needed. But to ensure short lines and customer satisfaction, ABC
Corporation must replace each cashier lost to turnover. Since turnover is high in retail it's beer for this industry to use
positions.
Also, an added advantage to using Positions is when you hire somebody new, many of the aributes are inherited from
the position. This speeds up the hiring process.
58
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Store Manager
Phil Jones
Assistant Store
Manager
Anita Camp
Cash Supervisor
Currently vacant
Service Desk
Front Line Cashier Layaway Cashier
Cashier
10 positions 2 positions
3 positions
The hospital has a structured headcount and detailed budgeting. For example, a specic number of surgeons, nurses,
and interns of various types are needed. These positions must be lled in order for the hospital to run smoothly. Use
jobs and positions when you apply detailed headcount rules.
59
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Hospital
Licensed
Cardiac Neural Registered Cardiac Neural
Practical
Surgeon Surgeon Nurse Intern Intern
Nurse
Positions
General Nursing General
Surgeon Aide Intern
Examples of Jobs
Jobs are typically used without positions by service industries where exibility and organizational change are key
features.
Software Industry
For example, XYZ Corporation has a director over the departments for developers, quality assurance, and technical
writers.
In software industries, the organization is uid. Using jobs gives an enterprise the exibility to determine where to use
headcount, because the job only exists through the person performing it. In this example, when the three developers
leave XYZ Corporation, their jobs no longer exist, therefore the corporation has the exibility to move the headcount to
other areas.
60
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
XYZ Corporation
Technology
Department
Quality Assurance
Developer Technical Writer
Specialist
Job Titles
61
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
This gure illustrates how job type and job level provide further details for the HR Application Specialist job.
Job Attributes
HR Application
Consultant 4
Specialist
62
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
This gure illustrates how title and position number provide further details for the manager position.
Position Attributes
Position
Position Name Title
Number
Assistant
Manager Store 10050
Manager
63
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
For example, XYZ Corporation uses the same grades throughout the entire organization. Instead of dierent business
units seing up and using the same grades, XYZ Corporation decides to create a set called Grades, which contains the
grades. All business units in the organization have the Grades set so that the grades can be shared and used.
Note: For specic information about conguring reference data sharing for a particular object or product,
refer to the relevant product documentation.
64
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Partitioning
Partitioning reference data and creating data sets provide you the exibility to handle the reference data to fulll your
business requirements. You can share modular information and data processing options among business units with
ease. You can create separate sets and subsets for each business unit. Alternatively, you can create common sets or
subsets to enable sharing reference data between several business units, without duplicating the reference data.
The following gure illustrates the reference data sharing method. The user can access the data assigned to a specic
set in a particular business unit, as well as access the data assigned to the common set.
has
access to ...
Common Set
UK
Business Unit
UK
Location Set
65
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Related Topics
• Dene Default Reference Data Sets
Your enterprise can determine that certain aspects of your corporate policy can aect all business units. The remaining
aspects are at the discretion of the business unit manager to implement. This allows your enterprise to balance
autonomy and control for each business unit. For example, your enterprise holds business unit managers accountable
for their prot and loss, but manages working capital requirements at a corporate level. In such a case, you can let
managers dene their own sales methods, but dene payment terms centrally. In this example:
• Each business unit has its own reference data set for sales methods.
• One central reference data set for payment terms is assigned to all business units.
The reference data sharing is especially valuable for lowering the cost of seing up new business units. For example,
your enterprise operates in the hospitality industry. You are adding a new business unit to track your new spa services.
The hospitality divisional reference data set can be assigned to the new business unit to quickly set up data for this
entity component. You can establish other business unit reference data in a business unit-specic reference data set as
needed.
• Assignment to one set only, no common values allowed. This method is the simplest form of sharing reference
data that allows assigning a reference data object instance to one and only one set. For example, Asset Prorate
Conventions are dened and assigned to only one reference data set. This set can be shared across multiple
asset books, but all the values are contained only in this one set.
• Assignment to one set only, with common values. This method is the most commonly used method of sharing
reference data that allows dening reference data object instance across all sets. For example, Receivables
Transaction Types are assigned to a common set that's available to all the business units. You need not
66
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
explicitly assign the transaction types to each business unit. In addition, you can assign a business unit-specic
set of transaction types. At transaction entry, the list of values for transaction types includes the following:
• Assignment to multiple sets, no common values allowed. The method of sharing reference data that allows
a reference data object instance to be assigned to multiple sets. For instance, Payables Payment Terms use
this method. It means that each payment term can be assigned to one or more than one set. For example,
you assign the payment term Net 30 to several sets, but assign Net 15 to a set specic only to your business
unit. At transaction entry, the list of values for payment terms consists of only the set that's assigned to the
transaction's business unit.
Note: Oracle Fusion Applications contains a reference data set called Enterprise. Dene any reference data
that aects your entire enterprise in this set. Also update the data set going forward as you create new
reference data items.
Determinant Types
The partitioned reference data is shared using a business context seing called the determinant type. A determinant
type is the point of reference used in the data assignment process. The following table lists the determinant types used
in the reference data assignment.
Asset Book Information about the acquisition, depreciation, and retirement of an asset that belongs to a
ledger or a business unit.
Cost Organization The organization used for cost accounting and reporting on various inventory and cost centers
within an enterprise.
Project Unit A logical organization within an enterprise that's responsible for enforcing consistent project
management practices.
67
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Determinant
The determinant (also called determinant value) is a value that corresponds to the selected determinant type. The
determinant is one of the criteria for selecting the appropriate reference data set.
Reference Groups
A transactional entity may have multiple reference entities (generally considered to be setup data). However, all
reference entities are treated alike because of similarity in implementing business policies and legal rules. Such
reference entities in your application are grouped into logical units called reference groups. For example, all tables
and views that dene Sales Order Type details might be a part of the same reference group. Reference groups are
predened in the reference groups table.
Items
If you share your items across warehouses or manufacturing facilities, you can access them through a common item
master. Congure one or multiple item masters for your enterprise, based your enterprise structure. A single item
master is recommended because it provides simpler and more ecient maintenance. However, in rare cases, it may be
benecial to keep multiple item masters. For example, if you acquire another enterprise and want to continue to operate
your lines of business separately, maintaining a second item master might be the best decision.
Suppliers Sites
You can approve particular suppliers to supply specied commodities and authorize your business units to buy from
those suppliers when the need arises. For example, you might be a household cleaning products manufacturer and
need dyes, plastics, and perfumes to make your products. You purchase from a central supplier 70% of your perfume
supplies with an additional supplier, in reserve, from whom you purchase the remaining 30%. At the same time, each of
your business units purchases plastics and dyes from the same supplier, but from dierent local supplier sites to save
transportation costs.
To implement business unit-specic supplier sites, Oracle Fusion Procurement supports a method for dening suppliers
sites as owned and managed by the business unit responsible for negotiating the supplier terms. Your other business
units that have a service provider relationship dened with your procurement business unit subscribe to the supplier
sites using the supplier site assignments feature. In addition, Procurement allows sharing of the following procurement
data objects across business units:
• Catalog content, such as agreements, smart forms, public shopping lists, and content zones
68
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Trading Community Model Customer Account Relationship Assignment to one set only, no common
values allowed
Trading Community Model Customer Account Site Assignment to one set only, no common
values allowed
Opportunity Management Sales Method Group Assignment to one set only, with common
values
Work Management Assessment Templates Assignment to one set only, with common
values
Enterprise Contracts Contract Types Assignment to one set only, with common
values
Common Components Activity Templates Assignment to one set only, with common
values
Receivables Auto Cash Rules Assignment to one set only, with common
values
69
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Advanced Collections Collections Setups Assignment to one set only, with common
values
Advanced Collections Dunning Plans Assignment to one set only, with common
values
70
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Project Billing Project and Contract Billing Assignment to multiple sets, no common
values allowed
Project Foundation Project Accounting Denition Assignment to one set only, no common
values allowed
Project Foundation Project Rates Assignment to one set only, with common
values
Order Management Hold Codes Assignment to one set only, with common
values
Order Management Orchestration Process Assignment to one set only, with common
values
71
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Assets Asset Queue Names Assignment to one set only, with common
values
72
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Dene Enterprises
An enterprise is a collection of legal entities sharing common control and management.
Enterprise Dened
When implementing Oracle Fusion Applications you operate within the context of an enterprise that has already been
created in the application for you. This is either a predened enterprise or an enterprise that has been created in the
application by a system administrator. An enterprise organization captures the name of the deploying enterprise and
the location of the headquarters. In Oracle Fusion Applications, an organization classied as an enterprise is dened
before dening any other organizations in the HCM Common Organization Model. All other organizations are dened
as belonging to an enterprise.
The locations that you create exist as separate structures that you can use for reporting purposes, and in rules that
determine employee eligibility for various types of compensation and benets. You enter information about a location
only once. Subsequently, when you set up other workforce structures you select the location from a list.
Location Sets
When you create a location, you must associate it with a set. Only those users who have access to the set's business unit
can access the location set and other associated workforce structure sets, such as those that contain departments and
jobs.
• You can also associate the location to the common set so that users across your enterprise can access the
location irrespective of their business unit.
• When users search for locations, they can see the locations that they have access to along with the locations in
the common set.
73
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
The following gure shows how locations sets restrict access to users.
has
access to ...
Common Set
UK
Business Unit
UK
Location Set
Related Topics
• Upload Workforce Structures Using a Spreadsheet
74
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
What happens if I select a geographic hierarchy node when I create or edit a location?
The calendar events that you created for the geographic node start to apply for the location and may impact the
availability of worker assignments at that location. You manage locations using the Manage Locations task in the
Workforce Structures work area.
The geographical hierarchy nodes available for selection on the Locations page display from a predened geographic
hierarchy.
Related Topics
• How an Individual's Schedule Is Determined
Dene Geographies
How You Set up Address Cleansing
Address cleansing validates, corrects, and standardizes address information that you enter in the application. Address
cleansing, unlike geography validation, validates both the geography aributes and the address line aributes.
To use the address cleansing functionality, you need to have license for the customer data quality application, because
the feature is delivered using data quality integration.
You can specify the real-time address cleansing level for each country by choosing either of these options:
Once you have enabled address cleansing for a country, a Verify Address icon appears at address entry points in the
application. Click the icon to perform address cleansing and receive a corrected, standardized address. If the application
doesn't nd a matching address, then an alert message is displayed.
75
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Geography Structure
Firstly, you need to create a geography structure for each country to dene which geography types are part of the
country structure, and how the geography types are hierarchically related within the country structure. For example,
you can create geography types called State, City, and Postal Code. Then you can rank the State geography type as the
highest level within the country, the City as the second level, and the Postal Code as the lowest level within the country
structure. Geography structure can be dened using the Manage Geographies task, or can be imported using tasks in
the Dene Geographies activity.
Geography Hierarchy
Once the geography structure is dened, the geographies for each geography type can be added to the hierarchy. For
example, in the hierarchy of United States you can create a geography called California using a State geography type.
As part of managing the geography hierarchy you can view, create, edit, and delete the geographies for each geography
type in the country structure. You can also add a primary and alternate name and code for each geography. A
geography hierarchy can be created using the Manage Geographies task, or can be imported using tasks in the Dene
Geographies activity.
Geography Validation
After dening the geography hierarchy, you need to specify the geography validations for the country. You can choose
which address style format you would like to use for the country, and for each selected address style format you can
map geography types to address aributes. You can also select which geography types to include in geography or tax
validation, and which geography types will display in a list of values during address entry in other user interfaces. The
geography validation level for the country, such as error or warning, can also be selected.
Geography Structures
This topic describes geography structures and the tasks you can perform using geography structures.
A geography structure is a hierarchical grouping of geography types for a country. The following table describes the
geography structure for the United States.
1 State
2 County
3 City
76
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
4 Postal Code
You can use the geography structure to relate geography types for a country and dene geography types for a country.
You can use a geography type that you create within the country structure for other country structures as well.
Geography Hierarchy
This topic describes geography hierarchy and various aspects of geography hierarchy.
Geography hierarchy is a data model that creates conceptual parent-child relationships between geographies. At
the highest level of the geography hierarchy is country, which is the parent, and the hierarchy contains several child
geographies. The following table shows sample parent-child relationships in a geography.
94065 Child
77
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
When you enter just 94065, the application determines that the postal code is in California and the corresponding city is
Redwood City.
The application uses geography hierarchy information to facilitate business processes that rely on geography
information, such as, tax calculation, order sourcing rules, and sales territory denition. The geography hierarchy
information is centrally located and shared among other application oerings.
Geography Validation
Geography validation determines the geography mapping and validation for a country's address styles, as well as the
overall geography validation control for a country.
The No Styles Format address style format is the default address style format for a country. By dening the mapping
and validation for this format you will ensure that validations can be performed for any address in the country. After the
No Styles Format is dened you can set up additional mapping for specic address styles.
For each address style format, you can dene the following:
• Map to aribute
• Enable list of values
• Tax validation
• Geography validation
• Geography validation control
Aribute Mapping
For every address style format, you can map each geography type to an address aribute. For example, you can
map the State geography type to the State address aribute for the United States, or map the State geography type
to the County address aribute for the United Kingdom. The geography types that appear are based on how the
country structure is dened. The list of address aributes that appear are based on address formats delivered with the
application, or your customer dened address formats.
Note: You only need to map geography types that you want to use for geography or tax validation purposes.
78
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Tax Validation
You can also specify whether a geography type will be included in tax validation. For example, for the United States
North America address style format you specify that County, State, and City are used for tax validation. This will mean
that when a transaction involves an address with the North America address style, the address must have the correct
county, state, and city combination based on the geography hierarchy data, to be considered valid for tax calculation.
Geography Validation
You must set up geography validation for those geography elements that you plan to use in your sales territories.
Seing up validation also helps users ll in missing address information, and validate addresses during entry. For
example, you can have users select states or other address elements from lists to ensure accuracy during entry, and
you can have the application ll in missing values. For example, when the user enters a Postal Code, the application can
retrieve the city and state.
You can specify whether a geography type will be included in geography validation. For example, when the user enters
a United States address using the North America address style format, the address must have the correct country, state,
and postal code combination based on geography hierarchy data to be considered geographically valid.
If an address element is mapped to a geography type, but not selected for geography validation usage, then during
address entry suggested values are provided for the address element, but the address element isn't be validated.
You need to verify that the default mapping between Geography Type and Map to Aribute is valid in the Geography
Mapping and Validation region and update it if required when you dene geography validation. Oracle recommends
that you use the following valid mapping for the countries that GBG | Loqate supports:
79
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Department • County
• Municipality • City
• Postal Code • Postal code
80
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
81
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
82
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
83
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• District • State
• Subdistrict • County
• City • City
• Postal Code • Postal code
84
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
85
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Muhafazah • State
• District • County
• City • City
86
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
87
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Postal Code
88
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• City • City
• Postal Code • Postal code
Note: For either the tax or geography validation, don't skip more than one consecutive level unless you're
certain that the selected geography types can uniquely identify geographies. For example, the United States
country structure is: State, County, City, and Postal Code, and you want to select just State and Postal Code
for geography or tax validation. However, for the combination of California and 94065, the city can be either
Redwood Shores or Redwood City. In this case, you should also select at least the City geography type for
geography or tax validation.
• Error - only completely valid addresses can be saved, with all mandatory address elements entered.
• No Validation - all addresses can be saved including incomplete and invalid addresses.
Regardless of the result of validation, the validation process will try to map any address aribute to a geography of
the country, and store any mapping it could establish based on the available data. This is called Geography Name
Referencing and it's executed as part of validation. The result of this referencing is used in several business processes
in the application to map an address to a specic geography or zone.
The Geography Dimension value in territories is derived from sell-to addresses of sales accounts. To use geography
dimensions in territories, you must validate the geography elements in the addresses, such as state, city, and postal
code. You can validate the address by enabling geography validation for each country using the Manage Geographies
task. Perform the following in the Manage Geographies task:
• Enable at least one level in the geography hierarchy for geography validation.
89
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Enable geography validation for all geography levels that you intend to use for territory denition for each
country.
• If needed, enable a list of values containing specic geography elements. This will help users search and select
appropriate geography values during addresses entry and eliminate all possibilities of wrong address entry.
You can set geography validation control to Error in the Manage Geography Validation page. This ensures that users
can only use valid geography elements in addresses.
Note: If you have already created addresses before seing up geography validation for a country, you must
enable geography validation and then execute the Run Maintain Geography Name Referencing task for that
country. This validates all your geography elements.
For more information, see the Importing Geographies chapter in the Oracle CX Understanding File-Based Data Import
and Export for CX Sales and Service guide.
90
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
The following table lists the object entity, the interface table, the destination tables, and the resulting application object.
Related Topics
• Overview of Implementing Customer Data Management
• Import Your Geography Data
• Import Your Territory Geographies Data
91
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
The validation information includes the navigation path to the task where you can dene values in Oracle Application
Cloud. For example, if you have values in your data that correlate to a choice list in Oracle Application Cloud, then the
validation information provides the task name where you can dene your values. For additional information, such as a
list of reference guide le names and locations, see the topic How Country Structure Import Objects Work Together.
Congurable Aributes
Here is how you can congure the objects to import your legacy or source data:
• Use the Application Composer to design your object model extensions and to generate the required artifacts to
register your extensions.
• Make the artifacts available for importing the object.
92
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
You can map these congurable aributes to your source le data. You can use the same source le to import both the
congurable aributes and the standard import object aributes.
You can also access these tasks from the Data Import and Export functional area of the Sales oering.
You must have the Master Data Management Administrator job role to access and submit the import activities for
country structures.
Related Topics
• How File-Based Data Import Works
• About File-Based Import Documentation
When updating an existing country structure, you must provide the parent reference information of the existing
country structure. This reference information connects the imported geography structure to the existing one. Use the
ImpGeoStructureLevel target import object to create and update country structure information.
93
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Aribute descriptions
• Default values
• Validations for the aributes
Review the validation for each aribute to know if you need to do any setup tasks.
◦ Oering: Sales
◦ Functional Area: Data Import and Export
◦ Task: Manage File Import Mappings
2. Dene the mapping when creating an import activity in the Setup and Maintenance work area:
◦ Oering: Sales
◦ Functional Area: Data Import and Export
◦ Task: Manage File Import Activities
Note: If any of your source aributes doesn't have a corresponding target object aribute, then you can
extend the Country Structure object. Review the Application Composer Extensibility features for the Country
Structure object for more information.
For detailed information about importing geographies using le-based import, refer to Document No. 1481758.1,
Importing Master Reference Geography Data, on the Oracle Support site.
94
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Related Topics
• How File-Based Data Import Works
• About File-Based Import Documentation
• How You Import Country Structures
Note: CX Sales and B2B Service ships with third-party master geography data for multiple countries. You
can import geography data using the Manage Geographies task. Search for the country, and select Import
Geography Data from the Actions menu. If the licensed data isn't available for a country, then the Import
Geography Data action is disabled. For more information, see the procedure Replacing Existing Master
Geography Data with Revised Oracle-Licensed Geography Data.
95
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Values that populate aributes by default when you don't provide values
• Validation information for each aribute
The validation information includes the navigation path to the task where you can dene values in Oracle Application
Cloud. For example, if you have values in your data that correlate to a choice list in Oracle Application Cloud, then the
validation information provides the task name where you can dene your values. For additional information, such as a
list of reference guide le names and locations, see the topic How Geography Import Objects Work Together.
Congurable Aributes
Here is how you can congure the objects to import your legacy or source data:
• Use the Application Composer to design your object model extensions and to generate the required artifacts to
register your extensions.
• Make the artifacts available for importing the object.
You can map these congurable aributes to your source le data. You can use the same source le to import both the
congurable aributes and the standard import object aributes.
You can also access these tasks from the Data Import and Export functional area of the Sales oering.
You submit le import activities for each import object. When you're creating a new geography, you use the Geography
object to import your data. You must have the Master Data Management Administrator job role to access and submit
the import activities for geographies.
When importing geography information, you must provide the parent reference information for all parent levels for the
entity.
Related Topics
• How File-Based Data Import Works
• About File-Based Import Documentation
96
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
The target import objects in the Geography import object contain information about the geography hierarchy. When
updating an existing geography, you must provide the parent reference information of the existing geography.
Use the ImpGeography target import object to create and update geography information.
Note: Before you import geography data for a country, you must dene the country's geography structure.
Review the validation for each aribute to know if you need to do any setup tasks.
97
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Note: If any of your source aributes doesn't have a corresponding target object aribute, then you can
extend the Geography object. Review the Application Composer Extensibility features for the Geography
object for more information.
Related Topics
• How File-Based Data Import Works
• About File-Based Import Documentation
What le type are you using for your source data? Text le
Where are you uploading your source data le from? Your desktop
Which elds are you importing into the application? All, except for the RecordTypeCode eld
98
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
1 (Country) US 1 NA
2 (State) CA 11 1
99
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Field Value
Object Geography
Note: Ensure that the le type that you select in the Create Import Activity: Set Up page matches
the le type of the source data le.
4. Click Next.
5. In the Create Import Activity: Map Fields page, map each eld from your source le to the database object and
aribute, as shown in the following table.
Primary Geography Primary Geography United States Imp Geography Primary Geography
Name Name Name
100
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
If you don't want to import a column in the text le, then you can select Ignore.
Note: If you can't map the elds from your source le to the relevant target object, then see the
import object spreadsheets.
6. Click Next.
7. In the Create Import Activity: Create Schedule page, select Immediate in the Schedule eld so that the import
will start as soon as you activate it.
Instead of immediately importing the data, you can choose a date and time to start the import. You can also
specify whether the import will be repeated and the frequency of the repeated import.
8. Click Next.
1. In the Create Import Activity: Review and Activate page, verify your import details in the Import Details, File
Details, Import Options, and Schedule sections. Update the import details if required by navigating to the
previous screens using the Back link.
2. Conrm your import details, and click Activate to submit the import.
After the import activity has nished, the Status eld value changes to Completed.
101
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Related Topics
• Manage Territory Geographies
1. County
2. Post Town
102
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Which address style format will you use when mapping geography The default address style format, called the No Styles Format.
validations?
1. On the Manage Geographies page, enter GB in the Code eld. Click Search.
2. On the Manage Geographies page, click Structure Dened.
3. On the Manage Geography Structure page, click the Create buon next to the Copy Country Structure From
eld.
4. In the Geography Structure section, select the County list item in the Add Geography Type eld.
5. Click Add.
6. Select the Post Town list item in the Add Geography Type eld.
7. Click Add.
1. On the Manage Geographies page, enter GB in the Code eld. Click Search.
2. On the Manage Geographies page, click Hierarchy Dened.
3. In the Geography Hierarchy section, click United Kingdom to highlight the table row, and click Create.
4. In the Create County page, Primary and Alternate Names section, enter Berkshire in the Name eld.
5. Click Save and Close.
6. In the Geography Hierarchy section, click Berkshire to highlight the table row, and click Create.
7. In the Create Post Town page, Primary and Alternate Names section, enter Reading in the Name eld.
8. Click Save and Close.
103
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
How can I add a geography that's at a lower level to any geography in a geography
hierarchy?
Select the geography that you want to create a geography at lower level, and then click the Create icon. This lets you
create a geography for a geography type that's one level lower to the geography type you selected. The structure of the
country's geography types are dened in the Manage Geography Structure page.
104
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Jurisdictions
Jurisdiction is a physical territory such as a group of countries, country, state, county, or parish where a particular piece
of legislation applies. French Labor Law, Singapore Transactions Tax Law, and US Income Tax Laws are examples of
particular legislation that apply to legal entities operating in dierent countries' jurisdictions. Judicial authority may be
exercised within a jurisdiction.
Types of jurisdictions are:
• Identifying Jurisdiction
• Income Tax Jurisdiction
• Transaction Tax Jurisdiction
Identifying Jurisdiction
For each legal entity, select an identifying jurisdiction. An identifying jurisdiction is your rst jurisdiction you must
register with to be allowed to do business in a country. If there's more than one jurisdiction that a legal entity must
register with to commence business, select one as the identifying jurisdiction. Typically the identifying jurisdiction is the
one you use to uniquely identify your legal entity.
Income tax jurisdictions and transaction tax jurisdictions don't represent the same jurisdiction. Although in some
countries, the two jurisdictions are dened at the same geopolitical level, such as a country, and share the same legal
authority, they're two distinct jurisdictions.
Legal Authorities
A legal authority is a government or legal body that's charged with powers to make laws, levy and collect fees and taxes,
and remit nancial appropriations for a given jurisdiction.
For example, the Internal Revenue Service is the authority for enforcing income tax laws in United States. In some
countries, such as India and Brazil, you're required to print legal authority information on your tax reports. Legal
authorities are dened in the Oracle Fusion Legal Entity Congurator. Tax authorities are a subset of legal authorities
and are dened using the same setup ow.
Legal authorities aren't mandatory in Oracle Fusion Human Capital Management (HCM), but are recommended and are
generally referenced on statutory reports.
105
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Legal Jurisdictions
Create a legal jurisdiction by following these steps:
1. Navigator > Setup and Maintenance > Manage Legal Jurisdictions > Go to Task.
2. Select Create.
3. Enter a unique Name, United States Income Tax.
4. Select a Territory, United States.
5. Select a Legislative Category, Income tax.
6. Select Identifying, Yes. Identifying indicates the rst jurisdiction a legal entity must register with to do business
in a country.
7. Enter a Start Date if desired. You can also add an End Date to indicate a date that the jurisdiction may no
longer be used.
8. Select a Legal Entity Registration Code, EIN or TIN.
9. Select a Legal Reporting Unit Registration Code, Legal Reporting Unit Registration Number.
10. Optionally enter one or more Legal Functions.
11. Save and Close.
Legal Authorities
Create a legal authority by following these steps:
1. Navigator > Setup and Maintenance >Manage Legal Authorities > Go to Task.
2. Enter the Name, California Franchise Tax Board.
3. Enter the Tax Authority Type, Reporting.
Note: Create an address for the legal authority.
4. Select Create.
5. The Site Number is automatically assigned.
6. Optionally enter a Mail Stop.
106
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Legal Entity
Create a legal entity by following these steps:
1. Navigator > Setup and Maintenance > Manage Legal Entity > Go to Task.
2. Accept the default Country, United States.
3. Enter Name, InFusion USA West.
4. Enter Legal Entity Identier, US0033.
5. Optionally enter Start Date. When the start date is blank the legal entity is eective from the creation date.
6. Optionally enter an End Date.
7. Optionally, if your legal entity should be registered to report payroll tax and social insurance, select the Payroll
statutory unit check box.
8. Optionally, if your legal entity has employees, select the Legal employer check box.
9. Optionally, if this legal entity is not a payroll statutory unit, select an existing payroll statutory unit to report
payroll tax and social instance on behalf of this legal entity.
10. Enter the Registration Information
11. Accept the default Identifying Jurisdiction, United States Income Tax.
12. Search for and select a Legal Address, 500 Oracle Parkway, Redwood Shores, CA 94065.
The legal address must have been entered previously using the Manage Legal Address task.
13. OK.
14. Optionally enter a Place of Registration.
15. Enter the EIN or TIN.
16. Enter the Legal Reporting Unit Registration Number.
107
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
108
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Overview
A legal entity is a recognized party with rights and responsibilities given by legislation.
Legal entities have the following rights and responsibilities to:
• Own property
• Trade
• Repay debt
• Account for themselves to regulators, taxation authorities, and owners according to rules specied in the
relevant legislation
Their rights and responsibilities may be enforced through the judicial system. Dene a legal entity for each registered
company or other entity recognized in law for which you want to record assets, liabilities, expenses and income, pay
transaction taxes, or perform intercompany trading.
A legal entity has responsibility for elements of your enterprise for the following reasons:
• Facilitating local compliance
• Minimizing the enterprise's tax liability
• Preparing for acquisitions or disposals of parts of the enterprise
• Isolating one area of the business from risks in another area. For example, your enterprise develops property
and also leases properties. You could operate the property development business as a separate legal entity to
limit risk to your leasing business.
Legal entities must comply with the regulations of jurisdictions, in which they register. Europe now allows for companies
to register in one member country and do business in all member countries, and the US allows for companies to register
in one state and do business in all states. To support local reporting requirements, legal reporting units are created and
registered.
You are required to publish specic and periodic disclosures of your legal entities' operations based on dierent
jurisdictions' requirements. Certain annual or more frequent accounting reports are referred to as statutory or external
reporting. These reports must be led with specied national and regulatory authorities. For example, in the United
States (US), your publicly owned entities (corporations) are required to le quarterly and annual reports, as well as other
periodic reports, with the Securities and Exchange Commission (SEC), which enforces statutory reporting requirements
for public corporations.
Individual entities privately held or held by public companies don't have to le separately. In other countries, your
individual entities do have to le in their own name, as well as at the public group level. Disclosure requirements are
diverse. For example, your local entities may have to le locally to comply with local regulations in a local currency, as
well as being included in your enterprise's reporting requirements in dierent currency.
109
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
A legal entity can represent all or part of your enterprise's management framework. For example, if you operate in a
large country such as the United Kingdom or Germany, you might incorporate each division in the country as a separate
legal entity. In a smaller country, for example Austria, you might use a single legal entity to host all of your business
operations across divisions.
• Simple Conguration
• Multiple Legal Employers and Tax Reporting Units
• One Payroll Statutory Unit and Two Tax Reporting Units
• One Payroll Statutory Unit with Several Tax Reporting Units
• Multiple Payroll Statutory Units with Several Tax Reporting Units
These models include a legislative data group (LDG) that isn't an organization classication and show how you can
partition payroll data by associating them with a payroll statutory unit
Simple Conguration
This is an example of a simple conguration without any tax reporting units. The enterprise has only one legal entity,
which is both a payroll statutory unit and a legal employer, and shares the same boundaries. In this type reporting can
be done only at a single level. Countries such as Saudi Arabia and the United Arab Emirates (UAE) might use this type of
model, as these countries report at the legal entity level.
110
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
This gure illustrates a simple conguration where the enterprise has only one legal entity, which is both a payroll
statutory unit and a legal employer.
InFusion Corporation
Enterprise
Division
PSU
Legal
Employer
The implication is that payroll statutory reporting boundaries vary from human resources (HR) management, and you
can categorize the balances separately as either a payroll statutory unit, legal employer, or a tax reporting unit.
This conguration is based on tax ling requirements, as some tax-related payments and reports are associated with a
higher level than employers. An example of a country that might use this model is the US
111
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
This gure illustrates an enterprise that has one payroll statutory unit and multiple legal employers and tax reporting
units.
InFusion Corporation
Enterprise
US Division
InFusion US
Legal Entity
USA Legislative
Data Group PSU
US LE 1 InFusion Inc
Legal Reporting Unit Legal Reporting Unit
Legal
Legal Employer
Employer
Tax Reporting
Tax Reporting
Unit
Unit
In this enterprise, legal entity is the highest level of aggregation for payroll calculations and reporting. Statutory
reporting boundaries are the same for both payroll and HR management. An example of a country that might use this
model is France.
112
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
This gure illustrates an example of an organization with one legal entity. The legal entity is both a legal employer and a
payroll statutory unit and that has two tax reporting units.
InFusion Corporation
Enterprise
Division
InFusion France
Legal Entity
France
Legislative Data PSU
Group
Legal
Employer
Using this model, you can't report on tax reporting unit balances within a legal employer, and categorize balances by
either or both organizations, as required. An example of a country that might use this model is India.
113
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
This gure illustrates an enterprise with one legal entity that's a payroll statutory unit and a legal employer. The tax
reporting units are independent from the legal employer.
InFusion Corporation
Enterprise
India Division
InFusion InFusion
Hyderabad Bangalore
Tax Reporting Tax Reporting
Unit Unit
Using this model, you can't report on tax reporting unit balances within a legal employer, and categorize balances by
either or both organizations, as required. An example of a country that might use this model is the United Kingdom
(UK).
114
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
This gure illustrates an enterprise with two legal entities, and legal employers and tax reporting units are independent
from each other.
InFusion Corporation
Enterprise
Division
Legislative
Data Group
Legal Entity Legal Entity
PSU PSU
Legal
Employer
Related Topics
• Legislative Data Groups
115
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
How Legal Employers Work with Payroll Statutory Units and Tax
Reporting Units
You can designate legal entities as legal employers and payroll statutory units, which makes them available for use in
Oracle Fusion Human Capital Management (HCM). You can have only one legal entity that's also a payroll statutory unit
and legal employer, or multiple legal entities, payroll statutory units and legal employers.
Payroll statutory units and tax reporting units share a parent child relationship with the payroll statutory unit being a
parent of a tax reporting unit.
For example, if a single tax reporting unit is linked to a payroll statutory unit and two legal employers are associated
with this payroll statutory unit, then both legal employers are associated with the tax reporting unit. Use the Manage
Legal Reporting Unit HCM Information task to designate an existing legal reporting unit as a tax reporting unit. You
need to select a parent payroll statutory unit when you create a legal reporting unit belonging to a legal employer (that
isn't a payroll statutory unit as well). Next, you need to designate the legal reporting unit as a tax reporting unit and
select the legal employer.
Related Topics
• What's a tax reporting unit
116
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
company enterprise, then you register a payroll statutory unit in each country where you employ and pay people.
You can optionally register a consolidated payroll statutory unit to pay and report on workers across multiple legal
employers within the same country. You associate a legislative data group with a payroll statutory unit to provide the
correct payroll information for workers.
• First parties
• Third parties
• Tax authorities
First Parties
Set up tax proles for your rst-party legal entities, legal reporting units, and business units.
First-party legal entities identify your organization to the relevant legal authorities, for example, a national or
international headquarters. Legal entities let you model your external relationships to legal authorities more accurately.
The relationships between rst-party legal entities and the relevant tax authorities normally control the setup of the
transaction taxes required by your business. In most circumstances, the tax setup is used and maintained based on
the conguration of the legal entity. Enter the default information, party scal classications, tax reporting codes, and
conguration options for your legal entities. You can also specify if you're using the tax services of an external service
provider for tax calculation.
First-party legal reporting units identify each oce, service center, warehouse, and any other location within the
organization with a tax requirement. A legal reporting unit tax prole is automatically created for the headquarter legal
entity. Set up additional legal reporting unit tax proles for those needed for tax purposes. For legal reporting units,
enter the default information, tax registrations, party scal classications, and tax reporting codes. Also, dene tax
reporting details for your VAT and global tax reporting needs for tax registrations of tax regimes that allow this setup.
Business units organize your company data according to your internal accounting, nancial monitoring, and reporting
requirements. To help you manage the tax needs of your business units, you can use the business unit tax prole in
either of two ways:
• Indicate that business unit tax setup is used and maintained based on the conguration of the associated legal
entity at transaction time. The tax setup of the associated legal entity setup is either specic to the legal entity
or shared across legal entities using the Global Conguration Owner setup.
• Indicate that tax setup is used and maintained by a specic business unit. Create conguration options for the
business unit to indicate that the subscribed tax content is used for the transactions created for the business
unit.
For business units that maintain their own setup, enter the default information, tax reporting codes, conguration
options, and service providers as required.
117
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Third Parties
Set up third-party tax proles for parties with the usage of customer, supplier, and their sites. Enter the default
information, tax registrations, party scal classications, and reporting codes required for your third parties or third-
party sites. You can set up tax exemptions for your customers and customer sites.
Banks are also considered third parties. When a bank is created, the tax registration number specied on the bank
record is added to the party tax prole record in Oracle Fusion Tax. You can't modify the party tax prole for a bank as
it's view only. You can only modify the bank record.
Note: You don't need to set up party tax proles for third parties. Taxes are still calculated on transactions for
third parties that don't have tax proles.
Tax Authorities
Set up a tax authority party tax prole using the Legal Authorities setup task. The tax authority party tax prole
identies a tax authority party as a collecting authority or a reporting authority or both. A collecting tax authority
manages the administration of tax remiances. A reporting tax authority receives and processes all company
transaction tax reports.
The collecting and reporting tax authorities appear in the corresponding list of values on all applicable Oracle Fusion
Tax pages. All tax authorities are available in the list of values as an issuing tax authority.
Related Topics
• Considerations for Specifying Third-Party Tax Prole Options
• When does a party tax prole get created for a third party
• Defaults and controls: Applicable to legal entities and legal reporting units. Business units that use their own tax
setup don't have defaults and controls.
• Tax registrations: Applicable to legal reporting units.
• Party scal classications: Applicable to legal entities and legal reporting units.
• Tax reporting codes: Applicable to legal entities, legal reporting units, and business units who don't use the tax
setup of the legal entity.
• Conguration options: Applicable to legal entities and business units who don't use the tax setup of the legal
entity.
• Service subscriptions: Applicable to legal entities and business units who don't use the tax setup of the legal
entity.
118
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Option Description
• Header: Applies rounding to calculated tax amounts once for each tax rate per invoice.
• Line: Applies rounding to the calculated tax amount on each invoice line.
The rule that denes how the rounding must be performed on a value involved in a taxable
Rounding Rule transaction. For example, up to the next highest value, down to the next lowest value, or
nearest.
Note: If you dened a rounding precedence hierarchy in the conguration owner
tax option seings for the combination of conguration owner and event class,
Oracle Fusion Tax considers the rounding details in the applicable tax prole.
This rst party intends to send or receive invoices with invoice line amount inclusive of the tax
Set Invoice Values as Tax Inclusive amount.
Note: This option overrides the tax inclusive handling seing at the tax level, but
not at the tax rate level.
Tax Registrations
Set up a separate tax registration to represent each distinct registration requirement for a rst-party legal reporting unit.
Oracle Fusion Tax uses tax registrations in tax determination and tax reporting. If your rst party has more than one tax
registration in the same tax regime, then the application considers the tax registration in the order: tax jurisdiction; tax;
tax regime.
You must enable the Use tax reporting conguration option on the rst-party tax regime to allow entry of global tax
reporting conguration details during tax registration setup for legal reporting units for these tax regimes.
119
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Conguration Options
The legal entities and business units in your organization are each subject to specic sets of tax regulations as
designated by the tax authorities where you do business. Use conguration options to associate legal entities and
business units with their applicable tax regimes. You can set up tax conguration options when you create a tax regime
or when you create a party tax prole. Both setup ows display and maintain the same party and tax regime denitions.
Service Subscriptions
You can use a service subscription to reference a specic transaction tax oering or oerings provided by an external
tax partner. The transaction tax oering provided by an external tax partner can be related to content, calculation
services, or both. Oracle Fusion Tax supports the use of transaction tax oerings provided by external tax partners
for transaction tax calculation processing. Depending on the specic depth and scope of an individual tax partner's
oerings, you can use either Oracle Fusion Tax or a Partner Tax Application to perform the transaction tax calculation.
Related Topics
• Tax Registrations
• Tax Conguration Options
• Considerations for Seing Tax Reporting Conguration Controls for VAT
• Party Information
You can also create one manually. Just use the Create Legal Entity Tax Prole page. You can also edit the
autogenerated tax prole with relevant tax information.
120
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
location, such as sales oces. For example, set up legal reporting units to represent your company and its oces for tax
reporting.
Caution: Once you begin using your chart of accounts, making changes to its fundamental aributes is
neither recommended nor supported. This includes your chart of account segments, including the segment
labels as well as other characteristics of those segments.
The chart of accounts facilitates aggregating data from dierent operations, from within an operation, and from
dierent business ows, thus enabling the organization to report using consistent denitions to their stakeholders in
compliance with legislative and corporate reporting standards and aiding in management decisions.
Best practices include starting the design from external and management reporting requirements and making decisions
about data storage in the general ledger, including thick versus thin general ledger concepts.
121
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• A general ledger used in conjunction with an enterprise protability management product, which has data
standardized from each operation, is a thin general ledger. Use this variation if your solution is project-based,
and Oracle Fusion Project Portfolio Management is implemented. More detailed reporting can be obtained
from the Projects system. In the thin general ledger, business units, divisions, and individual departments aren't
represented in the chart of accounts.
• A thick general ledger:
A thick general ledger is designed to serve as a repository of management data for a certain level of
management. For example, a general ledger designed to provide management data to supervise operations,
such as daily sales, without invoice details.
• A primary and secondary ledger, with one thick general ledger and the other a thin general ledger, provides
dual representation to meet reporting requirements.
• Has natural accounts at a statutory reporting level, for example, payroll expense, rent, property taxes, and
utilities.
• Has cost centers at the functional expense level, such as Research and Development or Selling, General, and
Administrative, rather than at department or analytic levels.
• Omits business unit, division, and product detail.
122
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
One example of an industry that frequently uses a thin general ledger is retail. In a retail organization, the general ledger
tracks overall sales numbers by region. A retail point of sales product tracks sales and inventory by store, product,
supplier, markup, and other retail sales measures.
A thick general ledger had details for cost of goods sold and inventory balances and track property plant and equipment
at a granular level. Cost centers represent functional expenses, but also roll up to departmental or other expense
analysis levels. Using product and location codes in optional segments can provide reporting by line of business.
Posting daily, at the individual transaction level, can maximize the data stored in the general ledger.
One example of an industry that frequently uses a thick general ledger is electronic manufacturers. Detail on the
revenue line is tagged by sales channel. Product is structured dierently to provide detail on the cost of goods sold
line, including your bill of materials costs. The general ledger is used to compare and contrast both revenue and cost of
goods sold for margin analysis.
Other Considerations
Consider implementing a thick ledger if there are business requirements to do any of the following:
• Track entered currency balances at the level of an operational dimension or segment of your chart of accounts,
such as by department or cost center
• Generate nancial allocations at the level of an operational dimension or segment
• Report using multiple layered and versions of hierarchies of the operational dimension or segment from your
general ledger
Consider implementing a thin ledger in addition to a thick ledger, if there are additional requirements for:
• Minimal disclosure to the authorities in addition to the requirements previously listed. For example, in some
European countries, scal authorities examine ledgers at the detailed account level.
• Fiscal only adjustments, allocations, and revaluations, which don't impact the thick general ledger.
The important consideration in determining if a thick ledger is the primary or secondary ledger is your reporting needs.
Other considerations include how the values for an operational dimension or segment are derived and the amount of
resources used in reconciling your dierent ledgers. If values for an operational dimension or segment are entered by
the user, then a thick primary ledger is the beer choice.
However, if values for the operational segment are automatically derived from aributes on transactions in your
subledger accounting rules, then use a thick secondary ledger. This decision aects the amount of:
• Storage and maintenance needed for both the general ledger and subledger accounting entries
123
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
◦ Minimum demand on storage, maintenance, and system resources with the use of a thin ledger
◦ Greater demand on storage, maintenance, and system resources with the use of a thick ledger
◦ Greatest demand on storage, maintenance and system resources with the use of both thick and thin
ledgers
Note: Generally speaking, there is a trade-o between the volume of journals and balances created
and maintained versus system resource demands. Actual performance depends on a wide range
of factors including hardware and network considerations, transaction volume, and data retention
policies.
Summary
The factors you should consider in your decision to use a thick or thin general ledger for your organization, are your:
124
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
to use in general ledger processing, such as intercompany balancing or retained earning summarization. Segments are
secured by security rules and accounts are secured by cross validation rules.
Chart of Chart of
Accounts Accounts
Strucutre Instances
Primary Balancing
Second Balancing
Deploy
Rules
Third Balancing
Cost Center
Security
Intercompany
Account
Combinations
Chart of Accounts
The chart of accounts denes the number and aributes of various segments, including:
• Order of segments
• Width of segments
• Prompts
125
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Segments
A chart of accounts segment is a component of the account combination. Each segment has a value set aached to it to
provide formaing and validation of the set of values used with that segment. The combination of segments creates the
account combination used for recording and reporting nancial transactions. Examples of segments that may be found
in a chart of accounts are company, cost center, department, division, region, account, product, program, and location.
Caution: You must use Independent validation only for the Accounting Key Flexeld value sets. Other
validations prevent you from using the full chart of accounts functionality, such as data security, reporting,
and account hierarchy integration. Dependent values sets aren't supported.
Segment Labels
Segment labels identify certain segments in your chart of accounts and assign special functionality to those segments.
Segment labels were referred to as exeld qualiers in Oracle E-Business Suite. Here are the segment labels that are
available to use with the chart of accounts.
• Balancing: Ensures that all journals balance for each balancing segment value or combination of multiple
balancing segment values to use in trial balance reporting. The three balancing segment labels are: primary,
second, and third balancing. The primary balancing segment label is required.
• Cost Center: Facilitates grouping of natural accounts by functional cost types, accommodating tracking of
specic business expenses across natural accounts. As cost centers combine expenses and headcount data
into costs, they're useful for detailed analysis and reporting. Cost centers are optional, but required if you're
accounting for depreciation, additions, and other transactions in Oracle Fusion Assets, and for storing expense
approval limits in Oracle Fusion Expense Management. If you're implementing Oracle Fusion Procurement, you
can use cost centers for business intelligence reporting and to route transactions for approval.
• Natural Account: Determines the account type (asset, liability, expense, revenue, or equity) and other
information specic to the segment value. The natural account segment label is required.
• Intercompany: Optionally, assigns the segment to be used in intercompany balancing functionality.
Note: All segments have a segment qualier that enables posting for each value. The predened seing is
Yes to post.
126
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Account Combinations
An account combination is a completed code of segment values that uniquely identies an account in the chart of
accounts, for example 01-2900-500-123, might represent InFusion America (company)-Monitor Sales (division)-
Revenue (account)-Air Filters (product).
Rules
The chart of accounts uses two dierent types of rules to control functionality.
• Security rules: Prohibit certain users from accessing specic segment values. For example, you can create a
security rule that grants a user access only to his or her department.
• Cross-validation rules: Control the account combinations that can be created during data entry. For example,
you may decide that sales cost centers 600 to 699 should enter amounts only to product sales accounts 4000
to 4999.
Rapid implementation is a way to congure a nancial enterprise and nancial reporting structures quickly using sheets
in a workbook that upload lists of:
• Companies (legal entities)
• Ledgers by country
• Business units
• Chart of accounts and segment values
• Segment value hierarchies
• Financial sequences
• Required subledger accounts
127
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Caution: Once you begin using your chart of accounts, calendar, and ledger, making changes to their
fundamental aributes is neither recommended nor supported. This includes your chart of account segments,
including the segment labels as well as other characteristics of those segments, and your calendar structure or
paern.
The following gure illustrates the ow of the enterprise structure setup.
Legal entities (companies) incur transactions that are identied by business units with business functions. Transactions
that are recorded in subledgers are transferred to the ledger. A ledger is characterized by a calendar, a currency, and a
chart of accounts. A chart of accounts consists of segments, some of which are assigned segment labels, such as cost
128
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
center, natural account, and primary balancing segment. Legal entities can be assigned primary balancing segment
values.
Legal Entities
Incurred
(Companies)
Transactions
Calendar
Balancing
Segments Identified by
Currency
Ledger
Business Units
Chart of
Accounts
Recorded in
Cost Natural
Centers Accounts
Subledgers
Other
Segments
Subledger
Transferred to
Accounting
Method
Additional information for some of the common setup objects depicted in the gure follows:
• Legal Entity: Identies a recognized party with rights and responsibilities given by legislation, which has the
right to own property and the responsibility to account for itself.
• Business Units: Performs one or many business functions that can be rolled up in a management hierarchy. A
business unit can process transactions on behalf of many legal entities. Usually a business unit has a manager,
strategic objectives, a level of autonomy, and responsibility for its prot and loss. When created through the
spreadsheet, all available business functions are automatically enabled for the business unit.
129
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Ledger: Maintains records and is a required component in your conguration. The rapid implementation
process:
◦ Creates primary ledgers by combining the chart of accounts, calendar, and currency as well as other
required options dened in the rapid implementation workbook.
◦ Assigns the standard accrual subledger accounting method to the primary ledger. The subledger
accounting method is used to group subledger journal entry rule sets together to dene a consistent
accounting treatment.
◦ Creates a General Ledger balances cube for each ledger with a unique chart of accounts and calendar
combination. Each segment is created as a dimension in the balances cube along with the standard cube
dimensions.
• Subledger: Captures detailed transactional information, such as supplier invoices, customer payments, and
asset acquisitions. Uses subledger accounting to transfer transactional balances to the ledger where they are
posted.
• Chart of Accounts: Congures accounts that consist of components called segments. Accounts are used to
record balances and organize nancial information and reporting.
• Segment: Identies one of the components of a chart of accounts, which when combined with other segments,
creates an account combination for recording transactions and journal entries. A segment is associated with a
value set, which provides the set of values for that segment, along with the formaing and validation for those
values.
• Segment Label: Identies certain segments in a chart of accounts and assigns special functionality to those
segments.
◦ Balancing Segment: Ensures that all journals balance for each balancing segment value or combination
of multiple balancing segment values for nancial processes and reports. The three balancing segment
labels are: Primary Balancing Segment, Second Balancing Segment, and Third Balancing Segment.
◦ Natural Account: Determines the account type (asset, liability, expense, revenue, or equity) and specic
categorization of the nancial activity. Facilitates General Ledger processes, such as closing of the
income statement accounts to retained earnings at the beginning of a new scal year.
◦ Cost Center: Facilitates grouping of natural accounts by functional cost types, accommodating tracking
of specic business expenses across natural accounts.
130
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Workbook Overview
In the Setup and Maintenance work area, create an implementation project that includes the Dene Financials
Conguration for Rapid Implementation task list. Download the workbook using the Create Chart of Accounts, Ledger,
Legal Entities, and Business Units in Spreadsheet task.
• Instructions
• Chart of Accounts, Calendar, and Ledger
• Business Units
• Companies and Legal Entities
• Natural Accounts
• Financial Sequences
New sheets for entering segment values and hierarchies for additional segments of your chart of accounts can be
created automatically. After you enter the segments on the Chart of Accounts, Calendar, and Ledger sheet, click Add
Segment Sheets or Generate Additional Hierarchy.
Note: The rapid implementation process creates a standard ledger. You can convert a standard ledger to an
average daily balance ledger before the rst period is opened by selecting the Enable average balances check
box on the Specify Ledger Options page.
Instructions
Review the Instructions sheet for important information about how to use the workbook and submit the accounting
conguration. The sheet includes data preparation requirements, setup object concepts, and best practices and
recommendations. Instructions on how to create additional hierarchies or additional hierarchy versions are also
included.
Use the sample completed workbook to familiarize yourself with how to enter data, preview the sample report, and
generate the required upload les.
131
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
The following gure shows the section of the Instructions sheet called Rapid Implementation Template with Sample
Data. This section includes the sample completed workbook, which you can download.
Caution: Once you begin using your chart of accounts, calendar, and ledger, making changes to their
fundamental aributes is neither recommended nor supported. This includes your chart of account segments,
including the segment labels as well as other characteristics of those segments, and your calendar structure or
paern.
The following gure shows an example of the Chart of Accounts, Calendar and Ledger sheet with sample values.
A primary ledger is created for each unique country that's entered in the Companies and Legal Entities sheet.
A country code is appended to the name that you specify. For example, one legal entity is based in the United
132
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
States and another in Canada. If you enter the ledger name of InFusion Ledger, two primary ledgers are
automatically created, InFusion Ledger US and InFusion Ledger CA.
All of the primary ledgers that are created use the same chart of accounts, account hierarchies, and accounting
calendar. Legal entities and their primary balancing segment values are assigned to the primary ledger of their
respective countries. If the addresses provided for the legal entities on the Companies and Legal Entities sheet
are all in the same country, then only one primary ledger is created.
• Currency: If you're not entering legal entities and only a single ledger should be created by the rapid
implementation conguration, enter the ledger currency in which you want to maintain accounting for in that
ledger. If you're entering legal entities, leave this eld blank. The currency is automatically supplied based on
the country.
• Period Frequency: Select from among the list of available frequencies for the ledger calendar.
Caution: For the accounting calendar created using the Rapid Implementation Enterprise Structure
solution, the choices of paerns are limited to the period frequency and adjusting periods options
that are available for selection in the spreadsheet. It is not possible to make alterations to the paern
or specied scal year start date once the calendar has already been created. The accounting
periods of the calendar are automatically named using a preset format. If you want to change
these period names, you have a limited window of time to make those changes. Use the Manage
Accounting Calendar page in the application to make the changes before the accounting calendar is
being used actively, such as when one of its accounting periods has been set to a status of Open.
• Adjusting Periods: Select the number of periods used to segregate closing, auditing, or other adjustments in
the General Ledger. The entries are tracked in the adjusting period and not in your monthly activity.
• Fiscal Year Start Date: Enter the start date of the accounting calendar. The date can't be changed after the
submission of the conguration.
Caution: If you plan to run translations, enter a scal year start date for the entire accounting year
that's before the rst period for which you intend to run translations. You can't run translation in the
rst dened period of an accounting calendar. For example, if your scal year starts on January 1,
and you want to start translations for the period of Mar-17, then you should select a scal year start
date of January 1, 2016. Also when determining the scal year start date, you might want to consider
whether you plan to load history.
• Segment: Enter the names for your segments. The value sets are created from the segments.
• Segment Label: Select segment labels to assign special functionality to segments.
Segment labels specifying the segment's purpose, such as balancing, cost center and natural account, can only
be assigned once to a chart of accounts segment. The Primary Balancing Segment and Natural Account
Segment labels must be assigned, while the other segment labels are optional. Segments that are assigned
these two particular labels cannot be assigned any other label. However, segments that are assigned the other
remaining labels can also be assigned additional labels, provided they're not Primary Balancing Segment or
Natural Account Segment.
The Intercompany Segment label assignment is optional. If assigned, that segment reuses the value set that's
created for the segment with the Primary Balancing Segment label. Using the same value set ensures that the
values for both segments remain synchronized.
Note: For the posting process to apply intercompany balancing, you must select the Enable
intercompany accounting option on the Specify Ledger Options page.
133
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Caution: If you plan to implement segment value security rules for the segment that's assigned
the Primary Balancing Segment label, then don't assign the Intercompany Segment label to a
segment on this sheet. Segment value security rules are assigned at the value set level. Sharing the
value set between the two segments causes security conicts because segment value enforcement
is simultaneously applied in the same way to both segments. For example, you dene a segment
value security rule for the Company segment where a user can only access company 01. Since
the value set is shared, that user also can't transact with other companies in an intercompany
transaction. Instead, follow these steps:
a. Include the intercompany segment in the sheet, but don't assign it the Intercompany
Segment label.
b. Click the Add Segment Sheets buon to add a sheet for the intercompany value set.
c. Create the values for your intended intercompany segment on the new sheet. Assign
the same values to the intercompany segment as you have for the primary balancing
segment and maintain this consistency going forward.
d. Complete the Upload Chart of Accounts task. Before starting the Upload Ledger,
Legal Entities, and Business Units task, in the Oerings work area, go to the following:
• Oering: Financials
• Functional Area: Financial Reporting Structures
• Task: Manage Chart of Accounts Structures
e. Assign the Intercompany Segment label to the intercompany segment of the chart
of accounts on the Edit Key Flexeld Segment page.
f. Redeploy the key exeld.
• Short Prompt: Enter a short name for the segment, which is used on applications pages.
• Display Width: Enter the segment size. Select the size carefully and leave room for growth. For example, if you
have 89 cost centers, enter 3 for the display length to allow for more than 100 cost centers in the future.
• Add Segment Sheets: Select this buon to create sheets for additional segments. Sheets are provided only for
the Company and Natural Accounts segments.
From the new segment sheet, you can click the Generate Additional Hierarchy buon to create more than
one hierarchy for any chart of account segment. A worksheet is then automatically created and populated with
the data already entered for that segment. Change this data as required for the new hierarchy. You can create
additional hierarchies during initial setup, or after the initial setup is done.
Caution: You can't change the chart of accounts, accounting calendar, or currency for your ledgers after the
setup is created.
Business Units
Enter the name of your business units and related default legal entities.
134
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
The following gure shows an example of the Business Units sheet with sample values for the Name and Default Legal
Entity Name elds.
Business units are created with the names that you enter. You can enter more than one business unit per ledger. Based
on the default legal entity specied for the business unit in the Business Units sheet, the business unit is assigned the
primary ledger to which its default legal entity is assigned.
Enter your legal entities for the child values with the address, registration number, and reporting unit registration
number. The registration number identies legal entities registered for your company and recognized by law for
which you want to record and perform transactions. The reporting unit registration number identies the lowest level
component of a legal structure that requires registrations.
135
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
The following gure shows part of the Companies and Legal Entities sheet with sample values. The sheet includes
columns for dierent levels of parent values, the child value, and company description. The Legal Entity columns
include name, identier, country, address information, and registration numbers.
To create additional hierarchies for the company segment for reporting or other purposes, click the Generate
Additional Hierarchy buon. A worksheet is automatically created and populated with the data already entered for that
segment. Change this data as required for the new hierarchy. You can create additional hierarchies during initial setup,
or after the initial setup is done.
When a new hierarchy sheet is created, the name for that sheet is derived by adding a counter to the sheet name. For
example, when you click Generate Additional Hierarchy on the Companies and Legal Entities sheet, the new sheet
is named Companies and Legal Entities 1. When you click Generate Additional Hierarchy again, another sheet is
generated with the name Companies and Legal Entities 2.
Note: Adding legal entity information isn't supported on a new hierarchy sheet for the Company segment.
Natural Accounts
Enter account hierarchies, account values, and specify account types.
136
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
The following gure shows part of the Natural Accounts sheet with sample parent and child values, descriptions, and
account type.
• Parent: Enter parent account values to dene hierarchies. Hierarchies are used for chart of accounts mappings,
revaluations, data access sets, cross-validation rules, and segment value security rules. The balances cube and
account hierarchies are also used for nancial reporting, Smart View queries, and allocations.
• Child: Enter child account values to dene the postable accounts.
• Description: Enter descriptions for the segment values.
• Account Type: You must assign an account type to each account value. Account types are used in year-end
close processes and to correctly categorize account balances for reporting. Select from among general account
types and expanded account types. The general account types are: Asset, Liability, Owner's Equity, Revenue,
Expense. Expanded account types provide specialized functionality and are used to:
◦ Identify the intended usage of your natural account values to facilitate automation and enable
completion of other required setup objects. For example, assign the Asset - Intercompany Receivable
and Liability - Intercompany Payable expanded account types. The Rapid Implementation process then
automatically creates a chart of accounts level intercompany balancing rule, which is a required setup for
the application to perform intercompany balancing.
◦ Automatically generate fully dened initial Financial Reporting reports and Account Groups based on
your enterprise structure.
You must assign the Revenue - Top Revenues Parent Account and Expense - Top Operating Expenses
Account account types to the parent accounts that are your highest level and comprehensive revenue and
operating expenses accounts. You can optionally assign the account type of Expense - Top Cost of Sales
Parent Account, if it's applicable for your scenario.
The Generate Financial Reports and Account Groups process, which is automatically submied when the
accounting conguration is created in the application, generates a set of Financial Reporting reports and
137
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
account groups according to the accounting conguration dened in the workbook. The top parent accounts
are used as the basis for deriving the accounts referenced in the reports and in the Account Groups.
The immediate descendants of the top parent accounts are used to dene the rows on the reports. Depending
on whether both the top operating expense and top cost of sales accounts are tagged, dierent variations
of the income statements are generated. If the optional top cost of sales account is provided, the Financial
Reporting reports that are income statements also include a gross margin section.
Caution: Assign account types carefully. If you assign an incorrect account type to a natural
account segment value, accounting entries are recorded incorrectly and nancial statements are
inaccurate. Misclassied accounts are also potentially handled incorrectly at year end, with actual
balances either geing zeroed out to retained earnings, or accumulating into the next year.
• Financial Category: Select a value to identify groups of accounts for reporting with Oracle Transactional
Business Intelligence. Accounts that are tagged with expanded account types are automatically assigned a
nancial category. You can override the default category or leave it out.
• Generate Additional Hierarchy: To create additional hierarchies for the natural account segment for reporting
or for other purposes, click the Generate Additional Hierarchy buon. A worksheet is automatically created
and populated with the data already entered for that segment. Change this data as required for the new
hierarchy. You can create additional hierarchies during initial setup or after the initial setup is done.
Financial Sequences
Enable document or journal sequences to assign unique numbers to transactions to meet legal requirements.
The following gure shows the Financial Sequences sheet with sample values for the Restart and Initial Value columns.
Document sequences are created for these transactions: Payables invoices, Payments, Receivables invoices, Receivables
credit memos, Receivables adjustment activities. Reporting and accounting journal sequences are created for Subledger
journals and General Ledger journals.
For each transaction, you can provide values for the following elds:
138
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
1. On the Chart of Accounts, Calendar, and Ledger sheet, click the Step 1: Validate buon.
The validation checks the worksheets for missing or inappropriate setups. Errors are marked as actionable
items in a validation report sheet that's dynamically generated. You can review the anomalies and make
the corrections as indicated. The Field column on the validation report notes the issue. Click the text link
to navigate to the appropriate eld in the sheet that must be updated. When the validation is successful, a
message appears with the option of previewing a sample of the reports that are automatically generated as part
of the enterprise conguration.
The following gure shows the message that appears after a successful validation.
If you select to preview the sample report, a new sheet is automatically created called Preview Report. The
preview incorporates elements of the setup that you provided. The rows on the report are derived based on the
top parent revenue and expense account values that you tagged on the Natural Accounts sheet. The preview
also reects the reporting hierarchy for your natural accounts.
The following gure shows an example of the sample Financial Reporting report.
139
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
You can use the preview to validate whether the hierarchy setup aligns to your reporting needs. If the natural
account hierarchy requires adjustments, this is your chance to make those corrections before actually creating
the account hierarchies in the application. You can modify your enterprise structure setup, validate the
spreadsheet, and preview the revised sample reports for as many times as you need. The account hierarchies
are created when you nally submit the accounting conguration in the rapid implementation spreadsheet.
2. Click Step 2: Generate Chart of Accounts File. The process generates a data le called ChartOfAccounts.xml
with the entered chart of accounts and hierarchies setup data. Save the le to a network or local drive.
3. Click Step 3: Generate Ledger, LE, and BU File. The process generates a data le called
FinancialsCommonEntities.xml with the entered ledger, legal entities, and business unit setup data. Save the le
to a network or local drive.
4. From your implementation project, go to the Upload Chart of Accounts task. The Upload Enterprise Structures
and Hierarchies process is launched.
5. Accept the default selection of the Upload Enterprise Structure option.
6. Click Browse and select the rst le that you saved called ChartOfAccounts.xml.
7. Click Submit.
8. Verify that the process completed without errors or warnings.
9. From your implementation project, go to the Upload Ledger, Legal Entities, and Business Units task. The
Upload Enterprise Structures and Hierarchies process is launched.
10. Accept the default selection of the Upload Enterprise Structure option.
11. Click Browse and select the second le that you saved called FinancialsCommonEntities.xml.
140
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
The process also generates three account groups. These include two for the infolets, Revenues and Expenses, and
one for the Close Monitor called Close Monitor Summary Income Statement. A set of these three account groups is
generated for the balances cube, to be shared among all the ledgers that are part of that balances cube.
Related Topics
• Overview of Trees
• How Financial Reporting Reports and Account Groups Are Generated
• Manage Setup Using Implementation Projects
141
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Scenario
Your company, InFusion Corporation, is a multinational conglomerate that operates in the United States (US) and the
United Kingdom (UK). InFusion has purchased an Oracle Fusion Enterprise Resource Planning (ERP) solution including
Oracle Fusion General Ledger and all of the Oracle Fusion subledgers. You are chairing a commiee to discuss creation
of a model for your global nancial reporting structure including your charts of accounts for both your US and UK
operations.
InFusion Corporation
InFusion Corporation has 400 plus employees and revenue of 120 million US dollars. Your product line includes all the
components to build and maintain air quality monitoring systems for homes and businesses.
Analysis
In Oracle Fusion General Ledger, the chart of accounts model is framed around the concept of a chart of accounts
structure, for which one or more chart of accounts structure instances can be created.
For each chart of accounts structure, it is possible to associate one or more chart of accounts structure instances. Chart
of accounts structure instances for the same structure share a common conguration with the same segments, in the
same order, and the same characteristics. Using one chart of accounts structure with multiple instances simplies your
accounting and reporting.
At the chart of accounts structure instance level, each segment is associated with a value set that conforms to the
characteristic of that segment. For example, you assign a value set with the same segment type and length to each
segment. You are using hierarchies with your chart of accounts segments. Each structure instance segment is assigned
a tree code to indicate the source of the hierarchy information for the associated value set. The same value set can
be used multiple times within the same or across dierent chart of accounts instances within the same structure or in
dierent structures. This functionality reduces your segment value creation and maintenance across your charts of
accounts.
The collective assignment of value sets to each of the segments forms one chart of accounts instance. At the chart of
accounts structure instance level, you can select to enable dynamic insertion. Dynamic insertion allows the creation of
account combinations automatically the rst time your users enter that new account combination. The alternative is to
create them manually. By deciding to enable dynamic insertion, you save data entry time and prevent delays caused
by the manual creation of new account combinations. Well-dened cross-validation rules help prevent the creation of
inappropriate account combinations.
Perform deployment after a new chart of accounts structure and structure instances are dened or any of their
modiable aributes are updated. Deployment validates and regenerates the necessary objects to enable your charts of
accounts and chart of accounts structure instances. By unifying and standardizing you organization's chart of accounts,
you are positioned to take full advantage of future functionality in Oracle Fusion General Ledger.
In summary, you are recommending to your company to unify the organization's chart of accounts in a single chart of
accounts structure based on chart of accounts commonalities across ledgers. You have also decided to use the chart
of accounts structure instance construct to serve dierent accounting and reporting requirements by using value sets
specic to each of your entities.
142
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
◦ Oering: Financials
◦ Functional Area: Financial Reporting Structures
◦ Task: Manage Chart of Accounts Structures
2. Select the General Ledger module and click Search.
3. Click Manage Structures.
4. On the Manage Key Flexeld Structures page, select the General Ledger row and click the Create icon.
5. On the Create Key Flexeld Structure page, enter the unique structure code INFUSION_AM_COA_STRUCTURE
and name InFusion America COA Structure. Provide an optional description of InFusion America Inc. chart
of accounts structure.
6. Select a delimiter to visually separate the segment values.
7. Click Save.
8. To create a segment, click the Create icon to open the Create Key Flexeld Segment page.
Field Value
Sequence Number 1
143
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Field Value
Prompt Company
Short Prompt CO
Display Width 2
b. Select a segment label, Primary Balancing Segment, to indicate its purpose within your chart of
accounts.
Note: Two segment labels are required: primary balancing segment and natural account
segment. These labels aren't used with each other or with other labels in a specic segment.
c. Click Save and Close.
d. Click Done.
e. Dene additional segments following the same steps.
◦ Oering: Financials
◦ Functional Area: Financial Reporting Structures
◦ Task: Manage Chart of Accounts Structure Instances
2. On the Manage Chart of Accounts Structure Instances page, select the General Ledger module and click
Search.
3. Select the General Ledger row and click Manage Structure Instances.
4. On the Manage Key Flexeld Structure Instances page, click the Create icon.
5. On the Create Key Flexeld Structure Instance page, enter the unique structure instance code
INFUSION_AM_COA_INSTANCE and name InFusion America COA Instance. Provide an optional description,
InFusion America Inc. chart of accounts structure instance.
6. Select the Dynamic combination creation allowed option to indicate that you want to dynamically generate
account combinations.
7. Associate your instance with the structure InFusion America Structure.
Note: By default, an instance inherits the key aributes of the associated structure. Some aributes,
such as the value set assigned to each the segment, can be modied.
8. Click Save.
9. To modify an instance segment, select the segment row and click Edit.
144
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Note: Select the Required and Displayed options for all segments including those intended for
future use. The recommended best practice is to dene one segment for future use and set a default
value. This ensures room for expansion in your chart of accounts and that the extra segment is
populated in account combinations. Select the BI enabled option to use key exeld segments in
Oracle Fusion Transactional Business Intelligence. The business intelligence option is only valid
when enabled on segments with segment labels. The second step is to populate the BI Object Name
eld for each of the segment labels on the Manage Segment Label page, which you open from the
Manage Key Flexelds page.
11. Click OK.
12. Click Save and Close.
13. Dene additional instances following the same process.
Note: Alternatively, proceed directly with creating your value set values by selecting the
corresponding Value Set Code in the Segment Instances table.
14. Click Done.
15. Click Deploy Flexeld.
16. Click OK.
Related Topics
• Considerations for Enabling Key Flexeld Segments for Business Intelligence
• Update Existing Setup Data
By enabling multiple balancing segments for your chart of accounts, you can produce nancial statements for each
unique combination of segment values across one, two, or three qualied balancing segments. This ability provides
you greater insights into your operations as it aords you visibility along the critical scal dimensions you use to plan,
monitor, and measure your nancial performance.
145
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Importing journals: Adds lines using the suspense account on unbalanced journals.
• Posting journals: Adds additional lines to unbalanced journals for the following enabled account types:
◦ Suspense
◦ Rounding
◦ Net income
◦ Retained earnings
◦ Cumulative translation adjustments from replication of revaluation journals to reporting currencies and
for multiple reporting currency account type specic conversion
• Posting prior period journals: Calculates any income statement impact and posts to the appropriate retained
earnings account.
• Translating balances: Supports multiple balancing segments for the following accounts:
◦ Retained earnings: Calculated translated retained earnings are post to the retained earnings accounts by
balancing segment. Retained earnings accounts represent the summing of the translated revenue and
expense accounts across multiple balancing segment values.
◦ Cumulative translation adjustment: Amounts posted by balancing segment to these accounts represents
currency uctuation dierences between ranges of accounts which use dierent rate types. For example,
period end rates are used for asset and liability accounts and historical rates for equity accounts.
• Revaluing Balances: Supports multiple balancing segments when calculating gain or loss accounts.
• Creating Opening Balances: Initializes reporting currency balances by converting from the total primary
currency. Any dierence in the reporting currency amounts is oset by populating retained earnings accounts.
• Closing year end: Supports multiple balancing segments when calculating the income statement oset and
closing account in the closing journals.
146
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Implementation Timing
When using optional second and third balancing segments, remember that these chart of accounts segment labels are
set from the beginning of time. Ensure that balances are immediately maintained in accordance with the necessary
balancing actions to produce consistent nancial reporting for the wanted business dimensions. Multiple balancing
segment ledgers that aren't maintained from the beginning of time, require extensive manual balance adjustments to
catch up and realign the balances.
Note: Do not set a segment already qualied as a natural account or intercompany segment as any of the
three balancing segments. Validations aren't performed when segment labels are assigned, so verify that all
are assigned correctly before using your chart of accounts.
Change Options
Once a segment has been enabled and designated as a balancing segment, you must not change the segment. Do not
disable the segment or remove the segment labels. These seings must be consistently maintained throughout the life
of the chart of accounts to control the accuracy and integrity of the nancial data.
Migration Adjustments
For charts of accounts migrated from Oracle E-Business Suite to Oracle Fusion General Ledger that uses a second and
third balance segments, steps must be taken to ensure the proper transition. The required adjustments are extensive.
For ledgers associated with a migrated chart of accounts, the balances must be adjusted manually. The manual
adjustment is to ensure that the second and third balancing segments are consistent as though these segment labels
have been in place since the beginning of entries for these ledgers. Recomputing and updating of the following
processes is required to reect the correct balancing for each account using the second and third balancing segments.
• Intercompany balancing
• Suspense posting
• Rounding imbalance adjustments on posting
• Entered currency balancing
• Revaluation gains or losses
• Retained earnings calculations at the opening of each new scal year
• Cumulative translation adjustments during translation
Note: All previously translated balances must also be purged. New translations must be run to properly
account for translated retained earnings and cumulative translation adjustments with the correct level of
balancing.
Related Topics
• How can I change segments in an existing chart of accounts structure
Scenario
Your company has a chart of accounts with two balancing segments and three segments, qualied as follows:
• Company: Primary balancing segment
147
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
The following table shows a journal that was entered to transfer advertising and phone expense from company 1, cost
center A to company 2, cost center B.
The posting process creates journal lines to balance the entry across the primary and second balancing segments,
company and cost center. The following table shows all of the journal lines, including balancing lines 5 through 8, which
were automatically created.
148
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Module Designation
The module designation is used to tag value sets and sets the value sets apart during upgrades and other processes.
When creating value sets for a chart of accounts, the module can be specied as General Ledger to distinctly identify its
intended use in an accounting exeld, basically a chart of accounts.
Validation Type
Assign one of the following validation types to chart of accounts value sets:
• Independent: The values are independently selected when lling out the segments in an account combination.
149
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Table: The values are stored in an external table to facilitate maintenance and sharing of reference data.
Caution: You must use Independent validation only for the Accounting Key Flexeld value sets. Other
validations prevent you from using the full chart of accounts functionality, such as data security, reporting,
and account hierarchy integration. Dependent values sets aren't supported.
Format Assignments
Value sets for chart of accounts must use the Value Data Type of Character. The Value Subtype is set to Text. These
two seings support values that are both numbers and characters, which are typical in natural account segment values.
Set the maximum length of the value set to correspond to the length of the chart of accounts segment to which it's
assigned. Best practices recommend restricting values to Upper Case Only or Numeric values that are zero lled by
default.
Security Rules
If exeld data security rules are to be applied to the chart of accounts segment associated with the value set, the
Enable Security option for the assigned value set must be selected. In addition, assign a data security resource name to
enable creation of a data security object automatically for the value set. The data security object is used in the denition
of exeld data security rules.
Value Denition
Once these basic characteristics are dened for the value set, values can be added to the set on the Manage Values
page.
1. Enter the value and description. Set the value to conform to the value set length and type.
2. Indicate whether the value is enabled and specify the start and end dates.
3. Assign the following aributes: Summary, Allow Posting, Allow Budgeting.
4. If the value set is used with a natural account segment, you must set the Account Type aribute. Select one of
the following options: Asset, Liability, Owner's Equity, Revenue, or Expense.
Caution: Assign account types carefully. If you assign an incorrect account type to a natural
account segment value, accounting entries are recorded incorrectly and nancial statements are
inaccurate. Misclassied accounts are also potentially handled incorrectly at year end, with actual
balances either geing zeroed out to retained earnings, or accumulating into the next year.
5. Other aributes that you can set are Third-Party Control Account, Reconcile, and Financial Category, which
is used with Oracle Transactional Business Intelligence reporting.
The Third-Party Control Account aribute enables you to maintain detailed balances by third party for an
account combination. Valid third-party information must be associated with the journal line if the account is a
third-party control account. General Ledger prevents manual journal entries from posting to third-party control
accounts. This ensures that journal lines that post to control accounts such as the supplier liability account
and the customer receivables account, are associated with valid third-party information in the respective
subledgers.
◦ Customer Control Account: Customer information is required when such accounts are used in
subledger transactions or subledger journals.
◦ Supplier Control Account: Supplier information is required when such accounts are used in subledger
transactions or subledger journals.
◦ Third-Party Control Account: Third-party information is required when such accounts are used in
subledger transactions or subledger journals.
150
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
◦ Restrict GL Manual Journals: Third-party information isn't required when such accounts are used in
subledger transactions or subledger journals.
◦ No: Not a control account.
Caution: Don't enable the third-party control account type for exchange gain or loss accounts
because third-party information is required when a control account is used and this information isn't
available for exchange gain or loss journal lines.
General Ledger prevents manual journal entries to all of the accounts whose Third-Party Control Account
aribute is set to a value other than No.
Tip: Best practice is to dene value set values after the value set has been assigned to a chart of accounts
structure instance. Otherwise you can't dene the mandatory value aributes, such as the summary indicator,
the posting allowed indicator, and the account type for natural account segments. The aributes must be
added after the value set is assigned to a chart of accounts structure instance.
Scenario
You are creating a company value set to be used in your chart of accounts for your enterprise, Vision Corporation.
Follow these steps:
◦ Oering: Financials
◦ Functional Area: Financial Reporting Structures
◦ Task: Manage Chart of Accounts Value Sets
2. Click the Create icon in the Search Results section.
3. On the Create Value Set page, enter a unique value set code, Vision Corporation, and an optional description,
Company values for Vision Corporation
4. Select General Ledger from the list in the Module eld.
5. Select Independent as the validation type.
Note: You must use Independent validation only for Accounting Key Flexeld value sets. Other
validations prevent you from using the full chart of accounts functionality, such as data security,
reporting, and account hierarchy integration. Dependent values sets aren't supported.
Related Topics
• Update Existing Setup Data
151
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
◦ Oering: Financials
◦ Functional Area: Financial Reporting Structures
◦ Task: Manage Chart of Accounts Structures
2. Enter GL# in the Key Flexeld Code eld.
3. Click Search.
4. Click Manage Structure Instances.
5. Click Search.
6. Click the specic chart of accounts and click the Edit icon.
7. Click the specic segment and click the Edit icon.
8. Select the BI enabled option.
9. Click Save. This should be done for all segments in every chart of accounts structure instance that you intend
to be mapped in the RPD.
10. Click Save and Close.
11. Click Done.
Follow these steps to specify a BI object name for each segment label. This name is the logical table name in the RPD
that's used as the dimension for the corresponding segment.
1. In the Setup and Maintenance work area, use the following:
◦ Oering: Financials
◦ Functional Area: Financial Reporting Structures
◦ Task: Manage Chart of Accounts Structures
2. Enter GL# in the Key Flexeld Code eld.
3. Click Search.
4. Select the Actions menu and click Manage Segment Labels.
5. Populate the BI Object Name eld for all of the segment labels that must be mapped in the RPD. Complete the
elds, as shown in this table.
152
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
6. Click Save.
Note: For all the nonqualied segment labels, populate the BI Object Name with one of the following values:
• Dim - GL Segment1
• Dim - GL Segment2
• Dim - GL Segment3
• Dim - GL Segment4
• Dim - GL Segment5
• Dim - GL Segment6
• Dim - GL Segment7
• Dim - GL Segment8
• Dim - GL Segment9
• Dim - GL Segment10
Deploy the exeld using the Deploy Flexeld buon on the Manage Key Flexelds page. For more information
about using both key and descriptive exelds in Oracle Fusion Transactional BI, refer to the Oracle Fusion
Transactional Business Intelligence Administrator's Guide.
Related Topics
• Update Existing Setup Data
Caution: The choices you make when specifying the following options are critical, because it's dicult to
change your accounting calendar after a period status is set to open or future enterable.
• Budgetary control only
• Start Date
• Period Frequency
• Adjusting Period Frequency
153
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Note: To help create and maintain accounting calendars, the common calendar types of monthly, weekly,
4-4-5, 4-5-4, 5-4-4, 4-week, quarterly, and yearly, are automatically generated. By using the period frequency
option, you no longer have to go through the tedious task of dening each period manually.
Start Date
If you plan to run translation, specify a calendar start date that's a full year before the start date of the year of the rst
translation period for your ledger. Translation can't be run in the rst period of a calendar. Consider how many years of
history you're going to load from your previous application and back up the start date for those years plus one more.
You can't add previous years once the rst calendar period has been opened.
Period Frequency
Use the period frequency to set the interval for each subsequent period to occur, for example, monthly, quarterly, or
yearly. If you select the period frequency of Other, by default, the application generates the period names, year, and
quarter number. You specify the start and end dates. You must manually enter the period information. For example,
select the period frequency of Other and enter 52 as the number of periods when you want to dene a weekly calendar.
For manually entered calendars, when you click the Add Year buon, the application creates a blank year. Then, you
must manually enter the periods for the new year. The online validation helps prevent erroneous entries.
If the year has been dened and validated, use the Add Year buon to add the next year quickly. Accept or change the
new rows as required. For example, with the Other frequency type calendar, dates may dier from what the application
generates.
Note: A calendar can have only one period frequency and period type. Therefore, if you have an existing
calendar with more than one period type associated with it, during the upgrade from Oracle E-Business Suite,
separate calendars are created based on each calendar name and period type combination.
◦ For example, April 10, 2016 to May 9, 2016 has the period name of Apr-16 and December 10, 2016 to
January 9, 2017 has the name of Dec-16.
154
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
◦ If period frequency is Other, then the period format section is hidden. The application generates a
temporary period name for calendars with period frequency of Other, using a xed format of Period
numberYY. You can override this format with your own period names.
Note: For an accounting calendar that's associated with a ledger, changing period names or adding a year
updates the accounting period dimension in the balances cubes.
Period number beyond the maximum 13 for a 12 period calendar with no adjusting periods
number of periods per year
Missing period numbers Periods 1 through 6 are dened for a calendar with 12 months
Period numbers not in sequential Period 1 covers 01-Jan-2017 to 31-Jan-2017 and period 2 covers 01-Mar-2017 to 31-Mar-2017,
order by date and period 3 covers 01-Feb-2017 to 28-Feb-2017.
155
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Period start or end dates more than July 1, 2015 in a 2017 calendar
one year before or after the scal year
Calendar period naming format: Select the calendar period format to append the period's start date's year to the prex.
For the period covering September 1, 2014 to December 31, 2014, then 2014 or just 14, depending on the period format
selected, is appended to each period's name. For the remaining periods covering January 1, 2015 to August 31, 2015,
then 2015 or 15, is appended to each period's name.
Fiscal period naming format: Select the scal period format to always append the period's year assignment to the prex.
If the accounting periods in the set of twelve are all assigned the year of 2015, then 2015 or just 15, depending on the
period format selected, is appended to the period name of all 12 periods.
What happens if I upgrade my calendar from Oracle E-Business Suite Release 12?
The migration script assigns a period frequency that most closely matches your Oracle E-Business Suite Release 12
calendar. When you use the Oracle Fusion applications Add Year functionality for the rst time, you have an opportunity
to review and change the period frequency. The Calendar Options page opens only for calendars upgraded from
Release 12 to allow one time modication.
156
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Make your changes to the period frequency, adjusting period frequency, and period name format, including the prex
and separator, as needed. Changes cannot conict with the existing upgraded calendar denition. Update the calendar
name and description in the calendar header, as needed, for all calendars. Period details for a new year are generated
automatically based on the latest calendar options. You can also manually update the calendar. The modied calendar
options aect future years only.
• The Oracle Accounting Hub Cloud oering is used to add the General Ledger and Subledger Accounting
application features to an existing Enterprise Resource Planning (ERP) source system to enhance reporting and
analysis.
• The Financials oering includes the General Ledger and Subledger Accounting application features and one or
more subledger nancial applications.
When adding an oering to an implementation project, update the tasks displayed by adding additional tasks.
The number of ledgers and subledgers is unlimited and determined by your business structure and reporting
requirements.
Single Ledger
If your subsidiaries all share the same ledger with the parent company or they share the same chart of accounts and
calendar, and all reside on the same applications instance, you can consolidate nancial results in Oracle Fusion General
Ledger in a single ledger. Use Oracle Fusion Financial Reporting functionality to produce individual entity reports by
157
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
balancing segments. General Ledger has three balancing segments that can be combined to provide detailed reporting
for each legal entity and then rolled up to provide consolidated nancial statements.
Multiple Ledgers
Accounting operations using multiple ledgers can include single or multiple applications instances. You need multiple
ledgers if one of the following is true:
• You have companies that require dierent account structures to record information about transactions and
balances. For example, one company may require a six-segment account, while another needs only a three-
segment account structure.
• You have companies that use dierent accounting calendars. For example, although companies may share
scal year calendars, your retail operations require a weekly calendar, and a monthly calendar is required for
your corporate headquarters.
• You have companies that require dierent functional currencies. Consider the business activities and reporting
requirements of each company. If you must present nancial statements in another country and currency,
consider the accounting principles to which you must adhere.
Subledgers
Oracle Fusion Subledgers capture detailed transactional information, such as supplier invoices, customer payments,
and asset acquisitions. Oracle Fusion Subledger Accounting is an open and exible application that denes the
accounting rules, generates detailed journal entries for these subledger transactions, and posts these entries to the
general ledger with exible summarization options to provide a clear audit trail.
Primary Ledgers
A primary ledger:
• Is the main record-keeping ledger.
• Records transactional balances by using a chart of accounts with a consistent calendar and currency, and
accounting rules implemented in an accounting method..
• Is closely associated with the subledger transactions and provides context and accounting for them.
To determine the number of primary ledgers, your enterprise structure analysis must begin with your nancial, legal,
and management reporting requirements. For example, if your company has separate subsidiaries in several countries
worldwide, enable reporting for each country's legal authorities by creating multiple primary ledgers that represent
each country with the local currency, chart of accounts, calendar, and accounting method. Use reporting currencies
linked to your country-specic primary ledgers to report to your parent company from your foreign subsidiaries. Other
considerations that aect the number of primary ledgers required are:
• Corporate year end
• Ownership percentages
158
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Secondary Ledgers
A secondary ledger:
• Is an optional ledger linked to a primary ledger for the purpose of tracking alternative accounting.
• Can dier from its primary ledger by using a dierent accounting method, chart of accounts, accounting
calendar, currency, or processing options.
When you set up a secondary ledger using the Manage Secondary Ledger task, you select a data conversion level. The
data conversion level determines what level of information is copied to the secondary ledger. You can select one of the
following levels: Balance, Journal, Subledger, or Adjustment Only.
• Balance: When you run the Transfer Balances to Secondary Ledger process, balances are transferred from the
primary ledger to the secondary ledger.
• Journal: When you post journals in the primary ledger, the posting process copies the journals to the
secondary ledger for the sources and categories that you specify in the Journal Conversion Rules section on the
Map Primary to Secondary Ledger page.
In the Journal Conversion Rules section, you can do one of the following:
◦ Accept the default seing of Yes for the journal source and category combination of Other, and then
specify the source and category combinations to exclude from the conversion.
◦ Set the journal source and category combination of Other to No, and then specify the source and
category combinations to include in the conversion.
• Subledger: When you run the Create Accounting process in the primary ledger, the process creates subledger
journals for both the primary and secondary ledgers. When you run the Post Journals process in the primary
ledger for journals that are created through methods other than the Create Accounting process, the posting
process copies the primary ledger journals to the secondary ledger. For any journals that you don't want
copied by posting, you can change the seings in the Journal Conversion Rules section on the Map Primary
to Secondary Ledger page. To prevent duplication, posting doesn't copy any journal that originated from
subledgers, regardless of the seings in the Journal Conversion Rules section.
Caution: You don't have to specify journal conversion rules for your subledgers because journal
conversion rules are applicable only to postings from Oracle Fusion General Ledger. The Create
Accounting process automatically produces accounting for both the primary and the secondary
ledger, regardless of the journal conversion rule seings.
• Adjustment Only: This level is an incomplete accounting representation that holds only adjustments. The
adjustments can be entered as manual journals in General Ledger. This type of secondary ledger must share
the same chart of accounts, accounting calendar, period type, and currency as the associated primary ledger.
Tip: To obtain a complete secondary accounting representation that includes both transactional data and
adjustments, use ledger sets to combine the ledgers when running reports.
Example
Your primary ledger uses US Generally Accepted Accounting Principles (GAAP) and you maintain a secondary ledger
for International Financial Reporting Standards (IFRS) accounting requirements. You rst decide to use the subledger
conversion level for the IFRS secondary ledger. However, since most of the accounting between US GAAP and IFRS
is identical, the adjustment only level is the beer solution for the secondary ledger. The subledger level requires
duplication of most subledger and general ledger journal entries and general ledger balances. The adjustment only level
159
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
transfers only the adjustment journal entries and balances necessary to convert your US GAAP accounting to the IFRS
accounting. Thus, requiring less processing resources.
Tip: To avoid dicult reconciliations, use the same currency for primary and secondary ledgers. Use
reporting currencies or translations to generate the dierent currency views to comply with internal reporting
needs and consolidations.
Reporting Currencies
Reporting currencies maintain and report accounting transactions in additional currencies. Consider the following
before deciding to use reporting currencies.
• Each primary and secondary ledger is dened with a ledger currency that's used to record your business
transactions and accounting data for that ledger.
• Best practices recommend that you maintain the ledger in the currency in which the majority of its transactions
are denominated. For example, create, record, and close a transaction in the same currency to save processing
and reconciliation time.
• Compliance, such as paying local transaction taxes, is also easier using a local currency.
• Many countries require that your accounting records be kept in their national currency.
If you maintain and report accounting records in dierent currencies, you do this by dening one or more reporting
currencies for the ledger. When you set up a reporting currency using the Manage Reporting Currency task, you select a
currency conversion level. The currency conversion level determines what level of information is copied to the reporting
currency.
You can select one of the following levels: Balance, Journal, Subledger.
• Balance: When you run the Translate General Ledger Account Balances process, balances are transferred from
the specied ledger to the reporting currency and converted.
• Journal: When you post journals, the posting process copies the journals to the reporting currency for the
sources and categories that you specify in the Journal Conversion Rules section on the Create or Edit Reporting
Currency pages.
In the Journal Conversion Rules section, you can do one of the following:
◦ Accept the default seing of Yes for the journal source and category combination of Other, and then
specify the source and category combinations to exclude from the conversion.
◦ Set the journal source and category combination of Other to No, and then specify the source and
category combinations to include in the conversion.
• Subledger: When you run the Create Accounting process in the primary ledger, the process creates subledger
journals for both the primary ledger and the reporting currency. When you run the Post Journals process in
the primary ledger for journals that are created through methods other than the Create Accounting process,
the posting process copies the primary ledger journals to the reporting currency. For any journals that you
don't want copied by posting, you can change the seings in the Journal Conversion Rules section on the
Edit Reporting Currency page. To prevent duplication, posting doesn't copy any journal that originated from
subledgers, regardless of the seings in the Journal Conversion Rules section.
Caution: You don't have to specify journal conversion rules for your subledgers because journal
conversion rules are applicable only to postings from Oracle Fusion General Ledger. The Create
Accounting process automatically produces accounting for both the primary ledger and the
reporting currency, regardless of the journal conversion rule seings.
160
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Note: A full accounting representation of your primary ledger is maintained in any subledger level reporting
currency. Secondary ledgers can't use subledger level reporting currencies.
Do not use journal or subledger level reporting currencies if your organization translates your nancial statements to
your parent company's currency for consolidation purposes infrequently. Standard translation functionality meets this
need. Consider using journal or subledger level reporting currencies when any of the following conditions exist.
• You operate in a country whose unstable currency makes it unsuitable for managing your business. As a
consequence, you manage your business in a more stable currency while retaining the ability to report in the
unstable local currency.
• You operate in a country that's part of the European Economic and Monetary Union (EMU), and you select to
account and report in both the European Union currency and your National Currency Unit.
Note: The second option is rare since most companies have moved beyond the initial conversion to the EMU
currency. However, future decisions could add other countries to the EMU, and then, this option would again
be used during the conversion stage.
Related Topics
• What's the dierence between mapping with segment rules and mapping with account rules
• When do account rules override segment rules in a chart of accounts mapping
161
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
The following gure provides an example of an enterprise structure with primary ledgers, secondary ledgers, a
reporting currency, legal entities, business units, and balancing segments, and shows their relationships to one another.
Corporate
Primary
Ledger
Reporting
Currency
Subsidiary
Secondary
Primary
Ledgers
Ledgers
Mapping Chart of
Accounts
Business
Units
Legal Legal
Entities Entities
Transactions
Balancing Balancing
Segments Segments
Primary Ledgers
A primary ledger is the main record-keeping ledger. Create a primary ledger by combining a chart of accounts,
accounting calendar, ledger currency, and accounting method. To determine the number of primary ledgers, your
enterprise structure analysis must begin with determining nancial, legal, and management reporting requirements.
For example, if your company has separate subsidiaries in several countries worldwide, create multiple primary ledgers
representing each country with the local currency, chart of accounts, calendar, and accounting method to enable
reporting to each country's legal authorities.
If your company just has sales in dierent countries, with all results being managed by the corporate headquarters,
create one primary ledger with multiple balancing segment values to represent each legal entity. Use secondary ledgers
or reporting currencies to meet your local reporting requirements, as needed. Limiting the number of primary ledgers
simplies reporting because consolidation isn't required. Other consideration such as corporate year end, ownership
considerations, and local government regulations, also aect the number of primary ledgers required.
162
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Secondary Ledgers
A secondary ledger is an optional ledger linked to a primary ledger. A secondary ledger can dier from its related
primary ledger in chart of accounts, accounting calendar, currency, accounting method, or ledger processing options.
Reporting requirements, for example, that require a dierent accounting representation to comply with international or
country-specic regulations, create the need for a secondary ledger.
Note: Journal conversion rules, based on the journal source and category, are required to provide instructions
on how to propagate journals and types of journals from the source ledger to the secondary ledger.
Reporting Currencies
Reporting currencies are the currency you use for nancial, legal, and management reporting. If your reporting currency
isn't the same as your ledger currency, you can use the foreign currency translation process or reporting currencies
functionality to convert your ledger account balances in your reporting currency. Currency conversion rules are required
to instruct the application on how to convert the transactions, journals, or balances from the source representation to
the reporting currency.
Legal Entities
Legal entities are discrete business units characterized by the legal environment in which they operate. The legal
environment dictates how the legal entity should perform its nancial, legal, and management reporting. Legal entities
generally have the right to own property and the obligation to comply with labor laws for their country. They also have
the responsibility to account for themselves and present nancial statements and reports to company regulators,
taxation authorities, and other stakeholders according to rules specied in the relevant legislation and applicable
accounting standards. During setup, legal entities are assigned to the accounting conguration, which includes all
ledgers, primary and secondary.
Balancing Segments
You assign primary balancing segment values to all legal entities before assigning values to the ledger. Then, assign
specic primary balancing segment values to the primary and secondary ledgers to represent nonlegal entity related
transactions such as adjustments. You can assign any primary balancing segment value that hasn't already been
assigned to a legal entity. You are allowed to assign the same primary balancing segment values to more than one
ledger. The assignment of primary balancing segment values to legal entities and ledgers is performed within the
context of a single accounting setup. The Balancing Segment Value Assignments report is available to show all primary
balancing segment values assigned to legal entities and ledgers across accounting setups to ensure the completeness
and accuracy of their assignments. This report lets you quickly identify these errors and view any unassigned values.
Business Units
A business unit is a unit of an enterprise that performs one or many business functions that can be rolled up in a
management hierarchy. When a business function produces nancial transactions, a business unit must be assigned
a primary ledger, and a default legal entity. Each business unit can post transactions to a single primary ledger, but it
163
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
can process transactions for many legal entities. Normally, it has a manager, strategic objectives, a level of autonomy,
and responsibility for its prot and loss. You dene business units as separate task generally done after the accounting
setups steps.
For example, if your company requires business unit managers to be responsible for managing all aspects of their part
of the business, then consider using two balancing segments, company and business unit to enable the production of
business unit level balance sheets and income statements.
Transactions are exclusive to business units. In other words, you can use business unit as a securing mechanism for
transactions. For example, if you have an export business that you run dierently from your domestic business, use
business units to secure members of the export business from seeing the transactions of the domestic business.
Scenario
You have been assigned the task of creating a primary ledger for your company Vision Corporation.
1. In the Setup and Maintenance work area, go to the following:
◦ Oering: Financials
◦ Functional Area: General Ledger
◦ Task: Manage Primary Ledger
2. Click the Create icon.
3. Complete the elds, as shown in this table.
Field Value
Currency USD
164
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Field Value
Related Topics
• Update Existing Setup Data
Note: Both primary and secondary ledgers are created in the same way and use the same user interface to
enable their specic ledger options.
165
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Field Value
166
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
To complete the intercompany accounting functionality, you must dene intercompany rules.
Note:
◦ This example describes seing options for a standard ledger. You can convert a standard ledger
to an average daily balance ledger before the rst period is opened by selecting the Enable
average balances check box on the Specify Ledger Options page.
◦ You can also convert an average daily balance ledger to a standard ledger before submiing the
Review and Submit Accounting Conguration task, provided the average daily balance ledger
wasn't created through the rapid implementation process.
Related Topics
• How Single Currency Journals Are Balanced
• How MultiCurrency Journals Are Balanced
Related Topics
• How Translated Balances Are Deleted
Note: The recommended reversal method for the journals is Change Sign.
4. If you have translated balances for the ledger, follow the process of deleting translated balances for a change in
the retained earnings account.
Related Topics
• How Translated Balances Are Deleted
167
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
168
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Related Topics
• Update Existing Setup Data
When you post a journal in a ledger that has one or more reporting currencies dened, the posting process:
• Creates journals converted to each of your reporting currencies.
• Includes them in the same batch as the original journal with a status of Posted.
Multiple dependencies exist between a reporting currency and its source ledger. Therefore, complete your period
opening tasks, daily journal or subledger level reporting currencies accounting tasks, and period closing tasks in the
correct order. The following table describes some of the tasks for each task type.
Type Tasks
Period Opening Open the accounting period in both your ledger and reporting currencies before you create
or import journals for the period. Converted journals are only generated in your reporting
currency if the period is open or future enterable.
Daily Enter daily conversion rates to convert journals to each of the reporting currencies.
Period Closing • Finish entering all regular and adjusting journals for the period in your ledger.
• Post all unposted journals in your ledger if not already done in the previous step.
• Post all unposted journals in your reporting currencies if not already done in the
previous step.
169
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Type Tasks
• Run revaluation in both your ledger and reporting currencies. Post the resulting
revaluation batches in each ledger.
• As needed, translate balances in your ledger.
• Generate needed reports from both your ledger and reporting currencies.
• Close your accounting period in both your ledger and reporting currencies.
• Create accounting.
• Post journal entries.
• Translate balances.
General Ledger and Subledger Accounting automatically generate journals in your reporting currencies where the
entered currency amounts are converted to the reporting currency amounts. Other factors used in the calculation of
reporting currency balances are listed:
• Manual Journals: Enter a manual journal batch in your reporting currency at the journal or subledger level by
using the Create Journals page. Select the journal or subledger level reporting currency from the ledger's list of
values. Continue in the same manner as entering any other manual journal.
• Conversion Rounding: Use the reporting currency functionality to round converted and accounted amounts
using the same rounding rules used throughout your Oracle Fusion Applications. The reporting currency
functionality considers several factors that are a part of the currencies predened in your applications,
including:
◦ Currency Precision: Number of digits after the decimal point used in currency transactions.
◦ Minimum Accountable Unit: Smallest denomination used in the currency. This might not correspond to
the precision.
• Converted Journals: Generate and post automatically journals in your reporting currencies when you post the
original journals in the source ledger for the following types of journals:
◦ Manual journals
◦ Periodic and allocation journals
◦ Unposted journals from non-Oracle subledger applications
◦ Unposted journals from any Oracle Fusion subledger that does not support reporting currency transfer
and import
◦ Optionally, revaluation journals
• Unconverted Journals: Rely on the subledger accounting functionality to convert and transfer Oracle Fusion
subledger journals, for both the original journal and the reporting currency journal, to the General Ledger for
import and posting. The reporting currency conversion for these journals is not performed by the General
Ledger.
• Approving Journals: Use the journal approval feature to process reporting currency journals through your
organization's approval hierarchy. You can enable journal approval functionality separately in your source
ledger and reporting currencies.
170
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Document Numbers: Accept the default document numbers assigned by the General Ledger application to your
journal when you enter a journal in your ledger. The converted journal in the reporting currency is assigned
the same document number. However, if you enter a journal in the reporting currency, the document number
assigned to the journal is determined by the reporting currency.
• Sequential Numbering: Enable sequential numbering to maintain the same numbering in your reporting
currency and source ledger for journals, other than those journals for Oracle Fusion subledgers. Do not create
separate sequences for your reporting currencies. If you do, the sequence dened for the reporting currencies
is used. The sequences can cause the document numbers not to be synchronized between the ledger and
reporting currencies.
Note: General Ledger enters a document number automatically when you save your journal if:
◦ The Sequential Numbering prole option is set to Always Used or Partially Used.
◦ Automatic document numbering sequence is dened.
If you use manual numbering, you can enter a unique document number.
• Revaluation: Run periodically revaluation in your ledger and reporting currencies as necessary to satisfy the
accounting regulations of the country in which your organization operates.
• Account Inquiries: Perform inquires in the reporting currency. You can:
◦ Drill down to the journal detail for the reporting currency balance.
◦ Drill down to see the source ledger currency journal amounts from any automatically converted journal
that was created when the original journal posted.
Note: Be careful when changing amounts in a reporting currency, since the changes are not reected in your
source ledger. Making journal entry changes to a reporting currency makes it more dicult to reconcile your
reporting currency to your source ledger. In general, enter or change your journals in your source ledger, and
then allow posting to update the reporting currency.
Note: If you use journal or subledger level reporting currencies, statistical journals are generated for your
reporting currencies, but the journals are not converted.
• Assign your business units to one primary ledger. For example, if a business unit is processing payables
invoices, then it must post to a particular ledger. This assignment is required for your business units with
business functions that produce nancial transactions.
• Use a business unit as a securing mechanism for transactions. For example, if you run your export business
separately from your domestic sales business, then secure the export business data to prevent access by the
171
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
domestic sales employees. To accomplish this security, set up the export business and domestic sales business
as two separate business units.
The Oracle Fusion Applications business unit model provides the following advantages:
• Enables exible implementation
• Provides consistent entity that controls and reports on transactions
• Shares sets of reference data across applications
Business units process transactions using reference data sets that reect your business rules and policies and can dier
from country to country. With Oracle Fusion Application functionality, you can share reference data, such as payment
terms and transaction types, across business units, or you can have each business unit manage its own set depending
on the level at which you want to enforce common policies.
Business Functions
A business function represents a business process, or an activity that can be performed by people working within
a business unit and describes how a business unit is used. The following business functions exist in Oracle Fusion
applications:
• Billing and revenue management
• Collections management
• Customer contract management
• Customer payments
172
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Expense management
• Incentive compensation
• Marketing
• Materials management
• Order fulllment orchestration
• Payables invoicing
• Payables payments
• Procurement
• Procurement contract management
• Project accounting
• Receiving
• Requisitioning
• Sales
Although there is no relationship implemented in Oracle Fusion Applications, a business function logically indicates a
presence of a department in the business unit with people performing tasks associated with these business functions.
A business unit can have many departments performing various business functions. Optionally, you can dene a
hierarchy of divisions, business units, and departments as a tree over HCM organization units to represent your
enterprise structure.
Note: This hierarchy denition isn't required in the setup of your applications, but is a recommended best
practice.
Your enterprise procedures can require a manager of a business unit to have responsibility for their prot and loss
statement. In such cases, any segment that allows the identication of associated revenue and costs can be used as a
prot center identication. The segment can be qualied as the Cost Center Segment.
However, there are cases where a business unit is performing only general and administrative functions, in which case
your manager's nancial goals are limited to cost containment or recovering of service costs. For example, if a shared
service center at the corporate oce provides services for more commercially-oriented business units, it doesn't show a
prot and therefore, only tracks its costs.
In other cases, where your managers have a responsibility for the assets of the business unit, a balance sheet can be
produced. The recommended best practice to produce a balance sheet is to setup the business unit as a balancing
segment in the chart of accounts. The business unit balancing segment can roll up to divisions or other entities to
represent your enterprise structure.
When a business function produces nancial transactions, a business unit must be assigned to a primary ledger, and a
default legal entity. Each business unit can post transactions to a single primary ledger, but it can process transactions
for many legal entities.
The following business functions generate nancial transactions and will require a primary ledger and a default legal
entity:
• Billing and revenue management
• Collections management
• Customer payments
• Expense management
• Materials management
173
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Payables invoicing
• Project accounting
• Receiving
• Requisitioning
The InFusion Air Systems division further segments your business into the System Components and Installation
Services subdivisions. Your subdivisions are divided by business units:
• System Components by products: Air Compressors and Air Transmission
• Installation Services by services: Electrical and Mechanical
Oracle Fusion applications facilitates independent balance sheet rollups for legal and management reporting by
oering up to three balancing segments. Hierarchies created using a second or third balancing segment can provide
the divisional results. For example, it's possible to dene second or third balancing segment values to correspond to
business units, and arrange them in a hierarchy where the higher nodes correspond to divisions and subdivisions, as in
the InFusion US Division example.
174
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Payables Payment
◦ Services business units that enable the Payables Invoicing business function.
◦ Processes payments for client business units.
• Customer Payments
◦ Services business units that enable the Billing and Revenue Management business function.
◦ Processes payments for the transactions of client business units assigned the Billing and Revenue
Management business function.
This functionality is used to frame service level agreements and drive security. The service provider relationships
provides you with a clear record of how your business operations are centralized. For other centralized processing,
business unit security is used (known in Oracle E-Business Suite as Multi-Org Access Control). This means that users
who work in a shared service center have the ability to get access and process transactions for many business units.
Your shared service centers provide services to your client business units that can be part of other legal entities. In such
cases, your cross charges and recoveries are in the form of receivables invoices, and not merely allocations within your
general ledger, thereby providing internal controls and preventing inappropriate processing.
For example, in traditional local operations, an invoice of one business unit can't be paid by a payment from another
business unit. In contrast, in your shared service center environment, processes allowing one business unit to
175
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
perform services for others, such as paying an invoice, are allowed and completed with the appropriate intercompany
accounting. Shared service centers provide your users with access to the data of dierent business units and can
comply with dierent local requirements.
Security
The setup of business units provides you with a powerful security construct by creating relationships between
the functions your users can perform and the data they can process. This security model is appropriate in a
business environment where local business units are solely responsible for managing all aspects of the nance and
administration functions.
In Oracle Fusion applications, the business functions your business unit performs are evident in the user interface
for seing up business units. To accommodate shared services, use business unit security to expand the relationship
between functions and data. A user can have access to many business units. This is the core of your shared service
architecture.
For example, you take orders in many businesses. Your orders are segregated by business unit. However, all of these
orders are managed from a shared service order desk in an outsourcing environment by your users who have access to
multiple business units.
Benets
In summary, large, medium, and small enterprises benet from implementing share service centers. Examples
of functional areas where shared service centers are generally implemented include procurement, disbursement,
collections, order management, and human resources. The advantages of deploying these shared service centers are
the following:
• Reduce and consolidate the number of control points and variations in processes, mitigating the risk of error.
• Increase corporate compliance to local and international requirements, providing more ecient reporting.
• Implement standard business practices, ensuring consistency across the entire enterprise and conformity to
corporate objectives.
• Establish global processes and accessibility to data, improving managerial reporting and analysis.
• Provide quick and ecient incorporation of new business units, decreasing start-up costs.
• Establish the correct balance of centralized and decentralized functions, improving decision making.
• Automate self-service processes, reducing administrative costs.
• Permit business units to concentrate on their core competencies, improving overall corporate prots.
Procurement Example
The Oracle Fusion Procurement product family has taken advantage of the service provide model by dening
outsourcing of the procurement business function. Dene your business units with requisitioning and payables
invoicing business functions as clients of your business unit with the procurement business function. Your business unit
responsible for the procurement business function takes care of supplier negotiations, supplier site maintenance, and
purchase order processing on behalf of your client business units. Subscribe your client business units to the supplier
sites maintained by the service providers, using a new procurement feature for supplier site assignment.
176
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
In the InFusion example, business unit four (BU4) serves as a service provider to the other three business units
(BU1, BU2, and BU3.) BU4 provides the corporate administration, procurement, and human resources (HR) business
functions, thus providing cost savings and other benets to the entire InFusion enterprise.
InFusion Corporation
InFusion Financial
Services Inc. InFusion UK Systems Ltd.
InFusion America Inc.
Primary Ledger Primary Ledger (GBP) with
Primary Ledger (USD)
(USD) Reporting Currency (USD)
Standard, Jan - Dec
Average Balancing Standard, Jan - Dec
May-April
BU 1 BU 2 BU 3
US Systems Fin Services UK Systems
BU 4
Corporate Administration, Procurement, and HR Shared Services Center
Note: You must select a default currency in the customer or supplier business function properties
page, if not populated automatically from the ledger assigned to the business unit in the assign
business function setup task.
177
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
In the Bill Transaction Currency to Contract Currency region, enter currency conversion details that will normally be
used, by all contracts owned by this business unit, to convert transaction amounts in the bill transaction currency to the
contract currency. Newly created contracts contain the default currency conversion values, but you can override the
values on any contract, if needed.
These options exist in two sets - one for customer billing and a second for internal billing:
• Select an invoice numbering method, either Manual or Automatic. The invoice numbering method is the
method that Oracle Fusion Receivables uses to number its invoices, upon release of draft invoices from Project
Billing.
◦ If the invoice numbering method is Manual, then select an invoice number type, which sets the type of
Receivables invoice numbers that are allowed. Valid values are Alphanumeric and Numeric.
◦ If the invoice numbering method is Automatic, then enter the next invoice number to use when
generating Receivables invoice numbers.
178
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Select the Receivables batch source to use when transferring invoices to Receivables.
If you choose the automatic numbering method, you must select a determinant level for the numbering. You must then
select the appropriate clause sequence category from document sequences that you set up for this numbering level.
179
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
the global business unit. The clauses and contract terms templates available for adoption are listed in the
administrator's Terms Library work area.
4. Adopt global clauses for new business unit
If you're creating a new local business unit and have to adopt existing global clauses, run the Adopt Global
Clauses for a New Business Unit process. Refer to the Enterprise Scheduler processes topic for more
information.
You can choose to display the clause number in front of the clause title in contracts by selecting the Display Clause
Number in Clause Title option.
If this prole option is set as No, you may see inconsistent numbering when you download the contract as the Microsoft
Word document.
1. In the Setup and Maintenance work area, go to the Manage Administrator Prole Values task.
2. On the Manage Administrator Prole Values page, search for and select the Consistent Microsoft Numbering
for Contract Terms Enabled prole option.
3. Set the prole option to Yes.
4. Save and Close.
Enter the RTF le you want used for formaing the printed clauses in the Clause Layout Template eld.
• The contract deviations report
The RTF le you select as the Deviations Layout Template determines the appearance of the contract
deviations report PDF. This PDF is aached to the approval notication sent to contract approvers.
180
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Related Topics
• How Business Unit Aects Clauses and Other Objects in the Library
• How Contract Expert Works
• Contract Printing and Layout Templates
Note: The customer must select a default currency in the customer or supplier business function properties
page, if not automatically populated from the ledger assigned to the business unit in the assign business
function setup task.
181
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
182
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
categories of global, ledger, and business unit. If clause numbering is manual, contract terms library administrators
must enter unique clause numbers each time they create a clause.
You can choose to display the clause number in front of the clause title in contracts by selecting the Display Clause
Number in Clause Title option.
If this prole option is set as No, you may see inconsistent numbering when you download the contract as the Microsoft
Word document.
1. In the Setup and Maintenance work area, go to the Manage Administrator Prole Values task.
2. On the Manage Administrator Prole Values page, search for and select the Consistent Microsoft Numbering
for Contract Terms Enabled prole option.
3. Set the prole option to Yes.
4. Save and Close.
Enter the RTF le you want used for formaing the printed clauses in the Clause Layout Template eld.
• The contract deviations report
The RTF le you select as the Deviations Layout Template determines the appearance of the contract
deviations report PDF. This PDF is aached to the approval notication sent to contract approvers.
Related Topics
• How Business Unit Aects Clauses and Other Objects in the Library
• How Contract Expert Works
• Contract Printing and Layout Templates
183
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Locations
A location identies physical addresses of a workforce structure, such as a department or a job. You create and manage
locations using the Manage Locations task in the Workforce Structures work area under My Client Groups.
You can also create locations to enter the addresses of external organizations that you want to maintain, such as
employment agencies, tax authorities, and insurance or benets carriers.
The locations that you create exist as separate structures that you can use for reporting purposes, and in rules that
determine employee eligibility for various types of compensation and benets. You enter information about a location
only once. Subsequently, when you set up other workforce structures you select the location from a list.
Location Sets
When you create a location, you must associate it with a set. Only those users who have access to the set's business unit
can access the location set and other associated workforce structure sets, such as those that contain departments and
jobs.
• You can also associate the location to the common set so that users across your enterprise can access the
location irrespective of their business unit.
• When users search for locations, they can see the locations that they have access to along with the locations in
the common set.
The following gure shows how locations sets restrict access to users.
has
access to ...
Common Set
UK
Business Unit
UK
Location Set
184
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Related Topics
• Upload Workforce Structures Using a Spreadsheet
What happens if I select a geographic hierarchy node when I create or edit a location?
The calendar events that you created for the geographic node start to apply for the location and may impact the
availability of worker assignments at that location. You manage locations using the Manage Locations task in the
Workforce Structures work area.
The geographical hierarchy nodes available for selection on the Locations page display from a predened geographic
hierarchy.
Related Topics
• How an Individual's Schedule Is Determined
185
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
These organizations can be included in many alternative hierarchies and used for reporting, as long as they have
representation in the chart of accounts.
Divisions
A division refers to a business-oriented subdivision within an enterprise, in which each division organizes itself
dierently to deliver products and services or address dierent markets. A division can operate in one or more
countries, and can be many companies or parts of dierent companies that are represented by business units.
A division is a prot center or grouping of prot and cost centers, where the division manager is responsible for
achieving business goals including prots. A division can be responsible for a share of the company's existing product
lines or for a separate business. Managers of divisions may also have return on investment goals requiring tracking of
the assets and liabilities of the division. The division manager generally reports to a corporate executive.
By denition a division can be represented in the chart of accounts. Companies can use product lines, brands, or
geographies as their divisions: their choice represents the primary organizing principle of the enterprise.
Historically, divisions were implemented as a node in a hierarchy of segment values. For example, Oracle E-Business
Suite has only one balancing segment, and often the division and legal entity are combined into a single segment where
each value stands for both division and legal entity.
186
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Scenario
You are part of a senior management team at InFusion Corporation. InFusion is a global company with organizations in
the following countries:
• United States (US)
• United Kingdom (UK)
• France
• China
• Saudi Arabia
• United Arab Emirates (UAE)
The company's main area of business is in the high tech industry, and it recently acquired a new company. You must
analyze the company's current enterprise structure and determine the new organizations to create in the new company.
Analysis
The following table summarizes the key decisions that you must consider when determining what new organizations to
set up and how to structure the enterprise.
Create location? The Financial Services company and its departments are based in Frankfurt. Therefore, you
only have to create one location.
Create separate division? Yes. Although the new division will exist in the current enterprise structure, you want to
keep the Financial Services company as a separate line of business. By creating a separate
division, you can manage the costs and reporting separately from the InFusion Corporation.
Additionally you don't have to modify any organizations in the enterprise setup.
Create business unit? Yes. The Financial Services business requires you to create several jobs that don't exist in your
high tech business. You can segregate the jobs that are specic to nancial services in a new
business unit.
How many departments? The Financial Services company currently has departments for sales, accounting, and
marketing. As you have no plans to downsize or change the company, you can create three
departments to retain the structure.
187
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
How many cost centers? Although you can have multiple cost centers to track the department costs, you decide to
create one cost center for each department.
• Record assets
• Record liabilities
• Record income
• Pay transaction taxes
• Perform intercompany trading
You must dene the legal entity as a legal employer and payroll statutory unit. As the new
division operates only from Germany, you can congure the legal entity to suit Germany's legal
and statutory requirements.
Note: You can identify the legal entity as a payroll statutory unit. When you
do so, the application transfers the legal reporting unit associated with the
legal entity to Oracle Fusion HCM as a tax reporting unit.
Create legislative data group? Yes. Because you currently don't employ or pay people in Germany, you must create one
legislative data group to run payroll for the workers in Germany.
188
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
The following gure illustrates the structure of InFusion Corporation after adding the new division and the other
organizations.
InFusion
Corporation
Tax
Business Unit Reporting
Unit
Legislative
Data
Group
189
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
A cost center represents the smallest segment of an organization for which you collect and report costs. A department is
an organization with one or more operational objectives or responsibilities that exist independently of its manager and
has one or more workers assigned to it.
Cost Centers
A cost center represents the destination or function of an expense rather than the nature of the expense which is
represented by the natural account. For example, a sales cost center indicates that the expense goes to the sales
department.
A cost center is generally aached to a single legal entity. To identify the cost centers within a chart of accounts
structure use one of these two methods:
• Assign a cost center value in the value set for each cost center. For example, assign cost center values of
PL04 and G3J1 to your manufacturing teams in the US and India. These unique cost center values allow easy
aggregation of cost centers in hierarchies (trees) even if the cost centers are in dierent ledgers. However, this
approach requires dening more cost center values.
• Assign a balancing segment value with a standardized cost center value to create a combination of segment
values to represent the cost center. For example, assign the balancing segment values of 001 and 013 with
cost center PL04 to represent your manufacturing teams in the US and India. This creates 001-PL04 and 013-
PL04 as the cost center reporting values. The cost center value of PL04 has a consistent meaning. This method
requires fewer cost center values to be dened. However, it prevents construction of cost center hierarchies
using trees where only cost center values are used to report results for a single legal entity. You must specify a
balancing segment value in combination with the cost center values to report on a single legal entity.
Departments
A department is an organization with one or more operational objectives or responsibilities that exist independently of
its manager. For example, although the manager may change, the objectives don't change. Departments have one or
more workers assigned to them.
A manager of a department is typically responsible for:
• Controlling costs within their budget
• Tracking assets used by their department
• Managing employees, their assignments, and compensation
The manager of a sales department may also be responsible for meeting the revenue targets.
The nancial performance of departments is generally tracked through one or more cost centers. In Oracle Fusion
Applications, departments are dened and classied as Department organizations. Oracle Fusion Human Capital
Management (HCM) assigns workers to departments, and tracks the headcount at the departmental level.
The granularity of cost centers and their relationship to departments varies across implementations. Cost center
and department conguration may be unrelated, identical, or consist of many cost centers tracking the costs of one
department.
Department Classications
A department can be classied as a project organization, sales and marketing organization, or cost organization.
Oracle Fusion Human Capital Management (HCM) uses trees to model organization hierarchies. It provides predened
tree structures for department and other organizational hierarchies that can include organizations with any
classication.
190
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Project Organization
Classify departments as a project owning organization to enable associating them with projects or tasks. The project
association is one of the key drivers for project access security.
In addition, you must classify departments as project expenditure organizations to enable associating them to project
expenditure items. Both project owning organizations and project expenditure organizations can be used by Oracle
Fusion Subledger Accounting to derive accounts for posting Oracle Fusion Projects accounting entries to Oracle Fusion
General Ledger.
The following gure illustrates a management hierarchy, in which the System Components Division tracks its
expenses in two cost centers, Air Compressors and Air Transmission. At the department level, two organizations with a
classication of Department are dened, the Marketing Department and Sales Department. These two departments can
be also identied as a Resource Organizations, which enable assigning resources, such as salespeople, and other sales
specic information to them. Each department is represented in the chart of accounts by more than one cost center,
enabling granular as well as hierarchical reporting.
Air Air
Compressors Transmission
Business Unit Business Unit
Sales Marketing
Department Department
US East US West
Cost Center Cost Center
191
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Cost Organization
Oracle Fusion Costing uses a cost organization to represent a single physical inventory facility or group of inventory
storage centers, for example, inventory organizations. This cost organization can roll up to a manager with
responsibility for the cost center in the nancial reports.
A cost organization can represent a costing department. Consider this relationship when determining the setup of
departments in HCM. No system dependencies are required for these two entities, cost organization and costing
department, to be set up in the same way.
Related Topics
• What's a job set
Basic Details
Basic details for a job include an eective start date, a job set, a name, and a code.
A job code must be unique within a set. Therefore, you can create a job with the code DEV01 in the US set and another
job with the same code in the UK set. However, if you create a job with the code DEV01 in the Common set, then you
can't create a job with the same code in any other set.
Benchmark Information
You can identify a job as being a benchmark job. A benchmark job represents other jobs in reports and salary surveys.
You can also select the benchmark for jobs. Benchmark details are for informational purposes only.
192
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Progression Information
A progression job is the next job in a career ladder. Progression jobs enable you to create a hierarchy of jobs and are
used to provide the list of values for the Job eld in the Promote Worker and Transfer Worker tasks.
The list of values includes the next three jobs in the progression job hierarchy. For example, assume that you create
a job called Junior Developer and select Developer as the progression job. In the Developer job, you select Senior
Developer as the progression job. When you promote a junior developer, the list of values for the new job will include
Developer and Senior Developer. You can select one of these values, or select another one.
Evaluation Criteria
You can dene evaluation criteria for a job, including the evaluation system, a date, and the unit of measure for the
evaluation system.. The Hay system is the predened evaluation system that's available. An additional value of Custom
is included in the list of values for the Evaluation System eld, but you must add your own criteria and values for this
system.
Related Topics
• Job and Position Lookups
• Guidelines for Using Desktop Integrated Excel Workbooks
• Considerations for Enforcing Grades at Assignment Level
Examples of Jobs
Jobs are typically used without positions by service industries where exibility and organizational change are key
features.
Software Industry
For example, XYZ Corporation has a director over the departments for developers, quality assurance, and technical
writers.
• Recently, three developers have resigned from the company.
• The director decides to redirect the headcount to other areas.
193
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Instead of hiring all three back into development, one person is hired to each department, quality assurance,
and technical writing.
In software industries, the organization is uid. Using jobs gives an enterprise the exibility to determine where to use
headcount, because the job only exists through the person performing it. In this example, when the three developers
leave XYZ Corporation, their jobs no longer exist, therefore the corporation has the exibility to move the headcount to
other areas.
XYZ Corporation
Technology
Department
Quality Assurance
Developer Technical Writer
Specialist
Job Titles
194
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Begin by creating shifts and then assigning those shifts to workday paerns. Next, create a schedule that's a collection
of workday paerns and any exception dates.
Schedule
Exceptions
Shift
A shift is a period of time, typically expressed in hours, and it can be dened by a start time and an end time, or a
duration. A shift can be for a work period or an o period. You can create time, duration, and elapsed shifts.
195
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Workday Paern
A workday paern is a collection of shifts for a specic number of days. You can create time, duration, and elapsed
workday paerns.
Exception
An exception is a record of a date that overrides the availability of a resource to which a schedule has been assigned.
For example, a resource is assigned a schedule that includes December 25 as a working day. An exception can be
created for December 25 and applied to that schedule to override resource availability for that date. Exceptions can also
be for a date time period such as 9 a.m. to 11 a.m. on December 25th.
Schedule
A schedule is dened by a start date, an end date, and a sequence of workday paerns to be followed between those
dates. A schedule can also contain exception dates that override the availability of resources to which the schedule is
assigned. Quarter types such as 4-4-5, 4-5-4 are supported.
196
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
should create a duration shift that indicates that resources are available for 24 hours, and create a second duration shift
that indicates that resources aren't available for 24 hours.
• Item management
• Item and inventory management
197
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Item Management
Inventory organizations used for item management, which are the same as item organizations, store only denitions
of items. Use inventory organizations for item management when the storage or movement of inventory doesn't need
to be physically or nancially tracked. For example, in a retail implementation you can create an inventory organization
for item management to store the names of items that are listed by and sold through each retail outlet, while a
dierent system tracks physical inventory and transactions. If it's necessary in the future, you can change an inventory
organization's usage from item management to item and inventory management in the inventory organization's
properties.
• Managed by a business unit, with the materials management business function enabled.
• Mapped to a legal entity and a primary ledger.
• Manufacturing facilities
• Storage facilities
Storage and manufacturing facilities are related to other organizational entities through a business unit that stores,
manufactures, and distributes goods through many factories, warehouses, and distribution centers. The material
parameters are set for both the facilities, enabling movement of material in the organization. This business unit has the
business function of Materials Management enabled. Oracle Fusion Applications permit many inventory organizations
to be assigned to one business unit.
198
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
In the following gure the two business units, Air Compressors and Air Transmission, share one distribution center
in Atlanta. The two inventory organizations, Air Compressors and Air Transmission represent the inventory for each
business unit in the Atlanta distribution center and are both assigned the Atlanta location.
Air Air
Compressors Transmission
Business Unit Business Unit
Distribution
Center
Location Atlanta
This gure illustrates the inventory owned by InFusion Air Quality legal entity. The InFusion Air Quality legal entity
is associated with the Air Compressors business unit, which is associated with the two Air Compressors inventory
199
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
organizations. Therefore, InFusion Air Quality legal entity owns the entire inventory in both the Dallas and Atlanta
locations.
Air InFusion
Compressors Air Quality Legal
Business Unit Entity
The default legal entity assigned to the business unit must be the
same as the legal entity assigned to the inventory organization.
200
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
• Whether to congure locator control and if so, the level at which to enforce the locator control
• How you want to congure movement request seings such as pick slip batch size and replenishment
movement request grouping
Consider the size of your operation, your usage of subinventories, and the type of labor or equipment required
when considering whether you want to use organization- or subinventory-level replenishment movement
request grouping.
• How you want to congure lot, serial, and packing unit generation seings
To make appropriate choices for these seings, you should be familiar with:
◦ Your company's guidelines for creating lot names, serial numbers, and packing unit numbers
◦ Whether your company requires you to assign the same lot number to multiple items in the same
organization, or a specic lot number to only one item in the same organization
◦ Whether your company requires you to lot control purchase order or shipping order material
• How you want to congure item sourcing details, such as the picking rule to use, and whether to specify the
inventory organization as a logistics services organization
• The seing that you select for the Round Order Quantity parameter on the Manage Inventory Organization
Parameters page, General tab, of the inventory organization containing the item subinventory
• The value that you specify for the Fixed Lot Multiple text box on the Add Item to Subinventory window
How Rounding the Reorder Quantity Aects Min-Max Planning Reorder Quantity
Calculations
If you enable rounding the reorder quantity for the inventory organization, and specify the xed lot multiple for the
item subinventory, the reorder quantity is rounded up. If you disable rounding the reorder quantity for the inventory
organization, and specify the xed lot multiple for the item subinventory, the reorder quantity is rounded down.
Note: To round reorder quantities, you must specify a xed lot multiple.
201
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Select one of these lot number uniqueness control options to apply to the items in your inventory organization:
• No uniqueness control
• Across items
When you perform transactions, Oracle Fusion Inventory Management checks the lot number uniqueness control to
generate lot numbers.
No Uniqueness Control
Choose this option if you don't want to establish lot number uniqueness. When selected, you can assign the same lot
number to multiple items in the same organization and across organizations. Organizations that choose No uniqueness
control can enter any lot as long as the lot doesn't exist in any organization that's set to Across items.
Across Items
Choose this option to control lot number uniqueness across items. With this option, you can assign a specic lot
number to only one item in the same organization and across organizations. The application veries that the lot number
doesn't exist for any other item in any other organization.
202
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
It is important to understand that when you use this seing for an organization, the same lot number can't exist for any
other item in any other organization. However, it's possible to have the same item with the same lot number in multiple
organizations.
Note: You can change the seing for the lot number uniqueness control at the inventory organization level if
there are no open transactions.
203
Oracle Procurement Cloud Chapter 6
Implementing Procurement Enterprise Structures for Procurement
Item Master
Inventory Organization
Holds definition of all items
and tracks transactions.
Item Master
Item Organization
Holds definition of all items and
does not track transactions.
Catalog Catalog
Air Compressors Air Compressors
US West Sales US East Sales
Item Organization Item Organization
Note: Oracle Fusion permits multiple item masters, however, use this capability cautiously. If you acquire
a company, there may be value in keeping the old item master for a transition period. If you manage your
subsidiaries as separate businesses, there may be reduced value in a single item master.
204
Oracle Procurement Cloud Chapter 7
Implementing Procurement Budgetary Control and Encumbrance Accounting
You dene the funds reservation point for documents at the business unit level. In the Procure-to-Pay Business
Functions section, you can set the reservation point for the Requisitioning and Procurement business functions. For a
business function, set the reservation point to one of these options:
The following are key aributes to dene when you set up a control budget to allow insucient funds override:
• Allow overrides: Select this option to enable funds override for the control budget.
• Maximum Override Amount: Enter the maximum total override amount for the control budget.
◦ You can also select options to notify the budget manager when overrides are taken, or when no overrides
are available.
• User Assignments: Add a line to the table for each override approver, and enter their user name.
• Type: For the override type for the approver, select Insucient Funds. For requisitions and purchase orders
only the Insucient Funds value is supported.
205
Oracle Procurement Cloud Chapter 7
Implementing Procurement Budgetary Control and Encumbrance Accounting
• Amount: Enter an override authorization amount for the approver. The amount is compared against the
override amount required by each distribution, rather than for the whole purchasing document. The amount is
used to select the override rule and approver used for a particular transaction.
• Transaction Type: Select the transaction types the approver has funds override authority for. For example:
Requisition, or Purchase Order.
Related Topics
• How You Manage Funds Override Approval Rules for Requisitions and Purchase Orders
206
Oracle Procurement Cloud Chapter 8
Implementing Procurement Security for Procurement
Overview of Security
Oracle Enterprise Resource Planning Cloud (Oracle ERP Cloud) and Oracle Supply Chain Management Cloud (Oracle
SCM Cloud) are secure as delivered; they limit access to one initial setup user. To enable application users to access
application functions and data, you perform security-related tasks in these areas, as appropriate:
• Dene Security for Financials
• Dene Security for Procurement
• Dene Users and Security for Product Management
• Dene Security for Project Execution Management
• Manage Data Access for Users
• Dene Security for Supply Chain Management
For more information on ERP and SCM security setup and task instructions, see these guides:
• Oracle Enterprise Resource Planning Cloud: Securing Oracle ERP Cloud.
• Oracle Supply Chain Management Cloud: Securing Oracle SCM Cloud.
Note: You can perform these tasks both during implementation, and later as requirements come up.
To do these tasks, a user must have the IT Security Manager or Application Implementation Consultant job role.
Manage Duties
The Oracle ERP Cloud and Oracle SCM Cloud security reference implementations provide many predened duty roles.
Use the Manage Duties task to do the following:
• Review the duties of a job or abstract role.
• Manage the duties of a custom job or abstract role.
• Create custom duty roles.
207
Oracle Procurement Cloud Chapter 8
Implementing Procurement Security for Procurement
To do these tasks, a user must have the IT Security Manager job role.
For such tasks, a user must have the IT Security Manager job role.
Note: You can perform this task after you set up and congure Oracle Social Network. If you don't use Oracle
Social Network, you can skip this task.
208
Oracle Procurement Cloud Chapter 8
Implementing Procurement Security for Procurement
By default, these roles are assigned to predened job roles, so if you have one of those job roles, you're usually good to
go.
There are a couple of predened roles for workow administration that aren't specic to a product family:
◦ Provides a bit more administration access than the product family roles
◦ Is assigned by default to at least one predened job role for most product families
Predened Roles
Here are the predened roles that give access to workow administration, and the predened job roles that they're
assigned to.
209
Oracle Procurement Cloud Chapter 8
Implementing Procurement Security for Procurement
Incentive Compensation
Application Administrator
(ORA_ CN_ INCENTIVE_
COMPENSATION_
ADMINISTRATOR_ JOB)
Marketing Analyst (ORA_
MKT_ MARKETING_
ANALYST_JOB)
Marketing Manager (ORA_
MKT_ MARKETING_
MANAGER_JOB)
Marketing Operations
Manager (ORA_ MKT_
MARKETING_ OPERATIONS_
MANAGER_JOB)
Marketing VP (ORA_ MKT_
MARKETING_ VP_JOB)
Procurement Application
Administrator (ORA_
PO_ PROCUREMENT_
APPLICATION_ ADMIN_JOB)
Project Application
Administrator (ORA_ PJF_
PROJECTS_ APPLICATION_
ADMINISTRATOR_ JOB)
Sales Lead Qualier (ORA_
MKL_ SALES_ LEAD_
QUALIFIER_ JOB)
Supply Chain Application
Administrator (ORA_
RCS_ SUPPLY_ CHAIN_
APPLICATION_
ADMINISTRATOR_ JOB)
Human Capital Management BPM Workow Human Capital BPMWorkowHCMAdmin Human Capital Management
Management Application Administrator
(ORA_ HRC_ HUMAN_
CAPITAL_ MANAGEMENT_
210
Oracle Procurement Cloud Chapter 8
Implementing Procurement Security for Procurement
APPLICATION_
ADMINISTRATOR_ JOB)
211
Oracle Procurement Cloud Chapter 8
Implementing Procurement Security for Procurement
Supply Chain Management BPM Workow Supply Chain BPMWorkowSCMAdmin Supply Chain Application
Administrator Administrator (ORA_
RCS_ SUPPLY_ CHAIN_
APPLICATION_
ADMINISTRATOR_ JOB)
• If your administrators manage workow for multiple product families, you or your security administrator should
give those users a custom role with the appropriate family-specic roles added.
• If your administrators manage workow for all product families, give them a custom role with BPM Workow All
Domains Administrator Role.
Caution: Assign BPM Workow All Domains Administrator Role only if your administrators really do
need access to workow tasks from all product families. For access in multiple product families, but
not all, use the roles for the corresponding families instead.
• All administrators can see to-do tasks, no maer which role they have for workow administration.
• Only administrators with either BPM Workow All Domains Administrator Role or BPM Workow System Admin
Role would have Skip Current Assignment as an action to take on workow tasks.
Related Topics
• Assign Roles to an Existing User
• Edit Job and Abstract Roles
• Role Copying or Editing
• Actions and Statuses for Workow Tasks
212
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Task Conguration
Manage rule sets and rules that control approval ows.
• To congure a predened approval policy, select the predened rule set and click the Edit Task icon.
• To disable a predened rule set, select the Ignore participant check box for that rule set.
• To edit the rules within a predened rule set, you can insert, update, or delete while in edit mode.
• You can congure a specic rule to automatically approve a task without sending it to any approver.
◦ Modify the routing for that rule so that it is sent to the initiator (which means the requestor is the
approver).
Approval Groups
Each approval group includes a set of users that you congure to act on tasks in a certain paern. Tasks can be dened
to get routed to an approval group instead of an individual user.
• You can nest approval groups within approval groups.
• You have two options for dening the group:
213
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
◦ Dynamic: Provide the logic to use to determine the users in the group.
Related Topics
• Congure Oerings
• Update Existing Setup Data
The prole options with a smaller scope take precedence. For example, you have prole option A with a global scope
and prole option B with a product scope. If you're currently conguring notications for a particular product, use
prole option B to adjust the refresh time just for that product. But based on prole option A, the refresh is still at 24
214
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
hours for all other congurable notications in all other products. Prole option B takes precedence over prole option
A only for that one product.
Tip: To nd the product family or product code, go to the Setup and Maintenance work area. Use the Manage
Taxonomy Hierarchy task in the Application Extensions functional area for any oering. In the hierarchy,
expand the root node and then the Oracle Fusion node. Find the row for the family or product and look in the
Module Key column for the code.
1. In the Setup and Maintenance work area, go to the Manage Applications Core Prole Options task in the
Application Extensions functional area for your oering.
2. On the Manage Applications Core Prole Options page, click the New icon.
3. On the Create Prole Option page, enter the prole option code in the format that corresponds to the scope
you want.
4. Enter a display name that you can easily remember to help you nd the prole option later.
5. From the Application list, select Oracle Middleware Extensions for Applications.
6. From the Module list, select Application Core.
7. Specify a start date.
8. Click Save and Close.
9. On the Manage Applications Core Prole Options page, make sure your new prole option is selected in the
Search Results: Prole Options subsection.
10. In the <Prole Option>: Prole Option Levels subsection, select the Enabled and Updatable check boxes for
the Site level.
11. Save your work.
When you're done making and testing your changes, set the prole option back to 1440, which is 24 hours in minutes.
If you forget and leave your prole option as is for longer than eight hours, don't worry! At that point, the prole option
resets itself back to 1440 minutes.
Related Topics
• Update Existing Setup Data
• Set Prole Option Values
• Modules in Application Taxonomy
215
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Note: Make sure you select an aribute that gives you user IDs at runtime, the IDs that
users enter to sign in to the application.
• If you have seings at both the participant and task level, both would apply.
• If there's any conict, for example with the seing of the Reassign approvals to those users' managers check
box, the participant level seing takes precedence.
216
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
• It reassigns the direct reports of a terminated manager to that person's line manager and also assigns any
pending notications to the line manager. Only actionable notications will be reassigned.
• It reassigns pending approval notications based on the number of days you specify using the Past Period in
Days Considered for Reassigning Pending Approvals parameter.
Related Topics
• Submit Scheduled Processes and Process Sets
Overall Process
To set the due date, expiration policies, or both:
217
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
218
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
1. In the Expiration Seings section of the Deadlines subtab, specify a duration and optionally select the Exclude
Saturday and Sunday check box. For example, if you enter 30 days and select the check box, then:
◦ For sequential routing, the task expires if the last assignee doesn't act on the task within 30 weekdays
after the task is routed to that assignee. If the rst assignee doesn't act in 30 weekdays, the task is passed
to the next assignee, who gets another 30 weekdays. And so on, until the last assignee.
◦ For parallel routing, the task expires if the current assignees don't act on the task within 30 weekdays
after the task is assigned.
2. If you want tasks to get escalated or renewed after they expire, select the Escalate or Renew option. Otherwise,
leave the Expire only option selected.
3. To escalate, indicate how many times the approval escalates up the management chain. For example, you enter
2 in the Maximum Escalation Levels eld. When the task expires:
◦ For sequential routing, the task is routed to the manager (User 2) of the last assignee (User 1).
◦ For parallel routing, the task is routed to the managers (User 2) of all current assignees (User 1).
When User 2 doesn't act within 30 weekdays, then the task is escalated to the manager of User 2, who has
another 30 weekdays before the task goes into a nal Expired status.
4. To renew, indicate how many times the task can get renewed. For example, you enter 2 in the Maximum
Renewals eld. When the task expires:
1. In the Expiration Seings section of the Deadlines subtab, specify a duration and optionally select the Exclude
Saturday and Sunday check box. For example, if you enter 30 days and select the check box, then the task
expires if not all approvals are done 30 weekdays after the task is routed to the rst assignee. If there are three
assignees and the rst two take 25 weekdays to act, then the last assignee only gets 5 weekdays.
2. If you want tasks to get escalated or renewed after they expire, select the Escalate or Renew option. Otherwise,
leave the Expire only option selected.
3. To escalate, indicate how many times the approval escalates up the management chain.
For example, you enter 2 in the Maximum Escalation Levels eld and select Director in the Highest Approver
Title eld. When the task expires, it's routed to the manager (User 2) of the current assignee (User 1). When
User 2 doesn't act within 30 weekdays, then:
◦ If User 2 isn't a director, the task is escalated to the manager of User 2, who has another 30 weekdays
before the task goes into a nal Expired status.
◦ If User 2 is a director, then the task goes into a nal Expired status.
4. To renew, indicate how many times the task can get renewed. For example, you enter 2 in the Maximum
Renewals eld. When the task expires, all pending assignees get another collective 30 weekdays to act. If they
don't all act within that period, then the task is renewed for another 30 weekdays. If the task still isn't complete
in that time, then it goes into a nal Expired status.
219
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
• The seing applies only to email notications that are sent as part of workow tasks, not to all emails in
general.
• Users can still nd their workow tasks in the Worklist: Notications and Approvals work area.
◦ All: Email notications are enabled. Workow notications are included in the global header. This is the
default value.
◦ None: Email notications and workow notications in the global header are disabled.
◦ Email: Only email notications are enabled. New workow notications won't appear in the global header.
◦ In-app: Workow notications in the global header are enabled. Email notications are no longer sent.
Note: If you or another administrator has selected news feed as the default home page layout,
then users also get notications in the Things to Finish section on the home page, as well as the
Notications page. The same mode seing that applies to the notications in the global header also
applies to the Things to Finish section and the Notications page.
5. Click Save.
220
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Note: If you or another administrator has selected news feed as the default home page layout, then users
also get notications in the Things to Finish section on the home page, as well as the Notications page.
The scheduled process also applies to notications in these UIs. For example, the Things to Finish section
automatically reects changes made in the global header, but not changes made through email until the
scheduled process runs.
If the news feed home page layout is selected, then after synchronization, the notication:
The scheduled process doesn't update the title of notications in the global header. Similar to email subjects, the
notication titles are static.
Related Topics
• Submit Scheduled Processes and Process Sets
• Make notication secure (exclude details): Exclude business transaction details in email notications.
• Hide End User Web URL in notications: Remove the default rst line in the email body: Access this task in
the Workspace Application or take direct action using the links in this email. This line includes a link that opens
BPM Worklist. It is recommended to select this check box.
• Make notication actionable: Include links in email notications that users can click to directly take action, for
example to approve or reject.
• Send task aachments with email notications: Include les aached to the task as aachments in the email
notications.
221
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
1. Navigate to the Notications subtab in BPM Worklist for the task you want to edit.
2. Click the Add Notication icon to enable additional notication scenarios, or edit existing rows directly.
a. In the Task Status column, select when to send the notication, for example when the task has expired.
Aside from the actions or statuses available to end users, you can also select any of the following:
• Alerted: Usually, an error condition that can be xed. The task is assigned to the error assignee, or
someone else if the task doesn't have error assignees.
• Update: Whenever the task is updated, for example by adding a comment or aachment, without
aecting the approval status or routing.
• Update Outcome: Whenever the outcome of the task is updated, for example approved or
rejected.
• All other actions: Any action that's not already in the list of values.
b. In the Recipient column, select whom to notify.
• Assignees: The users or groups whom the task is currently assigned to.
• Initiator: The user who created the task.
• Approvers: The users who already approved the task as part of a sequential approval chain.
• Owner: The task owner, who's responsible for the business process that the task is related to.
• Reviewer: The user who can only add comments and aachments to a task.
3. To disable specic notication scenarios, select a row and click the Delete Notication icon.
4. Click the Save icon in the Tasks to be congured toolbar.
222
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
The following gure shows the table on the Notications subtab with predened scenarios for a workow task. In
this example, notications are sent to assignees whenever the task is assigned to them. The task initiator also gets a
notication when the task is complete, and administrators are notied if the task results in error.
Set Up Reminders
To send reminders in addition to the dened notication scenarios:
Related Topics
• Actions and Statuses for Workow Tasks
• Dene People to Support Workow Tasks
223
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
For some workow tasks, you can enable congurable email notications based on report layouts to be used instead of
the standard email notications. The Notication Header seing doesn't apply to those congurable email notications.
1. In the Setup and Maintenance work area, go to the Manage Task Congurations task or another approval setup
task in the Application Extensions functional area or another functional area.
2. In BPM Worklist, on the Task Conguration tab, select the workow task.
3. Click the Edit task icon in the Tasks to be congured toolbar.
4. Open the Notications subtab.
5. For the specic notication scenario on the Notications subtab, click the icon in the Notication Header
column.
6. In the Edit Notication Message dialog box, delete any existing content and enter the following in the
Notication Message eld.
◦ For company name: Enter text in single quotes, for example 'Oracle'. You can also use HTML
formaing, for example '<h2>Oracle</h2>'.
◦ For company logo: Enter the URL to your logo, following this syntax: '<img src="https://
cloud.oracle.com/res/images/header/oracle-cloud-logo.png" width="230" height="69" alt="Oracle
Logo">'.
Replace the URL and alternative text with your own.
7. Click the Save icon in the Tasks to be congured toolbar.
You can set up the sender name in application preferences for all workow tasks, or have dierent setup for specic
workow tasks. If not specied at the task level, the sender name seing defaults from the preferences.
224
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
◦ Select to specify the text to display. Enter your value or leave blank if you want nothing to appear in the
From eld.
◦ Select Submier to show the person who created the task.
◦ Select Previous Approver to show the previous assignee in the approval chain. When the notication is
sent to the rst assignee in the approval chain, the From eld shows the person who created the task.
3. Click Save.
225
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
1. In the Setup and Maintenance work area, go to the Manage Task Congurations task or another approval setup
task in the Application Extensions functional area or another functional area.
2. In BPM Worklist, on the Task Conguration tab, select the workow task.
3. Click the Edit task icon in the Tasks to be congured toolbar.
4. Open the Notications subtab.
5. On the Notications subtab, click the Expand More icon.
6. Select one of the Email "From:" Display Name options.
◦ Select Not Applicable so that what appears in the From eld depends on the application preferences
that apply to all workow tasks.
◦ Select to specify the text to display. Enter your value in quotes, for example "Oracle", or leave blank if
you want nothing to appear in the From eld.
◦ Select Previous Approver to show the previous assignee in the approval chain. When the notication is
sent to the rst assignee in the approval chain, the From eld shows the person who created the task.
7. Click the Save icon in the Tasks to be congured toolbar.
226
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Procurement business ows with congurable notications include the following workow tasks:
• Negotiation invitation
• Purchase order approval
• Purchase order change order approval
• Requisition approval
• Requisition reapproval (change to lines by requester, change to lines by buyer)
• Seller negotiation award decision
• Seller negotiation bid disqualication
• Seller negotiation change schedule
• Seller negotiation invitation
• External Supplier Registration Approval Decision
In addition to geing notications in email, users can also view in-application notications by:
• Clicking the Notications icon in the global header and opening a notication.
• Going to the Worklist: Notications and Approvals work area and opening a notication.
• Clicking the In-App Notication link at the end of an email notication.
227
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Process Overview
The process to generate congurable email and in-application notications is the same as generating other types of
report output. The process involves various types of objects in the business intelligence catalog, including data models,
subtemplates, style templates, and reports.
This gure shows how these objects work together to generate the output used for email and in-application
notications.
• Data Source: Stores the aributes and aribute values for business objects and transactions in the application
• Data Model: Determines which aributes from data sources are available to be included in the notication and
how that data is retrieved
• Subtemplate: Provides common components, for example a branding logo and buons, that can be reused in
multiple reports
• Style Template: Provides styles, such as the type of lines and fonts to use in tables, or the font type, size, and
color to use for headings
• Report: Contains a layout template that determines:
◦ Which aributes appear in the notication, from the data model used for the report
◦ What the notication looks like, using components from the subtemplate and styles from the style
template used for the report
• HTML: Is the output generated from the report
• Email Notication: Is sent to users as part of a business ow, with the HTML output embedded in the email
body
• In-Application Notication: Has the HTML output embedded in the application user interface
228
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Each workow task with congurable notications has a corresponding predened report in the BI catalog. For example,
the Requisition Approval Email Report contains the Requisition Approval Email Layout and uses the Requisition
Approval Email Data Model. The generated output is included in emails that are sent to users for requisition approval.
Notication Modications
After you enable congurable workow notications, the predened reports and related objects in the BI catalog work
by default. The report-based notications provide the same information as the standard notications, but in a format
optimized for mobile devices. To modify the notications, you can edit copies of the predened reports, data models,
and subtemplate (but not the style template). You proceed as you would to edit any report, data model, or subtemplate
in the catalog, for example:
1. Find a predened report for procurement in the BI catalog.
2. Use the Customize option to create a copy, or copy the report and paste it within the Custom folder.
3. Edit the copied report layout template.
Note: The congurable, report-based notications are delivered in a format optimized for mobile devices.
If your organization has approvers using mobile devices, minimize making modications that increase the
number of columns in tables, and test all such modications thoroughly on applicable mobile devices before
deploying the changes.
For more information about creating and editing reports, see the Oracle Procurement Cloud Creating and Administering
Analytics and Reports guide, available on the Oracle Help Center. You should get familiar with BI Publisher in general
before modifying congurable notications. Aspects specic to congurable notications include:
• You use only the Template Builder for Word add-in to edit the .rtf template in Microsoft Word, not the layout
editor or other tools available for creating and editing report layout.
• You usually edit a copy of predened layout templates, rather than create reports or layout templates.
Security
To modify reports and data models for workow notications, you must have the BI Administrator role.
Setup
If required, use the Oerings work area, Procurement oering to enable the congurable notications feature.
• Congure Negotiation Invitation Notication with Business Intelligence Publisher, found in the Sourcing
functional area
Also. download and install the Template Builder for Word add-in.
Related Topics
• Set Up for RTF and Excel Report Layout Templates
• Congurable Email Notications: Implementation Considerations
• Overview of Workow Tasks
• More About Oracle Business Intelligence Components
229
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Purchasing Purchase Order Notication Report Purchase Order Notication Data Model
Self Service Procurement Requisition Approval Email Report Requisition Approval Email Data Model
Sourcing Seller Negotiation Change Schedule Seller Negotiation Change Schedule Data
Notication Report Model
Sourcing Seller Negotiation Invitation Notication Seller Negotiation Invitation Data Model
Report
Suppliers External Supplier Registration Rejected FYI External Supplier Registration Rejected
Email Report Email Data Model
230
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Suppliers External Supplier Registration Request To External Supplier Registration Email Data
Resubmit Email Report Model
Suppliers External Supplier Registration Save for External Supplier Registration Email Data
Later Email Report Model
For each of these listed business process areas, you can use the associated reports and data models to congure both
email and in-application notications.
231
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
General Structure
In general, the workow notications contain a set of components that are displayed in a certain order.
The callouts in this gure identify the email notication components listed in the following table.
The callouts in this gure identify the in-app notication components listed in the following table. In addition to
describing each component, the table also indicates if the component appears in the email notication, in-app
notication, or both.
232
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
1 In-app
Buons with the primary actions to
take on the task, such as Approve and
Reject. These buons aren't part of the
congurable, report-based notication
content.
3 Email
Buons for the primary actions to take on
the task, such as Approve and Reject.
233
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
When you modify notications, try to keep to this general structure and don't remove essential elements such as the
action buons. Likewise, don't change the styles in your layout template. The predened style template should still
apply to your notication; don't edit a copy of the style template and apply that to your notication.
To add components to your notication, for example another table, consider rst downloading another style template
from My Oracle Support. This template contains Quick Parts content that you can use in Word when you do more
advanced work on layout templates. For example, from the Quick Parts gallery, you can select and add the table that's
consistent in format with predened tables already on your notication.
By default, the components that you add in the layout template appear in both email and in-app notications, where
available. You can add conditions to explicitly make a particular element, for example a eld, appear only in one type of
notication and not the other.
Shared Components
A predened subtemplate in the business intelligence (BI) catalog applies to all predened layout templates for workow
notications. The subtemplate contains components that are shared among the notications, for example:
• Branding logo, if you add one to the subtemplate, which would appear as the rst component in the email
body. The logo appears in email notications only.
• Action buons in email notications.
• Links at the end of the email notication, one to the corresponding transaction page, and another to the in-app
notication.
When you make a copy of a predened layout template to edit, the copy automatically inherits the same predened
subtemplate. To edit these shared components, make a copy of the predened subtemplate, edit the copied version,
and apply it to your own layout templates.
Mobile Considerations
Because users can view the workow notications on mobile devices, always consider mobile rst and keep the
notications as simple as possible. For example:
• Don't put too much content horizontally, such as too many columns in tables.
• Keep all text, including aributes and column headings, as short as possible.
234
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
• Center align lists of aributes and their values, if they appear outside tables.
Related Topics
• Subtemplates
• Dene the Number of Rows in Tables
All reports using the predened subtemplate are automatically redirected to point to your subtemplate in the
Custom folder. This applies:
235
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Related Topics
• Subtemplates
• How You Modify Copies of Predened Reports
• Generate Sample Report Data
Prerequisites
To get the predened Quick Parts content into your Quick Parts gallery:
1. Open Congurable Workow Notications: Implementation Considerations (2215570.1) on My Oracle Support at
hps://support.oracle.com.
2. Download the .dotx le and save it to your Microsoft Word template folder, for example C:\Users\<user name>
\AppData\Roaming\Microsoft\Templates.
Also, to preview your layout template changes before uploading the .rtf le back to the business intelligence (BI) catalog:
• Generate sample report data from the data model for the report that you're editing.
236
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
• Download a local copy of the subtemplate that applies to the layout template.
a. Copy the predened report and paste it in an appropriate subfolder within the Custom folder.
b. Click the Edit link for the copied report.
3. Click Edit for the layout template to insert Quick Parts content into, and save the .rtf le to your computer with
a new le name.
4. Open the .rtf le with Microsoft Word.
5. Put your cursor where you want to insert new content.
6. From the Insert tab on the ribbon, click Quick Parts within the Text group, and select the component to insert.
7. Edit the inserted component as needed and add any other components.
8. Save your changes in Word.
Related Topics
• Congurable Email Notications: Implementation Considerations
• How You Modify Copies of Predened Reports
• Generate Sample Report Data
• Style Templates
237
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Prerequisites
• Generate sample report data from the data model used for the report, and save the .xml le to your computer.
• Download a local copy of the subtemplate that applies to your own report layout template:
a. In the BI catalog, expand Shared Folders > Custom > Common Content > Templates if you're using
a modied subtemplate, or Shared Folders > Common Content > Templates for the predened
subtemplate.
b. Click Edit for Workow Notication Subtemplate.
c. In the Templates section, click the link in the Locale column.
d. Save the subtemplate .rtf le to your computer.
Previewing Output
To generate sample output from a local layout template:
1. Open your .rtf report layout template in Microsoft Word and make your edits.
2. On the ribbon, open the BI Publisher tab and click Sample XML within the Load Data group.
3. Select the .xml le you downloaded to import sample data from the data model.
4. At the beginning of your .rtf document, replace the path with the location of the downloaded subtemplate le
on your computer. For example, change <?import:xdoxsl:///Common Content/Templates/Workflow Notification
Subtemplate.xsb?> to <?import:file:///C:/Template_Directory/FinFunWorkflowNotificationSub.rtf?>.
5. From the BI Publisher tab on the ribbon, click HTML in the Preview group.
6. If the preview reects your changes as expected, then change the path back to the original location.
7. From the BI Publisher tab on the ribbon, click Validate Template in the Tools group.
8. Also in the Tools group, click Check Accessibility.
9. Save your changes in Word.
Related Topics
• Generate Sample Report Data
238
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
The logo, action buons, and links at the end of email notications are predened to appear only in emails, based on
the subtemplate. The approval history is usually predened to also appear in the body of only email notications. Any
conditional seing you apply to these components in the .rtf template won't override the predened setup.
Prerequisites
Generate sample report data from the data model used for the report, and save the .xml le to your computer.
Tip: To make sure you're looking at the correct form elds, double-click the C form eld to open the
Conditional Region dialog box and see the BINDISONLINENOTIF seing.
1. In your .rtf report layout template, put your cursor immediately before the content you want to make
conditional.
2. Enter the following code, which functions the same as the C form eld:
Related Topics
• Generate Sample Report Data
239
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Do I want to add prompts and headers to the layout template? No, not for this example.
Do I want to add data model aributes to the layout template? Yes, the Note to Supplier aribute.
Which language do I use for the RTF template? English (United States).
Prerequisites
1. Download and install the Oracle BI Publisher Desktop: hp://www.oracle.com/technetwork/middleware/bi-
publisher/downloads/index.html.
2. Download and install the Template Builder for Word to use Microsoft Word to edit the layout templates. To
download, install, and set up Template Builder for Word, see Creating RTF Templates by Using BI Publisher
11g Template Builder for Word: hp://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bip/
tb4word/tbwordbip.htm.
3. To preview the congured templates, download a local copy of the subtemplate that applies to your own report
layout template:
◦ Sign in to the Oracle Business Intelligence Publisher server with the BI Administrator Role to open the
Oracle Business Intelligence Home page.
240
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
◦ Click Catalog.
◦ In the BI catalog, go to Shared Folders > Common Content > Templates for the predened
subtemplate.
◦ Click More for the Workow Notication Subtemplate.
◦ Click the Download option.
◦ Save the subtemplate le to your computer.
Note: To add data model aributes to the template, perform steps 5 and 6. Otherwise, skip to step
7.
5. Click the Data tab.
6. Enter values for the following key aributes for an existing purchase order. Key aributes enable you to pull in
all the purchase order aributes:
◦ Document Number
241
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
1. On your local drive, open the UpdatedPurchaseOrderNotication.rtf template in Microsoft Word, with the
Template Builder installed.
2. Select the BI Publisher tab.
3. In the Load Data section, click Sample XML.
4. In the dialog box to select XML data that appears, browse to open the PurchasingNoticationDM_.xml le you
saved in the Exporting the Data Model XML File task. Then click Open.
5. In the Data loaded successfully dialog box, click OK.
6. Scroll to the TSRHLines section of the notication.
7. Place the cursor after the C UnitPriceEC line and press the Enter key.
8. On the new line, enter Note to Supplier:, and place the cursor at the end of the text you entered.
9. On the BI Publisher tab, in the Insert section, click the 123 Field buon.
10. On the Field dialog box, locate and select the NoteToSupplier aribute.
11. Click Insert.
12. Click Close to return to the UpdatedPurchaseOrderNotication.rtf template.
242
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Related Topics
• How You Modify Copies of Predened Reports
243
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Prerequisites
1. Download and install the Oracle BI Publisher Desktop: hp://www.oracle.com/technetwork/middleware/bi-
publisher/downloads/index.html.
The Template Builder for Microsoft is included in the BI Publisher.
2. To preview the congured templates, download a local copy of the subtemplate that applies to your own report
layout template:
a. In BI Publisher, click Catalog.
b. In the BI catalog, go to Shared Folders > Common Content > Templates for the predened
subtemplate.
c. Click More for the Workow Notication Subtemplate and then click Copy.
d. In the Folders section, expand Shared Folders > Custom > Procurement > Sourcing.
e. Click the Paste Resource icon.
f. Click More for the Workow Notication Subtemplate and then click Download.
g. Save the subtemplate to the local drive on your computer.
244
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
5. In the Negotiation Invitation Email Report, click the Sourcing Notications Data Model to open the Diagram
tab.
Note: To ensure that all data sets include requested elements with null values in the output XML
data, do the following:
◦ In the Data Model section, select Properties.
◦ In the Properties section, select Include Empty Tags for Null Elements.
◦ In the Data Model section, select Data Sets.
245
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Related Topics
• How You Modify Copies of Predened Reports
Which template do I update? External Supplier Registration Approved FYI Email Report
Do I want to add data model aributes to the layout template? CORPORATE WEBSITE
246
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Tasks Summary
Congure the External Supplier Registration Approved FYI Email Report:
1. Add an aribute to the Data Model.
2. Export the data model XML le.
3. Download the report layout template.
4. Edit email body information in the template.
5. Add data model aributes to the template.
6. Upload the modied report layout to the BI Publisher catalog.
Prerequisites
1. Download and install the Oracle BI Publisher Desktop: hp://www.oracle.com/technetwork/middleware/bi-
publisher/downloads/index.html.
The Template Builder for Microsoft is included in the BI Publisher.
2. To preview the congured templates, download a local copy of the subtemplate that applies to your own report
layout template:
a. In BI Publisher, click Catalog.
b. In the BI catalog, go to Shared Folders > Common Content > Templates for the predened
subtemplate.
c. Click More for the Workow Notication Subtemplate and then click Copy.
d. In the Folders section, expand Shared Folders > Custom > Procurement > Suppliers.
e. Click the Paste Resource icon.
f. Click More for the Workow Notication Subtemplate and then click Download.
g. Save the subtemplate to the local drive on your computer.
247
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
5. In the External Supplier Registration Approved FYI Report, click the Supplier Registration Approved Email
Data Model to open the Diagram tab.
Note: To ensure that all data sets include requested elements with null values in the output XML
data, do the following:
◦ In the Data Model section, select Properties.
◦ In the Properties section, select Include Empty Tags for Null Elements.
◦ In the Data Model section, select Data Sets.
248
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
8. Proceed to the task Uploading the Modied Report Layout to the Oracle BI Publisher Catalog.
Note:
◦ These seings apply only to new tasks that are submied after you nish these steps, not
to tasks that are already in progress.
◦ The validation applies right before the user approves or rejects. For example, let's say
comments are not allowed for approval. If users add a comment and then do something
else immediately, like save, and then click Approve, they won't get an error. If they add a
comment and then immediately click Approve, they would get an error.
◦ The seings may or may not actually take eect, depending on which workow task
you're conguring and where users are approving or rejecting from.
249
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
6. Select the Perform update outcome only from task form check box if you want users to update tasks only
from the application, not from email.
7. Click the Commit task icon in the Tasks to be congured toolbar when you're ready to roll out your changes.
Action Types
There are three types of actions:
• Approval Required: The document or object will be routed for approvals.
• Automatic: The document or object can be approved or rejected automatically.
• Information Only: FYI tasks will be sent to notify the specied persons.
You can also choose to route approvals through a specic worker chain by selecting the name of the worker.
Start With
• Identify the rst participant in a list. The Start With aribute can be:
250
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
• Indicate the number of job levels that are required to perform the approval action if the rule applies. For
example, using the gure below, if Mary (Job Level 1) submits a document for approval and the Minimum Job
Level is set to 3, then only John Allens must also approve.
Casey Brown
(Director, Job Level 3)
John Allens
(Sr. Manager, Job Level
2)
Pat Stock
(Manager, Job Level 2)
Mary Walton
(Assistant, Job Level 1)
• Identify the person at the top of the employee hierarchy, or the top person in the approval chain. In most cases,
this is the CEO.
Include
• Indicates if everyone returned in the list of participants from this action will be included, the rst and last
approver from the list will be included, or only the last approver will be included.
251
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Position Hierarchy
• Indicates if everyone returned in the list of participants from this action will be included, the rst and last
approver from the list will be included, or only the last approver will be included.
Position Chain Of
• Select the approval chain of the persons within a document. For example, select preparer and requester in
purchase requisitions, or a buyer in purchasing documents.
Start With
• Identify the rst participant in a list. The Start With aribute can be:
◦ Next Position (default value).
◦ The value selected in the Approval Chain Of choice list.
General Manager,
Job Level 5
Regional Manager,
Job Level 3
Include
• Indicates if everyone returned in the list of participants from this action will be included, the rst and last
approver from the list will be included, or only the last approver will be included.
252
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Start With
• Start With identies the rst participant in a list. The Start With aribute can be:
• The number of approvers in the supervisory hierarchy starting with the person specied in Start With.
• The Top Worker in Hierarchy identies the person at the top of the employee hierarchy, or the top person in
the approval chain. In the most cases, this is the CEO.
User-Dened Routing
You can congure user-dened aributes to return a single user, or a list of users, to whom human tasks can be routed.
Related Topics
• Considerations for Using Jobs and Positions
• Examples of Jobs
• Examples of Positions
• Position Hierarchy Approval-Rule Aributes
253
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
This gure shows the predened stages: Preapproval, Terms, Post Approval, and Post Approval FYI.
Preapproval Stage
Terms Stage
The participants predened within each stage are illustrated in the gures below. Note that the participant name
conveys both the participant type and the voting regime. For example, Preapproval (Parallel) First Responder Wins has a
participant type of Parallel and voting regime of First Responder Wins. This implies that all the approvers will be notied
in parallel and the rst responder decision will be nal for that participant.
This gure shows the predened participants for the Preapproval stage:
• Preapproval FYI Participant
• Preapproval Parallel Consensus Participant
254
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Preapproval Stage
Preapproval FYI
Participant
This gure shows the predened participants for the Terms stage:
255
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Terms Stage
Terms Approval
FYI Participant
Terms
Terms
Terms Terms Terms Approval
Approval
Approval Approval 2 Approval 3 Parallel First
Parallel
Serial Serial Serial Responder
Consensus
Participant Participant Participant Wins
Participant
Participant
This gure shows the predened participants for the Postapproval stage:
Postapproval Stage
Post Approval
Post Approval
Parallel First Post Approval
Parallel
Responder Serial
Consensus
Wins Participant
Participant
Participant
This gure shows the predened participants for the Postapproval FYI stage:
256
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
• Example
• Aributes
• Setup
Example
Use the award contract number aribute in an approval rule condition to evaluate if a purchase order distribution is
associated to a sponsored project. Then add the principal investigator in charge of the award as an approver to the
approval workow to ensure they approve expenditures against the award.
Aributes
Some of the project aributes you can use for approval rules and routings include:
For more information, refer to the white paper available on My Oracle Support (MOS): Seing Up Document Approvals
for Oracle Fusion Procurement (document ID 1967303.1).
257
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
The delivered funds override approval rule for requisitions has the following aributes:
• Stage: Header Postapproval Stage
• Participant: Funds Override Approval
• Routing: Parallel
• Voting Regime: Consensus
• Enabled: Check box is selected.
You can't edit this rule on the Manage Requisition Approvals page. You can only enable or disable it.
You can dene a funds override approval rule dierent from what's delivered. You can add conditions based on these
aributes:
• Funds Override Approver
• Funds Override Approver User Name
For example, you might dene a condition where a certain approver can route the document to another approver.
The delivered funds override approval rule for purchase orders has the following aributes:
• Stage: Postapproval Stage
• Participant: Funds Override Approval
• Routing: Parallel
• Voting Regime: Consensus
• Enabled: Check box is selected.
You can't edit this rule on the Manage Purchasing Document Approvals page. You can only enable or disable it.
You can dene a funds override approval rule dierent from what's delivered. For example, you might want to have
funds override approval for purchase orders occur at the preapproval stage rather than the postapproval stage. To
dene the rule set the aribute values as follows:
• Stage: Preapproval Stage.
• Participant, Routing, Voting Regime, Enabled: Same values as for the delivered rule for purchase orders.
• Conditions: Funds override approver isn't blank.
• Action Type: Approval Required.
• Route Using: Single Approver.
• User Type: Funds override approver.
258
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Related Topics
• How You Dene Funds Override Rules for a Control Budget
AND
OR
ACTIONS
259
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Once you have dened the aribute, then it can be used in the rule condition as follows: Requisition Amount in USD
greater than 500
260
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Technology category includes two lower-level categories: System Cards, and Computers. Included under each of those
two lowest-level categories are, respectively, specic memory module cards and computer servers.
Category Hierarchy
Information
Technology
Components for
Information
Technology
If the approval policy is: If the requisition contains lines from IT where the lines total is greater than 500, then route the
requisition to the IT group for approval.
When dening summation aribute, you can use distribution amount or the distribution approval amount. You can also
apply up to three lter criteria on the lines or distributions of the transaction using aribute or hierarchy. For match
using hierarchy, the following hierarchies can be used:
• Balancing Segment
• Category Name
• Cost Center
261
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
• Management Segment
• Natural Account
The following is a sample approval rule using the IT Spend user-dened aribute:
CONDITION
ACTION
In the Setup and Maintenance work area, use the Manage Requisition Approvals task in the Approval Management
functional area to congure requisition approval rules.
The following gure depicts the stages seeded for requisition approvals and also indicates that the stages are seeded in
sequence.
Header Stage
Approvals are routed through the seeded stages in the following sequence:
1. Header Preapproval Stage
262
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
The following gure shows seeded participants in the header preapproval stage.
Requester FYI
Participant
2. Header Stage
Header Stage
Header Stage
Header Header Header First Header Stage
Hierarchy Hierarchy 2 Hierarchy 3 Responder Consensus
Participant Participant Participant Wins Participant
Participant
263
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
The following gure shows seeded participants in the header postapproval stage.
Postapproval
Header Header First
Header
Consensus Responder
Hierarchy
Participant Participant
Participant
The following gure shows seeded participants in the postapproval FYI stage.
Preparer FYI
Participant
There are four seeded stages for requisition approvals and within each stage, there are seeded participants. The non-
FYI participants are seeded as rule based, which lets you pick the list builder (Supervisory, Position, Job Level, Single
User, User-Dened Routing, and Approval Groups) that's applicable for your organization.
Line and distribution level rules can be dened within the stages with header dimension.
Seeded Participants:
1. Requester FYI
◦
The requester on every line for a requisition receives a requisition FYI notication. This allows requesters
to be notied when a preparer creates a requisition on their behalf. Each requester on every requisition
line is notied. The rule to notify the requester is available out of the box, hence you don't need to
perform additional steps for this.
2. Preapproval Header Consensus
◦ Approvals are routed in parallel for this participant. This participant is more commonly used in
conjunction with approval groups. This participant requires approval from all approvers.
264
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
◦
Approvals are routed in parallel for this participant. This participant is more commonly used in
conjunction with approval groups. The rst responder to approve or reject represents the outcome of all
remaining approvers.
4. Preapproval Header Hierarchy
Header Stage
The header stage is often used for scal approvals, based on the requisition amount.
Seeded Participants:
1. Header Hierarchy
◦
Approvals are routed in serial. This participant is generally used for supervisory or position hierarchy-
based routing.
◦ The approvers returned based on all rules that apply in a serial participant are notied in sequence, even
if the rules are evaluated against lines or distributions.
2. Header Hierarchy 2
◦
Approvals are routed in parallel for this participant. This participant is more commonly used in
conjunction with approval groups. This participant requires approval from all approvers.
5. Header Stage First Responder Wins
◦ Approvals are routed in parallel for this participant. This participant is more commonly used in
conjunction with approval groups. The rst responder to approve or reject represents the outcome of all
remaining approvers.
Note:
If you set up the overriding approver aribute, you may also send an FYI task to the original system generated rst
approver notifying the original approver that they have been bypassed.
265
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Seeded Participants:
1. Header Consensus
◦
Approvals are routed in parallel for this participant. This participant is more commonly used in
conjunction with approval groups. This participant requires approval from all approvers.
2. Header First Responder Wins
◦
Approvals are routed in parallel for this participant. This participant is more commonly used in
conjunction with approval groups. The rst responder to approve or reject represents the outcome of all
remaining approvers.
3. Postapproval Header Hierarchy
This stage isn't available in the BPM Worklist or Approvals UI pages for conguration.
Note
You do not need to use all of the seeded stages and participant. However, if you do not need to use any of the seeded
participants, you simply need to select the Enable or Disable action for the respective participant on the Manage
Approval Task page.
266
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
This gure illustrates Acme's approval policies. Depending on the purchase amount, the requisition is autoapproved, or
must go through one, two, or three levels of supervisory approval.
1. No approvals required, such as self approved, for requisitions less than or equal to 500 USD.
ACTION
Action Type: Automatic
Set Outcome To: Approved
AND
2. One level of Supervisory hierarchy approval required for requisitions more than 500 USD and less than or equal
to 1000 USD.
CONDITION
Approval Amount is greater than 500
AND Approval Amount is less than or equal to 1000
AND Functional Currency Code equals USD
ACTIONS
Action Type: Approval Required
Route Using: Supervisory Hierarchy
Approval Chain Of: Preparer
Start With: Manager
Number of Approval Levels: 1
Top Worker in Hierarchy: Joe Smith
267
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
AND
3. Two levels of Supervisory hierarchy approval required for requisitions more than 1000 USD and less than or
equal to 2000 USD.
CONDITION
AND
4. Three levels of supervisory approval required for requisitions more than 2000 USD.
CONDITION
Approval Amount is greater than 2000
AND Functional Currency Code equals USD
ACTIONS
Action Type: Approval Required
Route Using: Supervisory Hierarchy
Approval Chain Of: Preparer
Start With: Manager
Number of Approval Levels: 3
Top Worker in Hierarchy: Joe Smith
AND
268
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Scenario
Rules in Lines Preapproval Header Stage: Preapproval Header Hierarchy Participant:
1. If the requisition is an emergency request, the preparer's manager's approval is required before other
approvers are notied.
IF
THEN
Task Aggregation Once per task Within the same task, if a participant is
returned multiple times based on the
approvals rules, then the participant will
only receive one worklist task for action or
review.
Allow all participants to invite other Yes (checked) Participants can add other approval or FYI
participants participants in the approval list.
Allow participants to edit future Yes (checked) Participants can update participants
participants remaining in the approval list who weren't
assigned the approval task. Note that
participants can't remove approver
participants pre-dened in Approval
Groups or generated by the application.
269
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Allow initiator to add participants Yes (checked) A requisition preparer can insert ad-hoc
approval or FYI participants.
Complete task when participant chooses Reject The entire requisition approval task will
be completed when a Reject action is
performed by a participant.
Enable early completion of parallel Yes (checked) The entire requisition approval task will
subtasks be completed when a Reject action is
performed by a participant.
Complete parent tasks of early completing Yes (checked) The entire requisition approval task will
subtasks be completed when a Reject action is
performed by a participant.
You can congure approval rules taking into consideration your internal material transfer requests. The 'Internal
Transfer Requisition' approval aribute indicates whether all lines of the requisition are for internal material transfer or
not. This lets you decide on the approval routing for your internal transfer requisitions. In addition, you can dene rule
conditions based on the requisition line aributes source organization and source type.
If your organization doesn't require approvals for internally sourced items, you can congure a rule to bypass approvals
when all lines in the requisition are sourced internally.
270
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
These stages are modeled as serial stages. All rst stage approvals must be completed before the second stage
approvals routing rules are executed.
Related Topics
• Supplier Registration Process
To access the supplier registration approvals tasks, in the Setup and Maintenance work area, go to the following:
• Oering: Procurement
• Functional Area: Approval Management
271
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Use the Task: Manage Supplier Registration Approvals to congure approval routing rules for registrations submied by
external users of companies interested in becoming a supplier.
Use the Task: Manage Internal Supplier Registration Approvals to congure approval routing rules for registrations
submied by internal users on the company's behalf.
The following gure shows the seeded supplier registration approval stages that are executed in Oracle Fusion Supplier
Portal.
Approval rules congured in the seeded stages are executed in the following sequence:
272
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Parallel Approval
Serial Approval
The following gure shows the second stage approvals that are executed after all rst stage approvals are completed.
Parallel Approval
Serial Approval
273
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Approval Stages
Approvals to review supplier registration requests happen in a exible two-stage process.
Within each stage, there are three seeded rule-based participants. You can pick a routing type (Supervisory, Position,
Job Level, Single User, and User-Dened Approval Groups) to congure the list of approvers entitled to receive the
document for approval.
You do not need to use all of the seeded stages and participants. You can disable unused participants by selecting the
unused participant on the Manage Approvals Task page and clicking the Disable buon.
Disabled Rules or Participants will not be evaluated. For example, if the participant is already disabled, then no rules
within that participant will be evaluated. The same applies for disabled rules.
All identied approvers receive a notication for approval in parallel. The rst responder to approve or reject
the request denes the outcome of all remaining approvers.
• Parallel Approval
All identied approvers receive a notication for approval in parallel. Approval is required from all approvers.
• Serial Approval
Approvals are routed in serial. The approval is completed sequentially from approver to approver.
All identied approvers receive a notication for approval in parallel. The rst responder to approve or reject
the request denes the outcome of all remaining approvers.
• Parallel Approval
All identied approvers receive a notication for approval in parallel. Approval is required from all approvers.
• Serial Approval
Approvals are routed in Serial. The approval is completed sequentially from approver to approver.
274
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Supplier Managers are derived from the users dened in procurement agents. All procurement agents with Manage
Suppliers function for the BU that the registration was created will receive the approval notication.
Even if new rules are not congured, the seeded rule will execute unless it is deleted.
Note: You can, at any point of time, modify or delete the seeded rule.
Supplier Registration
You can congure the supplier registration process based on the expected supplier business relationship of a supplier.
You can dene two separate registration ows based on the intended business relationship.
• Spend Authorized Supplier requests: Companies already identied for a procurement need are directed by
the buying organization to the spend authorized registration ow. The ow captures more rigorous prole
information needed before agreements, orders, and invoices can be transacted. For example, a spend
authorized company registering can be required to provide bank account information.
• Prospective Supplier requests: Unknown companies are presented with the prospective supplier ow. They
must only provide minimal prole information to participate in the sourcing and supplier qualication activities.
Possible prole components that you can include during a registration ow include:
When you congure the two supplier registration ows you identify which prole aributes the supplier sees. Also you
can specify whether the supplier must enter a value for the aribute.
• Enabled: The aribute is displayed to the supplier, but the supplier is not required to enter information.
• Required: The supplier must supply information for this aribute.
Note: Your supplier registration conguration applies to suppliers from all registration sources.
275
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
In the Default Business Relationship for Registration Sources region, you identify the default business relationship
for each registration ow. The default business relationship determines what prole information is included as
congured for the registration page.
276
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
• Supplier Qualication
• Supplier Negotiation
Supplier proles can also be changed by internal users. Updates to bank account changes by internal users are
submied to an approval process. See Conguring Internal Supplier Bank Account Change Approvals: Explained.
The Congure Supplier Registration and Prole Change Requests task does not congure supplier prole changes
made by internal users.
You can specify approval requirements for prospective and spend authorized suppliers for the following entities:
• Organization Details: Basic supplier information including the supplier name and supplier prole level
descriptive exelds.
• Contacts: Supplier contact information including supplier contact descriptive exelds.
• Contact User Account: User accounts that control account privileges for supplier contacts to use Supplier Portal.
• Addresses: Company addresses including associated contacts including supplier address descriptive exelds.
• Business Classications: Supplier certications important to the buying organization such as supplier diversity
programs.
• Bank Accounts: Supplier banking information.
• Payment Methods The method used to pay the supplier.
• Products and Services: Identies what categories of products and services are provided by the supplier.
• Tax Identiers: Tax organization, tax country, and taxpayer ID to identify the supplier for tax purposes.
• Site Details: Site information such as the address and site purpose (spend authorized suppliers only).
Conguration of the Site Details aribute for prospective suppliers is not available.
Related Topics
• Supplier Products and Services Categories
• Supplier Registration Process
• How You Congure Internal Supplier Bank Account Change Approvals
Approval Task
In many end-to-end business processes human intervention is required such as for approving documents, managing
exceptions, or performing activities required to advance the business process. The document approval request tasks
allow you to send approval requests to approvers enabling them to make decisions and thus advancing the request-to-
pay business process.
You create dierent approval task for each approval need, based on the business it serves. For example, you might
create approval tasks for purchase requisitions approvals; expense reports approvals, and so on.
In the Setup and Maintenance work area, use the following tasks to set up approvals for procurement document
objects:
• Manage Requisition Approvals, found in the Approval Management and Self Service Procurement functional
areas
277
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
• Managing Purchasing Document Approvals, found in the Approval Management functional area
◦ Use the Managing Purchasing Document Approvals task to create approval rules for both agreements
and purchase orders.
Based on your unique business requirements, administrators can choose to send the approval request to approvers in
parallel or in sequence. Approvals can be sought using single approver, supervisory chain, position, job level hierarchy,
or using a list of approvers.
This gure shows the structural hierarchy of the components used in seing up an approval request task: Stage,
Participant and Rule.
Stage
Participant
Rule
Routing Condition
Type
Task Dimension
Configuration
Voting Action
Regime
Stage
Use stages to organize approval routing rules into logical groupings. Each stage is associated with a dimension. A
dimension contains a set of aributes at a specic purchasing document level, such as header or lines, which can be
used to author routing rules. Approval actions within each stage must be completed before entering the next stage.
Participant
There can be many participants within a stage. Properties set on the participants determine whether approvals would be
routed in serial or in parallel.
Oracle Fusion Procurement is seeded with one or more participants within each stage to enable exibility in document
approvals routing.
278
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Rule
Approval rules are routing policies or rules that determine the approvers or FYI recipients for a business transaction.
• Condition: The IF clauses in an approval rule and evaluated to either true or false. For the rule to apply to a
transaction, all of its conditions must be true. An example of a condition is: If requisition approval amount is
less than 500 USD, or if requisition approval amount is between 500 USD and 10000 USD.
• Action: Instruction to include a given set of approvers within an approval rule.
Related Topics
• Approval Management Conguration Options for Oracle Fusion Human Capital Management
• Update Existing Setup Data
The setup task approval conguration does not include any seeded approval rules. You must congure at least one
approval rule in one of the available stages in order to use the feature.
For information about supplier prole change request approvals, see Supplier Prole Change Request Approval:
Explained.
Related Topics
• Supplier Prole Change Request Approval
• Set Up Supplier Prole Change Request Approvals
• How You Congure Internal Supplier Bank Account Change Approvals
279
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Requested changes to bank accounts are applied to the supplier prole only when the request is approved. While
the request is pending approval, the rest of the prole is still available for editing, and these changes are applied
immediately when submied.
After submiing a bank account change for approval, you cannot make additional bank account changes until the
approval process is complete, or the submied changes are canceled.
Use the Supplier page to view pending change request details. Click View Change Request to display the Prole
Change Request page, which shows the supplier aribute changes that have been submied.
You can also cancel the request by clicking Cancel Change Request.
Use the Supplier Prole Change Request page to review and manage internal supplier bank account changes for an
internal supplier prole change request. Access it by clicking the change request link in the Notications dialog.
Changes to aributes are indicated with the Changed icon adjacent to the bank account row. To see what was changed,
click the Details icon. The Change Details dialog box shows which aributes were changed, and the values before and
after the proposed change.
Related Topics
• How You Congure Internal Supplier Bank Account Change Approvals
• Internal Supplier Prole Bank Account Change
280
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
• Leave the prole option with the default value of 7, or replace it with a dierent number.
• The prole value represents the number of days after the FYI task is created.
When assignees don't read or dismiss an FYI task within the specied number of days after the task was created, the
task is then eligible to be automatically dismissed. All other tasks are eligible for automatic withdrawal when assignees
don't take action to send the task to a nal status within six months after the task was created.
Related Topics
• Set Prole Option Values
• Update Existing Setup Data
Archive
Tasks are automatically archived once a month without you doing any setup. You can't change or stop this automatic
archive. You can, however, also run the Archive Workow Tasks scheduled process as needed; for example, you need
the latest data archived immediately for reporting purposes. The process includes all eligible tasks that aren't yet
archived.
Archived data includes task details, approval history, comments, and aachments. How you view or use the archived
data depends on the products you're using. For example, the data might be displayed in a table on a page, or available
through a business intelligence subject area that you can select to create an analysis.
281
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Purge
Archived tasks that were last updated over 30 days ago are immediately purged after the monthly automatic archive,
without you doing any setup. You can't change or stop this automatic purge.
Related Topics
• Submit Scheduled Processes and Process Sets
Note: If you don't see this task, then make sure that the Application Toolkit Component Maintenance feature
is enabled at the oering level in the Oerings work area.
On the Manage Application Toolkit Administrator Prole Values page, set the Welcome Dashboard Worklist Timeout
Interval prole option.
• If you don't set a value for this prole option, which is blank by default, then the region doesn't time out.
• Retrieving data for the Worklist region aects the performance of My Dashboard as a whole. So, select a value
for this prole option if your users have the Worklist region on My Dashboard and notice performance issues.
After the timeout, users can refresh the region to try retrieving the data again.
Related Topics
• Set Prole Option Values
• Congure Oerings
282
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Electronic Signature
How You Congure Electronic Signature for Purchasing
Documents
Before your organization can use electronic signature functionality for purchasing documents, you must enable the
feature and perform some setup steps. After the setup is complete, authorized users in your organization can use the
electronic signature functionality with purchase agreements, purchase orders and change orders.
To set up electronic signature for purchasing documents, you must complete following tasks:
• Obtain a license from and register with the supported third-party electronic signature service provider.
• Enable the feature in the Procurement oering.
• Set up the Manage Electronic Signature page.
Note: When you enable the feature, the Require Signature option is available to users on the create order,
agreement and change order pages.
Note: If you have already set up this page for the Contracts oering, you don't have to set it up again for the
Procurement oering.
Related Topics
• Set Up an Oering with Scope
• Congure Oerings
283
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Transaction Console
Give People Access to Manage Self Service Procurement
Transactions
You have a couple of options for giving people access to the Transaction Console work area, depending on whether
you're assigning them predened job roles, or your own congured job roles.
• Assign the predened Procurement Application Administrator
(PO_PROCUREMENT_APPLICATION_ADMIN_JOB) job role.
Your own congured job roles must include this duty role:
This duty role inherits data security and the function security privilege Review Approval Transactions
(PER_REVIEW_APPROVAL_TRANSACTIONS_PRIV).
1. In the Setup and Maintenance work area, go to the Manage Enterprise HCM Information task.
◦ Oering: Procurement
◦ Functional Area: Enterprise Prole
◦ Task: Manage Enterprise HCM Information
2. On the Enterprise page, click the Edit buon and select Update.
3. In the Update Enterprise dialog box, ll in your information and click OK.
4. In the Transaction Console Information section, select the Enable Transaction Security check box.
5. Click Submit.
Note: You just need to do this for one oering. The seing now applies to all product families. If you're also
using Oracle HCM Cloud, make sure transaction security proles are set up so that HCM administrators can
see and act on HCM transactions.
284
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
Your own congured job roles must include this duty role:
This duty role inherits data security and the function security privilege Review Approval Transactions
(PER_REVIEW_APPROVAL_TRANSACTIONS_PRIV).
1. In the Setup and Maintenance work area, go to the Manage Enterprise HCM Information task.
◦ Oering: Procurement
◦ Functional Area: Enterprise Prole
◦ Task: Manage Enterprise HCM Information
2. On the Enterprise page, click the Edit buon and select Update.
3. In the Update Enterprise dialog box, ll in your information and click OK.
4. In the Transaction Console Information section, select the Enable Transaction Security check box.
5. Click Submit.
Note: You just need to do this for one oering. The seing now applies to all product families. If you're also
using Oracle HCM Cloud, make sure transaction security proles are set up so that HCM administrators can
see and act on HCM transactions.
285
Oracle Procurement Cloud Chapter 9
Implementing Procurement Approval Management for Procurement
286
Oracle Procurement Cloud Chapter 10
Implementing Procurement Help Conguration
10 Help Conguration
Set Up Help
You don't have to set anything up for help to work. But you can do optional setup, for example to make help icons
visible to everyone, or to give people access to add help content. First enable help features, then do some tasks in the
Application Extensions functional area.
Enable Features
In the Oerings work area, review these features at the oering level.
• Local Installation of Help: Make sure to leave this enabled.
• Access to Internet-Based Help Features: This feature isn't used, so it doesn't maer if you enable it or not.
• Help Content Management: Enable this feature if you want some people to be able to add company-specic
help to help windows or the Geing Started work area.
• Security for Added Help: Enable this feature if you want certain help to be available only to a restricted set of
user roles.
Caution: Enable this feature only if you have this requirement, because the feature can aect
performance.
Related Topics
• Congure Oerings
• How You Manage Dierent Types of Help
By default, help icons that open help windows are hidden. You can set it up so that users do see the icons every time
they sign in, on any page that has help icons.
1. In the Setup and Maintenance work area, go to the Set Help Options task in the Application Extensions
functional area.
2. On the Set Help Options page, select the Show help icons by default check box. You just need to do this for
one oering, and the seing applies to everyone.
3. Sign out and sign back in to see the icons by default. The same goes for any user next time they sign in.
To hide the icons, people can still click their user image or name in the global header and select Hide Help Icons, and
later select Show Help Icons to see the icons again.
287
Oracle Procurement Cloud Chapter 10
Implementing Procurement Help Conguration
Note: What we are talking about here aects only help windows, not help text that appears when you hover
over or click certain UI elements on the page. To edit or delete UI element help text, use Page Composer or
other tools.
Related Topics
• Update Existing Setup Data
By default, the administrators for product families have this privilege. Your security administrator can assign job roles
with this privilege to other users. The Assign Help Text Administration Duty task is a reminder for you to follow up
with your security administrator. Make sure that people who want to create and edit help have the access to do so.
Related Topics
• How You Manage Dierent Types of Help
Related Topics
• Overview of Global Search Setup
288
Oracle Procurement Cloud Chapter 10
Implementing Procurement Help Conguration
Field Value
HR
Help Security Group
HR Only
Display Name
4. Click Save.
5. With your new help security group selected, go to the Associated Roles section and add a new row.
6. Select PER_HUMAN_RESOURCE_SPECIALIST as the role name.
7. Click Save and Close.
Related Topics
• Congure Oerings
• Update Existing Setup Data
• Add Your Content to Help Windows
• Create and Edit Added Help
289
Oracle Procurement Cloud Chapter 10
Implementing Procurement Help Conguration
• Use the User Interface Text tool to edit the text for any type of help for UI elements, including informational text
in help windows. You usually use this tool to make bulk changes, for example to change a phrase wherever it
appears in any UI label, help for UI elements, messages, and so on.
Related Topics
• Modify Pages
• Page Component Properties
• Modify Text Using User Interface Text Tool
290
Oracle Procurement Cloud Chapter 11
Implementing Procurement Application Toolkit Conguration
Tasks
Use these tasks in the Application Extensions functional area:
• Map Reports to Work Areas: Determine what's available in the Reports and Analytics pane for specic work
areas.
• Set Watchlist Options: Dene seings that aect what's displayed in the Watchlist and how often items are
refreshed.
• Manage Application Toolkit Administrator Prole Values: Set prole options to aect how some Application
Toolkit components work.
• Use other Application Toolkit tasks in this functional area to set up help:
◦ Set Help Options
◦ Assign Help Text Administration Duty
◦ Manage Help Security Groups
Related Topics
• Set Up the Mapping Service for Contextual Addresses
• Set Up the Worklist Region on My Dashboard
• Set Up Help
291
Oracle Procurement Cloud Chapter 11
Implementing Procurement Application Toolkit Conguration
Related Topics
• Why can't I see reports when I edit seings for the Reports and Analytics panel tab
• Why can't I see reports when mapping reports to work areas for the Reports and Analytics panel tab
Field Value
Enterprise Scheduler Job Package The path for the job denition, for example: / oracle/ apps/ ess/<product family>/
Name <product>/ <business area>/ Jobs
292
Oracle Procurement Cloud Chapter 11
Implementing Procurement Application Toolkit Conguration
Field Value
Enterprise Scheduler Job Denition The job denition name (not display name), for example: ABCDEFG
Name
Related Topics
• How You Set Up Reports to Run as Scheduled Processes
• How You Access and Modify Report Components
Ultimately, what users see in their own Watchlist would be the categories and predened items that you enable in the
Set Watchlist Options page:
• Plus any saved searches that the user is using as Watchlist items
• Minus any categories or items that the user decides to hide using Watchlist preferences
• Minus any items with no results found, if the user decides to hide such items using Watchlist preferences
If you disable a Watchlist category, then the category isn't available for users to include in their Watchlist. All Watchlist
items within the category are also disabled.
293
Oracle Procurement Cloud Chapter 11
Implementing Procurement Application Toolkit Conguration
Watchlist Category
If you disable a Watchlist category, then:
• The category isn't available for users to include in their Watchlist.
• All Watchlist items within the category are also disabled.
Note: You can see the Watchlist icon in the global header only if your default home page layout is Panel or
Banner.
Related Topics
• Refresh Intervals for Watchlist Items
• How can I change predened Watchlist category and item names
• Create Watchlist Items
• Show or Hide Watchlist Items
• Why can't I see some icons in the global header
294
Oracle Procurement Cloud Chapter 12
Implementing Procurement Maintain Common Reference Objects
To make the Maintain Common Reference Objects tasks available in your implementation project, go to the Oerings
work area and enable the Maintain Common Reference Objects feature.
Related Topics
• Overview of Moving Common Reference Objects
• Descriptive exelds
• Extensible exeld contexts
• Extensible exeld pages
• Value sets
• Tree structures
295
Oracle Procurement Cloud Chapter 12
Implementing Procurement Maintain Common Reference Objects
Note: You can specify only those languages that are available in the supported language
pack. If you don't specify any value, all available language packs are supported.
4. Click Save and Close. The language entries will take eect for the user in the next sign in.
Related Topics
• Enter or Edit Translated Text
Related Topics
• Change Your Photo
Related Topics
• How can I set general preferences for myself
296
Oracle Procurement Cloud Chapter 12
Implementing Procurement Maintain Common Reference Objects
A detailed introduction to application taxonomy is provided in the Oracle Fusion Applications Developer's Guide.
Hierarchy
• The application taxonomy hierarchy contains various levels and types of nodes, or modules.
Usage
• Use application taxonomy to understand relationships among applications and between an application and its
les. This information is helpful in managing various phases of the product life cycle.
297
Oracle Procurement Cloud Chapter 12
Implementing Procurement Maintain Common Reference Objects
Identiers
Module ID is the unique primary key for nodes in the taxonomy table. When you create a module, a unique read-only ID
is automatically generated. The module contains two other identiers: Module key and alternative ID. The module key is
a string identier, for example AP for the Oracle Fusion Payables application. The alternative ID is a numeric identier,
for example 1 for the Oracle Fusion product line. These additional identiers are provided for the product line, product
family, and application modules. However, you can optionally add them for logical business areas and new modules.
Note: Don't change the module key or alternative ID for predened modules.
The product code is relevant only to application and logical business area modules. You can leave the eld blank for
other module types. The product code for applications is the short name that can be displayed in lists of application
values. For example, FND for Oracle Fusion Middleware Extensions for Oracle Application.
Names
Module name is the logical name for the module. The name must be unique among nodes within the hierarchy level
with the same parent, but Oracle recommends keeping it unique in the entire hierarchy. The user name and description
can appear to users in other parts of Oracle Applications Cloud.
Usage Types
Though you can update the usage type to reect the current state of the module, just doing so doesn't aect the actual
state. For example, seing a module as installed doesn't mean the module is actually installed if the installation itself
didn't take place. Installation refers to operations related to laying down all the components required to create an Oracle
Applications Cloud environment. Deployment is the process that starts the managed servers and clusters and facilitates
the actual use of product oerings. A licensed module is available for installation and deployment, and a deployed
module is considered actively used when actually used by users.
Seed Data
If seed data is allowed, then data residing in exelds and lookups can be extracted for the module using seed data
loaders. By default, extract is allowed for all predened modules of type application and logical business area.
Associations
You can associate a logical domain to modules of the type Product Family, as well as one or more enterprise
applications to modules of type Application. This association represents the relationship between the taxonomy
modules and the corresponding domain and enterprise applications stored in the Oracle Applications Cloud Functional
Core (ASK) tables.
298
Oracle Procurement Cloud Chapter 12
Implementing Procurement Maintain Common Reference Objects
A common reference data set is available as the default set, which can be assigned to several business units sharing
the same reference data. For commonly used data such as currencies, you can use the common reference data set and
assign it to multiple business units in various countries that use the same currency. In cases where the default set can't
be assigned to an entity, you can create specic sets. The data set visible on the transactional page depends on the
sharing method used to share reference data.
For example, XYZ Corporation uses the same grades throughout the entire organization. Instead of dierent business
units seing up and using the same grades, XYZ Corporation decides to create a set called Grades, which contains the
grades. All business units in the organization have the Grades set so that the grades can be shared and used.
Note: For specic information about conguring reference data sharing for a particular object or product,
refer to the relevant product documentation.
Related Topics
• Reference Data Sets
• Reference Data Sets and Sharing Methods
• Assignment of Reference Data Sets to Reference Objects
Partitioning
Partitioning reference data and creating data sets provide you the exibility to handle the reference data to fulll your
business requirements. You can share modular information and data processing options among business units with
ease. You can create separate sets and subsets for each business unit. Alternatively, you can create common sets or
subsets to enable sharing reference data between several business units, without duplicating the reference data.
299
Oracle Procurement Cloud Chapter 12
Implementing Procurement Maintain Common Reference Objects
The following gure illustrates the reference data sharing method. The user can access the data assigned to a specic
set in a particular business unit, as well as access the data assigned to the common set.
has
access to ...
Common Set
UK
Business Unit
UK
Location Set
Related Topics
• Reference Data Sets and Sharing Methods
• Dene Default Reference Data Sets
• Assignment of Reference Data Sets to Reference Objects
Determinant Types
The partitioned reference data is shared using a business context seing called the determinant type. A determinant
type is the point of reference used in the data assignment process. The following table lists the determinant types used
in the reference data assignment.
Asset Book Information about the acquisition, depreciation, and retirement of an asset that belongs to a
ledger or a business unit.
300
Oracle Procurement Cloud Chapter 12
Implementing Procurement Maintain Common Reference Objects
Cost Organization The organization used for cost accounting and reporting on various inventory and cost centers
within an enterprise.
Project Unit A logical organization within an enterprise that's responsible for enforcing consistent project
management practices.
Determinant
The determinant (also called determinant value) is a value that corresponds to the selected determinant type. The
determinant is one of the criteria for selecting the appropriate reference data set.
Reference Groups
A transactional entity may have multiple reference entities (generally considered to be setup data). However, all
reference entities are treated alike because of similarity in implementing business policies and legal rules. Such
reference entities in your application are grouped into logical units called reference groups. For example, all tables
and views that dene Sales Order Type details might be a part of the same reference group. Reference groups are
predened in the reference groups table.
Currency Codes
You can't change a currency code after you enable the currency, even if you later disable that currency.
Date Ranges
You can enter transactions denominated in the currency only for the dates within the specied range. If you don't enter
a start date, then the currency is valid immediately. If you don't enter an end date, then the currency is valid indenitely.
Symbols
Some applications support displaying currency symbols. You may enter the symbol associated with a currency so that it
appears along with the amount.
301
Oracle Procurement Cloud Chapter 12
Implementing Procurement Maintain Common Reference Objects
Related Topics
• What's the dierence between precision, extended precision, and minimum accountable unit for a currency
• What's a statistical unit currency type
• Euro Currency Derivation
Derivation Type
The Euro currency derivation type is used only for the Euro, and the Euro derived derivation type identies national
currencies of EMU member states. All other currencies don't have derivation types.
Derivation Factor
The derivation factor is the xed conversion rate by which you multiply one Euro to derive the equivalent EMU currency
amount. The Euro currency itself must not have a derivation factor.
Tasks
Once you add a language, it can't be deleted, but just disabled. You can optionally associate natural languages with
International Organization for Standardization (ISO) languages and territories, just for reference.
Values
When you create a natural language, use the alpha-2 ISO code as the language code, or, if not available, then alpha-3.
If the language is not an ISO language, then use x- as a prex for the code, for example x-ja for a Japanese dialect.
Use the sgn code of ISO-639-2 for sign languages, followed by territory code, for example sgn-US for American Sign
Language. You can also use Internet Assigned Numbers Authority (IANA) language tags.
The natural language description must be the language name with territory name in parenthesis where needed, for
example English (Australia) and English (Canada).
302
Oracle Procurement Cloud Chapter 12
Implementing Procurement Maintain Common Reference Objects
Related Topics
• Considerations for Dening Currencies
303
Oracle Procurement Cloud Chapter 12
Implementing Procurement Maintain Common Reference Objects
To enable auditing for Oracle Fusion Middleware products, select one of the levels at which auditing is required for that
product. The audit levels are predened and contain the metadata and events to be audited. For more information,
304
Oracle Procurement Cloud Chapter 12
Implementing Procurement Maintain Common Reference Objects
see Audit Events for Oracle Applications Cloud Middleware (Doc ID 2114143.1) on My Oracle Support at hps://
support.oracle.com.
If you don't want an application to be audited, you can stop the audit process by seing the Audit Level option to None.
Related Topics
• Audit Events for Oracle Applications Cloud Middleware
Selecting an Application
To set up auditing, you must select a web application that contains the required business objects that can be audited.
From the list of business objects, select those business objects that you want to audit. Selecting a business object also
displays its aributes that are enabled for auditing.
Selecting Aributes
For each selected business object to be audited, select the corresponding aributes to include in the audit. All aributes
that belong to that object are by default selected for audit and appear on the user interface. However, you can add or
remove aributes from the list. When you remove an aribute from the list, you stop auditing it even when the parent
object is selected for audit. So, if you want an aribute to be audited, you must add it to the list. If the object selected in
an audit hierarchy is also a part of several other audit hierarchies, the aribute conguration for that object is applicable
to all the hierarchies in that application.
Tip: For business objects based on exelds, select the Flexelds (Additional Aributes) check box to view
and add or remove exeld aributes, to include or exclude them from the audit.
For example, users intend to view the audit history of an object for the previous week, but auditing for that object was
stopped last month. They wouldn't get any audit results for that week, because during the entire month that object
wasn't audited. Even if you enable audit for that object today, users can't get the wanted results because audit data until
today isn't available.
305
Oracle Procurement Cloud Chapter 12
Implementing Procurement Maintain Common Reference Objects
Related Topics
• Audit Events for Oracle Applications Cloud Middleware
To open the Manage Oracle Social Network Objects page, use the following in the Set and Maintenance work area:
306
Oracle Procurement Cloud Chapter 12
Implementing Procurement Maintain Common Reference Objects
◦ Membership groups
◦ Activity feeds of the people you select
• Facilitate:
◦ One-on-one Conversations
◦ Reviews
◦ Document sharing
An important aspect of managing Oracle Social Network objects is enabling business objects for integration.
• Accesses the Manage Oracle Social Network Objects page in Oracle Applications Cloud
• Enables the business object for social network integration
Related Topics
• How can I update translations
• Synchronization of Business Objects
• What happens if I synchronize business objects
• Synchronize the newly translated text from Oracle Applications Cloud so that it can be used within social
network. This means you can:
• Send aribute labels and business object names to social network for use in its user interface.
307
Oracle Procurement Cloud Chapter 12
Implementing Procurement Maintain Common Reference Objects
308
Oracle Procurement Cloud Chapter 13
Implementing Procurement Enterprise Scheduler Job Denitions
To access the Manage Enterprise Scheduler Job Denitions and Job Sets tasks, use the following in the Setup and
Maintenance work area:
• Functional Area: Application Extensions or a product-specic functional area
• Task: Manage Enterprise Scheduler Job Denitions and Job Sets
Related Topics
• Overview of Scheduled Processes
309
Oracle Procurement Cloud Chapter 13
Implementing Procurement Enterprise Scheduler Job Denitions
Note: You can edit list of values sources for use only in job denitions that are not predened.
This table describes the columns in the table on the Manage Job Denitions tab.
Display Name Name of the job denition as available to users while submiing scheduled processes.
Path The full directory path where the job denition is saved.
Execution Type The type of job request for the given job denition, such as a Java, C, PL/SQL, Perl, or hosted
script job.
Job Type The name of the job type upon which the job denition is based.
310
Oracle Procurement Cloud Chapter 13
Implementing Procurement Enterprise Scheduler Job Denitions
Tip: The table of job denitions shows only 10 to 20 items by default but you can use Query by Example to
view other items.
Parameters
A parameter controls which records are included or how they are aected when the job runs. Parameters are available
to users when they submit scheduled processes based on your job denitions. For example, a job updates only the
records that are eective after the date that users enter in a Start Date parameter. You can create, edit and delete
parameters for job denitions that are not predened.
User Property
A user property is set in the job denition to aain some specic results.
Related Topics
• Overview of Scheduled Processes
Display Name Provide a name that the users see while submiing the scheduled process.
Name Provide a name with only alphanumeric characters, for example, AtkEssPrograms1. A job
denition name can't contain space or any special characters.
Job Application Name Select the name of the application to associate the job denition with.
311
Oracle Procurement Cloud Chapter 13
Implementing Procurement Enterprise Scheduler Job Denitions
Report ID Specify the path to the report in the catalog, starting with the folder within Shared Folders,
for example: User-Dened/ <Family Name>/ <Product Name>/<Report File Name>.xdo.
Make sure to include the .xdo le extension for the report denition.
Note: Don't select the Enable submission from Enterprise Manager check box.
Caution: You must not create or edit a user property unless you have the accurate information that
is required to create or edit one.
Note: The aribute validations present on the aributes in the parameters view object are not copied over.
312
Oracle Procurement Cloud Chapter 13
Implementing Procurement Enterprise Scheduler Job Denitions
◦ You can edit the display name of the job denition to use terms that are more familiar to your users.
◦ You can use the Prompt eld to edit parameter display names.
7. Click Save and Close.
Field Description
Retries The number of times to automatically run this job again if the scheduled process fails.
Job Category Specic to the application of the job denition, it's used to group denitions according to your
requirements.
Timeout Period The amount of time before stopping a scheduled process that couldn't complete.
Priority Priority of scheduled processes submied, with 0 as lowest. If other processes, based on the
same or another job, are scheduled to run at the same time, then priority determines the run
order.
When users run the scheduled process, the values they enter for the parameters determine the data to be included in
the report. Also, the values are passed to the data model that the report is using.
313
Oracle Procurement Cloud Chapter 13
Implementing Procurement Enterprise Scheduler Job Denitions
The parameters that you dene must be in the same order as parameters in the data model. For example, the data
model has parameters in this order:
• P_START_DATE
• P_END_DATE
• P_CURRENCY
Boolean
Select this if you want the parameter to be a check box.
Date or time
Select Date and time or Date only option.
Number
Select a Number Format.
String
Select a Page Element.
Select Choice list if you want a list with limited options (maximum 10).
Select List of values if you want a list with unlimited options with a search facility.
5. Select the Read Only check box if you don't want to enable users to set this parameter. When a parameter is set
as read only, the user is required to provide a default value to be passed to the job denition.
6. If you select list of values or choice list page element, select a List of Values Source and an Aribute.
314
Oracle Procurement Cloud Chapter 13
Implementing Procurement Enterprise Scheduler Job Denitions
7. From the list of available aributes, select the aributes you want to appear in the list and move them to the
selected aributes section. These aributes determine the values that the user can see.
8. Dene a Default Value for the parameter.
9. In the Tooltip Text eld, provide additional information for the user to follow.
10. Select the Required check box if users must set this parameter to submit the scheduled process.
11. Select the Do not Display check box if users should not see this parameter while submiing the process.
12. Click Save and Create Another or Save and Close.
Dependent Parameters
The aributes of some parameters depend on the aributes or values of certain other parameters. The aributes of a
parameter would change if the value of its dependent parameter changes.
For example, you have three parameters, namely Country, State and, City. In this case, the value of the Country
parameter would determine the values available in the State parameter. The values in the State parameter would
determine the values available in the City parameter.
315
Oracle Procurement Cloud Chapter 13
Implementing Procurement Enterprise Scheduler Job Denitions
Prerequisites
Create the parameters Region, Country and City. The values available to the users in the Country parameter list of
values depends on the value selected for the Region parameter. City parameter list of values depends on the value that
the user selects for the Country parameter.
1. On the Manage Job Denitions tab, open the Parameters sub tab.
2. Select the Region parameter.
3. Click the Manage Dependencies buon located next to the Delete buon.
4. From Available View Criteria, select getCountriesByRegion and move it to Selected View Criteria using the
move icons.
The selected view criteria appears in the Bind Variables section.
5. In the Bind Variables section, for the getCountriesByRegion view criteria, select Country from the mapped
parameters list of values.
The Country parameter list of values is now dependent on the value selected for the Region parameter.
6. Click OK.
7. Repeat the steps with Country parameter. Select getCitiesByCountries from the available view criteria and pass
City as a bind variable.
Job Sets
Job Sets
A job set is a collection of several jobs in a single process set that the users can submit instead of running individual
jobs separately. The job set denition also determines if the jobs run in serial or parallel, or based on some other
predetermined logic. In the Setup and Maintenance work area, go to the following:
• Functional Area: Application Extensions or a product-specic functional area
• Task: Manage Enterprise Scheduler Job Denitions and Job Sets
Use the Manage Enterprise Scheduler Job Denitions and Job Sets page to open the Manage Job Sets tab.
• On this tab, you can view and dene job sets, and use Query By Example to nd a specic job set.
• You can't edit or delete the predened job sets which are indicated by an asterisk. You can create job sets, and
also edit and delete job sets that are not predened.
316
Oracle Procurement Cloud Chapter 13
Implementing Procurement Enterprise Scheduler Job Denitions
System Properties
System Properties are the additional seings that determine how a job set runs. For example, you can use a system
property to determine the number of retries for a job set that fails to execute. On this tab, you can view and dene job
sets, and use Query By Example to nd a specic job set.
Field Description
Name Provide a name with only alphanumeric characters, for example, ExportMetadataTables1.
Note: A job set name can't have space or any special character.
Display Name Provide a name that the users see while submiing the scheduled process.
Description Provide more information about what the job set does.
Package Specify the path where you want to save the job set.
6. In the Job Set Steps section, select Serial or Parallel to dene the sequence of the job set.
7. Click Add Job Set Step to open the Add Step dialog box.
317
Oracle Procurement Cloud Chapter 13
Implementing Procurement Enterprise Scheduler Job Denitions
318
Oracle Procurement Cloud Chapter 13
Implementing Procurement Enterprise Scheduler Job Denitions
System Properties
This table lists some system properties with description.
SYS_ allowMultPending Species if the same job denition can have multiple pending requests.
SYS_ application Species the logical name of the Scheduling Services folder application used for request
processing. Oracle Enterprise Scheduler automatically sets this property during request
submission.
SYS_ eectiveApplication Species the logical name of the Scheduling Services folder application that is the eective
application used to process the request. You can associate a job denition, job type, or a
job set step with a dierent application by dening the EFFECTIVE_ APPLICATION system
property. This property can only be specied through metadata and cannot be specied as a
submission parameter.
SYS_priority Species the request processing priority. The priority interval is 0 to 9, where 0 is the lowest
priority and 9 is the highest. If this property is not specied, the default value used is 4.
SYS_ requestExpiration Species the expiration time for a request. This represents the time (in minutes) that a request
will expire after its scheduled execution time. An expiration value of zero (0) means that the
request never expires. If this property is not specied, the default value used is 0.
Request expiration only applies to requests that are waiting to run. If a request waits longer
than the specied expiration period, it does not run. After a request starts running, the request
expiration no longer applies.
SYS_retries Species the retry limit for a failed request. If request execution fails, the request is retried up
to the number of times specied by this property until the request succeeds. If the retry limit is
zero (0), a failed request is not retried. If this property is not specied, the default value used is
0.
319
Oracle Procurement Cloud Chapter 13
Implementing Procurement Enterprise Scheduler Job Denitions
320
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Related Topics
• Overview of Common Reference Objects
321
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Example
The following example is about importing the prole values using the web service. To import lookups or extensible
exelds, initiate the web service in the same way as shown here, after replacing the methods and other relevant values
in the code.
5. Run the following command to generate the JAX-WS proxy for the FndManageImportExportFilesService web
service.
C:\Program Files\Java\jdk1.7.0_04\bin>wsimport -s "d:\wsimport\FndManageImportExport" -d "d:\wsimport
\FndManageImportExport" http://<host>:<port>/fndAppCoreServices/FndManageImportExportFilesService?wsdl
import com.sun.xml.ws.developer.WSBindingProvider;
322
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
import java.io.File;
import java.io.IOException;
import java.util.List;
import java.util.Map;
import javax.xml.ws.BindingProvider;
import javax.xml.ws.WebServiceRef;
import javax.xml.ws.handler.Handler;
import oracle.webservices.ClientConstants;
import weblogic.wsee.jws.jaxws.owsm.SecurityPoliciesFeature;
// !THE CHANGES MADE TO THIS FILE WILL BE DESTROYED IF REGENERATED!
// This source file is generated by Oracle tools
// Contents may be subject to change
// For reporting problems, use the following
// Version = Oracle WebServices (11.1.1.0.0, build 130224.1947.04102)
requestContext.put(ClientConstants.WSSEC_KEYSTORE_TYPE,"jks");
// Provide location of 'mycompclient-keystore.jks' which was created during Step I)
requestContext.put(ClientConstants.WSSEC_KEYSTORE_LOCATION,"/home/user1/mycompclient-keystore.jks");
requestContext.put(ClientConstants.WSSEC_KEYSTORE_PASSWORD,"password");
requestContext.put(ClientConstants.WSSEC_RECIPIENT_KEY_ALIAS,"cdrmkey");
String id = invokeUploadFiletoUCMMethod(fndManageImportExportFilesService);
if (id != null) {
invokeUserProfileValuesDataLoader(fndManageImportExportFilesService, new Long(id));
}
}
323
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
try {
} catch (IOException e) {
System.out.println(e.getMessage());
}
catch(Exception e) {
System.out.println("Exception: "+e.getMessage());
}
try {
response = fndManageImportExportFilesService.uploadFiletoUCM(document);
System.out.println("Response: " + response);
} catch (ServiceException e) {
System.out.println(e.getMessage());
}
return response;
}
Note: Wherever applicable, replace the values referring to the prole values with those of the
lookups or exelds value sets.
324
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Here's a sample program that's a web service client for the asynchronous method deployFlexAsync(). This client
program starts callback client and does the asynchronous call. The required callback web service starts at the line no 58.
The callback web service will still be in Running state after the client program execution completes and you need to
close it manually. Alternatively, you can also comment the previous line here and run it in a separate client program.
package com.ws.client;
import com.sun.xml.ws.api.addressing.AddressingVersion;
import com.sun.xml.ws.api.addressing.WSEndpointReference;
import com.sun.xml.ws.developer.WSBindingProvider;
import com.sun.xml.ws.message.StringHeader;
import com.ws.client.callback.ApplicationsCoreSetupServiceResponseImpl;
import com.ws.client.types.DeployFlexAsyncResponse;
import java.util.Map;
import java.util.UUID;
import javax.xml.ws.Endpoint;
import javax.xml.ws.Response;
import javax.xml.ws.WebServiceRef;
import oracle.webservices.ClientConstants;
import weblogic.wsee.jws.jaxws.owsm.SecurityPolicyFeature;
// !THE CHANGES MADE TO THIS FILE WILL BE DESTROYED IF REGENERATED!
// This source file is generated by Oracle tools
// Contents may be subject to change
// For reporting problems, use the following
// Version = Oracle WebServices (11.1.1.0.0, build 150302.2135.1.30348)
ApplicationsCoreSetupService applicationsCoreSetupService =
applicationsCoreSetupService_Service.getApplicationsCoreSetupServiceSoapHttpPort(features);
requestContext.put(ClientConstants.WSSEC_KEYSTORE_TYPE, "jks");
requestContext.put(ClientConstants.WSSEC_KEYSTORE_LOCATION,
"/scratch/vgarikip/view_storage/work/keys/mycompclient-keystore.jks");
requestContext.put(ClientConstants.WSSEC_KEYSTORE_PASSWORD,
"mypassword1");
325
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
requestContext.put(ClientConstants.WSSEC_RECIPIENT_KEY_ALIAS,
"cdrmkey");
requestContext.put(WSBindingProvider.USERNAME_PROPERTY,
"app_impl_consultant");
requestContext.put(WSBindingProvider.PASSWORD_PROPERTY, "mypassword1");
applicationsCoreSetupService.deployFlexAsync("PER_CITIZENSHIPS_DFF", "DFF",
false); //.deployPatchedFlexAsync(mode, pCustomizationId, pCustomizationSetLoc);
System.out.println("####END OF WS CALL");
Thread.sleep(10000);
Example callback web service start utility if you comment line no 58 in the previous program:
package com.ws.client;
import com.ws.client.callback.ApplicationsCoreSetupServiceResponseImpl;
import javax.xml.ws.Endpoint;
}
}
326
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Dene Lookups
Overview of Lookups
Lookups are lists of values in applications. You dene a list of values as a lookup type consisting of a set of lookup
codes, each code's translated meaning, and optionally a tag. End users see the list of translated meanings as the
available values for an object.
Lookups provide a means of validation and lists of values where valid values appear on a list with no duplicate values.
For example, an application might store the values Y and N in a column in a table, but when displaying those values in
the user interface, Yes or No (or their translated equivalents) should be available for end users to select. For example,
the two lookup codes Y and N are dened in the REQUIRED_INDICATOR lookup type.
The following table contains an example of a lookup type for marital status (MAR_STATUS) that has lookup codes for
users to specify married, single, or available legal partnerships.
In this case, tags are used for localizing the codes. All legislations list Married and Single. Only the Dutch legislation lists
Registered Partner. And all legislations except France and Australia also list Domestic Partner.
327
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
statuses in a report. The lookup code values include All, so that users can report by all statuses: Approved, Resubmied
for approval, Pending or rejected, and Rejected.
Conguration Level
The conguration level of a lookup type determines whether the lookups in that lookup type can be edited. This applies
data security to lookups.
Some lookup types are locked so no new codes and other changes can be added during implementation or later, as
needed. Depending on the conguration level of a lookup type, you may be able to change the codes or their meanings.
Some lookups are designated as extensible, so new lookup codes can be created during implementation, but the
predened lookup codes can't be modied. Some predened lookup codes can be changed during implementation or
later, as needed.
The conguration levels are user, extensible, and system. The following table shows the lookup management tasks
permied at each conguration level.
Updating start date, end date, Yes Yes, only if the code isn't No
and enabling the lookup code predened data
If a product depends on a lookup, the conguration level must be system or extensible to prevent deletion.
Once the conguration level is set for a lookup type, it can't be modied. The conguration level for newly created
lookup types is by default set at the User level.
328
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Standard lookups are the simplest form of lookup types consisting only of codes and their translated meaning. They
dier from common lookups only in being dened in the standard lookup view. Common lookups exist for reasons
of backward compatibility and dier from standard lookups only in being dened in the common lookup view. These
can also be lookups having aribute columns. Set-enabled lookup types store lookup codes that are enabled for
reference data sharing. At runtime, a set-enabled lookup code is visible because the value of the determinant identies
a reference data set in which the lookup code is present.
Accessing Lookups
Standard, set-enabled, and common lookups are dened in the Standard, Set-enabled, and Common views,
respectively. Applications development may dene lookups in an application view to restrict the UI pages where they
may appear.
In lookups management tasks, lookups may be associated with a module in the application taxonomy to provide
criteria for narrowing a search or limiting the number of lookups accessed by a product specic task such as Manage
Purchasing Lookups.
Enabling Lookups
A lookup type is reusable for aributes stored in multiple tables.
Enable lookups based on the following.
If you make changes to a lookup, users must sign out and back in before the changes take eect. When dening a list of
values for display rather than validation, limit the number of enabled lookup codes to a usable length.
To view the predened lookups and their lookup codes, use the following tasks in the Setup and Maintenance work
area:
Translating Lookups
You can translate the lookups that you dened to the preferred language(s) without changing the language session
of the application. Use the translation option available on the lookup code table. By default, for each lookup, all the
permied language rows in the translator dialog box appear in the source language (the current session language).
When you edit a particular language entry, you can modify the translated meaning and description to the language in
which you want the lookup to appear. Once the updates are made, the end-users can view the lookup in the translated
text.
329
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Note: You can add the translation for only as many languages as are permied by the administrator.
The functionality to limit the number of languages displayed on the dialog box is controlled through the
Translation Editor Languages prole option. It can be set at the SITE or USER level. If nothing is specied, all
active languages are displayed.
Related Topics
• Enter or Edit Translated Text
Meaning Status
After you dene the lookup type, you need to dene the lookup codes and their related details. The following table lists
the lookup codes you dene for the COLORS lookup type.
BLUE Urgent No 4
330
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
The following table lists the meanings and the codes that were enabled. They appear in the order of the dened display
sequence.
Stop RED
Check YELLOW
Proceed GREEN
Analysis
The BLUE lookup code wasn't enabled and doesn't appear in the list of values. The display sequence of values in the list
of values is alphabetic, unless you enter a number manually to determine the order of appearance. Number 1 indicates
the rst value that appears in the list. Only lookups that are enabled and active between start and end dates are visible.
1 Jane RED
2 Bob YELLOW
3 Alice BLUE
The status for one user is BLUE because at the time they entered a value, BLUE was enabled. Disabling a lookup code
doesn't aect transaction records in which that code is stored. Data querying and reporting have access to disabled
lookup codes in transaction tables.
331
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
The following table elaborates the example, how these two reference data sets (US and EU) contain one lookup code
that's common, but each diering in its lookup meaning.
US RED Red
US YELLOW Yellow
US GREEN Green
EU RED Rouge
EU ORANGE Orange
Some lookup codes may be unique to one or another reference data set as the ORANGE lookup is to the EU reference
data set in the example.
In another example in the following table, a lookup type called HOLD_REASON provides a list of reasons for puing a
contract renewal on hold. Reference data sets determine which codes are included in the Hold Reason list of values.
332
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Referring to the example in the table, when end-users place a contract on hold in the US business unit, the three reason
codes in the US set are available. When placing a contract on hold in the China business unit, the two codes in the China
set are available.
Import Lookups
On each page pertaining to the tasks of managing the Standard, Common, and Set Enabled lookups, use the Import
option to import the lookup type and lookup code information.
Prerequisite
The separate les containing the lookup types and lookup codes are already available in the document repository of
Oracle WebCenter Content.
Importing Lookups
To import lookups:
1. In the Setup and Maintenance work area, go to the Manage Standard Lookups task. Depending on the lookup
you want to import, you may select the other lookup tasks.
2. In Search Results, from the Actions menu, select Import.
Note: If the import fails, click the link to the log le on the conrmation dialog box and examine the
cause of failure.
333
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
• Use a vertical bar or pipe ( | ) as a delimiter between elds for both header and value rows.
• Set the le encoding to UTF-8 without the Byte Order Mark (BOM), as per the Oracle WebCenter Content
specication.
The following sections contain details about the specic lookup types and codes.
Prerequisite
You must have worked with lookups in Oracle Cloud applications.
Here's a sample le that contains the header values at the beginning of the le, followed by line entries of the two
lookup types that are to be imported. For importing several lookup types, add more line entries in a similar format.
LookupType|Meaning|Description|ModuleType|ModuleKey
AFLOG_22APR_1|Log1|AFLOG_desc_1|APPLICATION|FND
PROD_22APR_2|Product1|PROD_desc_2|APPLICATION|FND
To create a le containing the lookup codes, include the following headers.
• Required headers:
• Optional headers:
◦ StartDateActive:Beginning of the date range during which the lookup code is active and visible on the
page. The format is dd/M/yyyy.
334
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
◦ EndDateActive:End of the date range during which the lookup code is active and visible on the page. The
format is dd/M/yyyy.
◦ Description: Description of the lookup code.
◦ Tag: Any tag associated with the lookup code that may be used for a quick reference or retrieval of
information.
◦ Seg: The name of the API used for a global segment dened for the descriptive exeld associated with
the lookup.
◦ CONTEXT_ATTRIBUTE: The context value specied in the CSV le for a particular descriptive exeld.
◦ ctxSeg: The name of the API for a context sensitive segment dened for a context aribute.
To create a le containing the set enabled lookup codes, include the following headers.
• Required headers:
• Optional headers:
◦ StartDateActive:Beginning of the date range during which the lookup code is active and visible on the
page. The format is dd/M/yyyy.
335
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
◦ EndDateActive:End of the date range during which the lookup code is active and visible on the page. The
format is dd/M/yyyy.
◦ Description: Description of the lookup code.
◦ Tag:Any tag associated with the lookup code that may be used for a quick reference or retrieval of
information.
Here's a sample le that contains the header values at the beginning and lists four set enabled lookup codes to be
imported. For importing several lookup codes, add more entries in the same format.
LookupType|LookupCode|DisplaySequence|EnabledFlag|StartDateActive|EndDateActive|Meaning|Description|Tag|
SetName
DATA_22APR_1|Code1_1|1|Y|25/12/2014|25/5/2015|DATA_22apr_1|Data_desc_1|Tag1_1|TEST SET CODE 2
DATA_22APR_1|Code1_2|2|N|25/1/2014|25/11/2015|DATA_22apr_2|Data_desc_2|Tag1_2|TEST SET CODE 3
DATA_22APR_2|code2_1|3|N|25/12/2012|25/7/2015|DATA_22qpr_2_1|Data_desc_2|tag2_1|TEST SET CODE 2
DATA_22APR_2|code2_2|3|Y|25/12/2012|25/7/2015|DATA_22qpr_2_2|Data_desc_2_2|tag2_2|TEST SET_ERR_CODE_Z
Related Topics
• Overview of Files for Import and Export
• Guidelines for File Import and Export
• Upload Files to WebCenter Content Server
Each task contains a predened set of lookup types that are classied and stored. Open a task to search and edit the
required lookup. However, you may not be able to edit a lookup if its conguration level doesn't support editing.
336
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Related Topics
• Use Query By Example
Validation of values One to one match of meaning to code Validation by format or inclusion in a table
included in a lookup view, or through the
determinant of a reference data set
Length of value Text string up to 30 characters Any type of variable length from 1 to 4000
Both lookup types and value sets are used to create lists of values from which users select values.
A lookup type can't use a value from a value set. However, value sets can use standard, common, or set-enabled
lookups.
337
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Manage Messages
Messages
Messages provide users with information about business or application errors or warnings.
Typically, messages inform the users about the following:
Besides notifying users about the problem, messages provide guidance to users on taking corrective action. Messages
also warn users about the consequences of a certain action.
Oracle provides a set of predened messages that are stored in a message dictionary. You can create additional
messages or modify the existing ones using the Manage Messages task in the Setup and Maintenance work area.
Note: Don't delete predened messages unless you're sure that they aren't used anywhere.
Message Dictionary
The message dictionary stores messages that the application requires at run time. Messages are predened for specic
applications and modules, but a few are common messages that can be used in any application or module.
When you create messages, use the message text and the following components to cover additional details addressing
users and help desk personnel:
• User Details: A detailed explanation of the message short text meant for users.
• Administrator Details: Details of the identied problem meant for the help desk personnel. The end users don't
see this text.
• Cause: An end-user version of the cause of error.
• User Action: Instructions to users for addressing the identied problem. Where there is no guidance for end
users, they must approach the help desk.
• Administrator Action: Corrective action that help desk personnel must take to correct the problem. This
information isn't available to the end users.
338
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Message Types
All messages must be associated with a message type. You can select the message type based on the message severity.
The available message types are:
• Error
• Warning
• Information
• UI String
Error Messages
Use the Error message to inform users about, for example, entering incorrect data or performing actions that trigger
validation. Error messages also inform users how to correct the situation so that they can continue with their task.
For example: You can't specify a task without specifying the project.
Error messages also tell users about any serious problem with the application or process, and when they must seek
assistance from the help desk. Some error messages trigger incidents or logs and have a mechanism to notify the help
desk automatically.
Warning Messages
Use the Warning message type to inform users about an application condition or a situation that might require their
decision before they can continue.
Warning messages:
• Describe the reason for the warning and potential consequence of the selected or intended user action.
• Can be either a question or a statement.
For example: You delete the primary user. Do you want to continue?
Information Messages
The Information message type tells users about changes in the application, a page, or a business object. These
messages aren't triggered by users, and they don't have to take any immediate action in response.
For example: No events have been started or processed for this employee.
Use the Information message type to communicate information that's neither an error nor a warning.
UI String Messages
Use the UI string message type to store shorter messages such as UI prompts, titles, or translated text, in the message
dictionary.
Related Topics
• Message Groups
339
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Creating a Message
To create a message, perform the following steps:
1. In the Setup and Maintenance work area, go to the Manage Messages task.
2. On the Manage Messages page, click the New icon.
3. On the Create Message page, enter details in each section.
4. In the Message Properties section:
a. Enter a unique message name that helps you nd the messages you create and avoid name conicts with
predened messages. Use underscore as a separator if the name contains multiple parts.
b. Select the application and module to associate the message with.
c. Enter a unique number that can be used as an identier for the message. Users can quote this number
when they contact the help desk for assistance.
Note: You can use any number between 10,000,000 and 10,999,999. This number range
is allocated for the messages you create. At runtime, this number appears along with the
application code after the message text, for example FND-2774.
d. In the Translation Notes eld, enter a description of the message indicating its use.
e. Select the relevant message type, category, and severity.
f. Select the Logging Enabled check box to create incidents or logs when messages appear on the UI.
5. In the Message Text section:
a. In the Short Text eld, provide the actual message text that appears on the page at runtime.
The short text can include tokens that are placeholders for displaying dynamic values at runtime.
However, to support easy translation, keep the message length (including values of tokens) within 160
characters in American English.
b. In the User Details eld, enter information for the users to know why the message appeared. You can also
include information for the users to resolve the issue themselves.
If your Short Text component has tokens that expand the text beyond the 160-character limit, move that
portion of text here.
c. In the Administrator Details eld, provide a detailed technical explanation of the message. This eld is
only visible to the help desk.
d. In the Cause eld, provide a concise explanation of why the message appears. This text is visible to the
users.
This information is optional and is only applicable to messages of type Error and Warning. However, if
you mention the cause, you must mention in the User Action eld the action that users must take.
e. In the User Action eld, enter the user action to guide the users with steps to respond to the message and
complete the task.
f. In the Administrator Action eld, provide information that the help desk can use to resolve the problem.
6. In the Message Tokens section, dene tokens that you want to use in this message.
7. Click Save and Close.
340
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Editing a Message
You can edit a predened message or a message that you created.
To edit a message, search for a message on the Manage Messages page and perform the following steps:
1. Select the existing message and click the Edit icon.
2. On the Edit Message page, modify the existing details according to the instructions provided in the Creating a
Message procedure.
Note: Don't edit the message number for predened messages.
Related Topics
• Message Groups
• Enter or Edit Translated Text
Use the Manage Messages task in the Setup and Maintenance work area to create and manage tokens. You must edit a
message to dene tokens for it. You can create tokens for a message and also delete them. However, you can't edit or
delete the predened tokens.
Token Denition
To dene a token, you must provide the following information:
• A unique name for the token.
• The type of data that the token replaces at run time. Available types are Date, Number, or Text.
• A description about what the token represents at run time.
Guidelines
Follow these general guidelines while dening tokens:
• Use curly brackets and all uppercase leers for the token names.
• Use underscore as a separator for a name containing two words or more.
341
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
The following table contains specic guidelines for each token data type.
Text Use tokens for substituting any variable text element that qualies as a noun.
Number Plan carefully while using tokens for numbers especially, where a token could refer to either a
singular or a plural number. You can use tokens for numbers representing an order, customer,
or any other business object bearing a numeric value.
Date Clearly dene the context of the date, such as the start date, or end date, or a date range.
Note: If you don't set any value to the prole option, the visibility of the message component is determined
by the default prole option seings.
Common Messages
Message names that begin with FND_CMN are common messages. Each common message can appear in multiple
places in any product family across Oracle Applications Cloud. For example, the FND_CMN_NEW_SRCH message can be
used for any search to indicate that no results were found. Common messages of type error or warning are part of the
message dictionary.
Common messages can be used in any application. Therefore, consider the ramications if you edit any aspect of the
message, including incident and logging seings. Changes would be reected in all instances where the message is
342
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
used. For example, if you change the message text, ensure that the text is generic and applies to the entire site of Oracle
Applications Cloud implementation.
• Automatic
• Manual
• Gapless
Note: Plan your document sequencing carefully before you start applying sequence numbers. Avoid
switching to a dierent mode after you saved your work on the Manage Document Sequences and Manage
Document Sequence Categories pages.
Automatic Sequencing
Automatic document sequencing assigns a unique number to each document automatically when the document is
generated. That unique number is stored in the database. You can set an initial value for the numbering sequence.
Thereafter, the numbering is sequential by date and time of creation. If you don't provide an initial value, the application
sets the default initial value as 1.
Manual Sequencing
Use the manual sequencing mode to assign a unique number to each document before the document is generated. In
manual sequencing, the numeric ordering and completeness of a transaction isn't automatically enforced. As a result,
users can skip or omit numbers when entering the sequence value. However, each time a user assigns a number, the
application validates its uniqueness.
Gapless Sequencing
Gapless sequencing is similar to automatic sequencing. It automatically generates a unique number for each document,
but does that only for successfully generated documents. Sequence numbers aren't assigned to incomplete or failed
documents. As a result, the sequence is maintained for all the successfully generated documents.
Additionally, you can control the gapless document sequencing by enforcing the Transaction Date Validation option.
When enabled, this option checks for the transaction date of a particular document and assigns the sequence number
accordingly, to chronologically maintain the documents. The sequence numbers and the transaction dates are
chronologically correlated to prevent any mismatch of a new document sequence assigned to an older document or an
older document sequence assigned to a new document.
Note: Use this type of sequencing only if necessary because it may aect the performance of the application
and slow down transaction processing.
343
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Related Topics
• Modules in Application Taxonomy
Note: Once a document sequence category is created, you can't change the application, the category code, or
the table name. Therefore, carefully consider these details and plan your document sequencing requirement
before you begin working with the application.
Once you create a document sequence category, it's available for use in the Document Sequences: Assignments
section on the Manage Document Sequences page. The Category eld contains the name of the document sequence
category. After you create a document sequence, you can assign it to a document sequence category.
• Determine beforehand the mode of document sequencing, because you can't switch to other types once a
sequence is in use.
• Note details such as the document sequence and document sequence category, for later reference.
• Identify if there are any restrictions or conguration prerequisites.
Note: Products that implement document sequencing have specications about its usage. Refer to the
corresponding product documentation for specic details and also to determine if there are any restrictions or
conguration prerequisites.
344
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
eld blank, the rst document is automatically assigned a value of 1. Once a document sequence is dened, you
can't change this initial value.
Related Topics
• Guidelines for Managing Modules in Application Taxonomy
Dene Trees
Overview of Trees
Trees are hierarchical data models that you can use to organize data, apply business rules, control data access, and
improve performance while querying. For example, an application maintains data of an organization called Vision
345
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Corporation that has two departments: Marketing and Finance. The Finance department has two functional divisions:
Receivables and Payables. You can dene a tree for Vision Corporation to establish a hierarchy across its departments,
and their respective functional divisions. You can use the hierarchy to manage data at various levels of the organization.
To work with trees, in the Setup and Maintenance work area, use any of the following tasks:
• Manage Tree Structures: To create and update tree structures. You must rst dene a tree structure to create a
tree.
• Manage Trees and Tree Versions: To create and update trees and their versions.
• Manage Tree Labels: To create and update tree labels.
Tree Structures
As the name suggests, tree structures provide you the framework to organize data such that you can establish a
hierarchy for use by the tree. So, similar to a template, a tree structure guides the creation of a tree.
Tree
A tree is an instance of the tree structure. The root node is the highest nodal point of a tree. Child nodes branch o from
the root node. Child nodes at the same level, branching o from a common parent node, are called siblings. Leaves are
details branching o from a node but not extending further down the tree hierarchy. You can create trees for multiple
data sources and share them across applications.
Tree Versions
A tree by default has only one version. If required, you can create and maintain more than one editable tree version. At
any point, only one tree version must be active. If you edit an existing version, it changes from active to draft. To use it
again, you must set it to active. Similar to any other version control system, versions of trees are maintained to track all
the changes that a tree undergoes in its life cycle.
Tree Labels
Tree labels are short names given to trees and tree structures. You can label the tree versions for beer accessibility and
information retrieval. When nodes are created in a tree, the existing tree labels are automatically assigned to the new
tree nodes. You can use any table to store the labels and register the label data source with the tree structure.
An administrator controls the access to tree structures through a set of rules that are periodically audited for validity.
346
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Modication
You can modify the predened tree structures as well as those you create. However, modifying a predened tree
structure is restricted and permied through additional privileges. Modication is limited to specic tree nodes and
lower in the tree hierarchy.
Status
When you change the status of a tree structure, the status of the trees and tree versions associated with that tree
structure also changes.
The following table lists the dierent statuses of a tree structure.
Status Meaning
Active In use, indicating that one or more trees or tree versions are created from the tree structure.
347
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Status Meaning
Running an Audit
Seing the status of a tree structure to active automatically triggers an audit of that tree structure. To manually trigger
an audit, select Audit from the Actions menu on the Manage Tree Structures page. The Tree Structure Audit Result table
shows a list of validations that ran against the selected tree structure.
Audit Validators
The following table lists the validators used in the audit process and describes what each validator checks for. It also lists
possible causes for validation errors and suggests corrective actions.
Restrict By Set ID Manage Tree Even when the check If reference data set
Structures: Specify If you select the box is selected, one or restriction is required
Data Sources Reference Data Set more data source view for this tree structure,
check box for the objects doesn't contain include a reference
Restrict Tree Node a reference data set data set aribute
List of Values Based aribute. on all data sources.
on option, each of Otherwise, deselect the
its data source view check box.
objects must have
a reference data set
aribute.
348
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Row Flaened Table Manage Tree You must specify a • The specied Correct the row
Name Structures: Specify valid row aened table doesn't aened table
Performance Options table for the tree exist in the denition.
structure. It can either database.
be the standard row • The specied
aened table FND_ table doesn't
TREE_NODE_RF or contain
another table. the same
columns as the
FND_TREE_NODE_RF
table.
Available Data Sources Add Data Source Each data source view • Any of the • Correct the
object specied for the specied data specied data
tree structure must be source view source view
accessible, and all its objects doesn't object.
primary key aributes exist. • Correct the
must be valid. • When you dene duplicate
a data source column in the
view object, registered
keep the Use primary keys.
non-dened • Correct the
primary key primary keys
columns check of the specied
box deselected. data source view
The database object.
automatically • Correct any
registers the mismatch in
primary keys for data types.
the view object.
Select this check
box if you want
the database
to register the
primary keys
349
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
you specify.
However, if
the registered
primary keys
contain any
duplicates, this
validation fails.
• The Use non-
dened primary
key columns
check box is
selected in a
data source,
but the list
of specied
primary key
columns doesn't
match the
primary keys
dened in the
corresponding
data source view
object.
• Any common
aribute that
exists in both
the data source
view object and
the tree node
view object isn't
of the same data
type in both view
objects.
Column Flaened Manage Tree You must specify a • The specied Correct the column
Table Name Structures: Specify valid column aened table doesn't aened table
Performance Options table for the tree exist in the denition.
structure. It can either database.
be the standard row • The specied
aened table FND_ table doesn't
TREE_NODE_CF or contain
another table. the same
columns as the
FND_TREE_NODE_CF
table.
Restrict by Date Manage Tree Even when the check If the date restriction
Structures: Specify If you select the Date box is selected, one or is required for this tree
Data Sources Range check box for more of its data source structure, include the
the Restrict Tree view objects doesn't eective start date
Node List of Values contain eective start and eective end date
Based on option for date and end date aributes on all data
a tree structure, each aributes. sources. Otherwise,
of its data source view deselect the check box.
objects must have
eective start date and
end date aributes.
This validation doesn't
take place when
350
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Tree Node Table Name Manage Tree You must specify a • No table is Correct the tree node
Structures: Specify valid tree node table specied in table denition.
Denition for the tree structure. the Tree Node
It can either be the Table eld.
standard row aened • The specied
table FND_TREE_NODE table doesn't
or another table. exist in the
database.
• The specied
table doesn't
contain
the same
columns as the
FND_TREE_NODE
table.
Labeling Schemes
Selecting a labeling scheme determines how the tree nodes are labeled. You may select a labeling scheme to assign at
the data source level, at the parent node level, or keep it open for customers assignment. You may also choose not to
have any labeling scheme. However, if you decide to use any of the labeling schemes, select the following additional
options, to restrict the list of values that appear in the selected tree node.
• Allow Ragged Nodes: To include nodes that have no child nodes, and are shorter than the remaining nodes in
the entire hierarchy.
• Allow Skip Level Nodes: To include nodes that are at the same level but have parent nodes at dierent levels.
• Date Range: Species whether a selection of nodes should be restricted to the same date range as the tree
version.
• Allow Multiple Root Nodes: Allows you to add multiple root nodes when creating a tree version.
• Reference Data Set: Species whether a selection of nodes should be restricted to the same set as the tree.
351
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Note: Parameter values modied at the tree level override the default values specied at the tree-structure
level.
The data source parameters are applied to any tree version belonging to that data source, when performing node
operations on the tree nodes. Data source parameters also provide an additional level of ltering for dierent tree
structures. The tree structure denition supports three data source parameter types.
• Bound Value: Captures any xed value, which is used as part of the view criteria condition.
• Variable: Captures and binds a dynamic value that's being used by the data source view object. This value is
used by the WHERE condition of the data ow.
• View Criteria: Captures the view criteria name, which is applied to the data source view object.
You can also specify which of the data source parameters are mandatory while creating or editing the tree structure.
View objects from the Oracle ADF business components are used as data sources. To associate the view object with the
tree structure, you can pick the code from Oracle ADF business component view objects and provide the fully qualied
name of the view object, for example, oracle.apps.fnd.applcore.trees.model.view.FndLabelVO.
Row Flaening
Row aening optimizes parent-child information for run-time performance by storing additional rows in a table for
instantly nding all descendants of a parent without initiating a CONNECT BY query. Row aening eliminates recursive
queries, which allows operations to perform across an entire subtree more eciently.
To store row aened data for the specic tree structure, users can either use the central FND_TREE_NODE_RF table or
they can register their own row aened table. For example, in a table, if Corporation is the parent of Sales Division
(Corporation-Sales Division), and Sales Division is the parent of Region (Sales Division-Region), a row-aened table
contains an additional row with Corporation directly being the parent of Region (Corporation-Region).
Column Flaening
Column aening optimizes parent-child information for runtime performance by storing an additional column in a
table for all parents of a child.
To store column aened data for the specic tree structure, users can either use the central FND_TREE_NODE_CF table or
they can register their own column aened table. For example, in a table, if Corporation is the parent of Sales Division
(Corporation-Sales Division), and Sales Division is the parent of Region (Sales Division-Region), a aened table in
addition to these columns, contains three new columns: Region, Sales Division, and Corporation. Although positioned
next to each other, the column Region functions at the lower level and Corporation at the higher level, retaining the data
hierarchy.
352
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
BI View Object
View objects from Business Intelligence can be used as data sources, eliminating the need to create new types of data
sources. This eld is to store the fully qualied name for the BI view object generated by the tree management for
business intelligence reporting and usage The BI view object is a combination of the tree data source and column
aened entity. Using this option prevents data redundancy and promotes greater reuse of existing data, thereby
improving the performance of the tree structure.
Level Labels that are automatically assigned based on the data source to which the tree node
belongs. A level label points to a specic data source. For example, in a tree that reects
the organizational hierarchy of an enterprise, all division nodes appear on one level and all
department nodes on another.
Depth Labels that are automatically assigned based on the depth of the tree node within the tree. No
manual assignment is performed.
Note: In an unbalanced hierarchy, a level may not be equal to depth.
353
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Note: Parameter values modied at the tree level will override the default values specied at the tree-
structure level.
When you edit a tree version bearing Active status, the status changes to Draft until the modications are saved or
canceled. To edit a tree version while keeping the status active select the Update tree nodes while keeping the tree
version active Check Box.
Running an Audit
An audit automatically runs whenever a tree version is set to active. You can also manually trigger an audit on the
Manage Trees and Tree Versions page, using Actions > Audit. If you run an audit on a tree version, which is in Draft
status, and want to change the status to Active after the audit is complete then select the Set tree version status to
active after audit is successfully complete Check Box.
The Tree Version Audit Result table shows a list of validations that ran against the selected tree version.
Validation Details
The following table lists the validators used in the audit process and describes what each validator checks for. It also lists
possible causes for validation errors and suggests corrective actions.
Validator Description (what's checked) Possible Cause for Validation Suggested Corrective Action
Failure
Eective Date The eective start and end The eective end date is set to Modify the eective start
dates of the tree version must a value that isn't greater than and end dates such that the
be valid. the eective start date. eective start date is earlier
than the eective end date.
354
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Validator Description (what's checked) Possible Cause for Validation Suggested Corrective Action
Failure
Root Node Even if the check box is Modify the tree version such
On the Manage Tree deselected, the tree version that there is exactly one root
Structures: Specify Data has multiple root nodes. node.
Sources page, if the Allow
Multiple Root Nodes check
box for the Restrict Tree
Node List of Values Based
on option isn't selected, and if
the tree structure isn't empty,
the tree version must contain
exactly one root node. This
validation doesn't take place if
the check box is selected.
Data Source Maximum Depth The tree version has data Modify the tree version such
For each data source in the at a depth greater than the that all nodes are at a depth
tree structure, on the Data specied depth limit on one or that complies with the data
Source dialog box, if the data more data sources. source depth limit.
source is depth-limited, the
data in the tree version must
adhere to the specied depth
limit. This validation doesn't
apply to data sources for
which the Maximum Depth
eld is set to Unlimited.
Duplicate Node Even when the check box is Remove any duplicate nodes
On the Data Source dialog deselected, the tree version from the tree version.
box, if the Allow Duplicates contains duplicate nodes.
check box isn't selected, the
tree version must not contain
more than one node with the
same primary key from the
data source. If the check box is
selected, duplicate nodes are
permied.
Available Node All nodes in the tree version • A node in the tree Remove any orphaned nodes
must be valid and available in version doesn't exist from the tree version. Update
the underlying data source. in the data source. tree reference nodes so that
Deleting data items they reference existing tree
from the data source versions.
without removing the
corresponding nodes
from the tree version
can result in orphaned
nodes in the tree
version. For example,
if you added node A
into your tree version,
and subsequently
deleted node A from
the data source without
removing it from
the tree version, the
validation fails.
• The tree version
contains a tree
reference node, which
references another tree
355
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Validator Description (what's checked) Possible Cause for Validation Suggested Corrective Action
Failure
Node Relationship All nodes must adhere to the The tree structure has data Modify the tree version
relationships mandated by the sources arranged in a parent- such that the nodes adhere
data sources registered in the child relationship, but the to the same parent-child
tree structure. nodes in the tree don't adhere relationships as the data
to the same parent-child sources.
relationship. For example, if
the tree structure has a Project
data source with a Task data
source as its child, Task nodes
must always be within Project
nodes in the tree version.
This validation fails if there
are instances where a Project
node is added as the child of a
Task node.
SetID Restricted Node Even when the check box is Modify the tree version such
On the Manage Tree selected, the tree version has that all nodes in the tree have
Structures: Specify Data nodes whose data source data sources with reference
sources page, if the Set ID values belong to a dierent data set matching that of the
check box is selected to enable reference data set than the tree.
the Restrict Tree Node List tree.
of Values Based on option for
each tree node, the underlying
node in the data source must
belong to the same reference
data set as the tree itself. This
restriction doesn't apply when
the check box isn't selected.
Label Enabled Node The tree structure has a Assign a label to any node that
On the Manage Tree labeling scheme but the tree doesn't have a label.
Structures: Specify Data version has nodes without
Sources page, if a labeling labels.
scheme is specied for the
tree structure by selecting a
list item from the Labeling
Scheme list, all nodes must
have labels. This restriction
doesn't apply when you select
None from the Labeling
Scheme list.
Date Restricted Node Even when the check box is Ensure that all nodes in the
On the Manage Tree selected, there are data source tree version have eective
Structures: Specify Data nodes that have a date range date range for the eective
Sources page, if the Date beyond the tree version's date range for the tree
Range check box is selected eective date range. For version.
to enable the Restrict Tree example, if the tree version
Node List of Values Based is eective from Jan-01-2012
on option for a tree structure, to Dec-31-2012, all nodes
each node in the underlying in the tree version must be
data source must have an eective from Jan-01-2012 to
eective date range same as Dec-31-2012 at a minimum. It
the eective date range of the is acceptable for the nodes to
tree version. This restriction be eective for a date range
356
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Validator Description (what's checked) Possible Cause for Validation Suggested Corrective Action
Failure
Multiple Active Tree Version Even when the check box isn't Set no more than one tree
On the Manage Tree selected, there is more than version to Active within the
Structures: Specify Denition one active tree version in the same date range and set the
page, if the Allow Multiple tree for the same date range. others to inactive or draft
Active Tree Versions check status.
box isn't selected for the tree
structure, there must not be
more than one active tree
version for a tree at any time.
This restriction doesn't apply if
the check box is selected.
Range Based Node Even when the check box isn't Ensure that any range nodes
On the Data Source dialog selected, there are range- in your tree version are from a
box, if the Allow Range based nodes from a data data source that allows range
Children check box isn't source. children.
selected, range-based nodes
aren't permied from that
data source. This restriction
doesn't apply if the check box
is selected.
Terminal Node Even when the check box Modify the tree version such
On the Data Source dialog isn't selected, values from a that all terminal nodes are
box, if the Allow Use as data source are added as leaf from data sources for which
Leaves check box isn't nodes (terminal nodes). this check box is selected.
selected, values from that
data source can't be added as
leaves (terminal nodes) to the
tree version. This restriction
doesn't apply if the check box
is selected.
357
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Access Control
Source data is mapped to tree nodes at dierent levels in the database. Therefore, the changes you make to the tree
nodes aect the source data. Access control set on trees prevents unwanted data modications in the database. Access
control can be applied to the tree nodes or anywhere in the tree hierarchy.
Tree Nodes
Tree nodes are points of data convergence where a tree branches into levels. Nodes are the building blocks of a tree
structure and are aached to tree versions. Whenever you create or edit a tree version, you need to specify its tree node.
In the Setup and Maintenance work area, open the panel tab and click Search to search for the Manage Trees and Tree
Versions task.
Node Levels
Usually, the nodes at a particular level represent similar information. For example, in a tree that reects the
organizational hierarchy, all nodes representing divisions appear at one level and all the department nodes on another.
Similarly, in a tree that organizes a user's product catalog, the nodes representing individual products might appear at
one level and the nodes representing product lines on the immediate higher level.
The following node levels are in use:
• Root node: The highest node in the tree structure
• Parent node: The node that branches o into other nodes
• Child node: The node that's connected to a node higher in hierarchy (parent node)
• Sibling node: Nodes that are at the same level and belong to the same parent node
• Leaf node: Entities branching o from a node but not extending further down the tree hierarchy
Node Types
A tree node has the following node types.
• Single: Indicates that the node is a value by itself.
358
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
• Range: Indicates that the node represents a range of values and possibly could have many children. For
example, a tree node representing account numbers 10000 to 99999.
• Referenced Tree: Indicates that the tree node is actually another version for the tree based on the same tree
structure, which isn't physically stored in the same tree. For example, a geographic hierarchy for the United
States can be referenced in a World geographic hierarchy.
In the Setup and Maintenance work area, use any of the following tasks:
• Manage Prole Options
• Manage Prole Categories
• Manage Administrator Prole Values
Manage Prole Options Create new prole options or modify existing prole options, except some which are
predened and restricted to prevent any modications.
Manage Prole Categories Group the prole options based on their functional similarities.
Manage Administrator Prole Values Set the prole values for the enabled prole options to control application behavior.
359
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
After you create or edit a prole option on the Manage Prole Options page, you must enable it. You can enable it at
multiple levels. The seing at the highest enabled level takes precedence over the lower levels. User level is the highest
in the hierarchy and always takes precedence over the seings at the site level.
On the Manage Administrative Prole Values page, set the prole value at any of the enabled levels of the prole option.
For this example, there are two users, John and Lisa. For John, the user-level prole value currency is set to US Dollar. If
the Currency prole option is enabled only at the site level, both John and Lisa would see Euro as the default currency. If
the prole option is enabled at the user level, users having a dierent currency set as their currency prole value would
see only that currency. In this case, John would see US Dollar as the default currency. If the Currency prole option is
enabled at the user level and there is no user level currency dened, the site level seing takes eect. When both site
and user levels are enabled, the value for the user level takes precedence over the site level value.
◦ Prole Level: Specify the level at which the prole value is to be set. If the prole value applies to the
entire site, select Site.
◦ Product Name: If you select Product as the prole level, select a product and specify the associated
prole value.
◦ User Name: If you select User as the prole level, select the user name and specify the associated prole
value.
◦ Prole Value: Select or enter the value corresponding to the selected prole level.
Note: For an existing entry, you can modify only the prole value.
4. Repeat step 3 to add more rows and set the prole values.
5. Click Save and Close.
360
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Note: Changes in the prole values take eect for a user on the next sign in.
Prerequisite
The le containing the prole values is available in the document repository of Oracle WebCenter Content.
Here's a sample le that contains the header values at the beginning of the le, followed by line entries of the two prole
values that are to be imported. For importing several prole values, add more line entries in a similar format.
361
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
ProfileOptionCode|LevelName|UserName|ProfileOptionValue
AFLOG_BUFFER_MODE|USER|APP_IMPL_CONSULTANT|TEST
AFLOG_LEVEL|USER|APPLICATION_DEVELOPER|FINEST
Related Topics
• Overview of Files for Import and Export
• Guidelines for File Import and Export
• Upload Files to WebCenter Content Server
As a result, on the Manage Administrator Prole Values page, the prole values Yes and No are
available for selection for that prole option.
◦ You can specify a date range to keep the prole option active during that period. Beyond the specied
duration, the prole option automatically becomes inactive. If you no longer require the prole option,
you must manually delete it from the Manage Prole Options page.
4. Click Save and Close.
5. On the Manage Prole Options page, search for the newly created prole option and from the results, select it.
6. In the Prole Option Levels section, do the following:
a. In Enabled, select the levels at which you want to enable the prole option.
Note: You can enable a prole option at multiple levels, but a higher-level prole value
overrides a lower-level value. Therefore, enable them only at the required levels.
b. In Updatable, select the prole level at which you want implementors to have update privileges. Leave
the check box deselected if you don't want the implementors to modify the prole values (they appear in
read-only mode).
7. Click Save and Close.
362
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
To edit a prole option that you created, search for it and edit the necessary details.
Note: While creating and editing prole options and prole categories, you can translate the details to the
preferred languages without changing the language session of the application. To specify the translations in
all the enabled language rows, use the Translation Editor option. Once the updates are made, users can view
the translated text for the specic details.
Related Topics
• Enter or Edit Translated Text
Tip: If you don't know the prole option code or the display name, use the Application or
Module elds to lter search results.
Prole Categories
You can create prole categories to group prole options based on their functional similarities and their use. In the
Setup and Maintenance work area, use the Manage Prole Categories task.
Prole categories help administrators or implementors in retrieving prole options using a search criterion on the
Manage Administrator Prole Values page.
Note: While you can add a prole option to more than one category, some prole categories are predened
and restricted from any modications. So, you can't edit them or add prole options to them.
363
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
The following table demonstrates the eect of the display sequence on the prole options when they're retrieved as
search results.
Prole Category Included Prole Option - Assigned Display Sequence of Prole Options in
Display Sequence the Search Results
Dene Flexelds
Overview of Flexelds
A exeld is a set of placeholder elds associated with business objects and placed on the application pages to
contain additional data. You can use exelds to modify the business objects and meet enterprise data management
requirements without changing the data model or performing any database programming. Flexelds help you to
capture dierent data on the same database table and provide a means to modify the applications features.
For example, an airline manufacturer may require specic aributes for its orders that aren't predened. Using a
exeld for the order business object, you can create and congure the required aribute.
Types of Flexelds
Flexelds that you see on the application pages are predened. However, you can congure the exelds or modify
their properties. Users see these exelds as eld or information aributes on the UI pages. To manage exelds, use
any of the following tasks in the Setup and Maintenance work area:
• Manage Descriptive Flexelds: Expand the forms on the application page to accommodate additional
information that is important and unique to your business. You can use a descriptive exeld to collect invoice
details on a page displaying invoices.
• Manage Extensible Flexelds: Establish one-to-many data relationships and make application data context-
sensitive. The exelds appear only when the contextual data conditions are fullled. Thus, extensible exelds
provide more exibility than the descriptive exelds.
• Manage Key Flexelds: Store information combining several values, such as a number combination. The key
exelds represent objects such as accounting codes and asset categories.
• Manage Value Sets: Use a group of values to validate the data entered in the exelds.
Note: You can manage value sets within the Manage Descriptive Flexelds or Manage Extensible
Flexelds tasks.
Related Topics
• Modules in Application Taxonomy
364
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Flexeld Components
A exeld is made up of several data entities that store and render information pertaining to exeld conguration.
Flexelds are made up of the following components:
• Segments
• Value Sets
• Contexts
• Structures
Segments
A segment is a eld within a exeld and represents a single table column of your database. When conguring a
exeld, dene the appearance and meaning of individual segments. Segments represent aributes of information.
Segments can appear globally wherever the exeld is implemented, or based on a structure or context. Each segment
captures a single atomic value and represents an aribute of information.
The characteristics of a segment vary based on the type of exeld in which it's used.
• In key exelds, a segment describes a characteristic of the entity. For example, a part number that contains
details about the type, color, and size of an item.
• In a descriptive or extensible exeld, a segment represents an information aribute on the application page.
For example, details about a device containing components, some of which are global while the remaining are
contextually dependent on the category of the device.
Value Sets
Users enter values into segments while using an application. A value set is a named group of values that validate the
content of a exeld segment. You congure a exeld segment with a value set to enforce entries of only valid values
for that segment.
Multiple segments within a exeld, or multiple exelds, can share a single value set.
Contexts
Context-sensitive exeld segments are available to an application based on a context value. You dene contexts as
part of conguring a exeld. Users see global segments as well as any context-sensitive segments that apply to the
selected context value.
In descriptive exelds and extensible exelds, you can reuse the context-sensitive segments that are based on the
database columns, in multiple contexts.
Structures
Key exelds have structures. Each key exeld structure is a specic conguration of segments. Adding or removing
segments, or rearranging their order, produces a dierent structure. You can reuse the segments that are based on the
database columns, in multiple structures.
365
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Note: You can translate all these exeld components to the preferred languages without changing the
language session of the application. To specify the translations in all the enabled language rows, use the
Translation Editor option on the respective edit pages. Once the updates are made, users can view the
translated text for the specic exeld components at runtime.
Related Topics
• Enter or Edit Translated Text
366
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
The following gure illustrates that the exeld denition consists of all the metadata dened during conguration and
stored in the database.
Oracle Fusion
Applications Database
Entity Table
Enabled for
Adding
Flexfield Flexfield Definition
Segments
Define Flexfields
Create Tasks for Configure
Define Flexfields Flexfield
flexfield. Application flexfield.
Tasks
Administrators
for Application
and
Developers
Implementation
Consultants
Flexfield Deployment
Attributes
on the entity display as
input fields in the user
interface.
Application developers create a exeld and register it so that it's available for conguration. Administrators and
implementation consultants congure segments and other properties of the available exelds. This information is
stored as additional exeld metadata in the database. Deploying the exeld generates ADF business components
based on the exeld metadata in the database.
The following aspects are important in understanding how exelds and Oracle Applications Cloud architecture work
together:
• Integration
• Deployment
367
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Integration
The aributes that you add by conguring exelds are available throughout the Oracle Fusion Middleware technology
stack. You can use the exeld segment's Application Programming Interface (API) to identify segments and integrate
the exelds in the following:
Deployment
The metadata for the exeld is stored in the application database as soon as you save your conguration changes.
Deploying the exeld generates the ADF business components so that the run time user interface reects the latest
exeld denition in the metadata.
Run Time
The latest denitions of a exeld reect on the user interface at run time only if the exeld is deployed. When the
user interface accesses a business object, the deployed exeld denition identies the aributes associated with the
captured values. On a page, if you add display congurations for a exeld using Oracle Composer, the same exeld
segments can appear dierently on dierent pages.
Patching
Flexeld congurations are preserved during patching and upgrading.
Flexeld Management
Considerations for Managing Flexelds
Managing exelds involves registering, planning, and conguring exelds.
You plan and congure the registered exelds provided in your applications by applications developers. How you
congure exeld segments determines how the exeld segments appear to users. Optionally, you can modify the UI
page to change how the exeld segments appear to users on that page.
368
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
The following gure shows the processes involved in making exelds available to users. The tasks in the Dene
Flexelds activity let administrators congure and deploy exelds. After you congure and deploy a exeld to a
sandbox, deploy it again to the mainline metadata so that it's available to the users.
Configure
flexfield
Flexfield-
Deploy to
enabled
sandbox
sandbox
Flexfield is
available to users
369
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Registering Flexelds
A exeld must be registered before it can be congured. Therefore, application development registers exelds so
that they are available to administrators and implementation consultants for conguration. The registration involves
reserving columns of entity tables for use in exelds. For more information about registering exelds, see Oracle
Fusion Applications Developer's Guide.
Planning Flexelds
Before you begin planning exelds, determine what type is appropriate to your needs, and which business objects are
available for modifying exelds. All exelds consist of segments which represent aributes of an entity. The value a
user enters for an aribute is stored in a column of the entity table. Carefully plan exelds before conguring them.
Before conguring new segments for your exelds, be sure to plan their implementation carefully.
If you have determined that a business object supports exelds, and those exelds have been registered, you can
begin planning their conguration. Note the code name of the exeld you intend to congure so that you can nd it
easily in the Dene Flexeld activity. In some cases you can determine and congure how the exeld appears on the
page. See Oracle Applications Cloud Help for specic products to determine any restrictions on using product-specic
exelds.
Conguring Flexelds
Administrators or implementors congure exelds so they meet the needs of the enterprise. Some exelds require
conguration to make an application operate correctly. You can congure exelds using the following methods:
• Use the manage exeld tasks in the Setup and Maintenance work area.
• Use the Highlight Flexelds command in the Administration menu while viewing a runtime page.
◦ Use the Congure Flexeld icon buon to manage all aspects of a exeld, such as change a segment's
sequence number or congure a exeld segment's business intelligence label.
◦ Use the Add Segment and Edit Segment icon buons to add and edit descriptive or extensible exeld
segments with simple congurations.
◦ Use the Add Context icon buon to add descriptive or extensible exeld context values.
Tip: You can create value sets while creating descriptive and extensible exeld segments. However, dene
value sets before conguring key exeld segments that use them, because you assign existing value sets
while conguring key exeld segments.
When creating table-validated, independent, dependent, or subset value sets while creating descriptive and extensible
exeld segments, you can optionally specify to display the description of the selected value next to the segment
at runtime. You can assign sequence order numbers to global segments and to context-sensitive segments in each
context. Segment display is always in a xed order based on the segments' sequence numbers. You cannot enter a
number for one segment that is already in use for a dierent segment. Therefore, you may consider numbering the
segments in multiples, such as 4, 5, or 10, to make it easy to insert new aributes.
370
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
A exeld column is assigned to a new segment automatically, but you can change the assignment before saving the
segment. If you must set a specic column assignment for a segment, create that segment rst to ensure that the
intended column isn't automatically assigned to a dierent segment.
Deploying Flexelds
Once you have congured a exeld, you must deploy it to make the latest denition available to runtime users. In the
Dene Flexelds tasks, you can deploy a exeld using either of the following commands:
• The Deploy Flexeld command deploys a exeld to the mainline metadata. This command is for general use
in a test or production environment.
• The Deploy to Sandbox command deploys a exeld to sandbox. This command is for conrming that the
exeld is correctly congured before deploying it to the mainline metadata.
Note: You can deploy your exeld changes to a sandbox only if you're using classic sandboxes. In unied
sandboxes, you can deploy your exeld changes directly to the mainline environment.
Once deployed, the deployment status indicates the state of the currently congured exeld relative to the last
deployed denition.
If the applications are running in dierent locales, you can provide dierent translations for translatable text, such as
prompts and descriptions. Enter translations using the locale that requires the translated text. In the global header,
click your user name and from the Seings and Actions menu, select Set Preferences. Then change the text to the
translated text for that locale.
371
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Even if a descriptive or extensible exeld isn't yet deployed and no segments appear on the runtime page in normal
view, the exeld appears in the Highlight Flexeld view for that page. For descriptive exelds, the segments as of the
last deployment appear. For extensible exelds, any segments and contexts that have been saved but not yet deployed
also appear as disabled.
Highlight Flexelds accesses the current exeld metadata denition. Use the highlighted exeld's Congure
Flexeld icon buon to manage exelds directly. Alternatively, note a highlighted exeld's name to search for it in
the tasks for managing exelds.
For more information about creating exelds and adding them to a UI page, see the Oracle Fusion Applications
Developer's Guide. For more information about modifying exeld segment appearance with Page Composer, see
guidance on modifying existing pages in the Oracle Applications Cloud Conguring and Extending Applications guide.
Display Properties
The following table summarizes display properties.
Property Description
Sequence The order the segment appears in relation to the other congured segments.
Prompt The string to be used for the segment's label in the user interface.
Selected and deselected values If the display type is check box, the actual values to save. For example, Y and N or 0 and 1.
Display height The height of the eld as measured in visible number of lines when the display type is a text
area.
372
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Property Description
Read only Whether the eld should display as read-only, not editable text.
Description help text The eld-level description help text to display for the eld. Use description help text to display
a eld-level description that expands on or claries the prompt provided for the eld.
If description help text is specied, a Help icon buon is displayed next to the eld in the run
time application. The description help text is displayed when the user hovers over the Help
icon buon.
Instruction help text The eld-level instruction help text to display for the eld.
Use instruction help text to provide directions on using the eld. If instruction help text is
specied, it's appears in an in-eld help note window when users move the cursor over the
eld.
You can congure as many range validated pairs as you want within the same exeld. Your application automatically
detects and applies range validation to the segment pairs that you dene, in sequence order. It must detect a low value
segment rst, and the next range validated segment that it detects must be a high value segment. These two segments
are assumed to be a matching pair. The low value and the high value can be equal.
373
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
values. If the context segment values are a superset or subset of the input values, you must assign a table-validated
value set or independent value set to validate context values.
You can also use Groovy validation to set additional restrictions or requirements for what values are allowed for certain
aributes of business objects. This is useful when you need to use the same value set to validate multiple segments, but
the exact validation requirement changes with each case. These validators can be dened at the global segment level,
or at the context level, based on your business needs. They have a validator code, validation expression, error message,
and description. After adding a new validator, click the Groovy Expression Builder icon to open the expression builder
window where you dene your validation expression. Groovy validation is done when a user tries to save their values to
an aribute that has a Groovy validator. If the value for this aribute fails validation against the Groovy expression, the
text dened in the Error Message column is displayed as an error message.
When you congure a descriptive exeld segment, you can specify a constant to use for seing the initial value. The
initial value can be an available parameter. For every planned segment, list the constant value or parameter, if any, to
use for the initial value.
Naming Conventions
Enter a unique code, name, and description for the segment. These properties are for internal use and not displayed to
end users. You can't change the code after the segment is created.
The Application Programming Interface (API) name is a name for the segment that isn't exposed to users. The API name
is used to identify the segment in various integration points including web services, rules, and business intelligence. Use
alphanumeric characters only with a leading character. For example, enter a code consisting of the characters A-Z, a-z,
0-9 with a non-numeric leading character. The use of spaces, underscores, multi-byte characters, and leading numeric
characters isn't permied. You can't change the API name after the segment has been created.
374
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
C CASCADE, CASE, CAST, CATCH, CATEGORY, CHAR, CHECK, CHILDREN, CLASS, CLONE,
CLOSE, CLUSTER, CLUSTERS, COALESCE, COLAUTH, COLUMN, COLUMNS, COMMENT,
COMMIT, COMPRESS, CONNECT, CONST, CONSTANT, CONSTRIANT, CONTAINS, CONTINUE,
COUNT, CRASH, CREATE, CURRENT, CURRENTROW, CURRVAL, CURSOR
E ELSE, ELSIF, EMPTY, ENABLED, ENABLEDSTRING, END, ENTRY, EQ, EQUALS, ERROR,
ESTIMATEDROWCOUNT, EXCEPTION, EXCLUSIVE, EXISTS, EXIT, EXTENDS
F FALSE, FETCH, FILE, FINAL, FINALIZE, FINALLY, FINDMODE, FLOAT, FOR, FORM, FROM,
FULLNAME, FUNCTION, FUTURE
J JAVA
K KEY
L LABEL, LABELS, LABELSET, LE, LEVEL, LIKE, LIMITED, LOCK, LONG, LOOP, LT
N NAME, NATIVE, NATURAL, NE, NEW, NEXTVAL, NOAUDIT, NOCOMPRESS, NOT, NOTFOUND,
NOTIFY, NOTIFYALL, NOWAIT, NULL, NULLIF, NUMBER
O OF, OFFLINE, ON, ONLINE, OPEN, OPERATIONENABLED, OPERATOR, OPTION, OR, ORDER,
ORDERBY, OTHERS, OUT, OUTER, OVERLAPS
375
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
T TABAUTH, TABLE, TABLES, TASK, TERMINATE, THEN, THIS, THROW, THROWS, TO,
TOOLTIP, TOSTRING, TRANSIENT, TRIGGER, TRUE, TRY, TYPE
V VALIDATE, VALUES, VAR, VARCHAR, VARCHAR2, VARIANCE, VIEW, VIEWS, VOID, VOLATILE
X XOR
The following aspects are important in understanding how exelds and value sets work together:
Note: Ensure that changes to a shared value set are compatible with all exeld segments that use the value
set.
376
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
You can also dene global segments that are shown for all value sets. However, this would be quite unusual since it
would mean that you want to capture that aribute for all values for all value sets.
Deployment
When you deploy a exeld, the value sets assigned to the segments of the exeld provide users with the valid values
for the aributes represented by the segments.
If your segment's default type is Groovy, you can set the Groovy expression you need using the expression builder. To
open the expression builder, select Groovy Expression as your Default Type and click the Groovy Expression Builder
icon. But you should know that Groovy defaulting doesn't support derivation when a dependent parameter changes.
The expression is evaluated only at segment creation.
The following table maps these dierent combinations. Initial runtime action corresponds to the row for the aribute
value being created in the entity table. If the default value is read only, it can't subsequently be changed through the
user interface. If the default value isn't read only, users can modify it. However, if the segment value is a derived value, a
user-modied segment value is overwrien when the derivation value changes.
Default Type Default value Derivation value Initial runtime action Runtime action after
specied? specied? parameter changes
377
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Default Type Default value Derivation value Initial runtime action Runtime action after
specied? specied? parameter changes
Parameter Yes Yes, and dierent from The default The changed
default value segment value is the parameter default
parameter's default value doesn't update
value segment value. Only
the changed derivation
value updates the
segment value.
Flexeld Usages
The exeld usage species the table with which the exeld and its segments are associated. A exeld can have
multiple usages. However, the rst table registered for a exeld indicates the master usage. Segments are based
on the master usage. Other usages of the same table for the same exeld use the same segment setup, though the
column names may have a dierentiating prex.
On the Manage Descriptive Flexelds and Manage Extensible Flexelds pages, click the Show Entity Usages icon for
a specic exeld to view its entity usage. On the Manage Value Sets page, you can view the exeld usages for a
selected value set.
Extensible Flexelds
For extensible exeld contexts, you can congure a dierent usage. The use of an extensible exeld context
determines the scenarios or user interfaces in which the segments of a context appear to users. For example, the
378
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Supplier page displays an extensible exeld's supplier usage and the Buyer page for the same exeld displays the
buyer usage. Then, a context that is associated only with the supplier usage appears only on the Supplier page and not
on the Buyer page.
Value Sets
The use of value sets species the exelds having segments where the identied value set is assigned.
Flexeld Deployment
Overview of Flexeld Deployment
Deployment generates or refreshes the Application Development Framework (ADF) business component objects
that render the exeld in a user interface. The deployment process adds user-dened aributes to the Web Services
Description Language (WSDL) schemas exposed by Oracle ADF services and used by SOA composites. Flexelds are
deployed for the rst time during the application provisioning process. After you congure or change a exeld, you
must deploy it to make the latest denition available to users.
If a descriptive exeld is enabled for business intelligence, the deployment process redeploys the exeld's business
intelligence artifacts.
You can deploy a exeld to a sandbox for testing or to the mainline metadata for use in a test or production run time
environment. You can deploy extensible exelds as a background process.
After deployment, the user-dened aributes are available for incorporating into the SOA infrastructure, such as
business process and business rule integration. For example, you can now write business rules that depend on the user-
dened aributes. You must sign out and sign back in to Oracle Applications Cloud to see the changes you deployed at
run time.
Deployment Status
Every exeld has a deployment status. Check the deployment status of your exeld after patching. The following
table lists the dierent deployment statuses a exeld can have.
Edited The exeld metadata denition hasn't been deployed yet. Updates of the metadata denition
aren't applied in the run time environment yet.
Patched The exeld metadata denition has been modied through a patch or a data migration
action, but the exeld hasn't yet been deployed. So, the updated denition isn't reected in
the run time environment.
379
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Deployed to Sandbox The current metadata for the exeld is deployed in ADF artifacts and available as a exeld-
enabled sandbox. The status of the sandbox is managed by the Manage Sandboxes dialog box
available in the Seings and Actions menu.
Deployed The current metadata for the exeld is deployed in ADF artifacts and available to users. No
changes have been made to the exeld after being deployed to the mainline metadata.
Note: Whenever a value set denition changes, the deployment status of a exeld that uses that value
set changes to edited. If the change results from a patch, the deployment status of the exeld changes to
patched.
Metadata Validation
Use the Validate Metadata command to view possible metadata errors before aempting to deploy the exeld.
Metadata validation is the initial phase of all exeld deployment commands. By successfully validating metadata
before running the deployment commands, you can avoid failures in the metadata validation phase of a deployment
aempt. The deployment process ends if an error occurs during the metadata validation phase. Metadata validation
results don't aect the deployment status of a exeld.
Metadata Synchronization
When an extensible or descriptive exeld is deployed, the deployment process regenerates the XML schema denition
(XSD). As a result, the user-dened aributes are available to web services and the SOA infrastructure.
After deploying a exeld conguration, you must synchronize the updated XML schema denition (XSD) les in the
MDS repositories for each SOA application.
Note: To synchronize the updated XSD les in the MDS repositories in Oracle Cloud implementations, log a
service request using My Oracle Support at hps://support.com/
380
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
background deployment process. A exeld's oine status is cleared and its deployment status updated when the
background deployment process has completed.
Note: When an application is provisioned, the provisioning framework aempts to deploy all exelds in that
application.
If you deploy the exeld to a sandbox successfully, the status is Deployed to Sandbox. The latest exeld metadata
denition in the application matches with the metadata denition that generated ADF business components in a
sandbox MDS Repository. Whether the sandbox is active or not doesn't aect the deployment status. If the exeld was
deployed to a sandbox and hasn't been edited or redeployed to the mainline metadata since then, the status remains
Deployed to Sandbox independent of whether the sandbox is active, or who is viewing the status.
If you deploy the exeld successfully to the mainline metadata, the status is Deployed. The latest exeld metadata
denition in the application matches the metadata denition that generated ADF business components in a mainline
MDS Repository. Change notications are sent when a exeld is deployed successfully to the mainline metadata.
If either type of deployment fails and that the current exeld denition isn't deployed, the status is Error. The
deployment error message gives details about the error. The latest exeld metadata denition in the application likely
diverges from the latest successfully deployed exeld denition.
If the exeld denition has been modied by a patch, the status is Patched. The latest exeld metadata denition in
the application diverges from the latest deployed exeld denition. If the exeld denition was Deployed before the
patch and then a patch was applied, the status changes to Patched. If the exeld denition was Edited before the patch
and then a patch was applied, the status remains at Edited to reect that there are still changes (outside of the patch)
that aren't yet in eect.
381
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
When a deployment aempt fails, you can access the Deployment Error Message for details.
The following gure shows the two types of deployment available in the Manage Flexeld tasks of the Dene Flexelds
activity. Deploying a exeld to a sandbox creates a sandbox MDS Repository for the sole purpose of testing exeld
behavior. The sandbox is only accessible to the administrator who activates and accesses it, not to users generally.
Deploying a exeld to the mainline metadata applies the exeld denition to the mainline MDS Repository where
it is available to end users. After deploying the exeld to the mainline metadata, modify the page where the exeld
382
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
segments appear. Modications done to the page in the sandbox MDS Repository cannot be published to the mainline
MDS Repository.
Access
Deploy flexfield to
sandbox to
sandbox.
test flexfield.
Flexfield
Metadata in Yes
Flexfield Business
Oracle Fusion
Components in Metadata
Applications
Services (MDS) Flexfield-
Database
Test in sandbox? Repository Sandbox enabled
Sandbox
Define
Flexfields
MDS
Modifications?
Caution: Don't modify exeld segment display properties using Page Composer in a exeld-enabled
sandbox as these changes will be lost when deploying the exeld to the mainline metadata.
383
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Related Topics
• How You Manage Congurations in Classic Sandboxes
You can deploy your exeld changes to a sandbox only if you're using classic sandboxes. In unied sandboxes, you
can deploy your exeld changes directly to the mainline environment.
When you deploy a exeld sandbox, the process generates the name of the exeld sandbox, and that exeld
sandbox is set as your current active sandbox. When you again sign in to the application, you can see the updated
exeld congurations. The Oracle Applications Cloud global header displays your current session sandbox.
Note: Unlike a standalone sandbox created using the Manage Sandboxes dialog box, the sandbox deployed
for a exeld contains only the single exeld. You can manage exeld sandboxes, such as seing an
existing exeld sandbox as active or deleting it, using the Manage Sandboxes dialog box.
When you deploy a exeld to the mainline metadata after having deployed it to the sandbox, the sandbox-enabled
exeld is automatically deleted.
You also can use the Manage Sandboxes dialog box in the Administrator menu of the Setup and Maintenance work area
to activate and access a exeld-enabled sandbox.
Note: Whether you use the Dene Flexelds or Manage Sandboxes task ows to access a exeld-enabled
sandbox, you must sign out and sign back in before you can see the changes you deployed in the runtime.
You cannot publish the exeld from the sandbox to the mainline metadata. You must use the Dene Flexelds task
ow pages to deploy the exeld for access by users of the mainline metadata because the exeld conguration in the
mainline metadata is the single source of truth.
384
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Related Topics
• How You Manage Congurations in Classic Sandboxes
Value Sets
Overview of Value Sets
A value set is a group of valid values that you assign to a exeld segment to control the values that are stored for
business object aributes.
A user enters a value for an aribute of a business object while using the application. The exeld validates the value
against the set of valid values that you congured as a value set and assigned to the segment.
For example, you can dene a required format, such as a ve-digit number, or a list of valid values, such as green, red,
and blue.
Flexeld segments are usually validated, and typically each segment in a given exeld uses a dierent value set. You
can assign a single value set to more than one segment, and you can share value sets among dierent exelds.
Note: Ensure that changes to a shared value set are compatible with all exelds segments using the value
set.
Validation
The following types of validation are available for value sets:
• Format only, where users enter data instead of selecting values from a list
• Independent, a list of values consisting of valid values you specify
• Dependent, a list of values where a valid value derives from the independent value of another segment
• Subset, where the list of values is a subset of the values in an existing independent value set
• Table, where the values derive from a column in an application table and the list of values is limited by a
WHERE clause
385
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
A segment that uses a format only value set doesn't present a list of valid values to users. If required, you may add table
validated value sets to the list of available value sets available for conguration.
Note: For the Accounting Key Flexeld value sets, you must use independent validation only. If you use other
validations, you can't use the full chart of accounts functionality, such as data security, reporting, and account
hierarchy integration.
Security
Value set security only works in conjunction with usage within exeld segments. You can specify that data security be
applied to the values in exeld segments that use a value set. Based on the roles provisioned to users, data security
policies determine which values of the exeld segment users can view or modify.
The application of value set security has the following conditions:
• At the value set level: The value set is the resource secured by data security policies. If a value set is secured,
every usage of it in any exeld is secured. Disabling security for individual usages of the same value set isn't
possible.
• Applies to independent, dependent, or table-validated value sets.
• Applies mainly when data is being created or updated, and to key exeld combinations tables for query
purposes. Value set security doesn't determine which descriptive exeld data is shown upon querying.
• Security conditions dened on value sets always use table aliases. When lters are used, table aliases are always
used by default. When predicates are dened for data security conditions, make sure that the predicates also
use table aliases.
For key exelds, the aributes in the view object corresponding to the account combination ID, structure instance
number (SIN), and data set number (DSN) can't be transient. They must exist in the database table. For key exelds,
the SIN segment is the discriminator aribute, and the account combination segment is the common aribute.
386
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
The following gure shows a value set used by a segment in a key exeld and the context segment of a descriptive
exeld.
For most value sets, when you enter values into a exeld segment, you can enter only values that already exist in the
value set assigned to that segment.
Global and context-sensitive segment require a value set. You can assign a value set to a descriptive exeld context
segment. If you specify only context values, not value sets for contexts, the set of valid values is equal to the set of
context values.
You can edit only value sets that are not marked as protected. You can't edit or delete protected value sets. If the value
set type supports values (such as independent, dependent or subset value sets), then you can't add, edit, or delete
values.
387
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Note: References to protected value sets aren't restricted. Value sets, protected or not, may be assigned
to any exeld segment. Likewise, other value sets may reference protected value sets; for example, an
unprotected dependent value set may reference a protected independent value set.
Related Topics
• Chart of Accounts Components
• Why can't I edit my exeld or value set conguration
388
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
For example, you could dene an independent value set of the states in the USA with values such as CA, NY, and so on.
Then you dene a dependent value set of cities in the USA with values such as San Francisco and Los Angeles that are
valid for the independent value CA. Similarly, New York City and Albany are valid for the independent value NY. In the
UI, only the valid cities can be selected for a given state.
Because you dene a subset value set from an existing independent value set, you must dene the independent value
set rst. Users don't have to select a value for another segment rst to have access to the subset value set.
Independent, dependent, and subset value sets require a user-dened list of valid values. Use the Manage Values page
to create and manage a value set's valid values and the order in which they appear.
Tip: You can congure the Manage Value Sets page to capture additional aributes for each valid value by
adding context-sensitive segments in a new context for FND_VS_VALUES_B descriptive eld.
Table Validation
Typically, you use a table-validated set when the values you want to use are already maintained in an application table,
such as a table of supplier names. Specify the table column that contains the valid value. You can optionally specify the
description and ID columns, a WHERE clause to limit the values to use for your set, and an ORDER BY clause.
If you specify an ID column, then the exeld saves the ID value, instead of the value from the value column, in the
associated exeld segment. If the underlying table supports translations, you can enable the display of translated
text by basing the value set's value column on a translated aribute of the underlying table. You should also dene
an ID column that's based on an aribute that isn't language-dependent so that the value's invariant ID (an ID that
doesn't change) is saved in the transaction table. The run time displays the corresponding translated text from the value
column for the run time session's locale.
Table validation lets you enable a segment to depend on multiple prior segments in the same context structure. You
can't reference other exeld segments in the table-validated value set's WHERE clause. Which means, the WHERE
clause can't reference SEGMENT.segment_code or VALUESET.value_set_code.
Table-validated value sets have unique values across the table, irrespective of bind variables. The WHERE clause
fragment of the value set is considered if it doesn't have bind variables. If it has bind variables, the assumption is that
the values are unique in the value set. If you use table validated value sets for key exelds, then you can't use all
integration options supported for key exelds, such as:
• Data security
• Oracle Transactional Business Intelligence (OTBI)
• Extended Spread Sheet Database (ESSbase)
• Tree or hierarchy integration
To use these integration options for key exelds, you must use independent value sets only.
Range
In the case of format, independent, or dependent value sets, you can specify a range to limit which values are valid. You
can specify a range of values that are valid within a value set. You can also specify a range validated pair of segments
where one segment represents the low end of the range and another segment represents the high end of the range.
For example, you might specify a range for a format-only value set with format type Number where the user can enter
only values between 0 and 100.
Security
In the case of independent and dependent values, you can specify that data security be applied to the values in
segments that use a value set. Based on the roles provisioned to users, data security policies determine which values of
the exeld segment users can view or modify.
389
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
To enable security on a value set, specify a database resource, typically the code value for the value set. Using the
Manage Database Security Policies task, specify conditions, such as lters or SQL predicates, and policies that associate
roles with conditions. You can use a lter for simple conditions. For more complex conditions, use a SQL predicate.
Value set data security policies and conditions dier from data security conditions and policies for business objects in
the following ways:
• You can grant only read access to users. You can't specify any other action.
• When dening a condition that's based on a SQL predicate, use VALUE, VALUE_NUMBER, VALUE_DATE,
VALUE_TIMESTAMP, or VALUE_ID to reference the value from a dependent, independent, or subset value set.
For table value sets, use a table alias to dene the table, such as &TABLE_ALIAS category=70.
When you enable security on table-validated value sets, the security rule that's dened is absolute and not contingent
upon the bind variables (if any) that may be used by the WHERE clause of the value set. For example, suppose a table-
validated value set has a bind variable to further lter the value list to x, y and z from a list of x, y, z, xx, yy, zz. The data
security rule or lter wrien against the value set must not assume anything about the bind variables. Instead the whole
list of values must be available and you write the rule, for example, to permit x, or to permit y and z. By default in data
security, all values are denied and show only rows to which access has been provided.
When you change an existing value set, the deployment status for all aected exelds changes to Edited. You must
redeploy all exelds that use that value set to make the exelds reect the changes. In the UI pages for managing
value sets, the value set's usages show which exelds are aected by the value set changes.
If your application has more than one language installed, or there is any possibility that you might install one or
more additional languages for your application in the future, select Translatable. This doesn't require you to provide
translated values now, but you can't change this option if you decide to provide them later.
Related Topics
• Considerations for Bind Variables in Table-Validated Value Sets
• Add Aributes to the Manage Value Sets Page
Prerequisite
Ensure that the web service FndManageImportExportFilesService is added to the Manage Application Flexeld Value Set
entitlement. Use the Security Console to perform this conguration on Oracle Entitlements Server. While conguring
the web service, provide the following details:
• Resource type: WebserviceResourceType
• Display name: ImportExport
• Name: hp://xmlns.oracle.com/oracle/apps/fnd/applcore/webservices/
FndManageImportExportFilesService#*
• Entitlement (In Default Policy Domain): Manage Application Flexeld Value Set
390
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
5. Run the following command to generate the JAX-WS proxy for the FndManageImportExportFilesService web
service.
C:\Program Files\Java\jdk1.7.0_04\bin>wsimport
-s "d:\wsimport\FndManageImportExport"
-d "d:\wsimport\FndManageImportExport" http://<host>:<port>/fndAppCoreServices/
FndManageImportExportFilesService?wsdl
parsing WSDL...
Generating code...
Compiling code...
import com.sun.xml.ws.developer.WSBindingProvider;
import java.io.File;
import java.io.IOException;
import java.util.List;
import java.util.Map;
import javax.xml.ws.BindingProvider;
import javax.xml.ws.WebServiceRef;
import javax.xml.ws.handler.Handler;
import oracle.webservices.ClientConstants;
391
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
import weblogic.wsee.jws.jaxws.owsm.SecurityPoliciesFeature;
// !THE CHANGES MADE TO THIS FILE WILL BE DESTROYED IF REGENERATED!
// This source file is generated by Oracle tools
// Contents may be subject to change
// For reporting problems, use the following
// Version = Oracle WebServices (11.1.1.0.0, build 130224.1947.04102)
requestContext.put(ClientConstants.WSSEC_KEYSTORE_TYPE,"jks");
// Provide location of 'mycompclient-keystore.jks' which was created during Step I)
requestContext.put(ClientConstants.WSSEC_KEYSTORE_LOCATION,"/home/user1/mycompclient-keystore.jks");
requestContext.put(ClientConstants.WSSEC_KEYSTORE_PASSWORD,"<password>");
requestContext.put(ClientConstants.WSSEC_RECIPIENT_KEY_ALIAS,"cdrmkey");
String id = invokeUploadFiletoUCMMethod(fndManageImportExportFilesService);
if (id != null) {
invokevalueSetValuesDataLoader(fndManageImportExportFilesService, new Long(id));
}
}
392
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
try {
// Provide location of 'VS.txt' which contains ValueSet values data in prescribed format
byte[] content =
org.apache.commons.io.FileUtils.readFileToByteArray(new File("/home/user1/VS.txt"));
} catch (IOException e) {
System.out.println(e.getMessage());
}
catch(Exception e) {
System.out.println("Exception: "+e.getMessage());
}
try {
response = fndManageImportExportFilesService.uploadFiletoUCM(document);
System.out.println("Response: " + response);
} catch (ServiceException e) {
System.out.println(e.getMessage());
}
return response;
}
Related Topics
• Import Value Set Values
393
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Descriptive Flexelds
Overview of Descriptive Flexelds
Use descriptive exelds to add aributes to business object entities, and dene validation for them.
All the business object entities that you can use in the application are enabled for descriptive exelds. However,
conguring descriptive exelds is an optional task.
Context
A descriptive exeld can have only one context segment to provide context sensitivity. The same underlying database
column can be used by dierent segments in dierent contexts.
For example, you can dene a Dimensions context that uses the following aributes:
You can also dene a Measurements context that uses the same columns for other aributes:
394
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
The following gure displays a descriptive exeld having one context segment called Category for which there are
three values: Resistor, Baery, and Capacitor. Additionally, the descriptive exeld comprises two global segments that
appear in each context, and three context-sensitive segments that only appear in the specic context.
Context-
Context Global sensitive
segment segments segments
Attributes: Category G1 G2 A3 A4 A5
Context: Context:
Resistor Capacitor
Context:
Battery
G1 G1
G2 G2
A3 A4
A4 A5
G1
G2
A3
A4
A5
Application development determines the number of segments available for conguring. During implementation,
congure the exeld by determining the following:
Value Sets
For each global and context-sensitive segment, you congure the values permied for the segment. Based on it, the
values that end users enter are validated, including interdependent validation among the segments.
395
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Segments
You can assign sequence order numbers to global segments and to context-sensitive segments in each context.
Segment display is always in a xed order. You can't enter a number for a segment if that number is already in use for a
dierent segment.
Value sets are optional for context segments and follow specic guidelines:
• The value set that you specify for a context segment consists of a set of context codes.
• Each context code corresponds to a context that's appropriate for the descriptive exeld.
• The value set must be independent or table-validated.
• If table-validated, the WHERE clause must not use the VALUESET.value_set_code or SEGMENT.segment_code
bind variables.
• The value set must be of data type Character with the maximum length of values being stored no larger than
the context's column length.
• If you don't specify a value set for a context segment, the valid values for that context segment are derived
from the context codes. The denition of each context segment species the set of context-sensitive segments
that can be presented when that context code is selected by the end user.
• For reasons of data integrity, you can't delete an existing context. Instead, you can disable the associated
context value in its own value set by seing its end date to a date in the past.
• You can congure the individual global segments and context-sensitive segments in a descriptive exeld.
These segment types are dierentiated by their usage, but they're congured on application pages that use
most of the same properties.
396
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Tip: After you add a context value, refresh the page to see the new value.
Usages
Descriptive exeld usages allow for the same denition to be applied to multiple entities or application tables, such as
a USER table and a USER_HISTORY table. Descriptive exeld tables dene the placeholder entity where the exeld
segment values are stored once you have congured the descriptive exeld. When you congure a exeld, the
conguration applies to all its usages.
Parameters
Some descriptive exelds provide parameters, which are aributes of the same or related entity objects. Parameters
are public arguments to a descriptive exeld. Parameters provide outside values in descriptive exeld validation.
You use parameters to set the initial value or derivation value of an aribute from external reference data, such as a
column value or a session variable, rather than from user input. Parameters can be referenced by the logic that derives
the default segment value, and by table-validated value set WHERE clauses.
397
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Delimiters
A segment delimiter or separator visually separates segment values when the exeld is displayed as a string of
concatenated segments.
Initial Values
The SQL statement dening an initial value must be a valid statement that returns only one row and a value of the
correct type.
You can use two types of SQL statements:
• SQL statement with no binding. For example, select MIN(SALARY) from EMPLOYEES.
• SQL statement with bind variables. You can use these bind variables in the WHERE clause of the SQL
statement.
◦ :{SEGMENT.<segment_code>}: Identies a segment in the same context.
◦ :{PARAMETER.<parameter_code>}: Identies a parameter.
◦ :{CONTEXT.<context_code>;SEGMENT.<segment_code>}: Identies a segment in a dierent context. The
context must be in the same category or in an ancestor category, and it can't be a multiple-row context.
◦ :{VALUESET.<value_set_code>}: Identies the closest prior segment in the same context that's assigned to
the specied value set.
◦ :{FLEXFIELD.<internal_code>}: Identies a exeld.
Business Intelligence
Selecting a global, context, or context-sensitive segment's BI Enabled check box species that the segment is available
for use in Oracle Business Intelligence.
When the exeld is imported into Oracle Business Intelligence, the label you selected from the BI Label drop-down list
equalizes the segment with segments in other contexts, and maps the segment to the logical object represented by the
label.
Related Topics
• Why can't I edit my exeld or value set conguration
After you deploy a business intelligence-enabled exeld, use the Import Oracle Fusion Data Extensions for
Transactional Business Intelligence process to import the exeld changes into the Oracle Business Intelligence
repository. Users can make use of the newly-generated aributes in business intelligence applications. For example, a
user can generate a report that includes aributes added by the descriptive exeld. For additional information about
logical objects and import, refer to the Oracle Transactional Business Intelligence Administrator's Guide.
398
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Flaening
When you deploy a business intelligence-enabled descriptive exeld, the deployment process generates an additional
set of aened Application Development Framework (ADF) business components in addition to the usual ADF
business components and ADF faces run time artifacts that are generated during deployment. The aened business
components include aributes for business intelligence-enabled segments only. Flaening means each user-dened
column in each context shows up as an aribute in an Oracle Business Intelligence folder.
Flaened components include one aribute for the BI-enabled context-segment, and one aribute for each business
intelligence-enabled global segment. For BI-enabled context-sensitive segments, consider the following:
• If you assigned a label to the segment, the aened components include an additional single aribute
representing segments with that label.
• If you didn't assign a label, the aened components include a discrete aribute for each BI-enabled context-
sensitive segment in each context.
If you assign a label to any set of context-sensitive segments that serve the same purpose in dierent contexts, you
can consolidate or equalize the segments into a single aribute. This prevents duplication and the extra workload and
complexity that result from the aening process. For example, a United States context might have a Passport segment
and a Canada context might have Visa segment. If you assign the NationalID segment label to both the Passport and
Visa segments, they are equalized into the same NationalID aribute in the aened business component.
Non-labeled context-sensitive segments aren't equalized across context values, so the aened components include a
separate aribute for each context-sensitive segment for each context value. It may not be possible to equalize similarly
labeled segments if they have incompatible data types or value set types.
Assign a label to a global segment, context segment, or context-sensitive segment to map the corresponding aribute
in the aened components to a logical object in Oracle Business Intelligence. Using labels to map segments to BI
logical objects minimizes the steps for importing the exeld into Oracle Business Intelligence.
Note: Assigning a label to a context-sensitive segment serves to equalize the aribute across contexts, as well
as map the equalized aribute to business intelligence.
Managing Labels
You may assign a predened label (if available) to segments or create new labels for assignment, as needed. Specify
a code, name, and description to identify each label. In the BI Object Name eld, enter the name of the logical object
in Oracle Business Intelligence to which the segment label should map during import. Specifying the BI logical object
minimizes the steps for importing the exeld into Oracle Business Intelligence and helps to equalize context-sensitive
segments across contexts.
If no labels are assigned to a BI-enabled segment, or the BI Object Name on the assigned label doesn't exist in business
intelligence, you must manually map the segment to the desired logical object when importing into Oracle Business
Intelligence.
In addition, context-sensitive segments without labels cannot be equalized across context values. The aened
components include a separate aribute for each non-labeled context-sensitive segment in each context.
399
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
propagate the exeld object changes. When you import the metadata into the Oracle Business Intelligence repository,
you must do so as the FUSION_APPS_BI_APPID user.
To import exeld changes into the Oracle Business Intelligence repository in Oracle Cloud implementations, run the
Import Oracle Fusion Data Extensions for Transactional Business Intelligence process. For additional information about
import, refer to the Oracle Transactional Business Intelligence Administrator's Guide.
Note: When you import a exeld into the Oracle Business Intelligence repository, you see both <name>_ and
<name>_c aributes for each segment, along with some other optional aributes. The <name> aribute contains
the value. The <name>_c aribute contains the code of the value set that the value comes from, and is used for
linking to the value dimension. You must import both aributes.
Extensible Flexelds
Overview of Extensible Flexelds
Extensible exelds are like descriptive exelds, with some additional features.
• You can add as many context-sensitive segments to the exeld as you need. You aren't restricted by the
number of columns predened and registered for the exeld.
• You can congure a one-to-many relationship between the entity and its extended aribute rows.
◦ A row of data can have multiple contexts associated with it.
◦ A row of data can have multiple occurrences of the same context.
• You can congure aributes in groups to form a context so that the aributes in the context always appear
together in the user interface.
• You can use existing hierarchical categories so that entities inherit the contexts that are congured for their
parents. Contexts are reusable throughout categories.
• Application development has registered some extensible exelds to support view and edit privileges. For such
exelds, you can specify view and edit privileges at the context level to control who sees the aributes and
who can change the aributes' values.
When you congure a context for multiple rows per entity, the segments are displayed as a table.
Unlike descriptive exelds, the extension columns corresponding to extensible exelds segments are part of
extension tables, separate from the base application table. Unlike descriptive exeld contexts, the set of aributes in
an extensible exeld context remains constant and doesn't dier by context value. An extensible exeld describes an
application entity, with the run time ability to expand the database that implementation consultants can use to dene
the data structure that appears in the application. Extensible exelds support one-to-many relationships between
the entity and the extended aribute rows. To get a list of predened extensible exelds, use the Manage Extensible
Flexelds task in the Setup and Maintenance work area.
400
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Usages
Similar to the descriptive exelds, you can dene multiple usages for an extensible exeld, which enables several
application tables to share the same exeld.
For example, a exeld for shipping options can be used by both a Supplier table and a Buyer table. In addition, you can
associate a context with one, some, or all of the exeld's usages. Thus, with the shipping information example, you can
associate a warehouse context with the Supplier usage, a delivery location context with the Buyer usage, and a ship-via
context with all usages.
Usages include security information for applying no security to user access or enforcing view and edit privileges. Some
product-specic extensible exelds have specialized usage elds beyond those for security.
Categories
You can congure multiple extensible exeld contexts and group the contexts into categories. All extensible exelds
have at least one category. For some extensible exelds, you can congure a hierarchy of categories. A child category
in the hierarchy can inherit contexts from its parent category.
You can dene categories for extensible exelds, and you can associate any combination of contexts with a given
category.
For example, the Electronics and Computers category hierarchy might include a Home Entertainment category, which
in turn might include an Audio category and a TV category, and so on. The Home Entertainment product might have
contexts that specify voltage, dimensions, inputs and outputs. Contexts are reusable within a given extensible exeld.
For example, the dimensions context could be assigned to any category that needs to include dimensional information.
Pages
Extensible exelds let you combine contexts into groups known as pages, which serve to connect the contexts so they
will always be presented together in the application user interface.
Each application page corresponds to one extensible exeld category, with a separate region of the page for each
associated context.
Security
When you congure a exeld, you set the privileges for a context at the usage level by selecting actions for the view
and edit privileges of a context usage.
When an end user performs a search, the user interface displays only the aribute values of the contexts for which the
user has view privileges. The user can perform a search using all aributes for all contexts, regardless of view privileges.
If end users access a context through a web service, an exception is thrown if they perform an action for which they
don't have privileges.
All extensible exelds have a base data security resource. Some data security resources for extensible exelds
are precongured with actions that you can use to specify access privileges. If no action is precongured, a security
administrator can create actions and policies to support access control on the extensible exeld aributes.
Some extensible exelds have a translatable option; these exelds also have a translation data security resource.
401
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
If an extensible exeld is partially protected, then you can't edit the protected portions of the exeld's conguration.
For example:
• If an extensible exeld context is protected, you can't edit its:
◦ Context details
◦ Context segments
◦ Context usages
• If an extensible exeld page is protected, you can't:
◦ Edit the page details or delete the page
◦ Edit the contexts associated with the page
Note:
• There is no restriction on page references to protected contexts. The pages you create may contain any
context, whether protected or not.
• There is a restriction on category references to protected contexts. If a context is protected, you can't add it
to or delete it from any category.
Related Topics
• Update Existing Setup Data
402
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
• Security
• Deployment
For contexts that store multiple rows, you can uniquely identify each row by having the values in each row form a
unique key.
If exeld has a category hierarchy, then you can leverage the hierarchy to reuse contexts for similar entities, such as
similar items in a product catalog.
Set the context to translatable so that free-form text entered by end users is stored in the language of the user's locale,
and dierent translations of that text can be stored in other languages. Segments in the translated contexts should use
format-only value sets for storing free-form, user-entered text.
Set the context security to give an end user view or edit access to a context. The context's task ow and region appear
in the user interface only for users with view access. With edit access, an end user can edit the context's aribute values.
With no action specied for a usage, no special privileges are enforced through the context's conguration.
Dene logical pages to group contexts together in the user interface. For a given category, you may create one or more
logical pages. You may add one or more of the category's associated contexts to each of the category's logical pages.
Categories
A category is a grouping of related data items that can be considered to belong together. You can associate any
combination of contexts with a given category. Extensible exelds with more than 30 categories must be deployed as a
background process.
A category hierarchy logically organizes a set of categories. For example, the Electronics and Computers category
hierarchy might include a Computer category and a Home Entertainment category, which in turn might include an
Audio category and a TV category, and so on.
A category can be a child or sibling of an existing category. The hierarchy can be as simple or as complex as desired,
with any combination of zero or more sibling categories and zero or more child categories. If no category is dened, the
data items are grouped in a single predened default category.
Each category has associated contexts that store relevant information about a data item in that category. For example, a
Home Entertainment product has contexts that specify Voltage, Dimensions, Inputs and Outputs. Contexts are reusable
within a given extensible exeld. Then, the Dimensions context could be assigned to any category that needs to
include dimensional information.
403
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
If a hierarchy includes child categories, each child category inherits the contexts from its parent category; for example,
the Home Entertainment category inherits Voltage and Dimensions from the Electronics and Computers category.
Each extensible exeld is associated with a particular category hierarchy. Consider category hierarchies to be dening
framework for extensible exelds and their contexts. A category hierarchy species which contexts are valid for each
category.
An extensible exeld can include multiple contexts which you dene to support a given category. These contexts can
be suitable for various purposes, but within a particular category, some contexts might be considered to be related to,
or dependent on, each other. You can combine these contexts into groups known as logical pages, and determine the
sequence in which the pages appear. This serves to connect the contexts so they will always be presented together and
in a particular order in the application user interface.
For example, the Home Entertainment category might have an Electrical Specications page that contains the Voltage,
Inputs and Outputs contexts, and a Physical Specications page that contains the Dimensions and Form Factor
contexts.
Initial Values
The SQL statement dening an initial value must be a valid statement that returns only one row and a value of the
correct type.
You can use two types of SQL statements:
• SQL statement with no binding. For example, select MIN(SALARY) from EMPLOYEES.
• SQL statement with bind variables. You can use these bind variables in the WHERE clause of the SQL
statement.
404
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Tip: After you add a context value, refresh the page to see the new value.
Indexed Segments
You can designate an extensible exeld segment as indexed so that it's one of the selectively required aributes a
user can use in an aribute search. If you indicate in the Manage Extensible Flexeld UI page that a segment should
be indexed, the column representing the segment must be added to the database index. Commonly, a database
administrator (DBA) adds columns to the database index.
When an extensible exeld with indexed segments is deployed, search task ows are generated along with the other
exeld artifacts and specify the indexed aributes as selectively required. In the deployed extensible exeld's search
task ow, an end user must specify at least one of the indexed aributes in the search criteria. This prevents non-
selective searches, which could cause performance issues.
For example, if you index the memory and processor aributes and ensure that the corresponding columns in the
database are indexed, a user can search an item catalog for computers by entering processor or memory or both as a
search criteria. No search is performed if an end user enters an aribute that isn't indexed as a search criterion.
Security
An extensible exeld's base data security resource typically has a name with an _B sux. The translation data security
resource is a view of a translation table that typically has a name with an _VL sux.
If a exeld supports the translatable option and has a translation data security resource, make sure that you create the
action for the appropriate data security resource.
• If you create a context-specic action for a nontranslatable context, add it to the base data security resource.
• If you create a context-specic action for a translatable context, add it to the translation data security resource.
405
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Deployment
You can only deploy extensible exelds using the Manage Extensible Flexelds task. You can deploy extensible
exelds oine as a background process and continue working in the session without having to wait for the
deployment to complete. You can queue up several extensible exelds and deploy as a background process. The
exelds are deployed, one at a time, in the order that you deploy them to the queue. You must deploy extensible
exelds with more than 30 categories as a background process.
You can remove an extensible exeld from the deployment queue with the Cancel Background Deployment command.
When an extensible exeld is deployed in a background process, its oine status indicates that the exeld is in a
background deployment process. A exeld's oine status is cleared and it's deployment status updated when the
background deployment process has completed.
Note: The Oine Status column refreshes when you perform a new search in the Manage Extensible
Flexelds task.
Related Topics
• Why can't I edit my exeld or value set conguration
Key Flexelds
Overview of Key Flexelds
Key exelds provide a means to capture a key such as a part number, a job code, or an account code. A key exeld
consists of one or more segments, where each segment can have a meaning.
For example, a part number 10-PEN-BLA-450 might correspond to a black pen from supplier #450 sold by division #10
(oce supplies). Behind the scenes, the application uses a unique number, 13452, for this part, but the user always sees
the 10-PEN-BLA-450 part number.
Key exelds aren't optional. You must congure key exelds to ensure that your applications operate correctly. You
congure and maintain key exeld denitions with the Manage Key Flexelds task. To get a list of predened key
exelds, use the Manage Key Flexelds task in the Setup and Maintenance work area. For information about specic
key exelds, see the help for the product where the associated business component is implemented.
Architecture
Flexeld metadata is stored in the exeld metadata tables. When you congure a key exeld, you dene metadata
about the key exeld covering aspects such as:
• Segments are in a structure
• Structures in the exeld
406
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Based on the exeld metadata, actual part numbers are captured at run time as a combination of segment values
and stored in a combinations table. A combinations table contains all the segment columns for a exeld, a unique
ID column, and a structure instance number column. The structure instance number column dierentiates multiple
arrangements of the segment columns. For example, a part number containing multiple segments can be represented
by a key exeld. A part number key exeld has a corresponding combinations table. In that table, the exeld stores a
list of the complete codes, with each segment of the code in a column, with the corresponding unique ID and structure
instance number for the code. When users dene a new part number or maintain existing part numbers in the parts
catalog, they directly maintain rows in the combinations table.
The foreign key table contains a dierent business entity than the combinations table. For example, the business entity
in the foreign key table is order lines or invoice lines that contain foreign key references to parts for ordering. Any
number of foreign key tables can reference a particular entity represented by a key exeld.
Applications identify a particular segment for some purpose such as security or computations. Segment name or
segment order cannot reliably identify a segment because key exeld segments can be congured to appear in any
order with any prompts. A segment label functions as a tag for a segment.
For example, the requirement is to identify which segment in the accounting exeld contains balancing information
and which segment contains natural account information. A segment label determines which segment you are using for
natural account information. When you dene your accounting exeld, you must specify which segment labels apply
to which segments. Some labels must be unique, and cannot be applied to more than one segment in each structure.
Other labels are required, and must be applied to at least one segment in each structure.
A segment label helps a user searching for segments, such as the Cost Center label for all segments across key exelds
that store a value for the cost center.
Structures
A key exeld structure denition includes the number of segments and their order.
In some applications, dierent users like to see dierent segment structures for the same exeld. A key exeld can
have multiple structures if registered to support more than one structure.
The exeld can display dierent elds for dierent users based on a data condition in your application data, such
as the value of another eld entered by the user or the user's role. For example, the correctly formaed local postal
address for customer service inquiries diers based on locale. A postal address key exeld could display dierent
segments and prompts for dierent users based on a location condition in your application data, such as the user's role
or a value entered by the user.
407
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Each structure can have one or more segments. Thus a segment is a child of a structure. To store a particular segment,
such as Cost Center, in two dierent structures, you must dene the segment separately in each structure. Each
structure may have one or more structure instances. Each instance of a structure shares the same number and order of
segments, but diers in the values or value sets used in validating the segments.
The segments in a key exeld structure instance are segment instances. A segment instance is a segment with a
specic value set assigned to it. If a key exeld is registered with a tree structure, you can specify a tree code for a
segment instance.
Combinations
A combination is a complete code, or combination of segment values that makes up the code, that uniquely identies
an object.
For example, each part number is a single combination, such as PAD-YEL-11x14 or 01-COM-876-7BG-LTN. In these
combinations, the hyphen is the segment separator. If you have ten parts, dene ten combinations. A valid combination
is an existing or new combination that can be used because it's currently active and doesn't violate cross-validation
or security rules. A combination has dierent segments depending on the exeld structure being used for that
combination. Any combination is associated with only one particular exeld structure.
Many applications refer to a key exeld combination by using the name of the entity or the key exeld itself. For
example, Assets uses the asset key exeld and refers to one of its combinations as an asset key or asset key exeld.
In another example, Oracle Fusion General Ledger refers to combinations of the accounting exeld as account or GL
account.
Each key exeld has one corresponding table, known as the combinations table, where the exeld stores a list of the
complete codes, with one column for each segment of the code, together with the corresponding unique ID number (an
account combination ID) for that code. Then, other tables in the application have a column that stores just the unique
ID for the code. For example, you may have a part number code, such as PAD-YEL-11x14. The Parts combinations table
stores that code along with its ID, 57494. If your application lets you take orders for parts, you might then have an
Orders table that stores orders for parts. That Orders table would contain a single column that contains the part ID,
57494, instead of several columns for the complete code PAD-YEL-11x14. Typically, one combinations page maintains
the key exeld, where the key exeld is the representation of an entity in your application. Maintain individual
combinations, such as part numbers in the combinations page.
408
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
If your key exeld or certain usages or references of the key exeld don't permit dynamic combination creation,
you may control whether dynamic combination creation is enabled for each structure instance. If enabled, a user can
enter a new combination of segment values using the exeld window from a foreign key page. For example, when
entering a transaction, a GL user can enter a new expense account combination for an account that doesn't yet exist.
Your application creates the new account by inserting the new combination into the combinations table behind the
scenes. Assuming that the new combination satises any existing cross-validation rules, the exeld inserts the new
combination into the combinations table, even though the combinations table isn't the underlying table for the foreign
key page.
Related Topics
• Update Existing Setup Data
Planning
Plan structures carefully and enable them for future needs. Don't change the number, order, and maximum length of
segments once you have acquired exeld data.
Structure Delimiters
A delimiter separates the segments when they appear to users. The delimiter value of a structure species the character
used to visually separate segment values when the key exeld is displayed as a string of concatenated segments in the
UI.
Identify the delimiter value of your key exeld carefully so that it doesn't conict with the exeld data. For example,
if your data frequently contains periods, such as in monetary or numeric values, don't use a period as your segment
separator. Any character you expect to appear frequently in your segment values or descriptions isn't a good choice for
the delimiter. If you change the conguration of a key exeld, such as the delimiter, the change aects the previously
stored key exelds with that structure.
Security
Oracle Fusion data security enforces value set security.
Within key exelds, value set security applies to the selection of the individual segment values in the segment list of
values. When selecting a key exeld segment value from the combinations table, data security permits display of only
the combinations whose segment values you have access to. Applications development controls whether or not value
set security rules propagate to the foreign key table. By default they do.
409
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
• Combinations pages where the underlying entity objects use the combinations table itself
• Foreign key pages where the underlying entity objects contain a foreign key reference to the combinations
table
• Partial usage pages where some or all of the key exeld's segment columns are in a product table
The same key exeld can be used in dierent ways on dierent pages.
A page with a foreign key reference has a base table or view that contains a foreign key reference to a combinations
table with the actual exeld segment columns. This lets you manipulate rows containing account combination IDs
(account combination).
A page with partial usage of a key exeld presents segments that are dened on a product's transactional table in
addition to being dened on a combinations table. In the case of a partial usage page, only a part of the conguration is
likely to be visible. This enables the key exeld to act more like a descriptive exeld.
An account combination maintenance page or combinations page presents the combinations table. This enables
directly creating and maintaining account combinations. The combinations table contains all key exeld segment
columns and a unique ID column.
A typical application has only one combinations page. An application might not have a combinations page if it doesn't
support maintenance by administrators.
A page containing a search region enables users to select which aributes of the key exeld view object to use as
criteria to search for exeld metadata.
For example, you can congure seven segments for the Account key exeld. In a foreign key reference page, users
see the typical key exeld picker with all seven segments where they can search for combinations. In a partial usage
page using the same key exeld, users potentially could see only a single segment such as the Cost Center labeled
segment, or they might see multiple segments but displayed as individual segments rather than options for selecting
combinations.
For more information about key exeld pages, see the Oracle Fusion Applications Developer's Guide.
410
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Enable segments to indicate that they are in use. A exeld doesn't display disabled segments in run time. To protect
the integrity of your data, disable a segment if you have already used it to enter data.
The dierences among structure instances include whether dynamic combination creation is permied. Likewise, at the
structure instance level, dierences among segment instances are based on the following:
• Value set
• Default type and default value
• Tree code
• Whether the segment is any of the following:
◦ Required
◦ Displayed
◦ Enabled for business intelligence
◦ Optional or required as a query criterion
For example, you can use one group of value sets for the US and another for France.
411
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
The following gure shows two structures instances for a part number structure.
Item Category
Type Item
Style
Part Number
Structure Instance A1 Color
Item Global Items
Part Number:
COM_512
Part Number Structure B Part Number Structure B
Structure Instance B1 Structure Instance B2
Segment Instances: Segment Instances:
APAC Value Sets US Value Sets
The structures dier in the number of segments and the segment separators used. The structure instances share all
the properties dened for that structure. However, the structure instances may vary if the properties are dened at the
structure instance or segment instance level. For example, the value set assigned to the segment instances.
412
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Following deployment, the combination picker of the key exeld displays the query required aributes as selectively
required. A user must specify at least one of the query required aributes in the search criteria. This prevents
unnecessary searches that could cause performance issues.
For example, you mark the cost center and account aributes as query required and ensure that the corresponding
columns in the database are indexed. A user can search for combinations by entering cost center or account or both as
search criteria. No search is performed if a user doesn't enter at least one query required aribute as search criteria.
Tip: Index the Structure Instance Number column on your combinations table to improve run time
performance.
Dynamic Combinations
If a key exeld supports dynamic combination creation, you can select to enable this feature by selecting Dynamic
Combination Creation Allowed. As a result, users enter values at run time that produce new account combinations
for the exeld. If Dynamic Combination Creation Allowed isn't enabled, new valid combinations can only be entered
using the combinations table for the exeld.
Trees
You may dene a tree code for the value set assigned to the segment instance. When you assign the tree code to the
segment instance, tree hierarchy search operations are available on the segment values.
For a segment instance to be based on a tree, the following must be true.
• Application development registered the key exeld with a tree structure. The tree structure may be xed
across all segments in the exeld, or may vary across segments.
• A tree code for that tree structure exists.
• The tree code includes tree versions containing the values of the value set assigned to the segment instance.
• You assign the required tree code directly to the segment instance.
If these conditions are satised, you can assign the same or dierent tree codes to the dierent segment instances that
use the same value set.
After you deploy a business intelligence-enabled exeld, use the Import Oracle Fusion Data Extensions for
Transactional Business Intelligence process to import the exeld changes into the Oracle Business Intelligence
repository. Users can make use of the newly-generated aributes in business intelligence applications. For additional
information about logical objects and import, refer to the Oracle Transactional Business Intelligence Administrator's
Guide.
413
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Flaening
When you deploy a business intelligence-enabled key exeld, the deployment process generates an additional set of
aened business components for use in business intelligence. The aened business components include aributes
for business intelligence-enabled segment instances only.
If you assigned a label to a segment, the aened components include a single aribute representing all segment
instances with that label. If you didn't assign a label, the aened components include a discrete aribute for each BI-
enabled segment instance in each structure.
Non-labeled segments aren't equalized across context values, so the aened components include a separate
aribute for each segment for each structure. It may not be possible to equalize similarly labeled segments if they have
incompatible data types or value set types.
Assign a label to a segment to map the corresponding aribute in the aened components to a logical object in Oracle
Business Intelligence. Using labels to map segments to BI logical objects minimizes the steps for importing the exeld
into Oracle Business Intelligence. Assigning a label to a segment serves to equalize the aribute across structures, as
well as map the equalized aribute to business intelligence.
Managing Labels
You may assign a predened label (if available) to segments or create labels for assignment, as needed. Specify a code,
name, and description to identify each label. In the BI Object Name eld, enter the name of the logical object in Oracle
Business Intelligence to which the segment label should map during import. Specifying the BI logical object minimizes
the steps for importing the exeld into Oracle Business Intelligence and helps to equalize context-sensitive segments
across structures.
If no labels are assigned to a BI-enabled segment, or the BI Object Name on the assigned label doesn't exist in business
intelligence, you must manually map the segment to the required logical object when importing into Oracle Business
Intelligence. In addition, segments without labels cannot be equalized across structures. The aened components
include a separate aribute for each non-labeled segment in each structure.
To import exeld changes into the Oracle Business Intelligence repository in Oracle Cloud implementations, run the
Import Oracle Fusion Data Extensions for Transactional Business Intelligence process. For additional information about
import, refer to the Oracle Transactional Business Intelligence Administrator's Guide.
414
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Note: When you import a exeld into the Oracle Business Intelligence repository, you see both <name>_ and
<name>_c aributes for each segment, along with some other optional aributes. The <name>_ aribute contains
the value. The <name>_c aribute contains the code of the value set that the value comes from, and is used for
linking to the value dimension. You must import both aributes.
Scenario
When entering details for each expense, the user species an account to which the expense is charged.
Analysis
The expense account eld is a foreign key reference to a account combination (EXPENSE_LINES.EXPENSE_ACCOUNT =
ACCOUNT.COMBINATION).
415
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
The following gure shows the origin in the account combinations table of the account specied by the user. The
account combination ID record stores the information of the key exeld segments used to assemble the expense
account based on the key exeld conguration.
Expenses Table
Expense Other Structure Code
Number Columns Instance Combination ID
1001 US 100345
1002 100565
Combination Details
Segment Value Description
The combinations page, which is the maintenance page for the key exeld, is for managing rows in the combinations
table. In this example, managing the combinations means adding or editing account numbers that adhere to the key
exeld metadata rules.
The following gure shows the account combination details for the example expense account reected in the exeld
conguration and the account combinations table.
416
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Combination Details
Segment Value Description
If dynamic combination creation isn't enabled, then when entering an expense line, the user can only select an account
that already exists in the ACCOUNTS (combinations) table. If they require an account that doesn't exist, they must
consult with the appropriate application administrator who can add the account to the combinations table.
If dynamic combination creation is enabled, then when entering an expense line, the user can either select a preexisting
account, or type in a new account that is created dynamically on the y in the ACCOUNTS (combinations) table. Once
the new combination is created, the same user can refer to it on the expense line.
When managing employee information, the user species the cost center that the employee belongs to. The cost center
eld corresponds to a single, labeled segment of the Account Key Flexeld and has metadata dened such as the
allowable value set for that segment.
In the following gure, instead of specifying a cost center ID reference to an account, only the cost center segment is
used and the value is stored directly on the employee table.
417
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Combination Details
Segment Value Description
Related Topics
• Example of One Chart of Accounts Structure with Many Instances
Tip: If you don't know the exeld name or the code, use the Module eld to lter search results.
Related Topics
• Update Existing Setup Data
418
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
For example, Western-region employees may choose only California, Nevada, Oregon, and so on as valid values. They
cannot select non-Western-region states. Eastern-region employees may choose only New York, New Jersey, Virginia,
and so on as valid values, but cannot select non-Eastern-region states. Value set security is implemented using Oracle
Applications Cloud data security.
For information about registering exelds, see the Oracle Fusion Applications Developer's Guide. Some business
objects aren't designed to support exelds. For information about how to enable business objects with exeld
capability, see Geing Started with Flexelds in the Oracle Fusion Applications Developer's Guide.
Note: Oracle CX Sales and Oracle B2B Service don't support exelds.
To add aributes to these applications, you may use Application Composer. For more information, see the product-
specic documentation.
You can set the default value to be a constant, if appropriate to the data type of the value set assigned to the segment.
In addition to an initial default value, you can set a derivation value for updating the aribute's value every time the
parameter value changes. The parameter you select identies the entity object source aribute. Any changes in the
value of the source aribute during run time are reected in the value of the segment.
If the display type of the segment is a check box, you can set whether the default value of the segment is checked or
unchecked.
Dene Aachments
419
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Aachments
You can use aachments to provide supplementary information to specic business objects. Aachments can be
URLs, desktop les, text, or repository folders. For a business object you may view, create, delete, or edit aachments,
depending on your role and granted privileges. For more information on aachments, see the Oracle Fusion
Applications Developer's Guide.
Repository
Aachments are stored in a content management repository provided by Oracle WebCenter Content Server. Users
managing aachments can't interact with the repository unless the repository mode is enabled. When enabled, users
can share aachments among objects, update aachments, and perform other tasks. Access to the aachment les is
controlled by a digital signing mechanism.
Security
Data security applicable to a specic business object also applies to its aachments For example, if a user has no access
to a specic expense report, then that user can't access its aachments. You can also use aachment categories to
control access and actions on aachments, based on roles associated with that category. For more information on
securing aachments, see the Oracle Fusion Applications Developer's Guide.
Aachment Entities
An aachment entity is usually a database entity, for example a table or view, that represents a business object with
which aachments can be associated. Each aachment UI must be dened with a corresponding aachment entity.
Aachment entities are used only in the context of aachments and exist separately from the database entities that
they're based on.
In the Setup and Maintenance work area, use the Manage Aachment Entities task to edit and create aachment
entities. You can either use the predened aachment entities with aachment UIs or create entities, for example when
developing your own UIs.
The entity name should match the name of the table or view that represents the business object used for aachment.
The name is also used in the repository folder that's automatically created to store aachments for the entity.
The data security policies associated with the database resource dened for the aachment entity apply to aachments
for that entity. However, the security seing must be enabled for that entity. The database resource value must match
the value in the OBJ_NAME column in the FND_OBJECTS table for the business object that the entity represents.
Related Topics
• Modules in Application Taxonomy
• How Database Resources and Data Security Policies Work Together
420
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
Aachment Entities and Manage Aachment Categories pages, any change in association on one page automatically
reects on the other page. You can open either page by starting in the Setup and Maintenance work area and searching
for the aachment tasks.
Managing Entities
On the Manage Aachment Entities page, you determine which aachment categories are relevant to a particular entity.
Each entity must have at least one category. For a particular expense report page with aachments functionality, you
can specify which category to use for the aachment. Accordingly, the data security dened for each category is applied
to the aachments on that page if security is enabled.
Managing Categories
If you create an aachment category and must assign it to multiple aachment entities, use the Manage Aachment
Categories page. The association is the same as that on the Manage Aachment Entities page.
Aachments Troubleshooting
Aachments UIs are very user-friendly and easy to work with. You may encounter issues in certain cases such as you
modify the aachments, for example create additional aachment categories, or implement data security on them.
Resolution
Use the Manage Aachment Entities page to ensure that aachment categories are associated to the relevant
aachment entity. You might need to check with your system administrator or help desk to determine the exact entity
used on the page with the expenses aachments or what categories to assign.
If data security is implemented on the categories for the aachment entity, verify that the Enable Security check box
is selected in the Manage Aachment Entities page for that entity. Also, make sure that users have a role that has the
necessary privileges. The following table lists the privileges required to view, add, update, or delete aachments with a
specic aachment category.
Action Privilege
Add or Update Update Application Aachment (FND_ UPDATE_ APPLICATION_ ATTACHMENT_ DATA)
421
Oracle Procurement Cloud Chapter 14
Implementing Procurement Applications Core Conguration
For example, if users have the Read Application Aachment privilege for all categories associated with the expense
report aachment entity, except the Receipts aachment category, then they can view all expense report aachments
except those created with the Receipts category. Likewise, if users don't have the Update Application Aachment
privilege for any aachment categories tied to the expense report aachment entity, then they can't create any
aachments for the expense reports.
For more information on aachment category data security, see the Oracle Fusion Applications Developer's Guide.
Certain aachments UI have predened restrictions for users on categories. Your developers can also introduce
additional lters to determine which document categories are available for a specic page. Check with your developers
or help desk.
Resolution
When the aachment was added, at least one category existed for the corresponding aachment entity. Since then, the
entity was edited so that it no longer has any assigned categories, so the user can't see the category associated with
that aachment.
Use the Manage Aachment Entities page to reassign aachment categories to the relevant aachment entity. For
example, if users can no longer see the Receipts aachment category for an aachment to an expense report, then
search for the expense report aachment entity and assign to it the Receipts category. You may need to check with your
system administrator or help desk to determine the exact entity used on the page with the expenses aachments or any
additional categories to assign.
Certain aachments UI have predened restrictions for users on categories. Your developers can also introduce
additional lters to determine which document categories are available for a specic page. Check with your developers
or help desk.
Related Topics
• Modules in Application Taxonomy
422
Oracle Procurement Cloud Chapter 15
Implementing Procurement Collaboration Messaging
15 Collaboration Messaging
• OAGIS 10.1
• OAGIS 7.2.1
You can enable messages for inbound and outbound communication. You can also communicate aachments and the
purchase order PDF with your outbound purchase order and change order messages.
423
Oracle Procurement Cloud Chapter 15
Implementing Procurement Collaboration Messaging
Outbound Messages -
• Process Purchase Order
• Change Purchase Order
• Cancel Purchase Order
Inbound Messages -
• Process Shipment Notication
• Process Invoice
• Receipt Advice
• Receipt Notication
For details about conguring electronic communications with Collaboration Messaging Framework, see the white
paper available on My Oracle Support: Oracle Procurement Cloud Purchasing Electronic Communication (Document ID
2174649.1).
Related Topics
• Update Existing Setup Data
To extend the information in the purchase order outbound message perform these main tasks:
1. Enable the Extensible Data Model Used for Electronic Messaging prole option.
2. Extend the Purchase Order Data Model by adding new aributes.
3. Update the predened XSLT map.
4. Duplicate the predened message and associate the updated XSLT map with the new message.
5. Update the trading partner setup to use the new message.
424
Oracle Procurement Cloud Chapter 15
Implementing Procurement Collaboration Messaging
2. In the Setup and Maintenance work area, access the Manage Administrator Prole Values task in the
Procurement Foundation functional area.
3. On the Manage Administrator Prole Values page, search for the Extensible Data Model Used for
Electronic Messaging (PO_ELECTRONIC_COMM_DATA_MODEL) prole option.
4. Set the prole option value to Yes.
425
Oracle Procurement Cloud Chapter 15
Implementing Procurement Collaboration Messaging
4. From the Manage Collaboration Message Denitions page, select the message you want to update.
5. From the Actions menu, click Duplicate Collaboration Messages.
6. The Duplicate Collaboration Message dialog opens and displays a new, automatically generated, unique
Message Name. You can enter a new, unique name of your choice instead.
7. Click Update to navigate to and specify the updated XSLT map le to associate with the new message.
8. Click Save and Close to upload the XSLT and create the new message. The new message is created with the
same external message type as the predened message.
426
Oracle Procurement Cloud Chapter 15
Implementing Procurement Collaboration Messaging
To set up the application to include the purchase order PDF in purchase order collaboration messages, perform these
main tasks:
1. Enable the Include Aachments in Electronic Communication prole option.
2. Download and modify the predened XSLT map.
3. Duplicate the predened message and associate the updated XSLT map with the new message.
4. Update the trading partner setup to use the new message.
427
Oracle Procurement Cloud Chapter 15
Implementing Procurement Collaboration Messaging
4. From the Manage Collaboration Message Denitions page, select the message you want to update.
5. From the Actions menu, click Duplicate Collaboration Messages.
6. The Duplicate Collaboration Message dialog opens and displays a new, automatically generated, unique
Message Name. You can enter a new, unique name of your choice instead.
7. Click Update to navigate to and specify the updated XSLT map le to associate with the new message.
8. Click Save and Close to upload the XSLT and create the new message. The new message is created with the
same external message type as the predened message.
1. Sign in to Oracle Applications Cloud as a user having the Procurement Application Administrator role.
2. From the Navigator, select Collaboration Messaging.
3. From the Collaboration Messaging Overview page, open the Manage B2B Trading Partners task.
4. On the Manage B2B Trading Partners page, search for, select, and act to edit the service provider or trading
partner.
5. From the Edit Trading Partner page, click the Outbound Collaboration Messages tab.
6. Add a row for the new message and enter the Collaboration Message Denition to include the new message.
7. Remove the row for the predened message.
8. Click Save.
428
Oracle Procurement Cloud Chapter 16
Implementing Procurement Other Common Setup and Maintenance Tasks
If prompted, select a context layer to determine the scope of users that your changes aect. After you complete your
changes, you can preview and test the changes, and then publish the sandbox to make your changes available to users.
Dene Seings
You can rename icons for infolet pages and other congurable pages in the page control, change their visibility seings,
and reorder them. On the Home Conguration page, you can:
• Click the infolet name or any other congurable page name to rename it.
• Click the Visible eld for an infolet or any other congurable page to change its visibility seing. You can show
or hide the icon for these pages in the page control on the home page. You can select one of the following
options:
◦ Yes: The icon appears in the page control.
◦ No: The icon doesn't appear in the page control.
◦ EL expression: The evaluation of the EL expression decides whether the icon appears in the page
control.
• Click the Default View eld for an available congurable page to specify whether the page should be set as the
default home view. You can select one of the following options:
◦ Yes: The page is set as the default home view.
◦ No: The page isn't set as the default home view.
◦ EL expression: The evaluation of the EL expression decides whether the page is set as the default home
view.
429
Oracle Procurement Cloud Chapter 16
Implementing Procurement Other Common Setup and Maintenance Tasks
Note: Only specic congurable pages, such as Quick Actions, are available for you to set as the
default home view. When you click the Default View eld for such pages, you get the options to
select Yes, No, or EL Expression. These options aren't available for other pages that you can't set as
the default home view.
• Use the Move Up and Move Down icons to adjust the relative positions of the icons for the infolet pages or
other congurable pages in the page control on the home page.
You can use prole options to dene seings for the lmstrip, which you can nd above all pages:
• To enable users to use the lmstrip, set the Springboard Strip Enabled prole option (FND_USE_FILMSTRIP)
to Yes.
• If the FND_USE_FILMSTRIP prole option is set to Yes, then you can display the lmstrip as expanded by
default. To do so, set the Springboard Strip Expanded prole option (FND_EXPAND_FILMSTRIP) to Yes. A
user can still collapse or expand the strip on any page, and when done, this prole option is set by default for
subsequent sessions of that user.
Related Topics
• Examples of EL Expressions for Conguring Navigation
• Set Prole Option Values
• Overview of Sandboxes
• Create and Activate Unied Sandboxes
Dene Display Seings for Home Page with Panel or Banner Layout
If you selected the panel or banner layout on the Themes page, follow these steps to congure the display of
information in the various sections of your home page:
1. Click the Home Page Display tab.
2. Select one of these options to display on the home page:
◦ Social: Displays social networking content, such as the number of followers.
430
Oracle Procurement Cloud Chapter 16
Implementing Procurement Other Common Setup and Maintenance Tasks
Dene Display Seings for Home Page with News Feed Layout
If you selected the news feed layout on the Themes page, follow these steps to congure the display of information in
the various sections of your home page:
1. Click the Home Page Display tab.
2. In the Name column of the table, click any section name to rename it.
3. Click the Visible eld for a section to change its visibility seing. You can show or hide the section on the home
page:
Related Topics
• Manage Themes
• Overview of Conguring Themes and Home Page Seings
• Create Themes
• Overview of Sandboxes
Create an Announcement
1. From the Navigator, select Tools > Announcements.
2. Click Create.
3. Specify the details, such as subject, start date, and end date.
4. Select a category. If you select User-Dened, a text box appears, where you can provide additional details.
5. Select any of these options:
431
Oracle Procurement Cloud Chapter 16
Implementing Procurement Other Common Setup and Maintenance Tasks
Note: Make sure your image size is 776x437 px or larger to avoid image distortion.
6. Add the content in the text box. Add the content in the text box. You can format your text using the formaing
options.
7. Click Save and Close.
Your changes on the Announcements page apply immediately to all users, even if you saved your changes while a
sandbox is active and not yet published.
Your default home page layout also determines how the home page displays the announcement.
• Panel or Banner: The home page displays only the announcement content, not the subject or image.
• News feed: The home page displays the entire announcement along with the subject and image in the News
and Announcements section.
Related Topics
• Overview of Conguring Themes and Home Page Seings
• Why can't I see announcements on the Home page
432
Oracle Procurement Cloud Chapter 16
Implementing Procurement Other Common Setup and Maintenance Tasks
• http://maps.live.com/default.aspx?where1=
• http://bing.com/maps/?v=2&encType=1&where1=
You can include parameters in the URL. For example, to avoid a locator box in Google Maps, add &iwloc=& to the
URL. So, you would enter http://maps.google.com/maps?iwloc=&&output=embed&q= as the prole value.
Related Topics
• Set Prole Option Values
• Why can't I see the map for contextual addresses
Caution: Don't enter any other value, such as Y, because that causes a broken link.
Access
Check with your security administrator that the appropriate users are assigned roles that inherit the following privileges:
• Record and View Issue (FND_RECORD_AND_VIEW_ISSUE_PRIV): To create a basic recording
• Set Issue Recording Advanced Options (FND_SET_ISSUE_RECORDING_ADVANCED_OPTIONS_PRIV): To
set advanced options before starting the recording
433
Oracle Procurement Cloud Chapter 16
Implementing Procurement Other Common Setup and Maintenance Tasks
Number of Users
Recordings are stored on servers, and by default, up to ve users can record at the same time on each
server. For performance reasons, you can set the Maximum Number of Users Allowed to Record Issues
(ORA_FND_RECORD_ISSUE_MAX_USERS) prole option to a number lower than ve.
Related Topics
• Record Issues to Troubleshoot
• How can I view the version information of an application
• Set Prole Option Values
434
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
435
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
This gure shows the relationships of the catalog components to each other.
Catalog
contains
1..n Attachment
Catalog or Image
root
contains
contains
Item
Category
1..n Assignment
contains
Item
1..n
Catalog
A catalog is a collection of categories that are organized to dene a classication of items. The top most level of a
catalog is the catalog root. All categories for the rst level in the category hierarchy are associated with the catalog root
through the catalog category association component.
Category
A category is a component of a catalog that represents a set of items. You can associate a category to a catalog through
the catalog category association. Both the shared category and the native category are associated thorough the catalog
category association.
436
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Item
An item represents objects such as a product, service or template. An item is assigned through the item category
assignment component.
Aachment or Image
Information is associated to the catalog or category through the aachment framework. Multiple aachments are
supported but you can only associate a single aachment or aachment type image with a catalog or category for
viewing in the UI.
Catalog Formaing
The format of a catalog is dened at the time the catalog is created and controls the behavior of the catalog at runtime.
When you format a catalog, the layout controls three main areas and includes the following tasks:
• Catalog conguration
• Date enablement
• Category sharing
Catalog Conguration
You can congure the catalog, and this aects how the content behaves. The catalog conguration contains a set of
aributes that dene the catalog conguration. These aributes interact to dene the runtime behavior of the catalog.
437
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
• Allow multiple item category assignment: When this option is selected, you can assign an item to one or more
categories in the catalog. The default is deselected, which means that each item can be assigned to only one
category in the catalog.
• Public Catalog: Select to mark this catalog as public. All users with access to view catalogs will have access to
this catalog.
Note: The catalog behavior for functional area catalogs is dened through the combination of elds within
the pages and the seeded functional area rules.
Category Sharing
The category sharing function enables sharing categories from a designated source catalog.
Related Topics
• Default Catalog Assignment
Catalog Details
You can view and edit a catalog on the Edit Catalog page when you have the appropriate permissions.
The following parts of the Edit Catalog page provide important capabilities for managing and editing catalogs:
• Catalog header region
• Catalog details tab
• Category hierarchy tab
You can change the default category for a catalog so that the category is used for the item creation process, based on
the values of aributes for the item. The choice of default category also enables other Oracle Fusion applications to
assign items to a category.
You can modify the start and end dates for a category as you update a catalog in order to control when the category is
used .
You can revise or reclassify the category to reect shifting relationships within the category hierarchy.
438
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
• The conguration aributes for the catalog, which control the runtime behavior for the catalog.
• The sharing aributes for the catalog, which control the source catalog that will be used for sharing from and
what content can be shared.
• The additional information for the catalog, which contains the descriptive exelds that support the catalog
metadata.
Related Topics
• Category Sharing
• Category Descriptive Flexelds
Automatic Assignments
The automatic assignment feature is enabled during catalog creation when you select the Enable automatic
assignment of category check box. The categories displayed for auto assignment catalogs are refreshed only at start
up and after you save.
Note that if you create a category in another catalog with the same structure value as the automatic assignment catalog,
the category is also added to your catalog. The categories displayed for auto assignment catalogs are refreshed only at
start up and after you save.
When you open a new catalog, any categories that have the same category structure value as the catalog structure
value for the catalog are automatically assigned to the catalog.
For example, Purchasing may maintain a master catalog containing all categories that represent commodities. Each
commodity team can create categories for their commodity in their own catalog.
The master catalog for purchasing is named Purchasing and is congured during creation to support the automatic
assignment of categories. Because you enabled automatic assignments for the Purchasing catalog, any categories
created by the commodity teams are added to the catalog automatically. The purchasing managers can view the
collection of all commodities represented as categories in the Purchasing catalog.
439
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Catalogs
What Can You Edit on the Edit Catalog Page
The Edit Catalog page is a shared page that has two modes - view and update. The view mode displays the selected
catalog in a read-only le. The update mode displays the selected catalog in an editable le. You must have edit catalog
privileges to access the catalog in the update mode. You can edit only an active or future-dated catalog.
You can edit the following elds in the catalog:
• Catalog Name
• Description
• Start Date
• End Date
• Default Category
• Allow multiple item category assignment
• Addition Information
• Category Hierarchy
• Category Details
• Items assigned to category
Default Category
You can edit this eld to select another category as the default category for item creation. You cannot remove the
default category if the catalog is assigned to a functional area that requires a default category to be specied.
Addition Information
You can edit the values of the descriptive exelds aributes.
After you make changes, clicking the Save buon saves the changes to the database but will does not close the Edit
Catalog page. Clicking the Save and Close buon saves the changes to the database and closes the Edit Catalog page.
440
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
the behavior of the category in the catalog. If a category association is inactive or end dated, having the value of the end
date aribute past the current date, then the items cannot be assigned to the category.
A catalog category association will be set to inactive state when the category referenced by the catalog category
association is set to an inactive state automatically, but the display will not be refreshed automatically.
You set the date enablement aributes are used to determine when a catalog, category, or catalog category association
is used or visible.
• On the Manage Catalog page, a table lter determines which catalogs appear. The default value for the choice
list is Active, indicating that only active catalogs will be displayed. You can select the value All to view both
active and inactive catalogs.
• On the Edit Catalog page, on the category hierarchy tab, two table lters determine what categories and catalog
category associations appear. The default values for the two choice lists are Active, indicating that only active
categories and active catalog category associations will be displayed. You can select the value All to view both
active and inactive categories and catalog categories associations.
• Other applications also use the date enablement aributes to lter information retrieved through application
programming interfaces or services for catalogs.
441
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
The following gure provides the date enablement aributes for these objects. The catalog, category, or the catalog
category association has an internal state that is active or inactive.
Catalog
Start Date
End Date
Catalog contains
root
1..1 Category
Catalog Category
Association
contains
Start Date
Start Date
The following aspects are important regarding date enablement for catalogs and categories:
• Start date
• End date
• Catalog and category objects
• Catalog category association
• Catalog and category rules
442
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Start Date
The start date is dened as the rst date that the object can be active. The start date can be future dated by seing the
value to a date later than the current date. The start date value defaults to the system date if no date is entered during
catalog or category creation.
End Date
The end date is dened as the last date that the object can be active. The object is end dated one second after the date
specied by the value of End Date, that is the next day at 12:00:01 a.m. You cannot set the end date in the past. Also,
you can change the end date from a condition when the object is ended to a new end date greater than or equal to the
system date, causing the object to go from inactive to active. The end date value is optional during catalog or category
creation.
443
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Category C1
Category C3
} Leaf level
category
and
assigned item
Category C4
Item BSX7489
}
Category C5
{Referenced Category} Referenced
category and
assigned item
Item
Category
Association
Item CX5488
444
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Components
The components of a category hierarchy are:
• Catalog root: The topmost node in category hierarchy that represents the object called catalog.
• Category: The catalog component that is used to represent the classication structure.
• Catalog category association: The line in the diagram represents the relationship between a catalog and
category or between a parent category and child category.
• Item category assignment: The doed line in the dialog represents the relationship between a category and an
item.
• Reference category: The category, C5 in this diagram, is shared as a reference category from a source catalog.
• Leaf level category: The lowest or boom-level category in a category hierarchy. You can assign items to all
levels in a category hierarchy if you congure the catalog to support this.
• Browsing category: The category, C2 in this diagram, is a browsing category. Browsing categories are categories
that you add to the category hierarchy for the purpose of classication and do not have items assigned to
them.
The category hierarchy does not have a limit on how many levels can be represented. The category hierarchy can have
multiple hierarchies within a single category hierarchy.
Category Edits
Categories can be edited only from within the Edit Catalog page, on the Category Hierarchy tab. To edit a category,
expand, or search in, the tree of categories associated with the catalog, then select the row for the category in the
category hierarchy table and edit the category's aributes in the category's Details panel. A category can only be edited
if the category is active and its associated catalog is active or future dated. If a category is directly shared, the same
category can be edited in multiple catalogs, except for the item assignments that are local to the catalog you are editing.
Category information can be edited in both the Details and Items subtabs.
After changes are made, the Save buon saves your changes without closing the Edit Catalog page. The Save and
Close buon saves your changes and closes the Edit Catalog page.
445
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Category Details
You can see category details when you select the row with the category in the category hierarchy table of the Edit
Catalog page. The category details are displayed in the right hand pane. You can edit the details of native categories.
The category detail region contains information about the category that is associated to the catalog. It also contains the
association start and end dates.
You can view and edit a catalog on the category details tab when you have rights to manage catalogs.
The following parts of the Category Hierarchy tab provide are important capabilities for managing and editing category
details:
• Details subtab
• Items subtab
• Aachments subtab
Details Subtab
The details tab contains information about the category that has been associated to the catalog. This information
appears in all catalogs, since a category can be associated to one or more catalogs. The details tab contains the category
conguration, category date enablement, association date enablement, and the additional aributes for the category.
The details tab contains aributes that dene a category. Unstructured information is added through aachments.
Images are added to a category and are displayed in the category details tab.
Items Subtab
The Items subtab contains item assignments are local to the catalog that the category is associated with. You can add
and delete item assignments.
Aachments Subtab
The Aachments tab contains the list of aachments that the category is associated with.
Create Categories
You can create categories in the context of a catalog, on the Category hierarchy tab on the Edit Catalog page . When you
select the Create icon in the category hierarchy table, the Create Category dialog appears.
446
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Select the Restrict category to item assignment only check box to add only items to the category.
After you complete the required elds for the catalog, clicking OK creates the category in the database, adds the
category to the point of selection in the category hierarchy, and closes the dialog.
Category Moves
You use the move category function in the category tree table region of the Edit Catalog page. This is a table row action.
The dialog is launched when you select an active or future dated category within the catalog and select this action.
Spreadsheet Interface
You can manage the catalog category hierarchy by downloading and modifying the content in the spreadsheet, and
then uploading the content back into the catalog.
Within the spreadsheet, you can dene new categories, edit the catalog hierarchy, and add categories to the catalog,
either as direct or reference categories. You can dene the category hierarchy for a catalog in the spreadsheet, by
creating or adding categories, then upload it when you create a catalog. If you have an existing hierarchy, you can cut
and paste the aened hierarchy into the spreadsheet.
You can export the category hierarchy from your catalogs so that it can be used by your partners. In the Product
Information Management work area, partners can directly import the category hierarchy into their catalogs.
Related Topics
• Set Up Desktop Integration for Excel
447
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
• File
• Repository File or Folder
• Text
• URL
File
You must provide a title for the le and create a description for the aachment. You select a le to upload from your
desktop.
Text
Enter the text string in the eld that you want to appear as an aachment. You must provide a title for the text and
create a description for the text aachment.
URL
Enter the URL address to a web page that you want to aach to the catalog. You must provide a title for the URL
aachment and create a description for it.
The Share check box alerts users that you added an aachment and the date that you performed the task.
448
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
The second method for creating the hierarchy is by importing the category hierarchy through the spreadsheet interface.
The category hierarchy can be exported from another catalog or other sources, edited and imported into a new catalog.
The hierarchy can also be added manually to the spreadsheet.
On the toolbar of the Category Hierarchy tab, you can create new categories, using the Create Category buon. You
can add categories, including shared categories, using the Add Category buon. If a catalog is has a category hierarchy,
you can edit it using the Move Category buon, which opens a dialog box.. You can also modify the hierarchy using
drag and drop. The catalog category association cannot be deleted, but can be end dated to make the catalog category
association inactive. The category hierarchy table provides a choice list lter that controls what catalog category
associations and categories area displayed based on the date enablement.
449
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
a referenced category. You use the list of values from the Add Categories menu. The Shared Category option will be
disabled if the catalog has not been congured for category sharing.
Related Topics
• Default Catalog Assignment
The punchout index le can either be provided by the supplier in the upload format, or you can prepare the upload le
based on the information provided by the supplier.
As a Catalog Administrator, you can continue to provide punchout catalog level keywords that return the punchout
catalog in the search results when there is a match. You can use high level keywords such as oce supplies or laptops
for those users who aren't looking for specic punchout items.
You can maintain a punchout search index le when dening or editing a punchout catalog. The search index can also
be maintained to reect any updates, such as price changes and item replacements.
450
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Items uploaded without error are available to users immediately if the catalog content security is set up correctly.
Upload Template
Using the aributes in the index, you can locate punchout items based on punchout item level information such as
Manufacturer, Part Number, or Supplier Part Number.
This table shows punchout item upload template aributes and their search and display behaviors.
Punchout Item Upload Searchable in Displayed in Search Displayed in Item Displayed in Item
Aribute Shopping Results Details Compare
451
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Punchout Item Upload Searchable in Displayed in Search Displayed in Item Displayed in Item
Aribute Shopping Results Details Compare
Upload Error
You can view upload errors in the Line Errors region on the Punchout Search Items Upload Status page.
You can access the Upload Status page from the Actions menu on the Manage Catalogs page, from the link in the
Punchout Upload Status column on the search results, and from the Upload Status eld on the Edit Punchout Catalog
page.
• Changes in prices
• Replacing items
• Removing items that are no longer available
• Adding new items
• Fixing any data errors
452
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Tasks
The following tasks are application maintenance tasks recommended when using the rapid implementation approach:
1. *Create a Supplier and Supplier Site
2. Import Suppliers
* Required task
◦ Name
◦ Tax Country
◦ Tax Registration Number
3. Click Create.
4. On the Edit Supplier page, Prole tab, enter:
◦ Supplier Type
5. On the Edit Supplier page, Addresses tab, click the Create icon.
6. On the Create Address page, enter:
◦ Address Name
◦ Country
Note: The Country eld automatically defaults to the country set in your Work
Location, as seen in the Personal Information page, Employment Details tab.
◦ Address Line 1
◦ City
◦ County
◦ State
◦ Postal Code
◦ Language
453
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
◦ Address Purpose
Select all applicable boxes. At a minimum select Purchasing.
If smart address search is enabled, then for a supplier, you can search a specic address and include that
address information here.
7. Click Save and Close.
Repeat address creation for all addresses you do business with for this supplier.
8. With your supplier selected, open the Sites tab and click the Create icon.
9. On the Create Site page, enter:
◦ Address Name
Select the address for this supplier site.
10. Click Save.
11. Click the Receiving subtab and enter:
◦ Receipt Routing
12. Click the Site Assignments subtab and click Autocreate Assignments. This may only be appropriate for your
rst site. Other sites may require manual creation.
13. Click Save and Close.
14. With your supplier selected open the Contacts tab and click the Create icon.
15. On the Create Contact page, enter:
◦ First Name
◦ Last Name
◦ Email
◦ Select Administrative contact check box
16. Click the Create icon.
17. In the Contact Addresses region, click the Select and Add icon:
◦ Select the contact address.
◦ Click Apply.
◦ Click OK.
18. In the User Account region, click the Create user account check box. Accept all the applicable roles for this
contact.
19. Click Save and Close.
20. Click Save and Close.
Supplier Numbering
The Procurement Application Administrator congures supplier numbering. Suppliers created through the Create
Supplier task ow, through the supplier registration process, or through supplier import, are automatically numbered.
The starting supplier number is dened in the Specify Supplier Numbering Setup page. The predened default number
is 1. The supplier number increments with each additional supplier created.
The next supplier number can be updated at any time, not just during initial setup. This can be used, for example, to
skip a range of supplier numbers. The application validates that the next supplier number specied is not already used.
454
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Related Topics
• Create Suppliers with the Import Suppliers Process
For more information refer to the Supplier Outbound Synchronization Service white paper on My Oracle Support.
Supplier Registration
You can congure the supplier registration process based on the expected supplier business relationship of a supplier.
You can dene two separate registration ows based on the intended business relationship.
• Spend Authorized Supplier requests: Companies already identied for a procurement need are directed by
the buying organization to the spend authorized registration ow. The ow captures more rigorous prole
information needed before agreements, orders, and invoices can be transacted. For example, a spend
authorized company registering can be required to provide bank account information.
• Prospective Supplier requests: Unknown companies are presented with the prospective supplier ow. They
must only provide minimal prole information to participate in the sourcing and supplier qualication activities.
Possible prole components that you can include during a registration ow include:
• Organization Details: Basic supplier information including the supplier name.
• Contacts: Supplier contact information.
• Contact User Account: User accounts control privileges for Supplier Portal contacts.
• Addresses: Company addresses including associated contacts.
• Business Classications: Supplier certications important to the buying organization such as supplier diversity
programs.
• Bank Accounts: Supplier banking information.
• Products and Services: Identies what categories of products and services are provided by the supplier.
• Qualications Questionnaire: Additional questions for suppliers.
455
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
When you congure the two supplier registration ows you identify which prole aributes the supplier sees. Also you
can specify whether the supplier must enter a value for the aribute.
• Enabled: The aribute is displayed to the supplier, but the supplier is not required to enter information.
• Required: The supplier must supply information for this aribute.
Note: Your supplier registration conguration applies to suppliers from all registration sources.
In the Default Business Relationship for Registration Sources region, you identify the default business relationship
for each registration ow. The default business relationship determines what prole information is included as
congured for the registration page.
456
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
• Suppliers
• Supplier Qualication
• Supplier Negotiation
Supplier proles can also be changed by internal users. Updates to bank account changes by internal users are
submied to an approval process. See Conguring Internal Supplier Bank Account Change Approvals: Explained.
The Congure Supplier Registration and Prole Change Requests task does not congure supplier prole changes
made by internal users.
You can specify approval requirements for prospective and spend authorized suppliers for the following entities:
• Organization Details: Basic supplier information including the supplier name and supplier prole level
descriptive exelds.
• Contacts: Supplier contact information including supplier contact descriptive exelds.
• Contact User Account: User accounts that control account privileges for supplier contacts to use Supplier Portal.
• Addresses: Company addresses including associated contacts including supplier address descriptive exelds.
• Business Classications: Supplier certications important to the buying organization such as supplier diversity
programs.
• Bank Accounts: Supplier banking information.
• Payment Methods The method used to pay the supplier.
• Products and Services: Identies what categories of products and services are provided by the supplier.
• Tax Identiers: Tax organization, tax country, and taxpayer ID to identify the supplier for tax purposes.
• Site Details: Site information such as the address and site purpose (spend authorized suppliers only).
Conguration of the Site Details aribute for prospective suppliers is not available.
Related Topics
• Supplier Products and Services Categories
• Supplier Registration Process
• Supplier Registration Approval
• Internal Supplier Prole Change Request Approvals
457
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Bank accounts created using import are not subject to review and approval and are saved to the prole immediately.
Supplier users cannot create any prole change requests while internal bank account changes are pending approval.
However, bank account import will still work when internal bank account changes are pending approval.
Any bank account changes pending approval can be canceled before the nal approval is obtained.
Related Topics
• Internal Supplier Prole Bank Account Change
• Options to Congure Supplier Registration and Supplier Prole Change Request
• Congure Oerings
• Internal Supplier Prole Change Request Approvals
• Set Up Internal Supplier Prole Change Request Approvals
458
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
The supplier match feature leverages Oracle Enterprise Data Quality, which provides data quality services for Oracle
Cloud applications.
Be aware that making changes to the Enterprise Data Quality setup tasks (tasks 2 and 3 in this topic) can impact other
product ows using Enterprise Data Quality, for example, customer data management.
◦ Cluster Key Level: Typical: When using the Supplier Matching feature, this value is set internally to
Exhaustive, which is the desired seing level to produce optimal matching results.
◦ Score Threshold: 50.0 This threshold indicates the minimum match score above which results are
returned.
◦ Match Results Display Threshold: 20.0 This threshold indicates the number of matched records that
display during the matching process.
3. To edit the seings, you must duplicate the predened conguration. Generally, this is not necessary as the
predened seings described above should return the desired results in the supplier matching process.
4. Select the conguration and click Duplicate.
5. Edit the conguration that you duplicated.
6. Click Rebuild Keys to rebuild all indexes for the new conguration matching to take eect. This process can take
a number of hours.
459
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Note: Note: The Rebuild Keys action must be performed even if you have not edited the predened
conguration. This step is essential in cases where the supplier matching feature is enabled on an
existing instance, for example, where parties already exist in the customer instance in order for
existing parties to be included in the search for duplicate matches.
To perform a quick test of the conguration and exercise the Enterprise Data Quality matching engine, go to Review
Conguration Results and enter the seings described previously:
Enter a Party Name that is similar to an existing supplier and click Find to retrieve the match results.
Note: The supplier match feature is available on Oracle Procurement Cloud only. It is not supported on Oracle
Fusion Procurement (on-premise).
Related Topics
• Update Existing Setup Data
Note: These setup tasks are supported by the Oracle Trading Community Architecture, which manages
external party data used by supplier and customer master data. Changes to these setup tasks impact other
products using Trading Community Architecture location data.
Note: The job role of Application Implementation Consultant is required to access these tasks.
460
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Note: Address cleansing is not available in Oracle Procurement Cloud. The seings selected on the Address
Cleansing Level dialog box have no eect on how Data Quality Management functions.
Related Topics
• Update Existing Setup Data
Transaction account types are predened by the Subledger Accounting application, and categorize dierent accounts
generated for transactions. Sources are assigned to transaction account types.
Transaction account types allow subledger applications to categorize dierent accounts that are generated for
transactions. Accounts that require a consistent derivation throughout the application should share the same
transaction account type. This also provides the ability to view or manually override an account on the transaction.
Transaction account types are assigned to transaction account denitions. Assign account combination or segment
rules to each transaction account type assignment in a transaction account denition. Assigned sources in each
transaction account type are available for use in account rules to derive accounts for a transaction account type.
This setup is accomplished using the Dene Transaction Account Rules task list in the Setup and Maintenance work
area.
461
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Sources
Legend
Introduced by Transaction Account Rules
Users
462
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Account Rules
Account rules are used to determine the accounts for subledger journal entry lines. In addition, you can specify the
conditions under which these rules apply. Using these capabilities, you can develop complex rules for dening accounts
under dierent circumstances to meet your specic requirements. You can dene account rules for an account,
segment, or value set.
Another segment can be determined with the use of a constant value. Creating the account one segment at a time
oers greater exibility, but also requires more setup.
Use both segment based and account based rules to derive a single account. Segment-specic rules are used, where
they are dened, and take the remaining values from an account-based rule. For example, you can use an account rule
which is for all segments and also separately use a rule which is for one particular segment. Segment-specic rules take
precedence over the all segments account based rule.
Combine account rules with segment rules. In this case, the segment value is derived from the segment rule to override
the corresponding segment of the account. If the segment rule has conditions associated with the priorities and none
are met, no override occurs and the segment value is derived from the account rule.
Note:
• If the returned account is end dated with a date that is the same or before the subledger journal entry
accounting date, and an alternate account is dened in the general ledger, the alternate account is used. The
original account is stored on the journal line for audit purposes
• If the alternate account is invalid, and the Post Invalid Accounts to Suspense Account option is selected
in the Create Accounting process, then a suspense account is used. An error message is displayed if a valid
suspense account is not available.
• Assign an account rule from the same or a dierent application to a journal line rule in the subledger journal
entry rule set. For example, to derive an expense account for journal line rule Expense, assign the Projects Cost
Account rule owned to the Payables journal line rule Expense.
• Create an account rule based on an account rule from another application and assign it to a journal line rule.
For example, you may create an account rule Invoice Expense Account referencing Project Cost Account
463
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
assigned in the Priorities region. You may aach the Invoice Expense Account rule to the journal line rule
Expense in the journal entry rule set.
Note:
• To share an account rule across applications, all sources used by the account rule must be available for the
event class.
• If the sources are available, an account rule is assigned to a journal line rule in the journal entry rule set.
Verication occurs to conrm that all sources used by the account rule are available for the journal line rule
accounting event class. Journal line rules are only available if the sources are shared; such as reference
objects.
The Create Accounting process evaluates conditions based on the priority of the rule detail. When the condition is met,
the rule detail is applied.
Related Topics
• Examples of Creating Condition
464
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
The chart of accounts is optional when dening this type of rule. If the account rule has a chart of accounts
assigned, then all the related account rules must use the same or no chart of accounts.
Note: A chart of accounts must be specied for account combination rules using constants.
Segment Rules
Set up segment rules as follows:
• When a chart of accounts is specied, create a rule to derive the value for a specic segment from the chart of
accounts.
• If the chart of accounts is not specied, create a rule to derive the value for an account segment with a specic
qualier.
Set up segment rules using the same methods discussed in the preceding Account Combination Rules section. By
specifying dierent value types, users can select the way in which the segment value is derived.
Note: A chart of accounts must be specied for segment rules using constants.
Mapping Sets
Mapping sets provide an ecient way to dene a segment or account combination value for one or more transaction or
reference aribute values. Using such input and output mappings is simpler than using complex conditions on account
rules.
Based on the value of the source input, a single segment or a full account is derived.
465
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
◦ Exporting all mappings created for the mapping set to add or edit the current mappings.
Example
The region name can be the input for the mappings to derive the value of the region segment. You can create a
mapping set that maps region names to the corresponding region code.
This table contains region names and segment values used in this example.
East 01
South 02
West 03
Additional transaction information, such as transaction type and salesperson name, could also be used as inputs to help
derive a dierent segment value for each combination of the input values.
Related Topics
• Accounting Sources
466
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
◦ Expected input or output combinations are constant across the charts of accounts.
◦ Based on the selection, the mapping set provides the value for an account, segment, or value set.
• Dene the input source:
◦ Specify the input source for mapping.
• The input source is provided for predened mapping sets.
• Dene the chart of accounts and value sets.
• Specify the output value for the mapping:
◦ For a given input value, enter the corresponding output value.
◦ The account rule uses this value to populate either the account or the segment.
• If the output type is a value set, the output value is an individual value from the value set entered.
• If the output type is segment, the output value is an individual segment value.
• If the output type is account combination, the output value is an entire account.
Example
In the following example, the chart of accounts is set up with four segments. A mapping set is dened with a value set
for Supplier Type as described in the following table.
Services 01-100-6120-000
Consulting 01-400-6110-000
467
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Assume that two invoices are entered, one for a supplier with a type of Services and one for a supplier with a type of
Manufacturing.
When using the mapping set, the source value Supplier Type is compared with the mapping set input values to
determine the account.
In this example, there is a match for the rst case; the invoice with a supplier type of Services maps to an input value.
However, the invoice with a supplier type of Manufacturing does not map to an input value.
1 Services 01-100-6120-000
Note: To ensure that transaction 2 is accounted, you may want to modify the account rule to which the
mapping set is assigned. If not, a separate rule can be dened to provide for the Manufacturing supplier type,
or dene a default output in the existing mapping set.
Aspects of using project information for account derivation that are covered in this topic are:
• Example
• Aributes
• Setup
Example
For example, you can set up an account rule to select the account to which a project expenditure should be charged.
Base the rule on the contract number, or the funding source of an award, or the contract owning organization.
Aributes
The following are some of the project aributes you can use in account rules.
• Award Owning Business Unit
468
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
• Award Purpose
• Award Type
• Contract Number
• Funding Source
• Principal Investigator
For more information refer to the following white paper available on My Oracle Support (MOS): Transaction Account
Builder in Oracle Fusion Procurement (document ID 1507175.1).
Use the Manage Account rules task to review the delivered Purchasing Charge Account Rule. The rule includes the
Outside Processing Account rule value. The rule value includes a condition dened for outside processing purchases,
where the Outside Processing Indicator value is set to Yes. When the condition is true the charge account is derived
from a mapping set.
Use the Manage Mapping Set task to congure the delivered Outside Processing mapping set associated with the
Purchasing Charge Account rule. To derive the charge account required for automatic creation of outside processing
purchase orders, you must dene rules for the delivered mapping set. Outside processing-related Input values include:
For each input value select an output charge account to map it to.
You can also use the Manage Account rules task to dene a rule with a condition where the Destination Type Code is set
to Work Order.
469
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
• Uniformly delivers tax services to all Oracle Fusion application business ows through one application interface
• Provides a single integration point for third-party tax products and services
• Lets you congure and add country-specic tax content
• Ensures control over manual intervention and update
With Oracle Fusion Tax, you can model your taxes according to the needs of the following local and international tax
requirements:
◦ New taxes
◦ Local law changes
◦ Special tax rates
◦ Special exceptions for products and customers
Task Lists
The Dene Tax Conguration activity contains the following task lists
• Dene Tax Conguration: Use these tasks to create a basic tax conguration for each of your tax regimes.
• Dene Advanced Tax Conguration: Use these tasks to congure optional tax setup that addresses more
complex tax requirements, such as exceptions to standard tax calculations.
470
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
What taxes am I subject to? Analyze your tax environment for each of Set up your tax regimes, taxes, and
the countries in which you operate. tax jurisdictions according to the tax
requirements for each country.
What do I do? Identify and classify the transactions that Create scal classications to classify and
you perform. categorize your transactions in a common
manner across your organization. Use
For example, do you primarily sell physical these scal classications in tax rules to
goods? If you do, do you manufacture obtain the appropriate tax result.
them, or do you buy and sell them without
additional manufacturing? Do you sell
these goods in another state or province?
Do you export these goods? Do you
provide or use services?
What products do I buy or sell? Determine the products that you buy and Where Oracle Fusion Inventory is
sell. The taxes that you are subject to installed use the Inventory Catalog
depend on them. feature with Oracle Fusion Tax product
scal classications and intended use
For example, you must register for, and functionality to classify the taxable nature
therefore collect and remit service taxes and intended use of the items. You
only if you provide taxable services. If you can then dene tax rules using these
manufacture goods for export, you may
471
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Who are my customers and suppliers? Determine the types of customers and Use the party classications feature to
suppliers. They can aect the taxes to categorize your customers and suppliers.
which you are subject, the tax status, or You can use the classications while
tax rate that applies. dening tax rules to derive the appropriate
tax result.
For example, you are a UK based company
that supplies physical goods to another You can create a party scal classication
country, which is also a member of the by assigning a Trading Community Model
European Union. The transaction rate class category to a predened party scal
for UK VAT is dependent on whether the classication type code. The Trading
customer is registered for VAT in the Community Model class codes dened
country to which the supply is made. under the class category become scal
classication codes belonging to the party
scal classication type. You can create
a hierarchy of party scal classication
types to reect the levels of codes and
subcodes within the Trading Community
Model classication.
Note: Scope is a valuable tool during implementation, but tax scope values are not mandatory. You can elect
to not dene them.
Dening Scope
When implementing transaction or withholding tax, you can dene scope values for taxes, tax jurisdictions, tax statuses,
tax rates, tax recovery rates, and tax rules. To set scope, you can:
The scope value you select denes the context of that setup. For example, if you select a tax regime to use as a scope
value for a tax, that value is automatically populated in the search aributes on the Manage Tax page. That tax regime's
aributes are also populated on the Create Tax page. The same logic applies to the next step in the tax setup.
472
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Scope Values
The following table identies where you dene the scope value in the Dene Tax Conguration and Dene Advanced
Tax Setup task lists:
At transaction time, the tax conguration determines the following taxes and tax amounts:
• Tax regimes
• Taxes
• Tax jurisdictions
• Tax statuses
• Tax rates
473
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
levels of specifying setup options for foundation tax components with Canada Goods and Services Tax (GST) and
Harmonized Sales Tax (HST) as an example.
Component Tasks you can perform: Tasks you cannot perform: Canada GST and HST
Example
Tax Regime • Share tax content • Dene conguration CA GST and HST
among legal entities owner tax options.
and business units. • Dene application tax
• Enable partner options.
integration. • Dene party tax
• Associate scal proles.
classications.
• Dene tax reporting
types and codes.
• Dene features to
inuence setup task list.
Tax Jurisdictions • Dene location-based Specify tax rule defaults. • CA Alberta GST
tax rates. • CA BC HST
• Dene customer
exemptions and rate
exceptions.
Tax Status • Dene common rules • Specify tax rule • GST Standard
for tax rates. defaults. • HST Standard
• Drive reporting needs. • Dene customer • HST Reduced
• Allow manual override exemptions.
to tax rates. • Specify party
registrations.
474
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
When running the tax determination process, the tax rules dened against the foundation tax conguration setup and
the details on the transactions are evaluated in the order of priority. If the rst rule is:
• Successfully evaluated, the result associated with the rule is used.
• Not successfully evaluated, the next rule is evaluated until either a successful evaluation or a default value is
found.
The following table presents the scenarios and actions associated with each of these categories:
No tax rules required For the tax, dene tax rule defaults for the
The tax authority levies tax on all sales tax status, tax rate, and tax recovery rate.
and purchase transactions at the same
rate. Tax applicability, tax rates and The tax determination process uses the
recovery rates do not vary based on: tax rule defaults to determine the tax.
• Parties to the transaction
• Products or services in the
transaction
• Business processes involved in the
transaction
475
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Related Topics
• Example of Dening an Exception to the Tax Registration Tax Rule Default
To support these requirements, dene and use geography regions and tax zones. Geography regions and tax zones
provide a conceptual model to use place information on transactions and information related to the transaction.
476
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Country Information
Country is a required eld in all of the tax-related address locations. The country elds are supported by a predened
ISO 3166 country name and two-character country code. For more information on country names and codes, see hp://
www.iso.org/iso/english_country_names_and_code_elements.
You don't set up a country as a specic geography level in Trading Community Model geography because country is an
inherent part of all tax-related address locations.
Tip: Use the highest level of geography, typically country, wherever possible.
Geography Elements
Dene geography elements as part of Trading Community Model geography. They control the use of geography and
addresses. Oracle Fusion Tax commonly uses the following features:
• Geography or tax zones
• Geography levels
• Address controls
• Geography name referencing
Use geography levels to dene the levels of geography that are used within a country. It's only relevant elements of the
address that are referenced for tax purposes. For example, state, county, and city are used for US Sales and Use Tax.
County in the UK isn't relevant from a tax perspective and therefore, you don't need to set it up.
Tip: When address elements are needed for tax purposes, such as county and city for US Sales and Use Tax,
set these address levels as mandatory within Trading Community Model geography. This ensures that these
elements are always present on all applicable addresses. Seing address levels as mandatory also ensures
that amended or newly applicable addresses are validated and that the level is either derived or entered. When
you're seing up migrated addresses ensure that they're compliant with the mandatory levels being present.
This should be validated and any address levels added as part of the migration process.
The geography name referencing process within Trading Community Model geography links specic addresses to the
levels dened in the geography setup. This process is typically automatic. However, when you encounter issues, you
may need to trigger this process to ensure that all addresses are correctly linked to their applicable levels.
Tax Zones
Use the tax zone functionality when you need to identify a group of geography elements while calculating tax. Tax
zones are dened as part of Trading Community Model geography.
For example, in the EC it's important to know whether goods and services are being delivered within the EC. Use the tax
zone functionality to create a tax zone, which denes the membership to the EC as well as, the dates on which a country
became the member.
Tip: Create a generic tax zone so that you create a tax zone type that can be used in multiple situations.
For example, for a tax zone type needed to identify EC, create a generic tax zone type for all economic
communities, which can later be used in other situations where economic communities or trade agreements
aect tax determination. You can also use the tax zone functionality to group postal codes to provide useful
groupings that can identify some higher-level tax regions such as, cities or counties.
477
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
The tax determining factors for locations are given generic names such as ship-to and bill-from, depending on the
transaction types.
These generic locations are mapped into specic locations based on the transaction as shown in the following table:
Ship-to party Customer (ship-to) party site Ship-to location on the line
Ship-from party Warehouse on the line. If there is no Supplier (ship-from) party site
warehouse on the line, such as with
services, the location from the item
validation organization in the Receivables
system parameters is used.
Use the country name to search for country defaults, which control the:
• Fiscal classication defaults
• Party tax prole defaults
• Tax regime defaults
478
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
• Tax defaults
Use the country name to select the following scal classications associated with that specic country:
Related Topics
• Overview of Transaction-Based Fiscal Classications
• Tax Rules
Create a condition set that refers to this geography determining factor as follows:
Use this combination of determining factors in any situation where you need to identify exports from the United States.
479
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
You can also use the geography level as a tax rule qualier.
The tax determining factors for locations are given generic names such as ship to and bill from, depending on the
transaction types. The transaction types are:
• Order-to-cash: For Oracle Fusion Order Management and Oracle Fusion Receivables transactions.
• Procure-to-pay: For Oracle Fusion Purchasing and Oracle Fusion Payables transactions.
These generic locations are mapped to the specic location, based on the transaction as shown in the following table:
Ship-to party Customer (ship to) party site First-party legal entity
Ship-from party First-party legal reporting unit Supplier (ship from) party site
Related Topics
• Overview of Transaction-Based Fiscal Classications
• Tax Rules
480
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
You can use this combination of determining factors in any situation where you need to identify specic deliveries to a
specic state.
The tax determining factors for locations are given generic names such as ship-to and bill-from, depending on the
transaction types.
These generic locations are mapped to the specic location based on the transaction as shown in the following table:
Ship-to party Customer (ship to) party site First-party legal entity
Ship-from party First-party legal reporting unit Supplier (ship from) party site
481
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Related Topics
• Overview of Transaction-Based Fiscal Classications
• Tax Rules
Scenario
Use geography as the determining factor class, ship-to as the class qualier, and all economic communities and country
as the determining factors of the tax zone type as shown in the following table:
You can use this combination of determining factors in any situation where you need to identify the deliveries that are
made from the UK to other EU countries.
482
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
• Tax regimes
• Taxes
• Tax jurisdictions
• Tax statuses
• Tax rates
Tax Regimes
Set up tax regimes in each country and geographical region where you do business and where a separate tax applies.
A tax regime associates a common set of default information, regulations, scal classications, and optionally,
registrations, to one or more taxes. For example, in the US, create a Sales and Use Tax tax regime to group taxes levied
at the state, county, and district levels. For the UK, create a tax regime for GB VAT.
Taxes
Set up details for the taxes of a tax regime. Each separate tax in a tax regime includes records for the tax statuses, tax
rates, and tax rules that are used to calculate and report on the tax.
For example, for US Sales and Use Tax dene a tax for each state, county, and city. For the UK, set up a tax for GB VAT.
Tax Jurisdictions
Set up tax jurisdictions for geographic regions or tax zones where a specic tax authority levies a tax. A tax jurisdiction
species the association between a tax and a geographic location.
You also use tax jurisdictions to dene jurisdiction-based tax rates. A tax jurisdiction tax rate is a rate that's distinct to a
specic geographic region or tax zone for a specic tax.
For example, for US Sales and Use Tax create a county jurisdiction for every county in the parent geography type of
State and in the parent geography name of California. For the UK, create a tax jurisdiction for the country of United
Kingdom.
Tax Statuses
Set up the tax statuses that you need for each tax that you create for a combination of tax regime, tax, and
conguration owner. A tax status is the taxable nature of a product in the context of a transaction and specic tax on
the transaction.
For example, for US Sales and Use Tax create a tax status for standard and exempt. For the UK set up separate tax
statuses for standard, zero, exempt, and reduced rates.
483
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Tax Rates
Set up tax rates for your tax statuses and tax jurisdictions. For tax statuses, set up a tax rate record for each applicable
tax rate that a tax status identies. For tax jurisdictions, set up tax rate records to identify the tax rate variations for a
specic tax within dierent tax jurisdictions.
For example, for US Sales and Use Tax create a tax rate for each tax jurisdiction (jurisdiction-based rates). For the UK,
set up separate tax rates for standard, zero, exempt, and reduced (tax status-based rates).
For example, organizations that produce VAT-applicable goods and services are allowed to recover 100% of the VAT
they pay on typical purchases. They would use a default 100% recovery rate.
Organizations, such as nancial institutions, which create services that are exempt from VAT, are not able to recover
VAT on their normal purchases. They would use a default 0% recovery rate.
Related Topics
• Tax Regimes
• Taxes
• Tax Jurisdictions
• Tax Rate Setup
A legal entity tax prole is automatically created when a legal entity is dened in the implementation. Similarly, a
business unit tax prole is automatically created when a business unit is dened. For the business unit, indicate whether
it uses the subscription of the legal entity instead of creating its own.
484
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
The basic tax denition includes controls that you can set to provide the override capability at transaction time. For
example, allow users to make manual updates on transaction tax lines, select the Allow override for calculated tax
lines and the Allow entry of manual tax lines options. However, to enforce automatic tax calculation on transaction
tax lines, don't enable these options.
Use the direct and indirect tax rule defaults to specify the values that apply to the majority of your transactions. Create
tax rules to address the exceptions or variations to the defaults. For example, for the Goods and Services Tax (GST) that
applies to the supply of most goods and services in Canada, set the Tax Applicability default to Applicable. A luxury
tax, on the other hand, is a tax on luxury goods or products not considered essential. As it doesn't apply to most goods
and services, set the Tax Applicability direct tax rule default to Not Applicable. Then create a tax rule to make the tax
applicable when the product in the transaction satises the luxury requirement.
Assign your default tax accounts for the taxes in a tax regime to post the tax amounts derived from your transactions.
The tax accounts you dene at the tax level, populate either the tax rate accounts or tax jurisdiction accounts for the
same ledger, and optionally, the same business unit. You can update these default tax accounts in the tax rate or tax
jurisdiction setup.
Note: When you create your tax, the tax recoverable account and tax liability account may be prepopulated
from default account values dened in the Rapid Implementation for General Ledger spreadsheet upload. You
can override these values.
The following table describes the direct tax rule defaults and examples:
485
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Tax Registration Determines the party whose tax With a direct default of bill-to party,
registration status is considered for an the tax registration of the bill-to party
applicable tax on the transaction. is considered. The application stamps
their tax registration number onto the
transaction, along with the tax registration
number of the rst-party legal reporting
unit.
486
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Note: Use the Manage Tax Rules task to dene exceptions to the direct tax rule defaults you dene for the
tax.
The following table describes the indirect tax rule defaults and examples:
Tax Jurisdiction Indicates the most common geographic Value-added tax (VAT) is applicable to
area where a tax is levied by a specic tax the supply of most goods and services in
authority. Portugal. For the tax PT VAT, create the
default tax jurisdiction as the country of
Portugal. To address specic tax regions
such as Azores and Madeira, which have
lower VAT rates than Portugal, dene
jurisdiction rates with dierent VAT rates.
Tax Recovery Indicates the recovery rate to apply to In Canada, both federal and provincial
each recovery type for each applicable tax components of Harmonized Sales Tax
on a purchase transaction. (HST) are 100% recoverable on goods
bought for resale. In this case, with
two recovery types, you can set up two
recovery rate defaults for the HST tax.
487
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Note: Use the Manage Tax Rules task to dene exceptions to the indirect tax rule defaults you dene for the
tax.
Note: When you create your tax, the tax recoverable account and tax liability account may be prepopulated
from default account values dened in the Rapid Implementation for General Ledger spreadsheet upload. You
can override these values.
Account Description
The ledger and business unit for which you are creating the tax accounts.
Ledger and Business Unit
Interim Tax An account that records tax recovery or liability until the event prescribed by the statute is
complete. Generally, the payment of the invoice is the event that triggers the generation of
the tax recovery or liability. You must set up an interim tax account for taxes and tax rates that
have a deferred recovery selement. Once you set up an interim tax account for this tax rate,
you can't change the recovery selement to Immediate.
An account that records tax recovery amounts. If you set up recovery rates for a tax that you
Tax Recoverable Account also self assess, then dene a tax recovery account for the associated recovery rates.
An account that relieves tax liability amounts. If you set up recovery rates for a tax that you
Tax Liability Account also self assess, then dene a tax liability account for the associated tax rates.
An account that records the tax liability associated with nance charges that is used as a
Finance Charge Tax Liability deduction against overall tax liability.
Accounts that record tax amounts on earned and unearned discounts and adjustments that
Nonrecoverable Tax Accounts you can't claim as a deduction against tax liability.
488
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Account Description
Accounts that record net changes generated by adjustments, earned and unearned discounts,
Expense and Revenue Accounts and nance charges. Receivables activities such as discounts and adjustments reduce the
receivable amount, and are therefore considered an expense.
Related Topics
• Tax Rules
489
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Field Value
Country
Regime Level
Canada
Country
1/1/01
Start Date
Note: Consider your tax planning carefully before you enter the start date. This
date must accommodate the oldest transaction that you want to process within
this tax regime. After you create the tax regime, you can only update this date
with an earlier date. If you enter an end date, you can't update this date after you
save the record.
Select
Allow cross regime compounding
5. On the Conguration Options tab, select a party name. The party name is either the legal entity or the business
unit (or both) for which you set up the conguration.
6. Select a subscription from the Conguration of Taxes and Rules list. This subscription denes the
conguration owner setup for transactions of the legal entity and business unit for this tax regime.
7. Enter the eective start date for this conguration option. This date must be within the date range of both the
party tax prole and the tax regime.
8. Click Save and Close.
Field Value
CA GST
Tax
490
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Field Value
Province
Geography Type
Country
Parent Geography Type
10
Compounding Precedence
Select
Allow override of calculated tax
lines
Select
Allow multiple jurisdictions
Select
Allow creation of multiple of
jurisdictions
Select
Allow tax recovery
Select
Allow tax recovery rate override
Standard
Primary Recovery Rate
Field Value
CA Ledger
Primary Ledger
CA Operations
Business Unit
0001-1500-1100-1000
Tax Recoverable Account
0001-1500-1100-1000
Tax Liability Account
491
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Field Value
Ship to
Place of Supply
Applicable
Tax Applicability
Ship-from party
Tax Registration
STANDARD_TC
Tax Calculation Formula
STANDARD_TB
Taxable Basis Formula
Field Value
CA Alberta
Tax Jurisdiction Code
Province
Geography Type
AB
Geography Name
Select
Set as default jurisdiction
1/1/01
Default Start Date
Field Value
CA GST STD
Tax Status Code
Select
Set as default tax status
1/1/01
Default Start Date
492
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Field Value
Field Value
STANDARD
Recovery Type
100
Rate Percentage
1/1/01
Eective Start Date
Select
Set as Default Rate
1/1/01
Default Start Date
Field Value
CA GST STD
Tax Status Code
Percentage
Tax Rate Type
5
Rate Percentage
Select
Set as Default Rate
1/1/01
Default Start Date
493
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Related Topics
• Update Existing Setup Data
The preceding options always appear as read-only check boxes in the Associated Taxes Setup Information region. The
option appears as selected if you selected the option in one of the taxes within this tax regime. If you didn't select the
option in one of the taxes, the option appears as not selected.
For example, suppose you have a California county sales tax that applies to all counties, so you need a tax with multiple
jurisdictions. In this case, enable the Multiple Jurisdictions feature at the tax regime level and select the Allow
multiple jurisdictions option at the tax level. When you open the Edit Tax Regime page, Associated Taxes Setup
Information region for this tax regime, the Allow multiple jurisdictions option appears as selected.
494
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
If applicable, designate the tax regime as a parent regime or indicate the parent regime name if the tax regime belongs
to a parent regime. Use a tax regime dened as a parent tax regime to group other nonparent tax regimes for reporting
purposes.
Defaults Region
495
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Use tax reporting Option that controls None None Controls whether you
conguration whether the tax can enter tax reporting
reporting details are conguration details on
available on the rst- the tax registration for
party tax registration this tax regime for your
record for this tax rst parties
regime
496
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Allow cross regime Option that controls None None Controls whether
compounding whether cross regime this tax regime is
compounding is compounded based on
needed for this tax the tax calculated from
regime another tax regime
Note: Oracle Fusion Tax provides features at the tax regime level to streamline your implementation by
selecting the features that are applicable to the tax regime in scope. You must enable the features to use that
functionality for the tax regime and related taxes.
Related Topics
• Tax Controls and Defaults
• Considerations for Specifying First-Party Tax Prole Options
Inclusive Taxes
Calculating tax on a transaction as inclusive of the line amount is generally a business decision. This decision is based
on the relationship between the transacting parties and the items or taxes involved.
Taxes applicable on a transaction are made inclusive of the item line amount either:
• Manually
497
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
• Automatically
Manual Approach
In the manual approach, you access the calculated tax lines on a transaction and select the Inclusive option. This action
includes the calculated tax amount with the item value.
However, this option is controlled through two factors:
• Privileges are assigned to the users for accessing and editing the calculated tax lines.
• Setup restrictions are applied to edit the Inclusive option on the calculated tax lines.
Automatic Approach
In the automatic approach, you can congure the tax setup and calculate the tax on a transaction as inclusive
of the item line amount. Since the tax legislation and the business relationship between the transacting parties
primarily drive this requirement, the option for conguring the inclusiveness is made available on the tax and tax rate
denition and the third party and legal reporting unit tax proles on the tax registration and general data tabs. The tax
determination process uses a hierarchy approach to evaluate the dened setup and applies the inclusiveness option on
the transaction.
In tax setup, the options to choose for applying the inclusiveness on a transaction are:
• Standard noninclusive handling: This option calculates the taxes as exclusive of the given transaction line
amount.
• Standard inclusive handling: This option calculates the taxes as inclusive of the given transaction line amount.
• Special inclusive handling: This option calculates the taxes as inclusive of the given transaction line amount,
but the calculation methodology diers from the standard inclusive process.
The following table illustrates the calculation methodology used with each of these options when a transaction line
amount is 1000 USD and the applicable tax rate is 10% of the taxable basis amount. For example, line amount:
Standard Noninclusive 1000 USD * 10/100 1000 USD 100 USD 1100 USD
Standard Inclusive 1000 USD * 10/110 909.09 USD 90.91 USD 1000 USD
Special Inclusive 1000 USD * 10/100 900 USD 100 USD 1000 USD
Related Topics
• What happens if I make the transaction line inclusive of tax
• Considerations for Conguring Inclusive Taxes
• How Tax Inclusiveness Hierarchy Is Determined
498
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
The following concepts control how this setup is managed, used, and shared:
Identify a specic rst-party legal entity as a parent rst-party organization. This allows the conguration to be owned
by a specic rst party and shared by other parties. You can then share this setup with another rst-party legal entity or
business unit for their transactions. Use a parent rst-party organization tax conguration to share among a group of
rst-party organizations. However, you still have the tax setup managed by a single rst-party organization.
For global conguration owner, if you're assigned the Create Tax Regime privilege, you have update rights to all tax
conguration data maintained by the global conguration owner.
• Tax
• Tax status
• Tax rate
• Tax recovery rate
• Tax rules
499
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Do this indirectly by adding higher priority rules specic to the subscribing rst-party legal entity or business
unit.
Common conguration For tax processing, the tax determination process uses the shared tax content dened and
maintained by the global conguration owner.
Party-specic conguration The specied rst-party organization denes and maintains its own tax content. For tax
processing, the tax determination process uses only the tax content owned by the specic
rst-party legal entity or business unit.
Common conguration with party This option is similar to the common conguration because it lets you use the tax content
overrides owned by the global conguration owner. However, you can also maintain party-specic
content which is used in preference to the common conguration content. In the absence of
tax content owned by the specic rst-party organization, the tax determination process uses
the tax content owned by the global conguration owner.
Parent rst-party organization with This option is similar to the common conguration with party override subscription with one
party overrides dierence. The tax content here is owned by a specic rst-party legal entity instead of the
global conguration owner.. You can override the specic rst-party setup.
A similar concept is used to dene where you use tax exceptions for a specic tax conguration. The tax subscription
option available for product exceptions is dictated to some extent by the main tax content subscription as follows:
Options Dened for Tax Content Content Subscription Options Available Description
Subscription for Product Exceptions
Common conguration Common conguration For tax processing, the tax determination
process uses tax exceptions dened and
maintained by the global conguration
owner.
Common conguration with party Common conguration For tax processing, the tax determination
overrides process uses tax exceptions dened and
maintained by the global conguration
owner.
Common conguration with party Party-specic conguration The specied rst-party organization
overrides denes and maintains its own tax
500
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Options Dened for Tax Content Content Subscription Options Available Description
Subscription for Product Exceptions
Parent rst-party organization with party Party-specic conguration The specied rst-party organization
overrides denes and maintains its own tax
exceptions. For tax processing, the tax
determination process uses only the tax
exceptions owned by the specic rst-
party organization.
Set up tax conguration options when you create a tax regime or when you create a party tax prole for a rst-party
legal entity or business unit. Both setup ows display and maintain the same party or regime denitions. Specify
eective start and end dates to identify which conguration should be used based on the transaction date. You can
enable the business unit so that Oracle Fusion Tax automatically uses the conguration of the legal entity. Once you
set this option the application records the date it occurred as the start date. This date is used and compared to the
transaction dates to identify if the application uses the legal entity subscription in preference to the subscription of
the business unit. The specic rst-party legal entity that is used is dened by the legal entity associated with the
transaction.
Individual tax partners can oer transaction tax solutions in the following areas:
501
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
• Tax partner can manage the entire tax compliance function from tax returns generation to payment
remiances.
The following table lists cases of customer implementations using tax partner oerings:
However, each individual tax partner is dierent with regard to specic transaction tax solutions they can oer and tax
implementation cases that they can fulll in practice.
You must follow up with an individual tax partner to understand the level of coverage and capabilities of their respective
transaction tax oerings, including any prerequisite conguration.
Using a Tax Partner Content Subscription Versus Oracle Fusion Tax Content
Use the tax content of an external tax partner for the following instances:
• When you need the tax content for a signicant number of tax jurisdictions.
• When you want a tax partner to automatically update the content for statutory changes on a recurring basis.
• When you need to automate the upload of content to minimize user intervention.
You can use the content provided by a tax partner in the following scenarios:
502
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Note: Not all tax partners support both scenarios. Even if an individual tax partner supports a specic
scenario, the level of depth and geographic scope of partner tax content provided varies between individual
tax partners. You must follow up with an individual tax partner to understand the level of coverage and
capabilities of all transaction tax oerings provided, including the tax content.
In both cases, when you subscribe or assign a business unit or legal entity to a tax regime, you must select the
level of tax conguration options that apply in this context. Sharing the tax content prevents the need for duplicate
maintenance with its ineciencies and potential inconsistencies.
Scenario Option
You have a single central corporate Use the common conguration with party override option. This allows a single tax setup to be
tax center responsible for created and maintained by the corporate tax center.
maintenance of tax setup for all legal
entities and business units.
You need strict control over who can Use the common conguration option. By not allowing party override, you restrict the access
maintain the tax content. to the global conguration owner to an authorized user who can maintain all of the tax
content.
You have regional centers Use the parent rst party conguration with party override option. This permits a regional
responsible for tax content. setup with an actual or logical parent legal entity to be created and maintained by each
regional center.
Even if there is no obvious need to share tax conguration, for example, there is only a single rst party legal entity
operating in each tax regime, signicant business events such as takeovers or mergers may mean that there could be
a future need to share content. In this case, the original rst party legal entity can act as the conguration owner and
then any subsequent rst party can subscribe to the rst party's content using the parent rst party conguration with
party override. Alternatively, set up the original tax content using global conguration owner to prepare for any future
business event that requires tax content to be shared.
Changing from Business Unit to Using Tax Conguration at the First Party Legal Entity
If you standardize your tax setup across all business units for a given legal entity, consider conguring and using tax
setup at the legal entity level. Set the Use subscription of the legal entity option on the business unit party tax prole.
Oracle Fusion Tax records the date this occurs and compares it to the transaction date to identify if the legal entity
subscription should be used in preference to the subscription to the business unit subscription.
503
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Note: If the Use subscription of the legal entity option is used on the business unit party tax prole, it is
an irrevocable election. Ensure that this type of conguration approach meets your business needs on a
permanent basis. If you are not sure, you can subscribe or assign the business unit to a tax regime and select
not to set the Use subscription of the legal entity option on the business unit party tax prole. The business
unit subscription approach is more common, but you must evaluate your requirements.
• Congurations dened for the combination of that rst-party organization (business unit or rst-party legal
entity)
• Tax regime derived from the addresses or from the tax classication codes used on the transaction
• Common conguration
• Party-specic conguration
• Common conguration with party overrides
• Parent rst-party organization with party overrides
Common conguration • The tax determination process uses only the tax content owned by the global
conguration owner.
• If you manually override tax information on the transaction, only the tax content owned
by the global conguration owner is displayed in the list of valid values available.
Party-specic conguration • The tax determination process uses only the tax content owned by the rst-party
organization, business unit or st party legal entity, for whom the transaction is being
entered.
• If you manually override tax information on the transaction, only the tax content owned
by the rst-party organization is displayed in the list of valid values available.
504
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Note: For the rst-party organization it can be the business unit owning
the tax content or the rst-party legal entity-owned setup depending on the
specic subscription being used.
Common conguration with party • The tax determination process uses any tax content owned by the rst party for whom
overrides the transaction is being entered. In the absence of tax content owned by that rst-
party organization, the tax determination process uses tax content owned by the global
conguration owner.
• If you manually override tax information on the transaction, both the override tax
content owned by the specic rst party and the tax content owned by the global
conguration owner that you haven't overridden are displayed in the list of valid values
available.
Parent rst-party organization with • The tax determination process uses any tax content owned by the rst party for whom
party overrides the transaction is being entered. In the absence of tax content owned by the rst-party
organization, the tax determination process uses tax content owned by the parent rst-
party organization.
• If you manually override tax information on the transaction, both the override tax
content owned by the specic rst party and the tax content owned by the designated
parent rst-party organization that you haven't overridden are displayed in the list of
valid values available.
If you are using product exceptions, those exceptions are applied to the transactions as shown in the following table:
Common conguration The tax determination process uses only the tax exceptions dened and maintained by the
global conguration owner.
Party-specic conguration The tax determination process uses only the tax exceptions owned by the specic rst-party
organization
505
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Each country has a single rst-party legal entity with a single business unit, except for:
• Countries with the regional corporate centers have a rst-party legal entity and business unit for each corporate
center.
• Sales, marketing, and manufacturing organization have a rst-party legal entity and business unit.
Create tax regimes for each country and the appropriate tax conguration options.
Prerequisites
To create the appropriate tax congurations, you must set up the following:
EMEA LE UK
GB LE UK
FR LE FR
DE LE DE
APAC LE AU
AU LE AU
SI LE SI
NZ LE NZ
NAM LE US
US LE US
CA LE CA
2. The sales, marketing, and manufacturing organization's business unit uses the tax conguration of the legal
entity.
3. The relevant tax regimes for each country's tax include:
506
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
NAM
United States
US SALES TAX
◦ US STATE SALES TAX
◦ US COUNTY SALES
TAX
◦ US CITY SALES TAX
NAM
Canada
CA HST and GST
◦ CA HST
◦ CA GST
Field Value
GB VAT
Tax Regime Code
Party-specic conguration
Conguration for Taxes and Rules
Party-specic conguration
Conguration for Product
Exceptions
Blank
Parent First-Party Organization
01-Jan-01
Eective Start Date
507
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
2. Select GB LE in the Legal Entity eld. In the Conguration Options tab enter:
Field Value
GB VAT
Tax Regime Code
EMEA LE
Parent First-Party Organization
01-Jan-01
Eective Start Date
Field Value
FR VAT
Tax Regime Code
EMEA LE
Parent First-Party Organization
01-Jan-01
Eective Start Date
Field Value
DE VAT
Tax Regime Code
508
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Field Value
EMEA LE
Parent First-Party Organization
01-Jan-01
Eective Start Date
Field Value
AU GST
Tax Regime Code
Party-specic conguration
Conguration for Taxes and Rules
Blank
Parent First-Party Organization
01-Jan-01
Eective Start Date
Field Value
AU GST
Tax Regime Code
APAC LE
Parent First-Party Organization
01-Jan-01
Eective Start Date
509
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Field Value
Field Value
SI VAT
Tax Regime Code
APAC LE
Parent First-Party Organization
01-Jan-01
Eective Start Date
Field Value
NZ VAT
Tax Regime Code
APAC LE
Parent First-Party Organization
01-Jan-01
Eective Start Date
510
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Field Value
US SALES TAX
Tax Regime Code
Party-specic conguration
Conguration for Taxes and Rules
Party-specic conguration
Conguration for Product
Exceptions
Blank
Parent First-Party Organization
01-Jan-01
Eective Start Date
Field Value
US SALES TAX
Tax Regime Code
NAM LE
Parent First-Party Organization
01-Jan-01
Eective Start Date
Field Value
511
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Field Value
NAM LE
Parent First-Party Organization
01-Jan-01
Eective Start Date
When the external tax partner integration is set up, the external tax partner integration service is called to provide tax
calculations for the following procurement ows where the Oracle Fusion tax engine is usually called.
Related Topics
• Overview of External Tax Partner Integrations
• Oracle Fusion Tax Conguration for External Tax Partner Calculation
• Example of Creating Tax Setup Using Tax Partner Content in the Tax Conguration Workbook
512
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
In some countries, tax authority guidelines require transaction taxes to be calculated and tracked as part of the pricing
in your transactions. You can enable and set up the Inclusive Tax Handling in Procure to Pay Flows feature to
implement inclusive tax calculation and tracking on purchase orders processed in Oracle Enterprise Resource Planning
Cloud.
A procurement-specic tax setup worth noting is to enable the inclusive tax option for a business unit's or legal entity's
purchase orders. To enable the option, in the Setup and Maintenance work area, use Manage Conguration Owner Tax
Options in the Transaction Tax functional area.
1. On the Manage Conguration Owner Tax options page, search using these criteria:
Related Topics
• How You View Inclusive and Exclusive Tax Information in Purchase Orders
• Congure Oerings
• Update Existing Setup Data
513
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
tax partners for transaction tax calculation processing. You can use either Oracle Tax or a partner tax application to
calculate transaction taxes. All you have to know is the specic depth and scope of the external tax partner's oerings.
Payment Terms
Payment Terms
Payment terms are used to automatically create invoice installments. You can dene payment terms to create multiple
installments and multiple levels of discounts.
Payment terms consist of one or more lines, each of which creates one invoice installment. When you dene a payment
term, you can specify either percentages or xed amounts. A payment term line can have up to three discounts. Each
line and corresponding installment have a due date and up to three discount dates. Each line and corresponding
installment also have due or discount amounts. You can assign a payment term to one or more sets to share that
payment term across business units.
514
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Tip: If you change the payment terms on an invoice, the installments are automatically recalculated and you
must reenter any manual adjustments made previously.
515
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
invoice with a terms date of January 10, the installment is due January 15. If the terms date is January 12
and Months Ahead is set to 1, the installment is due March 15.
Note: Only due dates, not discount dates, can be based on a calendar.
Yes Yes
Invoice
Related Topics
• How Invoice Installments Are Recalculated
• What's a Payables calendar
• Payment Terms and Reference Data Sharing
• Reference Data Sets and Sharing Methods
516
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
1. In the Setup and Maintenance work area, access the Manage Payment Terms task in the Procurement
Foundation functional area.
2. On the Manage Payment Terms page, click the Create icon.
3. On the Create Payment Terms page, enter a Name. For example, ABC Net 90.
4. Enter a Description. For example, Net in 90 days. Discounts for net in 30 or 60 days..
5. Enter a From Date and To Date.
6. Click the Add icon for Installments.
7. In the Installments table enter your payment due terms: For example, for Due enter 100, and for Days enter 90.
8. In the Discount region under the First Discount table header enter your term discount: For example, for
Discount enter 10, and for Days enter 30.
9. In the Discount region under the Second Discount table header enter your term discount: For example, for
Discount enter 5, and for Days enter 60.
10. In the Set Assignments table click the Add icon to create a new row.
11. Enter your Set Code. For example, COMMON.
12. Click Save and Close.
Related Topics
• Update Existing Setup Data
Units of Measure
How Units of Measure, Unit of Measure Classes, and Base Units of
Measure Relate to Each Other
Units of measure, unit of measure classes, and base units of measure are used for tracking, moving, storing, and
counting items.
517
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
The following graphic shows that the unit of measure class named 'Quantity' contains the units of measure: Box of 8,
Box of 4, and Each. The unit of measure named Each is assigned as the base unit of measure.
Base
UOM
=
Each
Units of Measure
Units of measure are used by a variety of functions and transactions to express the quantity of items. Each unit of
measure you dene must belong to a unit of measure class.
518
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Scenario
This table lists examples of unit of measure classes, the units of measure in each unit of measure class, and base unit of
measure. Note that the base unit of measure is the smallest unit of measure in its unit of measure class.
Scenario
This table lists examples of unit of measure classes, one unit of measure included in each class, the base unit of
measure for the unit of measure class, and the conversion factor dened for the unit of measure.
519
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Unit of Measure Class Unit of Measure Base Unit of Measure Conversion Factor
In the rst example, you're converting a unit of measure called dozen into a base unit of measure called each. The
conversion factor tells the application that for each dozen, there are 12 of the base unit each. For example, if you had 48
each of eggs, with a conversion factor of 12, you would get 4 dozen eggs.
You cannot create the interclass and intraclass conversions when building the standard conversions. The UOM must be
dened prior to creating Items. Items must be dened prior to creating interclass or intraclass conversions.
520
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Using the specied employee matching rule, the application automatically enters the transaction data for the new
corporate card and associates it with the applicable employee. If the employee matching rule fails to identify a match,
the application leaves the corporate card unassigned.
Tip: To reduce or eliminate manual eort, automatic corporate card creation is recommended.
The application searches and identies an employee in the business unit of your company account.
• Company account information on the transaction matches the company account information in the application.
The application searches and doesn't identify an employee in the business unit of your company account.
If the Perform employee matching across all business units check box is selected, the application searches
all other business units and identies an employee match.
• The company account in the application has no information, such as company account number, billing control
account, or card issuer number.
If no setup data exists, the application matches across business units, identies the employee and the
employee's business unit, and associates the corporate card to a company account in the same business unit.
521
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Note: Manual creation of corporate cards is the exception, rather than the rule. Corporate cards are company
account-specic. For example, if an employee transfers to another organization within your company and
the organization belongs to another company account, you must create the corporate card again with the
applicable company account name.
Related Topics
• Simplied Conguration for MasterCard CDF3 and Visa VCF4 Files
• How can I congure corporate card issuers
• What's a corporate card program
Default Distributions
Default distributions are used to dene accounts for payables transaction accounting.
Note: You can also specify some default distributions for a supplier on the Edit Site page.
522
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Oset Segments
If you enter invoices for expenses or asset purchases with more than one primary balancing segment value, consider
using automatic osets. Automatic osets balance accounting entries for Oracle Fusion Payables transactions. If you
don't use automatic osets, an invoice transaction has a single liability accounting entry and a payment transaction has
a single cash accounting entry.
Currency Conversion
This table describes the options you can set for currency conversion.
Option Description
Require conversion rate entry If enabled, you must provide a conversion rate whenever you enter an invoice or a payment in
a currency other than the ledger currency. If you maintain daily rates, the rate is automatically
supplied based on the date and rate type that you enter. If daily rates don't exist for that date
and rate type, you can't enter or save the transaction. If the conversion rate type is User,
then you must enter a conversion rate. You can't create accounting entries for, or pay foreign
currency invoices without conversion rates.
If you don't enable this option, you can enter conversion rates manually on invoices and
payments, or submit the Apply Missing Conversion Rates process. When you create a bills
payable document, you must still provide a maturity rate, rate type, and date.
This seing provides the default conversion rate type when you enter invoices or create
Conversion rate type payments. You can change the conversion rate type at invoice entry or payment creation time.
These distributions represent the default realized gain and loss accounts for payments
Realized Gain or Loss Distributions from each of your bank accounts. If the conversion rate changes between invoice entry and
payment time, the realized gain or loss is automatically calculated and recorded to these
accounts.
Expense Accruals
Determine when to accrue for expense items.
Self-Billed Invoices
This table lists the options for self-billed invoices.
Option Description
You can enable gapless, that's, no breaks in numbering, invoice number generation for your
Gapless invoice numbering buying organization during pay on receipt processing. You can enable gapless numbering for
the entire business unit with this seing or limit it to a supplier site.
A unique identier that's included in the invoice number created by the pay on receipt process
Buying Company Identier and in the debit memo number from returned receipts.
523
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Option Description
If your company operates in a member state of the European Union, select the country.
VAT Registration Member State
If your company operates in a member state of the European Union, enter the value-added tax
VAT Registration Number (VAT) registration number for your organization.
Enter the bill-to location to provide default values. The application uses the bill-to location to
Bill-to Location derive legal entity information.
Note: You can use the Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheet
task to automate common options setup.
Related Topics
• Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheets
• How Charts of Accounts, Ledgers, Legal Entities, and Business Units Are Created Using Spreadsheets
• Default Distributions
• Automatic Osets
• Considerations for Accruing Expense Items
In the Setup and Maintenance work area, in the Procurement oering, use the Manage Procurement Document
Numbering task in the Procurement Foundation functional are to dene procurement document numbering.
Determinant Type
Document numbers are typically based on the sold-to legal entity, the procurement business unit, or the requisition
business unit. On the Manage Procurement Document Numbering page this is the Determinant Type.
The determinant type is xed for a given document type. This table lists procurement document types and their
respective determinant types.
524
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Requisition Requisitioning BU
Negotiation Procurement BU
Assessment Procurement BU
Initiative Procurement BU
Qualication Procurement BU
Determinant Value
You can dene a unique document number sequence for a combination of document type, determinant type and the
determinant value, where determinant value represents a specic legal entity or business unit.
Related Topics
• Update Existing Setup Data
Note: A procurement category hierarchy isn't the same entity as a catalog category hierarchy. The structure
of the two can be the same, but don't have to be the same. Each hierarchy can be congured dierently
to meet the needs of your organization. Also, a procurement category hierarchy isn't the same entity as a
supplier products and services hierarchy.
525
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
In the Setup and Maintenance work area, use the Manage Procurement Category Hierarchy task in the Procurement
Foundation functional area to create a procurement category hierarchy.
1. On the Manage Procurement Category Hierarchy page, you can perform these actions to build a hierarchy:
Related Topics
• Update Existing Setup Data
526
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
For example, this graphic shows four levels of categories for IT level spend.
Information
Level 1 Technology
Level 2 Hardware
Software
Level 3 Desktop
Laptop
Level 4 Notebooks
Standard
Laptops
If you have approval policies that apply to all hardware categories, you need only one rule condition applied to
the highest hardware category level in the hierarchy. For example, you might set up an approval rule where if the
procurement category hierarchy equals level 2 hardware, then route a requisition to the information technology
approval group for approvals. This way, you don't need separate approval policies for the lower levels (notebooks
and standard laptops). In this example, any changes you make to the categories below hardware wouldn't aect the
approval policy rule because everything rolls up to hardware.
You can use procurement category hierarchies for approvals of requisitions, purchasing documents, and negotiation
approval tasks.
You can use a predened, delivered mapping set to derive natural account segments based on the requisitioning
business unit and procurement category hierarchy level 1.
527
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Do you want to set up an approval rule for requisitions, purchase Set up an approval rule for purchase orders.
orders or negotiations?
Do you have an existing approval group for your IT organization? Assume an approval group named IT Approvals exists.
Do you have an existing procurement category hierarchy to use? Assume the example procurement category hierarchy is set up
and available for use..
What procurement category hierarchy level do you want to use for In this example, use the level 2 category Information Technology.
the rule?
528
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
This gure illustrates the structure of the example procurement category hierarchy for information technology
purchases.
Root
Indirect
(Level 1)
...
Note: You can create more than 10 levels under the root category of a procurement category hierarchy. You
can only set up approvals based on the top 10 levels.
529
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
1. A procurement category hierarchy has been created in the Setup and Maintenance work area using the Manage
Procurement Category Hierarchy task in the Procurement Foundation functional area.
2. An IT approval group has been created in the Setup and Maintenance work area using the Manage Approval
Groups task in the Approval Management functional area.
Field Value
Parallel
Routing
3. Click the Edit Rules buon to open the Edit Approval Rules page.
4. In the Rules section, Actions list, select Create. Give the rule a name such as IT Approvals.
5. In the IT Approvals Details section add a condition stating "Procurement Category Hierarchy Level 2 Equals
Information Technology." Complete the elds as shown in this table.
Field Value
Equals
Operator
Information Technology
Value
6. In the Actions section, click the Add Action buon. Complete the elds as shown in this table.
Field Value
Approval Required
Action Type
IT Approval Group
Route Using
7. Click Save.
530
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
Use a procurement category hierarchy having the level 2 category, Information Technology, to set up an account
mapping set for purchases of computer hardware. This table summarizes key decisions to consider, and the decisions
made for this scenario.
Do you have an existing procurement category hierarchy to use? Assume the example hierarchy exists.
What procurement category hierarchy level do you want to use for In this example use the level 2 category Information Technology.
the mapping?
Do you have an account set up that you can use in the mapping? In this example assume the account Purchasing Computer
Hardware exists.
Does your organization have an account combination in the Chart In this example assume that it does.
of Accounts that you can use in the mapping?
531
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
This gure illustrates the structure of the example procurement category hierarchy.
Root
Indirect
(Level 1)
...
Note: You can create more than 10 levels of categories under the root category. You can only set up account
mapping sets based on the top 10 levels.
1. A procurement category hierarchy has been created, in the Setup and Maintenance work area using the
Manage Procurement Category Hierarchy setup task in the Procurement Foundation functional area.
532
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
2. Accounts have been created in the Chart of Accounts, using the Dene Chart of Accounts task.
3. Account rules have been created, using the Manage Account Rules setup task.
Field Value
HIERARCHY_ MAPPING
Short Name
Account Combination
Output Type
Field Value
Purchasing
Subledger Application
6. On the Create Mapping Set page, in the Input Sources section, the Number eld value is populated with 1. The
Source value is Procurement Category Hierarchy Level 2.
7. In the Chart of Accounts section, click the Add icon.
8. In the Chart of Accounts eld, select an account from the list of values. For example, Purchasing Computer
Hardware.
9. In the Mapping section, click the Add icon. Complete the elds as shown in this table.
Field Value
Input Value Enter the exact category name. For example, Information Technology.
Output Value
Click the Output icon. In the dialog enter the chart of accounts values for your account
combination: Company, Department, Account, Sub-Account, and Product.
533
Oracle Procurement Cloud Chapter 17
Implementing Procurement Common Procurement Conguration
534
Oracle Procurement Cloud Chapter 18
Implementing Procurement Purchasing Conguration
18 Purchasing Conguration
This table provides an example of a line with the line type Goods.
This table provides an example of a xed price-based line with the line type of Fixed Price Services.
535
Oracle Procurement Cloud Chapter 18
Implementing Procurement Purchasing Conguration
When you create a purchasing document using a document style, disabled features are hidden. For example, if price
breaks aren't allowed on an agreement document style then agreements using this style won't display the price break
region.
• Status is Active.
• Purchase Basis is Goods.
• Line Types is All. (For Goods only.)
• The Outside Processing value is enabled.
◦ The Congurations and Consignment Terms values aren't enabled. These three values are mutually
exclusive, only one can be enabled in a document style at a time.
• Display names are enabled for Outside Processing Purchase Order, Outside Processing Blanket Agreement, and
Outside Processing Contract Agreement.
◦ For Outside Processing Blanket Agreement the Price Breaks Allowed value is set to Yes.
You can't change the delivered Outside Processing Style. If needed, you can create a new document style with a
dierent set of values for outside processing.
Related Topics
• Update Existing Setup Data
536
Oracle Procurement Cloud Chapter 18
Implementing Procurement Purchasing Conguration
1. Enter a name and description for the document style, and set the status to Active.
2. Select the Purchase Bases: Goods, Services or Both.
3. Set the Outside Processing Enabled option to Yes.
The Outside Processing Enabled, Consignment Terms Enabled, and Conguration Ordering Enabled options
are mutually exclusive. You can't enable more than one of them in a document style.
4. Set the Line Types: All or Specied.
5. In the Purchase Order section enter the Display Name.
6. In the Blanket Purchase Agreement and Contract Purchase Agreement sections, you can optionally enable
the document style for those purchasing document types. Also enter display names for them. For blanket
agreements you can also dene whether or not price breaks are allowed.
For document styles having outside processing enabled, you can't disable the Outside Processing Enabled option if any
purchasing document is using the style.
537
Oracle Procurement Cloud Chapter 18
Implementing Procurement Purchasing Conguration
You can use the Congure Procurement Business Function task to select a document layout for each purchasing
document type. You can nd the task In the Setup and Maintenance work area, Procurement Foundation functional
area.
Related Topics
• Purchasing Document Report
• Update Existing Setup Data
Report Templates
Two predened purchasing document report templates are delivered: Purchase Order PDF Report and Purchase
Agreement PDF Report.
The reports have two main elements:
• Procurement data source.
• Report layout template.
Obtain the delivered report templates in Oracle BI Publisher, using the following path: Catalog/Shared Folders/
Procurement.
You can congure new versions of the delivered reports by adding elds to the report layout, to include reporting
aributes not shown in the delivered versions, such as:
• Aributes from the delivered data model.
538
Oracle Procurement Cloud Chapter 18
Implementing Procurement Purchasing Conguration
• Additional aributes from tables not available in the delivered data model.
Data Models
Two data models are delivered, one for each purchasing document report: Purchase Order Data Model, and Purchase
Agreement Data Model. Obtain them from Oracle BI Publisher, using the following path: Catalog/Shared Folders/
Procurement.
Use the data models to:
a. Obtain the delivered data model and report template appropriate to the purchasing document type.
b. Make a copy of them to congure into a new version, preserving the delivered versions unchanged.
c. Edit the data model and export the XML.
d. Download the report template.
2. Use Oracle BI Publisher Desktop, in Microsoft Word, to:
a. Upload the modied report template to the catalog, making it available to other users.
The modied report template displays in the Congure Procurement Business Function task. You can nd the task in
the Setup and Maintenance work area, Procurement Foundation functional area. For each aected business unit, you
can associate the modied report template with the appropriate purchasing document type.
For more information refer to the white paper available on My Oracle Support (MOS): Document Publishing and
Communication in Oracle Fusion Purchasing (document ID 1610339.1). The document:
• Provides detailed procedures for using Oracle BI Publisher to copy and congure reports.
• Includes a copy of the delivered XML data model.
Related Topics
• Purchasing Document Report
539
Oracle Procurement Cloud Chapter 18
Implementing Procurement Purchasing Conguration
The application assigns a buyer to a requisition line only if a suggested buyer isn't provided by the requester. The
application assigns a buyer using the following steps, in order of precedence:
1. Evaluate the buyer assignment rules, as set up in the Manage Buyer Assignment Rules task. Find the task in the
Setup and Maintenance work area, in the Purchasing Foundation functional area.
2. Use the default buyer from the item denition in the deliver-to organization of the requisition line. Find the
requisition line on the Process Requisitions page, in the Purchase Orders or Purchase Agreements work area.
3. Use the default buyer from the Congure Procurement Business Function task. Find the task in the Setup and
Maintenance work area, Procurement Foundation functional area.
If the Use Same Buyer for all Lines in a Requisition prole option is enabled in the application, the buyer assigned to
the rst line will also be assigned to all other lines.
Dene buyer assignment rules using the Manage Buyer Assignment Rules task, in the Setup and Maintenance work
area, Purchasing Foundation functional area.
These are the choices to consider when creating a buyer assignment rule:
• Rule Sequence
• Requisitioning BU
• Commodity
• Deliver-to Organization
• Project
• Supplier
• Noncatalog Request
• Exceeds Line Amount
• Procurement BU
• Buyer
Note: A value for rule sequence, procurement business unit, and buyer are required to create a rule. In
addition, either a requisitioning business unit, or a commodity, or both are required.
Rule Sequence
Specify a number to control the sequence of evaluation of the rules.
• Rules are evaluated in ascending order of the sequence number.
• The sequence numbers have to be rational numbers (supporting decimals).
• No two rules can have the same sequence number.
Commodity
Enter a Commodity that can be either a category or a group of categories. Dene commodity-based rules at higher
levels to avoid creating rules for each category.
540
Oracle Procurement Cloud Chapter 18
Implementing Procurement Purchasing Conguration
Deliver-to Organization
Identify the deliver-to organization of the requisition line. This determines the item denition used to derive the default
buyer.
Project
Specify the project identication, which the application matches to the requisition distribution. A requisition line is
considered a match only if all the distributions have the same project.
Supplier
Enter the supplier, which the application matches to the requisition line.
Noncatalog Request
Indicate whether or not the requisition line is for a noncatalog request.
Related Topics
• Update Existing Setup Data
a. View the overall outcome for your upload in the Status column of the spreadsheet.
b. View highlighted spreadsheet cells for any errors.
5. If there are errors, correct the errors in the spreadsheet and upload again.
Related Topics
• Guidelines for Using Desktop Integrated Excel Workbooks
• Update Existing Setup Data
541
Oracle Procurement Cloud Chapter 18
Implementing Procurement Purchasing Conguration
1. In the Setup and Maintenance work area, access the Manage Purchasing Prole Options task in the
Procurement Foundation functional area.
2. On the Manage Purchasing Prole Options page, in the list of names click the prole option code
PO_ASL_VALIDATION_FOR_BPA.
3. In the Search Results: Prole Options section, note the prole option display name is Approved Supplier
Validation for Blanket Purchase Agreements.
4. In the PO_ASL_VALIDATION_FOR_BPA: Prole Values section, select a Prole Value: Yes or No. The default
value is Yes.
◦ Yes: Blanket purchase agreements are validated to prevent submission unless the agreement supplier
has approved status for the agreement line items that are marked to use only approved suppliers.
◦ No: Blanket purchase agreements aren't validated on submission to ensure the agreement supplier has
approved status for the agreement line items that are marked to use only approved suppliers.
5. Click Save.
Related Topics
• Set Prole Option Values
1. In the Setup and Maintenance work area, access the Manage Purchasing Prole Options task in the
Procurement Foundation functional area.
2. On the Manage Purchasing Prole Options page, in the list of names click the prole option code
PO_REQUESTED_DELIVERY_DATE_VALIDATION.
3. In the Search Results: Prole Options section, note the prole option display name is Requested Delivery Date
Validation Against Agreement Eective Dates.
4. In the PO_REQUESTED_DELIVERY_DATE_VALIDATION: Prole Values section, select a Prole Value: Yes or
No. The default value is Yes.
◦ Yes: If a Requested Delivery Date is provided on an order that's sourced against a purchase agreement,
there is validation on purchase order submission that the date is within the agreement start and end
dates.
542
Oracle Procurement Cloud Chapter 18
Implementing Procurement Purchasing Conguration
◦ No: If a Requested Delivery Date is provided on an order that's sourced against a purchase agreement,
there is no validation on purchase order submission that the date is within the agreement start and end
dates.
5. Click Save.
Related Topics
• Set Prole Option Values
How can I automatically calculate blanket purchase order requested delivery dates?
Opt in to the Automatically Determine Requested Delivery Date Using Agreed Lead Time feature to enable requested
delivery date calculation. In the blanket agreement, set the Lead Time Days line aribute. When requisitions are
converted to orders, the requested delivery date on the requisition line is compared to the current date plus the Lead
Time Days on the agreement line. The later date is used for the requested delivery date on the order.
Cumulative Pricing
Select Cumulative Pricing if you want to choose the price break by adding the current release shipment quantity to the
total quantity already released against the purchase agreement line.
Note: Cumulative Pricing can't be used with global agreements.
Non-Cumulative Pricing
Select Non-Cumulative Pricing if you want to choose the price break by using the individual release shipment quantity
of the agreement line.
543
Oracle Procurement Cloud Chapter 18
Implementing Procurement Purchasing Conguration
Related Topics
• Update Existing Setup Data
Note: The receipt close tolerance percentage must be set in combination with this seing.
Accepted
Ordered goods have passed inspection and are ready for use.
Delivered
Ordered goods have been delivered and are ready for use.
Received
Ordered goods have been received and are ready for use.
Two-Way
Purchase order and invoice quantities must match within tolerance before the corresponding invoice can be paid.
544
Oracle Procurement Cloud Chapter 18
Implementing Procurement Purchasing Conguration
Three-Way
Purchase order, receipt, and invoice quantities must match within tolerance before the corresponding invoice can be
paid.
Four-Way
Purchase order, receipt, accepted quantities from inspection, and invoice quantities must match within tolerance before
the corresponding invoice can be paid.
What Happens When You Select Group Requisition Lines Check Box
This option determines whether each requisition line being fullled in the order will have its own order line or can be
combined with other requisition lines. Select this check box to group requisition lines into the same purchase order line.
The application will try to group requisition lines that share the same:
• Line type
• Item, item revision, item description, supplier item number, and supplier conguration ID
• Category
• UOM
• Source agreement and source agreement line
545
Oracle Procurement Cloud Chapter 18
Implementing Procurement Purchasing Conguration
• Requested delivery date (used optionally if the Use requested delivery date check box is selected)
• Ship-to Organization and Location (used optionally if the Use ship-to organization and location is selected)
• Negotiated seing
• Work order product
For all requisition lines grouped into the same purchase order line, the application will further group these lines into
schedules if they share the same:
• Requested delivery date, Ship-to Location, and Ship-to Organization
• Destination type
Standard terms and conditions are included with each purchasing document sent to the supplier.
Terms
Purchasing terms commonly indicate the buying organization's rules and expectations as related to pricing and
payment.
Conditions
Purchasing conditions typically describe the buying organization's rules related to but not limited to delivery,
acceptance of delivery, cancellations, additions to the approved order, and general behavior of the supplier during the
course of the transaction.
Languages
Indicate that this set of terms or conditions are not to be made available in all installed languages by selecting the check
box: Disable terms and conditions for all languages.
For example, with a receipt close tolerance percent of 99 with a quantity ordered of 100 and a closing point of receipt
the schedule would automatically be closed for receiving when 1 of the 100 are received.
546
Oracle Procurement Cloud Chapter 18
Implementing Procurement Purchasing Conguration
Related Topics
• What's a layout template
Requisitioning Section
Default Deliver-to Organization
The default organization is used as the deliver-to organization for a requisition line if it's a global location. This
organization is used to derive the list of item master items that are accessible to the user when creating a requisition for
the requisitioning BU.
Line Type
Line Type species the default line type to be used for requisition lines created for the requisitioning BU. Line Type can
be modied.
One-Time Location
The One-Time Location is the location code to be defaulted as the deliver-to location for the requisition line when the
requester species an unstructured one-time delivery address on a requisition. Note that this value isn't used if the
structured one-time delivery address feature is enabled.
The location specied must be a global location that's enabled for the requisitioning BU.
The Import Requisition process can be used to import requisitions from other Oracle or non-Oracle applications. On
import, requisition lines are grouped rst by requisition header number, then by the provided Group Code, then by the
value set in the Group-by input parameter (None, Buyer, Category, Item, Location, or Supplier). The specied aribute
is used as the default value for Group-by. All remaining requisition lines that haven't yet been assigned a requisition
number will be grouped together under the same requisition.
Select Allow one-time addresses to allow requesters to specify a unique delivery address not aached to any congured
location. One-time addresses are entered into a free-form eld unless the structured one-time delivery addresses
547
Oracle Procurement Cloud Chapter 18
Implementing Procurement Purchasing Conguration
feature is enabled for Procurement and is enabled for the requisitioning BU. In that case, the one-time address is
captured and validated in a set of elds determined by country.
Administrators can enable the feature on the Edit Features: Self Service Procurement page by selecting Capture One-
Time Address in Structured Format. See Conguring Oerings: Procedure for more information.
Reapproval required for changes made during an active approval process is applicable when allowing approvers to
modify a requisition when it's routed for approval. It controls whether the requisition must be sent back for reapproval
when the approver submits the modied requisition.
When selected, the Generate Orders program runs immediately after the requisition import process is complete.
When creating a requisition that includes internal transfer items, the source of supply can be modied.
When this is selected, availability information from each supply source for the transfer item is provided in the Select
Supply Source dialog, accessed when Select Source is clicked for a transfer requisition line.
You can dene additional aributes of a requisition at the header, line, and distribution level using descriptive ex-
elds. Specifying the context value pulls in the associated descriptive ex-elds when the user enters the requisition.
Purchasing Section
Default Procurement BU
A requisitioning BU can be served by multiple procurement business units. If a procurement BU can't be determined
based on information on the requisition line, the Default Procurement BU is used to process all requisition lines.
The Price Change Tolerance is applicable when there is a price change on the purchase order line associated with a
requisition line. If the value is null, no checks will be performed. If the value is a valid numeric value, then any changes
made to the price on the purchase order line must be within the tolerance percentage value, or the purchase order can't
be submied. The tolerance can be specied using the tolerance percentage or tolerance amount. The more restricting
of the two tolerances will take precedence if both are specied.
Ship-to Location
When the purchase order can't derive a ship-to location, the specied Ship-To on the Requisitioning BU is defaulted.
Cancel Unfullled Demand controls whether a backing requisition should be canceled when there is purchase order
cancellation.
548
Oracle Procurement Cloud Chapter 18
Implementing Procurement Purchasing Conguration
Options are:
• Always: When canceling the purchase order, Oracle Fusion Purchasing also cancels the requisition.
• Never: When canceling the purchase order, Oracle Fusion Purchasing doesn't cancel the requisition, therefore
it's available for inclusion on another purchase order.
• Optional: When canceling the purchase order, the buyer is given the option to cancel the requisition.
Control if a purchase order can contain ship-to organizations belonging to dierent legal entities.
If a requisition doesn't have an agreement specied, Allow requester-to-agreement UOM conversion is used to specify
whether Requisition UOMs can be converted to Agreement UOMs during agreement sourcing. Checking this box
indicates that agreements that meet the sourcing criteria, but have Agreement Line UOMs dierent from Requisition
Line UOMs, can be considered during agreement sourcing. If the box is left unchecked, such agreements won't be
considered.
Related Topics
• Overview of Descriptive Flexelds
549
Oracle Procurement Cloud Chapter 18
Implementing Procurement Purchasing Conguration
• Supplier Administrator
• Supplier Manager
• Supplier Qualication
They have procurement job responsibilities in the buying organization, such as creating purchase agreements,
purchase orders, and related procurement functions. You must set up these users as procurement agents for them to
manage procurement documents and perform other procurement actions.
Procurement Agents
Use the Manage Procurement Agents task to manage procurement agents, including dening an agent's access to
procurement functionality within a procurement business unit.
Find the task in the Procurement Foundation and Payables functional areas.
The following predened procurement roles are controlled by procurement agent access conguration:
• Buyer
• Catalog Administrator
• Category Manager
• Procurement Contracts Administrator
• Procurement Manager
• Supplier Administrator
• Supplier Manager
• Supplier Qualication
Procurement BU
Assign the agent to one or more procurement business units (BU).
Action
Enable the agent with access to one or more procurement actions for each procurement business unit.
• Manage Requisitions: Enable access to purchase requisitions.
• Manage Purchase Orders: Enable access to purchase orders.
• Manage Purchase Agreements: Enable access to blanket purchase agreements and contract agreements.
• Manage Negotiations: Enable access to Sourcing negotiations, if implemented by your organization.
• Manage Sourcing Programs: Enable access to track and manage sourcing programs.
• Manage Catalog Content: Enable access to catalog content. This includes local catalogs, punchout catalogs,
content zones, smart forms, information templates, and collaborative authoring.
550
Oracle Procurement Cloud Chapter 18
Implementing Procurement Purchasing Conguration
To enable the buyer managed transportation seing for a business unit, use the Congure Procurement Business
function task.
1. In the Setup and Maintenance work area, in the Procurement Foundation functional area, access the Congure
Procurement Business Function task.
2. On the Specify Procurement BU dialog, select the Procurement BU, and click OK.
3. On the Congure Procurement Business Function page's Main tab, General section, select the Buyer managed
transportation check box.
551
Oracle Procurement Cloud Chapter 18
Implementing Procurement Purchasing Conguration
4. In the Purchasing section, you have the option to select the Default promised date from requested date
check box. When selected, the buyer's requested date is used to populate the promised date eld, in purchasing
transactions for the business unit.
5. Click Save.
• Indicates your buying organization's intent to manage transportation for purchasing transactions for the site.
• Enables default action for the selection of the seing in procurement transactions for the site.
To enable the buyer managed transportation seing for a supplier site, in the Setup and Maintenance work area,
Suppliers functional area, use the Manage suppliers task. On the Edit Site page, Purchasing tab, Buyer Managed
Transportation drop-down list, select Yes and then save your change.
1. In the Setup and Maintenance work area, in the Suppliers functional area, access the Manage Transit Times
task.
2. On the Manage Transit Times page, set up transit information for the origin and destination locations.
Related Topics
• Buyer Managed Transportation in Procurement
• Congure Oerings
• Update Existing Setup Data
552
Oracle Procurement Cloud Chapter 19
Implementing Procurement Self Service Procurement Conguration
Information templates are available to the user if the items or request forms that the information templates are
associated with are available to the preparer.
Procurement catalog administrators can dene a unique information template name so they're easily identiable in
a request form. Information template header information provides users the ability to specify a non-unique Display
Name, while creating information templates with unique information template names. For example, more than one
procurement BU can maintain information templates to collect business card information. The same Display Name,
Business card information, can be used on these information templates to indicate the purpose of these templates
when displayed in Oracle Fusion Self Service Procurement. Procurement Catalog Administrators can also dene an
information template section description or instruction text providing users with specic instructions on how to ll out
the form.
Information templates can only be deleted if they're not referenced. An information template is considered referenced
if it's applied on any requisition lines, whether in completed or incomplete state. This is to prevent deletion of an
information template that's currently in use.
Once an information template is deleted, it's no longer returned on the Manage Information Templates page.
Aributes rst need to be set up in the Descriptive Flexelds application, and the catalog administrator species the
descriptive exeld context on the Create and Edit Information Template page to apply the list of aributes.
553
Oracle Procurement Cloud Chapter 19
Implementing Procurement Self Service Procurement Conguration
For example, the catalog administrator set up a context Business Cards Marketing, with the following context sensitive
elds:
• Job Title
• Organization
• Oce Location
When creating an information template, the catalog administrator can then specify in the Aribute List eld the context
Business Cards Marketing, which will associate the aributes to the information template.
Note: The maximum number of aributes that can be created for an information template is fty.
End Dates
Procurement Catalog Administrators can specify an End Date on an information template. An information template is
inactive if the system date is more than or equal to the End Date.
When an information template is inactive, it will no longer be applied when items (to which this information template is
assigned) are added to the requisition. Requisitions created with lines that are associated to this information template
will continue to display the information template information.
For incomplete requisitions, the inactive information templates are no longer available at the time the requisition is
retrieved.
For copied and withdrawn requisitions, information templates are also no longer available if the information template is
inactive at the time the requisition is copied or resubmied.
Related Topics
• How Information Templates and Smart Forms Work Together
• How Information Templates, Items, and Categories Work Together
554
Oracle Procurement Cloud Chapter 19
Implementing Procurement Self Service Procurement Conguration
Related Topics
• How You Browse Catalogs by Category
What's a category?
Categories are used to classify items. You can develop your own method of categorizing products or use a standard
coding system such as UNSPSC. Adopting a standard coding system allows beer visibility of spend analysis throughout
the corporation, cost control optimization, and ability to explore all the e-commerce capabilities.
Categories are used to classify items. With catalog category hierarchies you can create a parent category that includes
child categories. When users navigate through a parent category, the child categories appear, helping them to quickly
nd the products they need.
You can develop your own method of categorizing products. You can also use standard coding systems such as the
United Nations Standard Products and Services Code (UNSPSC). Some of the benets of adopting a standard coding
system are:
• Helps improve visibility of spend analysis throughout the corporation
• Aids the organizing and optimizing of cost control initiatives
555
Oracle Procurement Cloud Chapter 19
Implementing Procurement Self Service Procurement Conguration
• Provides a structure for exploring all the e-commerce capabilities for purchasing products and services
The gure below shows the category hierarchy for a catalog. You can dene a catalog category hierarchy using two
types of categories: browsing categories and item categories. You aren't required to have the same number of levels in
all branches of the hierarchy.
Office
Equipment and Information
Accessories Technology
and Supplies
Office Supplies
Browsing Category
Components
and Paper for Information
Products Technology
Mailing
Desk Supplies Paper System Cards Computers
Supplies
Code: 44.12.15.11
Code: 44.12.16.18 Code: 14.11.16.07
Name: Mailing
Name:Scissors Name:Poster boards
boxes
Browsing Categories
Browsing categories are also known as navigation categories. Use them to dene the catalog category hierarchy for
category browsing. The category hierarchy helps users browse for catalog items. Browsing categories can be either a
parent or child to another category, but can't contain any items. Browsing categories are optional and you can decide
what categories should be enabled for browsing.
You can associate catalogs (such as local, punchout or informational) and request forms to the browsing categories.
When a user navigates to a category, the associated content type is displayed. An alternative to seing up browsing
categories is to tag punchout, informational, and request forms with keywords, so that users can nd them when
performing a basic search.
Item Categories
Item categories are also known as purchasing categories. Use them to group items for various reports and programs. An
item category is a logical classication of items that have similar characteristics. For a catalog, every item must belong
to an item category. You can:
556
Oracle Procurement Cloud Chapter 19
Implementing Procurement Self Service Procurement Conguration
What Happens When You Associate Catalog Category Hierarchy With Catalog
When an administrator associates punchout, informational, local, or request form content to a category, the application
associates the content with all the browsing and purchasing categories of the same branch. Item master items, and
agreement items are indexed with their corresponding purchasing categories.
For example, in the gure below, the Dell USA punchout is associated with the browsing category Computers. When you
navigate down the branch from the Information Technology browsing category to the Computer Servers purchasing
category, the search results always include the punchout catalog. The categories of the same branch as Computers are:
• Information Technology
• Components for Information Technology
• Computers
• Computer Servers
The informational catalog How to Request Computer Services is associated with the browsing category Information
Technology. As you navigate the Information Technology branch, the Informational Catalog is seen at the following
levels:
• Information Technology
• Components for Information Technology
• System Cards
• Computers
• Memory Module Cards
• Computer Servers
Local catalog items are also included in browsing results. Using the example in the gure below, items in blanket
purchase agreements with supplier Zones Corporate are associated with the Information Technology content zone.
Such items show up as you navigate down the Information Technology branch, based on the content available to you
from the content zone.
The procurement catalog is automatically updated after an administrator saves any changes made to the catalog
category hierarchy.
557
Oracle Procurement Cloud Chapter 19
Implementing Procurement Self Service Procurement Conguration
This gure shows the example catalog category hierarchy structure discussed in this topic.
Office Supplies
Browsing Category
Components
and Paper Smartforms:
for Information
Products Business Cards
Technology
Mailing
Desk Supplies Paper System Cards Computers
Supplies
Name:Staplers
envelopes cards module cards servers
UNSPSC
Code: 44.12.15.11
Code: 44.12.16.18 Code: 14.11.16.07
Name: Mailing
Name:Scissors Name:Poster boards
boxes
Related Topics
• Update Existing Setup Data
558
Oracle Procurement Cloud Chapter 19
Implementing Procurement Self Service Procurement Conguration
With the structured one-time delivery address feature enabled for Procurement, when you congure the requisitioning
BU to allow one-time addresses, structured one-time addresses are used. In this case, one-time addresses are stored in
structured elds.
Structured address data can be accurately used by downstream processes. For example, one-time addresses can be
used in tax calculations performed after the requisition is submied.
559
Oracle Procurement Cloud Chapter 19
Implementing Procurement Self Service Procurement Conguration
You can optionally set up Enterprise Data Quality (EDQ) using the Manage Data Quality Server Congurations task.
After the feature is enabled for the BU, requesters can enter structured one-time addresses when creating requisition
lines or editing previously created requisition lines. Unstructured one-time addresses aren't available when the feature
is enabled. Structured addresses are passed downstream to purchase orders, but can't be created or edited in purchase
orders.
For each country, you can optionally enable address cleansing, which uses an external data quality application to
validate addresses as they're entered by the user. In addition, users can verify addresses on demand by clicking the
Verify Address icon, which appears for addresses in countries for which address cleansing is enabled.
Dene geography structures and country-specic address formats with the Manage Geographies and Manage Address
Formats tasks.
Related Topics
• How You Deliver to a Structured One-Time Address from a Requisition
• Structured One-Time Delivery Address in Purchase Orders
• Overview of Geographies
560
Oracle Procurement Cloud Chapter 19
Implementing Procurement Self Service Procurement Conguration
In the Oerings work area, enable the Fulll Expense Requisitions for Agreement-Based Catalog Items from
Internal Sources feature in the Procurement oering, Purchasing functional area.
After the feature is enabled, when a requester shops for an agreement-based expense item from the catalog:
• Their requisition for the item is fullled through an internal source, even if the item is also purchasable against
a blanket purchase agreement.
• They see the blanket purchase agreement price for the item when searching and shopping. When they add the
item to the Cart, the price may change if the internally ordered price for the item is dierent.
Related Topics
• Congure Oerings
561
Oracle Procurement Cloud Chapter 19
Implementing Procurement Self Service Procurement Conguration
562
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
• Supplier Administrator: This is a buying organization job role. Users with this role are responsible for
maintaining supplier prole information as well as administering user accounts for supplier contacts.
• Supplier Manager: This is a buying organization job role. Users with this role are responsible for authorizing
new suppliers for spending. They control the addition of new spend authorized suppliers into the supply base.
In smaller organizations, you can assign this job role and the Supplier Administrator role to the same individual.
• Supplier Self Service Administrator: This is a supplier organization job role. Supplier users with this role can
maintain company proles and request user accounts for their fellow employees. All prole changes and user
account requests made by the supplier self service administrator require approval by the buying organization.
• Supplier Self Service Clerk: This is a supplier organization job role. Supplier users with this role can maintain
company proles and request user accounts for their fellow employees. All prole changes and user account
requests made by the supplier self service clerk require approval by the buying organization.
You can perform user provisioning from the following procurement ows:
In each of these ows a user with one of the appropriate job roles can:
563
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
The Procurement Application Administrator can go to the Setup and Maintenance work area and use the Manage
Supplier User Role Usages task in the Procurement oering and Supplier Portal functional area.
Your buying organization uses the Manage Supplier User Roles page to perform the following setup actions. These
actions are performed by two dierent job roles: IT Security Manager, and Procurement Application Administrator.
• IT Security Manager: Dene the list of roles that can be granted to supplier users in Supplier Portal provisioning
ows. Only the IT Security Manager job role can add and remove roles. This helps your organization avoid the
risk of adding an internal application job role inadvertently. It prevents suppliers from gaining unauthorized
access to internal data. The supplier roles are added from the central Oracle LDAP roles repository which stores
all Oracle Fusion application job roles. Once they add a role to the table, the role is immediately available for
provisioning to supplier contacts by the Supplier Administrator.
• Procurement Application Administrator: Dene the supplier role usages. The Procurement Application
Administrator is responsible for this setup task. They manage seings for how the supplier job roles are
exposed in provisioning ows.
The IT Security Manager can also set supplier role usages, as they can access all functions on the setup page.
However, this task is typically performed by the Procurement Application Administrator. The Procurement Application
Administrator can't add or remove roles from the table.
Your buying organization can establish default roles which expedite supplier user account requests. To do this, identify
the minimum set of job roles that a supplier contact can be granted. Use default roles so that approvers don't have to
explicitly review and assign job roles for each user account request.
When the role default setup is done correctly, the Supplier Administrator (or approver) can review supplier contact user
account requests. This allows them to:
• Review requests with job roles selected based on the source of the request.
• Approve user account requests with appropriate role assignments.
• Default for Oracle Fusion Supplier Portal: If selected, the role is automatically added to supplier user requests in
the core user provisioning ows, such as supplier prole maintenance.
• Default for Oracle Fusion Sourcing: If selected, the role is automatically added to supplier user requests
generated in sourcing ows such as Create Negotiation.
A role in the table can be marked for one or more of the two usages.
Related Topics
• Supplier User Account Request
564
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
The IT security manager navigates to the Setup and Maintenance work area and uses the Manage Supplier User
Roles task in the Procurement oering and Supplier Portal functional area. They search for the supplier job role
Supplier Customer Service Representative, and add the role to the table.
The Procurement Application Administrator then navigates to the Setup and Maintenance work area and uses the
Manage Supplier User Role Usages task in the Procurement oering and Supplier Portal functional area. For the
Supplier Customer Service Representative role, they select the following option: Default for Supplier Portal.
Vision Corporation also recently implemented Oracle Fusion Sourcing. They must provision the Supplier Bidder role to
suppliers invited to sourcing events. The IT Security Manager navigates to the Manage Supplier User Roles page. They
add the Supplier Bidder role to the table. For the newly added role, they select the Default for Sourcing option.
Related Topics
• Supplier User Account Request
• Create Supplier Contact: When creating a supplier contact, the administrator can also request to create a user
account for the contact, request roles and grant data access. A supplier user can also request for a supplier
contact and user account to be created.
• Edit Supplier Contact: The supplier administrator can make changes to supplier contact information as well
as create or maintain the user account for the contact. A supplier user can also request a user account to be
created for an existing contact.
• Import Supplier Contact: When importing supplier contacts, the administrator can also use the User Account
Action column to create or update a user account for specied contacts.
565
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
• Approve supplier registration request: When approving a supplier registration, an approver can create and
edit supplier contacts. A user account is part of a supplier contact. The approver has the ability to create a user
account and assign roles within this ow.
Note: Creating a user account for a supplier contact can't be reversed. Once a user account is created it can't
be deleted, but it can be inactivated.
Select the Create User Account option for a contact to send a request to the identity management system to provision
the account. Status is displayed to communicate provisioning status during this process. When the process is complete,
the identity management system sends notication to the supplier contact with the user name and temporary password
for the Supplier Portal work area. If the process fails, a notication is sent to the Supplier Administrator that a user
account wasn't successfully provisioned.
Use the Roles subtab to control function security. This determines the business objects and task ows the supplier
user can access. Supplier job roles should be assigned based on the job that the contact performs within the supplier
organization. For example, Customer Service Representative or Accounts Receivable Specialist.
Use the Data Access tab to control data security. This determines which transactions the user can access for the specic
business objects their job role is associated with. The two levels of data security are: Supplier and Supplier Site. By
default, all supplier user accounts start with Supplier level, meaning they can access all transactions belonging to their
supplier company only. For more restrictive access, the Supplier Site level limits user access to transactions for specic
supplier sites only.
566
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
1. In the SUPPLIER_USER User Category: Notications page, click Edit and then click the template link.
2. Click Save and Close.
3. Click Save and then Done.
To access the supplier registration approvals tasks, in the Setup and Maintenance work area, go to the following:
• Oering: Procurement
• Functional Area: Approval Management
Use the Task: Manage Supplier Registration Approvals to congure approval routing rules for registrations submied by
external users of companies interested in becoming a supplier.
Use the Task: Manage Internal Supplier Registration Approvals to congure approval routing rules for registrations
submied by internal users on the company's behalf.
567
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
The following gure shows the seeded supplier registration approval stages that are executed in Oracle Fusion Supplier
Portal.
Approval rules congured in the seeded stages are executed in the following sequence:
Parallel Approval
Serial Approval
The following gure shows the second stage approvals that are executed after all rst stage approvals are completed.
568
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
Parallel Approval
Serial Approval
Approval Stages
Approvals to review supplier registration requests happen in a exible two-stage process.
Within each stage, there are three seeded rule-based participants. You can pick a routing type (Supervisory, Position,
Job Level, Single User, and User-Dened Approval Groups) to congure the list of approvers entitled to receive the
document for approval.
You do not need to use all of the seeded stages and participants. You can disable unused participants by selecting the
unused participant on the Manage Approvals Task page and clicking the Disable buon.
Disabled Rules or Participants will not be evaluated. For example, if the participant is already disabled, then no rules
within that participant will be evaluated. The same applies for disabled rules.
All identied approvers receive a notication for approval in parallel. The rst responder to approve or reject
the request denes the outcome of all remaining approvers.
• Parallel Approval
All identied approvers receive a notication for approval in parallel. Approval is required from all approvers.
• Serial Approval
Approvals are routed in serial. The approval is completed sequentially from approver to approver.
569
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
All identied approvers receive a notication for approval in parallel. The rst responder to approve or reject
the request denes the outcome of all remaining approvers.
• Parallel Approval
All identied approvers receive a notication for approval in parallel. Approval is required from all approvers.
• Serial Approval
Approvals are routed in Serial. The approval is completed sequentially from approver to approver.
• If supplier registration has business relationship of Prospective, then route to supplier administrator.
• If supplier registration has business relationship of Spend Authorized, then route to supplier managers.
Supplier Managers are derived from the users dened in procurement agents. All procurement agents with Manage
Suppliers function for the BU that the registration was created will receive the approval notication.
Even if new rules are not congured, the seeded rule will execute unless it is deleted.
Note: You can, at any point of time, modify or delete the seeded rule.
After you have congured and enabled the notication builder, it reduces any manual intervention required to
communicate various business related policies to the supplier when they are approved for spend.
570
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
Supplier Registration
You can congure the supplier registration process based on the expected supplier business relationship of a supplier.
You can dene two separate registration ows based on the intended business relationship.
• Spend Authorized Supplier requests: Companies already identied for a procurement need are directed by
the buying organization to the spend authorized registration ow. The ow captures more rigorous prole
information needed before agreements, orders, and invoices can be transacted. For example, a spend
authorized company registering can be required to provide bank account information.
571
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
• Prospective Supplier requests: Unknown companies are presented with the prospective supplier ow. They
must only provide minimal prole information to participate in the sourcing and supplier qualication activities.
Possible prole components that you can include during a registration ow include:
When you congure the two supplier registration ows you identify which prole aributes the supplier sees. Also you
can specify whether the supplier must enter a value for the aribute.
• Enabled: The aribute is displayed to the supplier, but the supplier is not required to enter information.
• Required: The supplier must supply information for this aribute.
Note: Your supplier registration conguration applies to suppliers from all registration sources.
In the Default Business Relationship for Registration Sources region, you identify the default business relationship
for each registration ow. The default business relationship determines what prole information is included as
congured for the registration page.
572
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
Supplier proles can also be changed by internal users. Updates to bank account changes by internal users are
submied to an approval process. See Conguring Internal Supplier Bank Account Change Approvals: Explained.
The Congure Supplier Registration and Prole Change Requests task does not congure supplier prole changes
made by internal users.
You can specify approval requirements for prospective and spend authorized suppliers for the following entities:
• Organization Details: Basic supplier information including the supplier name and supplier prole level
descriptive exelds.
• Contacts: Supplier contact information including supplier contact descriptive exelds.
• Contact User Account: User accounts that control account privileges for supplier contacts to use Supplier Portal.
• Addresses: Company addresses including associated contacts including supplier address descriptive exelds.
• Business Classications: Supplier certications important to the buying organization such as supplier diversity
programs.
• Bank Accounts: Supplier banking information.
• Payment Methods The method used to pay the supplier.
• Products and Services: Identies what categories of products and services are provided by the supplier.
• Tax Identiers: Tax organization, tax country, and taxpayer ID to identify the supplier for tax purposes.
573
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
• Site Details: Site information such as the address and site purpose (spend authorized suppliers only).
Conguration of the Site Details aribute for prospective suppliers is not available.
Related Topics
• Supplier Products and Services Categories
• Supplier Registration Process
• Supplier Registration Approval
• How You Congure Internal Supplier Bank Account Change Approvals
• Internal Supplier Prole Change Request Approvals
You can specify a sourcing qualication model for a particular procurement BU to assess a supplier's eligibility to
participate in sourcing negotiations.
When one of the triggering events occurs for which you have dened a rule set, the application creates a questionnaire
consisting of the qualication areas that you identied in your rule set. This questionnaire is what the supplier sees.
When you receive the supplier's response, you use the supplier's basic registration information and questionnaire
responses to evaluate the supplier information with regards to the triggering event.
When a supplier is approved as a prospective or spend authorized supplier, his responses are stored in the Supplier
Qualication Response Repository. Once the supplier's responses are in the Response Repository, you can use those
responses to create qualications for the supplier.
574
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
• User requests the supplier to be promoted to spend authorized manually on the supplier record by using the
promote to spend authorized buon from the Edit Supplier page.
• Initial creation of supplier with the business relationship of spend authorized. The supplier must rst be
approved through the supplier registration process before the request for spend authorization is sent for
approval.
• Negotiation is awarded to a prospective supplier, a spend authorization request is automatically created.
Approvers can approve, reject, or reassign the spend authorization requests. Rejected requests can be resubmied for
approval.
When you resubmit a pending request, you can include a reason, which will be available as additional information in
the approval history. Even though the current request is being rejected, this activity will not aect the Negotiation
Award ow (if the request has come from negotiation award) as a new request is immediately created and submied for
approval.
Related Topics
• Supplier Model
575
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
When you resubmit a pending request, you can include a reason, which will be available as additional information in the
approval history.
Update Suppliers
Updates can be viewed on a report, with the new column indicating the import action of the record.
576
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
Purging supplier records is a permanent action. Exercise caution when running the purge program.
After a purge, a report is generated lists the count of records successfully purged. If the purge process fails, all records
previously purged during the job will be restored. In this case, you must rerun the process for all records.
Related Topics
• Congure Oerings
• Share Supplier Taxpayer ID Sharing
577
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
Supplier Import
You can load data to interface tables using predened templates and the Load Interface File for Import scheduled
process. Both are part of the External Data Integration Services for the Oracle Cloud feature.
Obtain FBDI templates from the File-Based Data Import for Oracle Procurement Cloud guide from the links found in the
File-Based Data Imports section.
578
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
◦ POZ_SUP_THIRDPARTY_INT
Note: For more information about tables, see the Tables and Views for Oracle Procurement
Cloud guide. To obtain the templates to use, see File-Based Data Import for Oracle
Procurement Cloud. Use the instructions contained in the template to complete the template.
The elds used vary from one type of template to another, but all templates begin with these
elds:
◦ Batch ID - Enter a value in the Batch ID eld to group certain entries together. When you
perform the upload, you can choose to process only the entries with a certain batch ID
value. This lets you maintain a single upload le and selectively choose subgroups of
entries to be processed from it, without having to process the entire le. For example,
for a supplier address upload le, you might use a batch ID value for the state. When
you process the upload le, you can choose to process only the records for the state of
California.
◦ Import Action - Use Create to add a new entity, such as a new site assignment or a new
address. Use Update to modify an existing entity.
2. Once the data is inserted, the following concurrent processes must be run to import the supplier prole data in
Oracle Fusion Suppliers:
◦ Import Suppliers
◦ Import Supplier Addresses
◦ Import Supplier Sites
◦ Import Supplier Site Assignments
◦ Import Supplier Contacts
◦ Import Supplier Business Classications
◦ Import Supplier Products and Services Categories
◦ Import Supplier Aachments
These import processes are executed by the Enterprise Scheduler Service (ESS), which manages all concurrent
processes. You can monitor the status of each process and provides access to output reports.
Supplier import processes contain the following parameters:
◦Import Options: Options include All, New, and Rejected. Import Options are used to determine if the
import process should aempt to import new, rejected, or all rows from the respective open interface
tables.
◦ Report Exceptions Only: Values are Yes or No. Used to determine if the Import Process Reports prints
success and rejected information, or just the rejected information.
3. When the processes are complete, a .pdf report is generated detailing the status of the records that were
imported. If a record couldn't be imported, then the status is set to Rejected. The reason for the rejection is
provided.
Upload line level errors are applicable only to a line and don't aect the loader's capability to read and process
the remainder of the lines in the upload le. Upload line errors can be caused by an invalid UOM for a line, or
an incorrect data type specied for a line aribute. Line level errors are displayed in the line errors region or
parsing errors region on the upload errors page. Line level errors can be exported to a spreadsheet for review.
Upload le-level errors are detected at the start of processing. The loader is halted and no le lines are
processed. Upload le-level errors can be caused by invalid XML or cXML les, mandatory sections missing
579
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
from a TXT le, or sections out of order in a TXT le. The upload errors page displays the le level error. The
line or parsing errors region isn't displayed.
The error threshold parameter sets the maximum number of errors allowed on upload lines before termination
of upload le processing. You can export the items table to perform an error analysis.
Note:
◦ The supplier import processes are used to create new entities, and to update or delete
existing supplier prole data. Creation can be done only with aachments. Deletion can
be done only with contact addresses, business classications, and products and service
categories.
◦ Supplier import supports supplier numbering of characters that aren't numeric to allow
supplier records from legacy systems to retain their unique identier.
◦ Update supports updating the functional key aributes. The columns ending with _NEW
are specically earmarked for updates. Use this only if the underlying functional key
aributes must be updated. To update functional keys, the new value should be provided
in the _NEW column.
Import Suppliers
Both prospective or spend authorized suppliers can be imported. Sites and site assignments can't be imported for
prospective suppliers.
After a site is created and associated with an address, the association can't be changed. For this reason, including a
value for Address Name when updating an existing supplier site triggers an error. The Address Name eld maps to
PARTY_SITE_NAME, which is the eld named in the error.
Use the Supplier Sites Import process to load third-party payment relationships from an external system. Before you
import supplier site third-party payment relationship data, review the recommendations in the supplier site import
template, Instructions and CSV Generation worksheet.
There are two separate worksheets available for importing supplier sites and third-party payment relationships on the
supplier site import template.
580
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
Note: Two separate worksheets are available for contacts and contact addresses on the import upload
template for supplier contacts.
The import process checks for duplicate contacts. Provide distinguishing email addresses for imported supplier contacts
with the same last name as existing supplier contacts.
Use the User Account Action column to specify the action to create or update a user account. Create a user account by
using the default roles for the Supplier Portal work area, the Sourcing work area, or specifying individual roles. Update a
user account by adding or removing specic roles, or inactivating the user account. Use the Role 1 to Role 10 columns to
specify specic roles based on the user account action.
Here are things you can do after you run the supplier contact import process:
If you need to nd out the user accounts that are created or updated successfully, you can create a report for that. Go
to the Reports and Analytics work area, use aributes in Supplier - Supplier Real Time subject area to report on user
account details.
When a user account action is specied for any imported supplier contact, the Send Pending LDAP Requests process is
launched automatically to complete the user account action. If the user accounts aren't created or updated successfully,
you can manually run the process using these steps:
1. From the Tools work area, click Scheduled Processes.
2. Click Schedule New Processes and search for Send Pending LDAP Requests.
3. For Parameters, choose User Type as Party and Batch Size as A, and then click Submit.
Note:
Legacy data including both inactive and active data can be loaded for all the supplier entities
For File type aachments, you must add the le to a .zip le and upload the .zip to the Procurement Suppliers UCM
account: /prc/supplier/import. Multiple les can be added to the same .zip le and can be organized within folders
as needed. The template is designed to accept the path along with the le name. This tells the application in which
folder of the .zip le the le is located. The Recommendations for Loading Supplier Aachments Data section in the
Instructions and CSV Generation tab contains more information on importing aachments.
Related Topics
• Overview of External Data Integration Services for Oracle Cloud
581
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
To successfully import the record, for lookup type aributes, you must provide the necessary codes and not the
display values.
2. To get the necessary codes, in the Setup and Maintenance work area, go to the Manage Descriptive Flexelds
task and search for the exeld code JE_POZ_SUPPLIERS. Select to edit the DFF entity to get all the relevant
details.
For the regional information lookup, access the page Manage Contexts from the edit descriptive exeld page
for the descriptive exeld entity JE_POZ_SUPPLIERS. For the dependent aribute codes, access the context
sensitive segment for the respective context and nd the value set that is used. From the value set, you can get
the codes for these aribute lookup values.
3. Do the import.
You create this structure by using the supplier import process to create an additional relationship with an existing party.
The table below shows the column aributes and suggested values for the import template.
582
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
Column Value
Action Create
Supplier Name The name for the supplier you want to create
Tax Organization Type Tax organization type for the new supplier
Business Relationship
The type of relationship between your company and the new supplier. The relationship type
controls which transactions you and the supplier can conduct. There are two choices:
• Prospective supplier
• Spend authorized
To create the new supplier, you use the supplier import template. When you submit an import process to create a new
supplier relationship with an active party, the process checks that:
• The registry ID that you entered is valid and belongs to an active party.
• That party does not already have a supplier relationship.
• The supplier name that you entered in the template is an exact match with the party name for the registry ID
you entered in the import process.
When the supplier import process completes successfully, the existing party is associated with the supplier relationship
and is therefore available for transactions as a supplier. When you view the party as a supplier, you see the registry ID as
part of the prole information. Also, shared aributes like D-U-N-S Number, contacts, and addresses are available from
the existing party and displayed for the supplier.
For the tax registration number, set the country specic format requirements like country and the registration number
controls and default values, validation type and validation level.
583
Oracle Procurement Cloud Chapter 20
Implementing Procurement Supplier Portal Conguration
Supplier Portal
The Supplier Portal page serves as the landing page for Oracle Fusion Supplier Portal and provides quick access to tasks
and reports relevant to you. The content that you can access in the Supplier Portal is controlled by your job role and
your data access seings.
The Supplier Portal page includes an integrated search facility to locate particular orders, agreements, shipments and so
on, a Tasks list from which to access all Supplier Portal tasks and reports, and a number of dynamically updated infolets.
Infolets provide interactive graphic readouts of critical real time information, such as supplier transaction reports, for
example.
Tasks
Select tasks and reports from the Tasks list on the Supplier Portal page. Links are included for all activities you need
to perform in Supplier Portal such as managing shipments and deliverables and creating invoices. Updates to your
company prole can be initiated by clicking Manage Prole. See Supplier Prole Change Requests: Explained for more
information.
Include BI Reports
When you want to show reports on the Supplier Portal, for example, you want to report the supplier activities in a
negotiation, you can use the Page Composer based personalization to add a report. For more information on Page
Composer, see Oracle Applications Cloud Conguring and Extending Applications. After you have created a BI report,
you can add it to the Supplier Portal page in the form of a hyperlink that points to the report that suppliers can open. To
construct a report URL, see the topic Accessing Reports via a URL in the Oracle Fusion Middleware Report Designer's
Guide for Oracle Business Intelligence Publisher.
Related Topics
• Supplier Prole Change Requests
• How You Use and Personalize Infolets in Oracle SCM and Procurement Cloud
584
Oracle Procurement Cloud Chapter 21
Implementing Procurement Sourcing Conguration
21 Sourcing Conguration
Negotiation Styles
Example of Negotiation Styles
Negotiation styles control the denition of your negotiation documents. Negotiation styles can specify the terminology
used within the document and control which processing capabilities can be performed using the style. For example,
you can dene a simple negotiation style and then use it to create very straightforward, streamlined negotiations.
Alternately, you can create a negotiation style that takes advantage of many processing features. You can then use this
style to create a complex negotiation. Using negotiation styles, you can also dene default textual content for certain
sections of a negotiation document.
In this example, Jan Martin is going to create a new negotiation style for use with RFQs. She allows alternate lines,
multiple responses and response revision. She allows responses using a spreadsheet.
Negotiation Styles
You can create multiple negotiation styles that control the creation of your negotiation documents. Negotiation styles
can specify the terminology used within the document and control which processing capabilities can be performed
using the style. You can also create default content for certain sections of a negotiation document.
585
Oracle Procurement Cloud Chapter 21
Implementing Procurement Sourcing Conguration
For example, you might create a slimmed down style that doesn't include Instructions
• Instructions
• Autoextend seings
• Staggered closing
• Cost factors
• Contract terms
For some Sourcing capabilities, you must create a negotiation style that supports the capability. For example, to use the
following capabilities:
• Two stage RFQ
• Project tasks
• Alternate responses
Document Terminology
For each negotiation there is a pair of documents: negotiation document created by the category manager and a
response document created by the supplier contact. Each of these documents has a label. Within the application, there
are three types of negotiations: auction, RFI, or RFQ. Each type has its own document labels; however, you can change
the labels used in the negotiation style. :
The following table shows the predened values for negotiation document and response document.
Auction Bid
RFI Response
RFQ Quote
When creating a negotiation style, you can create alternate labels for the category manager-side or supplier-side
documents. Then any negotiation document created using that style replaces the default labels with the labels
you created in the style. These replacements appear both in the online application and any printed versions of the
document.
For example, you could use Tender or Oer for the supplier-side document, and you could use Solicitation for the
buyer-side document.
586
Oracle Procurement Cloud Chapter 21
Implementing Procurement Sourcing Conguration
• If you want to use this style to associate a negotiation to Oracle Projects project plan information, click the
Project tasks check box.
• If you want to allow the supplier to respond with dierent line information, click the Alternate response lines
check box.
Related Topics
• Supplier Negotiations
Negotiation Styles
Negotiation styles control the denition of your negotiation documents. Negotiation styles can specify the terminology
used within the document and control which processing capabilities can be performed using the style. For example,
you can dene a simple negotiation style and then use it to create very straightforward, streamlined negotiations.
Alternately, you can create a negotiation style that takes advantage of many processing features. You can then use this
style to create a complex negotiation.
Using negotiation styles, you can dene default textual content for use in a negotiation document. Also, you can
identify which negotiation capabilities are available when using this negotiation style.
Header Information
You enter header information to describe your negotiation style.
The following table shows the header level elds used in negotiation styles.
Field Meaning
Document Types
You can specify which document types category managers can create using this style. You can also change the
terminology used to refer to dierent document types and related terms. For example, you might want to change the
term quote to oer.
The following table shows the elds you can dene for dierent document types.
Field Meaning
Enable If enable is checked, you can use this style when creating negotiations of that type.
587
Oracle Procurement Cloud Chapter 21
Implementing Procurement Sourcing Conguration
Field Meaning
Negotiation Display Name Current display name used for this type of negotiation
Response Document Type Name of the response for this negotiation type
Response Display Name The current display name for responses to this negotiation type
Edit Content Icon that you can use to modify the negotiation display name and the response display name
Features include:
• Two-stage RFQ
• Integration with Oracle Fusion Project Management project plans.
• Abstracts.
• Team Scoring.
Related Topics
• Supplier Negotiations
• Examples of Negotiation Controls
• Associate a Negotiation with an Oracle Fusion Project Management Project Plan
• How You Use a Two-Stage RFQ
Aribute Lists
Line Aribute Properties and Their Acceptable Values
Line aributes identify additional information about an item or service requested by the category manager. Use the
following properties to describe your line aribute when dening it.
You use a line aribute's properties to control its behavior and how the supplier should respond.
588
Oracle Procurement Cloud Chapter 21
Implementing Procurement Sourcing Conguration
Response
You can control the supplier's interaction with the aribute by specifying the response type. Optional responses don't
require a supplier to oer a response. Suppliers must however provide a value for a required response. Suppliers can
view aributes which are display only, but they can't respond to them.
Value Type
Value type species the data type for the aribute value. There are four value types available. A text value accepts
characters and numbers. A number value accepts only numbers and the decimal point. Date values accept dates that
you select using the calendar picker. A URL value type accepts a URL in the format hp://url.name.here. URLs also
accept hps:
Target
For each aribute, you can dene a target value. This is the value which is most desirable for this aribute. You can also
display the value to the supplier or keep it hidden.
Acceptable Values
For text values, you can specify a list of values from which the supplier can select. Any value not dened to the list isn't
accepted. For number and date values, you can dene value ranges in terms of From Value and To Value. If you omit a
From Value, that range includes everything up to the To value. Likewise, if you omit a To value, the range includes all
values starting at the From value and above. Ranges can't overlap. You can specify a single number by dening it as
both the From and To values. Dates are dened similar to numbers.
589
Oracle Procurement Cloud Chapter 21
Implementing Procurement Sourcing Conguration
5. Once the group has been added, she clicks Add Aribute and uses the Add Aribute page to dene an
aribute to the list.
6. She repeats the last step until she has added all the necessary aributes to the list.
Cost Factors
Cost Factors and Cost Factor Lists
Cost factors allow you to identify and negotiate on additional costs related to a line.
There are two types of cost factors:
• External
• Internal
590
Oracle Procurement Cloud Chapter 21
Implementing Procurement Sourcing Conguration
Internal cost factors are determined by the buying organization and applied to the supplier's response amount. In
addition to the response amount, you can see the new transformed amount at the response header level and the overall
rank thereby aiding the award negotiation process. You can assign internal cost factors of type percentage of response
amount or xed amount to the response amount of one or more suppliers.
Overall Rank
The overall rank is based on the transformed amount. Lower the transformed amount, higher the overall rank. If a
supplier doesn't have an internal cost factors assigned, then the response amount is considered for the calculation of
the overall rank.
Here are things you can do or you need to know when you're working with internal cost factors.
• As a procurement administrator or category manager, you can create a new negotiation style or update an
existing negotiation style to enable the internal cost factors.
• If same set of internal cost factors are often applied to multiple negotiations, then you have the option to create
a negotiation template and add internal cost factors to it, set their values, and then use this template to create
negotiations.
• The value of the internal cost factors can be negative or positive. The negative internal cost factors will reduce
the transformed amount.
• You can modify internal cost factor values when the negotiation is in the active, closed, or award in progress
statuses.
• You can set the internal cost factor values at the time of negotiation creation or after you view the supplier
responses.
591
Oracle Procurement Cloud Chapter 21
Implementing Procurement Sourcing Conguration
• You can adjust internal cost factor values when the negotiation is in the active, closed, or award in progress
statuses.
• You can update internal cost factor values from the analyze, monitor, or award negotiation pages by selecting
the Apply Internal Cost Factors action.
• If you want to restrict transformation information for internal analysis, you must deselect the response rules
Display transformed amount to suppliers and Display overall rank to suppliers.
• When the transformed amount for more than one response is same, the earlier response gets the higher overall
rank.
• Overall rank isn't calculated for partial responses. To ensure overall rank is calculated for all supplier responses,
you must set response rules to not allow suppliers to respond with partial lines or quantities. Also, if a supplier's
access is restricted to one or more negotiation lines, then overall rank isn't calculated for responses from that
supplier.
Related Topics
• How Cost Factors Are Calculated
• How You Calculate Cost Factors in Awards
• Create Cost Factor Lists
Vision Corporation is expanding into a new branch of its items and services. Negotiations dealing with this new area
will need to negotiate new transportation-related costs with suppliers, specically with the new Chicago oce. The
procurement application administrator is going to dene several new cost factors. Once the cost factors are dened and
enabled, they become available for buyers to use individually or as members of a cost factor list.
592
Oracle Procurement Cloud Chapter 21
Implementing Procurement Sourcing Conguration
Negotiation Templates
Create a Negotiation Template
If the majority of the negotiations you create contain the same features, for example, line aributes, terms and
conditions, response controls; or negotiation data such as the value for the Location eld, you may want to create a
negotiation template that category managers can use each time they create a new negotiation.
Using a template saves time by streamlining the creation process. A negotiation template contains the features that
are similar among the negotiations you commonly create. When you create new negotiations using templates, you can
use the template as a shell for the negotiation, add to and edit details of the negotiation as necessary, and publish the
negotiation.
In this example, Sue Parado, a category manage, will dene a negotiation template to be used when negotiating for a list
of incumbent supplies from Vision's inventory category 200.13 which contains printers.
593
Oracle Procurement Cloud Chapter 21
Implementing Procurement Sourcing Conguration
you cannot dene a close date. The category manager will enter that date when she uses the template to create
a negotiation.
5. She enters Printer Auctionsas the template name, and on the Lines page, enters 200.13 for Category. On the
Suppliers page, she enters the names of the suppliers with whom the company has purchased printers in the
past.
6. When the procurement application administrator has completed the appropriate elds, she activates and saves
the new template.
Abstracts
Implement Abstracts
Abstracts are negotiation summaries that you post on your external website so they can be displayed to suppliers. Then
your suppliers can read information about your upcoming negotiations and decide if they are interested in participating
without having to log in to the sourcing application to view information. Abstracts are used mainly in public sector
entities such as state and local governments, EMEA and US federal negotiations.
To implement abstracts, you must do these tasks.
• Create a negotiation style that supports abstracts. See the topic on creating negotiation style in this chapter.
• Update the Congure Abstract Listing page.
594
Oracle Procurement Cloud Chapter 21
Implementing Procurement Sourcing Conguration
2. Select the Procurement business unit for which you want to congure the abstract listing page.
3. On the Congure Procurement Business Function page, go to the Sourcing section.
4. Click Congure Abstract Listing.
5. On the Congure Abstract Listing page, set the controls and formats as appropriate for abstracts for this
Procurement business unit. Note that you can also create text to be included as header or footers.
6. When you are nished, click Save and Close.
◦ Oering: Procurement
◦ Functional Area: Procurement Foundation
◦ Task: Congure Procurement Business Function
2. Specify the Procurement BU for which you want to dene negotiation terms and conditions.
3. Under Sourcing, click Dene Terms and Conditions.
4. Based on what you want to do, select any of these Display to Participants options:
◦ Select Before viewing negotiation to restrict supplier users to accept the terms and conditions before
viewing the negotiation.
◦ Select Before creating response to restrict supplier users to send a response to a negotiation only after
accepting the terms and conditions.
◦ Select Never if you don't want to have any restrictions.
5. Dene terms and optionally add aachments.
6. Click Save and Close.
To enable terms acceptance acknowledgment notication to buyers, do these steps:
1. In the Setup and Maintenance work area, go to the Manage Sourcing Notications task:
◦ Oering: Procurement
◦ Functional Area: Sourcing
◦ Task: Manage Sourcing Notications
2. Enable the Negotiation terms or participation acknowledged subscription.
3. Click Save and Close.
To enable view only terms notication to invited supplier additional contacts, do these steps:
1. In the Setup and Maintenance work area, go to the Manage Sourcing Notications task:
◦ Oering: Procurement
◦ Functional Area: Sourcing
◦ Task: Manage Sourcing Notications
595
Oracle Procurement Cloud Chapter 21
Implementing Procurement Sourcing Conguration
Related Topics
• Negotiation Terms and Conditions
596
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
The following table shows the aributes for a question and explains each one.
Question The name you use when searching for this question to add to an initiative.
Status
Statuses include
Revision The current version of this question. The question version is maintained automatically by the
application.
Question Level The level at which the question applies: supplier or supplier site
597
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
Responder type Whether the expected responder is a supplier or an internal employee, supplier questions are
used to build the questionnaire sent to the supplier for responses. Internal questions are used
to build the questionnaire sent to the internal responder.
If you select Automatic, then you can map questions to descriptive exelds from the supplier
prole. Also, the mapped questions are excluded from the questionnaire.
If supplier is selected and mapped to a supplier prole aribute, then the question is mapped
to an aribute in the supplier's prole.
Mapped to supplier aribute When suppliers register with the application, they provide information that's stored in a prole
for that supplier.
You can map your question to an aribute of the supplier prole. This let the information the
supplier provides in the response to be added to the supplier prole.
If the question level is supplier site, then you link to site level aributes.
Also, depending on which aribute you map to, values for Question Type and Response Type
default can't be changed.
Supplier Prole Aribute Search and add a descriptive exeld. To search for an active descriptive exeld, select
category as Additional Information.
Question Type
The type of response for this question:
Accepts comments from the Lets the responder to enter comments along with the response
responder
Response Aachments (for Question Whether the supplier can include aachments in the response
Type = text)
Preferred Response (for Question Your preferred response to the question and whether it should be visible to the supplier.
Type = text)
598
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
Scoring
Once a supplier has completed responding to an initiative, and you accept the response, you
can view the supplier's responses to the initiative questions and assign the response a numeric
value based on how desirable that response value is. This is called scoring the response. There
are three types of scoring methods you can choose:
You can have both scored and non-scored questions in a qualication area, but if you have
scoring enabled for a qualication area, you must have at least one scored question in that
qualication area.
Aachments Click to add aachments to the question. If you use Setup Migrator to migrate Supplier
Qualication objects to a new environment, aachments aren't carried over.
Question Text The text of the question. The text the supplier sees on the questionnaire. You can use rich text
formaing as needed.
Categories of business classications are also used to describe the supplier, and a hierarchy of products and services
that identify a supplier's products or services. Depending on which aribute you map to, values for Question Type and
Response Type default can't be changed. If there are multiple possible values dened for the aribute in the supplier
prole, those values include the acceptable values for the question. You can't add or delete values to this list.
For example, one of the supplier prole aributes is Payment Terms, and there may be several dierent types of
payment terms available. If you use Payment Terms in a question, your responder must select an answer from the list of
values.
599
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
You can leverage supplier descriptive exeld values in the supplier qualication process by mapping a qualication
question to a descriptive exeld aribute on the supplier prole. You can populate supplier descriptive exeld's
multiple choice single selection aribute for question mapping where both text type and multiple choice with single
selection descriptive exelds are supported.
When questionnaires are sent to suppliers and internal responders, questions congured with responder type as
automatic are excluded from these questionnaires. You can use this extended supplier information in the qualication
activity that may not originate directly from a supplier or internal responder.
For supplier responder type, information is gathered from suppliers using a questionnaire and for automatic responder
type, responses are gathered from supplier prole automatically. Qualication managers can view all the question
responses (this includes responses for automatic responder type questions too), during qualication evaluation process
and award a qualication outcome for the respective supplier.
For the supplier responder type where the question is mapped to an aribute from the supplier prole, if the supplier
responds with an updated value then after approval, this new value is updated in the supplier prole aribute and in the
response repository. You can score supplier descriptive exeld's multiple choice single selection aribute values.
For the supplier registration process, if the supplier registration form and questionnaire share similar descriptive
exelds (that's, the descriptive exelds are mapped to the questions), then the values in these descriptive exelds
are synchronized with the questionnaire responses.
Question Branching
In addition to providing the supplier with a choice of allowable values for a single question, you can also use the
supplier's response to an initial question to determine whether additional questions should be asked. This is called
question branching. In essence, if you select a particular value for a question, you may be prompted to answer an
additional question. You can do question branching for acceptable responses of supplier descriptive exeld's multiple
choice single selection based questions.
600
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
For example, using the preceding scenario, you would dene questions in the following order
1. First you would create your follow-up questions. You could dene these in any order.
a. "Have you received any awards from this organization? If so aach documentation."
b. "How long have you been a member of this organization?"
c. "Has a representative of your company been on the governing board of this organization within the last
ve years?"
2. Once you have dened your follow-up questions, you can dene your primary question, for example: "To which
of the following organizations does your company belong?"
3. As you specify the list of allowable answers to your primary question (in this case, the names of organizations),
for the appropriate organizations, you would link the follow-up questions to that answer.
Note that:
Scenario
Tim Jones is creating a question for use in later qualication initiatives. This question asks the supplier to identify
whether the company is public or private. It accepts a single answer. If the answer to the question is "public," the
supplier must answer an additional question. This question asks the supplier to specify the date the company went
public. If the answer to the question is "private," the supplier does not supply any additional information.
Scenario
Carmen SantAngelo is creating a question to use when soliciting certication information for suppliers. The primary
question includes a list of several possible certications for the type of supplier. The supplier chooses all the
certications from the list that apply to the supplier company. Depending on which certication the supplier chooses, an
additional question is displayed which prompts the supplier for the latest certication date.
601
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
Create a Question
You create and save questions to use later in initiatives. By creating the questions separately, you can build a repository
of frequently used questions for reuse. Therefore, you do not have to recreate the questions every time you want to
create a new initiative.
In this scenario, Clare Furey, the supplier qualication manager, is creating questions for later use in an initiative
Aribute Value
Question Text Enter your expected revenue for the current scal year.
4. Once Clare enters all the information in the preceding table, she is nished dening the question. She clicks
Activate and then Save and Close. She returns to the Manage Questions page.
Aribute Value
602
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
Aribute Value
The Supplier Prole Aribute eld Clare clicks the search icon.
displays.
The Search and Select: Supplier She chooses Corporate Prole from the Category menu and clicks Search.
Prole Aribute dialog box displays.
The aributes for the Corporate She highlights the Preferred Functional Currency aribute and clicks OK.
Prole category appear.
3. She enters all the information in the preceding table and nishes dening the question. She clicks Activate and
then Save and Close. She returns to the Manage Questions page
Aribute Value
3. This question's nal answer varies depending on whether the company is less than one year old. If the
company is older than one year, the resulting question prompts for an age value. If the company is not yet a
year old, the resulting question prompts for a list of key investors. To dene this question branching, Clare
must dene the test question rst, so she clicks the Add icon for Acceptable Values. She must add an entry for
each of the possible values.
603
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
4. For the rst allowable value, she enters "Less than one year." She then clicks the icon to edit the question
branching.
5. On the Edit Question Branching dialog box, she clicks the Search and Add icon.
6. Searches for a question called Identify Investors. This question has been previously dened and is regularly
used in many initiatives. When she sees the question in the search results, she highlights the question in the
table and clicks Apply. Then she clicks OK to close the Search and Add dialog box. She clicks OK again to close
the Edit Question Branching dialog box.
7. Now that the rst test condition has been taken care of, Clare denes the remaining condition.
8. She adds another allowable value called "More than a year old." She edits the question branching for this value
and identies an existing question called More Than One Year. This question is a simple text box that prompts
the supplier to enter a number.
9. Now that she has nished dening the parent question, she clicks Activate and then Save and Close.
10. She has completed dening her questions at this point, so she leaves the Manage Question page.
Aribute Value
Scoring Automatic
3. In the Acceptable Responses, Clair must specify the acceptable responses, so she clicks the plus sign. She
enters the values:
1 to 100 20
101 to 500 30
604
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
4. After specifying the response values and their scores, she is done dening the question, so she clicks Save and
then Activate.
Qualication Areas
Qualication areas are containers for your questions. You use a qualication area and its questions to evaluate a
particular aspect of a supplier. You add one or more qualication areas to an initiative and use the questions in
the qualication areas to create a questionnaire. You then send the questionnaire to the supplier and any internal
responders for a response. Once all the responders have submied replies, you and any other evaluators review the
answers. If all evaluators approve the responses, a qualication for the supplier is created for that qualication area.
If you try to use a qualication area whose questions have been updated, the questions are displayed with an alert
icon. You can revise the qualication area denition by using the Uptake Latest Revision. If you don't update the
qualication area denition, it uses the previous version of the question.
The table shows the aributes for a qualication area and explanations for each.
Name Explanation
Qualication Area The name of the qualication area you're creating. This name is used as the name of the
qualication.
Revision The number of the current version of this qualication area denition. As changes are made to
the qualication area denition, the Revision number is incremented.
Information only Select this check box if you don't want this qualication area to aect any outcomes.
Expiration Reminder Sets a future point in time before the qualication expires when the application starts sending
alerts to the qualication manager. The value you set here's the default that's used for any
qualication created using this qualication area. The owner of the qualication can override
the value.
Aachments You can browse to existing les and add as aachments on the qualication area. You can
browse to and aach les, enter free form text, or enter a URL in the format hps://some.
name.com
Status
Qualication area denitions can be in one of four statuses:
605
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
Name Explanation
• Active - the denition is available for use in initiatives and qualication models.
• Inactive - the denition is disabled and can't be used. It can be reactivated for use when
necessary.
• Archived - this denition has been superseded by a more recent revision.
Qualication Area Level Whether qualications generated using this model apply only at the supplier site level or at
both the supplier and the supplier site level.
Owning Procurement BU The procurement business unit that owns this denition.
Default Qualication Owner Select a user to set as the default qualication owner for all the accessing procurement BUs
when this qualication area is included in a qualication initiative.
When a default qualication owner is assigned, then all the procurement BUs that have access
to this area will have this user as the default qualication owner unless specied otherwise in
the Business Unit Access or Business Unit Defaults table.
Global BU access These values control who can use this qualication area. The default is the procurement
business unit of the creator. If you check Global, the qualication area can be used by all
procurement business units in the application. Otherwise, you choose the procurement
business unit which can use this qualication area. You can insert multiple rows as access
procurement BUs.
Business Unit Access You can assign a default qualication owner for various business units. When the area
isn't global BU access, you can also add the procurement business units which can use this
qualication area.
• Summary - the qualication outcome, the start date and end date.
• Supplier response - the supplier response to the area questions.
• Internal response - the internal responder's response to the area questions.
• Note - you can communicate any additional information to the supplier.
Qualication Duration (only If you choose to have qualications automatically evaluated, this is value is used to derive
if automatically evaluating the qualication end date. The application uses the date the evaluation is performed for the
qualications) qualication start date. The qualication duration is added to the qualication start date to
derive the qualication end date.
Automatically populate response If there are existing responses from a supplier's previous response to questions in this
qualication area, you can choose to have the application use the existing responses when
it generates a new questionnaire. This sets the default for any initiatives that use this
qualication area, although a qualication manager can override the seing when dening the
initiative.
606
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
Name Explanation
Automatically populating the questionnaire with previous responses relieves the supplier of
having to always answer all the questions.
Alternatively, you may want to force the supplier to answer all the questions every time (for
example, you're using the questionnaire as a poll, so you want updated responses every time).
Automatically accept responses If you choose, you can automatically accept responses to questionnaires. This allows the
responses to enter the application without needing an evaluator to manually view and accept
them rst.
If you enable automatic response acceptance here, this sets the default for any initiatives that
use this qualication area, although a qualication manager can override the seing when
dening the initiative.
Enable scoring If you enable scoring for this qualication area, it must contain at least one question with
scoring dened. You must also set a weight for the question. The weight reects the
importance of that question among the other scored questions in this area. Weights are
required for scored questions and the weight values must add up to 100.
You can also set a knockout score which all response scores must surpass if they're to be used
in further processing. Seing knockout scores is optional.
Additionally, you dene the area outcomes in terms of total scores. An area's total score is the
sum of the scores of all the questions in the area. Typically, for each outcome, you specify a
beginning and ending score range.
Automatic initiative with single Select to automatically create an initiative with a single qualication where subject maer
qualication experts as initiative owners can review and accept responses independently for complex
qualications with quicker turn around for responses. Qualication owner can then evaluate
each qualication quickly, without having to wait for other qualication responses when
multiple qualications are present in the initiative.
Automatically evaluate qualication You can also choose to have qualications automatically evaluated.
(only if scoring is enabled)
Automatic Requalication on Select to automatically requalify a supplier for certain qualication areas when the current
qualication expiration qualication has expired or is within the expiration reminder period so that the supplier always
has an active qualication.
If you enable automatic requalication on qualication expiration here, all the qualications
created based on this qualication area will have automatic requalication on expiration
enabled by default.
Automatic Requalication on new Select to automatically requalify a supplier for certain qualication areas when a new response
response is available so that the active qualication is always based on the latest information.
Add icon (Question section) Using the add icon opens up a dialog window where you can choose questions and add them
to your qualication area.
607
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
Name Explanation
Question/ Question text (Search and Enter the name of a question or the beginning text of a question you want to locate. You
Add dialog box) choose the appropriate questions from the search results. When you're returned to the Create
Qualication Area, the questions you chose are displayed.
Weight You can set dierent weights for the questions in this qualication area. The weight for a
question indicates the importance of that question relative to the other questions in the area.
The higher the weight, the more important the question. The sum of the weights for all scored
questions in this area must equal 100.
Knockout score You can set a minimum score that all supplier responses must beat to be considered an
acceptable response to this question. If any of the required question responses fail to pass the
knockout score, the application assigns the qualication an unacceptable outcome.
Add icon (Qualication Outcomes Use the icon to dene a possible evaluation outcome for this area.
section)
Set as Knockout (only if scoring is When dening an area outcome, clicking this buon identies this outcome and the one to use
enabled) for any responses that don't beat the knockout score.
Outcome The name of a possible qualication outcome. For example, you might dene three possible
outcomes, Best, Acceptable, and Unacceptable. You assign one of these outcomes later when
you're evaluating a supplier's response, or if you're using automatic evaluation, the application
assigns the outcome based on the sum of scores for all the questions.
If you have scored questions in this area, then you dene the possible outcomes in terms of
total score values (the sum of all the scores of all the questions) using the From Score and To
Score elds. You must dene one outcome to use when at least one of the required question
responses doesn't pass the knock out score.
From Score/To Score (only if scoring If scoring is enabled this qualication area, for each possible outcome, you must identify a
is enabled) From Score and a To Score. When the responses to scored questions are evaluated, their
scores are added together to give a total score. This total score value you use here. Eectively,
this assigns responses with dierent total scores to dierent area outcomes.
Notify For each outcome you dene, you can optionally choose to send a notication to the owner
of the qualication area a notication whenever a response was automatically evaluated and
(Only if automatic evaluation is assigned to this outcome.
enabled)
608
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
2. Click the Questions and Outcomes icon to display the Create Qualication Area: Questions and Outcomes
page.
3. Search for and add all the questions that are appropriate for the aspect of the supplier that you want to qualify.
If you add a question that uses scoring, enter a weight for that question (the sum of all the question weights
must equal 100).
4. Dene all the possible outcomes to use later when you're evaluating a supplier's response. If you add a question
that uses scoring, enter a weight for that question (the sum of all the question weights must equal 100).
5. Dene any additional classication values as appropriate.
6. Once you have completed dening the qualication area, use Activate to make the qualication area available
for use.
If any changes are made to the questions contained in a qualication area, you can synchronize the latest question
version with the qualication area by choosing Uptake Latest Revision. Existing qualication areas remain linked to the
version of the question used when the area was created.
If you're planning changes to a qualication area, and you want to see which qualication models use the area, you can
view the area denition and then choose the View Qualication Area Usage.
Related Topics
• How You Automatically Requalify Qualications
• How Qualications Are Evaluated
609
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
6. Since she later selects which Procurement BUs can use this area, she leaves the Global box unchecked.
7. Since Clare did not check the Global check box, she must specify which procurement BUs can use this
qualication area, so she clicks select and add icon in the Business Access table. When the Procurement
BU dialog box displays, she searches and selects the names of the BUs that can use this area for qualifying
suppliers. When she is nished listing the BUs, she clicks OK.
8. She can assign a default qualication owner to manage the evaluation.
9. Since Clare wants to reuse this qualication area every year to keep her supplier information current, she
chooses to not reuse responses. This way suppliers will need to complete the initiative questionnaire every year
with new, updated response values.
10. The questions in this qualication area solicit general information about the suppliers' nancial organization
and history. None of the questions are required, and many are open-ended, so there is no need for her to view
the responses and possibly reject any of them. Since she does not need to view the responses, she enables the
Automatically accept responses aribute.
11. In this qualication area, Clare uses several questions that allow scoring. If a question is scored, evaluators can
assign a numeric value to the supplier response value. These response scores help you and other evaluators to
compare and grade responses between dierent suppliers. To allow the scoreable questions to be used in this
qualication area, Clare selects the check box named Enable scoring.
12. If she wants to automatically create an initiative with a single qualication, then she selects the Automatic
initiative with single qualication check box.
13. She sets the default expiration reminder value to 30 days. Therefore, for any qualication created using this
area, (unless the qualication owner changes the value), expiration reminders start going out 30 days before
the qualication expires.
14. If she wants to automatically requalify qualications on expiration, then she can select the Automatic
Requalication on expiration check box.
15. If she wants to automatically requalify qualications whenever there is a new response, then she can select the
Automatic Requalication on new response check box.
16. Now Clare must add her questions, so she clicks the Add icon in the Questions region. When the Search and
Add dialog box appears, she nds and adds a question called Annual Revenue. This question has been dened
earlier and is typically used by all her basic supplier qualication initiatives.
17. When she has selected the question, she clicks Apply to add it to the area, and then clicks OK to close the
dialog box. The aributes for the question such as revision number, responder type, and whether a response is
required appear in the question table, once the question is added.
18. Clare continues adding questions. She could create a new question at this point by clicking Create and Add ,
but all the questions she needs for this area have already been dened.
19. She denes three possible outcomes that can result from qualications performed using the area: Good,
Satisfactory, and Unsatisfactory.
20. Once Clare is nished creating her new qualication area, she clicks Save and then Activate.
Once all the responders have submied replies, you review each of the responses and either accept it or return it
back to responders. The responders can update their responses and resubmit. Once you view and accept a supplier's
610
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
responses as well as any internal responses associated with the supplier, all qualications for that supplier are in Ready
for Evaluation. During the evaluation step, the designated reviewers view the supplier responses and assign an outcome
value. (You dene the possible outcome values that are available when you dene the qualication model.)When all
qualications are evaluated and nalized, corresponding assessment becomes active.
The table displays qualication model aributes and explains the aribute values.
Name Explanation
Question Model The name of the qualication model you're creating. This name is used as the name of the
assessment.
Revision The number of the current version of this qualication model denition. As changes are made
to the qualication model denition, the Revision number is incremented.
Default Assessment Owner Select a user to set as the default assessment owner for all the accessing procurement BUs
when this qualication model is included in an assessment.
When a default assessment owner is assigned, then all the procurement BUs that have access
to this model will have this user as the default assessment owner unless specied otherwise in
the Business Unit Access or Business Unit Defaults table.
Business Unit Access You can assign a default assessment owner for various business units. When the area isn't
global BU access, you can also add the procurement business units which can use this
qualication model.
Status
Qualication model denitions can be in one of four statuses:
• Draft - the initial denition hasn't yet been activated for use.
• Active - the denition is available for use in initiatives.
• Inactive - the denition is disabled and can't be used. It can be reactivated for use when
necessary.
• Archived - this denition has been superseded by a more recent revision.
Global BU access
These values control who can use this qualication model. The default is for the model to be
available to the procurement business unit of the creator. If you check Global, the qualication
model can be used by all procurement business units in the application. Otherwise, you choose
the procurement business unit which can use this qualication model. You can insert multiple
rows as access procurement BUs.
611
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
Name Explanation
created using the areas in this model can be communicated to a supplier when you nalize the
assessments. You can choose to share:
Qualication Model Level Whether assessments generated using this model apply only at the supplier site level or at
both the supplier and the supplier site level.
Enable scoring If you enable scoring for this qualication model, it must contain at least one qualication area
with scoring dened, and the qualication area must contain at least one question with scoring
dened.
Additionally, you dene the model outcomes in terms of total scores. A model's total score is
the sum of the scores of all the areas in the model. Typically, for each outcome, you specify a
beginning and ending score range.
Automatically evaluate assessment You can also choose to have assessments automatically evaluated. The application uses the
(only available if scoring is enabled) scoring information dened for the model's outcomes to evaluate the assessment.
Supplier Eligibility You can use this qualication model for evaluating and assessing supplier eligibility. Includes
options Sourcing and Share eligibility.
Sourcing You can choose to use this model to assess or evaluate supplier's eligibility for negotiations in
the Sourcing work area at a particular procurement BU.
Share eligibility You can choose to share the supplier eligibility resulting from the assessment outcome with
other Procurement BUs by also updating the supplier's default sourcing eligibility.
Expiration Reminder Sets a future point in time before the qualication expires when the application starts sending
alerts to the qualication manager. The value you set is the default that's used for any
assessment created using this qualication model. The owner of the assessment can override
the value.
Add icon (Qualication Area section) Use the add icon to open a window where you can choose the qualication areas and add them
to your qualication model.
Procurement BU/ Qualication Area Enter the name of a qualication model for which you want to search. You choose the
(Search and Add dialog box) appropriate questions from the search results. When you're returned to the Create
Qualication Model, the qualication areas you chose are displayed. Note that you can update
the question branching for questions in this area if necessary.
612
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
Name Explanation
Display Sequence and Outcome You can dene possible outcomes for your qualication model. Then when evaluators are
viewing a supplier's response, they can assign the response a particular outcome.
From Score/To Score (only available For each outcome, you specify the range of values that include that outcome. Additionally, you
if Enable scoring is selected) identify one outcome to be used as the knockout outcome.
Notify (only available if Automatically If you choose to have assessment automatically evaluated, for each outcome, you can choose
Evaluate Assessment is selected) to have the application send a notication to the assessment owner whenever an assessment
that evaluates to that outcome is received.
613
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
6. If she wants to assess the suppliers' eligibility for negotiations in the Sourcing work area, then she selects the
Supplier Eligibility Sourcing checkbox.
7. Since she chooses which Procurement BUs can use this area, when she creates the initiative, she leaves the
Global box unchecked. Also, she notes that the Qualication Model Level value indicates the model is available
for both supplier and supplier site level areas.
8. Since Clare didn't check the Global check box, she must specify which procurement BUs can use this
qualication model. She clicks select and add icon in the Business Access table. When the Procurement BU
dialog box displays, she searches and selects the names of the BUs that can use this model for qualifying
suppliers. When she is nished listing the BUs, she clicks OK.
9. She can assign a default qualication owner to manage the evaluation.
10. She sets the default expiration reminder value to 30 days. Therefore, for any assessment created using this
model, expiration reminders start going out 30 days before the assessment expires. The assessment owner can
change this value.
11. Now Clare must add her qualication areas to her model, so she clicks the Add icon in the Areas region. When
the Search and Add dialog box appears, she nds and adds an area called Financial Viability. This area has
been dened earlier and is typically used by all supplier qualication initiatives.
12. When she has chosen the area, she clicks Apply to add it to the model, and then clicks OK to close the dialog
box.
13. Clare continues adding areas. She could create and add a new area at this point, but all the areas she needs for
this model have already been dened so she doesn't create any new ones.
14. Once Clare is nished creating her new qualication model, she clicks Save and then Activate.
Rule Sets
Supplier Qualication Rule Sets
Oracle Fusion Procurement provides a functionality that you can use to solicit information from your suppliers at
various points in the supplier's life cycle. You control the content and timing of the questionnaire by dening rule sets.
A rule set consists of one or more qualication areas. The questions dened to these qualication areas are used to
generate a questionnaire and send it to a supplier. After the supplier receives and answers the questionnaire, you can
use the supplier's response information to update the supplier prole information. You can:
• Use existing qualication areas.
• Create qualication areas in Supplier Qualication Management and then use them in your rule set.
If you have to create a qualication area, note that:
◦ The questions must be at the supplier level.
◦ The questions can't include internal responders.
◦ The questions are active.
You can specify a sourcing qualication model for a particular procurement BU to assess a supplier's eligibility to
participate in sourcing negotiations.
When one of the triggering events occurs for which you have dened a rule set, the application creates a questionnaire
consisting of the qualication areas that you identied in your rule set. This questionnaire is what the supplier sees.
When you receive the supplier's response, you use the supplier's basic registration information and questionnaire
responses to evaluate the supplier information with regards to the triggering event.
614
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
When a supplier is approved as a prospective or spend authorized supplier, his responses are stored in the Supplier
Qualication Response Repository. Once the supplier's responses are in the Response Repository, you can use those
responses to create qualications for the supplier.
◦ Oering: Procurement
◦ Functional Area: Supplier Qualication
The application initially selects registration rule set. If you are creating a dierent type of rule set, click the link
for the rule set type. On the Create Rule Set page, enter rule set header information:
◦ Rule Set to specify the set name and optionally enter a description for the set.
◦ Select a Procurement BU.
◦ Whether to allow branching.
◦ Whether to automatically create questionnaires.
If you select this option, qualications are automatically created on the areas that were a part of the
registration questionnaire and the responses provided by the supplier are mapped to the qualication to
make it ready for evaluation.
2. Click Add Condition. On the Add Condition dialog window enter
◦ Supplier Prole Aribute - you select this from the list of prole aributes. You can use this
eld and the following two elds to create a condition based on a supplier prole aribute.
When a response entered by the supplier matches the condition, the qualication area for
this condition are used to generate the questionnaire.
◦ Operator - a relationship operator (=, <, > )
◦ Value - a value appropriate to the supplier prole aribute
3. When you are nished dening the condition, click OK.
4. When you return to the Create Rule Set page, highlight a condition and click Add Qualication Areas. Here you
specify which qualication areas are used when the condition you specied is met:
615
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
if you use a partial search value). Either way, from the search results, highlight the qualication area and
click Apply.
◦ Business Relationship - Prospective or Spend Authorized. You can restrict the use of this condition to the
appropriate business relationship value.
◦ When you are nished adding qualication areas to the condition, click OK.
5. When you are have entered all the information for your rule set, click Save and Activate.
◦ Oering: Procurement
◦ Functional Area: Supplier Qualication
◦ Task: Manage Supplier Qualication Rule Sets
In the Manage Rule Sets page, go to Create Rule Set page. The application defaults to a registration rule
set, so click the link for the registration approval rule set type. On the Create Rule Set page, enter rule set
header information: Rule Set to specify the set name and optionally enter a description for the set. Select a
Procurement BU.
2. Click Add Condition. On the Add Condition dialog menu appears, enter Condition Type. You have two options:
◦ Always displayed - if you choose this option the questions are always included in the questionnaire
created by the application.
◦ Response dependent. - If you choose a response dependent condition, you continue on the Create
Condition pop up and enter:
• Supplier Prole Aribute - you select this from the list of aributes. You can use this eld and the
following two elds to create a condition based on a supplier prole aribute.
• Operator - a logical operator )=, <, >)
• Value - a value appropriate to the supplier aribute. You choose a value from the list of values. The
values you can choose from depend on which aribute you selected.
• Registration Source - you can choose to have the condition apply selectively based on the source
of the registration request:
616
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
You can search by Procurement BU or a qualication area name. A search on Procurement BU returns a list
of qualication areas owned by the BU. A search by qualication area name returns any qualication area
(multiple areas if you use a partial search value).
5. When the search results display, select the row for the qualication area you want to use and click Apply. Note
that you can select multiple qualication areas if needed.
If an icon appears in the Question Branching column for a particular qualication area, it indicates that there
is at least one question in the area that has branching. If you click the icon and follow the navigation, on the
Question Branching page, you can expand the question to see the branching information.
6. When you have nished selecting your qualication areas, click OK.
7. When you have entered the qualication area information for your registration approval rule set you are
creating, click Save and Activate.
617
Oracle Procurement Cloud Chapter 22
Implementing Procurement Supplier Qualication Management
7. When the search results display, select the row for the qualication area you want to use and click Apply. Note
that you can select multiple qualication areas if needed.
8. When you have nished selecting your qualication areas, click OK. You return to the Create Rule Set page.
Question Branching - If an icon appears in the Question Branching column for a particular area, there is at least
one question in the area that has branching. If you click the icon and follow the navigation, on the Question
Branching page, you can expand the question to see the branching information.
9. After you have entered the qualication area information, click Save and Activate.
1. In the Setup and Maintenance work area use the Manage Supplier Qualication Rule Sets task:
◦ Oering: Procurement
◦ Functional Area: Supplier Qualication
◦ Task: Manage Supplier Qualication Rule Sets
618
Oracle Procurement Cloud Chapter 23
Implementing Procurement Procurement Contracts Conguration
619
Oracle Procurement Cloud Chapter 23
Implementing Procurement Procurement Contracts Conguration
of the Contract Terms Library features, including clauses and contract terms templates, you must navigate to the Terms
Library work area. Dashed boxes highlight features that are available only in procurement contracts.
Contract types specify properties of dierent contracts including the type of permied contract lines, party
roles, contract validation checks, and the contract acceptance and signature requirements. For the Contract
Terms Library, you can use the Manage Contract Types task to:
You must enable contract terms authoring for a contract type to use any of the library features for
contracts of that type.
620
Oracle Procurement Cloud Chapter 23
Implementing Procurement Procurement Contracts Conguration
◦ Specify the Oracle BI Publisher layout template that will be used to format the printed contract terms for
contracts of this type.
• Dening Clause Types
If you want to categorize the clauses in the library, select the Manage Contract Clause Types task to set up
clause types.
• Conguring Business Units for Contracts
The use of most of the Contract Terms Library content is restricted to the business unit where you create
it. This includes clauses, contract terms templates, and Contract Expert business rules. Using either the
Specify Customer Contract Management Business Function Properties or the Specify Supplier Contract
Management Business Function Properties tasks, you can:
◦ Enable content adoption between business units and automatic approvals for content
◦ Specify the Contract Terms Library administrator, the employee who will receive approvals and other
notications regarding library content.
◦ Enable the Contract Expert feature for the business unit.
Using Oracle BI Publisher, you can set up layout templates that determine the formaing of clauses, contract
terms template previews, the contract deviations report, and the contract itself.
Download the sample layout templates provided with your application from the Oracle BI Publisher library. You
can copy and edit the sample layout templates and upload them.
Note: For an example on how to use XML to build your own layouts, see the topic Seing Up
Enterprise Contracts - Part 2.
Select the Manage Contract Terms Value Sets task to set up value sets for use in contract terms variables and
Contract Expert questions.
• Specifying the Location of the File Used for Clause Import
You can import legacy clauses into the Contract Terms Library, either from a le or from an interface table
using Oracle Fusion Enterprise Scheduler processes.
If you are importing clauses from a le, then you must specify the location of the le by seing the prole
option Specify Contract Clause Import XML File Location by selecting the Manage Clause and Template
Management Proles task.
• Creating Clauses
Create standard clauses for use during contract terms authoring, including alternate clauses, clauses included
by reference, and provision clauses. By specifying dierent clause properties, you can modify clause behavior.
For example, you can make clauses mandatory in contracts or protect them from editing by contract authors.
• Creating Variables
621
Oracle Procurement Cloud Chapter 23
Implementing Procurement Procurement Contracts Conguration
You can use variables in the Contract Terms Library to represent information within individual clauses and for
use within Contract Expert rule conditions. Your application comes with predened variables, called system
variables. You can create additional variables, called user variables, with or without programming.
• Creating Numbering Schemes
You can set up additional clause and section numbering for contract terms. You can select which numbering
scheme you want to use with each contract terms template.
• Creating Contract Terms Templates
Create contract terms templates to insert boilerplate terms and conditions into contracts during contract
authoring. Contract authors can apply the templates manually, or the application can apply the templates
automatically using default rules you set up.
• Creating Contract Expert Business Rules
Set up business rules that ensure compliance of contracts with corporate standards.
Contract Expert helps you to set up business rules that can:
◦ Apply the appropriate contract terms template to a contract
For example, apply the contract terms template Software License and Service Agreement if the contract
is authored in the North America Operations business unit and the contract amount exceeds one million
dollars.
◦ Insert additional clauses into specic predetermined locations in the contract
For example, add an audit clause if an audit is required.
◦ Report contract deviations from corporate policies
For example, report a contract worth one million dollars or more that includes payment terms greater
than 90 days.
You can base Contract Expert rule conditions on the values of variables in the contract, the presence of other
clauses, or you can set up questions that contract authors must answer during authoring.
For example, you can ask authors a series of questions about the nature of the materials being shipped to
customers and insert additional liability clauses based on their answers.
If you are seing up business rules with numeric conditions (for instance, insert a special payment terms clause
if the contract amount exceeds $1 million) then you must set up constants to hold the numeric values. You
cannot enter the numeric values directly.
• Contract Deliverables
Contract deliverables track both contractual and non-contractual commitments that must be completed as part
of negotiations, purchasing, and enterprise contracts between businesses and suppliers or customers based
on contract intent. These deliverables can be used in purchasing and sourcing documents that include contract
terms and in enterprise contracts.
• Importing Clauses
You can import clauses from legacy applications by running Oracle Fusion Enterprise Scheduler (ESS)
processes from the Terms Library work area by selecting the Import Clauses task or from the Setup Manager
by selecting the Manage Processes task.
• Seing Up and Maintaining the Index for Clause Text Searches Using the Keyword Field
622
Oracle Procurement Cloud Chapter 23
Implementing Procurement Procurement Contracts Conguration
By selecting the Manage Processes task in the Terms Library work area, you can also run the ESS processes
required to set up and maintain the text index required for searches of clauses and contract terms templates
using the Keyword eld.
Related Topics
• How Business Unit Aects Clauses and Other Objects in the Library
• Variables
• Standard clauses
• Clauses included by reference
• Provision clauses for contracts with a buy intent
623
Oracle Procurement Cloud Chapter 23
Implementing Procurement Procurement Contracts Conguration
A mandatory clause is highlighted by a special icon during contract terms authoring and cannot be deleted by
contract authors without a special privilege. You can make a clause mandatory for a particular contract terms
template by selecting the Make Mandatory action after you have added the clause to the template. A clause
is also become mandatory if it is added by a Contract Expert rule and you have selected the Expert Clauses
Mandatory option in the template.
• Protect it from edits by contract authors.
A protected clause is highlighted by a special icon during contract terms authoring and cannot be edited by
contract authors without a special privilege. You can protect any clause by selecting the protected option
during clause creation or editing.
• Specify that a clause can be selected by contract authors as an alternate of another clause.
You can specify clauses to be alternates of each other on the Relationships tab of the create and edit clause
pages. When editing contract terms, contract authors are alerted by an icon that a particular clause includes
alternates and can select an alternate to replace the original clause.
• Specify that the clause cannot be in the same document as another clause
You can use the Relationship tab to specify a clause you are creating is incompatible with another clause in the
library. The application highlights incompatible clauses added by contract authors in the contract deviations
report and during contract validation.
• Make a clause available for use in other business units.
Clauses you create in the library are normally available only within the same business unit where you create
them. If you create the clause in the business unit that is specied as global during business unit setup, then
you can make the clause available for adoption in other business units by selecting the Global option during
clause creation or edit. This option appears only in the one business unit specied as global.
624
Oracle Procurement Cloud Chapter 23
Implementing Procurement Procurement Contracts Conguration
• Can default contract terms directly on purchase orders and sourcing documents, and on enterprise contracts.
For these documents, contact terms templates can also include contract deliverables which can be used to track
the completion of contractual tasks in the contract.
• Set up Contract Expert rules to recommend additional clauses for contracts that use the template and insert
these clauses in specied locations in the contract if marked as conditional.
• Associate a layout template for previewing the template.
• Specify a contract terms numbering scheme for the template.
• Set up template selection rules to default the template into a contract automatically.
625
Oracle Procurement Cloud Chapter 23
Implementing Procurement Procurement Contracts Conguration
The following gure illustrates the dierent aspects of contract terms templates, such as section and clauses, contract
terms deliverables, layout template, numbering scheme and so on.
Layout Template
Sections and Clauses
….
3. Contract Definitions
3.1. Firm Price Clause Numbering Scheme
3.2. Warranty
...
Contract Terms
Deliverables
Adding Sections
You can add sections that you have created in the library or create sections that are specic to the template itself.
Adding Clauses
You can add clauses in one of two ways:
• Add a clause from the Contract Terms Library directly into a section in the template.
626
Oracle Procurement Cloud Chapter 23
Implementing Procurement Procurement Contracts Conguration
You can create the clause in the library from the template if the library does not have what you need.
• Create Contract Expert rules to add clauses to the contract terms in a contract depending on the specics of the
contract.
For example, you may want to add a boilerplate jurisdiction clause directly into the template, but use a Contract Expert
rule to insert the appropriate liability clause. This way a contract that calls for the shipment of hazardous materials will
get a liability clause that's dierent from a contract that does not include any, for example.
The properties that you set up in the clause apply automatically. If you set up a clause as mandatory, you will not be
able to delete the clause after it is inserted by the template unless you have the special Override Contract Terms and
Conditions Controls privilege. If you set up a clause with alternates, then you can substitute any of the alternate clauses
in the contract.
Note: You are not required to add any sections or clauses to a template directly. You can use Contract Expert
rules exclusively, if appropriate.
You can also place recommended clauses for insertion n their predetermined locations, if the clauses are marked as
conditional clauses and their locations are dened in the terms template associated with the contract.
You can use deliverables to record the status of the tasks, keep everyone notied of past and future deadlines, and as a
repository of the deliverable documents themselves. For example, vendors agreeing to supply a monthly report can log
in to their sourcing portal and aach the report or ask for an extension. If they fail to respond by the specied deadline,
the deliverable can trigger an automatic notication that the deliverable is overdue.
If you marked Contract Expert recommended clauses as conditional on the terms template, then these are displayed in
gray font in the print preview to distinguish them from regular clauses.
627
Oracle Procurement Cloud Chapter 23
Implementing Procurement Procurement Contracts Conguration
The layout template is an RTF le stored in the Enterprise Contracts folder in the Business Intelligence Presentation
Catalog. A sample layout template is provided with your application. You can copy the sample template and edit it to
create your own as described in a related topic.
If you enabled the feature Enable Contract Terms in Oracle Fusion Procurement for Procurement Contracts during
implementation, then you can also apply templates to procurement documents based on document type.
While editing the contract terms template, you specify a template to be the default for a contract type or document type
in the Document Types region. You can set up only one template as the default for each contract type or document
type. You set up the Contract Expert template selection rules separately as described in a related topic. You can have
multiple rules recommend the same template.
Here is how the default values you enter in the Document Types region and the Contract Expert template selection rules
interact to select and apply a template during contract authoring:
• Contract Expert template selection rules always take priority. If the rules specify a single template for a contract,
then it is applied regardless of the default you entered in the Document Type region.
• If the Contract Expert rules recommend dierent templates, then the application uses the default from the
Document Type region as a tiebreaker.
• If no Contract Expert selection rule applies and you specied a default, then the application uses the default.
• If you did not set up any rule or default for a contact type or document type, then you must select the template
from a list while authoring.
Related Topics
• How You Activate and Revise Contract Terms Templates
628
Oracle Procurement Cloud Chapter 23
Implementing Procurement Procurement Contracts Conguration
Each rule comprises conditions that must be met and the rule results. You can base rule conditions on:
Dierent Contract Expert rule types support dierent condition types, as illustrated in the following gure.
• Clause selection rules, which can default individual clauses and sections into a contract, can be based on
clauses, questions, and variables.
• Template selection rules, which identify the default contract terms template for the contract, can be based on
variables only.
• Policy deviation rules, which identify contract deviations from company policies, use questions and variables
only.
629
Oracle Procurement Cloud Chapter 23
Implementing Procurement Procurement Contracts Conguration
The following gure illustrates the Clause Selection, Template Selection, and Policy Deviation Contract Expert rules.
Contract Expert
Contract Terms
Clause Selection Rule
Section 1
Clause 1.1
Clauses Clause 1.2
Questions Section 2
Insert clause
Clause 2.1
Variables Section 3
Clause 3.1
Clause 3.2
630
Oracle Procurement Cloud Chapter 23
Implementing Procurement Procurement Contracts Conguration
◦ IS NOT
◦ IN (allows the selection of multiple values)
◦ NOT IN (allows the selection of multiple values)
◦ >=: (greater than or equal to)
◦ <=: (less than or equal to)
◦ =: (equal to)
◦ > (greater than)
◦ < (less than)
Rule outcomes
The rule can:
When the rule is evaluated The rule is evaluated every time that a user runs Contract Expert.
Users receive a warning message during contract validation if they fail to run Contract Expert.
631
Oracle Procurement Cloud Chapter 23
Implementing Procurement Procurement Contracts Conguration
Conditions
Conditions can be based on:
• clauses
• questions
• variables
You can use both predened system variables and user variables. Both types of user
variables are supported: those that require entry by contract authors and those where
the values are supplied by a Java procedure.
Where it applies
The rule applies only within the business unit and for the intent that you specify. You can have
the rule apply to one of the following:
Rule outcomes The application automatically applies a contract terms template to a contract. Or, if the author
removed the contract terms using the Actions menu, the template displays the template name
as the default when applying a new template.
The rule is also evaluated to determine if the contract contains the recommended template
whenever the contract author:
In both cases, the rule generates a warning if the author applied a dierent template from that
recommended by the rule.
Where it applies The rule applies only within the business unit and for the intent specied in the rule.
632
Oracle Procurement Cloud Chapter 23
Implementing Procurement Procurement Contracts Conguration
Contract Expert doesn't apply a contract terms template if the contract terms template default rules you set up
recommend multiple terms templates for a single contract. Instead, Contract Expert applies the contract terms template
specied as the default for the business document type during contract terms template setup. If no document type
default is specied, then the application displays the Add Contract Terms buon and permits authors to select a
template of their own choice. The choices are restricted to the templates specied for the contract type.
The following gure describes choosing a contract terms template for application to a contract.
No
Default template
specified for Yes
document type?
Contract
No
633
Oracle Procurement Cloud Chapter 23
Implementing Procurement Procurement Contracts Conguration
Rule results The rule displays a deviation in the contract deviations report.
The rule name becomes the deviation.
Conditions
Conditions can be based on:
• Questions
• Variables
Both predened system variables and those user-dened variables where the values are
supplied by a Java procedure.
Where it applies The rule applies only for the contract terms templates within the business unit and for the
intent that you specify.
You can build rule conditions out of both questions and variables. In the contract deviation report, your entry in the
Rule Name eld becomes the deviation name and your entry in the rule Description eld becomes the deviation
description.
634
Oracle Procurement Cloud Chapter 23
Implementing Procurement Procurement Contracts Conguration
Questions
Clause Deviations
Variables
Policy deviation rules list policy deviations in the contract deviations report, along with any clause deviations that are
identied automatically by the application. Contract authors can run the report before submiing the contract for
approval and enter comments to explain the deviation to the approver. The report is rerun automatically when the
author submits the contract for approval and a copy of the report is aached to the approval notication.
Note: To activate a rule, you must assign it to at least one contract terms template. The template doesn't
have to be approved at the time that you make the assignment, but it does have to be approved before the
rule can be used.
Activating a rule triggers an automatic validation process. You must correct all errors before the rule gets activated.
Related Topics
• Examples of Contract Expert Clause Selection Rules and Follow-up Questions
• Contract Expert Rule Statuses and Available Actions
• How Contract Expert Works
• How can I predene locations of Contract Expert clauses in the contract
• How does Contract Expert identify where to insert clauses into contracts
635
Oracle Procurement Cloud Chapter 23
Implementing Procurement Procurement Contracts Conguration
636
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
24 External Integration
Web Services
Overview of Web Services
Use web services to integrate web-based applications into your Oracle Applications Cloud. Web services expose
business objects and processes to other applications using open standards-based technologies.
Web services support development environments and clients that comply with these open standards:
• Extensible Markup Language (XML)
• Simple Object Access Protocol (SOAP)
• Business Process Execution Language (BPEL)
• Web Services Description Language (WSDL)
• XML Schema Denitions (XSD)
ADF services
ADF services usually represent business objects, such as employees or purchase orders. You
can use these services to expose standard operations, such as create, update, and delete.
However, for locally-persisted objects, ADF services aren't limited to these operations.
Here are a few examples of ADF services and what they're used for:
• Worker.changeHireDate - Use to update the hire date of the worker business object.
• ProjectTask.createTask - Use to adds a task to the project task business object.
Composite services
Composite services usually represent end-to-end business process ows that act on business
events produced by the ADF services. You can use these services to manage multiple object-
based services, rules services, and human workows. Here are a few examples of composite
services and what they're used for:
For more information about web services, see the SOAP Web Services guide for your cloud services.
637
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
Developer Connect
Overview of Developer Connect
The Developer Connect portal provides information about the web services deployed to your Oracle Applications Cloud
instance. You can use this information to integrate with or extend Oracle Applications Cloud and develop solutions to
suit your business requirements.
To use the Developer Connect portal, your job role must have the FND_INTEGRATION_SPECIALIST_JOB,
FND_APPLICATION_DEVELOPER_JOB, or ZCA_CUSTOMER_RELATIONSHIP_MANAGEMENT_APPLICATION_ADMINISTRATOR_JOB privilege.
Alternately, you can grant the ATK_WEB_SERVICE_INFO_ACCESS_PRIV entitlement to your custom role, and then grant the
custom role to users who require access. For more information, see the security guide for the appropriate cloud service
at Oracle Help Center (hps://docs.oracle.com).
To open the Developer Connect portal, from the Navigator menu, select Tools - Developer Connect. This portal
displays dynamic information of the web services, and the modications done to web services to integrate with Oracle
Applications Cloud. You can synchronize the Developer Connect portal with your cloud instance to retrieve the latest
web service information such as service aributes, operations, business objects, security policies, and WSDL les.
• View the summary of the web service information such as the business object that the service denes, life cycle
status, and security policy.
• Discover the operations available for the selected web service, and the request and response payloads for each
operation.
• View the hierarchy of the service data objects and know information such as the data type and whether it's a
required eld for user-dened aributes.
• Review the sample payload XMLs for the operations of the web service. You can add or edit sample payloads,
and also delete user-dened sample payloads.
Note: You must use the active version of the service. If you were previously using a service that has
been deprecated, then migrate to the new, active version.
638
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
1. On the Web Service overview page, select Help Topic Abstract Service.
2. On the Summary page of the web service, click the Sample Payloads tab and select getEntityList operation.
3. In the Edit Sample Payload dialog box, edit the payload XML and click OK.
1. On the Web Service overview page, select Help Topic Abstract Service.
2. On the Summary page of the web service, click the Sample Payloads tab and select getEntityList operation.
3. Click the delete icon for the selected operation and click OK.
639
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
1. On the Web Services overview page, select Manage File Import and Export Service. The Summary panel shows
information such as the display name, business object that the service denes, life cycle status, QName,
security policy used, and a brief overview of the service.
2. Click the Operations tab to view the operations supported by the web service.
3. Click the uploadFiletoUCM operation and review the result parameter in the response payload. This parameter
holds the le ID in the WebCenter Content repository from which the value set values are imported.
4. Click the valueSetValuesDataLoader operation and review the fileIdAtRepository parameter in the request
payload. This parameter holds the le ID in the WebCenter Content repository.
5. Click WSDL File link of the service to download the web service information.
1. Click the Sample Payloads tab and then click Add Sample Payload.
2. Select uploadFiletoUCM from the operation name list.
3. Enter a brief description of the payload in the description text box.
4. Add the payload to get the le ID from the WebCenter Content repository:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<ns1:uploadFiletoUCM
xmlns:ns1="http://xmlns.oracle.com/oracle/apps/fnd/applcore/webservices/types/"
ns2="http://xmlns.oracle.com/oracle/apps/fnd/applcore/webservices/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ns1:document xsi:type="ns2:DocumentDetails">
<ns2:fileName>VS123.txt</ns2:fileName>
<ns2:contentType>plain/text</ns2:contentType> <ns2:content>
VmFsdWVTZXRDb2RlfEluZGVwZW5kZW50VmFsdWV8SW5kZXBlbmRlbnRWYWx1ZU51bWJlcnxJbmRlcGVuZGVudFZhbHVlRGF0ZXxJbmRlcGVuZGVud
QX R0cmlidXRlNH
xDdXN0b21WYWx1ZUF0dHJpYnV0ZTV8Q3VzdG9tVmFsdWVBdHRyaWJ1dGU2fEN1c3RvbVZhbHVlQXR0cmlidXRlN3xDdXN0b21WYWx1ZUF0dHJpYn
Hx 8fHx8fHx8fHw K
UkVMN19CNl9WU19OVU1fSU5EfHx8fHwyMDAwfHx8fHxUZXN0aW5nIGZvciBCdWcgMTczNzU2ODR8WXwyMDExLTEwLTAxfDIwMTItMTAtMzB8Mnx8
8f Hx8fHx8fHx8f H
x8fHx8fHx8fHx8fHx8fApSRUw3X0I2X1ZTX0RBVEVfSU5EfHx8fHx8fDIwMzAtMDEtMDJ8fHxUZXN0aW5nIGZvciBCdWcgMTczNzU2ODQtMXxZfD
UV fREVQfDIwMzE t
MDMtMDEgMDE6MDA6MDAuMDB8fHwyMDMxLTAzLTAxIDAxOjAwOjAwLjAwfDIwMzEtMDMtMDEgMDE6MDE6MDAuMDB8fHwyMDMxLTAzLTAxIDAxOjAx
</ns1:content>
<ns2:documentAccount>fin$/tax$/import$</ns2:documentAccount>
<ns2:documentTitle>VS</ns2:documentTitle>
</ns2:document>
</ns1:uploadFiletoUCM>
</soap:Body>
</soap:Envelope>
5. Click OK.
6. Select valueSetValuesDataLoader from the operation name list.
7. Enter a brief description of the payload in the description text box.
8. Add the payload to read the contents from the le and import the value set values:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
640
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
<ns1:valueSetValuesDataLoader
xmlns:ns1="http://xmlns.oracle.com/oracle/apps/fnd/applcore/webservices/types/">
<ns1:fileIdAtRepository>1234</ns1:fileIdAtRepository>
</ns1:valueSetValuesDataLoader>
</soap:Body>
</soap:Envelope>
Message Paerns
All operations exposed on a business object service have both synchronous and asynchronous message paerns
dened. For conciseness, the service documentation includes the denition for the synchronous message paern
only. Both synchronous and asynchronous operations have the same functional behavior, and request and response
payloads. Custom object services don't have corresponding asynchronous operations.
Using Help Topic Abstract Service as an example, if the name of the synchronous operation is getEntityList, the
asynchronous operation name and callback name would be getEntityListAsync and getEntityListAsyncResponse.
CORS
Cross-Origin Resource Sharing (CORS) is a mechanism that allows cross-domain communication and lets a browser
securely access resources from a dierent domain. By default, browser-based programming languages, such as
JavaScript, can access resources only from the same domain. But with CORS, you can overcome this limitation and
manage resources across domains.
Here are the CORS headers you can congure to make that possible.
Access-Control-Allow-Origin Contains a comma-separated list of trusted origins, or domains, that a client application can
get resources from.
Access-Control-Max-Age Species how long to store the results of a request in the preight result cache.
Access-Control-Allow-Credentials Species whether a client application can send user credentials with a request.
641
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
Example
A client application retrieves resource X from server A, which is what the application runs on. The client application then
makes an HTTP request to get resource Y from server B. For this cross-server request to work, you must congure the
Access-Control-Allow-Origin header in server B. Otherwise, the request fails and we end up with an error message.
Related Topics
• Set Prole Option Values
CORS Header Prole Option Name (Prole Option Prole Option Values
Code)
Access-Control-Max-Age CORS: Access-Control-Max-Age (CORS_ Default value for caching preight request
ACCESS_ CONTROL_ MAX_AGE) is 3600 seconds.
642
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
CORS Header Prole Option Name (Prole Option Prole Option Values
Code)
Related Topics
• Set Prole Option Values
Job Denitions
A job denition contains the metadata that determines how a scheduled process works and what options are available
during submission.
◦ Manage Enterprise Scheduler Job Denitions and Job Sets for Financial, Supply Chain Management, and
Related Applications
◦ Manage Enterprise Scheduler Job Denitions and Job Sets for Human Capital Management and Related
Applications
◦ Manage Enterprise Scheduler Job Denitions and Job Sets for Customer Relationship Management and
Related Applications
3. In the Manage Job Denitions tab, select your job denition and click Edit.
643
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
Security
Privileges provide the access required to run specic scheduled processes. Privileges are granted to duty roles, which
are granted to job roles. To see which job roles inherit the required privileges, use the Security Console or the security
reference manuals for the appropriate product family.
• Information or assistance regarding general access to content management (including all metadata)
• Creating and managing accounts
• Programmatically uploading and downloading content
644
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
File Size
Upload and download don't apply the following by default:
• Data compression
• File spliing
The UPLOAD_MAX_DISK_SPACE parameter in the web.xml le determines the maximum allowable le size in content
management. The default maximum size is 10240000 (10MB).
Dening Security
You require the File Import and Export Management duty role for accessing the File Import and Export page. This duty
role is included in the predened role hierarchy for integration specialist roles and product family administrator roles.
Files in Oracle WebCenter Content are associated with an account so that only users having access to that account can
work with those les. Account names are unique and each account is treated as discrete by access control. You can
only upload and download les to and from content repositories that are linked to the accounts you can access. The
underlying integrated content management handles security tasks such as virus scanning.
Searching Records
A record in Oracle WebCenter Content contains the metadata used for accessing the le. When a scheduled process is
run on a le, the record for the le is assigned a process ID.
645
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
• End the name with a dollar sign ($) to avoid partial string matching.
• Use dollar sign and slash ($/) as a separator in the hierarchical structure.
For example: fin$/journal$/import$ The File Import and Export page transforms account names by removing the dollar
sign ($) separators. For example fin$/journal$/import$ appears as fin/journal/import. The Remote Intradoc Client
(RIDC) HTTP command-line interface (CLI) transforms the account name you specify without the dollar sign ($) to one
that includes the sign. For example, n/journal/import becomes fin$/journal$/import$ in WebCenter Content.
Deleting Files
You can delete one le at a time when you use the File Import and Export page. To delete multiple les simultaneously
from the content repository, use the standard service page in Oracle WebCenter Content.
Related Topics
• Document Transfer Utility
External Data Integration Services for Oracle Cloud include the following components:
• Templates to structure, format, and generate the data le according to the requirements of the target
application tables.
• File-based load process to load the data les into the interface tables.
• Application-specic data import processes to transfer data from interface tables to the application tables in
your Oracle Fusion Applications.
646
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
The following ow diagram outlines the steps involved in loading data from external sources.
Upload file to
Download the
Prepare data file Universal Load data to
File Import
using template Content interface table
template
Management
Correct data in
Yes interface table
Errors using ADFdi
spreadsheet
No
Data successfully
uploaded to product
tables
For further information, see Using External Data Integration Services for Oracle ERP Cloud (2102800.1) on My Oracle
Support at hps://support.oracle.com.
Related Topics
• Using External Data Integration Services for Oracle ERP Cloud
• Downloading templates
• Preparing data using the XLS template
647
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
Downloading Templates
To download the templates:
1. Open the File Based Data Import guide for your cloud service.
2. Locate the import process.
3. View the list of les.
◦ Control les describe the logical ow of the data load process.
◦ XLSM templates include the worksheets and macros for structuring, formaing, and generating your
data le.
Note: You can use XML templates to import data into Oracle Data Integrator.
4. Click the template link in the File Links table to download the le. For example, click
JournalImportTemplate.xlsm in the Journal Import topic.
1. Open the XLS template. The rst worksheet in each le provides instructions for using the template.
Note: If you don't follow the instructions, you get data load errors and data import failures.
The macro generates a comma-separated values (CSV) le and compresses the le into a ZIP le. You must
transfer the ZIP le to the content management server.
◦ Integration projects
◦ Content management document transfer utility
7. Execute the package. The package generates the CSV le and compresses it into a ZIP le.
Related Topics
• Document Transfer Utility
648
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
Template Structure
The integration templates include the following characteristics:
The worksheet columns appear in the order that the control le processes the data le.
For more information on the template structure, see the Instructions and CSV Generation worksheet in the template.
Template Requirements
To minimize the risks of an unsuccessful data load, ensure the following:
Caution: Deleting or reordering columns causes the load process to fail and results in an
unsuccessful data load.
• External data must conform to the data type accepted by the control le and process for the associated
database column.
• Date column values must appear in the YYYY/MM/DD format.
• Amount column values can't have separators other than a period (.) as the decimal separator.
• Negative values must be preceded by the minus (-) sign.
• Column values that require whole numbers include data validation to allow whole numbers only.
• For columns that require internal ID values, refer to the bubble text for additional guidance about nding these
values.
After you nish preparing the data in the sheet, click the Generate CSV File buon to generate a ZIP le containing one
or more CSV les.
649
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
The File Based Data Import guides in the Oracle Help Center (hps://docs.oracle.com) include three types of XML
templates that you import as target models in your Oracle Data Integrator repository:
• Family level
• Product level
• Product
650
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
• Import each product XML le one time. The model is based on File technology.
• Select Synonym Mode Insert Update as the import type.
• After you import the product model, connect the model to the correct logical schema.
Related Topics
• Use XML Templates to Generate Data Files for Integration
• Document Transfer Utility
Related Topics
• Document Transfer Utility
651
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
Parameters
Import Process
Data le
Enter the relative path and the le name of the *.zip data le in the content repository.
Related Topics
• Document Transfer Utility
Note: The data le remains in the content repository after the process ends.
652
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
Note: For more information on the process used for data prepared using the spreadsheet template, see the
Instructions and CSV Generation tab of the spreadsheet template.
Related Topics
• Document Transfer Utility
653
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
Run the import process to import purchase orders, blanket agreements, or contract agreements into the application for
further processing.
You can query, modify and validate successfully imported documents. During import, records that have insucient
or invalid data are rejected. You can use an automatically produced report to review the documents that couldn't be
imported. You can resubmit the import task after making corrections to rejected documents.
How You Import Extended Item Aributes and Translations into Blanket Agreements
You can import rich catalog content data such as thumbnail images, image URLs, item availability and lead time
information, and other extended item aributes into blanket agreements using le-based data import. You can also
import extended item aribute translations such as item description, item manufacturer, comments and so on.
Note: You can load data to interface tables using predened templates and the Load Interface File for
Import scheduled process. Both are part of the External Data Integration Services for Oracle Cloud. For other
implementations, optionally use this feature only if you have SFTP congured for it.
For more information refer to the File-Based Data Import for Oracle Procurement Cloud guide on the Oracle Help
Center.
Limitations
File-based data import doesn't support the creation or update of purchasing documents with more than 10,000
distributions. Exceeding 10,000 distributions can cause performance issues and could lead to failures.
654
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
1. From the Purchase Agreements or Purchase Orders work area, open the appropriate task you want to use:
◦ Import Orders
◦ Import Blanket Agreements
◦ Import Contract Agreements
2. Depending on the purchase document import task you're using, you can set one or more selection parameters
before running the process. The following table lists some of the possible selection parameters and their
descriptions.
Parameter Description
Procurement BU Specify the name of the Procurement business unit that these documents should be
imported into.
Default Buyer Specify the name of the buyer to be used when one isn't included in the import data.
Create or Update Item Select "Yes" to create an item that doesn't exist or update an existing item.
Approval Action
Select one of the following actions:
Batch ID Enter the value for your import data from the le-based data import template, to select the
interface table data to be processed in the current run. For example: Batch ID = 123. Use it
in conjunction with Import Source to identify the documents to be loaded to the application
tables.
Import Source Enter the value for your import data from the le-based data import template, to select
the interface table data to be processed in the current run. For example: Import Source
= External Contracts. Use it in conjunction with Batch ID to identify the documents to be
loaded to the application tables.
Default Requisitioning BU Specify the name of the Requisitioning business unit to be used when one isn't included in
the import data.
Communicate Orders, or Select Yes to have imported purchasing documents communicated to the supplier.
Communicate Agreements
Select No to not have imported purchasing documents communicated to the supplier.
655
Oracle Procurement Cloud Chapter 24
Implementing Procurement External Integration
3. When the processes are complete, view the output report in PDF format. The report details the status of the
records that were imported. If a record couldn't be imported, then the Status is set to Rejected with a reason for
the rejection.
4. Fix the problems that are identied in the report and then resubmit the import task.
Related Topics
• Examples of Purchase Order Line Types
Deep Links
You can use deep links to open pages without navigating through the menu structure. Deep links come in handy if you
have corporate internal portals and you want to enable direct navigation from the portals to Oracle Applications Cloud.
For example, you can enable direct navigation to the My Team page. Use the Deep Links work area to view a complete
list of the available deep links.
You can simply copy a URL from the Deep Links page and paste it in your external portals as is. You don't even need to
know the URL format.
656
Oracle Procurement Cloud Chapter 25
Implementing Procurement Importing and Exporting Setup Data
Parameters
The common reference objects are represented as business objects. A single object can be referenced in multiple
setup tasks with dierent parameters. In the conguration package created for the implementation project, parameters
passed to a setup task are also passed to the business objects being moved. As a result, the scope of the setup tasks is
maintained intact during the movement.
Dependencies
Common reference objects may have internal references or dependencies among other common reference objects.
Therefore, you must note all the dependencies before moving the objects so that there are no broken references among
them.
Related Topics
• Overview of Setup Data Export and Import
• Setup Data Export and Import Using an Oering or a Functional Area
Choice of Parameters
The following table lists the business objects, the movement details, and the eect of the setup task parameter on the
scope of the movement.
Note:
• You can move only the translations in the current user language.
• You can move the Oracle Social Network business objects and the changes to the Navigator using the
conguration sets on the Conguration Set Migration page.
657
Oracle Procurement Cloud Chapter 25
Implementing Procurement Importing and Exporting Setup Data
Business Object Name Moved Functional Item Eect on the Scope of Movement
Application Message Messages and associated tokens No parameters: All messages are moved.
Parameter moduleType/ moduleKey
Only messages belonging to the specied
module and its descendant modules in the
taxonomy hierarchy are moved.
Parameter messageName/ applicationId
Only the specied message is moved.
Application Taxonomy Application taxonomy modules and No parameters: All taxonomy modules
components and components are moved.
Application Aachment Entity Aachment entities No parameters: All aachment entities are
moved.
Parameter moduleType/ moduleKey
Only aachment entities belonging to
the specied module and its descendant
modules in the taxonomy hierarchy are
moved.
Application Aachment Category Aachment categories and category-to- No parameters: All aachment categories
entity mappings and category-to-entity mappings are
moved.
Parameter moduleType/ moduleKey
Only aachment categories belonging to
the specied module and its descendant
modules in the taxonomy hierarchy along
with the respective category-to-entity
mappings are moved.
Application Document Sequence Category Document sequence categories No parameters: All categories are moved.
Parameter moduleType/ moduleKey Only
categories belonging to the specied
module and its descendant modules in the
taxonomy hierarchy are moved.
Parameter code/ applicationId Only the
specied document sequence category
code is moved.
Application Document Sequence Document sequences and their No parameters: All sequences are moved.
assignments
Parameter moduleType/ moduleKey
Only document sequences belonging to
the specied module and its descendant
modules in the taxonomy hierarchy are
moved
Parameter name: Only the specied
document sequence is moved.
658
Oracle Procurement Cloud Chapter 25
Implementing Procurement Importing and Exporting Setup Data
Business Object Name Moved Functional Item Eect on the Scope of Movement
Application Descriptive Flexeld Descriptive exeld registration data and No parameters: All descriptive exelds
setup data are moved.
Parameter moduleType/ moduleKey
Only descriptive exelds belonging to
the specied module and its descendant
modules in the taxonomy hierarchy are
moved.
Parameter descriptiveFlexeldCode/
applicationId Only the specied
descriptive exeld is moved. Importing
the metadata of a exeld can change
its deployment status. Therefore,
you must redeploy if there are any
aected exelds. The import process
automatically submits aected exelds
for redeployment. Also only exelds
with a deployment status of Deployed or
Deployed to Sandbox are eligible to be
moved.
Application Extensible Flexeld Extensible exeld registration data and No parameters: All extensible exelds are
setup data, including categories moved
Parameter moduleType/ moduleKey
Only extensible exelds belonging to
the specied module and its descendant
modules in the taxonomy hierarchy are
moved.
Parameter extensibleFlexeldCode/
applicationId Only the specied extensible
exeld is moved. Importing the metadata
of a exeld can change its deployment
status and therefore, the aected
exelds must be redeployed. The import
process automatically submits aected
exelds for redeployment.
Also, only exelds with a deployment
status of Deployed or Deployed to
Sandbox are eligible to be moved.
Application Key Flexeld Key exeld registration data and setup No parameters: All key exelds are
data moved.
Parameter moduleType/ moduleKey Only
key exelds belonging to the specied
module and its descendant modules in the
taxonomy hierarchy are moved.
Parameter keyFlexeldCode/ applicationId
Only the specied key exeld is moved.
Importing the metadata of a exeld
can change its deployment status and
therefore, the aected exelds must
be redeployed. The import process
659
Oracle Procurement Cloud Chapter 25
Implementing Procurement Importing and Exporting Setup Data
Business Object Name Moved Functional Item Eect on the Scope of Movement
Application Flexeld Value Set Value set setup data No parameters: All value sets are moved.
Parameter moduleType/ moduleKey
Only value sets belonging to the specied
module and its descendant modules in the
taxonomy hierarchy are moved.
Parameter valueSetCode: Only the
specied value set is moved.
Importing the metadata of a value set
can change the deployment status of
exelds that use the value set. Therefore,
you must redeploy if there are any
aected exelds. The import process
automatically submits aected exelds
for redeployment.
Application Reference Currency Currency data No parameters: All currencies are moved.
Application Reference ISO Language ISO language data No parameters: All ISO languages are
moved.
Application Reference Industry Industry data including industries in No parameters: All industries are moved.
territories data
Application Reference Language Language data No parameters: All languages are moved.
Application Reference Natural Language Natural language data No parameters: All natural languages are
moved.
Application Reference Territory Territory data No parameters: All territories are moved.
Application Reference Time zone Time zone data No parameters: All time zones are moved.
Application Standard Lookup Standard lookup types and their lookup No parameters: All standard lookups are
codes moved.
Parameter moduleType/ moduleKey
Only standard lookups belonging to the
specied module and its descendant
modules in the taxonomy hierarchy are
moved.
660
Oracle Procurement Cloud Chapter 25
Implementing Procurement Importing and Exporting Setup Data
Business Object Name Moved Functional Item Eect on the Scope of Movement
Application Common Lookup Common lookup types and their lookup No parameters: All common lookups are
codes moved.
Parameter moduleType/ moduleKey
Only common lookups belonging to the
specied module and its descendant
modules in the taxonomy hierarchy are
moved.
Parameter lookupType: Only the specied
common lookup is moved.
Application Set-Enabled Lookup Set-enabled lookup types and their lookup No parameters: All set-enabled lookups
codes are moved.
Parameter moduleType/ moduleKey
Only set-enabled lookups belonging to
the specied module and its descendant
modules in the taxonomy hierarchy are
moved.
Parameter lookupType: Only the specied
set-enabled lookup is moved.
Application Prole Category Prole categories No parameters: All prole categories are
moved.
Parameter moduleType/ moduleKey Only
categories belonging to the specied
module and its descendant modules in the
taxonomy hierarchy are moved.
name/ applicationId Only the specied
category is moved.
Application Prole Option Prole options and their values No parameters: All prole options and
their values are moved.
Parameter moduleType/ moduleKey Only
prole options and their values belonging
to the specied module are moved.
Parameter proleOptionName: Only the
specied prole option and its values are
moved.
Application Prole Value Prole options and their values No parameters: All proles and their
values are moved.
Parameter moduleType/ moduleKey Only
proles and their values belonging to the
specied module are moved.
661
Oracle Procurement Cloud Chapter 25
Implementing Procurement Importing and Exporting Setup Data
Business Object Name Moved Functional Item Eect on the Scope of Movement
Parameter categoryName/
categoryApplicationId Only proles and
their values belonging to the specied
category are moved.
Parameter proleOptionName: Only the
specied prole and its values are moved.
Application Reference Data Set Reference data sets No parameters: All sets are moved.
Application Reference Data Set Reference data set assignments Parameter determinantType: Only
Assignment assignments for the specied determinant
type are moved.
Parameter determinantType/
referenceGroupName Only assignments
for the specied determinant type and
reference group are moved.
Application Tree Structure Tree structures and any labels assigned to No parameters: All tree structures (and
the tree structure their labels) are moved.
Parameter moduleType/ moduleKey Only
tree structures (and their labels) belonging
to the specied module are moved.
Parameter treeStructureCode: Only the
specied tree structure (with its labels) is
moved.
Application Tree Tree codes and versions No parameters: All trees are moved.
Parameter moduleType/ moduleKey Only
trees belonging to the specied module
are moved.
Parameter treeStructureCode: Only trees
belonging to the specied tree structure
are moved.
Parameter TreeStructureCode/ TreeCode
Only trees belonging to the specied tree
structure and tree code are moved.
Application Tree Label Tree structures and any labels assigned to No parameters: All tree structures (and
the tree structure their labels) are moved.
Parameter moduleType/ moduleKey
Only tree structures (and their labels)
belonging to the specied module and
its descendant modules in the taxonomy
hierarchy are moved.
Parameter treeStructureCode: Only the
specied tree structure (with its labels) is
moved.
662
Oracle Procurement Cloud Chapter 25
Implementing Procurement Importing and Exporting Setup Data
Business Object Name Moved Functional Item Eect on the Scope of Movement
Application Data Security Policy Database resources, actions, conditions, No parameters: All database resources/
and data security policies actions/ conditions/ policies are moved.
Parameter moduleType/ moduleKey Only
database resources/ actions/ conditions/
policies belonging to the specied module
and its descendant modules in the
taxonomy hierarchy are moved.
Parameter objName: Only the specied
database resource along with its actions/
conditions/ policies is moved.
If the policies being moved contain
reference to newly created roles, move
the roles before moving the policies.
If the source and target systems use
dierent LDAPs, manually perform the
GUID reconciliation after moving the data
security policies.
Dependencies
The dependencies among the common reference objects may be caused by any of the following conditions.
• Flexeld segments use value sets
• Value sets may make use of standard, common, or set-enabled lookups
• Key exelds may have an associated tree structure and key exeld segments may have an associated tree
code
• Tree codes and versions may be dened over values of a value set
• Data security policies may be dened for value sets that have been enabled for data security
You may decide to move one, some, or all of the business objects by including the ones you want to move in your
conguration package. For example, you may decide to move only value sets, or move both value sets and their lookups
as part of the same package. Whatever be the combination, Oracle recommends that during the movement of objects,
you follow an order that maintains the dependencies among the objects.
663
Oracle Procurement Cloud Chapter 25
Implementing Procurement Importing and Exporting Setup Data
4. Move created ISO languages before moving any objects that reference them, such as languages, natural
languages, and industries.
5. Move created tree structures before moving any objects that reference them, such as trees or tree labels.
6. Move created prole options before moving any objects that reference them, such as prole categories or
prole values.
7. Move created aachment entities before moving any objects that reference them, such as aachment
categories that reference them.
Note: In scenarios where there may be dependencies on other objects, you must move the dependencies
before moving the referencing object. For example, if data security policies have dependencies on newly
created security roles, you must move the security roles before moving the security policies.
Movement Dependencies
The seed data interface moves only the setup metadata. For example, if you use Seed Data Framework to import
exeld metadata, the exeld setup metadata is imported into your database. However, you must initiate the exeld
deployment process separately after seed data import to regenerate the runtime exeld artifacts in the target
environment. Similarly, if you use Seed Data Framework to import data security metadata, you must rst move any new
referenced roles and then manually run the GUID reconciliation where required.
To ensure that the reference data isn't lost during the movement, certain guidelines are prescribed. It's recommended
that you perform the movement of object data exactly in the following order:
1. Move created taxonomy modules before moving any objects that reference them, such as exelds, lookups,
proles, aachments, reference data sets, document sequences, messages, and data security.
2. Move created currencies before moving any objects that reference them, such as territories.
3. Move created territories before moving any objects that reference them, such as languages and natural
languages.
4. Move created ISO languages before moving any objects that reference them, such as languages, natural
languages, and industries.
5. Move created tree structures before moving any objects that reference them, such as trees or tree labels.
6. Move created prole options before moving any objects that reference them, such as prole categories or
prole values.
7. Move created aachment entities before moving any objects that reference them, such as aachment
categories that reference them.
8. Move created reference data sets before moving any objects that reference them, such as reference data set
assignments and set-enabled lookups.
9. Move created document sequence categories before moving any objects that reference them, such as
document sequences.
10. Move created tree labels before moving any objects that reference them, such as trees.
11. Move created data security objects and policies before moving any objects that reference them, such as value
sets.
664
Oracle Procurement Cloud Chapter 25
Implementing Procurement Importing and Exporting Setup Data
12. Move created value sets before moving any objects that reference them, such as exelds.
13. Move created trees before moving any objects that reference them, such as key exelds.
665
Oracle Procurement Cloud Chapter 25
Implementing Procurement Importing and Exporting Setup Data
666
Oracle Procurement Cloud Chapter 26
Implementing Procurement Supply Chain Management Integration
• In the Order Creation Controls section, optionally select the check boxes to automatically create purchase
orders from requisitions.
• Aach the work denition document to the agreement line for the item, using the To Supplier category.
For more information about contract manufacturing, see the Oracle SCM Cloud Implementing Manufacturing and
Supply Chain Materials Management guide.
Related Topics
• Contract Manufacturing Integration in Procurement
• Set Up a Supplier for Contract Manufacturing
• Update Existing Setup Data
667
Oracle Procurement Cloud Chapter 26
Implementing Procurement Supply Chain Management Integration
For more information about seing up back-to-back order fulllment, see the SCM Cloud Implementing Manufacturing
and Supply Chain Materials Management guide.
668
Oracle Procurement Cloud Chapter 26
Implementing Procurement Supply Chain Management Integration
Related Topics
• Back-to-Back Order Fulllment Integration in Procurement
• Enable Procurement to Support Back-to-Back Fulllment
• How You Automate Purchase Order Creation for Back-to-Back Items
• Congure Oerings
669
Oracle Procurement Cloud Chapter 26
Implementing Procurement Supply Chain Management Integration
• Also in the Order Creation Controls region, select the following check boxes. This enables the grouping of
requisition lines with the same sales order number, to be placed on a single PO.
◦ Group requisitions
◦ Use customer sales order
For more information about seing up drop ship order fulllment, see the Oracle Supply ChainAs a procurement
manager, you can dene buyer assignment rules that direct automatic routing of requisition lines to the most
appropriate buyer for processing. The application uses the rules to assign buyers to requisition lines, when requisitions
you create online or import are submied for approval.
Dene buyer assignment rules using the Manage Buyer Assignment Rules task, in the Setup and Maintenance work
area, in Purchasing Foundation functional area.
Related Topics
• Drop Shipment Order Fulllment Integration in Procurement
• Set Up Drop Ship in Order Management
• Congure Oerings
Optionally, you can dene your own document style for use with procured congurations using the Manage Document
styles task in the Setup and Maintenance work area, in the Procurement Foundation functional area. If you dene
your own document style for procured congurations, ensure the Goods check box is selected, and the Conguration
Ordering Enabled option is set to Yes.
670
Oracle Procurement Cloud Chapter 26
Implementing Procurement Supply Chain Management Integration
Be sure to complete other applicable, procurement-related setups for back-to-back or drop shipment orders.
Related Topics
• Congured Item Order Fulllment Integration in Procurement
671
Oracle Procurement Cloud Chapter 26
Implementing Procurement Supply Chain Management Integration
Internally and externally managed requisitions can also be created using File Based Data Import. However, not all
externally managed requisitions can be created using le import. Only the contract manufacturing and shipping method
are available in le import.
Supported Operations
The web service supports third party to Oracle Fusion applications integration, and Oracle Fusion to Oracle Fusion
applications integration. It provides the ability for external applications to send requests to Oracle Procurement Cloud in
the form of create, change, control and get operations. Oracle Procurement Cloud publishes the following web service
operations and actions:
• Create Purchase Request (Create, Populate, and Submit actions)
• Change Purchase Request (Change, Cancel, and Split actions)
• Control Purchase Request (Hold and Freeze, Release Hold and Unfreeze, and Firm actions)
672
Oracle Procurement Cloud Chapter 26
Implementing Procurement Supply Chain Management Integration
Additional Information
For more information about the Purchase Request Service, see the SOAP Web Services for Oracle Procurement Cloud
guide in the Oracle Help Center.
Related Topics
• SOAP Web Services for Oracle Procurement Cloud
Related Topics
• Oracle Supply Chain Management Cloud Implementing Manufacturing and Supply Chain Materials
Management
• Congure Oerings
673
Oracle Procurement Cloud Chapter 26
Implementing Procurement Supply Chain Management Integration
Project-specic purchase orders ensure that the cost of the purchase is charged to the project and the material is
received into project inventory. With this feature, you can automate the purchase of project-specic materials and carry
forward project aributes through the entire procure-to-pay cycle.
Related Topics
• Overview of Project-Driven Supply Chain Management
• How the Project-Driven Supply Chain Solution Works
• How You Set Up Project-Driven Supply Chain
674
Oracle Procurement Cloud Glossary
Implementing Procurement
Glossary
account rule
The rule that processing uses to derive complete accounts or segment values on a subledger journal entry. Conditions
can be defined within the rule to derive a different account based on specific attributes of the transaction.
accounting flexfield
The structure that determines the chart of accounts, including the number and order of the individual segments, as well
as assigning the value sets to the segments.
accounting method
A set of journal entry rules which determine how a subledger journal entry is created for each event class or event type.
action
The kind of access, such as view or edit, named in a security policy.
ADF
Application Developer Framework. A set of programming principles and rules for developing software applications.
analytics
Business intelligence objects such as analyses and dashboards that provide meaningful data to help with decision
making.
application feature
A standardized functionality that is available to implemented.
assignment
A set of information, including job, position, pay, compensation, managers, working hours, and work location, that
defines a worker's or nonworker's role in a legal employer.
675
Oracle Procurement Cloud Glossary
Implementing Procurement
balancing segment
A chart of accounts segment used to automatically balance all journal entries for each value of this segment.
browsing category
Parent or intermediate category that is associated with other categories in the catalog hierarchy, but has no assigned
items.
business function
A business process or an activity that can be performed by people working within a business unit. Describes how a
business unit is used.
business object
A resource in an enterprise database, such as an invoice or purchase order.
business unit
A unit of an enterprise that performs one or many business functions that can be rolled up in a management hierarchy.
calendar event
A period that signifies an event, such as a public holiday or a training course, that impacts worker availability.
catalog category
The association between a catalog and category or a category and category is called the catalog category. This
association includes the start date and end dates.
category
Catalog component that is associated to a catalog to classify items.
chart of accounts
The account structure your organization uses to record transactions and maintain account balances.
clause adoption
Reusing a clause from the global business unit in local business units either by adopting the clause without change or
by localizing it.
676
Oracle Procurement Cloud Glossary
Implementing Procurement
clause localization
A type of clause adoption where the adopted clause is edited to suit the local business unit needs.
condition
The part of a data security policy that specifies what portions of a database resource are secured.
constant
Holds the numeric value used to evaluate numeric conditions in Contract Expert rules. A constant permits you to reset
the conditions of many rules with just one edit.
context
A grouping of flexfield segments to store related information.
context segment
The flexfield segment used to store the context value. Each context value can be associated with a different set of
context-sensitive segments.
context-sensitive segment
A flexfield segment that may or may not appear depending upon a context. Context-sensitive segments are attributes
that apply to certain entity rows based on the value of the context segment.
contract deliverable
A task that needs to be performed as part of the execution of a contract or business document, and that is tracked as
part of the contract terms and conditions.
contract deviations
Differences between the contract terms in a contract and those in the contract terms template applied to that contract
and any deviations from company policies as determined by Contract Expert feature rules.
Contract Expert
A feature of the application that permits you to create business rules in the Contract Terms Library to enforce corporate
policies and standards for contracts.
677
Oracle Procurement Cloud Glossary
Implementing Procurement
contract type
A setup that specifies enterprise contract content, including the presence of contract terms and contract lines.
cost center
A unit of activity or a group of employees used to assign costs for accounting purposes.
Cost Factor
Cost factors allow a buyer to identify and control for additional costs associated with a negotiation line. Cost factors can
be calculated as either a per-unit cost, a percentage of the line price, or a fixed amount for the line.
cost organization
A grouping of inventory organizations that indicates legal and financial ownership of inventory, and which establishes
common costing and accounting policies.
dashboard
A page that gives quick access to key tasks and summary information for a business process or object.
data model
The metadata that determines where data for a report comes from and how that data is retrieved.
data security
The control of access and action a user can take against which data.
database resource
An applications data object at the instance, instance set, or global level, which is secured by data security policies.
678
Oracle Procurement Cloud Glossary
Implementing Procurement
department
A division of a business enterprise dealing with a particular area of activity.
descriptive flexfield
Expandable fields used for capturing additional descriptive information or attributes about an entity, such as a customer
case. You may configure information collection and storage based on the context.
determinant
A value that specifies the use of a reference data set in a particular business context.
determinant type
The value that affects sharing of reference data in a transaction across organizations, such as a business unit or a cost
organization.
determinant type
An optional value that affects document sequencing in a transaction. The available determinant types are Business Unit,
Ledger, Legal Entity, and Tax Registration.
determinant value
A value specific to the selected determinant type of a document sequence. If Ledger is the determinant type for
a document sequence, the determinant value is the specific ledger number whose documents are numbered by
the document sequence. It is relevant in a document sequence assignment only if the document sequence has a
determinant type.
division
A business-oriented subdivision within an enterprise. Each division is organized to deliver products and services or
address different markets.
document sequence
A unique number that is automatically or manually assigned to a created and saved document.
document type
A categorization of contracts, including auction, blanket purchase agreement, contract purchase agreement, RFI, RFQ,
standard purchase order, and enterprise contract.
679
Oracle Procurement Cloud Glossary
Implementing Procurement
enterprise
An organization having common control over one or more legal entities.
enterprise contract
A contract created in the Oracle Fusion Enterprise Contracts application.
entitlement
Grant of access to functions and data. Oracle Fusion Middleware term for privilege.
extensible flexfield
Expandable fields that you can use to capture multiple sets of information in a context or in multiple contexts. Some
extensible flexfields let you group contexts into categories.
feature
Business practices or methods applicable to the functional areas that enable the fine-tuning of business functionality.
filmstrip
The single strip of icons that you can use to open other pages. The strip appears between the global header and the
page title.
flexfield
A flexible data field that you can configure such that it contains one or more segments or stores additional information.
Each segment has a value and a meaning.
flexfield segment
An extensible data field that represents an attribute and captures a value corresponding to a predefined, single
extension column in the database. A segment appears globally or based on a context of other captured information.
680
Oracle Procurement Cloud Glossary
Implementing Procurement
global header
The uppermost region in the user interface that remains the same no matter which page you're on.
global search
The search in the global header that lets you search across many business objects.
grade
A component of the employment model that defines the level of compensation for a worker.
import
In the context of data integration, the transfer of data from interface tables to application tables, where the data is
available to application users.
infolet
A small interactive widget on the home page that provides key information and actions for a specific area, for example
your personal profile. Each infolet can have multiple views.
intent
Specifies if an object in the Contract Terms Library is used for procurement contracts or for sales contracts.
interface table
Database table that stores data during data transfer between applications or between databases that reside inside and
outside of an Oracle Fusion application.
inventory organization
A logical or physical entity in the enterprise that tracks inventory transactions and balances, stores definitions of items,
and manufactures or distributes products.
item categories
Term used to refer to the categories maintained in Product Information Management (PIM) under the purchasing
catalog. Within procurement, this category is referred to as a purchasing category. Item categories are used to group
items for various reports and programs. For Procurement, every item must belong to an item category.
item master
A collection of data that describes items and their attributes recorded in a database file.
item organization
Item definition where inventory balances are not stored and movement of inventory is not tracked in the applications.
Item attributes that carry financial and accounting information are hidden.
681
Oracle Procurement Cloud Glossary
Implementing Procurement
item subinventory
An association of an item with a subinventory that is created when you add an item to a subinventory.
job
A generic role that's independent of any single department or location. For example, the jobs Manager and Consultant
can occur in many departments.
job definition
The metadata that determines what a job does and what options are available to users when they submit the scheduled
process. A job is the executable for a scheduled process.
job role
A role, such as an accounts payable manager or application implementation consultant, that usually identifies and
aggregates the duties or responsibilities that make up the job.
key flexfield
Configurable flexfield comprising multiple parts or segments, each of which has a meaning either individually or in
combination with other segments. Examples of key flexfields are part numbers, asset category, and accounts in the
chart of accounts.
legal authority
A government or legal body that is charged with powers such as the power to make laws, levy and collect fees and
taxes, and remit financial appropriations for a given jurisdiction.
682
Oracle Procurement Cloud Glossary
Implementing Procurement
legal employer
A legal entity that employs people.
legal entity
An entity identified and given rights and responsibilities by commercial law through the registration with country's
appropriate authority.
legal jurisdiction
A physical territory, such as a group of countries, single country, state, county, parish, or city, which comes in the
purview of a legal authority.
Line Attribute
A unique specification for a negotiation line and the details that a supplier should provide when responding to that
negotiation line. Line attributes can be used to ensure that all responses submitted for the line include important details
beyond just the price offered for the line.
line of business
Set of one or more highly related products which service a particular customer transaction or business need. Refers to
an internal corporate business unit.
load
In the context of data integration, the transfer of external data from data files to the receiving interface tables in
preparation for an import into application tables.
lookup code
An option available within a lookup type, such as the lookup code BLUE within the lookup type COLORS.
lookup type
The label for a static list that has lookup codes as its values.
mainline metadata
The primary branch of metadata that a sandbox is published to. Once published, changes made in the sandbox become
available to all users.
683
Oracle Procurement Cloud Glossary
Implementing Procurement
manufacturing facilities
Employed in the making of goods for sale such as a factory or plant.
mapping set
Maps a combination of input source values to specific output values. The output value of a mapping set is used to
derive accounts or segments in account rules.
model profile
A collection of the work requirements and required skills and qualifications of a workforce structure, such as a job or
position.
native catalog
A catalog that a user is managing.
natural account
Categorizes account segment values by account type, asset, liability, expense, revenue, or equity, and sets posting,
budgeting, and other options.
noncatalog request
A request to purchase goods or services not available from the catalog.
numbering scheme
The style of numbering used for the sections and clauses in contract terms.
offering
Grouping of setup tasks that support specific business functions, such as Sales, Service, and Product Management.
position
A specific occurrence of one job that's fixed within a department. It's also often restricted to one location. For example,
the position Finance Manager is an instance of the job Manager in the Finance Department.
684
Oracle Procurement Cloud Glossary
Implementing Procurement
primary ledger
Main record-keeping ledger.
privilege
A grant of access to functions and data; a single, real world action on a single business object.
profile option
User preferences and system configuration options that users can configure to control application behavior at different
levels of an enterprise.
provision clause
A clause that is used only in negotiations and is dropped when the negotiation is converted to a contract.
purchasing category
Code used to group purchased items with similar characteristics such as plastics, paints, hard drives, or bolts. For
procurement, every item must belong to a purchasing category. Also referred to as an item category.
685
Oracle Procurement Cloud Glossary
Implementing Procurement
Query By Example
The icon for filtering data in a table.
reference data
Data in application tables that is not transactional or high-volume, which an enterprise can share across multiple
organizations. For example, sales methods, transaction types, or payment terms.
reference group
A logical collection of reference data sets that correspond to logical entities, such as payment terms defined across
multiple tables or views. Based on the common partitioning requirements across entities, the reference data sets are
grouped to facilitate data sharing among them.
referenced category
A category within the native catalog that is shared from a designated source catalog. A reference category is not
editable.
registration
The record of a party's identity related details with the appropriate government or legal authorities for the purpose of
claiming and ensuring legal and or commercial rights and responsibilities.
report
An output of select data in a predefined format that's optimized for printing.
role
Controls access to application functions and data.
sandbox
A testing environment that isolates untested code changes from the mainline environment so that these changes don't
affect the mainline metadata or other sandboxes.
scheduled process
A program that you run to process data and, in some cases, generate output as a report.
segment
A segment is a single field within a flexfield and maps to a single table column in your database. When configuring a
flexfield, you define the appearance and meaning of individual segments.
686
Oracle Procurement Cloud Glossary
Implementing Procurement
set
Classified and grouped reference data that organizational entities share.
set enabled
A property that describes entities that an organization shares as reference data. For example, you can indicate a lookup,
customer, location, or document attachment as set enabled.
shared category
A category within a source catalog that has been added to a native catalog as a referenced category. The category can
be shared with one or more catalogs.
source
Contextual and reference information from subledger applications used in conjunction with accounting rules to create
subledger journal entries.
storage facilities
Commercial building for storage of goods such as a warehouse.
Style template
An .rtf template containing style information that's applied to report layout templates to achieve a consistent look and
feel across reports.
Subtemplate
An .rtf or .xsl format that is defined once and used multiple times within a single report layout template or across
multiple layout template files.
687
Oracle Procurement Cloud Glossary
Implementing Procurement
system variable
A predefined variable that gets its value from an attribute of the contract or other document.
tax
The classification of a charge imposed by a government through a fiscal or tax authority.
tax jurisdiction
A geographic area where a tax is levied by a specific tax authority.
tax rate
The rate specified for a tax status for an effective time period. A tax rate can be expressed as a percentage or a value
per unit quantity.
tax recovery
The full or partial reclaim of taxes paid on the purchase or movement of a product.
tax regime
The set of tax rules that determines the treatment of one or more taxes administered by a tax authority.
tax registration
The registration of a party with a tax authority that confers tax rights and imposes certain tax obligations.
tax rule
A user-defined rule that looks for a result for a specific tax determination process in relation to a transaction tax. Tax
rules can use determining factors such as determining place of supply or tax registration, among others.
tax status
The taxable nature of a product in the context of a transaction for a tax.
territory
A legally distinct region used in the country field of an address.
688
Oracle Procurement Cloud Glossary
Implementing Procurement
tree
Information or data organized into a hierarchy with one or more root nodes connected to branches of nodes. A tree
must have a structure where each node corresponds to data from one or more data sources.
tree structure
A set of guidelines or a framework applied to create a tree, include data, version a tree, or access a tree.
tree version
An instance of a tree that includes life cycle elements such as start and end dates, and indicates whether the tree is
active. If a tree is associated with a reference data set, all tree versions belong to one set.
user variable
A variable that can be created by the Contract Terms Library administrator for use within clause text or in Contract
Expert rules.
value set
A predefined set to validate the values that a user enters in the application. The set may be hierarchical.
work area
A set of pages containing the tasks, searches, and other content you need to accomplish a business goal.
work relationship
An association between a person and a legal employer, where the worker type determines whether the relationship is a
nonworker, contingent worker, or employee work relationship.
workflow
An automated process that passes a task from one user (or group of users) to another to view or act on. The task is
routed in a logical sequence to achieve an end result.
689
Oracle Procurement Cloud Glossary
Implementing Procurement
690