Implementating Project FInancial Management Rel 9 PDF

Oracle
Project Portfolio
Management Cloud
Implementing Project
Financial Management
This guide also applies to on-premise

Release 9 implementations
Oracle® Project Portfolio Management Cloud Implementing Project Financial Management
Part Number E53161-03
Copyright © 2011-2014, Oracle and/or its affiliates. All rights reserved.
Authors: Marilyn Crawford, Gayathri Akkipeddi, Sreya Dutta, Asad Halim, Tanya Poindexter, Tejaswi Tatavarthi
Contributors: Asra Alim, Scott Dunn, Hema Hardikar, Essan Ni Jirman, Mary Kalway, Suzanne Kinkead, Peggy Larson, Michael Laverty, Kristin Penaskovic,
Barnali Roy, P. S. G. V. Sekhar, Reshma Shaik, Srinivas Vellikad, Megan Wallace, Jiri Weiss, Kathryn Wohnoutka, Jacqui Wood
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 permitted 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 find 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, the following
notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/
or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation
and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating
system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions
applicable to the programs. 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 affiliates 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 Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or
registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of
Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation
and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle
Corporation and its affiliates 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.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=docacc
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Project Portfolio Management Cloud
Implementing Project Financial Management
Contents
Preface i
1 Overview 1
Project Financial Management Offering: Overview ..................................................................................................... 1
Common Implementation: Overview .......................................................................................................................... 4
Getting Started with an Implementation: Overview .................................................................................................... 5
Manage Application Implementation .......................................................................................................................... 8
2 Define Synchronization of Users and Roles from LDAP 12

User and Role Synchronization: Explained .............................................................................................................. 12
3 Define Implementation Users 13

Define Implementation Users: Overview .................................................................................................................. 13
4 Define Enterprise Profile 14

Enterprise Structures: Overview .............................................................................................................................. 14
Enterprise Structures Business Process Model: Explained ...................................................................................... 16
Global Enterprise Configuration: Points to Consider ................................................................................................ 19
Modeling Your Enterprise Management Structure in Oracle Fusion: Example .......................................................... 20
Define Initial Configuration ....................................................................................................................................... 24
Define Reference Data Sharing ............................................................................................................................... 45
Define Geographies ................................................................................................................................................. 57
Define Enterprise: Manage Locations ...................................................................................................................... 77
Define Enterprise: Manage Enterprise HCM Information .......................................................................................... 79
Define Legal Entities: Manage Legal Jurisdictions ................................................................................................... 79
Define Legal Entities: Manage Legal Addresses ...................................................................................................... 85
Define Legal Entities: Manage Legal Entity .............................................................................................................. 87
Define Legal Entities: Manage Legislative Data Groups ........................................................................................... 91
Define Legal Entities: Manage Legal Entity HCM Information ................................................................................... 91
Define Legal Entities: Manage Legal Entity Tax Profile ............................................................................................. 98
5 Define Financial Reporting Structures 102

Manage Currencies ............................................................................................................................................... 102
Manage Conversion Rate Types ........................................................................................................................... 103
Manage Daily Rates .............................................................................................................................................. 107
Define Chart of Accounts for Enterprise Structures: Manage Chart of Accounts Structures and Structure Instances .. 108
Define Chart of Accounts for Enterprise Structures: Manage Chart of Accounts Value Sets and Value Set Values ... 130
Define Chart of Accounts for Enterprise Structures: Manage Accounting Calendars .............................................. 134
Define Accounting Configurations of Enterprise Structures: Manage Primary Ledgers ............................................ 138
Define Accounting Configurations of Enterprise Structures: Specify Ledger Options .............................................. 145
Define Business Units ........................................................................................................................................... 148
Define Workforce Structures: Manage Divisions .................................................................................................... 152
Define Workforce Structures: Manage Departments .............................................................................................. 155
Define Workforce Structures: Manage Department and Organization Trees ........................................................... 158
Define Workforce Structures: FAQs for Manage Job Families ................................................................................ 172
Define Workforce Structures: Manage Job ............................................................................................................ 173
6 Define Project Organizations 175

Define Project Units: Manage Project Unit Organizations ....................................................................................... 175
Define Project Units: Manage Project Unit Options ............................................................................................... 180
Define Project Units: Manage Project Unit Set Assignments .................................................................................. 191
Define Project Business Unit Options .................................................................................................................... 196
7 Define Users and Security 202

Define Security: Overview ..................................................................................................................................... 202
8 Define Automated Governance, Risk, and Performance Controls 205

Segregation of Duties: Highlights .......................................................................................................................... 205
9 Define Project Portfolio Management Common Reference Objects 206

Manage Value Sets ............................................................................................................................................... 206
Define Flexfields .................................................................................................................................................... 223
Manage Messages ................................................................................................................................................ 263
Manage Attachment Categories ............................................................................................................................ 265
10 Project Foundation Configuration: Overview 269

Define Project Foundation Configuration: Overview ............................................................................................... 269
11 Project Foundation Configuration: Define Project Calendars and Periods 271

Maintaining Accounting Periods and Project Accounting Periods: Critical Choices ................................................. 271
FAQs for Define Project Calendars and Periods .................................................................................................... 272
12 Project Foundation Configuration: Define Types and Categorizations 274

Manage Revenue Categories ................................................................................................................................ 274
Manage Expenditure Categories and Types .......................................................................................................... 274
Manage Project Class Categories ......................................................................................................................... 280
Manage Work Types ............................................................................................................................................. 283
Manage Project Statuses ...................................................................................................................................... 284
13 Project Foundation Configuration: Define Project Roles 290

Project Roles in Budgeting and Forecasting: Explained ......................................................................................... 290
FAQs for Define Project Roles .............................................................................................................................. 292
14 Project Foundation Configuration: FAQs for Enable Automated Project 293

Spaces
How are project space roles mapped to project resources? ................................................................................. 293
15 Project Foundation Configuration: Define Project Resources 294

Manage Resource Classes ................................................................................................................................... 294
Manage Job Mappings ......................................................................................................................................... 296
Manage Nonlabor Resources ................................................................................................................................ 300
16 Project Foundation Configuration: Define Rate Schedules and Costing 304

Rules
Manage Rate Schedules ....................................................................................................................................... 304
Manage Labor Costing Multipliers ......................................................................................................................... 307
Manage Labor Costing Rules ................................................................................................................................ 307
Manage Labor Costing Overrides ......................................................................................................................... 309
Define Labor Costing Business Unit Options ......................................................................................................... 310
Manage Organization Costing Rules ..................................................................................................................... 313
17 Project Foundation Configuration: Define Project Resource Breakdown 315

Structures
Manage Planning and Billing Resource Breakdown Structures .............................................................................. 315
Manage Reporting Resource Breakdown Structures ............................................................................................. 324
FAQs for Define Project Resource Breakdown Structures ..................................................................................... 325
18 Project Foundation Configuration: Define Burdening 328

Manage Burden Cost Base Types, Bases, and Codes ......................................................................................... 328
Manage Burden Structures ................................................................................................................................... 334
Manage Burden Schedules ................................................................................................................................... 340
Manage Project Types: Burdening Options ........................................................................................................... 344
19 Project Foundation Configuration: Manage Project Types 347

Burdening Options for Project Types: Points to Consider ...................................................................................... 347
Capitalization Options for Project Types: Points to Consider ................................................................................. 349
Associating Project Types and Class Categories: Examples .................................................................................. 352
Asset Cost Allocation Methods: Explained ............................................................................................................ 354
20 Project Foundation Configuration: Define Action Controls 355

Action Controls: Explained .................................................................................................................................... 355
21 Project Foundation Configuration: Distribute and Install Desktop 357

Integrator Client
Project Cost Transactions: How They Are Imported to Oracle Fusion Project Costing ........................................... 357
Document and Document Entry Edit Options of Predefined and Third-Party Sources: Explained ............................ 359
FAQs for Distribute and Install Desktop Integrator Client ....................................................................................... 361
22 Project Control Configuration: Overview 363

Budgeting and Forecasting Security: Explained ..................................................................................................... 363
Budget and Forecast Workflow: Explained ............................................................................................................ 367
Project Roles in Budgeting and Forecasting: Explained ......................................................................................... 369
FAQs for Project Control Configuration: Overview ................................................................................................. 371
23 Project Control Configuration: Manage Period Profiles 373

Period Profiles: Explained ...................................................................................................................................... 373
Selecting a Current Period for a Period Profile: Example ....................................................................................... 373
Using Period Profiles: Examples ............................................................................................................................ 376
24 Project Control Configuration: Manage Spread Curves 378

Spread Curves: Explained ..................................................................................................................................... 378
Project and Financial Plan Period Amounts: How They Are Calculated Using Daily Spread Basis ........................... 379
Calculating Distribution Factors for Spread Curves: Examples ............................................................................... 383
25 Project Control Configuration: Manage Financial and Project Plan Types 386
Financial and Project Plan Types: Explained ......................................................................................................... 386
Financial Plan Types and Project Budget Versions: How They Work With Budgetary Controls ............................... 387
Planning Amounts in Financial Plan Versions: Critical Choices ............................................................................... 389
Summarized Financial Plan Types: Explained ........................................................................................................ 390
Manage Financial and Project Plan Types: Set General Planning Options .............................................................. 391
Manage Financial Plan Types: Set Forecasting Options ........................................................................................ 394
Manage Project Plan Types: Set Project Plan Options .......................................................................................... 395
FAQs for Manage Financial and Project Plan Types .............................................................................................. 396
FAQs for Manage Project Plan Types: Set Project Plan Options ........................................................................... 398
26 Project Integration Gateway Configuration: Overview 399

Oracle Fusion Project Foundation and Oracle Fusion Project Management: How They Work Together ................... 399
Primavera P6 Enterprise Project Portfolio Management and Oracle Fusion Project Portfolio Management: How They Work
Together ............................................................................................................................................................... 400
27 Project Integration Gateway Configuration: Define Project Management 404

Integration
Oracle Fusion Project Management Integration Options: Points to Consider .......................................................... 404
Planning Resources: How They are Exported to Oracle Fusion Project Management ............................................ 405
28 Project Integration Gateway Configuration: Define Primavera P6 408

Enterprise Project Portfolio Management Integration
Primavera P6 Integration Options: How They Work Together ................................................................................ 408
Planning Resources: How They Are Exported to Primavera P6 Enterprise Project Portfolio Management ............... 411
Projects and Tasks: How They Are Exported to Primavera P6 Enterprise Project Portfolio Management ................ 414
Project and Task Attributes Exported to Primavera P6 Enterprise Project Portfolio Management: Explained ........... 416
FAQs for Define Primavera P6 Enterprise Project Portfolio Management Integration .............................................. 418
29 Microsoft Project Integration: Overview 419

Microsoft Project and Project Financial Management Applications: How They Work Together ................................ 419
30 Project Costing Configuration: Define General Costing Setup 422

Manage Project Transaction Sources .................................................................................................................... 422
31 Project Costing Configuration: Define Capital Projects 434

Asset Cost Allocation Methods: Explained ............................................................................................................ 434
FAQs for Define Capital Projects ........................................................................................................................... 435
Define Capitalized Interest ..................................................................................................................................... 435
32 Project Costing Configuration: Define Borrowed and Lent Accounting 438

Define Borrowed and Lent Business Unit Options ................................................................................................. 438
33 Project Costing Configuration: Define Project Costing Integrations 441

Oracle Fusion Project Costing Integration with Oracle Fusion Applications: How They Work Together .................... 441
Capturing Project Costs: Explained ....................................................................................................................... 442
Deriving Project-Related Accounts for Oracle Fusion Applications: Explained ........................................................ 446
FAQs for Define Purchasing Integration ................................................................................................................. 447
FAQs for Define Payables Integration .................................................................................................................... 447
FAQs for Define Inventory Integration .................................................................................................................... 447
34 Project Billing Configuration: Define Contracts Configuration for Project 448

Billing
Define Document Sequences ................................................................................................................................ 448
Define Project Contract Business Unit Options ..................................................................................................... 451
35 Project Billing Configuration: Define Project Invoicing Options 454

Invoice and Revenue Method Components: How They Work Together ................................................................. 454
Project and Contract Invoice Components: How They Work Together .................................................................. 457
Specifying the Unit of Measure for Invoice Lines Sent to Oracle Fusion Receivables: Critical Choices ..................... 460
Invoice and Revenue Method Classifications: Critical Choices ............................................................................... 460
Invoice Formats: Explained ................................................................................................................................... 462
FAQs for Define Project Invoicing Options ............................................................................................................. 463
36 Project Billing Configuration: Define Project Revenue Options 464

Invoice and Revenue Method Components: How They Work Together ................................................................. 464
Project and Contract Revenue Components: How They Work Together ............................................................... 467
Invoice and Revenue Method Classifications: Critical Choices ............................................................................... 470
FAQs for Define Project Revenue Options ............................................................................................................. 471
37 Project Billing Configuration: Define Project Billing Business Unit Options 473
Specify Customer Contract Management Business Function Properties ................................................................ 473
FAQs for Define Project Billing Business Unit Options ........................................................................................... 476
38 Project Billing Configuration: Define Intercompany Project Billing 477

Intercompany Balancing Rules: Explained ............................................................................................................. 477
Intercompany Balancing Rules: Examples ............................................................................................................. 477
Defining Ledger Balancing Options: Explained ...................................................................................................... 482
Defining Ledger Balancing Options: Examples ...................................................................................................... 483
Project Components for Internal Billing: How They Work Together ........................................................................ 489
Contract Components for Internal Billing: How They Work Together ..................................................................... 490
Define Invoicing Options ....................................................................................................................................... 492
FAQs for Define Intercompany Project Billing ........................................................................................................ 501
39 Project Billing Configuration: Define Transfer Pricing 502

Manage Transfer Price Rules ................................................................................................................................ 502
Manage Transfer Price Schedules ......................................................................................................................... 509
40 Project Billing Configuration: Define Customer Billing Configuration for 512

Project Billing
Manage Transaction Sources ................................................................................................................................ 512
41 Project Billing Configuration: Define Taxes for Rapid Implementation 517

Define Tax Configuration: Overview ....................................................................................................................... 517
Defining Tax Configuration for Transaction Taxes: Critical Choices ........................................................................ 518
Scope Values for Define Tax Configuration Task List: Explained ............................................................................ 520
Foundation Tax Configuration: Points to Consider ................................................................................................ 521
Tax Rule Configuration: Points to Consider ........................................................................................................... 523
Tax Account Configuration: Explained ................................................................................................................... 525
Manage Tax Regimes ........................................................................................................................................... 526
Manage Tax Rates ................................................................................................................................................ 545
Manage Tax Recovery Rates ................................................................................................................................ 554
Manage Tax Rules ................................................................................................................................................ 563
Manage Tax Registrations ..................................................................................................................................... 590
Manage Simulator Transactions ............................................................................................................................ 594
42 Project Performance Reporting Configuration: Manage Project Units: 609

Performance Reporting Options
Performance Data Summarization: How It Is Calculated ........................................................................................ 609
Setting Up the Planning Amount Allocation Basis: Points to Consider ................................................................... 610
FAQs for Manage Project Units: Performance Reporting Options .......................................................................... 611
43 Project Performance Reporting Configuration: Define Key Performance 613

Indicators
Manage Trend Indicators ...................................................................................................................................... 613
FAQs for Manage Performance Measures ............................................................................................................. 617
Manage Key Performance Indicators .................................................................................................................... 617
44 Project Performance Reporting Configuration: FAQs for Define Region 627

Personalization
Can I choose the regions to appear on Project Performance Reporting dashboard? ............................................. 627
45 Manage Project Templates 628

Expenditure Item Chargeable Status: How It Is Determined .................................................................................. 628
Spaces: How They Work With Projects ................................................................................................................ 630
Project Quick Entry: Explained .............................................................................................................................. 630
Summarized Financial Plan Types: Explained ........................................................................................................ 633
Transaction Controls: Explained ............................................................................................................................ 633
Using Class Categories: Examples ........................................................................................................................ 635
FAQs for Manage Project Templates .................................................................................................................... 637
46 Define Subledger Accounting Rules 638

Manage Accounting Methods ............................................................................................................................... 638
Manage Subledger Journal Entry Rule Sets .......................................................................................................... 656
Manage Journal Line Rules ................................................................................................................................... 658
Manage Account Rules ......................................................................................................................................... 661
Manage Description Rules .................................................................................................................................... 663
47 Define Approval Management 665

Approval Management: Highlights ......................................................................................................................... 665
48 Define Help Configuration 666

Setting Up Help: Overview .................................................................................................................................... 666
Set Help Options .................................................................................................................................................. 667
FAQs for Assign Help Text Administration Duty .................................................................................................... 668
Manage Help Security Groups .............................................................................................................................. 669
49 Define Application Toolkit Configuration 671

Define Application Toolkit Configuration: Overview ................................................................................................ 671
Map Reports to Work Areas ................................................................................................................................. 671
Set Watchlist Options ........................................................................................................................................... 673
50 Maintain Common Reference Objects 676

Maintain Common Reference Objects: Overview ................................................................................................... 676
Why can't I edit setup data? ................................................................................................................................ 676
Define Application Taxonomy ................................................................................................................................ 676
Define Reference Data Sharing ............................................................................................................................. 678
Define ISO Reference Data ................................................................................................................................... 683
Manage Data Security Policies .............................................................................................................................. 685
Set Activity Stream Options .................................................................................................................................. 694
Manage Menu Customizations .............................................................................................................................. 695
Manage Audit Policies ........................................................................................................................................... 700
Manage Oracle Social Network Objects ................................................................................................................ 702
Manage Applications Core Common Reference Objects ....................................................................................... 705
51 Define WebLogic Communication Services Configuration 777

Oracle Sales Cloud CTI: Highlights ....................................................................................................................... 777
Configuring PSTN Gateway Address Using Topology Manager: Worked Example ................................................. 778
52 Define Client Extensions 780

Define Project Extensions ..................................................................................................................................... 780
Define Burdening Extensions ................................................................................................................................. 782
FAQs for Define Expenditure Extensions ............................................................................................................... 786
Define Labor Costing Extensions .......................................................................................................................... 787
Define Borrowed and Lent Extensions .................................................................................................................. 790
Define Transfer Pricing Extensions ........................................................................................................................ 795
Define Project Billing Extensions ........................................................................................................................... 797
53 Other Common Setup and Maintenance Tasks 817

Define Transactional Business Intelligence Configuration ....................................................................................... 817
Define Extensions: Define Custom Enterprise Scheduler Jobs ............................................................................... 820
Contextual Addresses ........................................................................................................................................... 821
FAQ for Privacy Statement ................................................................................................................................... 822
54 External Integration 823

Web Services: Overview ....................................................................................................................................... 823
Files for Import and Export ................................................................................................................................... 824
External Data Integration Services for Oracle Cloud .............................................................................................. 826
55 Importing and Exporting Setup Data 841

Configuration Packages: Explained ....................................................................................................................... 841
Exporting and Importing Setup Data: Explained .................................................................................................... 841
Moving Common Reference Objects .................................................................................................................... 842
Oracle Project Portfolio Management Cloud Preface
Preface
This Preface introduces information sources available to help you use Oracle Applications.
Oracle Applications Help

Use the help icon to access Oracle Applications Help in the application.
Note
If you don't see any help icons on your page, click the Show Help button in the global area. Not all pages have
help icons.
You can also access Oracle Applications Help at https://fusionhelp.oracle.com/.
Oracle Applications Guides

To find other guides for Oracle Applications, go to:
• Oracle Applications Help, and select Documentation Library from the Navigator menu.
• Oracle Help Center at http://docs.oracle.com/
Other Information Sources

My Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://
www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you
are hearing impaired.
Oracle Enterprise Repository for Oracle Fusion Applications

Oracle Enterprise Repository for Oracle Fusion Applications (http://fusionappsoer.oracle.com) provides details on assets (such
as services, integration tables, and composites) to help you manage the lifecycle of your software.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://
www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Comments and Suggestions

Please give us feedback about Oracle Applications Help and guides! - Send e-mail to:
oracle_fusion_applications_help_ww_grp@oracle.com. - Click your user name in the global area of Oracle Applications Help,
and select Send Feedback to Oracle.
i
Oracle Project Portfolio Management Cloud Chapter 1
Implementing Project Financial Management Overview
1 Overview
Project Financial Management Offering: Overview

In the Project Management business process area, your enterprise can configure how you manage projects, including how to
plan, budget, forecast, collect costs, bill customers, and report performance.
Before you begin, use the Getting Started page in the Setup and Maintenance work area to access reports for each offering,
including full lists of setup tasks, the functional areas and features that you can select when you configure the offering, and
business objects and enterprise applications that are associated with the offering.
The first implementation step is to configure the offerings in the Setup and Maintenance work area by selecting the offerings,
functional areas, and features that you want to make available to implement.
The following list describes the project-related functional areas for the Project Financial Management offering.
Functional Area Description
Project Organizations Configure how you manage project units, project

classifications, organization hierarchies, and business
unit options.

Project Foundation Configure how you manage project organizations, create

projects, plan project tasks, and review project details.
This common foundation is shared across the Oracle
Fusion Project Financial Management products.

Burdening Configure options used to calculate, group, and apply

indirect costs to project expenditure items to report and
account for the total cost of a project.

Project Control Configure how you monitor project execution, progress,

budgeting, and forecasting.

Project Integration Gateway Configure how you integrate with third-party scheduling
tools such as Primavera P6 Enterprise Project Portfolio
Management.

Project Costing Configure how you collect, monitor and influence the
costs associated with the delivery of the project and
management of capital assets.

Project Costing - Project Costing Base Configure how you collect, monitor, and influence the
costs associated with the delivery of the project.

1
Functional Area Description
Project Costing - Capital Projects Configure how you record asset costs, calculate
capitalized interest, and create events to group costs
and assets.

Project Billing Configure how you invoice customers and recognize

revenue for project contracts, including contract
management, intercompany billing, and the calculation
of estimated taxes on invoices.

Project Billing - Project Contracts Configure the funding and billing relationships between
the external parties who require the project and the
parties who deliver the project.

Project Billing - Project Billing Base Configure how you invoice customers and recognize
revenue for project contracts.

Project Billing - Internal Project Billing Configure how you use internal invoices to share costs
and revenue across projects and organizations.

Project Performance Reporting Configure how you collect and review project
performance data against defined performance areas.

Project Accounting Configure subledger accounting and set up subledger

accounting rules for Project Financial Management.

Project Business Intelligence Analytics Enable business intelligence reporting and analytics
capabilities for project management data.

Project Revenue and Billing Business Intelligence Enable business intelligence reporting and analytics
Analytics capabilities for project revenue and billing data.

Project Performance Business Intelligence Analytics Enable business intelligence reporting and analytics
capabilities for project performance data.

Project Control and Costing Business Intelligence Enable business intelligence reporting and analytics
Analytics capabilities for project control and costing data.

The following functional areas are also in the Project Financial Management offering, but are not unique to this offering:
• Initial Users
• Enterprise Profile
2
• Legal Structures
• Financial Reporting Structures
• Organization Structures
• Workforce Structures
• Users and Security
• Transaction Tax
• Transactional Business Intelligence
• Application Extensions
Next, create one or more implementation projects for the offerings, functional areas, and features that you want to implement
first, which generates task lists for each project. The application implementation manager can customize the task list and
assign and track each task.
If you enable all functional areas and features, the generated task list for this offering will contain the groups of tasks listed in
the following table:
Task List Description
Define Initial Users for Project Financial Management Populate the product tables with the users and roles
held in LDAP and then create and provision job and data
roles for the initial users.

Define Enterprise Profile for Project Financial Access your enterprise organization, such as legal
Management entities, legal jurisdictions and authorities, and business
units, and specify their use in Project Financial
Management applications.

Define Financial Reporting Structures for Project Define the accounting configuration and chart of
Financial Management accounts that serve as a framework for how financial
records are maintained for an organization.

Define Organization Structures for Project Financial Configure business units for controlling transactions and
Management workforce structures for managing the enterprise.

Define Project Organizations Manage the organizations that own, control, or

contribute to projects, including the project units and the
project and business unit implementation options used
by Project Financial Management.

Define Users and Security for Project Financial Define and assign security policies and data roles to
Management enable users to perform functions related to their job
roles.

Define Project Foundation Configuration Configure all foundation components for creating and
maintaining projects in Oracle Fusion Project Portfolio
Management.
3

Define Project Control Configuration Configure Oracle Fusion Project Control to monitor
project execution, progress, budgeting, and forecasting.

Define Project Integration Gateway Configuration Configure Oracle Fusion Project Integration Gateway to
integrate with scheduling applications such as Primavera
P6 Enterprise Project Portfolio Management or Oracle
Fusion Project Management.

Define Project Costing Configuration Configure Oracle Fusion Project Costing to collect,
monitor, and influence the costs associated with the
delivery of the project.

Define Project Billing Configuration Configure Oracle Fusion Project Billing to invoice
customers and recognize revenue for project contracts.

Define Project Performance Reporting Configuration Configure Oracle Fusion Project Performance Reporting
to collect and review project data against defined
performance areas.

Manage Project Templates Manage templates to quickly create projects that share
common features, attributes, and options.

Define Subledger Accounting Rules for Project Financial Configure subledger accounting and set up subledger
Management accounting rules for Project Financial Management.

Define Transactional Business Intelligence Configuration Define the configuration for Oracle Transactional
Business Intelligence to enable business intelligence
reporting with the Oracle Fusion Applications.

Define Application Extensions for Project Financial Configure specific extensions for customization of
Management Project Financial Management.

You can also customize and extend applications using other tools. For more information, see the Oracle Fusion Applications
Extensibility Guide.
Common Implementation: Overview

Common implementation involves accessing tasks that are available in multiple offerings, or that apply to multiple products
and product families. The Define Common Applications Configuration task list and other activities include these common
setup and implementation tasks.
4
In addition, you can customize and extend applications using various tools. For more information, see the Oracle Sales
Extensibility Guide.
Define Common Applications Configuration Task List

Use the Define Common Applications Configuration task list to set up and administer an implementation of behaviors across
offerings.
Most Oracle Fusion Applications offerings include the Define Common Applications Configuration task list for implementing
what is common in multiple or all Oracle Fusion applications. The task lists and tasks within Define Common Applications
Configuration can be present in all offerings, some, or just a single offering.
Common implementation includes such tasks as setting up security, defining enterprise structures, configuring Oracle Fusion
Applications help, and setting options. Many of the common implementation tasks involve configuring reference objects
provided by Oracle Middleware Extensions for Applications (Applications Core), such as messages, flexfields, document
sequences, and profile options. Some common implementation tasks involve configuring features provided by Oracle
Application Toolkit (ATK), such as the Watchlist. Other common implementation tasks involve products such as the Assign
Balancing Segment Values to Ledger task in General Ledger.
Other Common Setup and Maintenance Tasks

Other setup and maintenance tasks exist in multiple offerings but not in the Define Common Applications Configuration task
list. Use these other task lists to define an Oracle Transactional Business Intelligence configuration, and to define extensions
such as custom Oracle Enterprise Scheduler jobs.
You can access common implementation tasks and task lists by starting in the Setup and Maintenance Overview page and
searching for task lists by name. Setup and Maintenance is available from the Administration menu to users provisioned with
appropriate roles. The Administration menu provides access to other tasks, such as for customization.
Getting Started with an Implementation: Overview

To start an Oracle Fusion Applications implementation, you must set up one or more initial users using the super user
that was created during installation and provisioning of the Oracle Fusion Applications environment, or using the initial
administrator user provided by Oracle for Oracle Cloud implementations. Because Oracle Fusion Applications is secure as
delivered, the process of enabling the necessary setup access for initial users requires the following steps when getting
started with an implementation:
1. If you are not starting an Oracle Cloud implementation, sign into Oracle Identity Manager (OIM) as the OIM
Administration users and provision the IT Security Manager job role with roles for user and role management.
This enables the super user account, which is provisioned with the IT Security Manager job role, to create
implementation users.
2. For starting all implementations, sign in as the user with initial access: either the Oracle Fusion Applications
installation super user or the initial Oracle Cloud administrator user.
3. Select an offering to implement, and generate the setup tasks needed to implement the offering.
4. Perform the following security tasks:
a. Synchronize users and roles in the Lightweight Directory Access Protocol (LDAP) store with HCM user
management by using the Run User and Roles Synchronization Process task.
b. Create an IT security manager user by using the Create Implementation Users task.
c. Provision the IT security manager with the IT Security Manager role by using the Provision Roles to
Implementation Users task.
5
5. As the newly created IT security manager user, sign in to Oracle Fusion Applications and set up at least one
implementation user for setting up enterprise structures.
a. Create an implementation user by using the Create Implementation Users task.
b. Provision the implementation user with the Application Implementation Manager job role or the Application
Implementation Consultant job role by using the Provision Roles to Implementation Users task. The
Application Implementation Consultant job role inherits from all product-specific application administrators
and entitles the necessary View All access to all secured objects.
c. Optionally, create a data role for an implementation user who needs only the limited access of a product-
specific Application Administrator by using the Create Data Role for Implementation Users. Then assign the
resulting data role to the implementation user by using the Provision Roles to Implementation Users task.
6
The figure shows the task flow from provisioning the IT Security Manager job role with the user and role management
entitlement to creating and provisioning implementation users for enterprise setup.
Related Topics
• Initial Security Administration: Critical Choices
• User and Role Synchronization: Explained
• Enterprise Structures: Overview
7
Manage Application Implementation
Manage Application Implementation: Overview

The Manage Applications Implementation business process enables rapid and efficient planning, configuration,
implementation, deployment, and ongoing maintenance of Oracle Fusion applications through self-service administration.
The Setup and Maintenance work area offers you the following benefits:
• Prepackaged Lists of Implementation Tasks
Task lists can be easily configured and extended to better fit with business requirements. Auto-generated, sequential
task lists include prerequisites and address dependencies to give full visibility to end-to-end setup requirements of
Oracle Fusion applications.
• Rapid Start
Specific implementations can become templates to facilitate reuse and rapid-start for comparable Oracle Fusion
applications across many instances.
• Comprehensive Reporting
A set of built-in reports helps to analyze, validate and audit configurations, implementations, and setup data of
Oracle Fusion applications.
With Oracle Fusion Functional Setup Manager you can:
• Learn about and analyze implementation requirements.
• Configure Oracle Fusion applications to match your business needs.
• Achieve complete visibility to setup requirements through guided, sequential task lists downloadable into Excel for
project planning.
• Enter setup data through easy-to-use user interfaces available directly from the task lists.
• Export and import data from one instance to another for rapid setup.
• Validate setup by reviewing setup data reports.
• Implement all Oracle Fusion applications through a standard and consistent process.
The following documentation resources are available for learning how to configure Oracle Fusion Applications.
• Functional Setup Manager Developer's Guide
• Common Implementation Guide
• Customer Data Management Implementation Guide
8
• Enterprise Contracts Implementation Guide
• Marketing Implementation Guide
• Sales Implementation Guide
• Fusion Accounting Hub Implementation Guide
• Financials Implementation Guide
• Compensation Management Implementation Guide
• Workforce Deployment Implementation Guide
• Workforce Development Implementation Guide
• Incentive Compensation Implementation Guide
• Procurement Implementation Guide
• Project Execution Management Implementation Guide
• Project Financial Management Implementation Guide
Implementation Projects: Explained

An implementation project is the list of setup tasks you need to complete to implement selected offerings and functional
areas. You create a project by selecting the offerings and functional areas you want to implement together. You manage the
project as a unit throughout the implementation lifecycle. You can assign these tasks to users and track their completion
using the included project management tools.
Maintaining Setup Data

You can also create an implementation project to maintain the setup of specific business processes and activities. In this
case, you select specific setup task lists and tasks
Exporting and Importing

Implementation projects are also the foundation for setup export and import. You use them to identify which business
objects, and consequently setup data, you will export or import and in which order.
Selecting Offerings
When creating an implementation project you see the list of offerings and functional areas that are configured for
implementation. Implementation managers specify which of those offerings and functional areas to include in an
implementation project. There are no hard and fast rules for how many offerings you should include in one implementation
project. The implementation manager should decide based on how they plan to manage their implementations. For example,
if you will implement and deploy different offerings at different times, then having separate implementation projects will make
it easier to manage the implementation life cycles. Furthermore, the more offerings you included in an implementation project,
the bigger the generated task list will be. This is because the implementation task list includes all setup tasks needed to
implement all included offerings. Alternatively, segmenting into multiple implementation projects makes the process easier to
manage. It is strongly recommended that you have no more than one offering in an implementation project. This ensures that
import and export of the project data will be straightforward and that the export and import sequence will be correct.
9
Offerings: Explained
Offerings are application solution sets representing one or more business processes and activities that you typically provision
and implement as a unit. They are, therefore, the primary drivers of functional setup of Oracle Fusion applications. Some of
the examples of offerings are Financials, Procurement, Sales, Marketing, Order Orchestration, and Workforce Deployment. An
offering may have one or more functional area, and one or more or features.
Implementation Task Lists

The configuration of the offerings will determine how the list of setup tasks is generated during the implementation phase.
Only the setup tasks needed to implement the selected offerings, functional areas and features will be included in the task list,
giving you a targeted, clutter-free task list necessary to meet your implementation requirements.
Enabling Offerings
Offerings and their functional areas are presented in an expandable and collapsible hierarchy to facilitate progressive decision
making when specifying whether or not an enterprise plans to implement them. An offering or its functional areas can either
be selected or not be selected for implementation. Implementation managers decide which offerings to enable.
Provisioning Offerings
The Provisioned column on the Configure Offerings page shows whether or not an offering is provisioned. While you are not
prevented from configuring offerings that have not been provisioned, ultimately the users are not able to perform the tasks
needed to enter setup data for those offerings until appropriate enterprise applications (Java EE applications) are provisioned
and their location (end point URLs) is registered.
Options: Explained
Each offering in general includes a set of standard functionality and a set of optional modules, which are called options. For
example, in addition to standard Opportunity Management, the Sales offering includes optional functionality such as Sales
Catalog, Sales Forecasting, Sales Prediction Engine, and Outlook Integration. These optional functions may not be relevant
to all application implementations. Because these are subprocesses within an offering, you do not always implement options
that are not core to the standard transactions of the offering.
Feature Choices: Explained

Offerings include optional or alternative business rules or processes called feature choices. You make feature selections
according to your business requirements to get the best fit with the offering. If the selected offerings and options have
dependent features then those features are applicable when you implement the corresponding offering or option. In general,
the features are set with a default configuration based on their typical usage in most implementations. However, you should
always review the available feature choices for their selected offerings and options and configure them as appropriate for the
implementation.
You can configure feature choices in three different ways:
Yes or No
If a feature can either be applicable or not be applicable to an implementation, a single checkbox is presented for selection.
Check or uncheck to specify yes or no respectively.
Single Select
If a feature has multiple choices but only one can be applicable to an implementation, multiple choices are presented as radio
buttons. You can turn on only one of those choices.
10
Multi-Select
If the feature has multiple choices but one or more can be applicable to an implementation then all choices are presented with
a checkbox. Select all that apply by checking the appropriate choices.
11
Implementing Project Financial Management Define Synchronization of Users and Roles from LDAP
2 Define Synchronization of Users and Roles from

LDAP
User and Role Synchronization: Explained

Oracle Identity Management maintains Lightweight Directory Access Protocol (LDAP) user accounts for users of Oracle
Fusion applications. Oracle Identity Management also stores the definitions of abstract, job, and data roles and holds
information about roles provisioned to users.
During implementation, any existing information about users, roles, and roles provisioned to users must be copied from the
LDAP directory to the Oracle Fusion Applications tables. To copy this information, you use the task Run User and Roles
Synchronization Process. This task calls the Retrieve Latest LDAP Changes process.
You can perform the task Run User and Roles Synchronization Process from an implementation project or the Setup and
Maintenance work area. Select Navigator - Tools - Setup and Maintenance .
Note
You must perform this task before you create implementation users so that appropriate roles are available for
them.
Once the Oracle Fusion Applications tables are initialized with this information, it's maintained automatically.
12
Implementing Project Financial Management Define Implementation Users
3 Define Implementation Users
Define Implementation Users: Overview

Implementation users perform the tasks in Oracle Enterprise Resource Planning Cloud (Oracle ERP Cloud) and Oracle Supply
Chain Management Cloud (Oracle SCM Cloud) implementation projects.
This topic introduces the tasks in the Define Implementation Users task list. For more information on implementation users
and task instructions, see:
• Oracle ERP Cloud: Securing Oracle ERP Cloud.
• Oracle SCM Cloud: Securing Oracle SCM Cloud.
Create Implementation Users

You must have at least one implementation user. To ensure segregation of critical duties, multiple implementation users are
recommended. For example, one implementation user typically performs functional setup tasks and another performs security
setup tasks. When you create implementation users, you also assign some predefined job roles to them directly. The job roles
vary with the tasks that the implementation users perform.
The cloud service administrator creates implementation users.
Create Data Role for Implementation Users

Implementation users must access application setup data. Depending on the base role you use for implementation, you might
need to create data roles. For example, the Application Implementation Consultant role already includes access to all setup
data. However, the Financial Application Administrator role does not include access to financial setup data. If the base role
assigned to an ERP or SCM implementation user includes no access to ERP and SCM setup data, use this task to create the
appropriate data roles.
An implementation user with appropriate access creates the ERP and SCM data roles for other implementation users.
Provision Roles to Implementation Users

Use this task to assign predefined abstract roles, such as employee, and appropriate ERP and SCM implementation data
roles to functional implementation users.
An implementation user with appropriate access provisions roles to other implementation users.
13
Implementing Project Financial Management Define Enterprise Profile
4 Define Enterprise Profile
Enterprise Structures: 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 affected 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, legal, managerial, and functional, that describe its operations and provide
a basis for reporting.
In Oracle Fusion, these structures are implemented using the chart of accounts and organization hierarchies. Although 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, and departments aligned by your strategic objectives.
Legal Structure
The figure above shows 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:
• A distinct legal entity from its owners and managers.

• Owned by its shareholders, who may be individuals or other corporations.
14
There are many other kinds of legal entities, 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 it 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 under the laws of each country in which their enterprise operates.
In the figure above:
• A separate card represents a series of registered companies.

• Each company, including the public holding company, InFusion America, must be registered in the countries where
they do business.
• Each company contributes to various divisions created for purposes of management reporting. These are shown as
vertical columns on each card.
For example, a group might have a separate company for each business in the United States (US), but have their 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 finance 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 do not need to be reflected directly in
the legal structure of the enterprise. The management structure can include divisions, subdivisions, lines of business, strategic
business units, profit, and cost centers. In the figure above, 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
reflected 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 structure is represented
by the Functional Axis in the figure above. You reflect the efforts 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 (R&D) and selling, general, and administrative (SG&A) expenses. In Oracle Fusion Applications,
the functional structure is implemented using departments and organizations, including sales, marketing, project, cost, and
inventory organizations.
15
Enterprise Structures Business Process Model:

Explained
In Oracle Fusion Applications, the Enterprise Performance and Planning Business Process Model illustrates the major
implementation tasks that you perform to create your enterprise structures. This process includes:
• Set Up Enterprise Structures business process, which consist of implementation activities that span many product
families.
• Information Technology, a second Business Process Model which contains the Set Up Information Technology
Management business process.
• Define Reference Data Sharing, which is one of the activities in this business process and is important in the
implementation of the enterprise structures. This activity creates the mechanism to share reference data sets across
multiple ledgers, business units, and warehouses, reducing the administrative burden and decreasing the time
needed to implement.
16
The following figure and chart describes the Business Process Model structures and activities.
BPM Activities Description
Define Enterprise Define the enterprise to capture the name of

the deploying enterprise and the location of the
headquarters.

17
Define Enterprise Structures Define enterprise structures to represent an organization

with one or more legal entities under common control.
Define organizations to represent each area of business
within the enterprise.

Define Legal Jurisdictions and Authorities Define information for governing bodies that operate
within a jurisdiction.

Define Legal Entities Define legal entities and legal reporting units for business
activities handled by the Oracle Fusion Applications.

Define Business Units Define 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 profit and loss.

Define Financial Reporting Structures Define financial reporting structures, including

organization structures, charts of accounts,
organizational hierarchies, calendars, currencies and
rates, ledgers, and document sequences which are
used in organizing the financial data of a company.

Define Chart of Accounts Define chart of accounts including hierarchies and values
to enable tracking of financial transactions and reporting
at legal entity, cost center, account, and other segment
levels.

Define Ledgers Define the primary accounting ledger and any secondary
ledgers that provide an alternative accounting
representation of the financial data.

Define Accounting Configurations Define the accounting configuration that serves as a

framework for how financial records are maintained for
an organization.

Define Facilities Define 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.

18
Define Reference Data Sharing Define how reference data in the applications is
partitioned and shared.

Note
There are product specific implementation activities that are not listed here and depend on the applications you
are implementing. For example, you can implement Define Enterprise Structures for Human Capital Management,
Project Management, and Sales Management.
Global Enterprise Configuration: Points to Consider

Start your global enterprise structure configuration by discussing what your organization's reporting needs are and how to
represent those needs in the Oracle Fusion Applications. The following are some questions and points to consider as you
design your global enterprise structure in Oracle Fusion.
• Enterprise Configuration
• Business Unit Management
• Security Structure
• Compliance Requirements
Enterprise Configuration
• What is the level of configuration 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?
Business Unit Management

• What reporting do I need by business unit?
• How can you set up your departments or business unit accounts to achieve departmental hierarchies that report
accurately on your lines of business?
• What reporting do you need to support the managers of your business units, and the executives who measure
them?
• How often are business unit results aggregated?
• What level of reporting detail is required across business units?
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?
19
• 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 first or an autonomous local approach?
• Where are you on a spectrum of centralization, very centralized or decentralized?
Modeling Your Enterprise Management Structure in

Oracle Fusion: Example
This example uses a fictitious global company to demonstrate the analysis that can occur during the enterprise structure
configuration planning process.
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 committee 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. Your product line includes all the components to
build and maintain air quality monitoring (AQM) systems for homes and businesses. You have two distribution centers and
three warehouses that share a common item master in the US and UK. Your financial services organization provides funding
to your customers for the start up costs of these systems.
Analysis
The following are elements you need to 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 need to
achieve proper statutory reporting?
• Your managers need reports that show profit 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 one segment that
represents both to produce useful, but confidential 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 unit in which to perform all these functions? How
will your shared service center be configured?
20
Global Enterprise Structure Model

The following figure and table summarize the model that your committee has designed and uses numerical values to provide
a sample representation of your structure. The model includes the following recommendations:
• Creation of three separate ledgers representing your separate legal entities:
◦ InFusion America Inc.
◦ InFusion Financial Services Inc.
◦ InFusion UK Services Ltd.
• Consolidation of results for system 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
21
• US Financial Services maintains its own payables and receivables departments
22
In this chart, the green globe stands for mandatory and gold globe stands for optional setup. The following statements
expand on the data in the chart.
• The enterprise is mandatory because it serves as an umbrella for the entire implementation. All organizations are
created within an enterprise.
• Legal entities are also mandatory. They can be optionally mapped to balancing segment values or represented
by ledgers. Mapping balancing segment values to legal entities is mandatory if you plan to use the intercompany
functionality.
• At least one ledger is mandatory in an implementation in which you record your accounting transactions.
• Business units are also mandatory because financial 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 mandatory because they track your employees.
• Optionally, add an item master organization and inventory organizations if you are tracking your inventory
transactions in Oracle Fusion Applications.
Note
Some Oracle Fusion Human Capital Management and Oracle Sales Cloud implementations do not require
recording of accounting transactions and therefore, do not require implementation of a ledger.
Note
The InFusion Corporation is a legal entity but is not discussed in this example.
23
Define Initial Configuration
Establishing Enterprise Structures Using the Enterprise

Structures Configurator: Explained
The Enterprise Structures Configurator is an interview-based tool that guides you through the process of setting up a basic
enterprise structure. By answering questions about your enterprise, the tool creates a structure of divisions, legal entities,
business units, and reference data sets that reflects your enterprise structure. After you create your enterprise structure, you
also follow a guided process to determine whether to use positions, and whether to set up additional attributes for jobs and
positions. After you define your enterprise structure and your job and position structures, you can review them, make any
necessary changes, and then load the final configuration.
This figure illustrates the process to configure your enterprise using the Enterprise Structures Configurator.
To be able to use the Enterprise Structures Configurator, you must select the Enterprise Structures Guided Flow feature for
your offerings on the Configure Offerings 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 offerings, and you can't create
multiple configurations to compare different scenarios.
24
Establish Enterprise Structures

To define your enterprise structures, use the guided flow within the Establish Enterprise Structures task to enter basic
information about your enterprise, such as the primary industry. You then create divisions, legal entities, business units,
and reference data sets. The Establish Enterprise Structures task enables you to create multiple enterprise configurations
so that you can compare different scenarios. Until you load a configuration, you can continue to create and edit multiple
configurations until you arrive at one that best suits your enterprise.
Establish Job and Position Structures

You also use a guided process to determine whether you want to use jobs only, or jobs and positions. The primary industry
that you select in the Establish Enterprise Structures task provides the application with enough information to 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 flexfield structure for jobs, and for positions if applicable. Descriptive flexfields enable you to
capture additional information when you create jobs and positions.
Review Configuration
You can view a result of the interview process prior to loading the configuration. 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 configuration.
Load Configuration
You can load only one configuration. When you load a configuration, the application creates the divisions, legal entities,
business units, and so on. After you load the configuration, you then use individual tasks to edit, add, and delete enterprise
structures.
Rolling Back an Enterprise Structure Configuration: Explained

The Enterprise Structures Configurator (ESC) provides the ability to roll back an enterprise configuration in the following
circumstances:
Roll Back a Configuration Manually

You can manually roll back an enterprise configuration after loading it, for example, because you decide you do not want to
use it. Clicking the Roll Back Configuration button on the Manage Enterprise Configuration page rolls back any enterprise
structures that were created as a part of loading the configuration.
Roll Back a Configuration Automatically

If an error occurs during the process of loading the configuration, then the application automatically rolls back any enterprise
structures that were created before the error was encountered.
Designing an Enterprise Configuration: Example

This example illustrates how to set up an enterprise based on a global company operating mainly in the US and the UK with a
single primary industry.
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 (AQM) systems for homes and businesses. Its
25
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. Outside the US, InFusion employs 200
people and has revenue of $60 million.
Analysis
InFusion requires three divisions.
• The US division covers the US locations.
• The Europe division covers UK and France.
• Saudi Arabia and the UAE are covered by the Middle East division.
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, in order 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 defined within a reference data set that multiple business units may subscribe to. Business
units are also required for financial purposes. Financial transactions are always processed within a business unit.
Resulting Enterprise Configuration

Based on this analysis, InFusion requires an enterprise with multiple divisions, ledgers, legal employers, payroll statutory units,
tax reporting units, legislative data groups, departments, cost centers, and business units.
26
This figure illustrates the enterprise configuration that results from the analysis of InFusion Corporation.
Division: Explained
Managing multiple businesses requires that you segregate them by their strategic objectives and measure their results.
Responsibility to reach objectives can be delegated along the management structure. Although related to your legal structure,
the business organizational hierarchies do not reflect directly the legal structure of the enterprise. The management entities
and structure can include:
• Divisions and subdivisions
• Lines of business
27
• Other strategic business units

• Their own revenue and cost centers.
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 differently to
deliver products and services or address different markets. A division can operate in one or more countries, and can be
comprised of many companies or parts of different companies that are represented by business units.
A division is a profit center or grouping of profit and cost centers, where the division manager is responsible for attaining
business goals including profit goals. 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 top corporate executive.
By definition a division can be represented in the chart of accounts. Companies may choose to represent product lines,
brands, or geographies as their divisions: their choice represents the primary organizing principle of the enterprise. This may
coincide with the management segment used in segment reporting.
Oracle Fusion Applications supports a qualified management segment and recommends that you use this segment to
represent your hierarchy of business units and divisions. If managers of divisions have return on investment goals, make the
management segment a balancing segment. Oracle Fusion applications allows up to three balancing segments. The values of
the management segment can be comprised of business units that roll up in a hierarchy to report by division.
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.
Use of Divisions in Oracle Fusion Human Capital Management (HCM)

Divisions are used in HCM to define the management organization hierarchy, using the generic organization hierarchy. This
hierarchy can be used to create organization based security profiles.
Legal Entities: Explained

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 specified in the relevant
legislation
Their rights and responsibilities may be enforced through the judicial system. Define a legal entity for each registered company
or other entity recognized in law for which you want to record assets, liabilities, expenses and income, pay transaction taxes,
or perform intercompany trading.
A legal entity has 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
28
• 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.
The Role of Your Legal Entities

In configuring your enterprise structure in Oracle Fusion Applications, you need to understand that the contracting party on
any transaction is always the legal entity. Individual legal entities:
• Own the assets of the enterprise
• Record sales and pay taxes on those sales
• Make purchases and incur expenses
• Perform other transactions
Legal entities must comply with the regulations of jurisdictions, in which they register. 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 specific and periodic disclosures of your legal entities' operations based on different jurisdictions'
requirements. Certain annual or more frequent accounting reports are referred to as statutory or external reporting. These
reports must be filed with specified national and regulatory authorities. For example, in the United States (US), your publicly
owned entities (corporations) are required to file quarterly and annual reports, as well as other periodic reports, with the
Securities and Exchange Commission (SEC), who enforces statutory reporting requirements for public corporations.
Individual entities privately held or held by public companies do not have to file separately. In other countries, your individual
entities do have to file in their own name, as well as at the public group level. Disclosure requirements are diverse. For
example, your local entities may have to file locally to comply with local regulations in a local currency, as well as being
included in your enterprise's reporting requirements in different 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.
Creating Legal Entities in the Enterprise Structures

Configurator: Points to Consider
Use the Enterprise Structures Configurator (ESC), to create legal entities for your enterprise automatically, based on the
countries in which divisions of your business operate, or you can upload a list of legal entities from a spreadsheet.
Automatically Creating Legal Entities

If you are not certain of the number of legal entities that you need, you can create them automatically. To use this option, you
first identify all of the countries in which your enterprise operates. The application opens the Map Divisions by Country page,
which contains a matrix of the countries that you identified, 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 identifies 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 Configurator. You must return to the Map Divisions by Country page and deselect the legal entities that you no
longer want.
29
Example: Creating Legal Entities Automatically

InFusion Corporation is using the ESC to set up their enterprise structure. They have identified two divisions, one for Lighting,
and one for Security. The Lighting division operates in Japan and the US, and the Security division operates in the UK and
India.
This figure illustrates InFusion Corporation's enterprise structure.
This table represents the selections that InFusion Corporation makes when specifying which legal entities to create on the
Map Divisions by Country page.
Country Enterprise InFusion Lighting InFusion Security
Japan No Yes No

US No Yes No

UK No No Yes

India No No Yes

Based on the selections made in the preceding table, the ESC creates the following four legal entities:
• InFusion Lighting Japan LE

• InFusion Lighting US LE
• InFusion Security UK LE
• InFusion Security India LE
Creating Legal Entities Using a Spreadsheet

If you have a list of legal entities already defined for your enterprise, you can upload them from a spreadsheet. To use this
option, you first download a spreadsheet template, then add your legal entity information to the spreadsheet, and then
30
upload directly to your enterprise configuration. You can export and import the spreadsheet multiple times to accommodate
revisions.
Related Topics
• What's an ultimate holding company?
• Working in Desktop Integrated Excel Workbooks: Points to Consider
Legal Entity in Oracle Fusion: Points to Consider

Oracle Fusion Applications support the modeling of your legal entities. If you make purchases from or sell to other legal
entities, define these other legal entities in your customer and supplier registers, which are part of the Oracle Fusion Trading
Community Architecture.
When your legal entities are trading with each other, you represent both of them as legal entities and also 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 identified as legal employers and therefore, are
available for use in Human Capital Management (HCM) applications.
There are several decisions to consider when you create legal entities.
• The importance of legal entity in transactions

• Legal entity and its relationship to business units
• Legal entity and its relationship to divisions
• Legal entity and its relationship to ledgers
• Legal entity and its relationship to balancing segments
• Legal entity and its relationship to consolidation rules
• Legal entity and its relationship to intercompany transactions
• Legal entity and its relationship to worker assignments and legal employer
• Legal entity and payroll reporting
• Legal reporting units
The Importance of Legal Entity in Transactions

All of the assets of the enterprise are owned by individual legal entities. Oracle Fusion Financials allow your users to enter legal
entities on transactions that represent a movement in value or obligation.
For example, the creation of a sales order creates an obligation for the legal entity that books the order to deliver the goods
on the acknowledged date, and an obligation of the purchaser to receive and pay for those goods. Under contract law in
most countries, damages can be sought for both actual losses, putting the injured party in the same state as if they had not
entered into the contract, and what is called loss of bargain, or the profit that would have made on a transaction.
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 reflected 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.
Legal Entity and its Relationship to Business Units

A business unit can process transactions on behalf of many legal entities. Frequently, a business unit is part of a single legal
entity. In most cases the legal entity is explicit on your transactions. For example, a payables invoice has an explicit legal entity
field. Your accounts payables department can process supplier invoices on behalf of one or many business units.
31
In some cases, your legal entity is inferred from your business unit that is processing the transaction. For example, Business
Unit ACM UK has a default legal entity of InFusion UK Ltd. When a purchase order is placed in ACM UK, the legal entity
InFusion UK Ltd is legally obligated to the supplier. Oracle Fusion Procurement, Oracle Fusion Project Portfolio Management,
and Oracle Fusion Supply Chain applications rely on deriving the legal entity information from the business unit.
Legal Entity and its Relationship to Divisions

The division is an area of management responsibility that can correspond to a collection of legal entities. If desired, you can
aggregate the results for your divisions by legal entity or by combining parts of other legal entities. Define date-effective
hierarchies for your cost center or legal entity segment in your chart of accounts to facilitate the aggregation and reporting by
division. Divisions and legal entities are independent concepts.
Legal Entity and Its Relationship to Ledgers

One of your major responsibilities is to file financial statements for your legal entities. Map legal entities to specific ledgers
using the Oracle Fusion General Ledger Accounting Configuration Manager. Within a ledger, you can optionally map a legal
entity to one or more balancing segment values.
Legal Entity and Its Relationship to Balancing Segments

Oracle Fusion General Ledger supports up to three balancing segments. Best practices recommend that one of these
segments represents your legal entity to ease your requirement to account for your operations to regulatory agencies, tax
authorities, and investors. Accounting for your operations means you must produce a balanced trial balance sheet by legal
entity. If you account for many legal entities in a single ledger, you must:
1. Identify the legal entities within the ledger.
2. Balance transactions that cross legal entity boundaries through intercompany transactions.
3. Decide which balancing segments correspond to each legal entity and assign them in Oracle Fusion General
Ledger Accounting Configuration Manager. Once you assign one balancing segment value in a ledger, then all
your balancing segment values must be assigned. This recommended best practice facilitates reporting on assets,
liabilities, and income by legal entity.
Represent your legal entities by at least one balancing segment value. You may represent it by two or three balancing
segment values if more granular reporting is required. For example, if your legal entity operates in multiple jurisdictions in
Europe, you might define 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 division or
business unit. For example, use this solution 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 are disposing of a part of a legal entity and need to isolate the assets and
liabilities for that entity.
Important
Implementing multiple balancing segments requires every journal entry that is not balanced by division or business
unit, to generate balancing lines. Also, you cannot change to multiple balancing segments easily after you have
begun to use the ledger because your historical data is not balanced by the new multiple balancing segments.
Restating historical data must be done at that point.
If your enterprise regularly spins off businesses or if they hold managers of those businesses accountable for
utilization of assets, it make be useful to identify the business with a balancing segment value. If you decided
to account for each legal entity in a separate ledger, there is no requirement to identify the legal entity with a
balancing segment value within the ledger.
32
Tip
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 it is not a separate legal entity. If you do not map legal entities sharing the same ledger
to balancing segments, you are not be able to distinguish them using the intercompany functionality or track their
individual equity.
Legal Entity and Its Relationship to Consolidation Rules

In Oracle Fusion Applications you can map legal entities to balancing segments and then define consolidation rules using
your balancing segments. You are creating a relationship between the definition of your legal entities and their role in your
consolidation.
Legal Entity and its Relationship to Intercompany Transactions

Use Oracle Fusion Intercompany feature to create intercompany entries automatically across your balancing segments.
Intercompany processing updates legal ownership within the enterprise's groups of legal entities. Invoices or journals
are created as needed. To limit the number of trading pairs for your enterprise, set up intercompany organizations and
assign then to your authorized legal entities. Define processing options and intercompany accounts to use when creating
intercompany transactions and to assist in consolidation elimination entries. These accounts are derived and automatically
entered on your intercompany transactions based on legal entities assigned to your intercompany organizations.
Intracompany trading, in which legal ownership isn't changed but other organizational responsibilities are, is also supported.
For example, you can track assets and liabilities that move between your departments within your legal entities by creating
departmental level intercompany organizations.
Tip
In the Oracle Fusion Supply Chain applications, model intercompany relationships using business units, from
which legal entities are inferred.
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 Configurator. You must enter
legal employers on worker assignments in Oracle Fusion HCM.
Legal Entity and Payroll Reporting

Your legal entities are required to pay payroll tax and social insurance such as social security on your payroll. In Oracle Fusion
Applications, you can register payroll statutory units to pay and report on payroll tax and social insurance on behalf of many
of your legal entities. As the legal employer, you might be required to pay payroll tax, not only at the national level, but also
at the local level. You meet this obligation by establishing your legal entity as a place of work within the jurisdiction of a local
authority. Set up legal reporting units to represent the part of your enterprise with a specific legal reporting obligation. You can
also mark these legal reporting units as tax reporting units, if the legal entity must pay taxes as a result of establishing a place
of business within the jurisdiction.
Business Units: Explained

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 profit and loss. Roll business units up into divisions if you structure
your chart of accounts with this type of hierarchy.
33
In Oracle Fusion Applications:
• Assign your business units to one primary ledger. For example, if a business unit is processing payables invoices
they will need to post to a particular ledger. This assignment is mandatory for your business units with business
functions that produce financial transactions.
• Use business unit as a securing mechanism for transactions. For example, if you run your export business separately
from your domestic sales business, secure the export business data to prevent access by the domestic sales
employees. To accomplish this security, set up the export business and domestic sales business as two separate
business units.
The Oracle Fusion Applications business unit model:
• Allows for flexible implementation
• Provides a consistent entity for controlling and reporting on transactions
• Anchors the sharing of sets of reference data across applications
Business units process transactions using reference data sets that reflect your business rules and policies and can differ from
country to country. With Oracle Fusion Application functionality, you can choose to share reference data, such as payment
terms and transaction types, across business units, or you can choose to have each business unit manage its own set
depending on the level at which you wish to enforce common policies.
In countries where gapless and chronological sequencing of documents is required for subledger transactions, define your
business units in alignment with your legal entities to ensure the uniqueness of sequencing.
In summary, use business units in the following ways:
• Management reporting
• Processing of transactions
• Security of transactional data
• Reference data definition and sharing
Brief Overview of Business Unit Security

Business units are used by a number of Oracle Fusion Applications to implement data security. You assign data roles to
your users to give them access to data in business units and permit them to perform specific functions on this data. When
a business function is enabled for a business unit, the application can trigger the creation of data roles for this business unit
based on the business function's related job roles.
For example, if a payables invoicing business function is enabled, then it is clear that there are employees in this business
unit that perform the function of payables invoicing, and need access to the payables invoicing functionality. Roles authorized
to this function for the data in this business unit are automatically created. Use Oracle Fusion Human Capital Management
(HCM) security profiles to administer security for employees in business units.
Creating Business Units in the Enterprise Structures

Configurator: Points to Consider
Business units are used within Oracle Fusion applications for management reporting, processing of transactions, and security
of transactional data. Using the Enterprise Structures Configurator (ESC), you create business units for your enterprise either
automatically or manually.
34
Automatically Creating Business Units

To create business units automatically, you must specify the level at which to create business units. Business units within your
enterprise may be represented at one of two levels:
• Business function level, such as Sales, Consulting, Product Development, and so on.
• A more detailed level, where a business unit exists for each combination of countries in which you operate and the
functions in those countries.
You can automatically create business units at the following levels:
• 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 financial
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 system 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
flow, 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.
Example: Selecting Business Unit Levels

InFusion Corporation is using the Enterprise Structures Configurator to set up their enterprise structure. They have identified
two divisions, one for Lighting, and one for Security. They operate in four countries: US, UK, Japan, and India, and they have
created a legal entity for each of the countries. The sales and marketing functions are based in both India and Japan, while
the US and the UK have only the sales function.
35
This figure illustrates InFusion Corporation's enterprise structure.
36
The following table lists the options for business unit levels and the resulting business units that the application suggests for
InFusion Corporation.
Business Unit Level Suggested Business Units
Country • US

• UK
• Japan
• India
Country and Division • InFusion Lighting: Japan

• InFusion Lighting: US
• Infusion Security: UK
• Infusion Security: India
Country and business function • Sales: Japan

• Marketing: Japan
• Sales: US
• Sales: UK
• Marketing: India
• Sales: India
Division • InFusion Lighting

• InFusion Security
Division and Legal Entity • InFusion Lighting: Japan

• InFusion Lighting: US
• Infusion Security: UK
• Infusion Security: India
Division and Business Function • InFusion Lighting, Sales

37
Business Unit Level Suggested Business Units

• InFusion Lighting, Marketing
• InFusion Security, Sales
• InFusion Security, Marketing
Business Function • Sales

• Marketing
Legal Entity • Legal Entity: Japan

• Legal Entity: US
• Legal Entity: UK
• Legal Entity India
Legal Entity and Business Function • Legal Entity: Japan, Sales

• Legal Entity: Japan, Marketing
• Legal Entity: US, Sales
• Legal Entity: UK, Sales
• Legal Entity India, Marketing
• Legal Entity India, Sales
Manually Creating Business Units

If none of the levels for creating business units meets your business needs, you can create business units manually, and
you create them on the Manage Business Units page. If you create business units manually, then no reference data sets are
created automatically. You must create them manually as well.
Related Topics
• What reference data objects can be shared across asset books?
Reference Data Sets and Sharing Methods: Explained

Oracle Fusion Applications reference data sharing feature is also known as SetID. The reference data sharing functionality
supports operations in multiple ledgers, business units, and warehouses, thereby reducing the administrative burden and
decreasing the time needed to implement new business units. For example, you can share sales methods, transaction types,
or payment terms across business units or selected other data across asset books, cost organizations, or project units.
38
The reference data sharing features use reference data sets to which reference data is assigned. The reference data sets
group assigned reference data. The sets can be understood as buckets of reference data assigned to multiple business units
or other application components.
Reference Data Sets

You begin this part of your implementation by creating and assigning reference data to sets. Make changes carefully as
changes to a particular set affect all business units or application components using that set. You can assign a separate
set to each business unit for the type of object that is being shared. For example, assign separate sets for payment terms,
transaction types, and sales methods to your business units.
Your enterprise can decide that some aspects of corporate policy should affect all business units and leave other aspects to
the discretion of the business unit manager. This allows your enterprise to balance autonomy and control for each business
unit. For example, if your enterprise holds business unit managers accountable for their profit and loss, but manages working
capital requirements at a corporate level, you can let managers define their own sales methods, but define payment terms
centrally. In this case, each business unit would have its own reference data set for sales methods, and there would be one
central reference data set for payment terms assigned to all business units.
The reference data sharing is especially valuable for lowering the cost of setting 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 setup data for this entity
component. You can establish other business unit reference data in a business unit specific reference data set as needed.
Reference Data Sharing Methods

There are variations in the methods used to share data in reference data sets across different types of objects. The following
list identifies the methods:
• Assignment to one set only, no common values allowed. 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
defined 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. The most commonly used method of sharing reference data
that allows defining reference data object instance across all sets. For example, Receivables Transaction Types are
assigned to a common set that is available to all the business units without the need to be explicitly assigned the
transaction types to each business unit. In addition, you can assign a business unit specific set of transaction types.
At transaction entry, the list of values for transaction types includes transaction types from the set assigned to the
business unit, as well as transaction types assigned to the common set that is shared across all business units.
• 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 the payment term Net 15 is assigned to only your corporate business
unit specific set. At transaction entry, the list of values for payment terms consists of only one set of data; the set
that is assigned to the transaction's business unit.
Note
Oracle Fusion Applications contains a reference data set called Enterprise. Define any reference data that affects
your entire enterprise in this set.
Related Topics
39
Business Units and Reference Data Sets: How They Work

Together
Reference data sharing enables you to group set-enabled reference data such as jobs or grades so that the data can be
shared across different parts of the organization. Sets also enable you to filter reference data at the transaction level so that
only data that has been assigned to certain sets is available to select. To filter reference data, Oracle Fusion Human Capital
Management (HCM), applications use the business unit on the transaction. To set up reference data sharing in Oracle Fusion
HCM, you create business units and sets, and then assign the sets to the business units.
Common Set Versus Specific Sets

Some reference data in your organization may be considered global, and should therefore be made available for use within
the entire enterprise. You can assign this type of data to the Common Set, which is a predefined set. Regardless of the
business unit on a transaction, reference data assigned to the Common Set is always available, in addition to the reference
data assigned to the set that corresponds to the business unit on the transaction.
Other types of reference data may be specific to certain business units, so you want to restrict the use of the data to those
business units. In this case, you can create sets specifically for this type of data, and assign the sets to the business units.
Business Unit Set Assignment

When you assign reference data sets to business units, you assign a default reference data set to use for all reference data
types for that business unit. You can override the set assignment for one or more data types.
Example: Assigning Sets to Business Units

InFusion Corporation has two divisions: Lighting and Security, and the divisions each have two locations. Each location has
one or more business functions.
The following figure illustrates the structure of InFusion Corporation.
40
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 specific 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
InFusion assigns business units to sets as follows:
Business Unit Default Set Assignment Set Assignment Overrides
Sales_Japan Sales_ Japan_Set for grades, Jobs set for jobs

departments, and locations

Marketing_ Japan Mktg_Japan_Set for grades, None


Sales_US Sales_US_Set for grades, Jobs set for jobs


Sales_UK Sales_UK_Set for grades, Jobs set for jobs


Marketing_ India Mktg_India_Set for grades, None


Sales_India Sales_ India_Set for grades, Jobs set for jobs


41
When setting up grades, departments, and locations for the business units, InFusion assigns the data to the default set for
each business unit. When setting 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 units on the transaction. For example, when a manager hires an employee for the Sales_India business unit,
the list of jobs is filtered to show jobs from the Jobs and Common sets.Set.
The following figure illustrates what sets of jobs can be accessed when a manager creates an assignment for a worker.
Creating Reference Data Sets in the Enterprise Structures

Configurator: Explained
If you created business units automatically, then the Enterprise Structures Configurator automatically creates reference data
sets for you. The Enterprise Structures Configurator creates one reference data set for each business unit. You can add
additional sets, but you cannot delete any of the sets that were created automatically.
A standard set called the Enterprise set is predefined.
Common Set
The Common set is a predefined 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
42
Jobs: Example
Jobs are typically used without positions by service industries where flexibility 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 left the company.

• The director decides to redirect the head count to other areas.
• 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 fluid. Using jobs gives an enterprise the flexibility to determine where to use head
count, 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 flexibility to move the headcount to other areas.
This figure illustrates the software industry job setup.
Job and Position Structures: Explained

Job and position structures identify the descriptive flexfield structure that enables you to specify additional attributes that
you want to capture when you define jobs and positions. Job and position attributes provide further detail to make jobs and
positions more specific. You also use attributes to define the structure of your jobs and positions. You can specify attributes
at the enterprise level for jobs and positions, at the business unit level for positions, and at the reference data set level for
jobs. Job and position structures are optional.
Enterprise-Level Job Attributes

When you define a job, you enter a value for the name of the job. To make job names more specific, set up attributes to
identify additional details about the job, such as the nature of the work that is performed or the relative skill level required. If
these attributes apply to all jobs within your enterprise, set up enterprise-level job attributes. Standard capabilities mean that
you can use the different segments of the name to identify common jobs or job holders for analysis or compensation, or for
grouping records in reports, for example, to find all jobs of a specific job type. You should not use attributes with values that
change regularly, for example, salary ranges or expense approval levels that change every year.
43
This figure illustrates how job type and job level provide further details for the HR Application Specialist job.
Enterprise-Level Position Attributes

Position attributes at the enterprise level are similar to those for jobs. Each position that you define identifies a specific role
in the enterprise, which you can manage independently of the person in the position. A position belongs to one specific
department or organization. The name of each position must be unique. To simplify the process of managing unique names
for positions, set up enterprise-level attributes to identify separate components of the position name. For example, you can
set up an attribute for position title and one for position number. When defining the attributes that make up the structure of
a position name, consider whether any of your attributes are part of the definition of a common job type. Using job types for
a position can help you manage common information that applies to many different positions. For example you can define a
job type of Manager.Level 1 and use this for comparison of positions across departments or lines or business, or for setting
common job requirements. You can then define multiple manager type positions in your HR department, each of which has
responsibility for a different management function or group.
This figure illustrates how title and position number provide further details for the manager position.
44
Business Unit-Level Attributes for Positions

If you have information that you want to capture for positions that is specific to each business unit, then you can define
attributes at the business unit level for positions. When you create positions, these attributes appear in addition to any
enterprise-level attributes. For example, you may want to identify the sales region for all positions in the sales business unit.
You can set up a text attribute called Sales Region and use it to enter the necessary information when creating positions for
the sales business unit.
Reference Data Set-Level Attributes for Jobs

If you have information for jobs that applies to specific reference data sets, set up attributes for jobs at the reference data set
level. When you create jobs, these attributes appear in addition to any enterprise-level attributes. For example, you may want
to identify all information technology (IT) jobs within a specific set. You can set up a text attribute called Function and use it to
enter IT in jobs that you create that perform an IT function within a specific set.
FAQs for Define Initial Configuration

What happens if I don't use the Enterprise Structures Configurator to set up my enterprise
structures?
The Enterprise Structures Configurator is an interview-based tool that guides you through setting up divisions, legal entities,
business units, and reference data sets. If you do not use the Enterprise Structures Configurator, then you must set up your
enterprise structure using the individual tasks that correspond to each enterprise component. In addition, you can't set up
multiple configurations and compare different scenarios. Using the Enterprise Structures Configurator is the recommended
process for setting up your enterprise structures.
What's the default reference data set?

The reference data set that is assigned to a business unit for all reference data groups, such as grades, locations,
departments, and jobs. You can override the default reference data set for any reference data group.
What happens if I override the set assignment?

For the selected business unit, you can override the default reference data set for one or more reference data groups. For
example, assume you have three reference data groups: Vision 1 SET, Vision 2 SET, and Vision 3 SET, where Vision SET 1 is
the default set for business unit United Kingdom Vision 1 BU. You can override the default so that:
• Grades are assigned to Vision 2 SET
• Departments are assigned to Vision 3 SET
• Jobs are assigned to the default set, Vision 3 SET
Define Reference Data Sharing
Reference Data Sharing: Explained

Reference data sharing facilitates sharing of configuration data such as jobs and payment terms, across organizational
divisions or business units. You define reference data sets and determine how the data is shared or partitioned. Use reference
data sets to reduce duplication and maintenance by sharing common data across business entities where appropriate.
Depending on the requirement (specific or common), each business unit can maintain its data at a central location, using a
set of values either specific to it or shared by other business units.
You can share reference data after it is filtered on the basis of sets. 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
45
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 cannot be assigned to an entity, you can create specific 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 managers in different
business units setting up the same grades, XYZ Corporation decides to create a set called Grades and assign the grades
reference data group for all business units in the organization to the Grades set, so that the grades can be shared.
Note
For specific information on configuring reference data sharing for a particular object or product, refer to its product
documentation.
Reference Data Sets: Explained

Reference data sets are logical groups of reference data that can be accessed by various transactional entities depending
on the business context. Oracle Fusion Applications contains a common reference data set as well as an enterprise set that
may be used as a default set. Depending on your business requirement you can create and maintain additional reference data
sets, while continuing to use the common reference data set.
Consider the following scenario.
Partitioning
The partitioning of reference data and creation of data sets enable you to create reference entities across tables or lookup
types, and share modular information and data processing options among business units. With the help of partitioning, you
can choose to create separate sets and subsets for each business unit depending upon its business requirement, or create
common sets or subsets to enable sharing reference data between several business units, without the need for duplicating
the reference data. Partitioning provides you the flexibility to handle the reference data in a way appropriate to your business
needs.
46
The following figure illustrates the reference data sharing method (assignment to one set only, with common values) where the
user can access the data assigned to a specific set in a particular business unit, as well as access the data assigned to the
common set.
Related Topics
• Defining Default Reference Data Sets : Points to Consider

Reference Data Sets

47

Note
Related Topics
Assigning Reference Data Sets to Reference Objects: Points to

Consider
You can assign the reference data sets to reference objects on the Manage Reference Data Set Assignments page. For
multiple assignments, you can classify different types of reference data sets into groups and assign them to reference entity
objects. The assignment takes into consideration the determinant type, determinant, and reference group, if any.
Determinant Types
The partitioned reference data is shared based on a business context setting called the determinant type. It is the point of
reference used in the data assignment process. The following table lists the determinant types used in the reference data
assignment.
48
Type Description
Asset Book Information about the acquisition, depreciation, and

retirement of an asset that belongs to a ledger or a
business unit.

Business Unit The departments or organizations within an enterprise.

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

is responsible for enforcing consistent project
management practices.

Reference Data Set References to other shared reference data sets.

Determinant
The determinant or determinant value is the value that corresponds to the selected determinant type. The determinant is
one of the criteria for selecting the appropriate reference data set. For example, when managing set assignments for the set
determinant type, Reference Data Set is the determinant type, and you would enter the corresponding set code value as the
corresponding determinant value.
Reference Groups
A transactional entity may have multiple reference entities (generally considered to be setup data) that are treated in the same
manner because of commonness in implementing business policies and legal rules. Such reference entities in your application
are grouped into logical units called reference groups, based on the functional area and the partitioning requirements that
they have in common. For example, all tables and views that define Sales Order Type details might be part of the same
reference group.
Note
The reference groups are predefined in the reference groups table and are available for selection and assignment.
Items and Supplier Site Reference Data Sharing: Explained

Some products required special logic for reference data sharing and have implemented their own domain specific ways for
sharing data.
Items and supplier sites are two such product specific reference data objects that use product specific mechanisms to share
data.
Items
If you share your items across warehouses or manufacturing facilities, you can access them through a common item
master. Configure one or multiple item masters for your enterprise, based your enterprise structure. A single item master
is recommended because it provides simpler and more efficient maintenance. However, in rare cases, it may be beneficial
49
to keep multiple item masters. For example, if you acquire another enterprise and need 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 specified 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 different local supplier sites to save transportation costs.
To implement business unit specific supplier sites, Oracle Fusion Procurement supports a method for defining 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 defined 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:
• Supplier qualification data, such as approved supplier lists
• Catalog content, such as agreements, smart forms, public shopping lists, and content zones
• Procurement configuration data
Related Topics
Set Assignments and Project Data: How They Work Together

Reference data set assignments determine how you share enterprise information, including project data, across
organizational units. In other words, you can decide which data is global, which data can be shared by certain organizations,
and which data must remain organization-specific. Reference data sharing enables enterprises to balance autonomy and
control for organizations.
Oracle Fusion Projects employs two set determinants: business unit and project unit.
Business Unit as Set Determinant

Business units enable you to control and report on financial transactions, usually for specific geographical entities within the
enterprise. For project management purposes, assign the Project Accounting business function to the business unit.
Business unit is a set determinant for the following project-related reference data objects.
Reference Data Object Entities
Project Accounting Definition Project types

Project Rates Project rate schedules

You assign a default set to each business unit. You can optionally override the default set for the Project Accounting
Definition and Project Rates reference data objects. To enable a project type or rate schedule for use within the business
unit, you must assign the same reference data set to that entity.
50
Note
If you assign a common set to a rate schedule, then that rate schedule is available for use across business units.
Project Unit as Set Determinant

Use project units to enforce consistent project management practices across your enterprise. Project unit is a set determinant
for the following reference data objects.
Project Definition Class codes, financial plan types and project plan types,
project roles, and project statuses

Project Transaction Types Expenditure types and work types

When specifying project unit implementation options, you select a default set. You can optionally override the default set for
the Project Definition and Project Transaction Types reference data objects. To enable an entity like a financial plan type
for use on projects owned by a project unit, assign the set associated with the Project Definition reference data object to the
financial plan type.
Similarly, to enable expenditure types and work types for use on projects owned by a project unit, assign the set associated
with the Project Transaction Types reference data object to those entities.
Related Topics
• Associating Sets with Financial Plan Types: Example
• Business Units: How They Work with Projects
• Project Units: Explained
Partitioning Project Data Using Set Determinants: Examples

Use business units and project units to independently manage access to financial and project management data based on
the unique requirements of your enterprise.
This topic illustrates the following scenarios.
1. Maintaining separate project management methodologies and data across units within an enterprise while
centralizing financial management of data
2. Enforcing a single project management methodology across units within an enterprise while partitioning financial
data
Note
These examples are only illustrative. Any combination of business units and project units can exist.
51
Using Multiple Project Units with One Business Unit

Assume that Vision Corporation is a services company with facilities across the United States. Its business is based on
research and development activities and consulting practice. Projects are used by each line of business as follows:
• Consulting uses projects to manage consulting engagements and provide billing details to contracts.
• Research and Development uses projects to manage design project schedules.
• Real Estate uses projects to manage facilities, including new construction and repairs.
Vision Corporation implemented project units and business units as follows:
• Project Units
◦ Consulting
◦ Real Estate
◦ Research and Development

• Business Unit: Vision Corporation
Set assignments for reference data objects, where project unit is the set determinant, are as follows:
Project Unit Default Set
Consulting Consulting Set

Real Estate Real Estate Set

Research and Development Research and Development Set

Note
The default set is used as the reference data set for both the Project Definition and Project Transaction Types
reference data objects.
Vision Corporation can maintain independent setup data for each project unit, while sharing a single approach to financial
management across all project units. For example, Vision Corporation uses different expenditure types across project units,
as described in the table below.
Expenditure Type Sets
Labor Consulting Set

Real Estate Set

Research and Development Set

52
Airfare Consulting Set

Hotel Consulting Set

Equipment Real Estate Set

The Labor expenditure type can be used for projects belonging to any project unit. However, expenditure types for airfare and
hotel accommodation are used only on consulting projects.
Using Multiple Business Units with One Project Unit

Assume that InFusion Corporation is a services and product development company with research and development facilities
across the globe, including in the United States and Canada. Due to its international operations, financial data must be
partitioned using separate business units. However, basic research and development activities, based on projects, are the
same across the enterprise. Therefore, a single project unit is created.
The enterprise structure and set assignments are described below.
• Project Unit: Research and Development

• Business Units
◦ InFusion United States
◦ InFusion Canada
Default set assignments for the business units are as follows:
Business Unit Default Set
InFusion United States US Set

InFusion Canada Canada Set

InFusion Corporation maintains independent financial data for each business unit, while employing a unified approach to
project management that includes common financial and project plan types, project roles, and project statuses. As the
enterprise must use different resource rates in each country, rate schedule setup is as follows.
Rate Schedule Name Project Rates Set
Enterprise Project Rates: United States US Set

Enterprise Project Rates: Canada Canada Set

53
Common Enterprise Project Rates Common Set

These set assignments govern how planned and actual amounts are calculated for projects.
For example, when InFusion Corporation defines organization costing rules for the InFusion United States business unit, they
can select only the Enterprise Project Rates: United States or the Common Enterprise Project Rates rate schedules. Later,
the application uses the selected rate schedule to calculate actual costs when project accountants import uncosted time
cards for the InFusion United States business unit.
FAQs for Define Reference Data Sharing

What reference data objects can be shared across business units?
The following list contains the reference data objects for the Oracle Fusion Applications that can be shared across business
units and the method in which the reference data for each is shared.
Application Name Reference Data Object Method of Sharing
Trading Community Model Customer Account Relationship Assignment to one set only, with
common values

Trading Community Model Customer Account Site Assignment to one set only, with
common values

Trading Community Model Sales Person Assignment to one set only, with
common values

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

Sales Sales Method Assignment to one set only, with

common values

Common Components Activity Templates Assignment to one set only, with

common values

54
Payables Payment Terms Assignment to multiple sets, no

common values allowed

Receivables Accounting Rules Assignment to one set only, with

common values

Receivables Aging Buckets Assignment to one set only, with

common values

Receivables Auto Cash Rules Assignment to one set only, with

common values

Receivables Collectors Assignment to one set only, with

common values

Receivables Lockbox Assignment to one set only, with

common values

Receivables Memo Lines Assignment to one set only, with

common values

Receivables Payment Terms Assignment to one set only, with

common values

Receivables Remit To Address Assignment to one set only, with

common values

Receivables Revenue Contingencies Assignment to one set only, with

common values

Receivables Transaction Source Assignment to one set only, with

common values

Receivables Transaction Type Assignment to one set only, with

common values

Advanced Collections Collections Setups Assignment to one set only, with

common values

55
Advanced Collections Dunning Plans Assignment to one set only, with

common values

Tax Tax Classification Codes Assignment to multiple sets, no


Human Resources Departments Assignment to one set only, with

common values

Human Resources Jobs Assignment to one set only, with

common values

Human Resources Locations Assignment to one set only, with

common values

Human Resources Grades Assignment to one set only, with

common values

Project Billing Project and Contract Billing Assignment to multiple sets, no


Project Foundation Project Accounting Definition Assignment to one set only, no


Project Foundation Project Rates Assignment to one set only, with

common values

Distributed Order Orchestration Hold Codes Assignment to one set only, with
common values

Distributed Order Orchestration Orchestration Process Assignment to one set only, with
common values

What reference data objects can be shared across cost organizations?

The following list contains the reference data objects for Oracle Fusion Cost Management that can be shared across cost
organizations and the method in which the reference data for each is shared.
56
Cost Management Cost Structure Assignment to one set only, no


What reference data objects can be shared across project units?

The following table contains the reference data objects for Oracle Fusion Project Foundation that can be shared across
project units and the method in which the reference data for each is shared.
Project Foundation Project Definition Assignment to multiple sets, no


Project Foundation Project Transaction Types Assignment to multiple sets, no


Define Geographies
Defining Address Cleansing: Explained

Address cleansing validates, corrects, and standardizes address information that you enter in Oracle Sales Cloud. Address
cleansing, unlike geography validation, validates both the geography attributes and the address line attributes.
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:
• None: Specifies no real time address cleansing.
• Optional: Provides option to cleanse addresses.
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
does not find a matching address, then an alert message is displayed.
Geography Structure, Hierarchy, and Validation: How They Fit

Together
There are three components that are dependent on each other when defining a country: geography structure, geography
hierarchy, and geography validation. Every country has to have the geography structure defined first before the hierarchy can
be defined, and the geography hierarchy has to be defined before the validation can be defined.
57
Geography Structure
Firstly, you need to create a geography structure for each country to define 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 defined using the Manage Geographies task, or can be imported using tasks in the Define Geographies
activity.
Geography Hierarchy
Once the geography structure is defined, the geographies for each geography type can be added to the hierarchy. For
example, below the 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 Define Geographies
activity.
Geography Validation
After defining the geography hierarchy, you need to specify the geography validations for the country. You can choose
which address style formats you would like to use for the country, and for each selected address style format you can map
geography types to address attributes. You can also select which geography types should be included 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: Explained

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. For example, the geography structure for
the United States is as follows:
Level Geography Type
1 State

2 County

3 City

4 Postal Code

You can use the geography structure to relate geography types for a country and define geography types for a country.
58
Relate Geography Types for a Country

You can determine how a country's geographies are hierarchically related by creating the hierarchy of the geography types
in the geography structure. When you define a country's structure, the geography type Country is implicitly at the top of the
geography structure with the level 1. The subsequent geography types that you add after country are numbered in sequence.
You must add a geography type as a level in the country structure before you can define a geography for that geography
type in a country. For example, before defining the state of California, the State geography type must be added to the United
States country structure.
Note
You cannot delete geography types that have associated geography data.
To quickly create country structure, you can copy a structure from another country and modify the geography types for the
country.
Define Geography Types for a Country

You can use any of the master reference geography types to create your geography structure. If required, you can create a
geography type, before adding it to the country structure. Each geography type is added below the current lowest level.
Note
You can only delete the lowest level geography type of the country structure.
A geography type that you create within the country structure can be used for other country structures as well.
Geography Hierarchy: Explained

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. The top 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.
California Parent of San Mateo county
San Mateo County Parent of Redwood City

Redwood City Parent of 94065

94065 Child

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 definition. The geography hierarchy information is centrally
located and shared among other application offerings.
59
The geography hierarchy includes:
• Geography: Geography is a physical space with boundaries that is a defined instance of a geography type, such as
country, state, province or city. For example, San Jose is a geography of the City geography type.
• Geography type: Geography types are divisional grouping of user defined geographies, for example, Continent,
Country Regions, and Tax Regions.
• Geography usage: Geography usage indicates how a geography type or geography is used in the application.
• Master reference geography hierarchy: The geography hierarchy data is considered the single source of reference for
all geography related data such as geography types and geographies.
The geography usage for the entire hierarchy is the master reference, and defined geography types and geographies
are the master reference geography types and geographies. For example, you can create geography types called
State, City, and Postal Code. Then, you can rank the State as the highest level, City as the second level, and Postal
Code as the lowest level within the country structure.
• User defined zones: User defined zones are a collection of geographical data, created from master reference data for
a specific purpose. For example, while the territory zones are collections of master reference geographies ordered
with a hierarchy, the tax and shipping zones are without a hierarchical grouping.
Geography Validation: Explained

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 defining 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 defined you can set up additional mapping for specific address styles.
For each address style format, you can define the following:
• Map to attribute
• Enable list of values
• Tax validation
• Geography validation
• Geography validation control
Map to Attribute
For every address style format, you can map each geography type to an address attribute. For example, you can map
the State geography type to the State address attribute for the United States, or map the State geography type to the
County address attribute for the United Kingdom. The geography types that appear are based on how the country structure
is defined. The list of address attributes that appear are based on address formats delivered with the application, or your
customer defined address formats.
Note
You only need to map geography types that you want to use for geography or tax validation purposes.
Enable List of Values

Once a geography type is mapped to an attribute, then you can specify whether the geography type will appear in a list of
values during address entry in user interfaces. It is very important to review carefully if you want to enable a list of values. You
should only enable a list of values if you have sufficient geography data imported or created for that geography. If the setup
for master geography data is incomplete, then the geography data is either not imported or created. As a result, the list of
values for the address attribute does not list any geography data.
60
Once you have enabled a list of values for an address attribute, you can only select the geography data available for the
geography type. This means that if a specific geography value is not available in the geography hierarchy, you cannot create
an address with a different geography value.
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 can specify whether a geography type will be included in geography validation. This will mean that, 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 will be provided for the address element, but the address element will not be validated.
Note
For either the tax or geography validation, do not skip more than one consecutive level unless you are 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.
Geography Validation Control

You can select the geography validation level for a country. Validation will check if the entered address maps to the
geography hierarchy data available for the country, and the geography validation control determines whether you can save an
address that did not pass validation during address entry. For example, if the validation level is Error, then an address cannot
be saved if the values do not match the geography hierarchy data.
These are the geography validation levels you can choose:
• 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 attribute 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 is 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 specific geography or zone.
61
Note
The Geography Dimension value in territories is derived from sell-to addresses of sales accounts. To use
geography dimensions in territories, ensure that the geography elements in addresses, such as state, city,
and postal code, are validated. You can do so by enabling geography validation for each country using the
Manage Geographies task. While doing so, ensure that at least one level in the geography hierarchy is enabled
for geography validation. It is recommended that you enable geography validation for all geography levels that
you intend to use for territory definition for each country. You can enable a list of values containing specific
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 also set geography validation control to Error in the
Manage Geography Validation page. This ensures that users can only use valid geography elements in addresses.
If you have already created addresses before setting up geography validation for a country, you must execute the
Run Maintain Geography Name Referencing task for that country after enabling geography validation to ensure
that all your geography elements are validated.
Geocoding: Explained
This topic explains geocoding and how to enable this option in Oracle Sales Cloud.
Geocoding is the process of finding latitude and longitude coordinates from geographic data such as street addresses or zip
codes. Once these coordinates are available, you can use the spatial services feature to identify points of interest, such as
customer and contact addresses, in the vicinity. Oracle Sales Cloud integrates the Geocoding feature with eLocation (http://
elocation.oracle.com/maps_oracle_dot_com_main.html), which is a geocoder service provided by Oracle.
By default, the Geocoding option is turned off in Oracle Sales Cloud. You can enable the Geocoding option in the Setup and
Maintenance, Manage Geographies page.
If the Geocoding feature is enabled, the feature can be scheduled to run at regular time intervals. This ensures that newly
created or updated locations are picked up and geocoded whenever you create or update an address using the user
interface, web services, bulk import, or file-based import.
Related Topics
• What are Spatial Services?
Setting Up Geocoding: Procedure

This procedure lists the steps to set up geocoding in Oracle Sales Cloud.
Geocoding is a process that determines the latitude and longitude coordinates for a location. By default, geocoding is turned
off in Oracle Sales Cloud. You can use geocoding to display customers in the vicinity of a mobile address.
Enabling Geocoding for a Country

To enable geocoding for a country, complete these steps:
1. From the Setup and Maintenance work area, search for Manage Geographies and click Go to Task.
2. Search the country for which you want to enable geocoding. You can either search by the country name or country
code.
3. Click Search. The search results for the matching country names are displayed.
4. Select the country for which you want to enable the geocoding option.
62
5. Select Geocoding Defined for the country.
Populating Location Latitude and Longitude Information

Once geocoding is enabled, you can schedule this feature to run at regular time intervals so that newly created or updated
locations are picked up and geocoded. To schedule the geocoding feature to run at regular intervals, complete these steps:
1. Navigate to the Scheduled Processes work area, and click Schedule New Process.
2. Click the Name drop-down and search for Populate Location Latitude and Longitude Information, and then click
OK.
3. Enter the parameters such as Start Date and End Date, and click Submit.
Importing Geographies: Explained

A geography, such as Tokyo or Peru, describes a boundary on the surface of the earth. You can create new geographies
by importing data through interface tables. There are two options for populating the interface tables: using the tool of your
preference to load the data or using file-based data import. If you plan to provide the data details in a source file, use the file-
based import feature. If you will populate the interface table directly, run the geography loader process to import the data.
Having a good understanding of the import entity, interface table, and destination table will help you prepare your import data.
Consider the following when importing geographies:
• Nokia geography reference data
• File-based import option
• Geography loader process option
• Import object entity, interface table, and destination tables
Nokia Geography Reference Data

Oracle Sales Cloud includes third-party (Nokia) master geography for multiple countries that can be easily imported. You can
import Oracle-licensed Nokia data from Navteq, for those countries where the data is available, such as the U.S. You can
import Nokia Geography data using the Manage Geographies task. Search for the country, and select Import Nokia Data
from the Actions menu. If the licensed Navteq data is not available for a particular country, then the Import Nokia Data
action is disabled.
File-Based Import Option

The file-based import process reads the data included in your XML or text file, populates the interface tables, and imports the
data into the application destination tables. The File-Based Data Import Setup and Maintenance task list includes the
tasks needed to configure the geography import object, create source file mappings, and schedule the import activities.
Geography Loader Process Option

Populate the interface table with your import data, then navigate to the Run Geography Loader Setup and Maintenance
task to schedule the import of data from the interface table to the destination table.
Import Object Entity, Interface Table, and Destination Tables

The geography import object consists of one entity and interface table that forms the geography. If you are using file-based
import, you can map your source file data to import entity attributes that correspond to the interface table columns. The
import activity process populates the interface table based on the mapping and your source file. If using the geography
63
loader scheduled process, populate the interface table directly using your preferred tool. If you need the unique IDs of
existing application data for your import data, use the Define Data Export Setup and Maintenance task list to export the
information.
Note
Spreadsheets containing detailed information about each interface table, including the import attributes,
corresponding interface table columns, defaults, and validations, are available from the Oracle Enterprise
Repository by searching on a specific interface table name or initiating a search using the FusionApps: Interface
Table asset type.
The following lists the object entity, tables, and resulting application object:
File-Based Import Interface Tables Destination Tables Application Object

Entities
ImpGeography HZ_ IMP_ HZ_GEOGRAPHIES Geography

GEOGRAPHIES_T
HZ_ GEOGRAPHY_
IDENTIFIERS

HZ_ GEOGRAPHY_
TYPES_B

HZ_ HIERARCHY_
NODES

Related Topics
• File-Based Import Processing: How it Works
• Importing Nokia Geography Reference Data
Importing Country Structures Using File-Based Import:

Explained
This topic explains how to prepare and import country structure data from an external data source into Oracle Sales Cloud
using the File-Based Data Import feature. A country structure is a hierarchical grouping of geography types for a country. For
example, the geography structure for the United States has the geography type of State at the top, followed by the County,
then the City, and finally the Postal Code.
You can use the country structure to set up the following:
• The relationships between geographies within a country
• The types of geographies that you can define for a country
Consider the following questions when importing your data:
• How does your legacy system or source system represent the country structure compared to how Oracle Sales
Cloud represents the same data?
64
• Do you have to configure values in Oracle Sales Cloud to map to your data values?
• Do you have to customize Oracle Sales Cloud to capture additional attributes that are critical to the way you do
business?
• What import features are available for importing your business object?
• How do you verify your imported data?
Comparing Business Object Structures

You must understand how your country structure data corresponds with the data in Oracle Sales Cloud so that you can map
your legacy data to the data that Oracle Sales Cloud requires. First, you must understand how Oracle Sales Cloud represents
the structure of the data for a country structure.
You must import a separate country structure import object for each country. Each of these import objects must contain
the geography types that are used in the country's structure, organized in a hierarchy using geography level numbers. For
example, if you're importing the country structure of Australia, the country structure could be the following: 1: Country, 2:
State, 3: County, 4: Town, 5: ZIP.
Import Objects for the Country Structure

To facilitate importing country structures, Oracle Sales Cloud incorporates the structure of the country structure into import
objects. The import object for country structures is GeoStructureLevel.
Comparing Business Object Data

Each import object is a collection of attributes that helps to map your data to the Oracle Sales Cloud data and to support
one-to-many relationships between the structural components that make up the country structure.
You must understand the attribute details of the import objects so that you can prepare your import data. . You can use
reference guide files that contain attribute descriptions, values that populate attributes by default when you don't provide
values, and validation information for each attribute. The validation information includes the navigation path to the task where
you can define values in Oracle Sales Cloud. For example, if you have values in your data that correlate to a choice list in
Oracle Sales Cloud, then the validation information for that attribute provides the task name in the Setup and Maintenance
work area where you can define your values. For additional information, including a list of reference guide file names and
locations that you need to complete this task, see the following table.
Import Object Related Import Object Topic
Country Structure Country Structure Import Objects: How They Work

Together

Extensible Attributes
If you need to extend the Oracle Sales Cloud object to import your legacy or source data, you must use Application
Composer to design your object model extensions and to generate the required artifacts to register your extensions and
make them available for importing. The corresponding import object is updated with the extensible attributes, which can then
be mapped to your source file data. You can use the same source file to import both extensible custom attributes and the
standard import object attributes.
Importing Country Structures Using File-Based Data Import

For the country structure business object, you must use the File-Based Data Import feature. You prepare XML or text source
data files in a form that is suitable for a file-based import. The file-based import process reads the data in your source file,
populates the interface tables according to your mapping, and imports the data into the application destination tables.
65
The Define File-Based Data Import Setup and Maintenance task list includes the tasks that are required to configure the
import objects, to create source-file mappings, and to schedule the import activities. You submit file-based import activities
for each import object. When you're creating a new country structure, you import the Country Structure object.
You must be assigned the Master Data Management Administrator job role to access and submit the import activities for
country structures.
Verifying Your Imported Data

You can view the list of import activities from the Manage Import Activities page. You can verify your imported data by clicking
the Status column for your import activity.
Related Topics
• File-Based Data Import: How It Works
• Getting Started with File-Based Import: Documentation Overview
• Extending Simplified Pages for Households: Explained
Country Structure Import Objects: How They Work Together

This topic describes the Country Structure import object. You use the Country Structure import object when you submit a file-
based import activity to import your country structure information. This topic introduces the following:
• Target objects for the Country Structure import object

• Target import object attributes
• Reference guide files for target import object attributes
Country Structure Target Import Objects

The Country Structure import object contains one target import object. The target import object organizes the individual
attributes of the different aspects of the geography structure. 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.
Target Import Object Attributes

You must compare the attributes that you want to import with the target object attributes that are available and with their
valid values. To evaluate your source data and Oracle Sales Cloud attributes for mapping and validation, you use an Oracle
Enterprise Repository reference guide, which is available for each target import object. The reference guide file includes
attribute descriptions, default values, and validations performed by the import process. Review the validation for each
attribute to determine whether there are functional prerequisites or prerequisite setup tasks that are required.
To import your source file data, you define a mapping between your source file data and the combination of the target object
and target object attribute. You can predefine and manage import mappings using the Manage File Import Mappings task, or
you can define the mapping when you define the import activity using the Manage File Import Activities task. Both tasks are
available in the Setup and Maintenance work area.
Note
If any of the attributes you want to import does not have an equivalent target object attribute, then review the
Application Composer extensibility features for country structures.
66
Reference Files for Target Import Object Attributes

To access the reference guide files for the country code's target import objects, see the assets of type File-Based Data
Import in Oracle Enterprise Repository (http://fusionappsoer.oracle.com).
For detailed information on importing geographies using file-based import, refer to Document No. 1481758.1, Importing
Master Reference Geography Data, on the Oracle Support site.
The following table lists the reference guide files that are available from the Details tab for the Country Code Import asset.
Target Import Object Description Reference Guide File Names
ImpGeoStructureLevel Information that specifies a HZ_ IMP_ GEO_STRUCTURE _

country's geography structure. LEVELS_ Reference

Related Topics
• Extending Simplified Pages for Households: Explained
• Importing Country Structures Using File-Based Import: Quick Start
Importing Geographies Using File-Based Import: Explained

This topic explains how to prepare and import geography data from an external data source into Oracle Sales Cloud using
the File-Based Data Import feature. A geography is any region with a boundary around it, regardless of its size. It might be
a state, a country, a city, a county, or a ward. You must create or import geographies before you can associate them with
custom zones and addresses.
Note
Oracle Sales Cloud includes third-party (Nokia) master geography for multiple countries that can be easily
imported. You can import Oracle-licensed Nokia data from Navteq, for those countries where the data is available,
such as the U.S. You can import Nokia Geography data using the Manage Geographies task. Search for the
country, and select Import Nokia Data from the Actions menu. If the licensed Navteq data is not available
for a particular country, then the Import Nokia Data action is disabled. For more information, see Importing
Nokia Geography Reference Data, Define Geographies, Oracle Sales Cloud - Implementing Customer Data
Management guide.
If Nokia geography data is not available for a country, then use the information in this chapter to import it using
File-Based Data Import.
Consider the following questions when importing your data:
• How does your legacy system or source system represent the geography compared to how Oracle Sales Cloud
represents the same data?
• Do you have to configure values in Oracle Sales Cloud to map to your data values?
67
• What import features are available for importing your business object?
• How do you verify your imported data?
Comparing Business Object Structures

You must understand how your geography data corresponds with the data in Oracle Sales Cloud so that you can map your
legacy data to the data that Oracle Sales Cloud requires. First, you must understand how Oracle Sales Cloud represents the
structure of the data for a geography.
You must import a separate country structure import object for each country. Each of these import objects must contain
the geography types that are used in the country's structure, organized in a hierarchy using geography level numbers. For
example, if you are importing the country structure of Australia, the country structure could be the following: 1: Country, 2:
State, 3: County, 4: Town, 5: ZIP.
Import Objects for the Geography

To facilitate importing geographies, Oracle Sales Cloud incorporates the structure of the geography into import objects. The
import object for the geography is ImpGeography.
Comparing Business Object Data

Each import object is a collection of attributes that helps to map your data to the Oracle Sales Cloud data and to support
one-to-many relationships between the structural components that make up the geography.
You must understand the attribute details of the import objects so that you can prepare your import data. You can use
reference guide files that contain attribute descriptions, values that populate attributes by default when you do not provide
values, and validation information for each import object attribute. The validation information includes the navigation path to
the task where you can define values in Oracle Sales Cloud. For example, if you have values in your data that correlate to a
choice list in Oracle Sales Cloud, then the validation information for that attribute provides the task name in the Setup and
Maintenance work area where you can define your values. For additional information, including a list of reference guide file
names and locations that you need to complete this task, see the following table.
Import Object Related Import Object Topic
ImpGeography Geography Import Objects: How They Work Together

Hint: You can use the keyword importing geographies to search for related topics in Help.
Extensible Attributes
Oracle Sales Cloud doesn't support extensible attributes for geographies. You can import only data for geography object that
already exist by default in Oracle Sales Cloud.
Importing Geographies Using File-Based Data Import

For the geography business object, you must use the File-Based Data Import feature. You prepare XML or text source
data files in a form that is suitable for a file-based import. The file-based import process reads the data in your source file,
populates the interface tables according to your mapping, and imports the data into the application destination tables.
The Define File-Based Data Import Setup and Maintenance task list includes the tasks that are required to configure the
import objects, to create source-file mappings, and to schedule the import activities. You submit file-based import activities
for each import object. When you're creating a new geography, you import the Geography object. You must be assigned 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.
68
Verifying Your Imported Data

Oracle Sales Cloud Applications provide File-Based Import activity reports, which you can use to verify imported data. Users
with the Master Data Management Administrator job role can also navigate to the Manage Geographies work area to view the
imported geographies.
Related Topics
Geography Import Objects: How They Work Together

This topic describes the Geography import object. You use the Geography import object to import geography information.
This topic introduces the following:
• Target objects for the Geography import object

• Target import object attributes
• Reference guide files for target import object attributes
Geography Target Import Objects

You can use the Geography import object to import geography hierarchy information to create or update the geography data
of a country. To map the source data in your import file to the target attributes in Oracle Sales Cloud, you must understand
how the target objects are related and what attributes are included in each target object.
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, which connects the
geography to the country of which it is a part.
Use the ImpGeography target import object to create and update geography information.
Note
Before you import geography data for a country, you must define the country's geography structure.
Target Import Object Attributes

You must compare the attributes that you want to import with the target object attributes that are available and with their
valid values. To evaluate your source data and Oracle Sales Cloud attributes for mapping and validation, you use an Oracle
Enterprise Repository reference guide, which is available for each target import object. The reference guide file includes
attribute descriptions, default values, and validations performed by the import process. Review the validation for each
attribute to determine whether there are functional prerequisites or prerequisite setup tasks that are required.
To import your source file data, you define a mapping between your source file data and the combination of the target object
and target object attribute. You can predefine and manage import mappings using the Manage File Import Mappings task, or
you can define the mapping when you define the import activity using the Manage File Import Activities task. Both tasks are
available in the Setup and Maintenance work area.
Note
If any of the attributes you want to import do not have an equivalent target object attribute, then review the
Application Composer extensibility features for geography.
69
Reference Files for Target Import Object Attributes

To access the reference guide files for the geography's target import objects, see the assets of type File-Based Data Import in
Oracle Enterprise Repository (http://fusionappsoer.oracle.com).
For detailed information on importing geographies using file-based import, refer to Document No. 1481758.1, Importing
Master Reference Geography Data, on the Oracle Support site.
The following table lists the reference guide files that are available from the Details tab for the Geography File-Based Data
Import asset.
Target Import Object Description Attribute Reference Guide File

Names
ImpGeography Contains information that captures HZ_ IMP_ GEOGRAPHIES_T

a country's geography hierarchy _Reference
details, such as geography type,
geography code, etc.

Related Topics
Importing Geographies Using File-Based Data Import: Worked

Example
This example demonstrates how to import data using the File-Based Data Import tool. In this example, you have a source file
containing geography data that you want to import into the application so that the geography data can be used for real time
address validation and tax purposes.
The following table summarizes the key decisions that you must make in this scenario.
Decisions to Consider In This Example
What type of object are you importing? Geography

What file type are you using for your source data? Text file

Where are you uploading your source data file from? Your desktop

What data type is your source data file? Comma separated

Which fields are you importing into Oracle Sales Cloud? All, except for the RecordTypeCode field

70
When do you want to process the import? Immediately

Summary of the Tasks

You perform the following steps to create an import activity and activate the import:
1. Determining what information is in the source file.
2. Creating and scheduling the import activity.
3. Monitoring the import results.
Prerequisites for Importing Additional Geography Data After Your Initial

Import
1. Ensure that the combination of the Source ID and Parent Source ID values is unique for each row of data within a
single import. However, your source data files don't need to have the same Source ID and Parent Source ID values
as your previously imported geography data. If the geography structure levels and the parents for each geography
value are the same, then the changed IDs will not affect the import.
2. Ensure that all the parents of a child geography are included in your data file so that the child geography can be
added. For example, if you originally imported US, CA, and San Francisco, and now you want to import the city of
San Jose in CA, then your data file must include US, CA, and San Jose.
3. Check that your source data file has the correct values for the geography data that you have already loaded.
For example, if your initial import included the value US for country and CA as state, and in a subsequent import
you have California as a state, then your geography import creates two state records (CA and California) in the
application data, with the US as the country parent.
Determining What Information is in the Source File

1. The source geography data files must include a unique Source ID value for each row of data and Parent Source ID
value for the parent of that row of data. The Source or Parent Source IDs should not be longer than 18 characters.
2. You can structure your geography source data as follows:
Geography Level Name Source ID Parent Source ID
1 (Country) US 1

2 (State) CA 11 1

3 (County) Alameda 111 11

71
Geography Level Name Source ID Parent Source ID
4 (City) Pleasanton 1111 111

4 (City) Dublin 1112 111

Creating and Scheduling the Import Activity

You can create an import activity, enter the import details, and schedule the import. An import activity includes selecting the
source file or file location, mapping the source file to the Oracle Sales Cloud database, and scheduling the import.
1. In the Setup and Maintenance work area, search for the Manage File Import Activities task. Click Go to Task.
2. In the Manage Import Activities page, click Create.
3. In the Create Import Activity: Set Up page, create an import activity for the Geography object type by completing
the fields, as shown in this table.
Field Value
Name Master Reference Geographies

Object Geography

File Type Text File

File Selection Specific file

Upload From Desktop

File Name Choose relevant file from desktop

Data Type Comma separated

Note
Ensure that the file type that you select in the Create Import Activity: Set Up page matches the file type
of the source data file.
4. Click Next.
5. In the Create Import Activity: Map Fields page, map each field from your source file to the Oracle Sales Cloud
database object and attribute, as shown in the following table.
72
Column Example Value Ignore Object Attribute

Header
Primary Primary United States Imp Geography Primary

Geography Geography Geography
Name Name Name

Country Code US No Imp Geography Country Code

Record Type 0 Yes Imp Geography Record Type

Code Code

Source ID 10265 No Imp Geography Source ID

Parent Source ID 1053 No Imp Geography Parent Source ID

If you don't want to import a column in the text file, then you can select Ignore.
Note
If you can't map the fields from your source file to the relevant Oracle Sales Cloud database object, then
see the import object spreadsheets.
6. Click Next.
7. In the Create Import Activity: Create Schedule page, select Immediate in the Schedule field 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.
Monitoring the Import Results

You can monitor the processing of the import activity and view the completion reports for both successful records and errors.
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. Confirm your import details, and click Activate to submit the import.
After the import activity has finished, the Status field value changes to Completed.
Related Topics
• File-Based Import Processing: How it Works
73
Importing and Exporting Territory Geography Zones: Explained

Territory geography zones are geographical boundaries that you can set up to replicate your organization's regions, such as
a Pacific Northwest sales region. You can set up territory geography zones in one Oracle Sales Cloud applications instance,
and then after the territory geography zones are defined you can export the territory zones and import them into another
Oracle Sales Cloud instance.
To define your territory geography zones and then import your territory zones into another Oracle Sales Cloud instance, you
need to complete the following steps:
1. Import the master reference geography data into the Oracle Sales Cloud.
2. Define your territory geography zones using the Manage Territory Geographies task.
3. Export the territory geography zones.
4. Import the territory geography zones into another Oracle Sales Cloud instance.
Import the master reference geography data

Firstly, you need to import the master reference geography data. Master reference geography data consists of geography
elements such as country, state, and city, and is required for any geographical information you store in the application,
such as address information used in customer and sales records. For more information, refer to the Geography Hierarchy:
Explained topic listed in the related topics section. Master reference geography data can be imported into the application
using the Manage File Import Activities task in Setup and Maintenance - refer to the Importing Master Reference Geography
Data: Worked Example topic listed in the related topics section for more information.
Define your territory geography zones

Once the master reference geography data has been imported, you can then create your territory geography zones in the
application using the Manage Territory Geographies task in Setup and Maintenance. For more information, refer to the
Managing Territory Geographies: Worked Example topic listed in the related topics section.
Export the territory geography zones

Once you have completed importing the master reference geography data and defining your territory geography zone tasks,
you can create a configuration package to export the territory zone data. For more information, refer to the Exporting Setup
Data demo listed in the related topics section.
Import the territory geography zones

Once you have downloaded your configuration package for your territory geography zone setup, you can import the territory
zones into another Oracle Sales Cloud instance. For more information, refer to the Importing Setup Data listed in the related
topics section.
Note
Ensure that you import your master reference geography data into the new Oracle Sales Cloud instance before
you import the configuration package.
Related Topics
• Managing Territory Geographies: Worked Example
• Exporting Setup Data
74
• Importing Setup Data
Managing Geography Structures, Hierarchies, and Validation:

Worked Example
This example shows how to configure the geography structure, hierarchy, and validation for a country geography, using the
United Kingdom country geography as an illustration.
The following table summarizes the key decisions for this scenario.
Copy an existing country structure? No, create a new country structure.

What is the structure of the geography types? Create geography types with the following ranking
structure:
1. County
2. Post Town
What is the geography hierarchy? Create the following hierarchy:

1. Country of United Kingdom
2. County of Berkshire
3. Post Town of Reading
Which address style format will you use when mapping The default address style format, called the No Styles
geography validations? Format.

Are you using Oracle Fusion Tax for tax purposes? No, do not select Tax Validation for the geography
types.
Defining the Geography Structure

Add the County and Post Town geography types to the United Kingdom geography structure.
1. On the Manage Geographies page, enter GB in the Code field. Click Search.
2. On the Manage Geographies page, click Structure Defined.
3. On the Manage Geography Structure page, click the Create button next to the Copy Country Structure From
field.
4. In the Geography Structure section, select the County list item in the Add Geography Type field.
75
5. Click Add.
6. Select the Post Town list item in the Add Geography Type field.
7. Click Add.
Defining the Geography Hierarchy

To create the geography hierarchy for United Kingdom, add the geographies for the County and Post Town geography types
using the geography hierarchy user interfaces. You can also use the Manage File Import Activities task to import geography
hierarchies using a csv or xml file.
1. On the Manage Geographies page, enter GB in the Code field. Click Search.
2. On the Manage Geographies page, click Hierarchy Defined.
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 field.
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 field.
Defining the Geography Validations

To specify the geography validations for the geography types you added to United Kingdom, define the geography mapping
and validation for the United Kingdom default address style format. Then, map the geography types to attributes, enable the
geography types for Lists of Values and Geography Validation, and set the geography validation level.
1. On the Manage Geographies page, click Validation Defined.

2. In the Address Style section, click No Styles Format to highlight the table row.
3. For the County geography type, click the County list item in the Map to Attribute field.
4. Select the Enable List of Values and Geography Validation options.
5. For the Post Town geography type, click the City list item in the Map to Attribute field.
6. Select the Geography Validation option.
7. In the Geography Validation Control section, select Error in the Geography Validation Level for Country list.
FAQs for Define Geographies

When do I define address cleansing?
When address data entered into the application needs to conform to a particular format, in order to achieve consistency
in the representation of addresses. For example, making sure that the incoming data is stored following the correct postal
address format.
76
Why can't I update a geography structure by copying an existing country structure?

You can only update a geography structure by adding existing geography types, or by creating new geography types and
then adding them to the geography structure. You can only copy an existing country structure when you are defining a new
country structure.
Why can't I delete a level of the country geography structure?

If a geography exists for a country geography structure level then you cannot delete the level. For example, if a state
geography has been created for the United States country geography structure, then the State level cannot be deleted in the
country geography structure.
Can I add any geography to the geography hierarchy?

Yes. However, the geography type for the geography that you want to add must be already added to the country geography
structure.
Can I edit a specific geography in the geography hierarchy?

Yes. In the Manage Geography Hierarchy page you can edit details such as the geography's date range, primary and
alternate names and codes, and parent geographies.
How can I add a geography that is the level below another geography in a geography
hierarchy?
Select the geography that you want your geography to be created below, and then click the Create icon. This will allow you
to create a geography for a geography type that is the level below the geography type you selected. The structure of the
country's geography types are defined in the Manage Geography Structure page.
Define Enterprise: Manage Locations
Locations: Explained
A location identifies 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.
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 benefits 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 benefits. 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.
Note the following:
• 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.
77
The following figure shows how locations sets restrict access to users.
Uploading Locations Using a Spreadsheet

If you have a list of locations already defined for your enterprise, you can upload them from a spreadsheet.
To use this option:
• Download a spreadsheet template
• Add your location information to the spreadsheet
• Upload directly to your enterprise configuration
You can upload the spreadsheet multiple times to accommodate revisions.
Related Topics
• Uploading Workforce Structures Using a Spreadsheet: Explained
FAQs for Manage Locations

Why can't I see my location in the search results?
You can search for approved locations only. Also, if you created a location in Oracle Fusion Trading Community Model,
then you can't access that location from Oracle Fusion Global Human Resources. For use in Oracle Fusion HCM, you must
recreate the location from the Manage Locations page.
78
What happens if I select a geographic hierarchy node when I'm creating or editing 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 predefined geographic
hierarchy.
Related Topics
• Worker Availability: How It Is Determined
What happens if I inactivate a location?

Starting from the effective date that you entered, you can no longer associate the location with other workforce structures,
assignments, or applications. If the location is already in use, it will continue to be available to the components that currently
use it.
Define Enterprise: Manage Enterprise HCM

Information
Managing Enterprise Information for Non-Oracle Fusion HCM

Users: Explained
The Manage Enterprise HCM Information task includes default settings for your enterprise such as the employment model,
worker number generation, and so on. If you are not implementing Oracle Fusion Human Capital Management (HCM), then
the only action you may need to perform using this task is to change the enterprise name, if necessary. The other settings are
HCM-specific and are not relevant outside of Oracle Fusion HCM.
Define Legal Entities: Manage Legal Jurisdictions
Jurisdictions and Legal Authorities: Explained

You are required to register your legal entities with legal authorities in the jurisdictions where you conduct business. Register
your legal entities as required by local business requirements or other relevant laws. For example, register your legal entities
for tax reporting to report sales taxes or value added taxes.
Define jurisdictions and related legal authorities to support multiple legal entity registrations, which are used by Oracle Fusion
Tax and Oracle Fusion Payroll. When you first create a legal entity, the Oracle Fusion Legal Entity Configurator automatically
creates one legal reporting unit for that legal entity with a registration.
Jurisdictions: Explained
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
79
legislation that apply to legal entities operating in different 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 first jurisdiction you must register
with to be allowed to do business in a country. If there is more than one jurisdiction that a legal entity needs to 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 do not represent the same jurisdiction. Although in some countries,
the two jurisdictions are defined at the same geopolitical level, such as a country, and share the same legal authority, they are
two distinct jurisdictions.
Income Tax Jurisdiction

Create income tax jurisdictions to properly report and remit income taxes to the legal authority. Income tax jurisdictions by
law impose taxes on your financial income generated by all your entities within their jurisdiction. Income tax is a key source of
funding that the government uses to fund its activities and serve the public.
Transaction Tax Jurisdiction

Create transaction tax jurisdictions through Oracle Fusion Tax in a separate business flow, because of the specific needs
and complexities of various taxes. Tax jurisdictions and their respective rates are provided by suppliers and require periodic
maintenance. Use transaction tax jurisdiction for legal reporting of sales and value added taxes.
Legal Authorities: Explained

A legal authority is a government or legal body that is charged with powers to make laws, levy and collect fees and taxes, and
remit financial 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 are required to print legal authority information on your tax reports. Legal authorities are defined
in the Oracle Fusion Legal Entity Configurator. Tax authorities are a subset of legal authorities and are defined using the same
setup flow.
Legal authorities are not mandatory in Oracle Fusion Human Capital Management (HCM), but are recommended and are
generally referenced on statutory reports.
Creating Legal Jurisdictions, Addresses and Authorities:

Examples
Define legal jurisdictions and related legal authorities to support multiple legal entity registrations, which are used by Oracle
Fusion Tax and Oracle Fusion Payroll.
Legal Jurisdictions
Create a legal jurisdiction by following these steps:
1. Navigator > Setup and Maintenance > Manage Legal Jurisdictions > Go to Task.
80
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 first 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 Addresses for Legal Entities and Reporting Units

Create a legal address for legal entities and reporting units by following these steps:
1. Navigator > Setup and Maintenance > Manage Legal Address > Go to Task.
2. Select Create.
3. Select Country.
4. Enter Address Line 1, Oracle Parkway.
5. Optionally enter Address Line 2, and Address Line 3.
6. Enter or Select Zip Code, 94065.
7. Select Geography 94065 and Parent Geography Redwood Shores, San Mateo, CA.
8. Optionally enter a Time Zone, US Pacific Time.
9. OK.
10. 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.
81
Note
Create an address for the legal authority.
4. Select Create.
5. The Site Number is automatically assigned.
6. Optionally enter a Mail Stop.
7. Select Country, United States
8. Enter Address Line 1, 121 Spear Street, Suite 400.
11. Select Geography 94105 and Parent Geography San Francisco, San Francisco, CA.
12. OK.
14. Optionally click the One-Time Address check box.
15. The From Date defaults to today's date. Update if necessary.
16. Optionally enter a To Date to indicate the last day the address can be used.
Note
You can optionally enter Address Purpose details.
17. Select Add Row.
18. Select Purpose.
19. The Purpose from Date will default to today's date.
20. Optionally enter a Purpose to Date.
21. OK.
22. Save and Close.
Creating Legal Entities, Registrations, and Reporting Units:

Examples
Define a legal entity for each registered company or other entity recognized in law for which you want to record assets,
liabilities, and income, pay transaction taxes, or perform intercompany trading.
82
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 Identifier, US0033.
5. Optionally enter Start Date. When the start date is blank the legal entity is effective 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.
Note
Enter the Registration Information.
10. Accept the default Identifying Jurisdiction, United States Income Tax.
11. Search for and select a Legal Address, 500 Oracle Parkway, Redwood Shores, CA 94065.
Note
The legal address must have been entered previously using the Manage Legal Address task.
12. OK.
13. Optionally enter a Place of Registration.
14. Enter the EIN or TIN.
15. Enter the Legal Reporting Unit Registration Number.
16. Save and Close.
17. Navigator > Setup and Maintenance > Define Legal Entries > Manage Legal Entity > Select... to set scope.
18. Select the Manage Legal Entity.
19. In the *Legal Entity drop down, select Select and Add.
20. Click Apply and Go to Task.
21. Select your legal entity.
83
22. Save and Close on the very bottom of the window.
This sets the scope for your task list to the selected legal entity.
23. Save and Close.
Legal Entity Registrations

A legal entity registration with the same name as that of the legal entity will be created by default. To verify this, locate the
Manage Legal Entity Registrations task and then select Go to Task. To create another registration for the legal entity
follow these steps:
1. Navigator > Setup and Maintenance > Manage Legal Entity Registrations. Verify that the Legal Entity
scope value is set correctly.
2. Go to Task.
3. Select Create.
4. Enter Jurisdiction.
5. Enter Registered Address.
6. Enter Registered Name.
7. Optionally enter Alternate Name, Registration Number, Place of Registration, Issuing Legal Authority, and
Issuing Legal Authority Address, Start Date, and End Date.
8. Save and Close.
Legal Reporting Unit

When a legal entity is created, a legal reporting unit with the same name as that of the entity is also automatically created. To
create more legal reporting units or modify the settings follow these steps:
1. Navigator > Setup and Maintenance > Define Legal Reporting Unit . > Manage Legal Reporting Unit. Verify
that the Legal Entity scope value is set correctly.
2. Go to Task
3. Select Create.
4. Enter Territory, United States.
5. Enter Name.
6. Optionally enter a Start Date.
Note
Enter Registration Information.
7. Search for and select Jurisdiction.
84
Note
Enter Main Legal Reporting Unit information.
8. Select the value Yes or No for the Main Legal Reporting Unit. Set value to yes only if you are creating a new main
(primary) legal reporting unit.
9. Enter the Main Effective Start Date, 1/1/11.
10. Save and Close.
Related Topics
• Planning Legal Reporting Units: Points to Consider
Define Legal Entities: Manage Legal Addresses
Creating Legal Jurisdictions, Addresses and Authorities:

Examples
Define legal jurisdictions and related legal authorities to support multiple legal entity registrations, which are used by Oracle
Fusion Tax and Oracle Fusion Payroll.
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 first 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.
85
11. Save and Close.
Legal Addresses for Legal Entities and Reporting Units

Create a legal address for legal entities and reporting units by following these steps:
1. Navigator > Setup and Maintenance > Manage Legal Address > Go to Task.
2. Select Create.
3. Select Country.
4. Enter Address Line 1, Oracle Parkway.
7. Select Geography 94065 and Parent Geography Redwood Shores, San Mateo, CA.
9. OK.
10. 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.
7. Select Country, United States
8. Enter Address Line 1, 121 Spear Street, Suite 400.
11. Select Geography 94105 and Parent Geography San Francisco, San Francisco, CA.
86
12. OK.
14. Optionally click the One-Time Address check box.
15. The From Date defaults to today's date. Update if necessary.
16. Optionally enter a To Date to indicate the last day the address can be used.
Note
You can optionally enter Address Purpose details.
17. Select Add Row.
18. Select Purpose.
19. The Purpose from Date will default to today's date.
20. Optionally enter a Purpose to Date.
21. OK.
22. Save and Close.
Define Legal Entities: Manage Legal Entity
Legal Entities: Explained

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 specified in the relevant
legislation
Their rights and responsibilities may be enforced through the judicial system. Define a legal entity for each registered company
or other entity recognized in law for which you want to record assets, liabilities, expenses and income, pay transaction taxes,
or perform intercompany trading.
A legal entity has responsibility for elements of your enterprise for the following reasons:
• Facilitating local compliance
• Minimizing the enterprise's tax liability
87
• 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.
The Role of Your Legal Entities

In configuring your enterprise structure in Oracle Fusion Applications, you need to understand that the contracting party on
any transaction is always the legal entity. Individual legal entities:
• Own the assets of the enterprise
• Record sales and pay taxes on those sales
• Make purchases and incur expenses
• Perform other transactions
Legal entities must comply with the regulations of jurisdictions, in which they register. 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 specific and periodic disclosures of your legal entities' operations based on different jurisdictions'
requirements. Certain annual or more frequent accounting reports are referred to as statutory or external reporting. These
reports must be filed with specified national and regulatory authorities. For example, in the United States (US), your publicly
owned entities (corporations) are required to file quarterly and annual reports, as well as other periodic reports, with the
Securities and Exchange Commission (SEC), who enforces statutory reporting requirements for public corporations.
Individual entities privately held or held by public companies do not have to file separately. In other countries, your individual
entities do have to file in their own name, as well as at the public group level. Disclosure requirements are diverse. For
example, your local entities may have to file locally to comply with local regulations in a local currency, as well as being
included in your enterprise's reporting requirements in different 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.
Legal Entity in Oracle Fusion: Points to Consider

Oracle Fusion Applications support the modeling of your legal entities. If you make purchases from or sell to other legal
entities, define these other legal entities in your customer and supplier registers, which are part of the Oracle Fusion Trading
Community Architecture.
When your legal entities are trading with each other, you represent both of them as legal entities and also 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 identified as legal employers and therefore, are
available for use in Human Capital Management (HCM) applications.
There are several decisions to consider when you create legal entities.
• The importance of legal entity in transactions
• Legal entity and its relationship to business units
• Legal entity and its relationship to divisions
88
• Legal entity and its relationship to ledgers
• Legal entity and its relationship to balancing segments
• Legal entity and its relationship to consolidation rules
• Legal entity and its relationship to intercompany transactions
• Legal entity and its relationship to worker assignments and legal employer
• Legal entity and payroll reporting
• Legal reporting units
The Importance of Legal Entity in Transactions

All of the assets of the enterprise are owned by individual legal entities. Oracle Fusion Financials allow your users to enter legal
entities on transactions that represent a movement in value or obligation.
For example, the creation of a sales order creates an obligation for the legal entity that books the order to deliver the goods
on the acknowledged date, and an obligation of the purchaser to receive and pay for those goods. Under contract law in
most countries, damages can be sought for both actual losses, putting the injured party in the same state as if they had not
entered into the contract, and what is called loss of bargain, or the profit that would have made on a transaction.
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 reflected 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.
Legal Entity and its Relationship to Business Units

A business unit can process transactions on behalf of many legal entities. Frequently, a business unit is part of a single legal
entity. In most cases the legal entity is explicit on your transactions. For example, a payables invoice has an explicit legal entity
field. Your accounts payables department can process supplier invoices on behalf of one or many business units.
In some cases, your legal entity is inferred from your business unit that is processing the transaction. For example, Business
Unit ACM UK has a default legal entity of InFusion UK Ltd. When a purchase order is placed in ACM UK, the legal entity
InFusion UK Ltd is legally obligated to the supplier. Oracle Fusion Procurement, Oracle Fusion Project Portfolio Management,
and Oracle Fusion Supply Chain applications rely on deriving the legal entity information from the business unit.
Legal Entity and its Relationship to Divisions

The division is an area of management responsibility that can correspond to a collection of legal entities. If desired, you can
aggregate the results for your divisions by legal entity or by combining parts of other legal entities. Define date-effective
hierarchies for your cost center or legal entity segment in your chart of accounts to facilitate the aggregation and reporting by
division. Divisions and legal entities are independent concepts.
Legal Entity and Its Relationship to Ledgers

One of your major responsibilities is to file financial statements for your legal entities. Map legal entities to specific ledgers
using the Oracle Fusion General Ledger Accounting Configuration Manager. Within a ledger, you can optionally map a legal
entity to one or more balancing segment values.
Legal Entity and Its Relationship to Balancing Segments

Oracle Fusion General Ledger supports up to three balancing segments. Best practices recommend that one of these
segments represents your legal entity to ease your requirement to account for your operations to regulatory agencies, tax
authorities, and investors. Accounting for your operations means you must produce a balanced trial balance sheet by legal
entity. If you account for many legal entities in a single ledger, you must:
1. Identify the legal entities within the ledger.
89
2. Balance transactions that cross legal entity boundaries through intercompany transactions.
3. Decide which balancing segments correspond to each legal entity and assign them in Oracle Fusion General
Ledger Accounting Configuration Manager. Once you assign one balancing segment value in a ledger, then all
your balancing segment values must be assigned. This recommended best practice facilitates reporting on assets,
liabilities, and income by legal entity.
Represent your legal entities by at least one balancing segment value. You may represent it by two or three balancing
segment values if more granular reporting is required. For example, if your legal entity operates in multiple jurisdictions in
Europe, you might define 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 division or
business unit. For example, use this solution 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 are disposing of a part of a legal entity and need to isolate the assets and
liabilities for that entity.
Important
Implementing multiple balancing segments requires every journal entry that is not balanced by division or business
unit, to generate balancing lines. Also, you cannot change to multiple balancing segments easily after you have
begun to use the ledger because your historical data is not balanced by the new multiple balancing segments.
Restating historical data must be done at that point.
If your enterprise regularly spins off businesses or if they hold managers of those businesses accountable for
utilization of assets, it make be useful to identify the business with a balancing segment value. If you decided
to account for each legal entity in a separate ledger, there is no requirement to identify the legal entity with a
balancing segment value within the ledger.
Tip
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 it is not a separate legal entity. If you do not map legal entities sharing the same ledger
to balancing segments, you are not be able to distinguish them using the intercompany functionality or track their
individual equity.
Legal Entity and Its Relationship to Consolidation Rules

In Oracle Fusion Applications you can map legal entities to balancing segments and then define consolidation rules using
your balancing segments. You are creating a relationship between the definition of your legal entities and their role in your
consolidation.
Legal Entity and its Relationship to Intercompany Transactions

Use Oracle Fusion Intercompany feature to create intercompany entries automatically across your balancing segments.
Intercompany processing updates legal ownership within the enterprise's groups of legal entities. Invoices or journals
are created as needed. To limit the number of trading pairs for your enterprise, set up intercompany organizations and
assign then to your authorized legal entities. Define processing options and intercompany accounts to use when creating
intercompany transactions and to assist in consolidation elimination entries. These accounts are derived and automatically
entered on your intercompany transactions based on legal entities assigned to your intercompany organizations.
Intracompany trading, in which legal ownership isn't changed but other organizational responsibilities are, is also supported.
For example, you can track assets and liabilities that move between your departments within your legal entities by creating
departmental level intercompany organizations.
90
Tip
In the Oracle Fusion Supply Chain applications, model intercompany relationships using business units, from
which legal entities are inferred.
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 Configurator. You must enter
legal employers on worker assignments in Oracle Fusion HCM.
Legal Entity and Payroll Reporting

Your legal entities are required to pay payroll tax and social insurance such as social security on your payroll. In Oracle Fusion
Applications, you can register payroll statutory units to pay and report on payroll tax and social insurance on behalf of many
of your legal entities. As the legal employer, you might be required to pay payroll tax, not only at the national level, but also
at the local level. You meet this obligation by establishing your legal entity as a place of work within the jurisdiction of a local
authority. Set up legal reporting units to represent the part of your enterprise with a specific legal reporting obligation. You can
also mark these legal reporting units as tax reporting units, if the legal entity must pay taxes as a result of establishing a place
of business within the jurisdiction.
Define Legal Entities: Manage Legislative Data

Groups
Legislative Data Groups: Explained

Legislative data groups are a means of partitioning payroll and related data. At least one legislative data group is required for
each country where the enterprise operates. Each legislative data group is associated with one or more payroll statutory units.
Each payroll statutory unit can belong to only one legislative data group.
Payroll-related information, such as elements, is organized by legislative data groups. Each legislative data group:
• Marks a legislation in which payroll is processed.

• Is associated with a legislative code, currency, and its own cost allocation key flexfield structure.
• Is a boundary that can share the same set up and still comply with the local laws.
• Can span many jurisdictions as long as they are within one country.
• Can contain many legal entities that act as payroll statutory units.
Define Legal Entities: Manage Legal Entity HCM

Information
HCM Organization Models: Examples

These examples illustrate different models for human capital management (HCM) organizations that include a legislative data
group (LDG).
91
LDGs are not organization classification, but are included in the example to show how to associate them with a payroll
statutory unit to partition payroll data.
Simple Configuration
This example illustrates a simple configuration that does not include any tax reporting units.
Note the following:
• The legal employer and payroll statutory units are the same, sharing the same boundaries.
• Reporting can only be done at a single level. Countries such as Saudi Arabia and the United Arab Emirates (UAE)
might use this type of model, as reporting in these countries is done at the legal entity level.
This figure illustrates a simple configuration where the enterprise has only one legal entity that is both a payroll statutory unit
and a legal employer.
Multiple Legal Employers and Tax Reporting Units

This example illustrates a more complex configuration. In this enterprise, you define one legal entity, InFusion US as a
payroll statutory unit and having two separate legal entities, which are also legal employers. This model shows multiple legal
employers that are associated with a single payroll statutory unit, and how tax reporting units are always associated with a
specific legal employer (or employers) through the payroll statutory unit.
The implication is that payroll statutory reporting boundaries vary from human resources (HR) management, and you can
categorize the balances separately by either payroll statutory unit, legal employer, or tax reporting unit. This configuration
is based on tax filing 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.
92
This figure illustrates an enterprise that has one payroll statutory unit and multiple legal employers and tax reporting units.
One Payroll Statutory Unit and Two Tax Reporting Units

This model makes no distinction between a legal employer and a payroll statutory unit. You define tax reporting units are
defined as subsidiaries to the legal entity.
In this enterprise, legal entity is the highest level of aggregation for payroll calculations and reporting, and statutory reporting
boundaries are the same for both payroll and HR management. An example of a country that might use this model is France.
93
This figure illustrates an example of an organization with one legal entity that is both a legal employer and a payroll statutory
unit and that has two tax reporting units.
One Payroll Statutory Unit with Several Tax Reporting Units

In this model, the enterprise has one legal entity. Legal employers and tax reporting units are independent from each other
within a payroll statutory unit, because there is no relationship from a legal perspective. Therefore, you can run reporting on
both entities independently.
Using this model, you wouldn't typically 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.
94
This figure illustrates an enterprise with one legal entity that is a payroll statutory unit and a legal employer, and the tax
reporting units are independent from the legal employer.
Multiple Payroll Statutory Units with Several Tax Reporting Units

In this model, the enterprise has two legal entities. The legal employers and tax reporting units are independent from each
other within a payroll statutory unit, because there is no relationship from a legal perspective. Therefore, you can run reporting
on both entities independently.
Using this model, you wouldn't typically 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).
95
This figure illustrates an enterprise with two legal entities, and legal employers and tax reporting units are independent from
each other.
Payroll Statutory Units, Legal Employers, and Tax Reporting

Units: How They Work Together
When you set up legal entities, you can identify them as legal employers and payroll statutory units, which makes them
available for use in Oracle Fusion Human Capital Management (HCM). Depending on how your organization is structured, you
may have only one legal entity that is also a payroll statutory unit and a legal employer, or you may have multiple legal entities,
payroll statutory units, and legal employers.
96
Legal Employers and Payroll Statutory Unit

Payroll statutory units enable you to group legal employers so that you can perform statutory calculations at a higher level,
such as for court orders or for United Kingdom (UK) statutory sick pay. In some cases, a legal employer is also a payroll
statutory unit. However, your organization may have several legal employers under one payroll statutory unit. A legal employer
can belong to only one payroll statutory unit.
Payroll Statutory Units and Tax Reporting Units

Payroll statutory units and tax reporting units have a parent-child relationship, with the payroll statutory unit being the parent.
Tax Reporting Units and Legal Employers

Tax reporting units are indirectly associated with a legal employer through the payroll statutory unit. One or more tax reporting
units can be used by a single legal employer, and a tax reporting unit can be used by one or more legal employers. For
example, assume that a single tax reporting unit is linked to a payroll statutory unit. Assume also that two legal employers are
associated with this payroll statutory unit. In this example, both legal employers are associated with the single tax reporting
unit.
Use the Manage Legal Reporting Unit HCM Information task to designate an existing legal reporting unit as a tax reporting
unit. If you create a new legal reporting unit that belongs to a legal employer (that is not also a payroll statutory unit), you
select a parent payroll statutory unit and then, when you run the Manage Legal Reporting Unit HCM Information task, you
designate it as a tax reporting unit and select the legal employer.
Related Topics
• What's a tax reporting unit?
FAQs for Manage Legal Entity HCM Information

What's a legal employer?
A legal employer is a legal entity that employs workers. You define a legal entity as a legal employer in the Oracle Fusion Legal
Entity Configurator.
The legal employer is captured at the work relationship level, and all employment terms and assignments within that
relationship are automatically with that legal employer. Legal employer information for worker assignments is also used for
reporting purposes.
What's a payroll statutory unit?

Payroll statutory units are legal entities that are responsible for paying workers, including the payment of payroll tax and
social insurance. A payroll statutory unit can pay and report on payroll tax and social insurance on behalf of one or many
legal entities, depending on the structure of your enterprise. For example, if you are a multinational, multicompany 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.
97
Define Legal Entities: Manage Legal Entity Tax Profile
Party Tax Profiles: Explained

A tax profile is the body of information that relates to a party's transaction tax activities. A tax profile can include main and
default information, tax registration, tax exemptions, party fiscal classifications, tax reporting codes, configuration options, and
service subscriptions.
Set up tax profiles for the following parties involved in your transactions:
• First parties: All legal entities, legal reporting units, and business units in your organization that have a transaction tax
requirement.
• Third parties: Your customers and suppliers and their locations and banks.
• Tax authorities: Parties that administer tax rules and regulations.
First Parties
Set up tax profiles for your first-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 more accurately model your external relationships to legal authorities. The relationships
between first-party legal entities and the relevant tax authorities normally control the setup of the transaction taxes required by
your business. Under most circumstances the tax setup is used and maintained based on the configuration of the legal entity.
Enter the default information, party fiscal classifications, tax reporting codes, and configuration 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 office, service center, warehouse and any other location within the organization
that has a tax requirement. A legal reporting unit tax profile is automatically created for the headquarter legal entity. Set
up additional legal reporting unit tax profiles for those needed for tax purposes. For legal reporting units, enter the default
information, tax registrations, party fiscal classifications, and tax reporting codes. Also, define 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, financial monitoring, and reporting
requirements. To help you manage the tax needs of your business units, you can use the business unit tax profile in either of
two ways:
• Indicate that business unit tax setup is used and maintained based on the configuration of the associated legal entity
at transaction time. The tax setup of the associated legal entity setup is either specific to the legal entity or shared
across legal entities using the Global Configuration Owner setup.
• Indicate that tax setup is used and maintained by a specific business unit. Create configuration 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, configuration options, and
service providers as required.
Third Parties
Set up third-party tax profiles for parties with the usage of customer, supplier, and their sites. Enter the default information,
tax registrations, party fiscal classifications, 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 specified on the bank record is
added to the party tax profile record in Oracle Fusion Tax. You can't modify the party tax profile for a bank as it's view only.
You can only modify the bank record itself.
98
Note
Setting up party tax profiles for third parties is not required. Taxes are still calculated on transactions for third
parties that don't have tax profiles
Tax Authorities
Set up a tax authority party tax profile using the Legal Authorities set up task. The tax authority party tax profile identifies a tax
authority party as a collecting authority or a reporting authority or both. A collecting tax authority manages the administration
of tax remittances. 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
• Specifying Third-Party Tax Profile Options: Points to Consider
• When does a party tax profile get created for a third party?
Specifying First-Party Tax Profile Options: Points to Consider

Set up first-party tax profiles for all legal entities, legal reporting units, and business units in your organization that have a
transaction tax requirements. How you set up your first parties can impact the tax calculation on your transactions.
The first-party tax profile consists of:
• Defaults and controls: Applicable to legal entities and legal reporting units. Business units that use their own tax
setup do not have defaults and controls.
• Tax registrations: Applicable to legal reporting units.
• Party fiscal classifications: Applicable to legal entities and legal reporting units.
• Tax reporting codes: Applicable to legal entities, legal reporting units, and business units who do not use the tax
setup of the legal entity.
• Configuration options: Applicable to legal entities and business units who do not use the tax setup of the legal entity.
• Service subscriptions: Applicable to legal entities and business units who do not use the tax setup of the legal entity.
Defaults and Controls

The following table describes the defaults and controls available at the first-party tax profile level:
Option Description
Set as self-assessment (reverse charge) Automatically self-assess taxes on purchases.

Rounding Level Perform rounding operations on the:
• 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.
99
Option Description
Rounding Rule The rule that defines how the rounding should be
performed on a value involved in a taxable transaction.
For example, up to the next highest value, down to the
next lowest value, or nearest.

Note
If you defined a rounding precedence
hierarchy in the configuration owner tax
option settings for the combination of
configuration owner and event class, Oracle
Fusion Tax considers the rounding details in
the applicable tax profile.

Set Invoice Values as Tax Inclusive This first party intends to send or receive invoices with
invoice line amount inclusive of the tax amount.

Note
This option overrides the tax inclusive
handling setting at the tax level, but not at the
tax rate level.

Tax Registrations
You must set up a separate tax registration to represent each distinct registration requirement for a first-party legal reporting
unit. Oracle Fusion Tax uses tax registrations in tax determination and tax reporting. If your first party has more than one tax
registration under 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 configuration option on the first-party tax regime to allow entry of global tax
reporting configuration details during tax registration setup for legal reporting units for these tax regimes.
Party Fiscal Classifications

If applicable, associate first-party fiscal classification codes with this party. The party fiscal classification codes you enter
become part of tax determination for invoices associated with this party. Specify start and end dates to control when these
fiscal classifications are applicable for this party and transaction.
For legal entities, you can view the associated legal classifications that were assigned to the tax regime defined for this first
party. The legal classifications are used in the tax determination process, similarly to the party fiscal classifications.
Tax Reporting Codes

Set up tax reporting types to capture additional tax information on transactions for your tax reports for your first parties.
Depending on the tax reporting type code, you either enter or select a tax reporting code for this party. Specify start and end
dates to control when these tax reporting codes are applicable.
Configuration Options
The legal entities and business units in your organization are each subject to specific sets of tax regulations as designated by
the tax authorities where you do business. Use configuration options to associate legal entities and business units with their
100
applicable tax regimes. You can set up tax configuration options when you create a tax regime or when you create a party tax
profile. Both setup flows display and maintain the same party and tax regime definitions.
Service Subscriptions
Oracle Fusion Tax lets you use the tax services of external service providers for tax calculation of US Sales and Use Tax on
Receivables transactions. The setup for provider services is called a service subscription. A service subscription applies to the
transactions of one configuration option setup for a combination of tax regime and legal entity or business unit. Set up service
subscriptions when you create a tax regime or when you create a party tax profile for a first-party legal entity or business unit.
Related Topics
• Tax Registrations: Explained
• Configuration Options: Explained
• Setting Tax Reporting Configuration Controls for VAT: Critical Choices
• Party Information: Explained
• Rounding Precedence Hierarchy: How It Is Determined
FAQs for Manage Legal Entity Tax Profile

When does a party tax profile get created for a legal entity?
The legal entity party tax profile is automatically created when a legal entity record is created. If a legal entity party tax profile
record is not created, for example, when a legal entity is created through a back-end process, a legal entity party tax profile
is created upon saving the tax regime when a legal entity is subscribed to or upon saving the configuration owner tax options
when they are defined for the legal entity. Otherwise, create a party tax profile using the Create Legal Entity Tax Profile page.
You can edit the tax profile that was automatically generated with the relevant tax information, but it is not required.
101
Implementing Project Financial Management Define Financial Reporting Structures
5 Define Financial Reporting Structures
Manage Currencies
Defining Currencies: Points to Consider

When creating or editing currencies, consider these points relevant to entering the currency code, date range, or symbol for
the currency.
Currency Codes
You cannot change a currency code after you enable the currency, even if you later disable that currency.
Date Ranges
Users can enter transactions denominated in the currency only for the dates within the specified range. If you do not enter a
start date, then the currency is valid immediately. If you do not enter an end date, then the currency is valid indefinitely.
Symbols
Even if you enter a symbol for a currency, the symbol is not always displayed when an amount is displayed in this currency.
Some applications use currency symbols when displaying amounts. Others, like Oracle Fusion General Ledger, do not.
Related Topics
• What's a statistical unit currency type?
Euro Currency Derivation: Explained

Use the Derivation Type, Derivation Factor, and Derivation Effective Date fields to define the relationship between the official
currency (Euro) of the European Monetary Union (EMU) and the national currencies of EMU member states. For each EMU
currency, you define its Euro-to-EMU fixed conversion rate and the effective starting date.
Note
If you need to use a different currency code for Euro, you can disable the predefined Euro currency and create a
new one.
Derivation Type
The Euro currency derivation type is used only for the Euro, and the Euro derived derivation type identifies national
currencies of EMU member states. All other currencies do not have derivation types.
Derivation Factor
The derivation factor is the fixed conversion rate by which you multiply one Euro to derive the equivalent EMU currency
amount. The Euro currency itself should not have a derivation factor.
Derivation Effective Date

The derivation effective date is the date on which the relationship between the EMU currency and the Euro begins.
102
FAQs for Manage Currencies

When do I create or enable currencies?
Create or enable any currency for displaying monetary amounts, assigning currency to ledgers, entering transactions,
recording balances, or for any reporting purpose. Oracle Fusion Applications supports all currencies from the International
Organization for Standardization (ISO) 4217 standard.
The default currency is set to United States Dollar (USD).
What's the difference between precision, extended precision, and minimum accountable
unit for a currency?
Precision is the number of digits to the right of the decimal point used in regular currency transactions. Extended precision
is the number of digits to the right of the decimal point used in calculations for this currency, and it must be greater than or
equal to the standard precision. For example, USD would have 2 for precision because amounts are transacted as such, for
example $1.00. For calculations, for example adding USD amounts, you might want the application to be more precise than
two decimal digits, and would enter an extended precision accordingly.
Note
Some applications use extended precision. Others, such as Oracle Fusion General Ledger, do not.
Minimum accountable unit is the smallest denomination for the currency. For example, for USD that would be .01 for the cent.
This unit does not necessarily correspond to the precision for all currencies.
Manage Conversion Rate Types
Creating Conversion Rate Types: Critical Choices

Maintain different conversion rates between currencies for the same period with the Oracle Fusion General Ledger conversion
rate types functionality. Four predefined daily conversion rate types are seeded:
• Spot
• Corporate
• User
• Fixed
You can use different rate types for different business needs. During journal entry, the conversion rate is provided
automatically by the General Ledger based on the selected conversion rate type and currency, unless the rate type is user.
For user rate types, you must enter the conversion rate. Define additional rate types as needed. Set your most frequently
used rate type as the default. Conversion rate types cannot 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 predefined rate type Spot to populate your period average rates and
the predefined rate type Corporate to populate your 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:
• Convert foreign currency journal amounts to ledger currency equivalents.
103
• Convert journal amounts from source ledgers to reporting currencies or secondary ledgers.
• Run Revaluation or Translation processes.
In creating new conversion rates, decide whether to do the following:
• Enforce inverse relationships

• Select pivot currencies
• Select contra currencies
• Enable cross rates and allow cross rate overrides
• Maintain cross rate rules
Enforce Inverse Relationships

Check the Enforce Inverse Relationship check box to specify whether or not to enforce the automatic calculation of
inverse conversion rates when defining daily rates.
Action Results
Checked When you enter a daily rate to convert currency A to

currency B, General Ledger automatically calculates
the inverse rate, currency B to A, and enters it 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 check
box enforces that the inverse relationship is maintained
but does not prevent you from updating the rates.

Unchecked General Ledger calculates the inverse rate but you can
change the rate and update the daily rates table without
the corresponding rate being updated.

Select Pivot Currencies

Select a pivot currency that is commonly used in your currency conversions. A pivot currency is the central currency that
interacts with contra currencies. For example, you set up a daily rate between the US dollar (USD) and the Euro currency
(EUR) and another between the USD and the Canadian dollar (CAD). USD is the pivot currency in creating a rate between
EUR and CAD. EUR and CAD are the contra currencies. Select the pivot currency from the list of values which contains those
currencies that are enabled, effective, and not a statistical (STAT) currency. The description of the pivot currency is populated
automatically based on the currency definition.
If you want the application to create cross rates against a base currency, define the base currency as the pivot currency.
Selected pivot currencies can be changed in the Rate Types page.
Select Contra Currencies

Select currencies available on the list of values as contra currencies. The available currencies are those currencies which are
enabled, effective, not STAT currency, and not the pivot currency selected earlier. The description of the contra currency is
populated automatically based on the currency definition. Add or delete contra currencies in the Contra Currencies region of
the Rate Types page.
104
Enable Cross Rates and Allow Cross Rate Overrides

Check the Enable Cross Rates check box to calculate conversion rates based on defined currency rate relationships.
General Ledger calculates cross rates based on your defined cross rate rules. Associate your cross rate rules with a
conversion rate type, pivot currency, and contra currencies. Cross rates facilitate the creation of daily rates by automatically
creating the rates between contra currencies based on their relationship to a pivot currency. If the Enable Cross Rates
check box is changed to unchecked after entering contra currencies, the application stops calculating cross rates going
forward for that particular rate type. All the earlier calculated cross rates for that rate type remain in the database unless you
manually delete them.
For example, if you have daily rates defined for the pivot currency, USD to the contra currency, EUR, and USD to another
contra currency, CAD, the application will automatically create the rates between EUR to CAD and CAD to EUR. This
prevents the need to manually define the EUR to CAD and CAD to EUR rates.
Check the Allow Cross Rates Override check box to permit your users to override application generated cross rates. If you
accept the default of unchecked, the application generated cross rates cannot be overridden
Maintain Cross Rate Rules

Define or update your cross rate rules at any time by adding or removing contra currency assignments. Add a contra currency
to a cross rate rule and run the Daily Rates Import and Calculation process to generate the new rates. If your remove a cross
rate rule or a contra currency from a rule, any cross rates generated previously for that contra currency remain unless you
manually delete them. Changes to the rule are not retroactive and will not affect previously stored cross rates. The Cross Rate
process generates as many rates as possible and skips currencies where one component of the set is missing.
Note
With a defined web service that extracts daily currency conversion rates from external services, for example
Reuters, currency conversion rates are automatically updated for the daily rates and all cross currency
relationships.
Using Rate Types: Examples

There are four seeded conversion rate types in Oracle Fusion applications:
• Spot
• Corporate
• User
• Fixed
Scenario
You are the general ledger accountant for InFusion America Inc. You are entering a journal entry to capture three transactions
that were transacted in three different foreign currencies:
• Canadian dollar (CAD): A stable currency

• Mexican Peso (MXP): A fluctuating currency
• Hong Kong dollar (HKD): An infrequently used currency
You enter two lines with accounts and amounts for each foreign currency transaction. Based on your company procedures,
you select the appropriate 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.
105
Currency Selected Rate Type Selected Reason
CAD Corporate Entered a periodic type of

transaction. Your company has
established a daily rate to use for
the entire month across divisions
for all transactions in CAD. CAD
is a stable currency that only
fluctuations slightly over the month.

MXP Spot Entered a periodic type of

transaction. Your company enters
daily rates each day for MXP
because this currency is unstable
and fluctuates.

HKD User Entered a one time transaction.

Your company does not maintain
daily rates in HKD.

Note
Your company does not currently use the Fixed rate type. From January 1, 1999, the conversion rate of the
French franc (FRF) against the euro currency (EUR) was set at a fixed 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 EUR.
FAQs for Manage Conversion Rate Types

What's the difference between spot, corporate, user, and fixed rate types?
Spot, corporate, user, and fixed conversion rate types differ based on the fluctuations of your entered foreign currency and
your company procedures for maintaining daily rates.
Rate Type Usage
Spot For currencies with fluctuating conversion rates or when

exact currency conversion is needed.

Corporate For establishment of a standard rate across your

organization for a stable currency.

User For infrequent entries where your daily rates for the
entered foreign currency are not set up.

106
Rate Type Usage
Fixed For rates where the conversion is constant between two

currencies.

If you have infrequent foreign currency transactions, the user rate type can simplify your currency maintenance while providing
an accurate conversion rate on the date of the transaction.
Manage Daily Rates
Entering Daily Rates Manually: Worked Example

You are required to enter the daily rates for currency conversion from Great Britain pounds sterling (GBP) to United States
dollars (USD) each day for your company InFusion America Inc.
Oracle Application Development Framework (ADF) Desktop Integration is an Excel add-in that must be loaded onto each
client. Because ADF Desktop Integration is an add-in to Microsoft Office products, you can use this feature only if they have
Microsoft Excel 2007 or above, Internet Explorer 7 or above, and Microsoft Windows 7, XP Professional SP2, or Vista. Users
must download the installation files from Navigator > Tools > Download Desktop Integrator Installer.
Entering Daily Rates

1. Navigator > Period Close.
Use the Period Close work area to link to close processes and currency process.
2. Click the Manage Currency Rates link.
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 Create in Spreadsheetbutton.
Use the Create Daily Rates spreadsheet to enter daily rates in a template that you can save and reuse.
5. Click in the From Currency field. Select the GBP - Pound Sterling list item.
6. Click in the To Currency field. Select the USD - US Dollar list item.
7. Click in the Conversion Rate field. Select the Spot list item
8. Click in the From Conversion field. Enter a valid value e.g. "8/1/2011".
9. Click in the To Conversion Date field. Enter a valid value e.g. "8/1/2011".
10. Click in the Conversion Rate field. Enter a valid value e.g. "1.33225".
11. Click the Submit > OK twice.
12. Review the Record Status column to verify that all rows were loaded successfully.
13. Save the template to use to enter daily rates frequently. You can save the spreadsheet to either a local drive or a
shared network drive.
Related Topics
107
Updating Currency Rates: Worked Example

You are required to change today's daily rates that were already entered. The rates you are changing are for currency
conversion from Great Britain pounds sterling (GBP) to United States dollars (USD) for your company InFusion America Inc.
Currency conversion rates were entered by an automatic load to the Daily Rates table. They can also be entered through a
spreadsheet.
Updating Currency Rates

1. Navigate to the Period Close work area.
Use the Period Close work area to link to close processes and currency process.
2. Click the Manage Currency Rates link.
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 button.
9. Click in the Rate field. Enter the new rate of 1.7 in the Rate field.
10. Click in the Inverse Rate field. Enter the new inverse rate of 0.58822 in the Inverse Rate field.
11. Click the Save button.
Related Topics
Define Chart of Accounts for Enterprise Structures:

Manage Chart of Accounts Structures and Structure
Instances
Chart of Accounts: Explained

The chart of accounts is the underlying structure for organizing financial information and reporting. An entity records
transactions with a set of codes representing balances by type, expenses by function, and other divisional or organizational
codes that are important to its business.
A well-designed chart of accounts provides the following benefits:
• Effectively manages an organization's financial business.
• Supports the audit and control of financial transactions.
• Provides flexibility for management reporting and analysis.
108
• Anticipates growth and maintenance needs as organizational changes occur.

• Facilitates an efficient data processing flow.
• Allows for delegation of responsibility for cost control, profit attainment, and asset utilization.
• Measures performance against corporate objectives by your managers.
The chart of accounts facilitates aggregating data from different operations, from within an operation, and from different
business flows, thus enabling the organization to report using consistent definitions 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.
Chart of Accounts: How Its Components Fit Together

The important elements in a basic chart of accounts in Oracle Fusion Applications included a structure that defines the
account values, segments and their labels, and rules (security and validation). Account combinations link the values in the
segments together and provide the accounting mechanism to capture financial transactions.
Chart of Accounts
The chart of accounts defines the number and attributes of various segments, including:
• Order of segments
109
• Width of segments
• Prompts
• Segment labels, such as balancing, natural account, and cost center.
The chart of accounts further defines:
• Combination of value sets associated with each segment
• Type of segment
• Default values for the segments
• Additional conditions designating the source of the values using database tables
• Required and displayed properties for the segments
Segments
A chart of accounts segment is a component of the account combination. Each segment has a value set attached to it to
provide formatting and validation of the set of values used with that segment. The combination of segments creates the
account combination used for recording and reporting financial 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.
Value Sets and Values

The value sets define the attributes and values associated with a segment of the chart of accounts. You can think of a value
set as a container for your values. You can set up your flexfield so that it automatically validates the segment values that
you enter against a table of valid values. If you enter an invalid segment value, a list of valid values appears automatically so
that you can select a valid value. You can assign a single value set to more than one segment, and you can share value sets
across different flexfields.
Caution
You must use Independent validation only for the Accounting Key Flexfield 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 are not 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 flexfield qualifiers 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 specific
business expenses across natural accounts. As cost centers combine expenses and headcount data into costs,
they are useful for detailed analysis and reporting. Cost centers are optional, but required if you are accounting for
depreciation, additions, and other transactions in Oracle Fusion Assets, and for storing expense approval limits in
Oracle Fusion Expense Management.
• Natural Account: Determines the account type (asset, liability, expense, revenue, or equity) and other information
specific to the segment value. The natural account segment label is required.
• Management: Optionally, denotes the segment that has management responsibility, such as the department, cost
center, or line of business. Also can be attached to the same segment as one of the balancing segments to make
legal entity reporting more granular.
• Intercompany: Optionally, assigns the segment to be used in intercompany balancing functionality.
110
Note
All segments have a segment qualifier that enables posting for each value. The predefined setting is Yes to post.
Account Combinations
An account combination is a completed code of segment values that uniquely identifies 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 different types of rules to control functionality.
• Security rules: Prohibit certain users from accessing specific 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.
Create Chart of Accounts, Ledger, Legal Entities, and

Business Units in Spreadsheets: Explained
Represent your enterprise structures in your chart of accounts, ledger, legal entities, and business unit configuration to track
and report on your financial objectives and meet your reporting requirements. These components are the underlying structure
for organizing financial information and reporting.
The chart of accounts within the ledger facilitates:
• Aggregating data from different operations, from within an operation, and from different business flows
• Consistent definitions to your stakeholders in compliance with legislative and corporate reporting standards and aids
in management decisions.
Rapid implementation is a way to configure the Oracle Fusion Financial Enterprise and Financial Reporting Structures quickly
using sheets in a workbook to upload lists of:
• Companies (Legal Entities)
• Ledgers by Country
• Business Units
• Chart of Account Values
• Financial Sequences
• Hierarchies
Once the sheets have been uploaded, the application creates your:
• Chart of Accounts Structure and Instance
• Key Accounts such as Retained Earnings and Account Payables.
• Calendar
• Ledgers by Country
• Legal Entities and Their Locations
• Business Units
• Document and Journal Sequences
111
The following graphic shows the relationship of these components.
• Legal Entities: Identifies a recognized party with rights and responsibilities given by legislation, which has the right
to own property and the responsibility to account for themselves.
• Chart of Accounts: Configures accounts consisting of components called segments that are used to record
balances and organize your financial information and reporting.
• Segments: Contains a value set that provides formatting and validation of the set of values used with that segment.
When combined, several segments create an account for recording your transactions and journal entries.
• Segment Labels: Identifies certain segments in your chart of accounts and assigns special functionality to those
segments. The three required segment labels are:
◦ Balancing Segments: Ensures that all journals balance for each balancing segment value or combination of
multiple balancing segment values to use in financial processes and reporting. The three balancing segment
labels are: primary, second, and third balancing. The primary balancing segment label is required.
◦ Natural Account: Facilities processes in the General Ledger application, such as retained earnings posting.
For each child value, you must assign an Account Type. You can select from one of the general choices to
mark the account value as an Asset, Liability, Owner's Equity, Revenue, or Expense account.
112
If the account is used by the Rapid Implementation solution to provide accounts for setup objects, select the
appropriate Expanded Account Type for the child account. Examples of expanded account types required for
setup objects are:
• Owner's Equity - Retained Earnings to setup General Ledger ledgers.
• Liability - Accounts Payable to setup Payables common options.
• Asset - Account Receivable to setup Receivables receipt methods.
For accounts that are tagged with these special account types, the Financial Category defaults. You can
override the defaults in the Financial Category or leave it out.
◦ Cost Center: Facilitates grouping of natural accounts by functional cost types, accommodating tracking of
specific business expenses across natural accounts.
• Ledger: Maintains the records and is a required component in your configuration. The Rapid implementation
process:
◦ Creates your ledgers by combining your chart of accounts, calendar, and currency as well as other required
options defined in the sheets.
◦ Assigns a default for the fourth component, the subledger accounting method, used to group subledger journal
entry rule sets together to define a consistent accounting treatment.
◦ Creates a balances cube for each ledger with a unique chart of accounts and calendar. Each segment is
created as a dimension in the balances cube.
• Business Units with Business Functions: Identifies where subledger transactions are posted and provides
access to perform subledger business processes. Business units are assigned to a primary ledger, as well as a
default legal entity, when configured and identify where subledger transactions are posted.
• Subledgers: 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.
113
Note
Hierarchies: You can create more than one hierarchy for any of your chart of accounts segments. You can also
create additional hierarchies after the spreadsheet has been loaded once.
Document and Journal Sequences: You can create sequences for each legal entity or ledger based on the
predefined country defaults. Document Sequences are created for:
• Payables Invoices
• Payments
• Receivables Invoices
• Receivables Credit Memos
• Receivables Adjustment Activities
Reporting and Accounting Journal Sequences are created for:
• Subledger Journals
• General Ledger Journals
Create Chart of Accounts, Ledger, Legal Entities, and

Business Units in Spreadsheets: How They Are Processed
The Create Chart of Accounts, Ledger, Legal Entities, and Business Units rapid implementation process consists of four
steps.
1. Enter the data into the sheets.
2. Upload the XML files generated from the sheets.
3. Run the deployment process to finalize the chart of accounts configuration.
4. Upload the XML files generated from the sheets for the rest of the configuration.
Note
On the Instruction sheet is a link to a completed sample data workbook.
114
Process Overview
Begin by downloading the Rapid Implementation for General Ledger workbook using the Create Chart of Accounts,
Ledger, Legal Entities, and Business Units in Spreadsheet task on the Setup and Maintenance work area.
The following figure illustrates the Create Chart of Accounts, Ledger, Legal Entities, and Business Units process, what data is
entered into each sheet of the workbook, and the components that the process creates.
115
Process
Enter Data
The Create Chart of Accounts (COA), Ledger, Legal Entities, and Business Units workbook provides five sheets.
1. Instructions
2. COA, Calendar and Ledger
3. Business Units
4. Companies and Legal Entities
5. Natural Accounts
6. Financial Sequences
You create sheets to enter other segment values and hierarchies for additional segments by entering the segments on the
COA, Calendar, and Ledger sheet and then clicking the Add Segment Sheets or Create Hierarchies Only button.
Instructions Sheet
Read the planning tips, loading process, best practices, and recommendations.
COA, Calendar and Ledger Sheet

Enter your data to create your ledger, chart of accounts, currency, and calendar, and to set the required ledger options.
• Name: Enter the name of your primary ledgers. The name often appears in report titles, so enter a printable name.
Note
A primary ledger is created for each unique country entered in the Companies and Legal Entities sheet.
For example, if one of the legal entities is based in the United States and another in Canada, and the
ledger name is InFusion Ledger, then two primary ledgers, InFusion Ledger US and InFusion Ledger CA,
are created.
All 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.
116
• Currency: Enter the ledger currency in which most of your transactions are entered if you are not entering legal
entity data. If you are entering legal entities, leave the field blank. The currency is supplied by default based on the
country.
• Period Frequency: Select the frequency for your calendar.
• Adjusting Periods: Select the number of periods that are used to enter closing, auditing, or other adjustments in
the General Ledger at quarter or year end. The entries are tracked in the adjusting period and not in your monthly
activity.
• Fiscal Year Start Date: Enter the beginning date of your calendar for the ledgers. The date cannot be changed
after the ledgers are saved.
Important
Select a period before the first period in which you plan to load history or perform translations to enable
running translation. You cannot run translation in the first defined period of a ledger calendar.
• Chart of Accounts region: Enter your segments, segment labels, short prompts, and display width data that is
used to create your chart of accounts. Plan this data carefully because you are defining the basic structure for your
accounting and reporting.
◦ Segment: Enter the names of your segments.
◦ Segment Label: Select which segment the application uses for certain processing, such as the Primary
Balancing, which is used to balance journal entries.
Note
If you select an intercompany segment label, you must complete at least one intercompany rule
and check the Enable Intercompany Balancing option in the Specify Ledger Options task for the
Balancing API to perform intercompany balancing.
◦ Short Prompt: Enter a short name for the application to use.
◦ Display Width: Enter the segment size. Select 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 button: Select to create sheets for additional segments. Only the Company and Natural
Account segment sheets are provided.
• Step 1: Validate button: Select to validate your entered data. A Validation Report is generated if any errors occur.
Correct these errors before proceeding.
• Step 2: Generate Chart of Accounts File: Select to create a file that is then uploaded to create the chart of
accounts structures, values, and hierarchies.
• Step 3: Generate Ledger, LE, and BU File: Select to create a file that is then uploaded to create ledgers, legal
entities and their locations, business units, and document and journal sequences.
• Create Hierarchies Only button: Select to create sheets to enter additional hierarchies after setup has been run
one time.
117
Business Units Sheet

Enter the name of your business units and related default legal entities.
Note
You can enter more than one business unit per ledger. Business units are created with entered names. Based on
the default legal entity entered in the Business Units sheet, the respective country's primary ledger is supplied by
default for the business unit (BU). The first legal entity that is associated with the ledger is supplied by default for
all the BUs of that country.
Companies and Legal Entities Sheet

Enter a list of your legal entities with their addresses, registration number, reporting unit registration number, and assigned
parent or child value. You can create up to 9 levels of parent values to use to roll up your legal entities to meet corporate and
local reporting requirements.
118
Natural Accounts Sheet

Enter your account values that are used to record the type of balance.
• Parent Values, Child Values and Descriptions: Entered to build 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 financial reporting, Smart View queries, and allocations.
• Account Type: Enter to identify the type of account: Asset, Liability, Revenue, Expense, or Owner's Equity. Account
types are used in year-end close processes and to correctly categorize your account balances for reporting.
If the account is used by the Rapid Implementation solution to provide accounts for setup objects, select the
appropriate Expanded Account Type for the child account. Examples of expanded account types required for setup
objects are:
◦ Owner's Equity - Retained Earnings to setup General Ledger ledgers.
◦ Liability - Accounts Payable to setup Payables common options.
◦ Asset - Account Receivable to setup Receivables receipt methods.
For accounts that are tagged with these special account types, the Financial Category defaults. You can override the
defaults in the Financial Category or leave it out.
• Financial Category button: Enter to identify groups of accounts for reporting with Oracle Fusion Transactional
Business Intelligence.
Generate Additional Hierarchy button: To create more than one hierarchy for any of your COA segments, click the
Generate Additional Hierarchy button on the country's sheet. This creates a worksheet and populates it with the data
already entered for that segment. Change this data as required for the new hierarchy. For the Company Segment, adding
Legal Entity information is not supported on the new hierarchy's sheet.
119
Note
When you create a new hierarchy sheet the name is derived by adding a counter to the sheet name.
• Click the button on Companies and Legal Entities sheet to generate a new sheet named Companies and Legal
Entities1.
• Click the button again then another sheet with the name Companies and Legal Entities2 is generated.
When you generate the upload files, each of these sheets are treated as a separate tree of the segment. You can
create new hierarchies only and not new versions of existing hierarchies.
Financial Sequences Sheet

Enable your document or journal sequences to assign unique numbers to your transactions to meet legal requirements.
The transactions the Document sequences are created for include:
• Payables Invoices
• Payments
• Receivables Invoices
• Receivables Credit Memos
• Receivables Adjustment Activities
Reporting and Accounting Journal Sequences are created for:
• Subledger Journals
• General Ledger Journals
Complete the following steps on the Financial Sequences sheet:
1. Enabled: Set to yes to enable document or journal sequences for the transaction type.
120
2. Restart: Set to restart the numbering based on one of the following criteria:
◦ Annually: Restart sequence numbers once a year.
◦ Monthly: Restart sequence numbers each month.
◦ Never: Never restart sequences numbers. Continue with the same sequence.
3. Initial Value: The beginning number in the sequence.
Upload the Sheets and Run Deployment

Return to the COA, Calendar, and Ledger sheet after completing the other sheets to complete the following steps:
1. (B) Step 1: Validate: The process validates your data entry.
2. (B) Step 2: Generate Chart of Accounts File: The process generates an XML data file for the entered chart of
accounts and hierarchies setup data. Save the file to a network or local drive.
3. (B) Step 3: Generate Ledger, Legal Entity, and Business Units File: The program generates an XML data file
for the entered ledger, legal entities, and business unit setup data. Save the file to a network or local drive.
4. (N) Setup and Maintenance > Functional Setup Manager > Upload Chart of Accounts task: The Upload
Enterprise Structures process is launched.
5. (B) Upload File.
6. Leave the Upload Enterprise Structure radio button selected.
7. (B) Browse: Select the first file that you saved: ChartOfAccounts.xml.
8. (B) Submit.
9. Verify that the process was completed without errors or warnings.
121
10. (N) Setup and Maintenance > Deploy Chart of Accounts task > (B) Deploy the Accounting Flexfield.
11. (I) Refresh until the green check mark appears and verifies that the deployment is successful.
12. (N) Setup and Maintenance > Upload Ledger, Legal Entities, and Business Units task. The Upload
Enterprise Structures process is launched.
13. (B) Upload File.
14. Leave the Upload Enterprise Structure radio button selected.
15. (B) Browse. Select the second file that you saved: FinancialsCommonEntities.xml.
16. (B) Submit.
17. Verify that the process was completed without errors or warnings.
Tip
You cannot change the chart of accounts, accounting calendar, or currency for your ledgers after the setup is
created. Assign the data role that was automatically generated for the ledgers to your users. Then open the first
accounting period to begin entering data.
Related Topics
• Create Hierarchies in a Spreadsheet: Example
Creating One Chart of Accounts Structure with Many

Instances: Example
In Oracle Fusion General Ledger, the chart of accounts model is framed around the concept of a chart of accounts structure,
under which one or more chart of accounts structure instances can be created.
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 committee to discuss creation of a model for your
global financial 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. Your product line includes all the components to
build and maintain air quality monitoring (AQM) systems for homes and businesses.
122
Analysis
under which one or more chart of accounts structure instances can be created.
Chart of Accounts Model

The chart of accounts structure provides the general outline of the chart of accounts and determines the number of
segments, the type, the length, and the label (qualifier) of each segment. This forms the foundation of the chart of accounts
definition object.
For each chart of accounts structure, it is possible to associate one or more chart of accounts structure instances. Chart of
accounts structure instances under the same structure share a common configuration with the same segments, in the same
order, and the same characteristics. Using one chart of accounts structure with multiple instances simplifies 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 different chart of accounts instances within the same structure or in different 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 code combinations automatically the first 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 code combinations. Well defined cross validation rules help prevent the creation of inappropriate
account code combinations.
Perform deployment after a new chart of accounts structure and structure instances are defined or any of their modifiable
attributes 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 different accounting and reporting requirements by using value sets specific to
each of your entities.
Creating Chart of Accounts Structure and Instances: Examples

under which one or more chart of accounts structure instances can be created. A chart of accounts structure defines the
key attributes for your chart of accounts, such as the number of segments, the segment sequences, the segment names,
segment prompts, segment labels, for example natural account and primary balancing, and default value sets.
The chart of accounts instance is exposed in the user interfaces and processes. By default, a chart of accounts instance
inherits all the attributes of the chart of accounts structure, meaning that all instances of the same structure share a common
shape and have the same segments in the same order. However, at the chart of accounts instance level, you can override
the default value set assignments for your segments and assign a unique account hierarchy that determines the parent and
child relationships between the value set values. At the chart of accounts instance level, determine if allow dynamic insertion
is enabled to generate new account combinations dynamically instead of creating them manually.
123
Chart of Account Structure

You are creating a chart of accounts structure as you setup your chart of accounts for your enterprise, InFusion America, Inc.
Follow these steps:
1. Navigator > Setup and Maintenance > Manage Chart of Accounts > Go To Task.
2. Select General Ledger from the Module list of values and click Search.
3. Click Manage Structures to open the Manage Key Flexfield Structures page.
4. Select the General Ledger row and click the Create to open the Create Key Flexfield Structure page.
5. Enter a unique Structure Code, INFUSION_AM_COA_STRUCTURE, and Name, InFusion America COA
Structure. Provide an optional Description, InFusion America Inc. Chart of Accounts Structure.
6. Select the - Delimiter to visually separate your segment values.
7. Save.
8. To create a new segment, click the Create to open the Create Key Flexfield Segment page.
a. Enter the following parameters:
Parameter Value
Segment Code INFUSION_AM_CO

Name InFusion America Company

Description InFusion America Inc.

Sequence Number 1

Prompt Company

Short Prompt CO

Display Width 2

Column Name Segment1

Default Value Set Code INFUSION_ AM_COMPANY

b. Select a segment label, Primary Balancing Segment, to indicate its purpose within your chart of accounts.
124
Note
Two segment labels are required: primary balancing segment and natural account segment. These
labels are not used with each other or with other labels in a specific segment.
c. Save and Close.

d. Done.
e. Define additional segments following the same process.
Chart of Account Instance

You are creating a chart of accounts instance as you setup your chart of accounts for your enterprise, InFusion America, Inc.
Follow these steps:
1. Navigator > Setup and Maintenance > Manage Chart of Accounts > Go To Task.
2. Select General Ledger from the Module list of values and click Search.
3. Select the General Ledger row and click Manage Structure Instances to open the Manage Key Flexfield
Structure Instance page.
4. Click the Create icon to open the Create Key Flexfield Structure Instance page.
5. Enter a 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 Dynamic combination creation allowed to indicate that you want to dynamically generate account
combinations.
7. Associate your instance with your Structure Name, InFusion America Structure.
Note
By default, an instance inherits the key attributes of the associated structure. Some attributes, such as
the value set assigned to each the segment, can be modified.
8. Save.
9. Optionally, select the segment row and click Edit to modify instance segments.
10. Check Required, Displayed, and BI enabled check boxes.
Note
Check the Required and Displayed options for all segments including those intended for future use. The
recommended best practice is to define 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 the account
combinations.
Check the BI (Business Intelligence) enabled option to use key flexfield segments in Oracle Fusion
Transactional Business Intelligence. The business intelligence check box is only valid when enabled on
segments with segment labels. The second step is to populate the BI Object Name field for each of the
segment labels in the Manage Segment Label page opened from the Manage Key Flexfields page.
125
11. OK.
12. Save and Close.
13. Define 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. Done.
15. Deploy Flexfield.
16. OK.
Related Topics
• Creating Accounting Flexfield Segment Values
• Enabling Key Flexfield Segments for Business Intelligence: Points to Consider
Balancing Segments: Explained

Balancing segments ensure that all journals balance for each balancing segment value or combination of multiple balancing
segment values. You can secure access to your primary balancing segment values only with data access sets. The General
Ledger application automatically calculates and creates balancing lines as required in journal entries.
The three balancing segment labels are:
• Primary
• Second
• Third
Note
The primary balancing segment label is required.
By enabling multiple balancing segments for your chart of accounts, you can produce financial statements for each unique
combination of segment values across one, two, or three qualified balancing segments. This ability provides you greater
insights into your operations as it affords you visibility along the critical fiscal dimensions you use to plan, monitor, and
measure your financial performance.
The following explains processes that use balancing segments.
• Intercompany balancing: Adds lines to unbalanced journals using intercompany rules.
• Opening first period of the accounting year: Calculates retained earnings amounts at the level of granularity that
totals revenue and expense account balances for multiple balancing segment value combinations. This applies to
standard and average balances.
126
• 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 specific 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 fluctuation differences between ranges of accounts which use different 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
difference in the reporting currency amounts is offset by populating retained earnings accounts.
• Closing year end: Supports multiple balancing segments when calculating the income statement offset and closing
account in the closing journals.
Multiple Balancing Segments: Points to Consider

Oracle Fusion General Ledger supports tracking financial results at a finer level of granularity than a single balancing segment.
In addition to the required primary balancing segment for the chart of accounts, which is typically associated with the
company dimension of a business organization, two additional segments of the chart of accounts can be optionally qualified
as the second and third balancing segments respectively. Possible chart of accounts segments that can be tagged as
these additional balancing segments include cost center or department, additional aspects of a business commonly used in
measuring financial results.
There are several points to consider in using multiple balancing segments:
• Journal entry processing
• Implementation timing
• Change options
• Migration adjustments
127
Journal Entry Processing

Multiple balancing segments ensure that account balances come from journal entries where the debits equal the credits,
and thus, the financial reports are properly generated for each unique instance of account value combinations across the
balancing segments. Consider this option carefully as it provides more granular reporting but requires more processing
resources.
Implementation Timing
When considering implementing the optional second and third balancing segments, keep in mind that these chart of accounts
segment labels are set from the beginning of time and are actively used by your ledgers. This is important to ensure that
balances are immediately maintained in accordance with the necessary balancing actions to produce consistent financial
reporting for the desired business dimensions. Multiple balancing segment ledgers that are not maintained from the beginning
of time require extensive manual balance adjustments to catch up and realign the balances in accordance with the multiple
balancing segments.
Note
Do not set a segment already qualified as a natural account or intercompany segment as any of the three
balancing segments. Validations are not 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 settings must be consistently maintained throughout the life of the
chart of accounts to control the accuracy and integrity of the financial data.
Migration Adjustments
For charts of accounts migrated from Oracle E-Business Suite to Oracle Fusion General Ledger that use a segment with the
secondary balance tracking segment qualifier, steps must be taken to ensure the proper transition to the second and third
balancing segments. The required adjustments are extensive.
For ledgers associated with a migrated chart of accounts, its balances must be adjusted manually to be consistent with the
second and third balancing segments as though these segment labels have been in place since the beginning of entries for
these ledgers. This requires recomputing and updating of the following processes to reflect the correct balancing for each
unique combination of segment values across the additional 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 fiscal year
• Cumulative translation adjustments during translation
Note
All previously translated balances must also be purged, and new translations run to properly account for
translated retained earnings and cumulative translation adjustments with the correct level of balancing.
128
Related Topics
• How can I change segments in an existing chart of accounts structure?
Using Multiple Balancing Segments: Example

This simple example illustrates balancing along two balancing segments for a simple chart of accounts with three segments.
Scenario
Your company has a chart of accounts with two balancing segments and three segments, qualified as follows:
• Company: Primary balancing segment

• Cost Center: Second balancing segment
• Account: Natural account segment
The following multiple company and cost center journal has been entered to transfer advertising and phone expense from
Company 1, Cost Center A to Company 2, Cost Center B.
Account Debit Credit
Company 1-Cost Center A- 600

Advertising Expense Account

Company 2-Cost Center B- 600


Company 1-Cost Center A-Phone 800

Expense Account

Company 2-Cost Center B-Phone 800

Expense Account

During the posting process, the last four lines are created to balance the entry across the primary and second balancing
segments, company and cost center.




129
Company 1-Cost Center A-Phone 800

Expense Account

Company 2-Cost Center B-Phone 800

Expense Account


Balancing Account


Balancing Account


Balancing Account


Balancing Account

FAQs for Manage Charts of Accounts Structures and Structure

Instances
How can I use future accounting segments?
To plan for future growth in the business organization that requires additional segments in the chart of accounts, extra
segments can be added to the chart of accounts structure during your original implementation. Since all segments of the
chart are required and have to be enabled, these unused segments can be assigned value sets that have a single value
in the chart of accounts structure instance. This value is set as a default for that segment so that the extra segments are
automatically populated when an account code combination is used.

Manage Chart of Accounts Value Sets and Value Set
Values
Chart of Accounts Values Sets: Critical Choices

A value set is the collection of account values that are associated with a segment of a chart of accounts structure instance.
When creating values sets, consider the following critical choices:
• Module Designation
130
• Validation Type
• Format Assignments
• Security Rules
• Values Definition
Module Designation
The module designation is used to tag value sets in Oracle Fusion Applications and sets the value sets apart during upgrades
and other processes. Chart of accounts value sets upgraded from Oracle E-Business Suite Release 12 generically bear
the module value of Oracle Fusion Middleware. When creating value sets for a chart of accounts, the module can be
specified as Oracle Fusion General Ledger to distinctly identify its intended use in an accounting flexfield, 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 filling out the segment in the account combination.
• Table Validated: The values are stored in an external table to facilitate maintenance and sharing of the reference
data.
Caution
You must use Independent validation only for the Accounting Key Flexfield 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 are not 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 setting 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 is assigned.
Best practices recommend restricting values to Upper Case Only or Numeric values that are zero filled by default.
Security Rules
If flexfield data security rules are to be applied to the chart of accounts segment associated with the value set, the Enable
Security check box must be checked for the assigned value set. 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 definition of flexfield
data security rules.
Value Definition
Once these basic characteristic are defined for the value set, values can be added to the set in the Manage Values page.
• Set the values to conform to the value set length and type.
• Enter the value, its description, and its attributes including the Enable check box, Start Date, and End Date.
• Assign the following attributes: Parent or Summary check box, Posting is allowed, and Budgeting is allowed.
131
Note
If the value set is used with a natural account segment, the value also requires you set the Natural Account
Type, with one of the following values: Asset, Liability, Equity, Revenue, or Expense. Other attributes used
are Third-Party Control Account, Reconciliation indicator, and Financial Category used with Oracle
Transaction Business Intelligence reporting.
Oracle Fusion General Ledger best practice is to define the values for the value set after the value set is assigned
to a chart of accounts structure instance. Otherwise you are not able to define the mandatory value attributes,
such as summary flag, posting allowed, and account type for natural account segment. The attributes must be
added after the value set is assigned to a chart of accounts structure instance.
Creating a Value Set for Your Chart of Accounts: Example

Create your value sets before creating your chart of accounts. A value set can be shared by different charts of accounts or
across different segments of the same chart of accounts.
Scenario
You are creating a company value set to be used in your chart of accounts for your enterprise, InFusion America, Inc. Follow
these steps:
1. Navigator > Setup and Maintenance > Manage Chart of Accounts Value Sets >Go to Task.
2. Click the Create icon on the toolbar of the Search Results table. The Create Value Set page opens.
3. Enter a unique Value Set Code, InFusion America Company, and an optional Description, Company values for
InFusion America Inc.
4. Select General Ledger from the list in the Module field.
5. Select Independent as Validation Type.
Note
You must use Independent validation only for the Accounting Key Flexfield 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 are not supported.
6. Select Character as the Validation Data Type.
7. Save and Close.
Configuring Chart of Account Segment for Business

Intelligence: Explained
To map the Oracle Fusion General Ledger Accounting Flexfield in Oracle Fusion Transaction Business Intelligence (BI)
Repository file (RPD) for Oracle Fusion Financials, populate values in the Manage Key Flexfields user interface. These values
enable the Chart of Accounts segments for Oracle Fusion Transactional BI and provide the mapping with BI Object names
that are used as dimension for each of the Chart of Accounts segments.
132
Check each of the Chart of Accounts segments' BI enabled check box on all segments that you intend to map in the RPD
by performing the following steps:
1. From your implementation project or the Setup and Maintenance page, query for Manage Key Flexfields > Go
to Task.
2. Enter GL# in the Key Flexfield Code.
3. Search.
4. Click on Manage Structure Instances.
5. Search.
6. Click on the desired chart of accounts and Edit icon.
7. Click on the desired segment and the Edit icon.
8. Check the BI enabled check box.
9. 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. Save and Close > Done .
Populate the BI Object Name for each of the Segment Labels. This name is the logical table name in the RPD which would
be used as the dimension for the corresponding segment. Perform the following steps:
1. From your implementation project or the Setup and Maintenance page, query for Manage Key Flexfields > Go
to Task.
2. Enter GL# in the Key Flexfield Code.
3. Query for GL# as Key Flexfield Code in Manage Key Flexfields page.
4. Search.
5. Actions menu and click on Manage Segment Labels.
6. Populate the BI Object Name for all the segment labels that are need to be mapped in the RPD.
Segment Label Code BI Object Name
FA_COST_CTR Dim - Cost Center

GL_BALANCING Dim - Balancing Segment

GL_ACCOUNT Dim - Natural Account Segment

7. Save.
133
Note
For all the non qualified segment labels, the BI Object Name should be populated with one of the following:
• Dim - GL Segment1
Deploy the flexfield using the Deploy Flexfield button from Manage Key Flexfields page.
Important
For more information on extending both key and descriptive flexfields into Oracle Fusion Transactional BI, refer to
Oracle Fusion Transactional Business Intelligence Administrator's Guide.

Manage Accounting Calendars
Defining Accounting Calendars: Critical Choices

Define an accounting calendar to create your accounting year and the periods it contains. Specify common calendar options
that the application uses to automatically generate a calendar with its periods. Specifying all the options makes defining a
correct calendar easier and more intuitive with fewer errors. The choices you make when specifying the following options are
critical, because it is difficult 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
• Period Name Format
134
Note
In Oracle Fusion, the common calendar types, monthly, weekly, 4-4-5, 4-5-4, 5-4-4, 4-week, quarterly, and
yearly, are automatically generated. This functionality makes it easier to create and maintain accounting calendars.
By using the period frequency option, you no longer have to go through the tedious task of defining each period
manually.
Budgetary Control Only Check Box

Select the check box for Budgetary control only to use the calendar for budgetary control only. Budgetary Control refers to
the group of system options and the validation process of determining which transactions are subject to validation against
budgets and budget consumption to prevent overspending.
Start Date
If you plan to run translation, specify a calendar start date that is a full year before the start date of the year of the first
translation period for your ledger. Translation cannot be run in the first period of a calendar. Consider how many years of
history you are going to load from your previous system and back up the start date for those years plus one more. You
cannot add previous years once the first calendar period has been opened.
Period Frequency
Use 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 define a weekly calendar. For manually entered calendars,
when you click the Add Year button, 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 defined and validated, use the Add Year button to add the next year quickly. Accept or change the new
rows as required. For example, with the Other frequency type calendar, dates may differ from what the application generates.
Note
In Oracle Fusion applications a calendar can only have 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.
Adjusting Period Frequency

Use the adjusting period frequency to control when the application creates adjusting periods. For example, some of the
frequencies you select add one adjusting period at year end, two at year end, or one at the end of each quarter. The default
is None which adds no adjusting periods. If you select the frequency of Other, the Number of Adjusting Periods field is
displayed. Enter the number of desired adjusting periods and then, manually define them.
Period Name Format Region

In the Period Name Format region enter the following fields:
• User-Defined Prefix: An optional feature that allows you to enter your own prefix. For example, define a weekly
calendar and then enter a prefix of Week, - as the separator, and the period name format of Period numberYY fiscal
year. The application creates the names of Week1-11, Week2-11, through Week52-11.
• Format: A predefined list of values filtered on the selected separator and only displays the options that match the
selected separator.
• Year: The year displayed in the period names is based on the selected period name format and the dates the period
covers or if the period crosses years, on the year of the start date of the period.
◦ For example, April 10, 2010 to May 9, 2010 has the period name of Apr-10 and December 10, 2010 to
January 9, 2011 has the name of Dec-10.
135
◦ If period frequency is Other, then the period format region is hidden. The application generates a temporary
period name for calendars with period frequency of Other, using a fixed format of Period numberYY. You can
override this format with your own customized period names.
Note
For an accounting calendar that is associated with a ledger, changing period names or adding a year updates the
accounting period dimension in the balances cubes.
Calendar Validation: How It Works with the Accounting

Calendar
Calendar validation is automatic and prevents serious problems when you begin using the calendar. Once you set a calendar
period status to open or future enterable, you cannot edit the period.
Settings That Affect Calendar Validation

The calendar validation runs automatically when you save the calendar.
How the Calendar Is Validated

The following table lists the validation checks performed when the accounting calendar is saved.
Validation Performed Example of Data
Unique period number 2 assigned for two periods

Unique period name Jan-11 entered twice

Period number beyond the maximum number of periods 13 for a 12 period calendar with no adjusting periods
per year

Entered period name contains spaces Jan 11

Single or double quotes in the period name Jan '11

Nonadjusting periods with overlapping dates 01-Jan-2011 to 31-Jan-2011 and 30-Jan-2011 to 28-
Feb-2011

Period date gaps 01-Jan-2011 to 28-Jan-2011 and 31-Jan-2011 to 28-

Feb-2011

Missing period numbers Periods 1 through 6 defined for a twelve month calendar

136
Validation Performed Example of Data
Period number gaps 1, 3, 5

Period numbers not in sequential order by date Period 1 covers 01-Jan-2011 to 31-Jan-2011 and
period 2 covers 01-Mar-2011 to 31-Mar-2011, and
period 3 covers 01-Feb-2011 to 28-Feb-2011.

Quarter number gaps 1, 3, 4

Quarters not in sequential order by period 1, 3, 2, 4

Period start or end dates more than one year before or July 1, 2010 in a 2012 calendar
after the fiscal year

FAQs for Manage Accounting Calendars

How can I identify errors in my accounting calendar?
Oracle Fusion General Ledger identifies erroneous entries online as you enter a new calendar or change data on an existing
calendar. The application also automatically validates the data when you save the calendar.
What's the difference between calendar and fiscal period naming?

The period naming format determines the year that is appended to the prefix for each period in the calendar. For the example,
your accounting year has a set of twelve accounting period with a start date of September 1, 2011 and the end date is
August 31, 2012, with each period's date range following the natural calendar month date range.
Calendar period naming format: Select the calendar period format to append the period's start date's year to the prefix.
For the period covering September 1, 2011 to December 31, 2011, then 2011 or just 11, depending on the period format
selected, is appended to each period's name. For the remaining periods covering January 1, 2012 to August 31, 2012, then
2012 or 12, is appended to each period's name.
Fiscal period naming format: Select the fiscal period format to always append the period's year assignment to the prefix. If
the accounting periods in the set of twelve are all assigned the year of 2012, then 2012 or just 12, depending on the period
format selected, is appended to the period name of all 12 periods.
When do I update an existing calendar?

Update an existing calendar before the new periods are needed as future periods, based on the future period setting in your
accounting configuration. If a complete year has been defined and validated, use the Add Year button to add the next year
quickly. Accept or change the new rows as required. For example, with the Other frequency type calendar, dates may differ
from what the application generates.
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 first 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 modification.
137
Make your changes to the period frequency, adjusting period frequency, and period name format, including the prefix
and separator, as needed. Changes can not conflict with the existing upgraded calendar definition. Update the calendar
name and description in the calendar header, as needed, for all calendars. Period details for a new year will be generated
automatically based on the latest calendar options. You can also manually update the calendar. The modified calendar
options affect future years only.
Define Accounting Configurations of Enterprise

Structures: Manage Primary Ledgers
Accounting Configuration Offerings: Overview

The Setup and Maintenance work area in the Oracle Fusion Applications is used to manage the configuration of legal
entities, ledgers, and reporting currencies. To create a legal entity or ledger, first create an implementation project. This
implementation project can be populated by either adding a financials related offering or one or more task lists.
Note
Setup tasks that are not related to the ledger or legal entity setup tasks are opened from either an implementation
project or directly from the Setup and Maintenance work area.
The financial applications have two predefined implementations:
• The Oracle Fusion Accounting Hub offering: Used to add the Oracle Fusion General Ledger and Oracle Fusion
Subledger Accounting application features to an existing enterprise resource planning (ERP) system to enhance the
reporting and analysis.
• The Oracle Fusion Financials offering includes the Oracle Fusion General Ledger and Oracle Fusion Subledger
Accounting application features and one or more subledger financial applications.
When adding an offering to an implementation project, customize the tasks displayed by adding additional tasks.
Related Topics
• What's an implementation project?
• What's a functional area?
• What's an offering?
Ledgers and Subledgers: Explained

Oracle Fusion Applications reflect the traditional segregation between the general ledger and associated subledgers. Detailed
transactional information is captured in the subledgers and periodically imported and posted in summary or detail to the
ledger.
A ledger determines the currency, chart of accounts, accounting calendar, ledger processing options, and accounting
method for its associated subledgers. Each accounting setup requires a primary ledger and optionally, one or more
secondary ledgers and reporting currencies. Reporting currencies are associated with either a primary of secondary ledger.
138
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 financial results in Oracle Fusion General
Ledger in a single ledger. Use Oracle Fusion Financial Reporting functionality to produce individual entity reports by 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 financial 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 different 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 different accounting calendars. For example, although companies may share fiscal
year calendars, your retail operations require a weekly calendar, and a monthly calendar is required for your
corporate headquarters.
• You have companies that require different functional currencies. Consider the business activities and reporting
requirements of each company. If you must present financial 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 flexible application that defines the accounting rules,
generates detailed journal entries for these subledger transactions, and posts these entries to the general ledger with flexible
summarization options to provide a clear audit trail.
Ledgers: Points to Consider

Companies account for themselves in primary ledgers, and, if necessary, secondary ledgers and reporting currencies.
Your transactions from your subledgers are posted to your primary ledgers and possibly, secondary ledgers or reporting
currencies. Local and corporate compliance can be achieved through an optional secondary ledger, providing an alternate
accounting method, or in some cases, a different chart of accounts. Your subsidiary's primary and secondary ledgers can
both be maintained in your local currency, and you can convert your local currency to your parent's ledger currency to report
your consolidated financial results using reporting currencies or translation.
Primary Ledgers
A primary ledger is the main record-keeping ledger. Like any other ledger, a primary ledger records transactional balances
by using a chart of accounts with a consistent calendar and currency, and accounting rules implemented in an accounting
method. The primary ledger 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 financial, 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 specific
primary ledgers to report to your parent company from your foreign subsidiaries. Other considerations, such as corporate
year end, ownership percentages, and local government regulations and taxation, also affect the number of primary ledgers
required.
139
Secondary Ledgers
A secondary ledger is an optional ledger linked to a primary ledger for the purpose of tracking alternative accounting. A
secondary ledger can differ from its primary ledger by using a different accounting method, chart of accounts, accounting
calendar, currency, or processing options. All or some of the journal entries processed in the primary ledger are transferred
to the secondary ledger, based on your configuration options. The transfers are completed based on the conversion level
selected. There are four conversion levels:
• Balance: Only Oracle Fusion General Ledger balances are transferred to the secondary ledger.
• Journal: General Ledger journal posting process transfers the journal entries to the secondary ledger.
• Subledger: Oracle Fusion Subledger Accounting creates subledger journals to subledger level secondary ledgers as
well as reporting currencies.
• Adjustments Only: Incomplete accounting representation that only holds adjustments. The adjustments can be
manual or detailed adjustments from Subledger Accounting. This type of ledger must share the same chart of
accounts, accounting calendar, and period type combination, and currency as the associated primary ledger.
Note
A full accounting representation of your primary ledger is maintained in any subledger level secondary ledger.
Secondary ledgers provide functional benefits, but produce large volumes of additional journal entry and balance data,
resulting in additional performance and memory costs. When adding a secondary ledger, consider your needs for secondary
ledgers or reporting currencies, and select the least costly data conversion level that meets your requirements. For secondary
ledgers, the least costly level is the adjustment data conversion level because it produces the smallest amount of additional
data. The balance data conversion level is also relatively inexpensive, depending upon how often the balances are transferred
from the primary to the secondary ledger. The journal and subledger data conversion levels are much more expensive,
requiring duplication of most general ledger and subledger journal entries, as well as general ledger balances.
For example, you maintain a secondary ledger for your International Financial Reporting Standards (IFRS) accounting
requirements, while your primary ledger uses US Generally Accepted Accounting Principles (GAAP). You decided to select
the subledger level for your IFRS secondary ledger. However, since most of the accounting is identical between US GAAP
and IFRS, a better solution is to use the adjustment only level for your secondary ledger. The subledger level secondary
ledger requires duplication of most subledger journal entries, general ledger journal entries, and general ledger balances.
With the adjustment only level, your secondary ledger contains only the adjustment journal entries and balances necessary
to convert your US GAAP accounting to the IFRS accounting, which uses a fraction of the resources that are required by full
subledger level secondary ledger.
Following are scenarios that may require different combinations of primary and secondary ledgers:
• The primary and secondary ledgers use different charts of accounts to meet varying accounting standards or
methods. A chart of accounts mapping is required to instruct the application how to propagate balances from the
source (primary) chart of accounts to the target (secondary) chart of accounts.
• The primary and secondary ledgers use different accounting calendars to comply with separate industry and
corporate standards.
Note
Use the same currency for primary and secondary ledgers to avoid difficult reconciliations, if you have the
resources to support the extra posting time and data storage. Use reporting currencies or translations to generate
the different currency views needed to comply with internal reporting needs and consolidations.
Reporting Currencies
Reporting currencies maintain and report accounting transactions in additional currencies. Each primary and secondary
ledger is defined with a ledger currency that is used to record your business transactions and accounting data for that ledger.
140
It is advisable to 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 need to maintain and report accounting records in different currencies, you do this by defining one or more reporting
currencies for the ledger. There are three conversion levels for reporting currencies:
• Balance: Only General Ledger balances are converted into the reporting currency using translation.
• Journal: General Ledger journal entries are converted to the reporting currency during posting.
• Subledger: Subledger Accounting creates subledger reporting currency journals along with primary ledger journals.
Note
A full accounting representation of your primary ledger is maintained in any subledger level reporting currency.
Secondary ledgers cannot use subledger level reporting currencies.
Of the three data conversion levels available, the balance data conversion level is typically the least expensive,
requiring duplication of only the balance level information. The journal and subledger data conversion levels are
more expensive, requiring duplication of most general ledger and subledger journal entries, as well as general
ledger balances.
Do not use journal or subledger level reporting currencies if your organization has only an infrequent need to translate your
financial statements to your parent company's currency for consolidation purposes. 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 need to 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 is part of the European Economic and Monetary Union (EMU), and you choose to
account and report in both the European Union currency and your National Currency Unit (NCU).
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
• Reporting Currency Balances: How They Are Calculated
Financial Ledgers: How They Fit Together

Oracle Fusion Applications is an integrated suite of business applications that connects and automates the entire flow of the
business process across both front and back office operations and addresses the needs of a global enterprise. The process
of designing the enterprise structure, including the accounting configuration, is the starting point for an implementation.
This process often includes determining financial, legal, and management reporting requirements, setting up primary and
secondary ledgers, making currency choices, and examining consolidation considerations.
This figure shows the enterprise structure components and their relationships to each other. Primary ledgers are connected
to reporting currencies and secondary ledgers to provide complete reporting options. Legal entities are assigned to ledgers,
141
both primary and secondary, and balancing segments are assigned to legal entities. Business units must be connected to
both a primary ledger and a default legal entity. Business units can record transactions across legal entities.
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 financial, 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 different 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 simplifies reporting
because consolidation is not required. Other consideration such as corporate year end, ownership considerations, and local
government regulations, also affect the number of primary ledgers required.
Secondary Ledgers
A secondary ledger is an optional ledger linked to a primary ledger. A secondary ledger can differ from its related primary
ledger in chart of accounts, accounting calendar, currency, accounting method, or ledger processing options. Reporting
142
requirements, for example, that require a different accounting representation to comply with international or country-specific
regulations, create the need for a secondary ledger.
Below are scenarios and required action for different components in primary and secondary ledgers:
• If the primary and secondary ledgers use different charts of accounts, the chart of accounts mapping is required to
instruct the system how to propagate journals from the source chart of accounts to the target chart of accounts.
• If the primary and secondary ledgers use different accounting calendars, the accounting date and the general ledger
date mapping table will be used to determine the corresponding non-adjusting period in the secondary ledger. The
date mapping table also provides the correlation between dates and non-adjusting periods for each accounting
calendar.
• If the primary ledger and secondary ledger use different ledger currencies, currency conversion rules are required to
instruct the system on how to convert the transactions, journals, or balances from the source representation to the
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 financial, legal, and management reporting. If your reporting currency is not
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
system 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 financial, 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 financial statements and reports to company regulators, taxation authorities, and other
stakeholders according to rules specified in the relevant legislation and applicable accounting standards. During setup, legal
entities are assigned to the accounting configuration, 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 specific
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 has not 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
allows you to quickly identify these errors and view any unassigned values.
Business Units
hierarchy. When a business function produces financial 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 can process transactions for
many legal entities. Normally, it will have a manager, strategic objectives, a level of autonomy, and responsibility for its profit
and loss. You define business units as separate task generally done after the accounting setups steps.
The business unit model:

143
• Enables sharing of sets of reference data across applications

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 differently from your domestic business, use business
units to secure members of the export business from seeing the transactions of the domestic business.
Creating Primary Ledgers: Example

Create a primary ledger as your main record-keeping ledger. Like any other ledger, a primary ledger records transactional
balances by using a chart of accounts with a calendar, currency, and accounting rules implemented in an accounting
method. The primary ledger is closely associated with the subledger transactions and provides context and accounting for
them.
Scenario
Your company, InFusion Corporation is implementing Oracle Fusion Applications. You have been assigned the task of
creating a primary ledger for your InFusion America entity.
1. Navigator > Define Accounting Configurations > Manage Primary Ledgers > Go to Task.
2. Click the Create icon.
3. Enter the following values:
Field Value
Name InFusion America

Description InFusion America primary ledger for recording

transactions.

Chart of Accounts InFusion America Chart of Accounts

Accounting Calendar Standard Monthly

Currency USD

Accounting Method Standard Accrual

4. Click Save and Edit Task List to navigate back to the accounting configuration task list.
Note
You cannot change the chart of accounts, accounting calendar, or currency for your ledger after you
save your ledger.
144
Define Accounting Configurations of Enterprise

Structures: Specify Ledger Options
Specifying Ledger Options: Worked Example

This example demonstrates specifying the ledger options for your primary ledger. 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.
After completing your InFusion America Primary Ledger, select Specify Ledger Options under the Define Accounting
Configuration task list on the Functional Setup Manager page.
Note
Both primary and secondary ledgers are created in the same way and use the same user interface to enable their
specific ledger options.
Reviewing General Region Options

1. Accept the Name and Description defaults for the ledger selected.
2. Review the Currency and Chart of Accounts for the specified ledger, which are automatically populated.
Setting Accounting Calendar Region Options

1. Review the Accounting Calendar that defaults from your ledger.
2. Select Jan-2011 as the First Open Period for your ledger.
Important: Select a period after the first defined period in the ledger calendar to enable running translation. You
cannot run translation in the first defined period of a ledger calendar. In this example, your calendar began with
Jan-2010.
3. Enter 3 for the Number of Future Enterable Periods.
Any value between 0 and 999 periods can be specified to permit entering journals but not posting them in future
periods. Minimize the number of open and future periods to prevent entry in the wrong period.
Selecting the Subledger Accounting Region Options

1. Accept the default Accounting Method from your ledger.
2. Select US American English as your Journal Language.
Completing the Period Close Region Options

1. Enter your Retained Earnings Account: 101-00-31330000-0000-000-0000-0000.
This account is required for the General Ledger to perform the movement of revenue and expense account
balances to this account at the end of the accounting year.
145
2. Enter your Cumulative Translation Adjustment Account: 101-00-31350000-0000-000-0000-0000.

Note: The Cumulative Translation Adjustment (CTA) account is required for ledgers running translation.
3. Do not enter a Default Period End Rate Type or Default Period Average Rate Type.
The values entered here are used as the default for balance level reporting currency processing. InFusion America
Primary Ledger is using the subledger level reporting currency processing.
Specifying the Journal Processing Region Options

1. Specify the Balance options as outlined in the following table.
Option Setting
Enable Suspense General Ledger

Default Expense Account 101-00-98199999-0000-000-0000-0000

Rounding Account 101-10-98189999-0000-000-0000-0000

Entered Currency Balancing Account 101-10-98179999-0000-000-0000-0000

Balancing Threshold Percent 10

2. Click all the following Entry options listed in the table.
Option Description
Enable journal approval Click to enable journal approval functionality.

Approval rules must be created in the Oracle Fusion
Approvals Management (AMX).

Notify when prior period journal Notify the user when a prior period date is selected
on a journal entry.

Allow mixed and statistical journals Enter both monetary and statistical amounts on the
same line in a journal entry.

Validate reference date Requires a reference date in an open or future

enterable period.

3. Click the Separate journals by accounting date during journal import for the Import option to create individual
journal entries for each accounting date.
146
4. For the Reversal options, select InFusion America Accrual Set from the list of values in the Journal Reversal
Criteria Set field and click the Launch AutoReverse after open period to reverse accrual journal entries
automatically when a new period is opened.
5. Click the Enable intercompany accounting for the Intercompany option to enable automatic balancing by the
application for primary, second, and third balancing segments (if implemented) on intercompany journal entries and
transactions.
Note: To complete the intercompany accounting functionality, you must define intercompany rules.
Related Topics
• What happens if a cross currency journal is unbalanced?
• What happens if I change the retained earnings account?
• What happens if I change the cumulative adjustment account?
Assigning Legal Entities and Balancing Segments: Examples

Optionally, assign legal entities and balancing segments to your accounting configuration.
Assign Legal Entities

Assign one or more legal entities to your configuration by following these steps:
1. Navigator > Setup and Maintenance work area > Define Ledgers > Define Accounting Configurations >
Assign Legal Entities task.
2. If scope is:
◦ Not set: Select Scope link > Assign Legal Entities radio button > In the Primary Ledger drop down Select
and Add > Apply and Go To Task > Select your ledger > Save and Close.
◦ Set, click Go to Task
3. Click the Select and Add icon.
4. Enter your legal entity.
5. Apply > Done.
6. Save and Close.
Assign Balancing Segments to Legal Entities

Assign balancing segment values to your legal entities by following these steps:
Assign Balancing Segment Values to Legal Entities task.
2. If scope is:
◦ Not set: Select Scope link > Assign Balancing Segment Values to Legal Entities radio button > In the
Primary Ledger drop down Select and Add > Apply and Go To Task > Select your ledger > Save and
Close.
147
◦ Set, click Go to Task.

3. Click the Create icon.
4. Select the balancing segment value. Optionally, add a Start Date.
5. Save and Close to close the create page.
6. Save and Close.
Assign Balancing Segments to Ledgers

Assign balancing segment values directly to your ledger by following these steps:
Assign Balancing Segment Value to Ledger task.
2. If scope is:
◦ Not set: Select Scope link > Assign Balancing Segment Value to Ledger radio button > In the Primary
Ledger drop down Select and Add > Apply and Go To Task > Select your ledger > Save and Close.
◦ Set, click Go to Task.

3. Select the balancing segment value.
4. Optionally enter a start date.
5. Save and Close.
Note
The balancing segment values that are assigned to the ledger represent nonlegal entity transactions, such
as adjustments. If you use legal entities, you must assign balancing segment values to all legal entities before
assigning values to the ledger. The only available balancing segment values that can be assigned to ledgers are
those not assigned to legal entities.
Define Business Units
Define Business Units: Manage Business Units

148
business units.


Related Topics
• Reference Data Sets and Sharing Methods: Explained
Define Business Units: Assign Business Unit Business

Function
Business Functions: Explained
A business unit can perform many business functions in Oracle Fusion Applications. Prior to Oracle Fusion Applications,
operating units in Oracle E-Business Suite were assumed to perform all business functions, while in Oracle PeopleSoft, each
business unit had one specific business function. Oracle Fusion Applications blends these two models and allows defining
business units with one or many business functions.
149
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
• Expense management
• Incentive compensation
• Marketing
• Materials management
• Inventory management
• Order fulfillment 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 define a hierarchy of divisions,
business units, and departments as a tree over HCM organization units to represent your enterprise structure.
Note
This hierarchy definition is not 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 profit and loss statement.
In such cases, any segment that allows the identification of associated revenue and costs can be used as a profit center
identification. The segment can be qualified as a cost center segment.
However, there are cases where a business unit is performing only general and administrative functions, in which case your
manager's financial goals are limited to cost containment or recovering of service costs. For example, if a shared service
center at the corporate office provides services for more commercially-oriented business units, it does not show a profit 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 financial 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.
150
The following business functions generate financial transactions and will require a primary ledger and a default legal entity:
• Billing and revenue management

• Collections management
• Customer payments
• Expense management
• Materials management
• Payables invoicing
• Project accounting
• Receiving
• Requisitioning
Business Unit Hierarchy: Example

For example, your InFusion America Company provides:
• Air quality monitoring systems through your division InFusion Air Systems
• Customer financing through your division InFusion Financial Services
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
151
Oracle Fusion applications facilitates independent balance sheet rollups for legal and management reporting by offering
up to three balancing segments. Hierarchies created using the management segment can provide the divisional results.
For example, it is possible to define management segment values to correspond to business units, and arrange them in a
hierarchy where the higher nodes correspond to divisions and subdivisions, as in the Infusion US Division example above.
Define Workforce Structures: Manage Divisions
Division: Explained
Managing multiple businesses requires that you segregate them by their strategic objectives and measure their results.
Responsibility to reach objectives can be delegated along the management structure. Although related to your legal structure,
the business organizational hierarchies do not reflect directly the legal structure of the enterprise. The management entities
and structure can include:
• Divisions and subdivisions
• Lines of business
• Other strategic business units
• Their own revenue and cost centers.
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 differently to
deliver products and services or address different markets. A division can operate in one or more countries, and can be
comprised of many companies or parts of different companies that are represented by business units.
A division is a profit center or grouping of profit and cost centers, where the division manager is responsible for attaining
business goals including profit goals. 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 top corporate executive.
By definition a division can be represented in the chart of accounts. Companies may choose to represent product lines,
brands, or geographies as their divisions: their choice represents the primary organizing principle of the enterprise. This may
coincide with the management segment used in segment reporting.
Oracle Fusion Applications supports a qualified management segment and recommends that you use this segment to
represent your hierarchy of business units and divisions. If managers of divisions have return on investment goals, make the
management segment a balancing segment. Oracle Fusion applications allows up to three balancing segments. The values of
the management segment can be comprised of business units that roll up in a hierarchy to report by division.
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.
Use of Divisions in Oracle Fusion Human Capital Management (HCM)

Divisions are used in HCM to define the management organization hierarchy, using the generic organization hierarchy. This
hierarchy can be used to create organization based security profiles.
152
Adding a New Division After Acquiring a Company: Example

This example describes how you can restructure your enterprise after acquiring a new division.
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.
Details of the Acquired Company

The acquired company is a Financial Services business based in Germany. The Financial Services business differs significantly
from the high tech business. Therefore, you want to keep the Financial Services company as a separate business with all the
costs and reporting managed by the Financial Services division.
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.
Decision to Consider In This Example
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 specific to
financial services in a new business unit.

153
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.

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.

How many legal entities? Define a legal entity for each registered company or
some other entity recognized by law. Using the legal
entity, you can:
• Record assets
• Record liabilities
• Record income
• Pay transaction taxes
• Perform intercompany trading
In this case, you only need one legal entity.

You must define the legal entity as a legal employer and
payroll statutory unit. As the new division operates only
from Germany, you can configure 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.

Resulting InFusion Enterprise Structure

Based on the analysis, you must create the following:
• One new division

• One new location
• Three new departments
154
• Three new cost centers

• One new legal entity
• One new legislative data group
The following figure illustrates the structure of InFusion Corporation after adding the new division and the other organizations.
Define Workforce Structures: Manage Departments
Cost Centers and Departments: Explained

The two important components to be considered in designing your enterprise structure are cost centers and departments.
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.
155
Cost Centers
A cost center also represents the destination or function of an expense as opposed to 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 attached 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 different ledgers. However, this approach requires
defining 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 defined. 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 do not 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
Note
The manager of a sales department may also be responsible for meeting the revenue targets.
The financial performance of departments is generally tracked through one or more cost centers. In Oracle Fusion
Applications, departments are defined and classified 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 configuration may be unrelated, identical, or consist of many cost centers tracking the costs of one department.
Department Classifications: Points to Consider

A department can be classified 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 seeded tree
structures for department and other organizational hierarchies that can include organizations with any classification.
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
156
Subledger Accounting to derive accounts for posting Oracle Fusion Projects accounting entries to Oracle Fusion General
Ledger.
Sales and Marketing Organization

In Oracle Sales Cloud, you can define sales and marketing organizations. Sales organization hierarchies are used to report
and forecast sales results. Sales people are defined as resources assigned to these organizations.
In some enterprises, the HCM departments and hierarchies correspond to sales organizations and hierarchies. It is important
to examine the decision on how to model sales hierarchies in relationship to department hierarchies when implementing
customer relationship management to eliminate any possible redundancy in the definition of the organizations.
The following figure 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 classifications of
Department are defined, the Marketing Department and Sales Department. These two departments can be also identified as
a Resource Organizations, which will allow assigning resources, such as sales people, and other Oracle Sales Cloud specific
information to them. Each department is represented in the chart of accounts by more than one cost center, allowing for
granular as well as hierarchical reporting.
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 financial reports.
A cost organization can represent a costing department. Consider this relationship when determining the setup of
departments in HCM. There are no system dependencies requiring these two entities, cost organization and costing
department, be set up in the same way.
157
Define Workforce Structures: Manage Department

and Organization Trees
Trees: Overview
Use the tree management feature in Oracle Fusion applications to organize data into hierarchies. A hierarchy contains
organized data and enables the creation of groups and rollups of information that exist within an organization. Trees are
hierarchical structures that enable several data management functions such as better access control, application of business
rules at various levels of hierarchies, improved query performance, and so on.
For example, XYZ Corporation has two departments: Marketing and Finance. The Finance department has two functional
divisions: Receivables and Payables. Defining a tree for the XYZ Corporation establishes a hierarchy between the organization
and its departments, and between the departments and their respective functional divisions. Such a hierarchical modeling of
organizational data could be used for executing several data management functions within that organization.
You can create one or more versions of trees, and they can be labeled for better accessibility and information retrieval. You
can create trees for multiple data sources, which allow the trees to be shared across Oracle Fusion applications.
Tree Structures
A tree structure is a representation of the data hierarchy, and guides the creation of a tree. A tree is an instance of the
hierarchy as defined in the tree structure. Tree structures enable you to enforce business rules to which the data must
adhere.
The root node is the topmost node of a tree. Child nodes report to the root node. Child nodes at the same level, which report
to a common parent node, are called siblings. Leaves are details branching off from a node but not extending further down
the tree hierarchy.
Tree Versions
A tree is created having only one version. However, users can create more than one tree version depending on the need, and
they can make changes to those versions. Depending on varying requirements, users can create one or more tree versions
and publish all of them or some of them by making the versions active at the same time. Similar to any other version control
system, versions of trees are maintained to keep track of all the changes that a tree undergoes in its life cycle.
Tree Labels
Tree labels are short names associated with trees and tree structures and point directly to the data source. Tree labels are
automatically assigned to the tree nodes. You can store labels in any table and register the label data source with the tree
structure.
Related Topics
• Tree Labels: Explained
Tree Structures: Explained

A tree structure defines the hierarchy for creating trees and prescribes rules based on which trees are created, versioned, and
accessed. You can associate multiple data sources with a tree structure. A tree is an instance of this hierarchy. Every tree
structure can contain one or more trees.
158
You can create tree structures specific to an application but you can share tree structures across applications. If you apply
version control to the tree structure, it is carried over to the trees that are based on the tree structure. Each tree version
contains at least one root node. Occasionally, a tree version may have more than one root node.
An administrator controls the access to tree structures through a set of rules that are periodically audited for validity.
Tree Structure Definition: Points to Consider

Defining a tree structure involves specifying several important pieces of information on the Create Tree Structure: Specify
Definition page.
Tree Node Selection

The Tree Node table displays data in nodes that exist in the data hierarchy. You must select the correct and most
appropriate tree node table to be able to define the tree structure, based on the tree hierarchy you want to establish. This
selection also affects the level of security that is set on a tree node and its child entities.
Tree Sharing Mode

The following options are used to determine the mode of sharing a tree structure across the applications.
• Open: Indicates that the tree is associated with all reference data sets.
• Set ID: Indicates that the tree will be associated with a specific reference data set.
Creation Mode
Indicates the source where the tree structure is being defined. For predefined tree structures select Oracle and for custom
structures, select Customer.
Customization
You can customize the predefined tree structures as well as the ones that you created. However, customizing the predefined
tree structures involves certain level of access restrictions, and will be limited to specific tree nodes and downwards in
hierarchy.
Multiple Tree Versions

One or more trees and tree versions can be based on a tree structure. A tree structure can have one or more trees and tree
versions based on it. Usually, only one active version is permitted at any given point of time. However, depending on the
requirement, you can allow two or more tree versions to be in the active state for the same date range. This flexibility allows
you to choose the tree version that you want to implement.
Managing Tree Structures: Points to Consider

You can create, edit, and delete tree structures depending upon the requirement. You can also audit and change the status a
tree structure.
Creating and Editing Tree Structures

You can create trees on the basis of a tree structure. When you edit an active tree structure, the status of the tree structure
and all associated trees and their versions change to draft. To reuse a tree structure, you can create a copy of it without
copying the associated trees and tree versions. If you delete a tree structure, all the associated trees and tree versions are
automatically deleted.
Note
For specific information on working with the predefined tree structures that exist in an Oracle Fusion application,
refer to the specific product documentation.
159
Setting Status
If 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 different statuses of a tree structure.
Status Meaning
Draft Yet to be published or is in a modified state.

Active In use and based on which one or more trees or tree

versions are created.

Inactive Not in use.

Tree Structure Audit Results: Explained

Use the tree structure audit results to verify the tree structure's correctness and data integrity. The audit results include the
following details:
• The name of the validator, which is a specific validation check
• The result of the validation, including a detailed message
• Corrective actions to take if there are any validation errors
Running an Audit
Setting the status of a tree structure to active automatically triggers an audit of that tree structure. You can also manually
trigger an audit on the manage Tree Structures page, using Actions - Audit . The Tree Structure Audit Result table shows a
list of validations that ran against the selected tree structure.
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 is Possible Cause for Suggested Corrective

checked) Validation Failure Action
Restrict By Set ID On the Manage Tree Even when the check If reference data set
Structures: Specify Data box is selected, one or restriction is required
Sources page, if the more of its data source for this tree structure,
Set ID check box is view objects does not include a reference data
selected to enable the contain a reference data set attribute on all data
Restrict Tree Node set attribute. sources. Otherwise,
List of Values Based deselect the check box.
on option for a tree
structure, each of its
160

data source view objects
must have a reference
data set attribute. This
validation does not take
place when the check
box is not selected.
Row Flattened Table On the Manage Tree • The specified table Correct the row flattened
Name Structures: Specify does not exist in table definition.
Performance Options the database.
page, a valid row
flattened table must be • The specified
specified for the tree table does not
structure. It can either contain the same
be the standard row columns as the
flattened table FND_ FND_TREE_NODE_RF
TREE_NODE_RF or a table.
custom table.

Available Label Data On the Manage Tree • Any of the specified • Correct the
Sources Structures: Specify label data source specified label data
Data Sources page, if view objects do not source view object.
a labeling scheme is exist.
specified for the tree • Correct the
structure by selecting • Any of the specified primary keys of the
a list item from the label data source specified label data
Labeling Scheme view objects do not source view object.
list box, the label data have primary keys.
source view object • Either correct the
specified for each • When a label data primary keys in the
data source must be source view object label data source
accessible, and the is initially defined, view object to
primary keys must be the database match the primary
valid. This restriction registers the keys that were
does not apply when you primary keys for earlier registered in
select None from the the view object. If FND_TS_DATA_SOURCE,
Labeling Scheme list the view object is or correct the
box. later modified such primary keys
that its primary registered in that
keys no longer table to match the
match the primary new view object
keys that were definition.
registered earlier,
this validation fails.
Available Data Sources Each data source view • Any of the specified • Correct the
object specified for the data source view specified data
tree structure must be objects do not source view object.
accessible, and all its exist.
primary key attributes • Correct the
must be valid. duplicate column

161

• When a data in the registered
source view object primary keys.
is initially defined,
the database • Correct the
automatically primary keys of
registers the the specified data
primary keys for source view object.
the view object
if the Use non- • Correct any
defined primary mismatch in data
key columns types.
check box on the
Data Source dialog
If the check box
is selected, the
database registers
the primary keys
specified explicitly
by the user on the
Add Data Source
dialog box. If the
registered primary
keys contain any
duplicates, this
validation fails.
• The Use non

defined primary
key columns
check box is
selected in a data
source, but the list
of specified primary
key columns
does not match
the primary keys
defined in the
corresponding data
source view object.
• Any common
attribute that exists
in both the data
source view object
and the tree node
view object is not
of the same data
162

type in both view
objects.
Column Flattened Table On the Manage Tree • The specified table Correct the column
Name Structures: Specify does not exist in flattened table definition.
Performance Options the database.
page, a valid column
flattened table must be • The specified
specified for the tree table does not
structure. It can either contain the same
be the standard row columns as the
flattened table FND_ FND_TREE_NODE_CF
TREE_NODE_CF or a table.
custom table.

Restrict by Date On the Manage Tree Even when the check If the date restriction
Structures: Specify Data box is selected, one or is required for this tree
Sources page, if the more of its data source structure, include the
Date Range check box view objects does not effective start date
is selected to enable the contain effective start and effective end date
Restrict Tree Node date and effective end attributes on all data
List of Values Based date attributes. sources. Otherwise,
on option for a tree deselect the check box.
structure, each of its
data source view objects
must have effective start
date and effective end
date attributes. This
validation does not take
place when the check
Tree Node Table Name On the Manage Tree • No table is Correct the tree node
Structures: Specify specified in the table definition.
Definition page, a valid Tree Node Table
tree node table must field.
be specified for the
tree structure. It can • The specified table
either be the standard does not exist in
row flattened table the database.
FND_TREE_NODE or a
custom table. • The specified
table does not
contain the same
columns as the
FND_TREE_NODE
table.
163

Allow Node Level If the Allow Node Level The option is set to No Correct the option
Security Security option is set to for the tree structure but setting in the tree
No for the tree structure, one or more associated structure and their data
the same option cannot data sources have that sources.
be set to Yes on any of option set to Yes.
its data sources. This
is a database setting
that is not visible on the
Manage Tree Structures
page.

Specifying Data Sources for Tree Structures: Points to

Consider
The data sources provide the items for establishing hierarchy in a tree structure. In the tree management infrastructure, these
data sources are Oracle Application Development Framework (ADF) business components view objects, which are defined by
application development.
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, you may need to select the following additional
options, to restrict the list of values that appear under 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 different levels.
Restriction of Tree Node Values

You can decide the depth of the tree structure by selecting an appropriate value from the list. Keeping the depth limit open
renders an infinite list of values.
Using the following options, you can restrict the list of values that appear for selection under a specific tree node.
• Date Range: Specifies 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: Specifies whether a selection of nodes should be restricted to the same set as the tree.
Data Source Values and Parameters

Tree data sources have optional data source parameters with defined view criteria and associated bind variables. You can
specify view criteria as a data source parameter when creating a tree structure, and edit the parameters when creating a tree.
Multiple data sources can be associated with a tree structure and can have well-defined relationships among them.
Note
Parameter values customized at the tree level override the default values specified at the tree-structure level.
164
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 filtering for different tree structures. The tree
structure definition supports three data source parameter types.
• Bound Value: Captures any fixed value, which is used as part of the view criteria condition.
• Variable: Captures and binds a dynamic value that is being used by the data source view object. This value is used
by the WHERE condition of the data flow.
• 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 ADF business components are used as data sources. To associate the view object with the tree
structure, you can pick the code from ADF business component view objects and provide the fully qualified name of the view
object, for example, oracle.apps.fnd.applcore.trees.model.view.FndLabelVO.
Specifying Performance Options for a Tree Structure: Points to

Consider
Tree structures are heavily loaded with data. As a tree management guideline, use the following settings to improve
performance of data rendering and retrieval.
• Row Flattening
• Column Flattening
• Column Flattened Entity Objects
• ADF Business Component View Objects
Row Flattening
Row flattening optimizes parent-child information for run-time performance by storing additional rows in a table for instantly
finding all descendants of a parent without initiating a CONNECT BY query. Row flattening eliminates recursive queries, which
allows operations to perform across an entire subtree more efficiently.
To store row flattened data for the specific tree structure, users can either use the central FND_TREE_NODE_RF table or they can
register their own row flattened 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-flattened table contains an additional row
with Corporation directly being the parent of Region (Corporation-Region).
Column Flattening
Column flattening optimizes parent-child information for run-time performance by storing an additional column in a table for all
parents of a child.
To store column flattened data for the specific tree structure, users can either use the central FND_TREE_NODE_CF table or
they can register their own column flattened 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 flattened 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.
Column Flattened Entity Objects

In the absence of a column-flattened table, if you need to generate the business component view objects for your tree
structure for the flattened table, use the tree management infrastructure to correctly provide the fully qualified name of the
entity object for the column flattened table.
165
ADF Business Component View Objects

View objects from the ADF business components can also be used as data sources, eliminating the need to create new types
of data sources. This field is to store the fully qualified name for the business component view object generated by the tree
management for business intelligence reporting and usage The business component view object is a combination of the tree
data source and column flattened entity. Using this option prevents data redundancy and promotes greater reuse of existing
data, thereby improving the performance of the tree structure.
Manage Trees and Tree Versions

Tree Version Audit Results: Explained
Use the tree version audit results to verify the tree version's correctness and data integrity. The audit results include the
following details:
• The name of the validator, which is a specific validation check
• The result of the validation, including a detailed message
• Corrective actions to take if there are any validation errors
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 . 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.

Effective Date The effective start and The effective end date is Modify the effective start
end dates of the tree set to a value that is not and end dates such that
version must be valid. greater than the effective the effective start date is
start date. earlier than the effective
end date.

Root Node On the Manage Tree Even if the check box Modify the tree version
Structures: Specify is deselected, the tree such that there is exactly
Data Sources page, version has multiple root one root node.
if the Allow Multiple nodes.
Root Nodes check box
for the Restrict Tree
Node List of Values
Based on option is not
selected, and if the tree
structure is not empty,
the tree version must
contain exactly one root
node. This validation
does not take place if the
check box is selected.
166

Data Source Max Depth For each data source The tree version has data Modify the tree version
in the tree structure, on at a depth greater than such that all nodes are
the Data Source dialog the specified depth limit at a depth that complies
box, if the data source on one or more data with the data source
is depth-limited, the sources. depth limit.
data in the tree version
must adhere to the
specified depth limit.
This validation does not
apply to data sources
for which the Maximum
Depth field is set to
Unlimited.
167

Duplicate Node On the Data Source Even when the check Remove any duplicate
dialog box, if the Allow box is deselected, the nodes from the tree
Duplicates check box tree version contains version.
is not selected, the duplicate nodes.
tree version should not
contain more than one
node with the same
primary key from the
data source. If the
check box is selected,
duplicate nodes are
permitted.
Available Node All nodes in the tree • A node in the tree Remove any orphaned
version should be valid version does not nodes from the tree
and available in the exist in the data version. Update tree
underlying data source. source. Deleting reference nodes so that
data items from they reference existing
the data source tree 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
version that does
not exist.
168

Node Relationship All nodes must adhere The tree structure Modify the tree version
to the relationships has data sources such that the nodes
mandated by the data arranged in a parent- adhere to the same
sources registered in the child relationship, but parent-child relationships
tree structure. the nodes in the tree do as the data sources.
not adhere to the same
parent-child relationship.
For example, if the tree
structure has a Project
data source with a
Task data source as
its child, Task nodes
should always be under
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 On the Manage Tree Even when the check Modify the tree version
Structures: Specify Data box is selected, the such that all nodes in the
sources page, if the tree version has nodes tree have data sources
Set ID check box is whose data source with reference data set
selected to enable the values belong to a matching that of the tree.
Restrict Tree Node different reference data
List of Values Based set than the tree.
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
does not apply when
the check box is not
selected.
Label Enabled Node On the Manage Tree The tree structure has a Assign a label to any
Structures: Specify labeling scheme but the node that does not have
Data Sources page, if tree version has nodes a label.
a labeling scheme is without labels.
specified for the tree
structure by selecting
a list item from the
Labeling Scheme
list box, all nodes
should have labels. This
restriction does not
apply when you select
None from the Labeling
Scheme list box.
169

Date Restricted Node On the Manage Tree Even when the check Ensure that all nodes
Structures: Specify Data box is selected, there in the tree version have
Sources page, if the are data source nodes effective date range for
Date Range check box that have a date range the effective date range
is selected to enable beyond the tree version's for the tree version.
the Restrict Tree effective date range.
Node List of Values For example, if the
Based on option for tree version is effective
a tree structure, each from Jan-01-2012
node in the underlying to Dec-31-2012, all
data source must nodes in the tree version
have an effective date must be effective
range same as the from Jan-01-2012
effective date range of to Dec-31-2012
the tree version. This at a minimum. It is
restriction does not apply acceptable for the nodes
if the check box is not to be effective for a date
selected. range that extends partly
beyond the tree version's
effective date range (for
example, the node data
source value is effective
from Dec-01-2011 to
Mar-31-2013). It is not
acceptable if the nodes
are effective for none
or only a part of the
tree version's effective
date range (for example,
the node data source
value are effective only
from Jan-01-2012 to
June-30-2012).

Multiple Active Tree On the Manage Tree Even when the check Set no more than one
Version Structures: Specify box is not selected, there tree version to Active
Definition page, if the is more than one active within the same date
Allow Multiple Active tree version in the tree range and set the others
Tree Versions check for the same date range. to inactive or draft
box is not selected for status.
the tree structure, there
should not be more than
one active tree version
under a tree at any time.
This restriction does not
apply if the check box is
selected.
170

Range Based Node On the Data Source Even when the check Ensure that any range
dialog box, if the Allow box is not selected, there nodes in your tree
Range Children check are range-based nodes version are from a data
box is not selected, from a data source. source that allows range
range-based nodes children.
are not permitted from
that data source. This
restriction does not
apply if the check box is
selected.
Terminal Node On the Data Source Even when the check Modify the tree version
dialog box, if the Allow box is not selected, such that all terminal
Use as Leaves check values from a data nodes are from data
box is not selected, source are added as leaf sources for which this
values from that data nodes (terminal nodes). check box is selected.
source cannot be added
as leaves (terminal
nodes) to the tree
version. This restriction
does not apply if the
check box is selected.
Usage Limit On the Data Source Even if the Use All For each data source
dialog box, if the Use Values option is value that is not yet
All Values option is selected, there are available, add nodes to
selected to set the values in the data source the tree version.
Usage Limit for the that are not in the tree
data source, every value version.
in the data source must
appear as a node in the
tree. This restriction does
not apply if None option
is selected.
Trees and Data Sources: How They Work Together

Data sources form the foundation for tree management in Oracle Fusion Applications. Tree structures, trees, and tree
versions establish direct and real-time connectivity with the data sources. Changes to the data sources immediately reflect on
the Manage Trees and Tree Versions page and wherever the trees are being used.
Metadata
Tree structures contain the metadata of the actual data that is used in Oracle Fusion Applications. Tree structures contain the
core business logic that is manifested in trees and tree versions.
Data Storage
Trees and tree versions are built upon the tree structures. They employ the business rules defined in the tree structures and
allow an application to select and enable a subset of trees to fulfill a specific purpose in that application.
171
Access Control
Source data is mapped to tree nodes at different levels in the database. Therefore, changes you make to the tree nodes
affect the source data. Access control set on trees prevents unwanted data modifications in the database. Access control
can be applied to the tree nodes or anywhere in the tree hierarchy.
Adding Tree Nodes: Points to Consider

Tree nodes are points of data convergence that serve as the building blocks of a tree structure. Technically, the node may be
stored either in a product-specific table or in an entity that has been established by tree management as the default storage
mechanism. However, since all data in Oracle Fusion Applications usually have a storage home, only user-created data needs
to be stored in an entity.
Nodes are attached to tree versions. Whenever you create or edit a tree version, you need to specify its tree node.
Managing Tree Nodes

You can create, modify, or delete tree nodes on the Tree Version: Specify Nodes page. To add a tree node, ensure that
the tree structure with which the tree version is associated is mapped to a valid data source. You can also duplicate a tree
node if the multiple root node feature is enabled.
Node Levels
In most trees, all nodes at the same level represent the same kind of information. For example, in a tree that reflects the
organizational hierarchy, all division nodes appear on one level and all department nodes on another. Similarly, in a tree that
organizes a user's product catalog, the nodes representing individual products might appear on one level and the nodes
representing product lines on the next higher level.
When levels are not used, the nodes in the tree have no real hierarchy or reporting structure but do form a logical
summarization structure. Strictly enforced levels mean that the named levels describe each node's position in the tree. This
is natural for most hierarchies. Loosely enforced levels mean that the nodes at the same visual level of indentation do not all
represent the same kind of information, or nodes representing the same kind of information appear at multiple levels. With
loosely enforced levels, users assign a level to each node individually. The level is not tied to a particular visual position.
Node Types
A tree node has the following node types.
• Single: Indicates that the node is a value by itself.
• 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 is not physically stored in the same tree. For example, a geographic hierarchy for the United States
can be referenced in a World geographic hierarchy.
Define Workforce Structures: FAQs for Manage Job

Families
What's the difference between a job set and a job family?

A job family is a group of jobs that have different but related functions, qualifications, and titles. They are beneficial for
reporting. You can define competencies for job families by associating them with model profiles.
172
A job set is an organizational partition of jobs. For example, a job set can include global jobs for use in all business units,
or jobs for a specific country or line of business. When you select a job for a position or an assignment, you can view the
available jobs in your business unit set and the common set.
Related Topics
• What's a job set?
Define Workforce Structures: Manage Job
Jobs: Explained
Jobs are typically used without positions by service industries where flexibility and organizational change are key features. As
part of your initial implementation, you specify whether to use jobs and positions, or only jobs.
Basic Details
Basic details for a job include an effective 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.
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 field 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.
Jobs and Grades

You can assign grades that are valid for each job. If you're using positions, then the grades that you specify for the job
become the default grades for the position.
Evaluation Criteria
You can define evaluation criteria for a job, including the evaluation system, a date, and the unit of measure for the system.
The Hay system is the predefined evaluation system that's available. An additional value of Custom is included in the list of
values for the Evaluation System field, but you must add your own criteria and values for this system.
Uploading Jobs Using a Spreadsheet

If you have a list of jobs already defined for your enterprise, you can upload them from a spreadsheet.
173
To use this option:
1. Download a spreadsheet template.

2. Add your job information to the spreadsheet.
3. Upload directly to your enterprise configuration.
You can upload the spreadsheet multiple times to accommodate revisions.
Related Topics
• Job and Position Lookups: Explained
• Enforcing Grades at Assignment Level: Points to Consider
Jobs: Example
Jobs are typically used without positions by service industries where flexibility 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 left the company.

• The director decides to redirect the head count to other areas.
• 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 fluid. Using jobs gives an enterprise the flexibility to determine where to use head
count, 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 flexibility to move the headcount to other areas.
This figure illustrates the software industry job setup.
174
Implementing Project Financial Management Define Project Organizations
6 Define Project Organizations

Define Project Units: Manage Project Unit
Organizations
Setting Up Organizations for Oracle Fusion Project Portfolio

Management: Worked Example
This example describes the creation of three organizations for use in Oracle Fusion Project Portfolio Management. One
organization is the project unit, the second organization can own projects and tasks, and the third organization can incur
project expenditures. This example also describes the selection of the organization hierarchy type that controls the hierarchies
that can be assigned to business units, and the association of project units and organizations to business units.
The following table summarizes key decisions for this scenario.
What organizations do I want to classify as project units? Project Operations

What organization hierarchy type will be used by Oracle HCM Organization Hierarchy Tree Structure
Fusion Project Portfolio Management?

What organizations will own projects or tasks? Fusion Operations

What organizations will incur project expenses? Fusion Corporation

What project units will be associated with business Project Operations

units?
Project Manufacturing

Project Services

To set up organizations for projects, complete the following tasks:

• Classify organizations as project units
• Classify organizations to own projects and tasks or incur costs on a project
• Select the organization hierarchy type for Oracle Fusion Project Portfolio Management
• Select organization classifications that are relevant to projects
• Select organization hierarchies for the business unit
• Associate project units with business units
175
Prerequisites
Verify that the implementation team completed the following prerequisite steps.
1. Set up organization hierarchies, organization classifications, and organizations.

2. Enable the Project Accounting business unit function for all project business units.
Classifying Organizations as Project Units

To create a project unit organization, either enable an existing organization as a project unit or create a new organization as a
project unit. After the project unit is enabled for an organization, the project unit appears in searches on the Manage Project
Units page.
1. Click Create on the Manage Project Unit Organizations page.

2. On the Manage Project Unit Organizations page, complete the fields, as shown in this table.
Field Value
Create new Selected

Code PROJECT_OPS

Name Project Operations

Classifying Organizations to Own Projects and Tasks or Incur Costs on

a Project
Specify which organizations can own projects and tasks, and incur project expenses. If an organization can be a project
and task owning organization, you also specify whether the organization allows indirect, capital, and contract projects,
and associate the organization with a default project unit that is used during the project definition flow to control the list of
organizations that can own the project.
1. In the Search: Organization region of the Manage Project Organization Classifications page, enter the name Fusion
Operations and click Search.
2. In the Search Results: Organization region, select the Fusion Operations row and click Edit.
3. In the Change All Selected region of the Edit Project Organization Classifications page, complete the fields, as
shown in this table.
Field Value
Classify as Project Task Owning Organization Selected

Allow indirect projects Selected
176
Field Value

Note
The Allow indirect projects option allows
the organization to own projects that
are used to collect and track costs for
overhead activities.

Allow projects enabled for capitalization Selected

Allow projects enabled for billing Selected

Project Unit Project Operations

For organizations that can own capital contract projects, select the options to allow projects enabled for
capitalization and enabled for billing options.
4. Select Save and Close, then proceed to the next step to specify a project expenditure organization.
5. In the Search: Organization region of the Manage Project Organization Classifications page, enter the name Fusion
Corporation and click Search.
6. In the Search Results: Organization region, select the Fusion Corporation row and click Edit.
7. In the Change All Selected region of the Edit Project Organization Classifications page, complete the field, as shown
in this table.
Field Value
Classify as Project Expenditure Organization Selected

8. Select Save and Close.
Selecting the Organization Hierarchy Type for Oracle Fusion Project

Portfolio Management
Select the organization hierarchy type for use in Oracle Fusion Project Portfolio Management, which enables you to assign
organization hierarchies, such as the project and task owning organization hierarchy and project expenditure organization
hierarchy, to project business units.
1. In Oracle Fusion Project Portfolio Management on the Manage Organization Hierarchies and Classifications page,
go to the Organization Hierarchy Types region.
2. Select HCM Organization Hierarchy Tree Structure as the organization hierarchy type for Oracle Fusion Project
Portfolio Management.
Important
A hierarchy must be set up in Oracle Fusion Human Capital Management for the selected hierarchy type.
177
Selecting Organization Classifications that are Relevant to Projects

Oracle Fusion applications support many organization classifications, although some of the organization classifications may
not be relevant to a project. Only organizations with the classifications that you select in this task are available in choice lists
in areas of the application where a specific organization classification is not required, such as during set up of capitalized
interest rate schedules.
1. In Oracle Fusion Project Portfolio Management on the Manage Organization Hierarchies and Classifications page,
go to the Organization Classifications region.
2. In the Available column, select the organizations that are relevant to projects, as shown in this table.
Field Value
Available Asset Organization

Business Unit

Partner Organization

Project Expenditure Organization

Project Manufacturing Organization

Project Task Owning Organization

Project Unit Classification

3. Click the right arrow to move the selected items to the Selected column.
To select multiple organizations, hold down the control key as you select the desired organizations, then click the
right arrow.
Selecting Organization Hierarchies for the Business Unit

Associate project and task owning organizations to the business unit to restrict the project owning organizations in the project
creation flow. Associate project expenditure organizations to the business unit to restrict which organizations can incur costs
on the project. Specify an entire organization hierarchy to associate with the business unit by selecting the top node on
the tree, rather than individually associating organizations with the business unit. Specify part of an organization hierarchy
by selecting an organization at any level of the hierarchy as the starting node on the tree. Oracle Fusion Project Portfolio
Management associates all organizations in the hierarchy from the starting node down with the business unit.
178
Note
The following conditions are required for an organization to be eligible to be a project and task owning
organization:
• You must assign the Project and Task Owning Organization classification to the organization.
• The organization must belong to the hierarchy that you specify in the project implementation options for the
business unit.
The following conditions are required for an organization to be eligible to be a project expenditure organization:
• You must assign the Project Expenditure Organization classification to the organization.
• The organization must belong to the hierarchy that you specify in the project implementation options for the
business unit.
1. Go to the Configure Project Accounting Business Function setup page for the Vision Corporation Enterprise
business unit.
2. On the Project Setup tab, Project Task Owning Organization region, complete the fields, as shown in this table.
Field Value
Tree Name Corporate Tree Structure

Tree Version Name Corporate Tree Structure Version 1

Organization Project Operations

3. Select the Expenditures tab.

4. In the Project Expenditure Organization region, complete the fields, as shown in this table.
Field Value
Tree Name Corporate Tree Structure

Tree Version Name Corporate Tree Structure Version 1

Organization Corporate Operations

179
Associating Project Units with Business Units

1. Go to the Configure Project Accounting Business Function setup page for the Vision Corporation Enterprise
business unit.
2. On the Configure Project Accounting Business Function page, select the Project Units tab.
3. In the Available Project Units column, select the project units to associate with this business unit, as shown in
this table.
Field Value
Available Project Units Project Services

Project Manufacturing

Project Operations

4. Click the right arrow to move the selected items to the Selected Project Units column.
Define Project Units: Manage Project Unit Options
Creating a Project Unit: Worked Example

This example demonstrates how to complete the following tasks:
• Define project unit general properties
• Define project unit related business units
• Define project unit summarization options
• Define project unit performance reporting options
• Define project unit analytic reporting options
What is the default reference set for projects in this Enterprise set
project unit?

Note
By default, the set for each reference data
object comes from the default set specified
in the project unit general properties. Use the
Manage Project Unit Set Assignments flow to
assign sets to project units to determine how
reference data is shared across different lines
of business in a company.

180
Should I relate business units to this project unit? Yes

Note
Identify the business units that are
accountable for financial transactions for
projects in this project unit. Business units
that are not associated with any project unit
are valid for all project units.

What transactions should I include in project Cost, commitment, and budget and forecast
performance data summarization? transactions

Requisitions, purchase orders, and budget and forecast
commitment types

What currency and calendar types should be Project currency and project ledger currency
summarized and displayed on project performance
reports? Project accounting calendar and accounting calendar

Should I track key performance indicators? Yes

Should I track missing time cards from employees? Yes

Note
Missing transactions such as time cards may
affect project performance results, which
may result in misleading key performance
indicators for the project.

For each project unit, you configure project management settings such as the default set assignment, project numbering
series, full-time equivalent hours, related business units, and reporting options.
Prerequisites
This example is based on the assumption that the following prerequisite setup tasks are complete:
1. Set up organization hierarchies, organization classifications, and organizations.

2. Enable the Project Accounting business unit function for all project business units.
3. Classify organizations as project units.
Defining Project Unit General Properties

1. On the Manage Project Units page, Search Results region, select the Project Operations project unit, and click Edit.
2. On the Manage Project Units: General Properties page, complete the fields, as shown in this table.
181
Field Value
Default Set ENTERPRISE

Project Numbering - Method Manual

Project Numbering -Type Alphanumeric

Full-Time Equivalent Hours -Daily 8

Full-Time Equivalent Hours -Weekly 40

Defining Project Unit Related Business Units

1. Click Next on the Manage Project Units: General Properties page.
2. On the Manage Project Units: Related Business Units page, Available Project Units column, select the business
units to associate with this project unit, as shown in this table.
Field Value
Available Business Units Corporate Enterprise

Corporate Manufacturing

Internal Systems and Support

3. Click the right arrow to move the selected business units to the Selected column.
To select multiple items, press the control key while you select the desired business units, then click the right arrow.
Defining Project Unit Summarization Options

Specify which transaction amounts are summarized for display on project performance reports and whether to automatically
summarize the data when a transaction is created. Specify which commitment types and statuses are summarized for display
on project performance reports. Select the currency and calendar types to summarize and display financial information on
project performance reports.
1. Click Next on the Manage Project Units: Related Business Units page.
2. On the Summarization Options tab, Data Sources region, complete the fields, as shown in this table.
Field Include in Summarization Value
Cost Selected

182
Field Include in Summarization Value
Commitments Selected

Budgets and Forecasts Selected

3. In the Commitment Types region, complete the fields, as shown in this table.
Field Include in Summarization Status Value

Value
Requisitions Selected All

Purchase Orders Selected All

Budgets and Forecasts Selected All

Other Commitments Not selected Not applicable

4. In the Currency Types region, complete the fields, as shown in this table.
Field Value
Project currency Selected

Transaction currency Not selected

Project ledger currency Selected

5. In the Calendar Types region, complete the fields, as shown in this table.
Field Value
Project accounting calendar Selected

Accounting calendar Selected

6. In the Planning Amount Allocation region, complete the field, as shown in this table.
183
Field Value
Basis Period start date

Defining Project Unit Performance Reporting Options

Select the reporting options that determine the default display on project performance reports.
1. Click the Performance Reporting Options tab on the Manage Project Units: Reporting Setup page.
2. In the Performance Reporting Options tab, Reporting Options region, complete the fields, as shown in this table.
Field Value
Currency Type Project currency

Calendar Type Accounting

Effort Unit of Measure Hours

Project Accounting Period Current period

Accounting Period Current period

Amount Scale 1

3. In the Key Performance Indicators region, complete the fields, as shown in this table.
Field Value
Track key performance indicators Selected

Generate key performance indicators Not selected

Summarize project data Selected

Defining Project Unit Analytic Reporting Options

1. Click the Analytic Reporting Options tab on the Manage Project Units: Reporting Setup page.
2. In the Analytic Reporting Options tab, Missing Time region, complete the fields, as shown in this table.
184
Field Value
Track missing time Selected

Number of Prior Weeks 3

Include current week Selected

Comparison Period in Days 35

3. In the Missing Time Sources region, complete the field, as shown in this table.
Field Source Value Document Value
Missing Time Sources Time Entry System Time Card

4. In the Current Exception Reporting region, enter a value of 35 for the Comparison Period in Days field.
Project Unit Components: How They Work Together

Project units are operational subsets of an enterprise that conduct business operations using projects and need to enforce
consistent project planning, management, analysis, and reporting. Project units often represent lines of business, such as
Consulting Services, Sales, and Research and Development. You must set up at least one project unit to use in Oracle Fusion
Project Portfolio Management.
You can maintain independent setup data for each project unit while sharing a single approach to financial management
across all project units. The following diagram shows two project units that share a common approach to financial
management and data. Each project unit maintains separate reference data for managing projects.
General Properties
General property options include the default reference data set to be used for any new reference data object associated with
the project unit. You can override the default set for each reference data object. The method of project number creation,
185
either manual or automatic, and daily or weekly full time equivalent hours for reporting purposes, are also included in general
properties.
Set Assignments
You assign sets to project units to determine how reference data is shared across different lines of business in a company. A
project unit is a set determinant for the following objects.
• Project definition, which includes set-enabled reference data for the project definition such as class code, financial
plan type, project role, and project status.
• Project transaction types, which include set-enabled reference data for project transactions such as project
expenditure type and project work type.
Set assignment configuration includes the following options for each project unit.
• Reference set value: By default, the set for each reference data object is from the default set specified for the project
unit.
• Reference data objects: For the project definition and project transaction types.
Related Business Units

You associate business units with a project unit to identify the business units that are accountable for financial transactions of
projects in each project unit. You can change the project unit and business unit association if the combination has not been
used on a project or project template. If a business unit is not associated with any project unit, then the business unit is valid
for all project units.
Reporting Setup
Project performance reporting configuration includes the following options for each project unit.
• Summarization data sources, commitments to include in summarization, currency types, calendar types, and the
planning amount allocation basis for summarization.
• Default reporting options that determine how data appears in the Project Performance Reporting dashboard and
reports. You can override these settings.
• Key performance indicators tracking option.
• Analytic reporting options to track missing time transactions.
• Time sources that are available for the project unit.
• Number of days prior to current date to include in current reporting data.
Using Multiple Project and Business Units: Examples

A project unit defines a set of rules and options for creating and managing the nonfinancial aspects of projects, such as
project definition, scheduling, and reporting. You can define one or more project units based on how granular you want
to separate processing options, reference data, security, and other controls. The list of project units can be different
and independent from the list of business units that perform your enterprise financials functions, such as payables and
receivables.
Following are two examples of associating project units and business units.
186
Single Project Unit with Multiple Business Units

A consulting company has offices in the US, Canada, and Mexico. Each location uses local purchasing and payables
practices. The company uses projects to track time and expenses for billing through contracts.
Multiple Project Units with Multiple Business Units

A products and services company has main offices in the US and a warehouse and sales office in Canada. Due to operations
in two different countries, the company partitions financial data by using two business units. The research processes are
the same in both countries, so a single project unit facilitates common project management practices. The company has
an information technology (IT) services project unit that is associated with US business unit, and a sales and consulting
project unit that is associated with both the US and Canadian business units. The consulting line of business uses projects to
manage consulting engagements and provide billing details to contracts. The internal real estate line of business uses projects
to manage the US and Canada facilities, including new construction and repairs.
187
Performance Data Summarization: How It Is Calculated

Summarization is a systematic organization of information for purposes of project analysis and tracking. You use summarized
data to analyze the health of projects and drill down to the causes of any deviation from set thresholds. You can complete the
following tasks using summarized data:
• Analyzing project performance data
• Reviewing project performance
• Analyzing KPI categories and KPIs
• Tracking project progress
• Viewing revenue and invoice summaries
After you run summarization, the KPI related information is rendered out of date with respect to the latest summarized
information. Therefore, it is important that you generate KPI values once the summarization process is completed. You can
avoid generating KPI values manually, by enabling automatic generation of KPI values in the summarization options.
Settings That Affect Performance Data Summarization

You summarize data for a project unit or a business unit. You can also summarize performance data for a range of projects or
projects owned by a project manager. Besides this, you must specify the following parameters each time you want to run the
summarization process manually:
• Select the appropriate summarization method:
◦ Incremental, for general purpose summarization.
◦ Bulk, for summarizing large amounts of data all at once.
◦ Delete and resummarize, for correcting summary data when the source system data is changed outside the
regular transaction flow.
◦ Resource breakdown structure, for migrating all summary data from one resource breakdown structure version
to the next. If you select this option you must also specify the resource breakdown structure header.
• Specify whether to summarize budget and forecast, commitment, actual cost, revenue and invoice, and client
extension transactions.
How Performance Data Summarization Is Calculated

Performance data summarization collects data from various sources and assigns amounts to relevant tasks and resources
in the project. After data is summarized, you can view how much is being spent on, incurred by, or received by a task or
resource. Also, data is grouped according to periods so that it can be tracked across different time lines.
You can run the summarization process for different situations, such as:
• Your data is out of date and you want to update it.
• Your data is corrupt and you want to delete the existing data and resummarize.
188
• You have a large volume of data that is not yet summarized and want to summarize the entire bulk of data in one
run.
After you select the parameters for summarization and submit a request, the application performs the following steps to
generate the data that you view in the application:
• Scope summarization by determining the list of projects, contracts, and batches of transaction data for which to run
summarization.
• Extract data to be summarized from data sources, group it by periods, and ensure the data is prepared for resource
mapping.
• Populate summary data into designated tables before resource breakdown structure mapping.
• Populate business unit, project unit, and other lookup information.
• Populate performance reporting dimension data including time, task breakdown structure, and resource breakdown
structure.
• Look up resource breakdown structure mappings, scenario dimension members, period IDs, and prepare data for
Essbase load.
• Load data into Essbase and merge data into summary tables.
You can track the progress of summarization on the process monitor. If the process fails to complete, it continues from the
point of failure when you resubmit it.
Related Topics
• KPI Values: How They Are Generated
• How can I update project performance data and generate KPI values?
FAQs for Define Project Units

How can I associate a business unit with a project unit?
You can associate a business unit with a project unit during the Related Business Units step of the Manage Project Units
setup task if the business unit is already configured using the Configure Project Accounting Business Function setup task.
If the business unit is not configured, then you can associate a project unit with the business unit on the Project Units tab of
the Configure Project Accounting Business Function page.
What happens if I change the organization hierarchy type that is available for project
applications?
Changing the organization hierarchy type impacts existing transactions that use the hierarchy. Hierarchies that are specified
for the business unit are invalidated, which invalidates the values selected for the project and task owning organization and
project expenditure organization for the business unit.
The action also affects cross-charge transactions and capitalization transactions because the available hierarchies in these
areas are based on the hierarchies specified for the business unit.
189
Important
The organization hierarchy type used in Oracle Fusion Projects must be the same organization hierarchy type that
is set up in Oracle Fusion Global Human Resources for Oracle Fusion applications.
What happens if I remove organization classifications from the list of selected classifications
that are available for project applications?
The organization classifications no longer appear in the list of organization values that are available for selection in the
application.
Selected organization classifications on the Manage Organization Hierarchies and Classifications page are available for
selection in areas of the application where a specific organization classification is not required, such as setting up capitalized
interest rate schedules, burden schedules, and transfer price schedules.
What happens to project and task owning organizations and project expenditure
organizations if human resource organizations are reorganized?
The business unit implementation options for project and task owning organizations and project expenditure organizations
may become invalid. A project and task owning organization must belong to the organization hierarchy that is assigned to the
business unit, be classified as a project and task owning organization, and be active on the system date. Similar criteria apply
to project expenditure organizations.
If any of these conditions change as a result of the reorganization, then you may need to modify the organization hierarchy
used for Oracle Fusion Projects, project organization classifications, and project business unit options. Depending on the
new structure, you may also need to run the Change Project and Task Organizations process and Denormalize Organization
Hierarchies process.
What's a project expenditure organization?

A project expenditure organization is one that can incur expenditures and hold financial plans for projects. For an organization
to be eligible to be a project expenditure organization, you must assign the organization the Project Expenditure Organization
classification, and the organization must be assigned to the hierarchy that you specify in the project implementation options
for the business unit.
What's a project and task owning organization?

Every project is owned by an organization that is used for reporting, security, and accounting. An organization can own
specific types of projects, such as indirect projects, capital projects, billable projects, and capital contract projects. On a
contract project, the project owning organization can also be used in the accounting rules to determine which general ledger
cost center receives credit for the revenue. Assign project and task owning organizations to project units to specify which
organizations are available to own the project.
What's the difference between organizations and organization hierarchies?

Organizations are departments, sections, divisions, companies, or other organizational units in your enterprise. You can
gather collections of organizations into organization hierarchies.
Organization hierarchies help you manage expenditure and reporting data, and coordinate the project-owning organizations in
your enterprise.
During implementation, you select the organization hierarchy type for use in Oracle Fusion Projects, either the department
hierarchy tree structure or the generic organization hierarchy tree structure. Then you assign hierarchies to the project
implementation options for each business unit used in Oracle Fusion Projects.
Important
The organization hierarchy type used in Oracle Fusion Projects must be the same organization hierarchy type that
is set up in Oracle Fusion Global Human Resources for Oracle Fusion applications.
190
What's the difference between manual and automatic methods of numbering projects?
The manual method of project numbering requires you to enter a unique alphanumeric project number each time you create a
project.
The automatic method of project numbering requires that you set up the first project number during project unit configuration,
and then the application automatically assigns an incremental project number at project creation.
What's the difference between the project unit organization code and name?
Typically the project unit name is logical, descriptive, and easily recognizable.
The code is a unique short name that is used internally.
Both the project unit organization code and name are used to identify the project unit.
Can I specify the budgets and forecasts to include in summarization?

Certain financial plan types are included in summarization by default, while you must manually select others. Approved
forecast and baseline budget versions of the following financial plan types are automatically included in summarization of
project performance data:
• Approved Revenue Budget
• Approved Cost Budget
• Primary Revenue Forecast
• Primary Cost Forecast
Apart from the default financial plan types, you can include up to four others in summarization of project performance data.
What happens when I select a planning amount allocation basis for the project unit?
The Period Start Date and Period End Date options allocate amounts based on the period start and end dates. The Daily
Proration option spreads plan amounts evenly across the plan.
Define Project Units: Manage Project Unit Set

Assignments
Associating Sets with Financial Plan Types: Example

You associate sets with financial or project plan types so that project managers can use them to create financial plans
(budget or forecast versions) or project plans for projects or project templates. Financial or project plan types are available for
selection only when projects or project templates are created for project units linked to selected sets.
The following example illustrates the relationship between financial plan types, sets, and project units. Project plan types
share an identical relationship with sets and project units.
Scenario
An organization has two designated project units for project creation: Project Unit 1 and Project Unit 2. Project Unit 1 is
associated with Set 1 and Project Unit 2 is associated with Set 2.
During implementation, two financial plan types were created: Financial Plan Type A and Financial Plan Type B. Financial Plan
Type A is associated with Set 1. However, Financial Plan Type B is associated with both Set 1 and Set 2.
191
In such a case, project managers working on projects for Project Unit 1 can use only Financial Plan Type A to create financial
plan versions. Project managers working on projects for Project Unit 2 can use both Financial Plan Type A and Financial Plan
Type B.
The following diagram further illustrates the relationship between financial plan types, sets, and projects. Project plan types
share the same relationship with sets.
Set Assignments and Project Data: How They Work Together

Reference data set assignments determine how you share enterprise information, including project data, across
organizational units. In other words, you can decide which data is global, which data can be shared by certain organizations,
and which data must remain organization-specific. Reference data sharing enables enterprises to balance autonomy and
control for organizations.
Oracle Fusion Projects employs two set determinants: business unit and project unit.
192
Business Unit as Set Determinant

Business units enable you to control and report on financial transactions, usually for specific geographical entities within the
enterprise. For project management purposes, assign the Project Accounting business function to the business unit.
Business unit is a set determinant for the following project-related reference data objects.
Project Accounting Definition Project types

Project Rates Project rate schedules

You assign a default set to each business unit. You can optionally override the default set for the Project Accounting
Definition and Project Rates reference data objects. To enable a project type or rate schedule for use within the business
unit, you must assign the same reference data set to that entity.
Note
If you assign a common set to a rate schedule, then that rate schedule is available for use across business units.
Project Unit as Set Determinant

Use project units to enforce consistent project management practices across your enterprise. Project unit is a set determinant
for the following reference data objects.
Project Definition Class codes, financial plan types and project plan types,
project roles, and project statuses

Project Transaction Types Expenditure types and work types

When specifying project unit implementation options, you select a default set. You can optionally override the default set for
the Project Definition and Project Transaction Types reference data objects. To enable an entity like a financial plan type
for use on projects owned by a project unit, assign the set associated with the Project Definition reference data object to the
financial plan type.
Similarly, to enable expenditure types and work types for use on projects owned by a project unit, assign the set associated
with the Project Transaction Types reference data object to those entities.
Related Topics
• Partitioning Project Data Using Set Determinants: Examples
• Project Units: Explained
• Reference Data Sharing: Explained
193
Partitioning Project Data Using Set Determinants: Examples

Use business units and project units to independently manage access to financial and project management data based on
the unique requirements of your enterprise.
This topic illustrates the following scenarios.
1. Maintaining separate project management methodologies and data across units within an enterprise while
centralizing financial management of data
2. Enforcing a single project management methodology across units within an enterprise while partitioning financial
data
Note
These examples are only illustrative. Any combination of business units and project units can exist.
Using Multiple Project Units with One Business Unit

Assume that Vision Corporation is a services company with facilities across the United States. Its business is based on
research and development activities and consulting practice. Projects are used by each line of business as follows:
• Consulting uses projects to manage consulting engagements and provide billing details to contracts.
• Research and Development uses projects to manage design project schedules.
• Real Estate uses projects to manage facilities, including new construction and repairs.
Vision Corporation implemented project units and business units as follows:
• Project Units
◦ Consulting
◦ Real Estate
◦ Research and Development
• Business Unit: Vision Corporation
Set assignments for reference data objects, where project unit is the set determinant, are as follows:
Consulting Consulting Set

Real Estate Real Estate Set

194
Research and Development Research and Development Set

Note
The default set is used as the reference data set for both the Project Definition and Project Transaction Types
reference data objects.
Vision Corporation can maintain independent setup data for each project unit, while sharing a single approach to financial
management across all project units. For example, Vision Corporation uses different expenditure types across project units,
as described in the table below.
Labor Consulting Set

Real Estate Set

Research and Development Set

Airfare Consulting Set

Hotel Consulting Set

Equipment Real Estate Set

The Labor expenditure type can be used for projects belonging to any project unit. However, expenditure types for airfare and
hotel accommodation are used only on consulting projects.
Using Multiple Business Units with One Project Unit

Assume that InFusion Corporation is a services and product development company with research and development facilities
across the globe, including in the United States and Canada. Due to its international operations, financial data must be
partitioned using separate business units. However, basic research and development activities, based on projects, are the
same across the enterprise. Therefore, a single project unit is created.
The enterprise structure and set assignments are described below.
• Project Unit: Research and Development

• Business Units
◦ InFusion United States
◦ InFusion Canada
Default set assignments for the business units are as follows:
195
Business Unit Default Set
InFusion United States US Set

InFusion Canada Canada Set

InFusion Corporation maintains independent financial data for each business unit, while employing a unified approach to
project management that includes common financial and project plan types, project roles, and project statuses. As the
enterprise must use different resource rates in each country, rate schedule setup is as follows.
Enterprise Project Rates: United States US Set

Enterprise Project Rates: Canada Canada Set

Common Enterprise Project Rates Common Set

These set assignments govern how planned and actual amounts are calculated for projects.
For example, when InFusion Corporation defines organization costing rules for the InFusion United States business unit, they
can select only the Enterprise Project Rates: United States or the Common Enterprise Project Rates rate schedules. Later,
the application uses the selected rate schedule to calculate actual costs when project accountants import uncosted time
cards for the InFusion United States business unit.
Define Project Business Unit Options

business units.
196

Related Topics
Business Units: How They Work with Projects

Business units are subsets of an enterprise that perform one or more business functions and can be consolidated in both a
managerial and legal hierarchy. Project accounting is an example of a business function that is set up by business unit. Other
examples are billing and revenue management, customer contract management, and payables invoicing.
Business units are defined centrally. During implementation, you must enable the Project Accounting business unit for use
with Oracle Fusion Project Portfolio Management.
You can partition financial data using business units while sharing a single approach to project management across all
business units. The following diagram shows two business units, one from the United Kingdom (UK) and one from the United
197
States (US). These business units have the same research and development processes, so a single project unit is used by
both business units to facilitate common project management practices.
Project Setup
Following are project setup options for each business unit that you enable for use with Oracle Fusion Project Portfolio
Management.
• Project and task owning organization name, tree name, and tree version name.
Important
To own projects or tasks, an organization must be classified as project and task owning organization,
belong to the hierarchy associated with the business unit, and be active on the system date. The project
type class must be permitted to use the organization to create projects.
• Project and task owning organizations are associated with the business unit to restrict these organizations in project
creation flow. The project initiator specifies the business unit for the project, then can select from only those project
and task owning organizations that are associated with the selected business unit.
Note
A project can be associated with only one business unit.
Project Expenditure
Following are business unit project expenditure implementation options.
• Day of the week when the expenditure cycle begins.

• Project expenditure organizations to associate with the business unit to restrict which organizations can incur costs
on the project.
Project Costing
Following are business unit project costing implementation options.
• Project accounting calendar, either the default project accounting calendar from primary ledger calendar, or a
different calendar to assign to the business unit. You can change this calendar until you copy the project accounting
periods.
198
• Default asset book for assets in the business unit. The asset initiator can select a different asset book for the asset.
• Option to use either common accounting and project accounting periods, or unique project accounting periods.
• Overtime calculations option.
• Asset retirement processing option to capture and record the cost of removal and the proceeds of sale amounts for
retiring an asset.
• Separation of duties option for entering and releasing expenditure batches to ensure accuracy and accountability of
project costs.
• Conversion rate type to use when converting the amount on cost transactions in this business unit from the
transaction currency to the ledger currency.
Project Units
Project units are associated with business units to restrict the business units that can handle project transactions. When a
project unit isn't associated with a business unit, any business unit in your enterprise can process project transactions.
Cross-Charge Transactions
Following are business unit cross-charge transaction implementation options.
• Transfer price currency conversion rate date type and rate type for the business unit.
• Borrowed and lent cross-charge transaction option for distributions to be created for cross-charge transactions
between different organizations in the same business unit and legal entity.
• Borrowed and lent cross-charge transaction option for distributions to be created for cross-charge transactions
between different business units in the same legal entity.
• Borrowed and lent cross-charge transaction option for distributions to be created for cross-charge transactions for a
specific receiver business unit.
Customer Contract Management

You can configure customer contract management business function properties, such as currency conversion, cross-charge
transaction, and billing options, for each contract business unit.
Reference Data Sharing

Assign sets to business units to determine how reference data is shared across applications. A business unit is a set
determinant for the following objects:
• Project accounting definition, including set-enabled reference data such as project type.
• Project and contract billing, including set-enabled reference data such as invoice format.
• Project rates, including set-enabled reference data such as rate schedules.
Maintaining Accounting Periods and Project Accounting

Periods: Critical Choices
During business unit implementation you determine whether to maintain common accounting and project accounting periods,
or define project accounting periods that have a different frequency than the accounting periods.
199
Accounting periods are used by Oracle Fusion Projects to assign accounting periods and dates to transactions. Accounting
periods are maintained by ledger and use the same calendar as the general ledger periods. Project accounting periods are
used by Oracle Fusion Projects for project planning, costing, billing, budgeting, forecasting, and performance reporting.
Project accounting periods are maintained by business unit and typically do not use the same calendar as the accounting and
general ledger periods.
Maintaining Common Accounting and Project Accounting Periods

If you want to report project information with the same frequency as the accounting periods, you can use the accounting
period as both the accounting and project accounting period.
When you maintain common accounting and project accounting periods, period maintenance is simplified, calendar periods
are not copied to Oracle Fusion Projects, and period information is maintained in one physical location. Use Oracle Fusion
General Ledger to maintain accounting period statuses and run the processes to open and close accounting periods.
Defining Project Accounting Periods that are Different from Accounting Periods
If you want to account for project transactions and report project information more frequently than the accounting periods
allow, you can define project accounting periods that are shorter than the accounting periods. For example, you can define
weekly project accounting periods and monthly accounting periods, as shown in the following diagram.
Use Oracle Fusion General Ledger to maintain accounting period statuses and run the processes to open and close
accounting periods, and Oracle Fusion Projects to maintain project accounting period statuses and run the processes to
open and close project accounting periods.
FAQs for Define Project Business Unit Options

How can I set up common accounting and project accounting periods?
Complete these tasks to set up common accounting periods and project accounting periods.
• Set up the accounting calendar and manage the accounting period statuses in Oracle Fusion General Ledger.
• During project business unit implementation, set the project accounting calendar to the accounting calendar and
select the option to maintain common accounting and project accounting periods.
200
How can I set up project accounting periods that are different from accounting periods?
Complete these tasks to set up project accounting periods that are different from accounting periods.
• During project business unit implementation, specify the project accounting calendar for each business unit.
◦ Verify that the option to maintain common accounting and project accounting periods is not selected.
• Copy the accounting calendar into the project accounting period table, which copies the period start and end dates.
• Manage the period statuses for project accounting periods.
What's the difference between a project accounting period, an accounting period, and a
general ledger period?
Project accounting periods are used to track budgets and forecasts, summarize project amounts for reporting, and track the
project status. Project accounting periods are maintained by the business unit. You can set up project accounting periods
to track project periods on a more frequent basis than accounting periods. For example, you can define weekly project
accounting periods and monthly accounting periods. If you use the same calendar as your accounting periods, the project
accounting periods and accounting periods will be the same, although the statuses are maintained independently.
Accounting periods, which are used to derive accounting dates, are maintained by the ledger and use the same calendar as
the general ledger periods. Period statuses for the accounting period and general ledger period are maintained independently.
Note
You can select an option on the business unit definition to maintain common accounting and project accounting
periods. This option allows the accounting period to be used as the project accounting period and you maintain
only one period status.
What happens if I close an accounting or project accounting period permanently?

You can't enter any transactions in the period you have closed and you can adjust transactions in subsequent periods.
How can I associate a business unit with a project unit?

You can associate a business unit with a project unit during the Related Business Units step of the Manage Project Units
setup task if the business unit is already configured using the Configure Project Accounting Business Function setup task.
If the business unit is not configured, then you can associate a project unit with the business unit on the Project Units tab of
the Configure Project Accounting Business Function page.
201
Implementing Project Financial Management Define Users and Security
7 Define Users and Security
Define Security: Overview

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 tasks in these task lists, as appropriate:
• Define Security for Financials
• Define Security for Procurement
• Define Users and Security for Product Management
• Define Security for Project Execution Management
• Define Security for Project Financial Management
• Define Security for Supply Chain Management
This topic introduces the tasks in these task lists. 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 most tasks in these task lists both during implementation, and later as requirements emerge.
Manage Job Roles

The Oracle ERP Cloud and Oracle SCM Cloud security reference implementations provide many predefined job roles. You
can perform the Manage Job Roles task to:
• Review the role hierarchy and other properties of a job or abstract role.
• Create custom job and abstract roles.
• View the roles assigned to a user.
• View the users who have a specific role.
A user with the IT Security Manager or Application Implementation Consultant job role performs the Manage Job Roles task.
202
Manage Duties
The Oracle ERP Cloud and Oracle SCM Cloud security reference implementations provide many predefined duty roles. You
can perform the Manage Duties task to:
• Review the duties of a job or abstract role.
• Manage the duties of a custom job or abstract role.
• Create custom duty roles.
A user with the IT Security Manager job role performs the Manage Duties task.
Define Data Security

You can manage Oracle ERP Cloud and Oracle SCM Cloud application data by performing tasks in these task lists:
• Define Data Security for Financials
• Define Data Security for Procurement
• Define Data Security for Product Management
• Define Data Security for Project Financial Management
• Define Data Security for Supply Chain Management
You can perform the tasks in these task lists to:
• Manage data access sets that secure ledgers.
• Manage data role templates that facilitate data role provisioning.
• Manage Human Capital Management (HCM) security profiles that facilitate data role assignment for application
users.
• Manage data security policies that determine grants of entitlement to a user or role on an object or attribute group.
A user with the IT Security Manager job role performs the tasks in the Define Data Security task lists.
Manage Role Provisioning Rules

You create role mappings to control the provisioning of all types of roles to application users by performing this task. For
example, you can create a role mapping to provision the Accounts Payable Specialist role automatically to users that meet
criteria specific to accounts payable users.
A user with the IT Security Manager job role performs the Manage Role Provisioning Rules task.
Manage Oracle Social Network Objects

You can determine which business objects in Oracle ERP Cloud are available for social collaboration by performing this task.
For example, use this task to enable discussion among Oracle Social Network users about requisitions, purchase orders,
invoices, payments, receipts, and other transactions.
203
A user with the IT Security Manager or Application Implementation Consultant job role performs the Manage Oracle Social
Network Objects task.
Note
You can perform this task after you set up and configure Oracle Social Network. If you do not use Oracle Social
Network, you can skip this task.
204
Implementing Project Financial Management Define Automated Governance, Risk, and Performance
Controls
8 Define Automated Governance, Risk, and

Performance Controls
Segregation of Duties: Highlights

Segregation of duties (SOD) guards against individuals being assigned tasks that, in combination, may expose a company
to risk. For example, SOD controls may ensure that a person cannot both initiate a purchase order and approve payment
on that purchase order. Oracle Application Access Controls Governor (AACG) can provide SOD analysis in Oracle Fusion
Applications.
Note: A given version of AACG is not necessarily certified for use with a given version of Oracle Fusion Applications.
Before acquiring a license for any version of AACG, confirm whether it is certified for use with your version of Oracle Fusion
Applications.
For information on using AACG, see the Oracle Application Access Controls Governor User Guide and the Oracle
Application Access Controls Governor Implementation Guide. Both are available on Oracle Technology Network at http://
www.oracle.com/technetwork.
SOD Analysis in AACG

• AACG users create "continuous controls," which define conflicts among "access points." These, in turn, are objects
(such as roles, privileges, or permissions) that enable a person to view or manipulate data in applications such as
Oracle Fusion Applications. Each control identifies people who have been assigned the access points it defines as
conflicting.
• AACG control analysis may be detective, meaning that it uncovers SOD conflicts that currently exist. In this case,
controls generate "incidents" (records of violations), and "result investigators" use AACG to track the resolution of
those incidents. Resolution may involve rescinding a role assignment to a user, or redefining a role or other object in
a role hierarchy.
• AACG analysis may instead be preventive, meaning that continuous controls are evaluated at the moment a person
is assigned new access. Depending on how a continuous control is configured, it may permit the assignment of
conflicting access points (with the understanding that the assignment is to be monitored), prevent the assignment, or
suspend it pending approval.
205
Implementing Project Financial Management Define Project Portfolio Management Common Reference
Objects
9 Define Project Portfolio Management Common

Reference Objects
Manage Value Sets
Value Sets: Explained

A value set is a group of valid values that you assign to a flexfield segment to control the values that are stored for business
object attributes.
An end user enters a value for an attribute of a business object while using the application. The flexfield validates the value
against the set of valid values that you configured as a value set and assigned to the segment.
For example, you can define a required format, such as a five digit number, or a list of valid values, such as green, red, and
blue.
Flexfield segments are usually validated, and typically each segment in a given flexfield uses a different value set. You can
assign a single value set to more than one segment, and you can share value sets among different flexfields.
Caution
Be sure that changes to a shared value set are compatible with all flexfields segments using the value set.
The following aspects are important in understanding value sets:
• Managing value sets

• Validation
• Security
• Precision and scale
• Usage and deployment
• Protected value set data
Managing Value Sets

To access the Manage Value Sets page, use the Manage Value Sets task, or use the Manage Descriptive Flexfields and
Manage Extensible Flexfields tasks for configuring a segment, including its value set. To access the Manage Values page,
select the value set from the Manage Value Sets page, and click Manage Values. Alternatively, click Manage Values from
the Edit Value Set page.
Validation
The following types of validation are available for value sets:
• Format only, where end users enter data rather than 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
206
Objects
• Table, where the values derive from a column in an application table and the list of values is limited by a WHERE
clause
A segment that uses a format only value set doesn't present a list of valid values to users.
Note
Adding table validated value sets to the list of available value sets available for configuration is considered a
custom task.
Restriction
For the Accounting Key Flexfield 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 flexfield segments.
You can specify that data security be applied to the values in flexfield segments that use a value set. Based on the roles
provisioned to users, data security policies determine which values of the flexfield segment end users can view or modify.
Value set security applies 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 flexfield is secured. It isn't possible to disable security for individual usages of the same value
set.
Value set security applies to independent, dependent, or table-validated value sets.
Value set security applies mainly when data is being created or updated, and to key flexfield combinations tables for query
purposes. Value set security doesn't determine which descriptive flexfield data is shown upon querying.
Security conditions defined on value sets always use table aliases. When filters are used, table aliases are always used by
default. When predicates are defined for data security conditions, make sure that the predicates also use table aliases.
For key flexfields, the attributes in the view object that correspond to the code combination ID (CCID), structure instance
number (SIN), and data set number (DSN) cannot be transient. They must exist in the database table. For key flexfields, the
SIN segment is the discriminator attribute, and the CCID segment is the common attribute.
Precision and Scale

If the data type of a value set is Number, you can specify the precision (maximum number of digits user can enter) or scale
(maximum number of digits following the decimal point).
Usage and Deployment

The usage of a value set is the flexfields where that value set is used. The deployment status of flexfields in which the value
set is used indicates the deployment status of the value set instance.
207
Objects
The figure shows a value set used by a segment in a key flexfield and the context segment of a descriptive flexfield.
For most value sets, when you enter values into a flexfield 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 flexfield 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.
Protected Value Set Data

Application developers may mark some value sets as protected, indicating that you can't edit them.
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.
Note
There is no restriction on references to protected value sets. Value sets, protected or not, may be assigned to
any flexfield segment. Likewise, other value sets may reference protected value sets; for example, an unprotected
dependent value set may reference a protected independent value set.
208
Objects
Related Topics
• Chart of Accounts: How Its Components Fit Together
• What's the difference between a lookup type and a value set?
Defining Value Sets: Critical Choices

Validation and usage of value sets determine where and how end users access valid values for attributes represented by
flexfield segments.
Tip
As a flexfield guideline, define value sets before configuring the flexfield, because you can assign value sets to
each segment as you configure a flexfield. With descriptive and extensible flexfield segments, you can create value
sets when adding or editing a segment on the run time page where the flexfield appears.
The following aspects are important in defining value sets:

• Value sets for context segments
• Format-only validation
• Interdependent value sets
• Table validation
• Range
• Security
• Testing and maintenance
Value Sets for Context Segments

When assigning a value set to a context segment, you can only use table-validated or independent value sets.
You can use only table and independent value sets to validate context values. The data type must be character and the
maximum length of the values being stored must not be larger than the context's column length. If you use a table value set,
the value set cannot reference flexfield segments in the value set's WHERE clause other than the flexfield segment to which
the value set is assigned.
Format Only Validation

The format only validation type enables end users to enter any value, as long as it meets your specified formatting rules. That
is, the value must not exceed the maximum length you define for your value set, and it must meet any format requirements for
that value set.
For example, if the value set allows only numeric characters, users can enter the value 456 (for a value set with maximum
length of three or more), but can't enter the value ABC. A format only value set doesn't otherwise restrict the range of
different values that users can enter. For numeric values, you can also specify if a numeric value should be zero filled or how
may digits should follow the radix separator.
Interdependent Value Sets

Use an independent value set to validate input against a list that isn't stored in an application table, and not dependent on a
subset of another independent value set.
You cannot specify a dependent value set for a given segment without having first defined an independent value set that you
apply to another segment in the same flexfield. Use a dependent value set to limit the list of values for a given segment based
on the value that the end user has chosen for a related independent segment. The available values in a dependent list and the
meaning of a given value depend on which value was selected for the independently validated segment.
209
Objects
For example, you could define an independent value set of U.S. states with values such as CA, NY, and so on. Then
you define a dependent value set of U.S. cities, with values such as San Francisco and Los Angeles that are valid for the
independent value CA, and New York City and Albany that are valid for the independent value NY. In the UI, only the valid
cities can be selected for a given state.
Because you define a subset value set from an existing independent value set, you must define the independent value set
first. End users don't need to choose a value for another segment first to have access to the subset value set.
Independent, dependent, and subset value sets require a customized 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 customize the Manage Value Sets page to capture additional attributes for each valid value by adding
context-sensitive segments in a new context for FND_VS_VALUES_B descriptive field.
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 vendor 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 flexfield saves the ID value, instead of the value from the value column, in the associated
flexfield 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 attribute of the underlying table. You should also define an ID column that is based
on an attribute that isn't language-dependent so that the value's invariant ID (an ID that doesn't change) is saved in the
transaction table. This allows the run time to display the corresponding translated text from the value column for the run time
session's locale.
Table validation lets you enable a segment to depend upon multiple prior segments in the same context structure. You
cannot reference other flexfield segments in the table-validated value set's WHERE clause. That is, the WHERE clause cannot
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.
Restriction
If you use table validated value sets for key flexfields, then you can't use all integration functionalities supported for
key flexfields, such as:
• Data security
• Oracle Transactional Business Intelligence (OTBI)
• Extended Spread Sheet Database (ESSbase)
• Tree or hierarchy integration
To use these integration functionalities for key flexfieds, you must use independent value sets only.
210
Objects
Range
In the case of format, independent, or dependent value sets, you can specify a range to further 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 flexfield
segment end users can view or modify.
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 filters or SQL predicates, and policies that associate roles with
conditions. You can use a filter for simple conditions. For more complex conditions, use a SQL predicate.
Value set data security policies and conditions differ from data security conditions and policies for business objects in the
following ways:
• You can grant only read access to end users. You cannot specify any other action.
• When defining a condition that is 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 define the table, such as &TABLE_ALIAS category=70.
When you enable security on table-validated value sets, the security rule that is defined 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 filter the value list to x, y and z from a list of x, y, z, xx, yy, zz. The data security rule
or filter written against the value set shouldn't assume anything about the bind variables; it must assume that the whole list
of values is available and write the rule, for example, to allow x, or to allow y and z. By default in data security, all values are
denied and show only rows to which access has been provided.
Testing and Maintenance

There is no need to define or maintain values for a table-validated value set, as the values are managed as part of the
referenced table or independent value set, respectively.
You cannot manage value sets in a sandbox.
When you change an existing value set, the deployment status for all affected flexfields changes to Edited. You must redeploy
all flexfields that use that value set to make the flexfields reflect the changes. In the UI pages for managing value sets, the
value set's usages show which flexfields are affected 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 cannot change this option if you decide to provide them later.
Planning Value Sets: Points to Consider

The value sets you create and configure depend on the valid values on the business object attributes that will use the value
set. When creating value sets, you first give the value set a name and description, and then define the valid values of the set.
The following aspects are important in planning value sets:
• List of values
211
Objects
• Plain text input
• Value ranges
• Value format specification
• Security
List of Values
You can use one of the following types of lists to specify the valid values for a segment:
• Table column
• Custom list
◦ Subset of custom list
• Dependent custom list
If the valid values exist in a table column, use a table value set to specify the list of values. To limit the valid values to a subset
of the values in the table, use a SQL WHERE clause. Table value sets also provide some advanced features, such as enabling
validation depending on other segments in the same structure.
Use an independent value set to specify a custom set of valid values. For example, you can use an independent value set
of Mon, Tue, Wed, and so forth to validate the day of the week. You can also specify a subset of an existing independent
value set as the valid values for a segment. For example, if you have an independent value set for the days of the week, then
a weekend subset can be composed of entries for Saturday and Sunday.
Use a dependent value set when the available values in the list and the meaning of a given value depend on which
independent value was selected for a previously selected segment value. For example, the valid holidays depend on which
country you are in. A dependent value set is a collection of value subsets, with one subset for each value in a corresponding
independent value set.
For lists of values type value sets, you can additionally limit the valid values that an end user can select or enter by specifying
format, minimum value, and maximum value. For list of values type value sets, you can optionally implement value set data
security. If the Oracle Fusion applications are running in different locales, you might need to provide different translations for
the values and descriptions.
Plain Text Input

Use a format-only value set when you want to allow end users to enter any value, as long as that value conforms to
formatting rules. For example, if you specify a maximum length of 3 and numeric-only, then end users can enter 456, but not
4567 or 45A. You can also specify the minimum and maximum values, whether to right-justify, and whether to zero-fill. With a
format-only value set, no other types of validation are applied.
Value Ranges
You can use either a format-only, independent, or dependent value set to specify a range of values. For example, you might
create a format-only value set with Number as the format type where the end user can enter only the values between 0 and
100. Or, you might create a format-only value set with Date as the format type where the end user can enter only dates for a
specific year, such as a range of 01-JAN-93 to 31-DEC-93. Because the minimum and maximum values enforce these limits,
you need not define a value set that contains each of these individual numbers or dates.
Value Format
Flexfield segments commonly require some kind of format specification, regardless of validation type. Before creating a value
set, consider how you will specify the required format.
212
Objects
The following table shows options for validation type and value data type.
Option Description
Value data type Character, Number, Date, Date Time.

Value subtype Text, Translated text, Numeric digits only, Time (20:08),
Time (20:08:08).

An additional data type specification for the Character
data type for the Dependent, Independent, and Format
validation types.

Maximum length Maximum number of characters or digits for Character

data type.

Precision Maximum number of digits the user can enter.

Scale Maximum number of digits that can follow the decimal

point.

Uppercase only Lowercase characters automatically changed to

uppercase.

Zero fill Automatic right-justification and zero-filling of entered

numbers (affects values that include only the digits 0-9).

Caution
You cannot change the text value data type to a translated text value subtype after creating a value set. If there is
any chance you may need to translate displayed values into other languages, choose Translated text. Selecting
the Translated text subtype doesn't require you to provide translated values.

Security
When enabling security on a value set, the data security resource name is an existing value set or one that you want to
create. The name typically matches the code value for the value set.
Restriction
You cannot edit the data security resource name after you save your changes.
213
Objects
Related Topics
• What's the difference between a lookup type and a value set?
Table-Validated Value Sets and Bind Variables: Points to

Consider
After you assign a value set to a flexfield, you can use bind variables in the WHERE clause.
The following bind variables refer to flexfield elements:
• :{SEGMENT.<segment_code>}
• :{CONTEXT.<context_code>;SEGMENT.<segment_code>}
• :{VALUESET.<value_set_code>}
• :{FLEXFIELD.<internal_code>}
• :{PARAMETER.<parameter_code>}
Segment Code
:{SEGMENT.<segment_code>}
This bind variable refers to the ID or value of a segment where <segment_code> identifies the segment. Where referring to the
ID, the value set is ID-validated. Where referring to the value, the value set isn't ID-validated. The data type of the bind value is
the same as the data type of the segment's column.
For both descriptive and extensible flexfields, the segment must be in the same context as the source segment. The source
segment contains the WHERE clause. For descriptive flexfields, if the segment is global, then the source segment must be
global.
The segment must have a sequence number that is less than the sequence number of the target segment with this bind
variable. A matching segment must exist in the current flexfield context.
This bind variable is useful when the set of valid values depends on the value in another segment. For example, the values
to select from a CITIES table might depend upon the selected country. If SEGMENT1 contains the country value, then the
WHERE clause for the CITIES table might be <country_code> = :{SEGMENT.SEGMENT1}.
Context Code
:{CONTEXT.<context_code>;SEGMENT.<segment_code>}
This bind variable, which is valid only for extensible flexfields, refers to the ID (if the value set is ID-validated) or value (if not ID-
validated) of a segment that is in a different context than the target segment (the segment with the WHERE clause).
• The <context_code> identifies the context and must be in the same category or in an ancestor category. It cannot be a
multiple-row context.
• The <segment_code> identifies the segment. The data type of the bind value is the same as the data type of the
segment's column.
Tip
The target segment should appear in the UI after the source segment to ensure the source segment has a value.
If the target segment's context is a single-row context, the source and target segments must be on separate
pages and the target page must follow the source page.
214
Objects
Note
The framework of extensible flexfields doesn't perform any additional validation related to mismatched values for
segments defined with cross context bind parameters. Administrators must populate the correct pair of segment
values.
This bind variable is useful when the set of valid values depends on the value of a segment in another context. For example,
the values to select from a CERTIFICATION table for a segment in the Compliance and Certification context might depend on
the value of the country segment in the Manufacturing context.
Value Set Code

:{VALUESET.<value_set_code>}
This bind variable refers to the ID (if the value set is ID-validated) or value (if not ID-validated) of the segment that is assigned
to the value set that is identified by the value_set_code. The data type of the bind value is the same as the data type of the
segment's column.
The segment must have a sequence number that is less than the sequence number of the segment with this bind variable.
If more than one segment is assigned to the value set, the closest prior matching segment will be used to resolve the bind
expression. A matching segment must exist in the current flexfield context.
This bind variable is useful when the set of valid values depends on the value in another segment and that segment code
can vary, such as when the value set is used for more than one context or flexfield. For example, the values to select from
a CITIES table might depend upon the selected country. If the value set for the segment that contains the country value is
COUNTRIES, then the WHERE clause for the CITIES table might be <county_code> = :{VALUESET.COUNTRIES}.
Flexfield Internal Code

:{FLEXFIELD.<internal_code>}
This bind variable refers to an internal code of the flexfield in which the value set is used, or to a validation date. The
internal_code must be one of the following:
• APPLICATION_ID - the application ID of the flexfield in which this value set is used. The data type of
APPLICATION_ID and its resulting bind value is NUMBER.
• DESCRIPTIVE_FLEXFIELD_CODE - the identifying code of the flexfield in which this value set is used. The data type
of DESCRIPTIVE_FLEXFIELD_CODE and its resulting bind value is VARCHAR2. Note that you use this string for both
descriptive and extensible flexfields.
• CONTEXT_CODE - the context code of the flexfield context in which this value set is used. The data type of
CONTEXT_CODE and its resulting bind value is VARCHAR2.
• SEGMENT_CODE - the identifying code of the flexfield segment in which this value set is used. The data type of
SEGMENT_CODE and its resulting bind value is VARCHAR2.
• VALIDATION_DATE - the current database date. The data type of VALIDATION_DATE and its resulting bind value is
DATE.
Flexfield Parameters
:{PARAMETER.<parameter_code>}
This bind variable refers to the value of a flexfield parameter where parameter_code identifies the parameter. The data type of
the resulting bind value is the same as the parameter's data type.
Note
You cannot assign a table value set to a context segment if the WHERE clause uses VALUESET.value_set_code
or SEGMENT.segment_code bind variables.
215
Objects
Table-Validated Value Set: Worked Example

In an application user interface, you want to display a list of values that allow customers to enter satisfaction scores. The value
column name is 1, 2, 3, 4, 5 and the value column description is Extremely Satisfied, Satisfied, and so on. Users can pick
the appropriate value or description which stores the corresponding name so the name value can be used in a calculation
expression.
In this case, you can use the FND_LOOKUPS table as the basis for a table-validated value set. The lookup meaning
corresponds to the Value Column Name and the lookup description corresponds to the Description Column Name. The
properties of the value set are as follows:
Property Value
FROM clause FND_LOOKUPS

WHERE clause lookup_type = 'CN_ XX_ CUST_ SATISFACT_ SCORE'

ID column lookup_code

Value column meaning

Description column description

Enable Flag column enabled_flag

Start Date column start_ date_active

End Date column end_ date_active

Order by display_ sequence

After completing this task, you should have created your customer satisfaction value set for the Incentive Compensation page
of your implementation project.
Creating a Value Set Based on a Lookup

1. From the Setup and Maintenance work area, find the Manage Value Sets task and click the Go to Task icon
button.
2. On the Manage Value Sets page, click the Create icon button.
3. On the Create Value Set page, enter the following values:
a. In the Value Set Code field, enter CN_XX_CUSTOMER_SATISFACTION_SCORES
216
Objects
b. In the Description field, enter Customer satisfaction score.
c. In the Module field, select Search....
d. In the Search and Select: Module subwindow, enter Incent in the User Module Name field
e. Select Incentive Compensation.
f. Click OK.
4. On the Create Value Set page, enter the following values:

a. In the Validation Type field, select Table.
b. In the Value Data Type field, select Character.
c. In the Definition section FROM Clause field, enter FND_LOOKUPS.
d. In the Value Column Name field, enter DESCRIPTION.
e. In the Description Column Name field, enter MEANING.
f. In the ID Column Name field, enter LOOKUP_CODE.
g. In the Enabled Flag Column Name field, enter 'Y'.
h. In the Start Date Column Name field, enter START_DATE_ACTIVE.
i. In the End Date Column Name field, enter END_DATE_ACTIVE.
j. In the WHERE Clause field, enter LOOKUP_TYPE = 'CN_XX_CUST_SATISFACT_SCORE'.

6. In the Manage Value Sets page, click Done.
Adding Attributes to the Manage Value Sets Page: Procedures

For independent, dependent, and subset value sets, you can add attributes to a value set. The attributes appear in the
Manage Value Sets UI for capturing additional information about each valid value, such as its purpose.
Typically, these attributes are used to capture internal information. To display attrbitues on an application page, you must
programmatically modify the application to access them.
1. Find the FND_VS_VALUES_B flexfield using the Manage Descriptive Flexfields task.
2. Open FND_VS_VALUES_B for editing.
3. Click Manage Contexts.
4. Create a new context and use the value set code for the context code.
5. Add the new attributes as context-sensitive segments.
217
Objects
6. Deploy FND_VS_VALUES_B to the run time.
7. Sign out and sign back in.
8. Open the Manage Value Sets page to view the new attributes.
Importing Value Set Values: Procedure

You can import a file containing values that you want to edit or add to a given independent or dependent value set.
For example, uploading a hundred values may be more efficient than creating them individually using the Manage Value Sets
task. However, for just a few values, it may be quicker to perform the relevant tasks.
Importing Value Set Values

To import value set values:
1. Create a flat file containing the values in the value set that you want to add or update.
Important
◦ When creating the file, you must specify an existing value set code to which you want to add values
or edit existing values. If the value set does not exist, add the value set using the appropriate Manage
Value Sets setup task in the Setup and Maintenance work area.
◦ The file that you create must adhere to the formatting and content requirements for creating flat files
containing value set values.
2. Upload the flat file to the content repository using the Files for Import and Export page.
3. Import the file using the appropriate Manage Value Sets setup task in the Setup and Maintenance work area. To
import the file:
a. Click Actions - Import in the Manage Value Sets page.
b. In the File Name field, enter the name of the flat file you uploaded using the Files for Import and Export page.
c. In the Account field, select the user account containing the flat file.
d. Click Upload.
Note
Alternatively, you can import the file using either of the following methods:
◦ Run the Upload Value Set Values scheduled process.
◦ Use the Applications Core Metadata Import web service. For more information on the Applications
Core Metadata Import web service, see assets with the ADF Service type in Oracle Enterprise
Repository for Oracle Fusion Applications (http://fusionappsoer.oracle.com).
218
Objects
Related Topics
• Files for Import and Export: Explained
Requirements for Flat Files to Upload Value Set Values:

Explained
You can import large volumes of value set value data from the content repository. To upload value set values to the content
repository, create a flat file containing the values in the value set that you want to add or update. You upload these flat files to
the content repository using the Files for Import and Export page.
General Requirements
The first line of the flat file must contain the column names for the value set value data, including all mandatory columns, and
separated by the '|' (pipe) character. Each subsequent line should contain a row of data specified in the same order as the
column names, also separated by the '|' character.
The requirements for creating flat files vary with the type of value sets:
• Independent value sets
• Dependent value sets
Independent Value Set

A flat file for uploading values for independent value sets must contain the following mandatory columns:
Column Name Data Type
ValueSetCode VARCHAR2(60)

Value VARCHAR2(150)

Enabled Flag VARCHAR2(1), Y or N

Note
You can also specify optional columns.
Examples:
• To upload values to a COLORS independent value set with the minimum columns, you can use the following flat file:
ValueSetCode | Value | EnabledFlag
COLORS | Red | Y
COLORS | Orange | Y
COLORS | Yellow | Y
219
Objects
• To upload values to a STATES independent value set with more (optional) columns, you can use the following flat file:
ValueSetCode | Value | Description | EnabledFlag
STATES | AK | Alaska | Y
STATES | CA | California | Y
STATES | WA | Washington | Y
Dependent Value Sets

A flat file for uploading values for dependent value sets must contain the following mandatory columns:
Column Name Data Type
Value Set Code VARCHAR2(60)

Independent Value VARCHAR2(150)

Value VARCHAR2(150)

Enabled Flag VARCHAR2(1), Y or N

Note
You can also specify optional columns.
Example:
To upload values to a CITIES dependent value set (dependent on the STATES independent value set), you can use the
following flat file:
ValueSetCode | IndependentValue | Value | EnabledFlag
STATES | AK | Juneau | Y
STATES | AK | Anchorage | Y
STATES | CA | San Francisco | Y
STATES | CA | Sacramento | Y
STATES | CA | Los Angeles | Y
STATES | CA | Oakland | Y
Additional Optional Columns

In addition to the mandatory columns, you can add the following optional columns for both dependent and independent value
sets:
Column Name Type
Translated Value VARCHAR2(150), for use in value sets that are

translatable

Description VARCHAR2(240)

220
Objects
Column Name Type
Start Date Active DATE, formatted as YYYY-MM-DD

End Date Active DATE, formatted as YYYY-MM-DD

Sort Order NUMBER(18)

Summary Flag VARCHAR2(30)

Flex Value Attribute1 ... Flex Value Attribute20 VARCHAR2(30)

Custom Value Attribute1 ... Custom Value Attribute10 VARCHAR2(30)

Related Topics
Upload Value Set Values Process

This process uploads a flat file containing value set values for flexfields. You can use this scheduled process to upload a
file containing values you want to edit or add to an existing independent or dependent value set. This process is useful for
adding or updating large volumes of value set value data in an automated or recurring fashion. For example, you can upload
a hundred values on a recurring basis when scheduled as a recurring process. This method may be more efficient than using
the one-time Import action in the Manage Value Sets tasks in the Setup and Maintenance work area. However, for an ad hoc
task of uploading a hundred values, it may be quicker to use the Import action in the relevant tasks.
Run this process from the Scheduled Processes Overview page. You can run it on a recurring basis whenever the flat file in
the content repository account is updated.
You must create the flat file containing the values data, and upload the flat file to the content repository using the Files for
Import and Export page.
Parameters
Flat File Name
Enter the name of the flat file you uploaded using the Files for Import and Export page.
Account
Select the user account containing the flat file in the content repository to upload.
Related Topics
221
Objects
• Scheduled Processes: Explained
Translating Flexfield and Value Set Configurations: Explained

When you first configure a flexfield or segment, the translatable text that you enter, such as prompts and descriptions, is
stored as the text for all installed locales. You may then provide a translation for a particular locale. If you don't provide a
translation for a given locale, then the value that was first entered is used for that locale.
To translate the text for a particular locale, log in with that locale or specify the locale by selecting Settings and Actions -
Personalization - Set Preferences in the global area. Then, update the translatable text in the flexfield using the Manage
Descriptive Flexfields task, Manage Key Flexfields task, or Manage Extensible Flexfields task. Your modifications change the
translated values only for the current session's locale.
After you complete the translations, deploy the flexfield.
You can define translations for a dependent value set or an independent value set, if it is of type Character with a subtype
of Translated text. You define the translations by setting the current session to the locale for which you want to define the
translation and using the Manage Value Sets task to enter the translated values and descriptions for that locale.
For a table value set for which the underlying table supports multiple languages and for which the value set's value column
is based on a translated attribute of the underlying table, you can define translated values using the maintenance task for
the underlying table. For more information on using multilanguage support features, see the Oracle Fusion Applications
Developer's Guide.
FAQs for Manage Project Portfolio Management Value Sets

What happens if a value set is security enabled?
Value set security is a feature that enables you to secure access to value set values based on the end user's role in the
system.
As an example, suppose you have a value set of US state names. When this value set is used to validate a flexfield segment,
and users can select a value for the segment, you can use value set security to restrict them to selecting only a certain state
or subset of states based on their assigned roles in the system.
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 Fusion
Applications data security.
How can I set a default value for a flexfield segment?

When you define or edit a flexfield segment, you specify a default value from the values provided by the value set assigned to
that segment.
You can set the default value for a descriptive flexfield segment to be a parameter, which means the entity object attribute to
which the chosen parameter is mapped provides the initial default value for the segment.
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 attribute's value every time the parameter
value changes. The parameter you choose identifies the entity object source attribute. Any changes in the value of the source
attribute during run time are reflected 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.
222
Objects
Define Flexfields
Flexfields: Overview
A flexfield is an extensible set of placeholder fields in application pages that are associated with a business object. Each
segment of the flexfield corresponds to a single application field, such as a segment of a key identifying a particular purchase,
or the components of a student's contact information, or the features of a product in inventory.
Using descriptive and extensible flexfields, you can extend business objects to capture data that wouldn't otherwise
be tracked by the application. If you need to add custom fields to a business object to meet your enterprise-specific
requirements, configure the flexfield to have one segment for each needed field.
Using key flexfields, you can configure intelligent key codes comprised of meaningful parts according to your business
practices. You configure the key flexfield to have one segment for each part that makes up your key code.
Flexfields let you meet enterprise requirements without changing the data model. Different data can be captured on the
same database table. Each segment captures a single atomic value, has a name, and maps to a pre-reserved column in the
application database.
You can use a flexfield to extend a business object if it has been registered for use on that object. Application developers
create a flexfield and register it so that it is available for configuration. Administrators and implementation consultants set up
or configure segments and other properties of the available flexfields. End users see flexfield segments as fields or attributes
of information displayed in the application user interface. They enter a value for the attribute. The value may be selected from
a list of valid values or entered as free-form text that complies with formatting rules.
The following aspects provide an overview of flexfields:
• Accessing flexfields and flexfield management tasks

• Types of flexfields
• Flexfield segments
• Value sets
• Structure and context
• Deployment
• Run time appearance
Accessing Flexfields and Flexfield Management Tasks

You can view flexfields on a page where they occur using the Highlight Flexfields feature. You can access flexfield
management tasks directly from a highlighted flexfield, through product-specific flexfield management tasks, or by starting in
the Setup and Maintenance Overview page which is available from the Navigator or the Administration menu.
For lists of flexfields, see assets with the Flexfield: Descriptive, Flexfield: Extensible, or Flexfield: Key type in Oracle Enterprise
Types of Flexfields
The following three types of flexfields are available in Oracle Fusion Applications and provide a means to customize
applications features without programming.
• Key
223
Objects
• Descriptive
• Extensible
For example, in Oracle Fusion Financials, key flexfields represent objects such as accounting codes and asset categories.
Generally, correct operations of a product depend on key flexfield setup. In Oracle Fusion Payables, a descriptive flexfield
lets you collect custom invoice details fields on an invoices page. You can implement these fields, which are descriptive
flexfield segments, as context-sensitive so they appear only when needed on a row-by-row basis when specific contextual
information is met. Extensible flexfields are similar to descriptive flexfields, but provide additional advanced features. Generally,
setup of descriptive and extensible flexfields is optional because their segments capture custom fields needed beyond the
predefined fields.
Segments
Each field that you configure using flexfields is a flexfield segment. Segments represent attributes of information. They can
appear globally wherever the flexfield is implemented, or based on a structure or context.
You define the appearance and meaning of individual segments when configuring a flexfield.
A key flexfield segment commonly describes a characteristic of the entity identified by the flexfield, such as a part number
structured to include information about the type, color, and size of an item. A descriptive flexfield segment represents an
attribute of information that describes a characteristic of the entity identified on the application page, such as details about a
device containing components, some of which are globally present on the page while others are contextually dependent on
the category of the device.
Value Sets
A value set is a named group of values that can be used to validate the content of a flexfield segment.
You configure a flexfield segment with a value set that establishes the valid values that an end user can enter for the segment.
You define the values in a value set, including such characteristics as the length and format of the values. You can specify
formatting rules, or specify values from an application table or predefined list. Multiple segments within a flexfield, or multiple
flexfields, can share a single value set.
Structure and Context

Key flexfields have structure. Descriptive flexfields and extensible flexfields have context.
Each key flexfield structure is a specific configuration of segments. Adding or removing segments, or rearranging their order,
produces a different structure. The database columns on which segments in different structures are based can be reused in
as many structures as desired.
Descriptive flexfield segments can be context-sensitive, which means available to an application based on a context value
rather than globally available wherever the flexfield appears. A descriptive flexfield context is a set of context-sensitive
segments that store information related to the same context value. You define contexts as part of configuring a descriptive
flexfield. End users see global segments, as well as any context-sensitive segments that apply to the selected context value.
Extensible flexfield segments are made available to an application based upon a category value. An extensible flexfield context
serves as a container for related segments, used to organize the various segments that are applicable to a category value.
You define contexts with context-sensitive segments and associate them to categories as part of configuring an extensible
flexfield. End users see the segments displayed in subregions, one for each context associated to the selected category
value.
In descriptive flexfields and extensible flexfields, the database columns on which context-sensitive segments are based can
be reused in as many contexts as desired.
Deployment
A flexfield must be deployed to display its current definition in a run time application user interface. For example, if the
deployment status is Edited, the flexfield segments may appear in the UI based on the flexfield definition at the time of last
deployment, rather than the current definition.
224
Objects
Run Time Appearance

In an application user interface, descriptive flexfield segments appear as label and field pairs or as a table of fields where the
column headers correspond to the labels. The fields represent the flexfield segments and accept entered input or a selection
from a list of choices that correspond to the segment's assigned value set. Extensible flexfield segments appear grouped
within labeled regions, where each grouping is a context and the region labels are the context names.
Use the Highlight Flexfields command in the Administration menu of the Setup and Maintenance work area to identify the
location of the flexfields on the run time page. Flexfields in highlight mode display:
• An Information icon button to access details about the flexfield
• A Configure Flexfield icon button to manage the flexfield
• Tools to add and edit flexfield segments for descriptive and extensible flexfields
All segments of a single flexfield are grouped together by default. The layout and positions of the flexfield segments depend
on where the application developer places the flexfield on the page. Flexfields may also be presented in a separate section of
the page, in a table, or on their own page or subwindow.
You can use Oracle Composer to edit the layout, position, or other display features of the flexfield segments.
Related Topics
• Key Flexfields: Explained
• Modules in Application Taxonomy: Explained
• Extensible Flexfields: Explained
Configuring Flexfields: Overview

Configuring a flexfield ranges from identifying the need for extending a business object with custom attributes to integrating
the custom attributes into the deployment. In the case of key flexfields, configuring the flexfield involves identifying value set
assignments and determining segment structures.
Overall Process for Configuring Custom Attributes

For descriptive and extensible flexfields, the overall configuration process involves the following:
1. Use the Highlight Flexfields feature from the Administration menu to find flexfields on pages associated with
business objects.
2. Plan the flexfield configuration.
3. Plan flexfield validation.
4. Define the attributes by configuring the flexfield segments.
a. Use the Manage Extensible Flexfields or Manage Descriptive Flexfields tasks, or use the Configure Flexfield
icon button directly on the page where the flexfield is highlighted. For simple configurations, use the Add
225
Objects
Segment, Add Context Value, and Edit Segment icon buttons directly on the page where the flexfield is
highlighted.
b. Optionally, validate the flexfield configuration.
c. Optionally, deploy the flexfield to a sandbox for initial testing.
5. Deploy the flexfield to the mainline to display the custom attributes on the application pages and to make them
available for integration with other tools such as Oracle Business Intelligence.
6. Perform the necessary steps to integrate the custom attributes into the technology stack.
A simple configuration is limited to such actions as adding a format-only field or adding a field with a basic list of values.
Overall Process for Configuring Custom Keys

For key flexfields, the overall configuration process involves the following:
business objects.
3. Plan the flexfield validation.
4. Define the value sets before configuring the key flexfield segments by going to the Manage Value Sets task.
5. Define the key flexfield structures and their segments, and define structure instances for each structure.
a. Use the Manage Key Flexfields task or the Configure Flexfield icon button directly on the page where the
flexfield is highlighted.
6. Deploy the flexfield to the mainline to display it on the application pages and to make it available for integration with
other tools such as Oracle Business Intelligence.
7. Perform the necessary steps to integrate the flexfield into the technology stack.
Related Topics
226
Objects
Flexfields at Run Time: Explained

Many business objects in Oracle Fusion applications have an associated descriptive or extensible flexfield with which you
can create custom attributes for the business object. Some business objects have an associated key flexfield for configuring
flexible multiple part keys.
The following aspects are important in understanding flexfields at run time:
• Finding flexfields on a page
• Why no flexfields are on a page
Finding Flexfields on a Page

At run time, the custom attributes you define as extensible and descriptive flexfield segments appear in the application page
just like any other attribute. Key flexfields typically appear in the application page as a field with a key flexfield icon, where the
field's value is actually a collection of segments. In some pages, one or more key flexfield segments may be displayed in the
page like any other attribute. Thus, when viewing the page in standard mode, in many cases you may not be able to discern
which fields are flexfield segments, or whether flexfields are available to configure on the page.
Use the Highlight Flexfields feature to render the page in a special mode that lets you view:
• Where, if any, flexfields are available on your page
• Which, if any, of the fields on your page are flexfield segments rather than out-of-the-box fields
To obtain information about the flexfields on a page, open the page and choose Highlight Flexfields from the
Administration menu. Hover over the Information icon button next to the highlighted fields to display information about
the flexfield. Choose Unhighlight Flexfields from the Administration menu when you no longer want to see the highlighted
flexfields.
When you click the Configure Flexfield icon button for a highlighted flexfield, the applicable Manage Flexfields task is
displayed for that flexfield. For simple configurations of descriptive and extensible flexfields, you can click the Add Context
Value icon button to add a context value, or click the Add Segment or Edit Segment icon buttons to add or edit a global
segment or a context-sensitive segment that doesn't require advanced configuration.
Restriction
Not all flexfields are available for creating custom attributes. For example, some flexfields are protected, and you
either can't edit their configurations at all, or can do only limited changes to them. Consult the product-specific
documentation in Oracle Fusion Applications Help to verify whether there are any restrictions on using the flexfield.
Why No Flexfields Are on a Page

For a flexfield to be available in the page, it must be registered by developers. If a flexfield is available, you may configure
segments. The segments appear on the page only after you have successfully deployed the flexfield. For information about
registering flexfields, see the Oracle Fusion Applications Developer's Guide. Some business objects haven't been designed
to support flexfields. For information about how to enable business objects with flexfield capability, see Getting Started with
Flexfields in the Oracle Fusion Applications Developer's Guide.
Note
Oracle Sales Cloud doesn't support flexfields.
To add custom attributes to these applications, use Application Composer. For more information, see the "Editing an Object:
Explained" section in Oracle Sales Cloud: Extending Sales.
227
Objects
Customizing Flexfields Using Page Composer: Explained

Using Page Composer, you can create customizations to flexfields that are specific to a page.
In Page Composer, to customize:
• Extensible flexfields, open the page in Source view, and look for a region that is bound to an
EffContextsPageContainer task flow. This is the container for the extensible flexfield attributes and contexts. To view
the flexfield code and identifying information, open the properties panel for the region. To customize any component
within the region, select the desired tag and click Edit.
• Descriptive flexfields, open the page in Source view, and look for <descriptiveFlexfield> elements. Open the properties
panel for the element to view the flexfield code and identifying information. Within the properties panel, you may
customize properties for the global and context-sensitive segments or re-order the segments on the page.
Accessing Flexfield Management Tasks: Procedures

You can configure and manage flexfields by highlighting them on an application page and using the available on-screen
configuration tools. Alternatively, you can access product-specific flexfield tasks or global flexfield management tasks.
Accessing Flexfield Management Tasks through the Run time Page

You can identify flexfields on the run time application page where they are implemented.
1. Navigate to an application page.

2. Choose Highlight Flexfields from the Administration menu in the global area of Oracle Fusion Applications.
3. View the available flexfields highlighted on the page. If any of the fields on the page are custom fields configured as
part of a flexfield, they also appear highlighted.
4. To edit a flexfield, use the:
◦ Configure Flexfield icon button to access the flexfield management task pages for extensive configuration to
the flexfield and its segments.
◦ Add Segment icon button to access the subwindow for adding segments with limited configuration to
◦ Edit Segment icon button to access the subwindow for limited configuration changes to descriptive and
extensible flexfield segments.
Accessing Flexfield Management Tasks through Setup and Maintenance

Manage flexfields using tasks you access by starting in the Setup and Maintenance Overview page which is available from the
Navigator or the Administration menu.
To access tasks for configuring flexfields and value sets, you must be provisioned with roles that entitle you to access the
Define Flexfields task list or tasks for managing product-specific flexfields. Contact your security administrator for details. For
information about product-specific flexfield tasks, such as Manage Purchasing Descriptive Flexfields, consult the product-
specific documentation in Oracle Fusion Applications Help
To access the flexfield management tasks and search for existing flexfields, perform the following steps:
1. Choose Setup and Maintenance from the Administration menu in the global area of Oracle Fusion Applications.
2. Search for Define Flexfields in the All Tasks tab.
228
Objects
Tip
◦ Use the Business Object parameter to search:
• Application Key Flexfields, Application Descriptive Flexfields, and Application Extensible Flexfields
to find all tasks related to flexfields.
• Application Flexfield Value Set to find all tasks related to value sets.
◦ To manage any:
• Flexfield across all Oracle Fusion Applications products, search for the Define Flexfields task list
and access the Manage Descriptive Flexfields, Manage Extensible Flexfields, and Manage Key
Flexfields tasks.
• Value set across all Oracle Fusion Applications products, search for the Define Flexfields task list
and access the Manage Value Sets task.
Restriction
If you are configuring key flexfields, search for and access the Manage Value Sets task to set up value
sets before accessing the Manage Key Flexfields task.
3. Expand the task list to view the included tasks.
4. Click the Task icon button to open the manage flexfield pages.
5. Search for all or specific flexfields.
6. In the search results, select the flexfield.
7. Use the Edit action to open pages for viewing and configuring the flexfield. Access to managing value sets is
available within the tasks for managing descriptive and extensible flexfields.
Note
Access to managing value sets is:
• Available within the tasks for managing descriptive and extensible flexfields.
• Not available within the tasks for managing key flexfields. Therefore, configure value sets prior to configuring your
key flexfield.
229
Objects
Flexfields and Oracle Fusion Application Architecture: How

They Work Together
Administrators configure flexfield segments to capture data that represents the values of attributes. Flexfield segments
represent attributes of entities (business objects). Most business objects are enabled for descriptive flexfields. Some business
objects are enabled for extensible flexfields.
For example, an airline manufacturer might require very specific attributes for their orders that aren't provided by the out-
of-the-box implementation of an order. Because a flexfield exists for the order business object, you can use it to create and
configure the desired attribute.
The figure shows the layers of a flexfield: the business entity table and metadata in the database, business components
that are Application Development Framework (ADF) objects or ADF business component (ADFbc) objects derived from the
metadata and stored in Oracle Metadata Services (MDS) Repository, and the user interface where the input fields defined
230
Objects
by the flexfield segments are rendered. The flexfield definition consists of all the metadata defined during configuration and
stored in the database.
Application developers create a flexfield and register it so that it is available for configuration. Administrators and
implementation consultants configure segments and other properties of the available flexfields. This information is stored
as additional flexfield metadata in the database. Deploying the flexfield generates ADF business components based on the
flexfield metadata in the database.
The following aspects are important in understanding how flexfields and Oracle Fusion Applications architecture work
together:
• Integration
• Deployment
• Import and Export
231
Objects
• Run time
• Patching
Integration
The attributes that you add by configuring flexfields are available throughout the Oracle Fusion Middleware technology
stack, allowing the flexfields to be used in user interface pages, incorporated into the service-oriented architecture (SOA)
infrastructure, and integrated with Oracle Business Intelligence. You identify flexfield segments for integration by the
segment's Application Programming Interface (API) name.
A flexfield affects the Web Services Description Language (WSDL) schemas exposed by ADF services and used by SOA
composites. The Web services that expose base entity data also expose flexfield segment data.
Attributes incorporate into SOA infrastructure (BPEL, Rules) and integrate with business intelligence (Oracle Business
Intelligence, Extended Spread Sheet Database (ESSbase)).
Flexfield configurations are preserved across Oracle Fusion Applications updates.
Deployment
The metadata for the flexfield is stored in the application database as soon as you save your configuration changes.
Deploying the flexfield generates the ADF business components so that the run time user interface reflects the latest definition
of the flexfield in the metadata.
Importing and Exporting

You can export and import flexfields with a deployment status of Deployed or Deployed to Sandbox across instances of
Oracle Fusion Applications using the Setup and Maintenance Overview page. Ensure a flexfield is eligible for migration (by
verifying that it has successfully deployed) prior to attempting the migration.
Run time
For a flexfield to reflect the latest flexfield definition at run time it must be deployed. The user interface accesses a business
object and the deployed flexfield definition indicates which business object attributes the flexfield captures values for. If you
add display customizations for a flexfield using Oracle Composer, these are customizations on the page so that the same
flexfield segments can appear differently on various different pages.
Values entered for segments are validated using value sets.
Patching
Flexfield configurations are preserved during patching and upgrading.
Flexfields and Value Sets: Highlights

Before you use flexfields to create custom attributes, you should be familiar with the Oracle Fusion application architecture
that enables customization, customization layers, and the customization lifecycle.
In addition to the extensive information in the Oracle Fusion Applications Help about configuring flexfields that are already
available for configuration, consider the resources below for adding flexfields to business components and alternatives to
flexfields where flexfields cannot be enabled.
To assess the flexfields available in a deployment of Oracle Fusion Applications, see assets of type: flexfield in the Oracle
Enterprise Repository at http://fusionappsoer.oracle.com.
For customization not available through the tasks and user interface pages available in Oracle Fusion Applications, contact
My Oracle Support at http://www.oracle.com/pls/topic/lookup?ctx=acc=info or visit http://www.oracle.com/pls/topic/lookup?
ctx=acc=trs if you are hearing impaired.
232
Objects
Restriction
Don't use Oracle JDeveloper to customize flexfields.
Before Configuring Flexfields

You can add custom attributes to a business object using a flexfield, if a flexfield has been registered for that object by
developers.
• For Oracle Sales Cloud, use Application Composer to add custom attributes instead of using descriptive and
extensible flexfields.
Deploying Flexfields
• For information about synchronizing the updated XML schema definition (XSD) files in Oracle Metadata Services
(MDS) Repositories for each service-oriented architecture (SOA) application, refer to the Oracle Fusion Applications
Developer's Guide.
See: Customizing SOA Composite Applications
◦ Oracle ADF services used by SOA composites expose the Web Services Description Language (WSDL)
schemas where deployed flexfields are stored.
Oracle Business Intelligence

• For information about importing business intelligence-enabled flexfield changes into the Oracle Business Intelligence
repository, refer to the Oracle Transactional Business Intelligence Administrator's Guide.
See: Designating Flexfields as BI-Enabled
See: Importing Changes to Flexfields Automatically
Related Topics
• Exporting and Moving Customizations: Points to Consider
• Defining Fields: Explained
Manage Flexfields
Managing Flexfields: Points to Consider
Managing flexfields involves registering, planning, and configuring flexfields.
You plan and configure the registered flexfields provided in your applications by applications developers. How you configure
flexfield segments determines how the flexfield segments appear to end users. Optionally, you can customize the UI page to
change how the flexfield segments appear to end users on that page.
The figure shows the processes involved in making flexfields available to end users. The tasks in the Define Flexfields activity
let administrators configure and deploy flexfields. If you deploy a flexfield to a sandbox and decide to apply the configuration
233
Objects
to the mainline, select the flexfield in the Manage Flexfields tasks of the Define Flexfields activity and deploy the flexfield in the
mainline so that it is available to users.
Consider the following aspects of managing flexfields:
• Registering flexfields
• Planning flexfields
• Configuring flexfields
• Enabling a flexfields segment for business intelligence
• Deploying flexfields
• Optionally changing a flexfield segment's appearance in a user interface page
234
Objects
• Identifying flexfields on a run time page and troubleshooting
Registering Flexfields
Application development registers flexfields so they are available to administrators and implementation consultants for
configuration.
As part of registering a flexfield, application development reserves columns of entity tables for use in flexfields so an enterprise
can capture segments to meet their business needs. Many flexfields are registered in Oracle Fusion Applications.
A flexfield must be registered before it can be configured.
For more information on registering flexfields, see Oracle Fusion Applications Developer's Guide.
Planning Flexfields
Before you begin planning flexfields, determine what type is appropriate to your needs, and which business objects are
available for customizing flexfields.
All flexfields consist of segments which represent attributes of an entity. The values an end user inputs for an attribute are
stored in a column of the entity table.
Carefully plan flexfields before configuring them. Before configuring new segments for your flexfields, be sure to plan their
implementation carefully.
If you have determined that a business object supports flexfields, and those flexfields have been registered, you can begin
planning how to configure the flexfield for your needs. Note the code name of the flexfield you intend to configure so you can
find it easily in the Define Flexfield activity.
In some cases you can customize how the flexfield appears on the page.
See Oracle Fusion Applications Help for specific products to determine any restrictions on using product-specific flexfields.
Configuring Flexfields
Administrators or implementers configure flexfields so they meet the needs of the enterprise. Some flexfields require
configuration to make an application operate correctly.
You can configure flexfields using the following methods:
• Go to the manage flexfield tasks in the Setup and Maintenance work area.
• Use the Highlight Flexfields command in the Administration menu while viewing a run time page.
◦ Use the Configure Flexfield icon button to manage all aspects of a flexfield, such as change a segment's
sequence number, or configure a flexfield segment's business intelligence label.
◦ Use the Add Segment and Edit Segment icon buttons to add and edit descriptive or extensible flexfield
segments with simple configurations.
◦ Use the Add Context icon button to add descriptive or extensible flexfield context values.
Configuring a flexfield includes the following:
• Defining value sets against which the values entered by end users are validated
• Defining the structure or context of the segments in the flexfield
235
Objects
• Specifying the identifying information for each segment
• Specifying the display properties such as prompt, length and data type of each flexfield segment
• Specifying valid values for each segment, and the meaning of each value within the application
Tip
You can create value sets while creating descriptive and extensible flexfield segments. However, define value sets
before configuring key flexfield segments that use them, because you assign existing value sets while configuring
key flexfield segments.
When creating table-validated, independent, dependent, or subset value sets while creating descriptive and extensible
flexfield segments, you can optionally specify to display the description of the selected value to the right of the segment at run
time.
You can assign sequence order numbers to global segments and to context-sensitive segments in each context. Segment
display is always in a fixed order based on the segments' sequence numbers. You cannot enter a number for one segment
that is already in use for a different segment.
Tip
Consider numbering the segments in multiples, such as 4, 5, or 10, to make it easy to insert new attributes.
A flexfield column is assigned to a new segment automatically, but you can change the assignment before saving the
segment. If you need to set a specific column assignment for a segment, create that segment first to ensure that the intended
column isn't automatically assigned to a different segment.
Enabling a Flexfield Segment for Business Intelligence

You can enable flexfield segments for business intelligence if the flexfield is registered in the database as an Oracle Business
Intelligence-enabled flexfield. For more information on enabling segments for business intelligence, see points to consider
when enabling descriptive, extensible, and key flexfield segments for business intelligence.
For extensible flexfield segments, you can't assign labels to equalize segments across contexts that are semantically
equivalent.
Once you have configured a flexfield,, you must deploy it to make the latest definition available to run time users.
In the Define Flexfields tasks, you can deploy a flexfield using either of the following commands:
• The Deploy Flexfield command to deploy a flexfield to mainline. This is for general use in a test or production
environment.
• The Deploy to Sandbox command to deploy a flexfield to sandbox. This is to confirm that the flexfield is correctly
configured before deploying it to the mainline.
In Highlight Flexfields mode, when using the:
• Add Context, Add Segment, and Edit Segment tools for extensible flexfields, use the Save command to save
your changes, and then use the Deploy command to deploy the flexfield to mainline
• Add Segment and Edit Segment tools for descriptive flexfields, use the Save and Deploy command to save your
changes and deploy the flexfield to mainline
Once deployed, the deployment status indicates the state of the currently configured flexfield relative to the last deployed
definition.
236
Objects
Optionally Changing a Flexfield Segment Appearance

The flexfield attributes that you define integrate with the user interface pages where users access the attributes' business
object. Application development determines the UI pages where business objects appear and the display patterns used by
default to render flexfield segments.
After a flexfield has been deployed to the mainline Oracle Metadata Services (MDS) Repository so that it appears on
application pages, you can customize it on a per-page basis using Page Composer. For example, you can hide a segment,
change its prompt or other properties, or reorder the custom global attributes so that they are interspersed with the core
attributes in the same parent layout.
You can only customize the appearance of descriptive and extensible flexfield segments in the UI page using Pge Composer
once the flexfield is deployed to the mainline.
If the Oracle Fusion applications are running in different locales, you can provide different translations for translatable text,
such as prompts and descriptions. Enter translations by signing in using the locale that requires the translated text. You do
this by selecting Settings and Actions - Personalization - Set Preferences in the global area and changing the text to
the translated text for that locale.
Identifying Flexfields on a Run Time Page

The Highlight Flexfields command in the Administration menu of the Setup and Maintenance work area identifies the
location of flexfields on the run time page by displaying an Information icon button for accessing details about each flexfield.
Even if a descriptive or extensible flexfield hasn't yet been deployed and no segments appear on the run time page in normal
view, the flexfield appears in the Highlight Flexfield view for that page. In the case of:
• Descriptive flexfields, the segments as of the last deployment appear
• Extensible flexfields, any segments and contexts that have been saved but not yet deployed also appear as disabled
Highlight Flexfields accesses the current flexfield metadata definition.

Use the highlighted flexfield's Configure Flexfield icon button to manage flexfields directly. Alternatively, note a highlighted
flexfield's name to search for it in the tasks for managing flexfields.
For more information on creating flexfields and adding them to a UI page, see the Oracle Fusion Applications Developer's
Guide.
For more information about customizing flexfield segment appearance with Oracle Composer, see guidance on customizing
existing pages in the Oracle Fusion Applications Extensibility Guide.
Related Topics
• Managing Extensible Flexfields: Points to Consider
• Managing Key Flexfields: Points to Consider
Flexfield Segment Properties: Explained

Independent of the value set assigned to a segment, segments may have properties that affect how they are displayed and
how they behave.
The following aspects are important in understanding
• Display properties
• Properties related to segment values
237
Objects
• Properties related to search
• Range validation segments
• Rule validation of segment values
• Naming conventions
Display Properties
The following table summarizes display properties.
Property Description
Enabled Whether the segment can be used.

Sequence The order the segment appears in relation to the other

configured segments.

Prompt The string to be used for the segment's label in the user
interface.

Display type The type of field in which to display the segment.

Checked and unchecked values If the display type is check box, the actual values to
save. For example, Y and N or 0 and 1.

Display size The character width of the field.

Display height The height of the field as measured in visible number of

lines when the display type is a text area.

Read only Whether the field should display as read-only, not

editable text.

Description help text The field-level description help text to display for the
field. Use description help text to display a field-level
description that expands on or clarifies the prompt
provided for the field.

If description help text is specified, a Help icon button
is displayed next to the field in the run time application.
The description help text is displayed when the user
hovers over the Help icon button.

Instruction help text The field-level instruction help text to display for the field.
238
Objects

Use instruction help text to provide directions on
using the field. If instruction help text is specified, it is
displayed in an in-field help note window that appears
when users give focus to or hover over the field.

Properties Related to Search

Extensible flexfield segments can be marked as selectively required in search using the indexed property. The indexed
property requires end users to enter a value before conducting a search on the attribute represented by the indexed segment.
A database administrator must create an index on the segment column representing the indexed attribute.
Range Validation of Segments

Range validation enables you to enforce an arithmetic inequality between two segments of a flexfield. For example, a product
must be ordered before it can be shipped. Therefore, the order date must be on or before the ship date, and consequently
the order date segment value must be less than or equal to the ship date segment value. You can use range validation to
ensure this relationship.
The conditions for range validation are as follows:
• Segments must be configured for range validation in pairs, one with the low value and one with the high value.
• Both segments must be of the same data type.
• Both segments must be parts of the same structure in a key flexfield or parts of the same context in a descriptive
flexfield or extensible flexfield.
• The low value segment must have a lower sequence number than the high value segment.
• Non-range validated segments can exist between a range validated pair, but range validated pairs cannot overlap or
be nested.
You can configure as many range validated pairs as you want within the same flexfield. Your application automatically detects
and applies range validation to the segment pairs that you define, in sequence order. It must encounter a low value segment
first, and the next range validated segment that it encounters 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.
Rule Validation of Segment Values

Validation rules on descriptive and extensible flexfield segments determine how an attribute is validated. The value entered for
an attribute on a business object may need to match a specified format or be restricted to a list of values. Use a value set to
specify the validation rules.
Value set validation is required for global segments and context-sensitive segments, and optional for context segments. In
the case of context segments, the application may validate an input value instead of the value set validating the input value
against the context segment. However the application input values must match exactly the valid context segment 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.
When you configure a descriptive flexfield segment, you can specify a constant to use for setting 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 end users. The API
name is used to identify the segment in various integration points including web services, rules, and business intelligence.
239
Objects
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 permitted. You can't change the API name after the segment has been created.
Related Topics
Flexfields Segments: How They Are Rendered

Flexfield segments appear on pages as attributes of business objects.
Settings That Affect Flexfield Segment Display

When you configure flexfield segments, the value you enter for the segment's display type determines how the segment
appears on the run time page.
How Display Type ValuesAppear

The figure shows how display types appear at run time.
In the following figure, identify the display type by letter when referring to the table of descriptions for check box, drop-down
list, list of values, pop-up list of values, and radio button group.
240
Objects
In the following figure, identify the display type by letter when referring to the table of descriptions for radio button group, text
area, text box, date/time, and rich text editor.
The table describes each display type. The Example column refers to the figures above.
Display Type Example Description
Check Box A The field is displayed as a check

box. If the end user selects the
checkbox, the checked value is
used. Otherwise, the unchecked
value is used.

241
Objects
Drop-down List B The field displays a dropdown list of

values from which the end user can
select a value.

List of Values C The field displays a dropdown list of

select a value. The user can also
click Search to find more values.

Pop-up List of Values D The field displays as a text field

with a Search icon button. The end
users can type a value in the text
field or they can click the Search
icon button to open a subwindow
for searching.

Radio Button Group E The field is displayed as a set of

radio buttons. The end user can
select one button. Selecting a
button deselects any previously
selected button in the set.

Text Area F The field is displayed as a text area

in which the end user can type
multiple lines of text. The display
width and height specify the visible
width and number of lines in the
text area, respectively.

Text Box G The field is displayed as a text field

in which the end user can type a
single line of text. The display width
controls the width of the text box.

Date/Time H The field enables the end user to

enter a date if the data type is Date,
or a date and time if the data type
is Date Time. The user can select
the date from a calendar. If the data
type is Date Time, the field also
displays fields for specifying the
hour, minutes, seconds, AM or PM,
and time zone.

242
Objects
Rich Text Editor I The field is displayed as a text

area in which the end user can
enter and edit multiple lines of
formatted text. The display width
and height specify the visible width
and number of lines in the rich text
editor, respectively.

Restriction
This display type is
available for extensible
flexfields only.

Hidden The field isn't displayed.

Flexfields and Value Sets: How They Work Together

Value sets are specific to your enterprise. When gathering information using flexfields, your enterprise's value sets validate the
values that your users enter based on how you defined the value set.
You can assign a value set to any number of flexfield segments in the same or different flexfields. Value set usage information
indicates which flexfields use the value set.
The following aspects are important in understanding how flexfields and value sets work together:
• Defining value sets
• Shared value sets
• Deployment
Defining Value Sets

As a key flexfield guideline, define value sets before configuring the flexfield, because you assign value sets to each segment
as you configure a flexfield. With descriptive and extensible flexfields, you can define value sets when adding or editing a
segment.
Caution
Be sure that changes to a shared value set are compatible with all flexfield segments that use the value set.
Shared Value Sets

When you change a value in a shared value set, the change affects the value set for all flexfields that use that value set. The
advantage of a shared value set is that a single change propagates to all usages. The drawback is that the change shared
across usages may not be appropriate in every case.
Value Set Values

To configure custom attributes to be captured on the value set values screen in the Manage Value Sets task, configure the
Value Set Values descriptive flexfield. The object's code is FND_VS_VALUES_B.This flexfield expects the context code to
correspond to the value set code. For each value set, you can define a context whose code is the value set code, and whose
243
Objects
context-sensitive segments will be shown for the values of that value set. By default the context segment is hidden since it
defaults to the value set code and is not expected to be changed.
You can also define global segments that will be shown for all value sets. However, this would be quite unusual since it would
mean that you want to capture that attribute for all values for all value sets.
Deployment
When you deploy a flexfield, the value sets assigned to the segments of the flexfield provide end users with the valid values for
the attributes represented by the segments.
Defaulting and Deriving Segment Values: Explained

To populate a flexfield segment with a default value when a row is created, specify a default type of constant or parameter
and a default value.
To synchronize a segment's value with another field's value whenever it changes, specify the derivation value to be the
flexfield parameter from which to derive the attribute's value. Whenever the parameter value changes, the attribute's value is
changed to match. If you derive an attribute from a parameter, consider making the attribute read-only, as values entered by
users are lost whenever the parameter value changes.
When defaulting or deriving a default value from a parameter, only those attributes designated by development as parameters
are available to be chosen.
Different combinations of making the segments read only or editable in combination with the default or derivation value or
both, have different effects.
Initial run time behavior corresponds to the row for the attribute value being created in the entity table. If the default value is
read only, it cannot 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-modified segment value is overwritten when the derivation value
changes.
Default Type Default value Derivation value Initial run time Run time
specified? specified? behavior behavior after
parameter
changes
None No Yes No initial segment The changed

value parameter
derivation value
updates segment
value

Constant Yes No Default segment N/A

value

Constant Yes Yes Default segment The changed

value parameter
derivation value
updates segment
value

244
Objects
parameter
changes
Parameter Yes No The default N/A

segment value is
the parameter's
default value

Parameter Yes Yes, and same as The default The changed

default value segment value is parameter
the parameter's derivation value
default and updates segment
derivation value value

Parameter Yes Yes, and different The default The changed

from default value segment value is parameter default
the parameter's value doesn't
default value update segment
value. Only the
changed derivation
value updates the
segment value.

Flexfield Usages: Explained

Usage affects various aspects of flexfields. The usage of the flexfield is set when the flexfield is registered and specifies the
application and table with which the flexfield is associated.
Entity usage indicates the table containing the segments of a flexfield.
A flexfield can have multiple usages. The first table registered for a flexfield is the master usage. Segments are based on the
master usage, and other usages of the same table for the same flexfield use the same segment setup, though the column
names optionally may have a differentiating prefix.
Extensible Flexfields
You can configure different behavior for extensible flexfield contexts at the usage level. The usage of an extensible flexfield
context determines in which scenarios or user interfaces the segments of a context appear to end users. For example, if a
Supplier page displays an extensible flexfield's supplier usage and a buyer page displays that same extensible flexfield's buyer
usage, a context that is associated to the supplier usage but not the buyer usage displays only on the supplier page and not
the buyer page.
245
Objects
Value Sets
The usage of value sets specifies the flexfields having segments where the value set is assigned.
FAQs for Manage Flexfields

Why can't I edit my flexfield or value set configuration?
Your flexfield or value set configuration may be protected. Application developers mark some configurations as protected,
indicating that you can't edit them.
Some examples of configurations that may be protected are:
• Descriptive flexfields
• Extensible flexfield contexts
• Extensible flexfield pages
• Value sets
Why did my flexfield changes not appear in the run time UI?
The ADF business components or artifacts of a flexfield, which are generated into an Oracle Metadata Services (MDS)
Repository when the flexfield is deployed, are cached within a user session. You must sign out and sign back in again to view
flexfield definition changes reflected in the run time application user interface page.
A flexfield's deployment status indicates whether the flexfield segments as currently defined in the metadata are available
to end users. The flexfield segments seen by end users in the run time correspond to the flexfield definition that was last
deployed successfully.
How can I enable flexfield segments for Oracle Social Network Cloud Service?
Descriptive flexfield segments can be enabled for integration with Oracle Social Network Cloud Service. When you manage
Oracle Social Network Objects during setup and maintenance, search for the business object that includes descriptive
flexfields, and select the business object attributes that are defined as flexfield segments.
Deploy Flexfields
Flexfield Deployment: Explained
Deployment generates or refreshes the Application Development Framework (ADF) business component objects that
render the flexfield in a user interface. The deployment process adds the custom attributes to the Web Services Description
Language (WSDL) schemas that are exposed by Oracle ADF services and that are used by SOA composites. Flexfields are
deployed for the first time during the application provisioning process. After you configure or change a flexfield, you must
deploy it to make the latest definition available to end users.
If a descriptive flexfield is enabled for business intelligence, the deployment process redeploys the flexfield's business
intelligence artifacts.
You can deploy a flexfield to a sandbox for testing or to the mainline for use in a test or production run time environment. You
can deploy extensible flexfields as a background process.
After deployment, the custom attributes 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 custom attributes. You must
sign out and sign back in to Oracle Fusion Applications to see the changes you deployed in the run time.
246
Objects
The following aspects are important in understanding flexfield deployment:
• Deployment Status
• Initial Deployment Status
• Metadata Validations
• Metadata Synchronization
• Deployment as a Background Process
• Export of Artifacts from Flexfield MDS
Deployment Status
Every flexfield has a deployment status.
A flexfield can have the following deployment statuses:
Deployment Status Meaning
Edited The flexfield metadata definition hasn't been deployed

yet. Updates of the metadata definition aren't applied in
the run time environment yet.

Patched The flexfield metadata definition has been modified

through a patch or through a data migration action, but
the flexfield hasn't yet been deployed so the updated
definition isn't reflected in the run time environment.

Deployed to Sandbox The current metadata for the flexfield is deployed in ADF
artifacts and available as a flexfield-enabled sandbox.
The status of the sandbox is managed by the Manage
Sandboxes task available to the Administrator menu of
the Setup and Maintenance work area.

Deployed The current metadata for the flexfield is deployed in ADF

artifacts and available to end users. There haven't been
any changes to the flexfield since it was last deployed in
the mainline.

Error The deployment attempt in the mainline failed.

Note
Whenever a value set definition changes, the deployment status of a flexfield that uses that value set changes to
edited. If the change results from a patch, the deployment status of the flexfield changes to patched.
247
Objects
Initial Deployment Status of Flexfields

The Oracle Fusion Applications installation loads flexfield metadata into the database. This initial load sets the flexfield status
to Edited. The application provisioning process during installation deploys the flexfields of the provisioned applications, which
sets their status to Deployed if no errors are encountered.
When accessing a provisioned application, deployed flexfields are ready to use. In some cases, flexfield availability at run time
requires setup, such as defining key flexfields.
Metadata Validation
Use the Validate Metadata command to view possible metadata errors before attempting to deploy the flexfield. Metadata
validation is the initial phase of all flexfield deployment commands. By successfully validating metadata before running the
deployment commands, you can avoid failures in the metadata validation phase of a deployment attempt. The deployment
process aborts if it encounters an error during the metadata validation phase. Metadata validation results don't affect the
deployment status of a flexfield.
Metadata Synchronization
When an extensible or descriptive flexfield is deployed, the deployment process regenerates the XML schema definition
(XSD), which makes the custom attributes available to web services and the SOA infrastructure.
After deploying a flexfield configuration, you must synchronize the updated XML schema definition (XSD) files in the Oracle
Metadata Services (MDS) repositories for each SOA application.
Note
To synchronize the updated XSD files in the MDS repositories in Oracle Cloud implementations, log a service
request using My Oracle Support at http://support.com/
Deployment as a Background Process

You can deploy extensible flexfields or incremental changes made to extensible flexfields as a background process. You must
use this action to deploy extensible flexfields that have more than 30 categories. You can also use this action if you want to
deploy several extensible flexfields, or if you want to continue working in your session without having to wait for a deployment
to complete.
Export of Artifacts from Flexfield MDS

You can export business components from MDS for descriptive, extensible, or key flexfields, mainly for use in troubleshooting
issues with flexfields. Use Download Flexfield Archive on the Manage Flexfields page to export MDS artifacts of the
selected flexfield, and import them to an archive on your local machine. You can use these archived business components of
flexfields for troubleshooting purposes.
Alternatively, export the deployed artifacts using exportMetadata WLST.
Flexfield Deployment Status: How It Is Calculated

Flexfield deployment status indicates how the flexfield metadata definition in the Oracle Fusion Applications database relates
to the Application Development Framework (ADF) business components generated into an Oracle Metadata Services (MDS)
Repository.
The following aspects are important in understanding how flexfield deployment status is calculated:
• Settings that affect flexfield deployment status
• How deployment status is calculated
248
Objects
Settings That Affect Flexfield Deployment Status

If you have made a change to a flexfield and expect a changed deployment status, be sure you have saved your changes. No
settings affect flexfield deployment status.
How Deployment Status Is Calculated

If the flexfield definition has been edited through the Define Flexfields activity task flows, the status is Edited. The latest
flexfield metadata definition in the Oracle Fusion application diverges from the latest deployed flexfield definition. Any change,
including if a value set used in a flexfield changes, changes the deployment status to Edited. If a flexfield has never been
deployed, its status is Edited.
Note
When an application is provisioned, the provisioning framework attempts to deploy all flexfields in that application.
If you deploy the flexfield to a sandbox successfully, the status is Deployed to Sandbox. The latest flexfield metadata definition
in the Oracle Fusion application matches the metadata definition that generated ADF business components in a sandbox
MDS Repository. Whether the sandbox is active or not doesn't affect the deployment status. If the flexfield was deployed
to a sandbox and hasn't been edited or redeployed to the mainline 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 flexfield successfully to the mainline, the status is Deployed. The latest flexfield metadata definition in the
Oracle Fusion application matches the metadata definition that generated ADF business components in a mainline MDS
Repository. Change notifications are sent when a flexfield is deployed successfully to the mainline.
If either type of deployment fails so that the current flexfield definition isn't deployed, the status is Error. The deployment error
message gives details about the error. The latest flexfield metadata definition in the Oracle Fusion application likely diverges
from the latest successfully deployed flexfield definition.
If the flexfield definition has been modified by a patch, the status is Patched. The latest flexfield metadata definition in the
Oracle Fusion application diverges from the latest deployed flexfield definition. If the flexfield definition was Deployed before
the patch and then a patch was applied, the status changes to Patched. If the flexfield definition was Edited before the patch
and then a patch was applied, the status will remain at Edited to reflect that there are still changes (outside of the patch) that
aren't yet in effect.
When a deployment attempt fails, you can access the Deployment Error Message for details.
Related Topics
Deploying a Flexfield-Enabled Sandbox: How It Works With Mainline Metadata

The flexfield definition in a sandbox corresponds to the flexfield metadata definition in the Oracle Fusion Applications database
at the time the flexfield was deployed to the sandbox. When the flexfield is ready for end users, the flexfield must be deployed
to the mainline.
A flexfield-enabled sandbox uses the following components.
• Flexfield metadata in the Oracle Fusion Applications database
• Flexfield business components in a sandbox Oracle Metadata Services (MDS) Repository
• User interface customizations for the flexfield in the mainline MDS Repository
The figure shows the two types of deployment available in the Manage Flexfield tasks of the Define Flexfields activity.
Deploying a flexfield to a sandbox creates a sandbox MDS Repository for the sole purpose of testing flexfield behavior. The
sandbox is only accessible to the administrator who activates and accesses it, not to users generally. Deploying a flexfield to
the mainline applies the flexfield definition to the mainline MDS Repository where it is available to end users. After deploying
249
Objects
the flexfield to the mainline, customize the page where the flexfield segments appear. Customization of the page in the
sandbox MDS Repository cannot be published to the mainline MDS Repository.
Sandbox Metadata Services Repository Data

Deploying the flexfield to a sandbox generates the Application Development Framework (ADF) business components of a
flexfield in a sandbox MDS Repository for testing in isolation.
Warning
Don't customize flexfield segment display properties using Page Composer in a flexfield-enabled sandbox as
these changes will be lost when deploying the flexfield to the mainline.
250
Objects
Mainline Metadata Services Repository Data

The Oracle Fusion Applications database stores the single source of truth about a flexfield. When the flexfield is deployed, the
ADF business component objects that implement the flexfield in the run time user interface are generated in the mainline MDS
Repository from this source.
Related Topics
• Sandboxes: Highlights
Deploying a Flexfield to a Sandbox: Points to Consider

Deploying a flexfield to a sandbox creates a flexfield-enabled sandbox. Each flexfield-enabled sandbox contains only one
flexfield.
You can test the run time behavior of a flexfield in the flexfield-enabled sandbox. If changes are needed, you return to the
Define Flexfield tasks to change the flexfield definition.
When you deploy a flexfield to sandbox, the process reads the metadata about the segments from the database, generates
flexfield Application Development Framework (ADF) business component artifacts based on that definition, and stores in the
sandbox only the generated artifacts derived from the definition.
When you deploy a flexfield sandbox, the process generates the name of the flexfield sandbox, and that flexfield sandbox is
set as your current active sandbox. When you next sign in to the application, you can see the updated flexfield configurations.
The Oracle Fusion Applications global area displays your current session sandbox.
Note
Unlike a standalone sandbox created using the Manage Sandboxes tool, the sandbox deployed for a flexfield
contains only the single flexfield. You can manage flexfield sandboxes, such as setting an existing flexfield
sandbox as active or deleting it, using the Manage Sandboxes tool.
When you deploy a flexfield to the mainline after having deployed it to the sandbox, the sandbox-enabled flexfield is
Sandbox MDS Repository Data

The sandbox data lets you test the flexfield in isolation without first deploying it in the mainline where it could be accessed by
users.
Warning
Managing a Flexfield-Enabled Sandbox

When you deploy a flexfield as a sandbox, that flexfield-enabled sandbox automatically gets activated in your user session.
When you sign back in to see the changes, the sandbox is active in your session.
You can only deploy a flexfield to a sandbox using the Define Flexfields task flow pages.
You also can use the Manage Sandboxes feature in the Administration menu of the Setup and Maintenance work area to
activate and access a flexfield-enabled sandbox.
Note
Whether you use the Define Flexfields or Manage Sandboxes task flows to access a flexfield-enabled sandbox,
you must sign out and sign back in before you can see the changes you deployed in the run time.
251
Objects
You cannot publish the flexfield from the sandbox to the mainline. You must use the Define Flexfields task flow pages to
deploy the flexfield for access by users of the mainline because the flexfield configuration in the mainline is the single source of
truth.
Related Topics
Deploying Flexfields Using the Command Line: Explained

You can use the Manage Key Flexfields, Manage Descriptive Flexfields, and Manage Extensible Flexfields tasks to deploy
flexfields. You can also use WebLogic Server Tool (WLST) commands for priming the Oracle Metadata Services (MDS)
Repository with predefined flexfield artifacts and for deploying flexfields.
The table describes the available commands.
WebLogic Server Tool Command Description
Deploys all flexfields for the specified enterprise

application. Only flexfields whose status is other than
deployed are affected by this command unless the
option is enabled to force all flexfields to be deployed
regardless of deployment status.

Initial application provisioning runs this command to
prime the MDS Repository with flexfield artifacts.

Deploy a single flexfield regardless of deployment status

Deploys flexfield changes that have been delivered using

a flexfield Seed Data Framework (SDF) patch. Deploys
flexfields that have a Patched deployment status.

Displays MDS label of flexfield changes for viewing and

deleting patching labels.

Displays list containing flexfields that aren't deployed or

failed deployment.

Executing these commands outputs a report at the command line. The report provides the following information for every
flexfield that is processed.
• Application identity (APPID)
• Flexfield code
• Deployment result, such as success or error
In case of errors, the report lists the usages for which the errors were encountered. If a run time exception occurs, the output
displays the traceback information. For each WLST flexfield command, adding the reportFormat='xml' argument returns the
report as an XML string.
252
Objects
Consider the following aspects of command line deployment.
• Preparing to use the WLST flexfield commands
• Using the deployFlexForApp command
• Using the deployFlex command
• Using the deployPatchedFlex command
• Using the deleteFlexPatchingLabels command
• Using the validateFlexDeploymentStatus command
• Exiting the WLST and checking the results
Preparing To Use the WLST Flexfield Commands

You can only execute the WLST flexfield commands on a WebLogic Administration Server for a domain that has a running
instance of the Oracle Fusion Middleware Extensions for Applications (Applications Core) Setup application.
For more information on deploying the Applications Core Setup application, see the Oracle Fusion Applications Developer's
Guide.
Ensure that the AppMasterDB data source is registered as a JDBC data source with the WebLogic Administration Server and
points to the same database as the ApplicationDB data source.
Start the WebLogic Server Tool (WLST) if it isn't currently running.
UNIX:
sh $JDEV_HOME/oracle_common/common/bin/wlst.sh
Windows:
wlst.cmd
Connect to the server, replacing the user name and password arguments with your WebLogic Server user name and
password.
connect('wls_username', 'wls_password', 'wls_uri')
The values must be wrapped in single-quotes. The wls_uri value is typically T3://localhost:7101.
For more information on the WLST scripting tool, see the Oracle Fusion Middleware Oracle WebLogic Scripting Tool.
Using the deployFlexForApp Command

The deployFlexForApp command translates the product application's predefined flexfield metadata into artifacts in the MDS
Repository.
Important
This command is run automatically when you provision applications. However, after custom applications
development, you must run the deployFlexForApp command after you configure your application to read the flexfield
artifacts from the MDS Repository and before you log into the application for the first time, even if there is no
predefined flexfield metadata.
This command doesn't deploy flexfields that have a status of Deployed unless the force parameter is set to 'true' (the default
setting is 'false').
For more information on priming the MDS partition with configured flexfield artifacts, see the Oracle Fusion Applications
Developer's Guide.
253
Objects
From the WLST tool, execute the following commands to deploy the artifacts to the MDS partition, replacing
product_application_shortname with the application's short name wrapped in single-quotes.
deployFlexForApp('product_application_shortname'[, 'enterprise_id'] [,'force'])
In a multi-tenant environment, replace enterprise_id with the Enterprise ID to which the flexfield is mapped. Otherwise, replace
with 'None' or don't provide a second argument.
To deploy all flexfields regardless of their deployment status, set force to 'true' (the default setting is 'false'). If you want to
deploy all flexfields in a single-tenant environment, you either can set enterprise_id to 'None', or you can use the following
signature:
deployFlexForApp(applicationShortName='product_application_shortname',force='true')
Tip
The application's short name is the same as the application's module name.
For more information about working with application taxonomy, see the Oracle Fusion Applications Developer's Guide.
Using the deployFlex Command

From the WLST tool, execute the following command to deploy a flexfield, replacing flex_code with the code that identifies
the flexfield, and replacing flex_type with the flexfield's type, which is either DFF, KFF, or EFF. The values must be wrapped in
single-quotes.
deployFlex('flex_code', 'flex_type')
Optionally, execute the following command if the flexfield is an extensible flexfield, and you want to deploy all the flexfield's
configurations.
Note
By default, extensible flexfields are partially deployed. That is, only the pages, contexts, or categories that had
recent changes, are deployed.
deployFlex('flex_code', 'flex_type', ['force_Complete_EFF_Deployment'])

where, forceCompleteEFFDeployment=None
Using the deployPatchedFlex Command

Use the deployPatchedFlex command for situations where the patching framework doesn't invoke the command, such as when
an application has been patched offline.
If the installation is multi-tenant enabled, the command deploys all patched flexfields for all enterprises. This command isn't
intended to be invoked manually.
Check with your provisioning or patching team, or the task flows for managing flexfields, to verify that the flexfield has a
Patched deployment status.
From the WLST tool, execute the following command to deploy the artifacts to the MDS partition.
deployPatchedFlex()
Execute the following command to deploy all flexfields that have either a READY status or an ERROR status.
deployPatchedFlex(mode='RETRY')
Using the deleteFlexPatchingLabels Command

Whenever you deploy flexfield changes to MDS using the deployPatchedFlex() WLST command, an MDS label is created in the
format FlexPatchingWatermarkdate+time. Use the deleteFlexPatchingLabels command to inquire about and delete these labels.
254
Objects
From the WLST tool, execute the deleteFlexPatchingLabels () command with no arguments to delete the flexfield patching labels.
To output a list of flexfield patching labels, execute the command with the infoOnly argument, as follows:
deleteFlexPatchingLabels(infoOnly='true')
Using the validateFlexDeploymentStatus Command

The validateFlexDeploymentStatus() WLST command checks the deployment status of all flexfields in an Oracle Fusion Applications
deployment.
validateFlexDeploymentStatus()
Use this command to verify that all flexfields in the current instance of provisioned Java EE applications are deployed.
Exiting the WLST and Checking the Results

To exit the tool, execute the following command.
disconnect()
Optionally, sign into the application, access user interface pages that contain flexfields, and confirm the presence of flexfields
for which configuration exists, such as value sets, segments, context, or structures.
Manage Descriptive Flexfields

Descriptive Flexfields: Explained
Descriptive flexfields provide a way to add custom attributes to entities, and define validation and display properties for them.
These attributes are generally standalone. They don't necessarily have anything to do with each other and aren't treated
together as a combination.
All Oracle Fusion Applications business entities that you can access are enabled for descriptive flexfields. Descriptive
flexfields are optional. You can choose whether or not to configure and expose segments for the descriptive flexfield defined
and registered in your database. For lists of descriptive flexfields, see assets with the Flexfield: Descriptive type in Oracle
Enterprise Repository for Oracle Fusion Applications (http://fusionappsoer.oracle.com).
A descriptive flexfield provides a set amount of segments for an entity. You make the segments of a descriptive flexfield
available to end users as individual fields in the application user interface.
Context
A descriptive flexfield can have only one context segment to provide context sensitivity.
The same underlying column can be used by different segments in different contexts. For example, you can define a
Dimensions context that uses the ATTRIBUTE1 column for height, the ATTRIBUTE2 column for width, and the ATTRIBUTE3
column for depth. You can also define a Measurements context that uses the same columns for other attributes: the
ATTRIBUTE1 column for weight, the ATTRIBUTE2 column for volume, and the ATTRIBUTE3 column for density.
Segments and Contexts

Descriptive flexfield segments are of the following types.
Segment Type Run Time Behavior
Global segment Always available

255
Objects
Context segment Determines which context-sensitive segments are

displayed

Context-sensitive segment Displayed depending on the value of the context

segment

In the figure, a descriptive flexfield has one context segment called Category for which there are three values: Resistor,
Battery, and Capacitor. In addition, the descriptive flexfield consists of two global segments that appear in each of the
contexts, and three context-sensitive segments that only appear in the context in which they are configured.
Application development determines the number of segments available for configuring. During implementation, you configure
the flexfield by determining the following:
• Which attributes to add using the available segments

• The context values
• The combination of attributes in each context
A segment can be used for different attributes, such as Height in Context1 and Color in Context2. Each segment of a
descriptive flexfield that you make available to end users is exposed in the user interface as an individual field.
256
Objects
Value Sets
For each global and context-sensitive segment, you configure the values allowed for the segment and how the values that
end users enter are validated, including interdependent validation among the segments.
Protected Descriptive Flexfield Data

Application developers may mark some data configurations in a descriptive flexfield as protected, indicating that you can't
edit them. You can't edit any portion of a protected descriptive flexfield.
Related Topics
• Oracle Enterprise Repository for Oracle Fusion Applications: Explained
Planning Descriptive Flexfields: Points to Consider

Once you have identified a flexfield to configure, plan the configuration in advance. Compile a list of the UI pages and other
artifacts in your deployment that are affected by the configuration. Verify that you are provisioned with the roles needed to
view and configure the flexfield. View the flexfield using the Highlight Flexfields command in the Administration menu while
viewing the run time page where the flexfield appears. Plan how you will deploy the flexfield for test and production users.
Review the tools and tasks available for managing flexfields, such as the Define Flexfields task list, Manage Sandboxes, and
Highlight Flexfields for adding and editing flexfield segments.
Planning a descriptive flexfield can involve the following tasks:
1. Identify existing parameters.
2. Identify existing context values and whether the context value is derived.
3. Identify custom attributes and plan the descriptive flexfield segments, segment properties, and structure.
4. Plan validation rules.
5. Plan initial values.
6. Plan attribute mapping to Oracle Business Intelligence objects.
Identify Existing Descriptive Flexfield Parameters

Some descriptive flexfields provide parameters that can be used to specify the initial value of a descriptive flexfield segment.
The parameter is external reference data, such as a column value or a session variable. For example, if a flexfield has a user
email parameter, you can configure the initial value for a customer email attribute to be derived from that parameter.
Review the list of available parameters in the Derivation Value field in the Create Segment page for a descriptive flexfield. If
you decide to use one of the parameters to set an initial value, select that parameter from the Derivation Value drop-down
list when you add the descriptive flexfield segment.
Evaluate Whether the Context Value Is Derived

The context value for a descriptive flexfield might have been preconfigured to be derived from an external reference. For
example, if the context is Marriage Status, then the value might be derived from an attribute in the employee business object.
When the context value is derived, you might need to take the derived values and their source into consideration in your plan.
To determine whether the context value is derived, access the Edit Descriptive Flexfield task to view the list of configured
context values for the flexfield. The Derivation Value field in the Context Segment region displays a list of available parameters.
If context values have been preconfigured, see Oracle Fusion Applications Help for product-specific information about the use
of those values.
257
Objects
Plan the Segments, Segment Properties, and Structure

Identify the custom attributes you need for a business object to determine the segments of the descriptive flexfield. Determine
the segment properties such as the prompt, display type, or initial value.
The structure of the descriptive flexfield is determined by its global, context, and context-sensitive segments. Plan a global
segment that captures an attribute for every instance of the business object. Plan a context for segments that depend on
a condition of situation applying to a particular instance of the business object. Plan context-sensitive segments to capture
attributes that are relevant in the context.
There is only one context segment available for descriptive flexfields. If you have more than one group of custom attributes
where you could use the context segment, you will have to pick one group over the others, based on your company's needs
and priorities, and add the other custom attributes as global segments.
Plan Validation Rules

Define each segment's validation rules and check if value sets exist for those rules or you must create new ones. If you must
create a value set, you can create it either before configuring the flexfield or while creating or editing a segment.
When determining a segment's validation rules, consider the following questions:
• What is the data type - character, date, date and time, or number?
• Does the segment require any validation beyond data type and maximum length?
• Should a character type value be restricted to digits, or are alphabetic characters allowed?
• Should alphabetic characters automatically be changed to uppercase?
• Should numeric values be zero-filled?
• How many digits can follow the radix separator of a numeric value? In base ten numerical systems the radix
separator is decimal point.
• Does the value need to fall within a range?
• Should the value be selected from a list of valid values? If so, consider the following questions:
◦ Can you use an existing application table from which to obtain the list of valid values, or do you need to create
a custom list?
◦ If you are using an existing table, do you need to limit the list of values using a WHERE clause?
◦ Does the list of valid values depend on the value in another flexfield segment?
◦ Is the list of valid values a subset of another flexfield segment's list of values?
Plan Initial Values

For every segment, list the constant value or SQL statement, if any, to use for the initial value of the custom attribute.
Plan How Segments Map to Oracle Business Intelligence Objects

You can extend descriptive flexfields into Oracle Transactional Business Intelligence (OTBI) for ad hoc reporting purposes.
Determine the descriptive flexfield segments to be made available for reporting, and select the BI Enabled check box
accordingly on the Manage Descriptive Flexfields page. You must run a process to extend the BI enabled segments into
OTBI. For more information about extending the BI enabled segments into OTBI, see the Setup and Configuration chapter in
the Oracle Transactional Business Intelligence Administrator's Guide.
Depending on the reporting needs, you may map similar context-sensitive attributes from different contexts to the same
attribute in OTBI. For example, there may be a segment tracking the Product Color attribute in different contexts of a context
258
Objects
sensitive descriptive flexfield. You can use segment labels to map these context-sensitive attributes together by defining a
segment label and updating the BI Label list accordingly.
Managing Descriptive Flexfields: Points to Consider

Configuring descriptive flexfields involves managing the available flexfields registered with your Oracle Fusion Applications
database and configuring their flexfield-level properties, defining and managing descriptive flexfield contexts, and configuring
global and context-sensitive segments.
Every descriptive flexfield is registered to include a context segment, which you may choose to use or not.
In general, configuring descriptive flexfields involves:
1. Creating segment labels for business intelligence enabled flexfields.
2. Configuring global segments by providing identity information, the initial default value, and the display properties.
3. Configuring the context segment by specifying the prompt, whether the context segment should be displayed, and
whether a value is required.
4. Configuring contexts by specifying a context code, description, and name for each context value, and adding its
context-sensitive segments, each of which is configured to include identifying information, the column assignment,
the initial default value, and the display properties.
The following aspects are important in understanding descriptive flexfield management:
• Segments
• Adding Segments to a Highlighted Flexfield
• Usages
• Parameters
• Delimiters
• Initial Values
• Business Intelligence
Segments
display is always in a fixed order. You cannot enter a number for one segment that is already in use for a different segment.
Value sets are optional for context segments. The value set that you specify for a context segment consists of a set of
context codes, each of which corresponds to a context that is appropriate for the descriptive flexfield. 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 definition of each context segment specifies 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 cannot delete an existing context. Instead, you can disable the associated context value in
its own value set by setting its end date to a date in the past.
You can configure the individual global segments and context-sensitive segments in a descriptive flexfield. These segment
types are differentiated by their usage, but they are configured on application pages that use most of the same properties.
259
Objects
Adding Segments to a Highlighted Flexfield

When you highlight flexfields on a run time page and use an Add Segment icon button to create a segment, the segment
code, name, description, table column, and sequence number are set automatically. If you use an Add Segment icon button
to configure descriptive flexfield segments, you cannot use an existing value set. Value sets are created automatically when
you add the segments. You can enter the valid values, their descriptions, and the default value or specify the formatting
constraints for the value set, such as minimum and maximum values.
Depending on display type, the value set you create with the Add Segment icon button is either an independent value set
or a format-only value set. The table shows which type of value set is created depending on the segment display component
you select.
Display Component Value Set Created with Add Segment
Check box Independent

Drop-down list Independent

List of Values Independent

Radio Button Group Independent

Text Field With Search Independent

Text box Format Only

Text area Format Only

Date/Time Format Only

Tip
After you add a context value, refresh the page to see the new value.
Usages
Descriptive flexfield usages allow for the same definition to be applied to multiple entities or application tables, such as a
USER table and a USER_HISTORY table. Descriptive flexfield tables define the placeholder entity where the flexfield segment
values are stored once you have configured the descriptive flexfield. When you configure a flexfield, the configuration applies
to all its usages.
Parameters
Some descriptive flexfields provide parameters, which are attributes of the same or related entity objects. Parameters are
public arguments to a descriptive flexfield. Parameters provide outside values in descriptive flexfield validation. You use
parameters to set the initial value or derivation value of an attribute 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.
260
Objects
Delimiters
A segment delimiter or separator visually separates segment values when the flexfield is displayed as a string of concatenated
segments.
Initial Values
The SQL statement defining 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 the following bind variables in the WHERE clause of the SQL
statement.
◦ :{SEGMENT.<segment_code>}: Identifies a segment in the same context.
◦ :{CONTEXT.<context_code>;SEGMENT.<segment_code>}: Identifies a segment in a different context. The context

must be in the same category or in an ancestor category, and it cannot be a multiple-row context.
◦ :{VALUESET.<value_set_code>}: Identifies the closest prior segment in the same context that is assigned to the
specified value set.
◦ :{FLEXFIELD.<internal_code>}: Identifies a flexfield.
For more information about using bind variables, see the help for value sets.
Business Intelligence
Selecting a global, context, or context-sensitive segment's BI Enabled checkbox specifies that the segment is available for
use in Oracle Business Intelligence.
When the flexfield is imported into Oracle Business Intelligence, the label you selected from the BI Label dropdown list
equalizes the segment with segments in other contexts, and maps the segment to the logical object represented by the label.
Enabling Descriptive Flexfield Segments for Business Intelligence: Points to Consider

A descriptive flexfield that is registered in the database as enabled for Oracle Business Intelligence (BI) includes a BI Enabled
setting for each of its segments. When a global, context, or context-sensitive segment is BI-enabled, it is available for use in
Oracle Business Intelligence.
The following aspects are important in understanding BI-enabled flexfield segments:
• Flattening business components to use BI-enabled segments in Oracle BI
• Equalizing segments to prevent duplication and complexity in the flattened component
• Mapping attributes of flattened business components to logical objects in Oracle BI
• Managing the labels that map segments to logical objects in Oracle BI
After you deploy a business intelligence-enabled flexfield, use the Import Oracle Fusion Data Extensions for Transactional
Business Intelligence process to import the flexfield changes into the Oracle Business Intelligence repository. Users can make
use of the newly-generated attributes in business intelligence applications. For example, a user can generate a report that
261
Objects
includes attributes added by the descriptive flexfield. For additional information about logical objects and import, refer to the
Oracle Transactional Business Intelligence Administrator's Guide.
Flattening
When you deploy a business intelligence-enabled descriptive flexfield, the deployment process generates an additional
set of flattened 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 flattened business components
include attributes for business intelligence-enabled segments only. Flattening means each custom column in each context
shows up as an attribute in an Oracle Business Intelligence folder.
Flattened components include one attribute for the BI-enabled context-segment, and one attribute 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 flattened components include an additional single attribute representing
segments with that label.
• If you didn't assign a label, the flattened components include a discrete attribute for each BI-enabled context-
sensitive segment in each context.
Mapping to Logical Objects in Business Intelligence

You can simplify reporting by representing similar segments as a single logical object in Business Intelligence.
If you assign a label to any set of context-sensitive segments that serve the same purpose in different contexts, you can
consolidate or equalize the segments into a single attribute. This prevents duplication and the extra workload and complexity
that result from the flattening 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 attribute in the flattened business component.
Non-labeled context-sensitive segments aren't equalized across context values, so the flattened components include a
separate attribute for each context-sensitive segment for each context value.
Note
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 attribute in the
flattened components to a logical object in Oracle Business Intelligence. Using labels to map segments to BI logical objects
minimizes the steps for importing the flexfield into Oracle Business Intelligence.
Note
Assigning a label to a context-sensitive segment serves to equalize the attribute across contexts, as well as map
the equalized attribute to business intelligence.
Managing Labels
You may assign a predefined 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 field, 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 flexfield 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.
262
Objects
In addition, context-sensitive segments without labels cannot be equalized across context values. The flattened components
include a separate attribute for each non-labeled context-sensitive segment in each context.
Importing to Oracle Business Intelligence Repository

After you deploy a business intelligence-enabled flexfield, import the flexfield changes into the Oracle Business Intelligence
repository to make use of the newly flattened business components in business intelligence and then propagate the flexfield
object changes. When you import the metadata into the Oracle Business Intelligence repository, you must do so as the
FUSION_APPS_BI_APPID user.
Note
To import flexfield 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.
Tip
When you import a flexfield into the Oracle Business Intelligence repository, you see both <name>_ and <name>_c
attributes for each segment, along with some other optional attributes. The <name> attribute contains the value.
The <name>_c attribute 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 attributes.
Related Topics
FAQs for Manage Descriptive Flexfields

Can I display the context segment in the project Cost Collection flexfield?
No. The context segment is predetermined for each page. Displaying it and changing the value may result in capture of data
that is not applicable for the current transaction.
Manage Messages
Messages: Highlights
The message dictionary contains messages that tell users about business rule errors, such as missing or incorrect data,
and how to resolve them, to warn users about the consequences of intended actions, and provide information in log files.
These messages are defined for specific applications and modules, but a few are common messages that can be used in any
application. All applications also use messages stored outside of the message dictionary.
The message dictionary is described in the Oracle Fusion Applications Developer's Guide.
Managing Messages
• Use the Manage Messages page to create and edit custom messages in the message dictionary, as well as edit
predefined messages. Do not delete predefined messages unless you are sure that they are not used anywhere.
Refer to the Oracle Fusion Applications Developer's Guide.
See: Introduction to Message Dictionary Messages
263
Objects
• Messages outside of the message dictionary, such as confirmations and field validations, are managed either in the
Oracle Application Development Framework or through message resource bundles used for translation.
Related Topics
Creating and Editing Messages: Highlights

Each message in the message dictionary has many attributes and components, including message properties, text,
and tokens, that you define when creating or editing the message. To create or edit a message, navigate to the Manage
Messages page in the Setup and Maintenance work area.
Details about these messages are described in the Oracle Fusion Applications Developer's Guide.
Message Properties
• The message type identifies the type of information that the message contains.
See: Understanding Message Types
• The message name and number are identifiers for the message. There are specific message number ranges for
predefined messages in each application, and you should not edit numbers assigned to predefined messages. When
creating custom messages, use only message numbers within the 10,000,000 to 10,999,999 range.
See: About Message Names
See: About Message Numbers
• The translation notes for predefined messages might contain internal content that you can disregard.
See: About Translation Notes
• The message category, severity, and logging enabled option are related to the incident and logging process.
See: About Grouping Messages by Category and Severity
See: Understanding Incidents and Diagnostic Logs with Message Dictionary
Message Text and Tokens

• The message text comprises various components, some of which are displayed only to select users. To determine
which component of the message text is displayed to a particular user, set the Message Mode profile option
(FND_MESSAGE_MODE) at the user level for that user. The message component short text is visible to all users and
therefore, the profile option does not apply to this component. Also, the profile option applies only to messages in
the message dictionary.
See: About Message Components
• Tokens are variables that represent values to be displayed in the message text.
See: About Tokens
Related Topics
264
Objects
Common Messages: Points to Consider

Common messages, which have message names that begin with FND_CMN and message numbers between 0 and 999, are
used throughout Oracle Fusion Applications. Each common message can appear in multiple places in any product family. For
example, the FND_CMN_NEW_SRCH message can be used for any search to indicate that no results were found. Common
messages that are of type error or warning are part of the message dictionary.
Editing Common Messages

Because a common message can be used in any application, consider the ramifications if you edit any aspect of the
message, including incident and logging settings. Changes would be reflected in all instances where the message is used.
For example, if you change the message text, make sure that the text would make sense to all users across Oracle Fusion
Applications who might see it.
Creating Common Messages

You can create custom common messages for use in multiple places within a single product. Do not begin the message
name with FND_CMN, but use another suitable convention. The message number should be within the range that is
designated for the product.
Manage Attachment Categories
Attachments: Explained
Attachments are pieces of supplementary information that users can associate with specific business objects such
as expense reports or purchase orders. Attachments can be URLs, desktop files, text, or in cases where available,
repository folders. For any given business object, a user may be able to only view attachments, or also create, delete, or
edit attachments, depending on security. For more information on an introduction to attachments, see the Oracle Fusion
Applications Developer's Guide.
Repository
Attachments are stored in a content management repository provided by Oracle WebCenter Content Server. Users managing
attachments have no real interaction with the repository unless the repository mode is enabled for attachments on specific
business objects. In that case, users can share attachments among objects, update attachments by checking them
out of and back into the repository, and perform other tasks. Access to attachment files is controlled by a digital signing
mechanism. Depending on security, users might have direct access to the repository.
Security
Data security that applies to a specific business object also applies to attachments for that object, as determined by the
attachment entity defined for the object. For example, if a user has no access to a specific expense report, then the same
user cannot access attachments for the expense report. You can also use attachment categories to control access and
actions on attachments, based on roles associated with the category. For more information on securing attachments, see the
Oracle Fusion Applications Developer's Guide.
Attachment Entities: Explained

An attachment entity is usually a database entity, for example a table or view, that represents a business object attachments
can be associated with. Each attachment UI must be defined with a corresponding attachment entity, which not only
identifies the business object to attach to, but also controls what users can do. Attachment entities are used only in the
context of attachments and exist separately from the database entities that they are based on.
265
Objects
Edit and create attachment entities on the Manage Attachment Entities page, which you can access by starting in the Setup
and Maintenance Overview page and searching for the Manage Attachment Entities task. Though you would generally use
predefined attachment entities with attachment UIs, you might need to create new entities, for example when developing
custom UIs.
Entity Names
An attachment entity name should match the name of the table or view that represents the business object to attach to. The
name is also used in the repository folder that is automatically created to store attachments for the entity. The attachment
entity display name should be something that users know to represent the business object.
Database Resource
The data security policies associated with the database resource defined for the attachment entity would apply to
attachments for that entity. For example, based on the database resource for the expense reports attachment entity,
the same policies apply to attachments for expense reports. 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.
Enabling Security
Security based on the database resource associated with the attachment entity is always in effect. What you can enable or
disable is security based on attachment categories. If any of the attachment categories associated with the attachment entity
has data security defined, then that security applies to this entity only if enabled.
Related Topics
• Database Resources and Data Security Policies: How They Work Together
Attachment Entities and Attachment Categories: How They

Work Together
The association between attachment entities and categories determines which categories can be used for an entity. For
example, categories associated with the expense report attachment entity are available to be implemented in attachment UIs
for expense reports. You can define these associations when managing either entities or categories. Any association changes
in either the Manage Attachment Entities or Manage Attachment Categories page are reflected on the other page. You can
access either page by starting in the Setup and Maintenance Overview page and searching for attachment tasks.
Managing Entities
You determine which attachment categories are relevant to a particular entity on the Manage Attachment Entities page, and
each entity must have at least one category. Depending on configuration, any or all of the available categories for that entity
are used. For example, you assign three categories to the expense reports attachment entity. For a particular expense report
page with attachments functionality, you can customize the attachments component to specify which of the three categories
are used. Based on your selection, the data security defined for each category, if any, is applied to attachments on that page
if the attachment entity has category-based security enabled.
Managing Categories
If you create an attachment category and need to assign it to multiple attachment entities, use the Manage Attachment
Categories page. The association means the same as the association on the Manage Attachment Entities page.
266
Objects
Attachments Troubleshooting: Explained

Attachments UIs for users to add and manage attachments are fully functional as is, and users usually would not encounter
issues. If you customize attachments in any way, for example by creating additional attachment categories and implementing
data security on them, then some issues might arise.
Issue: Unable to View, Add, Update, or Delete Attachments

Users encounter issues when trying to view attachments or perform actions such as adding attachments.
• Users can no longer see specific attachments that they were previously able to see.
• Likewise, they can no longer update or delete attachments.
• Users get an error stating that they do not have permission to add attachments.
Resolution
Use the Manage Attachment Entities page to ensure that attachment categories are associated to the relevant attachment
entity. For example, if users can no longer see attachments for an expense report, then search for the expense report
attachment entity and assign all necessary categories to it. You might need to check with your system administrator or help
desk to determine the exact entity used on the page with the expenses attachments or what categories to assign.
If data security is implemented on the categories for the attachment entity, then verify that the Enable Security check box is
selected in the Manage Attachment Entities page for that entity. Make sure that users have a role with the privileges shown in
the following table, to view, add, update, or delete attachments with a specific attachment category.
Action Privilege
View Read Application Attachment (FND_ READ_

APPLICATION_ ATTACHMENT_ DATA)

Add or Update Update Application Attachment (FND_ UPDATE_


Delete Delete Application Attachment (FND_ DELETE_


For example, if users have the Read Application Attachment privilege for all categories associated with the expense report
attachment entity, except the Receipts attachment category, then they can view all expense report attachments except
those created with the Receipts category. Likewise, if users do not have the Update Application Attachment privilege for
any attachment categories tied to the expense report attachment entity, then they cannot create any attachments at all for
expense reports.
For more information on attachment category data security, see the Oracle Fusion Applications Developer's Guide.
Finally, certain attachments UI for users have predefined restrictions on categories in place. Your developers can also
introduce additional filters to determine which document categories are available for a specific page. Check with your
developers or help desk.
Issue: Missing Attachment Category

Users can see existing attachments, but the attachments no longer have an attachment category value.
267
Objects
Resolution
When the attachment was added, at least one category existed for the corresponding attachment entity, as otherwise the
attachment could not have been added. Since then, the entity was edited so that it no longer has any assigned categories, so
the user cannot see the category associated with that attachment.
Use the Manage Attachment Entities page to reassign attachment categories to the relevant attachment entity. For example,
if users can no longer see the Receipts attachment category for an attachment to an expense report, then search for
the expense report attachment entity and assign to it the Receipts category. You might need to check with your system
administrator or help desk to determine the exact entity used on the page with the expenses attachments or what additional
categories to assign.
FAQs for Management Attachment Categories

What's an attachment category?
An attachment category is used to classify and secure attachments. Each attachment user interface must be defined with at
least one category for users to be able to add attachments. If there are multiple categories, users can view them and select
one when adding attachments. For example, attachments for an expense report can be categorized as receipts, scanned
invoice images, and so on.
You can also associate roles with categories to determine user access and actions for attachments, based on the categories
assigned to the attachment entity. For example, security for expense report attachments can be based in part on the
categories assigned to the expense report attachment entity. You can define multiple categories per module, and add and
manage custom categories for your own purposes. For more information on attachment category data security, see the
Use the Manage Attachment Categories page, which you can access by starting in the Setup and Maintenance Overview
page and searching for the Manage Attachment Categories task.
Related Topics
268
Implementing Project Financial Management Project Foundation Configuration: Overview
10 Project Foundation Configuration: Overview
Define Project Foundation Configuration: Overview

In the Define Project Foundation Configuration activity, you configure foundation components for creating and maintaining
projects in Project Financial Management.
Setup tasks in the Define Project Foundation Configuration activity are grouped into the following task lists and tasks:
Define Project Foundation Common Reference Objects Review and manage common objects, for example value
sets and messages, that are used by Project Financial
Management.

Define Project Calendars and Periods Manage calendars, accounting period statuses, and
project accounting period statuses used for costing,
budgeting, forecasting, billing, and project performance
reporting.

Define Types and Categorizations Manage various classifications used to describe and
group projects, tasks, and transactions.

Manage Oracle Social Network Objects for Project Enable the display of information in Oracle Social
Foundation Network about changes to Project Financial
Management business objects, and select which
attributes to include for each object.

Define Project Spaces Configure how Project Financial Management interacts

with Oracle WebCenter Spaces.

Define Project Roles Define project roles and the business rules that control
how the roles are assigned.

Define Project Resources Define job mapping, attributes, and rate schedules for
project resources.

Define Rate Schedules and Costing Rules Define rate schedules and costing rules used for costing,
billing, work planning, and financial planning purposes.

269
Implementing Project Financial Management Project Foundation Configuration: Overview
Define Project Resource Breakdown Structures Define resource breakdown structures used for project
planning, billing, and reporting.

Define Burdening Configure options used to calculate, group, and apply

indirect costs to project expenditure items to report and
account the total cost of a project.

Manage Project Types Create classifications for projects and configure basic
options that are inherited by each project associated
with that project type.

Define Action Controls Define source products and configure action controls
to determine which actions cannot be performed in
Project Financial Management on data imported from a
particular third-party source.

Distribute and Install Desktop Integrator Client Distribute and install the software needed to integrate
Excel with costing, budgeting, and forecasting.

270
Implementing Project Financial Management Project Foundation Configuration: Define Project Calendars
and Periods
11 Project Foundation Configuration: Define

Project Calendars and Periods
Maintaining Accounting Periods and Project

Accounting Periods: Critical Choices
During business unit implementation you determine whether to maintain common accounting and project accounting periods,
or define project accounting periods that have a different frequency than the accounting periods.
Accounting periods are used by Oracle Fusion Projects to assign accounting periods and dates to transactions. Accounting
periods are maintained by ledger and use the same calendar as the general ledger periods. Project accounting periods are
used by Oracle Fusion Projects for project planning, costing, billing, budgeting, forecasting, and performance reporting.
Project accounting periods are maintained by business unit and typically do not use the same calendar as the accounting and
general ledger periods.
Maintaining Common Accounting and Project Accounting Periods

If you want to report project information with the same frequency as the accounting periods, you can use the accounting
period as both the accounting and project accounting period.
When you maintain common accounting and project accounting periods, period maintenance is simplified, calendar periods
are not copied to Oracle Fusion Projects, and period information is maintained in one physical location. Use Oracle Fusion
General Ledger to maintain accounting period statuses and run the processes to open and close accounting periods.
271
and Periods
Defining Project Accounting Periods that are Different from

Accounting Periods
If you want to account for project transactions and report project information more frequently than the accounting periods
allow, you can define project accounting periods that are shorter than the accounting periods. For example, you can define
weekly project accounting periods and monthly accounting periods, as shown in the following diagram.
Use Oracle Fusion General Ledger to maintain accounting period statuses and run the processes to open and close
accounting periods, and Oracle Fusion Projects to maintain project accounting period statuses and run the processes to
open and close project accounting periods.
Related Topics
• How can I set up project accounting periods that are different from accounting periods?
• How can I set up common accounting and project accounting periods?
FAQs for Define Project Calendars and Periods
What's the difference between a project accounting period, an

accounting period, and a general ledger period?
Project accounting periods are used to track budgets and forecasts, summarize project amounts for reporting, and track the
project status. Project accounting periods are maintained by the business unit. You can set up project accounting periods
to track project periods on a more frequent basis than accounting periods. For example, you can define weekly project
accounting periods and monthly accounting periods. If you use the same calendar as your accounting periods, the project
accounting periods and accounting periods will be the same, although the statuses are maintained independently.
272
and Periods
Accounting periods, which are used to derive accounting dates, are maintained by the ledger and use the same calendar as
the general ledger periods. Period statuses for the accounting period and general ledger period are maintained independently.
Note
You can select an option on the business unit definition to maintain common accounting and project accounting
periods. This option allows the accounting period to be used as the project accounting period and you maintain
only one period status.
How can I set up project accounting periods that are different

from accounting periods?
Complete these tasks to set up project accounting periods that are different from accounting periods.
• During project business unit implementation, specify the project accounting calendar for each business unit.
◦ Verify that the option to maintain common accounting and project accounting periods is not selected.
• Copy the accounting calendar into the project accounting period table, which copies the period start and end dates.
• Manage the period statuses for project accounting periods.
How can I set up common accounting and project accounting

periods?
Complete these tasks to set up common accounting periods and project accounting periods.
• During project business unit implementation, set the project accounting calendar to the accounting calendar and
select the option to maintain common accounting and project accounting periods.
Can I change a project accounting period date range?

No. You can't change a project accounting period date range if the following conditions exist:
• The period exists in the project accounting period table.
• The period exists as an accounting period that is associated with a project accounting period.
• The period exists in project summarization tables.
What happens if I close an accounting or project accounting

period permanently?
You can't enter any transactions in the period you have closed and you can adjust transactions in subsequent periods.
273
Implementing Project Financial Management Project Foundation Configuration: Define Types and
Categorizations
12 Project Foundation Configuration: Define Types

and Categorizations
Manage Revenue Categories
Revenue Categories: Examples

Your implementation team creates revenue categories to group expenditure types and event types for revenue recognition. A
revenue category describes a source of your organization's revenue.
Revenue Categories for Labor and Other Transactions

The following table illustrates possible revenue categories your implementation team can define for labor and other types of
revenue.
Revenue Category Name Description
Fee Fee Earned

Labor Labor Revenue

Other Nonlabor Revenue

Payment Payment

FAQs for Manage Revenue Categories

What's a revenue category?
Source of revenue for an organization. Revenue categories group expenditure types and event types for revenue and
invoices. Also used to define accounting rules.
Manage Expenditure Categories and Types
Expenditure Classifications: Examples

Expenditures are divided into expenditure categories and revenue categories. Within these groups, expenditures are further
classified by expenditure type classes, expenditure types, and nonlabor resources.
274
Categorizations
Expenditure Classifications
This following graphic shows examples of expenditure classifications. Each expenditure type consists of an expenditure
category, a unit of measure and one or more expenditure type classes.
Following are the expenditure categories, units of measure, and expenditure type classes for each expenditure type shown in
the diagram.
• Administrative
◦ Expenditure Category: Labor
◦ Unit of Measure: Hours
◦ Expenditure Type Class: Straight Time
• Clerical
◦ Expenditure Category: Labor
◦ Unit of Measure: Hours
275
Categorizations
◦ Expenditure Type Classes: Straight Time and Overtime
• Consulting
◦ Expenditure Category: Outside Services
◦ Unit of Measure: Currency
◦ Expenditure Type Classes: Supplier Invoices, Expense Reports, and Usages
• Photo Processing
◦ Expenditure Category: Product Development
◦ Unit of Measure: Currency
◦ Expenditure Type Classes: Supplier Invoices and Expense Reports
Expenditure Type Classes: Explained

An expenditure type class tells Oracle Fusion Projects how to process an expenditure item.
Oracle Fusion Projects predefines all expenditure type classes, which include the following:
• Straight Time
• Overtime
• Burden Transaction
• Expense Reports
• Inventory
• Miscellaneous Transaction
• Supplier Invoices
• Usages
• Work-in-Process
Expenditure Type Classes for Labor Costs

Oracle Fusion Projects uses the following expenditure type classes to process labor costs.
• Straight Time: Labor costs calculated using a base cost rate multiplied by hours.
• Overtime: Labor costs calculated using a premium cost rate multiplied by hours.
Expenditure Type Classes for Nonlabor Projects

Oracle Fusion Projects uses the following expenditure type classes to process nonlabor projects.
• Burden Transaction: Burden transactions track burden costs that are calculated in an external system or calculated
by Oracle Fusion Projects as separate, summarized transactions. These costs are created as a separate expenditure
item that has a burdened cost amount, and a quantity and raw cost value of zero.
You can adjust burden transactions that are not system-generated.
• Expense Reports: Expense reports imported from Oracle Fusion Payables or an external system.
276
Categorizations
Expense reports that you import into Oracle Fusion Projects must be fully accounted prior to import.
• Inventory: Inventory transactions imported from Oracle Fusion Inventory or an external system.
• Miscellaneous Transaction: Used to track miscellaneous project costs. Following are examples of miscellaneous
transactions.
◦ Fixed assets depreciation
◦ Allocations
◦ Interest charges
• Supplier Invoices: Supplier invoices, discounts, and payments from Oracle Fusion Payables or an external system,
and receipt accruals from Oracle Fusion Cost Management.
• Usages: You must specify the nonlabor resource for every usage item that you charge to a project.
For each expenditure type classified by a Usages expenditure type class, you also define nonlabor resources and
organizations that own each nonlabor resource.
• Work-in-Process: Used when you import work-in-process transactions from third-party applications or Oracle Fusion
Project Costing using Microsoft Excel or web services, or enter work-in-process transactions directly into Oracle
Fusion Projects.
Expenditure Type Class for Allocation Transactions: Points to

Consider
When defining an allocation rule, you must specify the expenditure type class for the allocation transaction attributes.
Choosing the expenditure type class determines how the allocated amount is created as costs on the expenditure item.
Miscellaneous Transactions
The miscellaneous transaction expenditure type class is used to allocate the source amount as raw cost on the expenditure
item.
Burden Transactions
The burden transactions expenditure type class is used to allocate the source amount as the burden cost for the expenditure
item, while expenditure item quantity and raw cost remain zero.
Related Topics
• Allocation Methods: Critical Choices
• Allocation Basis Methods: Critical Choices
• Project Cost Allocations: How They Are Processed
Expenditure Types: Explained

An expenditure type is a classification of cost that you assign to each expenditure item that you enter in Oracle Fusion
Projects. Create expenditure types for processing requirements, such as calculating raw costs, to classify costs, and to plan,
budget, forecast, and report on projects.
277
Categorizations
Following are examples of other ways that you can use expenditure types:
• Assign an expenditure type to each burden cost code when capturing burden costs on separate, summarized
expenditure items. The assigned expenditure type becomes the expenditure type for that type of burden cost.
• Specify default expenditure types for each resource class for different project units. The application uses the default
expenditure type for planning purposes. For example, when determining the raw and burdened cost rates for a
planning resource, if the resource format does not contain an expenditure type or nonlabor resource, then the
application uses the default expenditure type for the resource class of the resource to determine the rates.
• Labor cost multipliers are used to calculate costs for overtime expenditure items. Associate a labor cost multiplier to
an expenditure type with the Overtime expenditure type class. The costing process multiplies the standard labor cost
rate by the multiplier and the hours to calculate the cost for overtime expenditure items.
• Assign an expenditure type with the Usages expenditure type class to each nonlabor resource to define nonlabor
resources that are used to record usage transactions.
Expenditure types contain the following attributes.
• Expenditure and revenue categories
• Unit of measure
• Rate required
• Proceeds of sale
• Expenditure type classes
• Assigned sets
• Tax classification codes
Important
If you create and save an expenditure type, you cannot subsequently update the following attributes for the
expenditure type.
• Expenditure and revenue categories
• Unit of measure
• Rate required option
Instead, you must enter an end date for the expenditure type and create a new one. The end date for an
expenditure type has no effect on existing transactions. Oracle Fusion Projects uses the old expenditure type to
report on and process existing transactions.
Expenditure and Revenue Category

Expenditure categories group expenditure types for costing. Revenue categories group expenditure types for revenue and
billing.
Unit Of Measure
The expenditure type unit of measure is used as the default value on costing or planning transactions.
For inventory transactions, the primary unit of measure is from the inventory item, and not from the expenditure type on the
transaction.
You must use Hours as the unit of measure for labor expenditure types.
278
Categorizations
Rate Required Option

Enable the Rate Required option for an expenditure type that requires a cost rate.
Note
For supplier invoice expenditure types, if you specify that a rate is required, Oracle Fusion Projects requires you
to enter a quantity in Oracle Fusion Payables for invoice distributions using that expenditure type. When you
interface the invoice distribution to Oracle Fusion Projects, the application copies the quantity and amount to
the expenditure item and calculates the rate. If you define a supplier invoice expenditure type with the Rate
Required option disabled, then the quantity of the expenditure item is set to the amount you enter in Oracle
Fusion Payables.
Proceeds of Sale Option

Enable the Proceeds of Sale option for expenditure types that are used to track the proceeds of sale for a capital project.
Expenditure Type Classes

Expenditure type classes specify how an expenditure item is processed. For example, if you assign the Straight Time
expenditure type class to an expenditure type, Oracle Fusion Projects uses labor cost schedules to calculate the cost of an
expenditure item with that expenditure type and expenditure type class.
You can assign multiple expenditure type classes to an expenditure type. For example, an expenditure with the expenditure
type Materials can have the expenditure type class Supplier Invoice if it originated in Oracle Fusion Payables, and the
expenditure type class Inventory if it originated in Oracle Fusion Inventory. This allows you to use a single expenditure type
to classify as many costs as you need. You can use the same expenditure type for expenditures with different origins, and
therefore different accounting, that should otherwise be grouped together for costing, budgeting, or summarization purposes.
Assigned Sets
You must assign at least one project transaction type set to each expenditure type. You can add and delete set assignments
for an expenditure type at any time, except that you cannot delete the last set assignment for an expenditure type.
Tax Classification Codes

You can optionally select a default tax classification code to use for customer invoice lines for an expenditure type and
business unit.
FAQs for Manage Expenditure Categories and Types

Can I update or delete an expenditure category?
You can update expenditure category names and descriptions at any time. You cannot delete an expenditure category if it
is used in transaction controls, expenditure types, resource transaction attributes, or cost distribution organization overrides.
You can, however, stop usage of an expenditure category by setting an end date for it.
Can I assign multiple expenditure type classes to an expenditure type?

Yes. For example, an expenditure with the expenditure type Materials can have the expenditure type class Supplier Invoice
if it originated in Oracle Fusion Payables, and the expenditure type class Inventory if it originated in Oracle Fusion Inventory.
This allows you to use a single expenditure type to classify as many costs as you need. You can use the same expenditure
type for expenditures with different origins, and therefore different accounting, that should otherwise be grouped together for
costing, budgeting, or summarization purposes.
279
Categorizations
Can I distinguish cost of removal and proceeds of sale amounts when processing retirement
costs?
Yes. When capturing retirement costs in a capital project, enter proceeds of sale amounts using expenditure types specifically
created for that purpose. Oracle Fusion Projects automatically classifies amounts for all other expenditure types associated
with the retirement cost task as cost of removal.
Can I update or delete an expenditure type?

You can update expenditure type names, descriptions, and dates at any time. However, you can't update the following
attributes for the expenditure type: expenditure category, revenue category, unit of measure, rate required, and expenditure
type class.
To update these attributes, you must set an end date for the expenditure type and create another expenditure type with a
unique name.
You can't delete an expenditure type and the associated expenditure type class. However, you can stop the usage of an
expenditure type by setting an end date for it.
What's an expenditure category?

Describes and groups organization costs. For example, an expenditure category named Labor refers to the cost of labor.
An expenditure category named Supplier refers to the cost incurred on supplier invoices. You use expenditure categories for
budgeting, transaction controls, when you define organization overrides, and in accounting rules and reporting.
Manage Project Class Categories
Setting Up Class Categories: Points to Consider

You define project classifications to group projects. Project classifications include a class category and a class code. The
category is a broad subject within which you can classify projects, such as Industry Sector. The code is a specific value of the
category, such as Construction, Banking, or Health Care.
You specify the following options when setting up project classifications.
• Assign to all projects
• Assign to all project types
• Available as accounting source
• One class code per project
• Enter class codes percent
• Class codes
• Project types
Assign to All Projects

Enable this option if all projects must have a code assigned to this class category. Do not enable if this class category is
optional.
280
Categorizations
Assign to All Project Types

Enable this option if you want this class category to be required for projects of all project types.
Available as Accounting Source

This option indicates if the class category is available as an accounting source so that Oracle Fusion Subledger Accounting
can use the category to create mapping sets, account rules, journal line rules, and description rules.
Note
Only one class category at a time is available as an accounting source in Oracle Fusion Subledger Accounting. To
change the class category that Oracle Fusion Subledger Accounting uses, inactivate the old class category and
create a new one with a different date range.
One Class Code Per Project

Specify whether you want to allow entry of only one class code with this class category for a project.
Note
Defining multiple class codes for one category for a project may affect reporting by class category. For example,
defining multiple class codes may cause a code to be reported more than once.
Enter Class Codes Percent and Total Percent Must Equal 100
Enable this option if you want to associate percentages with the class codes associated with this category. When you have
multiple classification codes associated with a single class category, you can report the relative values of your projects in
terms of sales or a similar metric. When you enable this option, the application requires class code percentages for the
category regardless of the project type.
Enable the Total Percent Must Equal 100 option if you want the application to require that the sum of all class code
percentages to be 100% for the selected class category. You can clear this option at any time.
Class Codes
You can define class codes for the category to create more specific groups of projects for reporting. Assign each class code
to a reference data set so that only codes that are relevant to the project unit are available for the project.
Project Types
Associate project classifications with project types for the classification to be available for selection on projects with that
project type. You can add classifications to a project type definition, and add project types to a class category definition.
Select the Assign to all projects option for a project type if you require all projects of the project type to be associated with
the class category.
Related Topics
• Why do I specify a percentage for a class category and class code combination?
Using Class Categories: Examples

Class categories and class codes enable you to classify projects. The following example illustrates how you can use project
classifications.
281
Categorizations
Scenario
InFusion Corporation designs and implements heavy engineering projects for government and private customers. Because
InFusion Corporation maintains a diverse portfolio of contracts, the ability to track sector and funding is very important to
corporate management.
Therefore, the organization classifies projects by market sector and funding source. The following table describes the two
class categories used.
Class Category Assign to All One Class Code Enter Description

Projects per Project Percentage for
Class Codes
Market Sector Yes Yes No Market sector in

which project work
takes place.

A single class
code must be
provided on the
project for the
class category.

Funding Source Yes No Yes Source of funding

for project.

At least one class
code must be
provided on the
project for the
class category.
Percentages
must be provided
to indicate
contribution for
each source.

The following table describes the class codes available for the categories specified above.
Class Category Class Code Description
Funding Source Private Project funded by private

organizations

Funding Source Federal Project funded by the federal

government

282
Categorizations
Funding Source State or Local Project funded by a state or local

government

Funding Source Foreign Project funded by a foreign

government

Market Sector Utilities Project involves utility or power

plant construction

Market Sector Waste Project involves waste disposal or

recycling facility constructions

Market Sector Mechanical Project involves mechanical design

and engineering work

Market Sector Structural Project involves structural design


InFusion management can easily assess projects based on the above class categories and codes.
For example, you specify a class category Funding Source on your project. With this category, you select two class codes:
Private and Federal. If you assign 30 percent to Private and 70 percent to Federal, then you indicate the proportion of funding
received for your project from the two sources.
On the other hand, because you must select a single market sector, you indicate whether project work involves utilities,
waste, mechanical, or structural activities.
Manage Work Types
Work Types for Billing: Explained

A work type represents a classification of work. You use work types to classify both actual and scheduled work. The billable
status of a work type assigned to a scheduled assignment determines the default billable status of scheduled work.
In billing, you can use work types to classify work for the following purposes:
• To determine the default billable status of expenditure items.
• To classify cross-charge amounts into cost and revenue for cross-charge transactions.
Billable Project Work

The default billable status of scheduled work is determined by the billable status of the work type assigned to the scheduled
assignments. You can also control the billable status of actual work by the work type assigned to actual transactions. If
283
Categorizations
you choose to do this, then you must change the work type on an actual transaction to change the billable status of the
transaction. It is recommended that you do this in order to maintain consistency between processing of actual transactions
for customer billing and reporting for billable utilization.
Tip
To use work types to determine whether an expenditure item is billable you must set the profile option Work Type
Derived for Expenditure Item to Yes.
Cross-Charge Work
Cross-charge work is project work performed by resources from one organization on a project belonging to another
organization.
Typically the project-owning organization provides some compensation to the resource organization for this cross-charge
work. The compensation can be in the form of sharing revenue with the resource organization or taking on the cost from the
resource organization. This allows each organization to be measured on its performance independent of one another. You
can classify the transfer price amount type of cross-charge work into cost or revenue based on the work type assigned to
project work: scheduled or actual.
FAQs for Manage Work Types

What's a work type?
A classification of actual work. For example, a professional services enterprise may define work types such as Analysis,
Design, and External Training. Use work types to determine the billability of expenditure items and to classify cross-charge
amounts into cost and revenue.
When you create or import expenditure items, the default work type is inherited from the associated task. Tasks, in turn,
inherit work type values from parent tasks and ultimately from the project. Project types determine the default work type value
for projects and project templates.
Manage Project Statuses
Project Status Components: How They Work Together

Oracle Fusion Projects uses statuses for projects and progress.
• The Project status type controls which processes are allowed during each stage of a project.
Oracle Fusion Projects provides the following predefined project statuses.
◦ Unapproved
◦ Submitted
◦ Approved
◦ Rejected
◦ Pending close
284
Categorizations
◦ Closed
• The Progress status type specifies overall progress of a project, task, or resource. Progress statuses are used for
reporting and do not control what you can do with a project.
Following are the predefined progress statuses:
◦ On track
◦ At risk
◦ In trouble
You can define additional project and progress statuses based on the available system statuses to meet your business
needs.
Status Attributes
Each status is associated with a status type and a system status. Optionally you can specify status attributes for initial project
status and workflow.
• Status Type: Types are Project or Progress.
• System Status: Determines which actions are allowed for the project or progress status. Every status must map to
a predefined system status.
• Initial Project Status: If this option is enabled for a project status, and if the project status belongs to a reference
set that is associated with the project unit of the project, then the status is eligible for use as the starting status for
the project.
Initial starting status does not apply to progress statuses.
• Workflow Attributes: Oracle Fusion Projects provides an approval workflow that allows you to separate project
creation from project approval. If you enable workflow for a status, the approval workflow begins when a project
changes to that status.
Project status approval workflow includes these attributes:
◦ Status After Change Accepted: The status that the application assigns to the project when a project status
change is approved.
◦ Status After Change Rejected: The status that the application assigns to the project when a project status
change is rejected.
The project status after workflow is rejected can be the same as the current status.
Workflow attributes do not apply to progress statuses.
Assigned Sets
You assign project statuses to reference data sets so that only statuses that are relevant to the project unit are available for
the project.
285
Categorizations
Important
Before you can select a status for a project, the status must belong to a reference data set that is associated with
the project unit of the project.
Status Controls
Status controls for a system status determine which actions are allowed for projects in a project status that is associated with
the system status.
The following actions are controlled with status controls:
• Adjust transactions
• Capitalize assets
• Capitalized interest
• Create burden transactions
• Create new transactions
• Summarize project data
By default, all actions are allowed for projects in an Approved system status.
Not all of the default status controls are editable. For example, if a project status is associated with the Closed system status,
you cannot change the status controls to allow the creation of new transactions.
Status controls do not apply to progress statuses.
Next Allowable Statuses

Next allowable statuses specify which statuses are permitted as the new status when a status is changed manually. You
must define next allowable statuses for each project status.
Defining the next allowable statuses determines the project process flow. For example, you can specify that a project with a
Requested status can have the status changed to either Approved or Rejected. This example shows two possible process
flows for the project: Requested to Approved status, or Requested to Rejected status.
The following four options are available when you specify the next allowable statuses:
• All: The current status can change to any status. This is the default value.
• None: The current status cannot change.
• System Status: The next allowable statuses are based on system statuses. Specify which system statuses are next
allowable statuses.
• Status Name: The next allowable statuses are based on project statuses. Specify which project statuses are next
allowable statuses.
Next allowable statuses do not apply to progress statuses.
Project Status Change Workflow: Explained

Oracle Fusion Projects provides a default Project Status Change workflow process. If you enable workflow for a project
status, the approval workflow begins when a project changes to that status. The default workflow process routes a request
286
Categorizations
for approval of the project status change to the project manager. You can use client extensions to modify the default
workflow process to accommodate the needs of your business.
The following diagram shows the process of changing a project status.
Project Status Change Workflow Settings

During implementation, you specify the project statuses that require approval before a project changes to that status.
For each project status with workflow enabled, you can also specify the following parameters:
• The status that the application assigns to the project when a project status change is accepted.
• The status that the application assigns to the project when a project status change is rejected.
For example, assume that during implementation, you enable workflow for the Submitted status, and configure the following
workflow attributes:
• In the Status After Change Accepted field for the Submitted project status, you specify the Approved status as
the status that the application assigns to the project when the status change is accepted.
• In the Status After Change Rejected field for the Submitted project status, you specify the Rejected status as the
status that the application assigns to the project when the status change is rejected.
In this example, when a requester changes the project status to Submitted, the workflow process routes the status change
request to the project manager's worklist. If the project manager accepts the status change, the workflow process assigns
the Approved status to the project. If the project manager rejects the status change, the workflow process assigns the
Rejected status to the project.
Workflow attributes do not apply to progress statuses.
287
Categorizations
The following diagram shows an example project status flow when Project Status Change workflow is used for status
changes during the lifecycle of a project. In this example, a requester changes the project status to Submitted. A workflow
notification is sent to the project manager, who accepts the status change. Workflow is configured to change the project
status to Approved after a request to change the status to Submitted is accepted. After project completion, the requester
changes the project status to Pending Close. A workflow notification is sent to the project manager, who accepts the status
change. Workflow is configured to change the project status to Close after a request to change the status to Pending Close is
accepted.
Project Status Change Workflow Extensions

You can extend the functionality of Project Status Change workflow by using the following client extensions:
• Project Status Change Approver Extension: Overrides the project status change approver.
Use this client extension to specifying a status change approver other than the project manager. By default, the
project status change approver is the active project manager.
• Project Status Change Workflow Enabled Extension: Determines whether to call the workflow process when the
project status changes.
Use this extension to add and modify the conditions that enable workflow for project status changes.
288
Categorizations
• Project Status Change Rules Extension: Specifies the conditions that must be satisfied before a project status can
change.
Use this extension to build additional rules for changing a project status. For example, you can enforce a rule that
certain class categories and class codes must be assigned to a project before you can change the project to an
Approved status.
289
Implementing Project Financial Management Project Foundation Configuration: Define Project Roles

Project Roles
Project Roles in Budgeting and Forecasting:

Explained
Default project roles, including project application administrator, project manager, and project administrator can perform
specific budgeting and forecasting tasks.
Default Access for Roles

The following table describes the default access for each role.
Entitlement Area Project Project Manager Project Notes

Application Administrator
Administrator
Edit budget and Yes No No Project application

forecast planning administrators set
options planning options
for financial plan
types.

Project managers
and accountants
can view planning
options at the
version level.

Create versions No Yes Yes None

Generate versions No Yes Yes Applies to budgets

generated when
setting a baseline
for the project
plan.

Project
administrators
can't generate
forecasts from
progress (they
don't have
access to publish
progress.)

290

Administrator
Edit versions in No Yes Yes None

Excel

Submit versions No Yes Yes None

Approve versions No Yes No A team member

with project
manager security
role access must
be manually
designated as the
project manager
for the project.

Note
Project
creators
aren't
automatically
designated
as project
managers
for their
projects.

If workflow
is enabled,
then approval
occurs through a
notification. Menu
actions aren't
available on the
budgeting and
forecasting pages.

Review versions No Yes Yes None

291
FAQs for Define Project Roles
What's a project role?

Project roles represent either a requirement or an assignment on a project, such as a project manager or project team
member.
You associate an enterprise role with each project role. When you assign a project role to a project team member, the
associated enterprise role determines the type of access the team member has to project information. For example, project
managers can manage project progress or create budgets and forecasts. Project team members may only have access to
view progress or financial plans.
When you create a project role, you assign it to one or more reference data sets so that only project roles that are relevant to
the project unit are available to assign to project team members.
Important
Persons who are directly assigned enterprise roles such as Project Manager or Project Application
Administrator may have access to certain project information even if they are not project team members or do
not have a specific project role assignment.
What's the difference between a job title and a project role?

A job title represents the function of a person within an organization and the position within a reporting hierarchy. For
example, your organization may have designations or job titles such as software developer, sales representative, or accounts
manager.
Project roles represent either a requirement or an assignment on a particular project, for example, project manager. Project
roles may differ from project to project.
292
Implementing Project Financial Management Project Foundation Configuration: FAQs for Enable Automated
Project Spaces
14 Project Foundation Configuration: FAQs for

Enable Automated Project Spaces
How are project space roles mapped to project

resources?
The application automatically assigns each project resource to a project space role on the associated project space. The
project manager is assigned the role of project space moderator. All other project resources are project space participants.
Project space moderators can manually add additional participants or modify participant access, if required.
293
Implementing Project Financial Management Project Foundation Configuration: Define Project Resources

Project Resources
Manage Resource Classes
Resource Formats and Resource Classes: How They Work

Together to Create Planning Resources
The resources you can create for planning and billing resource breakdown structures are determined by a combination of
predefined resource classes and the resource format hierarchies you select for use.
Resource Formats and Resource Format Hierarchies

Before creating planning or billing resources, you must select the resource formats and resource format hierarchies you want
to use on your resource breakdown structure. For example, if you want to plan for project-related expenses such as air fare,
then you must select resource format hierarchies created using the resource type Expenditure Type.
Also, as resource format hierarchies support up to three levels, selecting from the available hierarchies enables you to
determine the granularity with which resources are created.
For example, for planning resource breakdown structures used for high-level or preliminary planning, you may decide to
enable only the Resource Class resource format. You can then create and use planning resources representing the four
resource classes: Labor, Equipment, Material Items, and Financial Resources.
To plan in greater detail, you may decide to use a two-level resource format hierarchy, such as Resource Class: Job or
a three-level hierarchy such as Resource Class: Job: Named Person. You can then create a resource such as Labor:
Electrical Engineer or Labor: Electrical Engineer: Chris Black.
Note
Selecting more granular resource formats automatically selects resource formats higher up within the same
hierarchy. For example, if you select the resource format Expenditure Type: Named Person: Job, then the
resource formats Expenditure Type: Named Person and Expenditure Type are automatically selected for use.
Resource Classes
Resource classes influence the creation of planning and billing resources in the following ways:
• Resource class as a resource format: As mentioned earlier, Resource Class is a resource type that is available for
use within resource format hierarchies on planning and billing resource breakdown structures.
• Predefined association with resource formats: For each resource format, you can create planning or billing resources
based on certain resource classes. For example, if the resource format contains Job, then the only available resource
class is Labor. However, if the resource format is Expenditure Category, then you can select any of the resource
classes (Labor, Material, Equipment, and Financial Resources) when you create a resource.
Related Topics
• Resource Formats: Explained
294
Resource Classes: Explained

Resource classes are predefined classification of resources. For each resource class, you can define specific attributes that
associated planning resources inherit.
Following is a description of the available resource classes and their attributes.
Available Resource Classes

The resource classes available in Oracle Fusion Projects are as follows:
Resource Class Description
Labor Named persons or any grouping of named persons

whose time capacity is consumed to complete project
work. Named persons may be grouped by attributes
such as job, organization, or role.

Equipment Nonperson resource such as machinery, equipment,

or facilities with time capacity that is consumed
to complete project work. Examples include
telecommunication charges (charged by call), or shared
facilities or laboratory (charged for hours used).

Material items Resources that are physically tracked as inventory,

subassembly, work in progress (WIP), purchasable
items, or finished goods.

Financial resources Resources that have a financial value for the project.
These resources use Currency as the unit of measure.

Resource Class Attributes

The attributes you can define for each resource class are as follows:
Attribute Description
Spread curve Determines how planned amounts for a planning

resource are spread across the duration of the project or
financial plan.

You can change the spread curve that you select for a
resource class at the planning resource level and for any
corresponding task assignments, or budget or forecast
lines.

295
Attribute Description
Item master and category set Determine the material item and item category lists
used in planned transactions and planning, billing, and
reporting resource breakdown structures.

Expenditure types Determine default raw and burdened rates for a planning
resource. For example, if the resource format does not
contain an expenditure type or nonlabor resource, then
the application uses the default expenditure type for the
resource class of the resource to determine the rates.

You must individually specify expenditure types for
project units.

Resource Class Rate Schedules

Create rate schedules for resource classes that you can use for project and financial planning. When creating resource class
rate schedules, you can specify both rates and markup percentages for each combination of resource class and organization.
Note
Markup percentage takes precedence for amount-based transactions where the unit of measure is Currency.
You specify a resource class rate schedule in the planning options for a financial or project plan type, project plan, or
financial plan version as the source for rates or markup percentages, unless they are available elsewhere. For example,
assume you are using actual rates on your financial plan version. If one of the planning resources is an expenditure category,
then resource class rate schedules are used to derive rates for that resource because actual rates are not maintained for
expenditure categories.
Manage Job Mappings
Job Mapping: Explained

Job mapping enables you to associate granular human resource jobs to less-detailed project jobs that you can use for project
management.
Job titles usually reflect human resource characteristics and can vary across countries or units, even within the same
enterprise. For example, you may have a project manager in the United States and a chef de projet in France. However, when
managing projects, especially global ones, you may want to use the same job definitions for all resources rather than unique
jobs that are defined by each resource-owning organization. These common, or global, jobs ease the maintenance of costing
rates and processes.
Following is a description of job mapping and a brief example.
Mapping Jobs
You map jobs from two job sets through an intermediate job set. That is, you must map jobs in your human resource jobs
sets to jobs from an intermediate set of jobs. You then map the jobs in the intermediate job set to jobs in your project job
sets.
296
For each combination of From Job Set, Intermediate Job Set, and To Job Set, you manually associate the intermediate
job to the to job only once. For subsequent mappings, the to job is displayed automatically when you select the intermediate
job and cannot be modified.
For example, and as illustrated in the following diagram, assume you want to map jobs from Human Resources Job Set to
Projects Job Set through an intermediate job set called Master Job Set. Within the Human Resources Job Set, you want to
map jobs Construction Worker and Forklift Operator to a single job called Laborer in the Projects Job set.
You first select Construction Worker as the from job, Master Laborer as the intermediate job, and Laborer as the to job. The
intermediate job Master Laborer and the to job Laborer are now linked. Next, when you select Forklift Operator as the to job
and Master Laborer as the intermediate job, Laborer is displayed automatically as the to job.
After you map the jobs, you can use the single job Laborer for project management purposes.
Creating a Job Mapping: Example

Job mapping enables you to associate granular human resource jobs to less-detailed project jobs that you can use for project
management. The following example illustrates how you map jobs from two job sets using an intermediate job set.
Scenario
InFusion Corporation is a global enterprise with business units in the United States and France. The following table lists
sample job titles in those two countries.
297
Job Set Jobs
United States Job Set Manager

Staff Consultant

Senior Consultant

Design Engineer

Electrical Engineer

Construction Worker

France Job Set Chef de Projet

Ingenieur Formateur

Architecte

Ouvrier

For project work, InFusion Corporation uses the following generic job roles, created for the Global job set:
• Project Manager
• Consultant
• Architect
• Laborer
To map the global jobs to country-specific jobs, InFusion Corporation created an intermediate job set, called the Master job
set, with the following jobs:
• Master Project Manager

• Master Consultant
• Master Architect
• Master Laborer
Jobs are mapped as follows for the United States job set:
Job in From Job Set Job in Intermediate Job Set Job in To Job Set
Manager Master Project Manager Project Manager

Staff Consultant Master Consultant Consultant

Senior Consultant Master Consultant Consultant

298
Design Engineer Master Architect Architect

Electrical Engineer Master Architect Architect

Construction Worker Master Laborer Laborer

Jobs are mapped as follows for the France job set:
Chef de Projet Master Project Manager Project Manager

Engenieur Formateur Master Consultant Consultant

Architecte Master Architect Architect

Ouvrier Master Laborer Laborer

InFusion Corporation associates the Global job set to its planning resource breakdown structures. Therefore, jobs such as
Project Manager and Laborer are available for creating planning resources. In addition, the Global job set is used to define
rates that can are then used for costing, invoicing, and financial planning.
FAQs for Manage Job Mappings

How can I map a human resource job to a project job?
You map jobs from two job sets through an intermediate job set. That is, you must map jobs in your human resource jobs
sets to jobs from an intermediate set of jobs. You then map the jobs in the intermediate job set to jobs in your project job
sets.
For example, you can map the human resources jobs Construction Worker and Forklift Operator to a single projects job
called Laborer through the intermediate job Master Laborer. After you have mapped your jobs, you can use the single job
Laborer for your project management purposes.
What's a job set?

An organizational partition of jobs. Use job sets to define how you create jobs and use them in your business. Define a single
set of jobs or separate job sets for each country or line of business.
For example, assume that the set of jobs your business uses for project management is less granular than the set of jobs for
human resource. You can define generic jobs for your project job set and map it to the human resource job sets. Associating
the project job set with planning, reporting, and billing resource breakdown structures ensures appropriate project reporting,
costing, invoicing, and revenue generation.
299
Manage Nonlabor Resources
Nonlabor Cost Rates: How They Are Determined

Oracle Fusion Projects uses cost rates to calculate the raw cost for transactions. For example, for cost transactions, the
application determines a cost rate for each transaction and calculates the raw cost during transaction costing, unless you
import the raw cost for transactions.
How Nonlabor Cost Rates Are Determined

Oracle Fusion Projects applies the following rules to determine the cost rate for each transaction.
1. The application uses an organization costing rule to determine the nonlabor cost rate schedule, using the following
logic. At each level, the application searches for a rule with a date range that includes the transaction date.
a. Organization costing rule for the expenditure organization.
The application searches for an active costing rule assigned to the organization of the transaction on the date
of the transaction.
b. Organization costing rule for the parent expenditure organization.
If an organization costing rule for the expenditure organization is not found, the application searches for a rule
assigned to the parent organization of the expenditure organization, and continues up the project expenditure
organization hierarchy until a rule is found.
You specify the project expenditure organization hierarchy for the business unit during implementation.
If an organization has multiple parent organizations, and a rule is assigned to more than one parent, the
application uses the rule assigned to the lowest level parent organization.
c. Organization costing rule for the business unit.
If no costing rule is found for the expenditure organization and parent organization, the application uses the
costing rule assigned to the business unit for the transaction.
2. The application uses the nonlabor rate schedule and then applies the cost rate that is associated with the unique
combination of expenditure type, nonlabor resource, and nonlabor resource organization.
3. If a cost rate does not exist for the combination of expenditure type, nonlabor resource, and nonlabor resource
organization, then the application uses the cost rate for the expenditure type and nonlabor resource combination
that is applicable to all nonlabor resource organizations to which the nonlabor resource belongs.
Note
This rule applies to cost transactions only. For billing and planning transactions, you can either not use
a nonlabor resource organization, or map the nonlabor resource organization to the organization that
maintains the rate schedule.
4. If a cost rate does not exist for the combination of expenditure type and nonlabor resource, then the application
uses then the applications uses the cost rate defined for the expenditure type.
300
If a rate is not found at any of these levels, then an error is generated for the transaction.
Related Topics
• Rate Schedule Types: Explained
Turning Equipment into Nonlabor Resources: Example

This example illustrates setting up assets as nonlabor resources.
Scenario
You are asked to set up nonlabor resources and assign them to the appropriate organizations for the InFusion Corporation.
Defining Nonlabor Resources

InFusion Corporation wants to capture costs for computer equipment, vehicles, survey equipment, and other assets.
In this example, assume that expenditure types and organizations are already set up, which are prerequisites of defining
nonlabor resources.
The Other Assets expenditure type is assigned to all divisions. This nonlabor resource captures miscellaneous items.
Analysis
To define a nonlabor resource, you specify a name and description of each asset, such as a piece of equipment or pool of
assets, and a date range during which the resource can be used.
For each nonlabor resource, you must choose an expenditure type with the Usage expenditure type class. Every usage item
that you charge to a project must specify the nonlabor resource utilized and the nonlabor resource organization that owns
the resource. You can select organizations that are classified as project and task owning organizations or project expenditure
organizations.
A nonlabor resource may be a piece of equipment with capacity that is consumed, such as a training room, or equipment
with physical output that is consumed, such as a copier. Enable the Equipment resource class to plan and report nonlabor
resources as equipment with capacity that is consumed.
Nonlabor Resource Details

The following table shows the nonlabor resources for InFusion Corporation.
Resource Description Expenditure Equipment From Date Organizations

Name Type Resource
Class
Laptop Laptop on the Computer Not enabled January 1, Data Systems

Headquarters Services 2011
Network Finance

Information
Services

Risk Analysis

301

Name Type Resource
Class
HQ SPARC Headquarters Computer Not enabled January 1, Information

T3-1 Server Sparc Services 2011 Services
Enterprise
Server

Oracle Data Systems Computer Not enabled January 1, Data Systems

Exadata Oracle Services 2011
Storage Storage
Server Server

Oracle Solaris Engineering Computer Not enabled January 1, InFusion

Studio and Services Services 2011 Engineering
Oracle
Development InFusion
Platform Services

Survey Standard Field Enabled May 1, 2011 InFusion

Surveying Equipment Engineering
Equipment

Van Heavy Duty Vehicle Not enabled January 1, InFusion

Van 2011 Construction

West

Midwest

East

South

International

Minivan Site Visit Vehicle Not enabled August 1, InFusion

Minivan 2011 Construction

West

Midwest

East

South

International

302

Name Type Resource
Class
Pickup Truck Heavy Duty Vehicle Not enabled January 1, West

Pickup Truck 2011
Midwest

East

Other Asset Other Asset Other Assets Not enabled January 1, Administration
2011
InFusion
Construction

InFusion
Engineering

InFusion
Services

FAQs for Manage Nonlabor Resources

What's a nonlabor resource?
An asset or a pool of assets. For example, a nonlabor resource can be a piece of equipment with capacity that is consumed,
such as training room, copier.
When you create a nonlabor resource, ensure that organizations and expenditure types exist. You can associate nonlabor
resources with Usages expenditure type class only.
Note
To plan and report on equipment, enable the Equipment resource class and specify Hours as unit of measure for
the expenditure type.
What's a nonlabor resource organization?

The organization to which a nonlabor resource is assigned. For example, Survey is a nonlabor resource, represents the survey
equipment, is assigned to the Engineering organization or another nonlabor resource, PC, represents a pool of personal
computers, and is assigned to multiple organizations such as Information Services, Finance, and Engineering.
You can assign nonlabor resources to any organization in the organization hierarchy, regardless of the Project Expenditure
Organization classification and organization date range.
Every usage item that you charge to a project must specify the nonlabor resource utilized and the nonlabor resource
organization to which the resource is assigned.
303
Implementing Project Financial Management Project Foundation Configuration: Define Rate Schedules and
Costing Rules
16 Project Foundation Configuration: Define Rate

Schedules and Costing Rules
Manage Rate Schedules
Rate Schedule Types: Explained

Schedule types determine usage for rates within rate schedules. You specify a schedule type for rate schedules created for
costing, billing, or planning purposes in Oracle Fusion Projects.
The schedule types are:
• Job
• Person
• Nonlabor
• Resource class
Job
Job rate schedules contain rates used to calculate amounts for the following types of labor transactions:
• Costing
• Billing (invoice and revenue)
• Planning
• Budgeting
• Forecasting
• Transfer price
The rate is based on the standard hourly rate assigned to a job title in Oracle Fusion Human Capital Management.
If you are using planning rates for financial or project planning, you can select a specific job rate schedule when configuring
rate settings at the plan type or project level. Job rate schedules are used if rates cannot be derived from the person labor
rate schedule.
When creating a job schedule type, you must select a job set from Oracle Fusion Human Capital Management. The job set is
the source of jobs in your rate schedule. Assign rates or markup percentages to jobs in the rate schedule.
Person
Person schedules contain raw cost rates and billing rates or markup percentages for labor transactions and transfer price
amounts. The rate that calculates the cost or billing amount for a project transaction is based on the standard hourly rate
or markup percentage assigned to a person, or the job or organization assigned to the person in the schedule. The job or
organization is based on the person's assignment in Oracle Fusion Human Capital Management.
You have the option of assigning rates to the following:
• Person
304
Costing Rules
• Person and job
• Person, job and organization
If you assign a rate to a person and job combination, that rate has precedence over the person rate. If you assign a rate to a
person, job and organization combination, that rate has precedence over the person rate or person and job combination.
If you are using planning rates for financial or project planning, you can select a specific person rate schedule when
configuring rate settings at the plan type or project level. Person rate schedules are used if rates cannot be derived from the
labor rate schedule.
Nonlabor
Nonlabor rate schedules contain rates or markup percentages that calculate cost, bill, revenue, plan, budget, forecast, or
transfer price amounts for nonlabor resources.
Enter a rate or markup percentage for expenditure types with the Rate Required option enabled. Otherwise, assign it only a
markup percentage. Assign rates to nonlabor resources and optionally define rates for nonlabor resource organizations.
If you are using planning rates for financial or project planning, you can select a specific nonlabor rate schedule when
configuring rate settings at the plan type or project level.
Resource Class
Resource class schedules contain the planning rates or markup percentages for a resource class or a combination of
resource class and organization. You optionally assign a resource class schedule to a project plan or financial plan (budgets
and forecasts) at the plan type level or version level. The resource class rate schedule determines rates for the associated
resources if the rates cannot be derived elsewhere.
Enter a rate or markup percentage for each resource class in the rate schedule. Optionally, assign the rate or markup
percentage to a specific organization for a resource class.
Related Topics
• Selecting Rate Schedules for Project and Financial Planning: Points to Consider
• Invoice and Revenue Rates: How They Are Determined
• Job Mapping: Explained
Labor Cost Rates: How They Are Determined

Oracle Fusion Projects uses cost rates to calculate the raw cost for expenditure items. The application determines a cost rate
for each expenditure item and calculates the raw cost during cost distribution processing, unless you import the raw cost for
expenditure items.
How Labor Cost Rates Are Determined

When you assign a labor costing rule and a rate schedule to an organization, Oracle Fusion Projects applies the following
rules in the order presented to determine the labor costing rule for each transaction.
1. Oracle Fusion Projects determines whether any labor costing overrides exist for the employee who is associated
with the expenditure item. The application uses the effective dates for the labor costing overrides to determine
whether an override is active on the expenditure item date. A labor costing override can have either an overriding
cost rate or an overriding rate schedule. If a labor costing override applies, then Oracle Fusion Projects uses it to
determine the cost rate.
Labor expenditure items always have a unit of measure of Hours.
305
Costing Rules
For labor transactions, the application searches for a labor costing override in the following order.
a. Person, job, and organization combination
b. Person and job combination
c. Person
2. If no override exists, Oracle Fusion Projects uses an organization costing rule to determine the cost rate. The
following logic determines the cost rate. At each level, the application searches for a rule with a date range that
includes the expenditure item date.
a. Organization costing rule for the expenditure organization
The application searches for an active costing rule assigned to the organization of the expenditure item on
the date of the transaction.
b. Organization costing rule for the parent expenditure organization
If an organization costing rule for the expenditure organization is not found, the application searches for a rule
assigned to the parent organization of the expenditure organization, and continues up the project expenditure
organization hierarchy until a rule is found.
You specify the project expenditure organization hierarchy for the business unit during implementation.
If an organization has multiple parent organizations, and a rule is assigned to more than one parent, the
application uses the rule assigned to the lowest level parent organization.
c. Organization costing rule for the business unit
If no costing rule is found for the expenditure organization and parent organization, the application uses the
costing rule assigned to the business unit for the expenditure.
Oracle Fusion Projects applies the costing rule to determine the cost rate for the expenditure item. You can associate either a
rate schedule, or a Labor Costing extension with an organization labor costing rule, to determine the cost rate.
FAQs for Manage Rate Schedules

Why can't I find persons in the list of resources when I enter team members, planning
resources, or person rate schedules?
You can't find persons in the list of resources when you enter team members, planning resources, or person rate schedules
in the following situations:
• The administrator did not assign a department while creating users. Persons must have an active assignment and
be assigned to a department in Oracle Fusion Human Capital Management before they can be added as team
members or entered as resources on the planning resource breakdown structure or person rate schedule.
• The resource is not active in Oracle Fusion Human Capital Management because the current date is before the
effective date of the resource. If you want to include persons who will start in the future, select the Include people
with future-dated effective start dates option when you search for the person.
• Persons assigned as project managers are not active as of the project start date.
306
Costing Rules
Manage Labor Costing Multipliers
Creating Labor Costing Multipliers: Examples

A labor costing multiplier is a value by which Oracle Fusion Projects multiplies an employee's labor cost rate to calculate
the employee's overtime premium cost rate. This is represented by the formula: labor cost rate * labor costing multiplier =
overtime premium labor cost rate.
Oracle Fusion Projects then multiplies the overtime premium labor cost rate by the number of overtime hours that an
employee works to calculate the overtime premium for the employee. This is represented by the formula: overtime premium
labor cost rate * overtime hours = overtime premium.
Labor Costing Multipliers

You define a labor costing multiplier for each kind of overtime your business uses such as double time, or time and a half.
For example, if you pay an employee double time for all overtime hours, you define a labor cost multiplier of 1.0. You multiply
the employee's labor cost rate by 1.0 to calculate the employee's overtime premium labor cost rate. If you pay an employee
time and a half for all overtime hours, you define a labor cost multiplier of 0.5 to calculate the employee's overtime premium
labor cost rate. An employee's total labor cost is the overtime premium plus the total number of hours that employee worked
multiplied by the employee's labor cost rate. This is represented by the formula: overtime premium + (total hours x labor cost
rate) = total labor cost.
The following table shows examples of labor cost multipliers for double time, time and a half, and uncompensated overtime.
The negative multiplier for uncompensated overtime reverses the cost of any overtime hours for the individuals who do not
get paid overtime.
Labor Costing Multiplier Name Multiplier
Double Time 1.0

Time and a Half 0.5

Uncompensated Overtime -1.0

Manage Labor Costing Rules
Labor Costing Rules: Explained

A labor costing rule determines how an employee is paid. For example, you can define a labor costing rule for pay types such
as exempt, nonexempt, uncompensated, compensated, and hourly.
When an employee charges time to a project, Oracle Fusion Projects processes the labor hours according to the employee's
labor costing rule. For example, if an employee's labor costing rule is Hourly, the employee is eligible for overtime pay; if the
employee's labor costing rule is Exempt, the employee is not eligible for overtime pay.
307
Costing Rules
Following are the key components of a labor costing rule:
• Costing method
• Overtime labor costing multipliers
• Default overtime transaction attributes
Costing Method
For labor costing rules with the Rates costing method, labor costs are calculated for entered hours using hourly cost rates.
For labor costing rules with the Extension costing method, labor costs are calculated by the Labor Costing extension. When
you use the Extension costing method, you are not required to maintain hourly cost rates in Oracle Fusion Projects.
Overtime Labor Costing Multipliers

If your employees enter overtime hours manually, you can assign cost multipliers to overtime expenditure types. When you
use the Rates costing method, and a transaction is charged to an expenditure type that has an assigned multiplier, the
application applies the multiplier as labor costs are calculated.
To calculate rates for overtime expenditure items, before you define labor costing rules, you must define an expenditure type
with the Overtime expenditure type class.
If overtime hours are calculated using the Overtime Calculation extension, you can specify the default expenditure types for
the overtime expenditure items generated by the extension.
Default Overtime Transaction Attributes

If overtime hours are created by the Overtime Calculation extension, you can specify the default business unit, project, and
task that incur the overtime costs generated by the extension. These attributes apply only if you use the Overtime Calculation
extension to calculate overtime hours.
Related Topics
• Overtime Calculation Extension
Defining Labor Costing Rules: Example

This example illustrates setting up labor costing rules to calculate overtime labor costs.
Scenario
You are asked to set up labor costing rules to calculate overtime labor costs for nonexempt and hourly employees for the
InFusion Corporation.
Overtime Costs
InFusion Corporation uses the Overtime Calculation extension to calculate overtime hours for nonexempt employees. All
overtime premium costs for nonexempt employees are charged to an indirect project.
Hourly employees are required to enter overtime hours manually. All labor costs, including overtime premiums, are charged to
the project and task indicated on the timecard.
308
Costing Rules
Analysis
For nonexempt employees, the expenditure types for overtime transactions created using the Overtime Calculation extension
are derived from the overtime labor cost multipliers that are assigned to the labor costing rule.
For hourly employees, when time is charged to an overtime expenditure type, the application applies the costing multiplier
assigned to the labor costing rule when labor costs are calculated.
Labor Costing Rule Details

The following table shows the labor costing rules for InFusion Corporation:
Labor Costing Rule Costing Method Project Task
Nonexempt Rates Overtime Time and a Half

Hourly Rates

The following table shows the overtime labor cost multipliers that are associated with the labor costing rules:
Labor Costing Rule Expenditure Type Labor Cost Multiplier
Nonexempt Overtime Time and a Half

Hourly Overtime Time and a Half

Hourly Premium Overtime Double Time

Manage Labor Costing Overrides
Setting Up Labor Costing Overrides: Critical Choices

You can override the labor costing definition for individual employees and contingent workers for a business unit. The
application uses a labor costing override to determine the labor rate for cost transactions, and to plan, budget, and forecast
transactions when you use an actual plan type.
Following are the key implementation concepts for setting up labor costing overrides:
• Override for a Person, Job, And Organization
• Override by Rate, Rate Schedule, or Extension
• People with Future-Dated and Terminated Assignments
309
Costing Rules
Override for a Person, Job, and Organization

You specify the labor costing override for a person, or for a more granular override, specify a combination of person and job,
or person, job, and organization.
The job and organization represent the human resources job and organization of the person. The jobs that you can select to
associate with a labor costing override are based on the person value. The organizations that you can select are based on the
job value. When you select a job, an organization is automatically selected by default. The default organization value is based
on the selected job assignment. You can accept the default organization for the labor costing override, select a different
organization that is associated with the job and person, or remove the organization so the labor costing override is for person
and job combination.
In the example shown in the following table, a person is assigned the Nurse job in two different organizations. When you
select Nurse to create a labor costing override, the application automatically selects the default organization General Hospital.
You can accept the General Hospital default organization, or change the selection to the University Hospital organization, to
create an override for the person, job, and organization combination. Alternatively, you can remove the organization value to
create an override for the person, job, and any organization.
Job Department Organization Person Type Primary
Nurse Administration General Hospital Employee Yes

Nurse Optometry University Hospital Contingent Worker No

Override by Rate, Rate Schedule, or Extension

When you use a labor costing override, an override rate, rate schedule, or extension takes precedence over a standard rate
schedule for the business unit.
When you select a labor costing rule for the override, if the costing method of the rule is Extension, then the override type is
Extension by default. If you do not select a labor costing rule, you cannot select an override type of Extension.
People with Future-Dated and Terminated Assignments

You can set up labor costing overrides for people with a start date in the future if you enable the People with Future Effective
Start Dates as Project Members Allowed profile option. You can set up labor costing overrides for people with terminated
assignments if you enable the Number of Days to Display People with Terminated Assignments profile option.
Define Labor Costing Business Unit Options
Overtime Calculation Components: How They Work Together

If you charge overtime costs to a project, you can use Oracle Fusion Projects to record the cost premium that you pay for
overtime. Your business can then recover overtime costs with higher bill rates or higher overhead rates.
You can set up Oracle Fusion Projects to calculate overtime hours and charge the hours to your overtime project using one of
the following methods:
• Manually enter time card transactions to calculate overtime hours and charge them to a project.
• Implement the Overtime Calculation Extension to calculate and charge the hours to a project automatically.
310
Costing Rules
Other components of overtime cost calculations are:
• Costing Method
• Overtime Expenditure Types
• Labor Costing Multipliers
• Labor Costing Rules
• Overtime Projects and Tasks
Rates Costing Method

If you enter overtime hours manually, you can assign cost multipliers to overtime expenditure types. When you use the
Rates costing method, and a transaction is charged to an expenditure type that has an assigned labor costing multiplier, the
application applies the multiplier as labor costs are calculated. To calculate rates for overtime expenditure items, before you
define labor costing rules, you must define an expenditure type with the Overtime expenditure type class.
When you charge overtime to the project on which overtime was worked, you can track all overtime costs on one expenditure
item. Oracle Fusion Projects uses the following formula to calculate the overtime premium cost: (Overtime Hours * Hourly Cost Rate)
+ (Overtime Hours * Hourly Cost Rate * Labor Cost Multiplier).
Extension Costing Method

Use the Overtime Calculation Extension to define your own rules to implement company-specific overtime calculation policies.
The application calculates labor costs based on the logic that you configure in the extension. If you use this extension, labor
costing rules establish the default overtime transaction attributes, such as business unit, project, and task. In addition, you are
not required to maintain hourly cost rates in Oracle Fusion Projects.
Sample business rules in the Overtime Calculation Extension calculate and charge overtime costs to a project other than the
project where the labor is charged. You can use this extension to create overtime transactions as separate expenditure items
to track overtime costs. In addition, you can customize this extension to use multiple projects to track costs.
Note
To charge overtime to the project where the labor is charged, consider creating overtime expenditure items using
the Related Transaction Extension.
If you use both the Overtime Calculation Extension and Related Transaction Extension, then you must define
conditions in both extensions so that each transaction is processed by only one of the extensions.
Important
You must select the Enable Overtime Calculations business unit implementation option for the Import and
Process Cost Transactions process to use the custom logic that you configure in the Overtime Calculation
Extension to create overtime premium transactions.
Overtime Expenditure Types

You must set up at least one overtime expenditure type that is classified by the Overtime expenditure type class.
Following are examples of overtime premium expenditure types and the corresponding expenditure type class:
Expenditure Type Expenditure Type Class
Double Time Premium Overtime

311
Costing Rules
Expenditure Type Expenditure Type Class
Time and Half Premium Overtime

Labor Costing Multipliers

Labor costing multipliers are values by which labor cost rates are multiplied to calculate overtime premiums. You define a
labor cost multiplier for each type of overtime your business uses, such as double time or time and a half. For example, if
you pay a person double time for all overtime hours, then define a labor cost multiplier of 1.0. The person's labor cost rate
is multiplied by 1.0 to calculate the person's overtime premium labor cost rate. If you pay a person time and a half for all
overtime hours, then define a labor cost multiplier of 0.5 to calculate the person's overtime premium labor cost rate.
Oracle Fusion Projects uses the following formula to calculate the overtime premium cost rate: Labor Cost Rate * Labor Cost
Multiplier = Overtime Premium Labor Cost Rate. The application then multiplies the overtime premium labor cost rate by the number of
overtime hours a person works to calculate the overtime premium for that person, as shown in this formula: Overtime Premium
Labor Cost Rate * Overtime Hours = Overtime Premium Cost.
A person's total labor cost is the overtime premium cost plus the total number of hours that the person worked multiplied by
the person's labor cost rate, as shown in this formula: Overtime Premium Cost + (Total Hours * Labor Cost Rate) = Total Labor Cost.
For example, assume that a person worked 10 hours of overtime at a rate of time and a half. The labor cost multiplier is 0.5,
and the person's labor cost rate is $40.00. Oracle Fusion Projects calculates the person's total labor cost as follows:
• $40.00 * 0.5 = $20.00 per hour Overtime Premium Labor Cost Rate
• $20.00 * 10 hours = $200.00 Overtime Premium Cost
• $200.00 + (10 * $40.00) = $600.00 Total Labor Cost
Labor Costing Rules

Labor costing rules associate overtime expenditure types with labor costing multipliers and determine how straight time and
overtime costs are calculated. When a person charges time to a project, Oracle Fusion Projects processes the labor hours
according to the person's labor costing rule.
You specify the default overtime project and overtime task in the labor costing rule to be used for the overtime expenditure
items that are generated by the Overtime Calculation Extension.
Overtime Projects and Tasks

You can define one project to hold all overtime costs, or you can define many projects, such as one project for each group or
office in your company. For example, you can create an overtime project for each office. You then charge each employee's
overtime hours to the overtime project for the office to which they are assigned.
For each overtime project, you must define a task for each type of overtime your business uses. Examples of task names are
Time and Half, Double Time, and Uncompensated Overtime.
If you use more than one project to hold overtime costs and you use the Overtime Calculation Extension to create overtime
transactions automatically, you must include the logic in the extension to charge the overtime hours to the appropriate
overtime project. You must also include logic in the Overtime Calculation Extension to charge overtime hours to the
appropriate overtime task.
Related Topics
• Overtime Calculation Extension
312
Costing Rules
Manage Organization Costing Rules
Organization Costing Rule Components: How They Work

Together
Use organization costing rules to assign labor costing rules, labor cost rate schedules, and nonlabor cost rate schedules, to
business units or specific expenditure organizations. The schedule type on the organization costing rule determines if a labor
cost rate schedule or nonlabor cost rate schedule is assigned.
The following components work together to determine organization costing rules.
• Business unit and expenditure organization
• Schedule type
• Labor costing rule and cost rate schedule
• Default overtime transaction attributes
Business Unit and Expenditure Organization

If you select a business unit for an organization costing rule, Oracle Fusion Projects limits the expenditure organizations that
you can select to just the organizations that belong to the project expenditure organization hierarchy for the selected business
unit. If you do not select a business unit for an organization costing rule, you can select any expenditure organization that
belongs to any project expenditure organization hierarchy.
If you assign an organization labor costing rule to an organization that is not classified as a project expenditure organization,
the labor costing rule applies to all organizations that are below the specified organization in the project expenditure
organization hierarchy, unless you assign a labor costing rule to an organization at a lower level in the hierarchy.
For example, assume a hierarchy has three organizations: Organization 1, Organization 2, and Organization 3. Organization
1 is the parent of Organization 2. Organization 2 is the parent of Organization 3. Organization 3 is the only organization that
is classified as a project expenditure organization. If you assign organization labor costing rules only to Organization 1 and
Organization 2, the rule that you assign to Organization 2 takes precedence for Organization 3.
Schedule Type
Use the Labor schedule type to use labor cost rate schedules to calculate costs for labor transactions such as timecards. If
you select a schedule type of Labor, you must enter a labor costing rule.
Use the Nonlabor schedule type to use nonlabor cost rate schedules to calculate costs for nonlabor transactions such
as miscellaneous or usage transactions. If you select a schedule type of Nonlabor, you must enter a nonlabor cost rate
schedule.
If the plan type is configured to use actual rates, the pricing engine also uses these rates for planning, budgeting, and
forecasting transactions.
Labor Costing Rule and Cost Rate Schedule

To calculate labor costs, you must assign a labor costing rule to each expenditure organization. You assign a labor costing
rule to the organization costing rule. If the labor costing rule has a costing method of Rates, you must also assign a cost rate
schedule that defines the hourly cost rates for employees in the selected organization.
313
Costing Rules
The labor costing rules and cost rate schedules that you assign to an organization apply to all employees in the organization.
Default Overtime Transaction Attributes

If an organization uses the Overtime Calculation extension, you can enter default overtime projects and tasks for the system-
generated transactions.
314
Implementing Project Financial Management Project Foundation Configuration: Define Project Resource
Breakdown Structures

Project Resource Breakdown Structures
Manage Planning and Billing Resource Breakdown

Structures
Planning Resource Breakdown Structures: Explained

A planning resource breakdown structure is a list of valid planning resource formats available for financial and project planning
and control. A resource format is a hierarchy of up to three resource types.
Before you can set up resource breakdown structures, you must set up the following:
• Attributes for the predefined resource classes of labor, equipment, material items, and financial resources.
• Inventory items, including item categories and item cost, if applicable.
• Resource elements, such as event types, expenditure categories, expenditure types, jobs, organizations, people,
revenue categories, roles, and suppliers.
315
Setting up planning resource breakdown structures is a three-step guided process. The following diagram illustrates the flow
of planning resource breakdown structures as they are created and added to projects or project templates.
As shown in the diagram, the steps to set up planning resource breakdown structures include the following:
• Define planning resource breakdown structure details

• Select resource formats
• Add planning resources
The last two steps shown in the diagram (add resource breakdown structures to a project or template and select the primary
resource breakdown structure) occur during project or template definition.
Resource Breakdown Structure Details

Planning resource breakdown structure details include the following attributes:
• Date range during which this planning resource breakdown structure is available to assign to projects
316
• Project unit
• Indicator that specifies whether resource changes are allowed at the project level
Important
If resource changes are not allowed at the project level, then all projects with the same planning resource
breakdown structure share the same set of resources, and it is not possible to define additional resources
in the context of an individual project. For example, new resources and resource formats that are added
to a planning resource breakdown structure for one project are available to all projects with this planning
resource breakdown structure.
If resource changes are allowed at the project level, then in addition to the resources defined centrally on
this resource breakdown structure, you can add resources for an individual project that are not available
to other projects with the same planning resource breakdown structure. However, resource formats are
still shared between the projects.
Resource Formats
You select resource formats to add to the planning resource breakdown structure.
Planning resource breakdown structures can have resource formats with up to three hierarchical levels of resource types, as
shown in the following example:
• Organization
◦ Expenditure category
• Named person
If you select a child resource format, the application automatically selects the parent. For example, if you select the resource
format of organization-expenditure category-named person, the application automatically selects the organization-expenditure
category format and expenditure category format.
The resource breakdown structure consists of one or more hierarchies of resource elements. An element is a resource type,
such as an organization or job, or a combination of resource type and specified resource, such as the job of consultant or a
person named Amy Marlin.
317
The following diagram shows examples of hierarchical levels of resource elements:
Planning Resources
You can add planning resources to any level of the resource format. You are not required to add resources to every level.
For example, assume that your resource breakdown structure has a resource format with three hierarchical levels. The
top level is organization, the second level is expenditure category, and the third level is named person. You can add an
organization resource to the first level, an expenditure category resource to the second level, and a named person to the third
level. Alternatively, you may add a named person to the third level only, and not add planning resources to the first two levels.
After you add planning resources to the resource breakdown structure, you can preview actual transaction associations to
find out where actual transaction amounts would be mapped in the project plan, budget, or forecast.
You update the resource mappings with these planning resources for the planning resource breakdown structures that are
used on the project plan and in project forecasts. When you update the mappings, the project performance reporting data
are synchronized with the planning resource breakdown structure.
Primary Resource Breakdown Structure

You designate one planning resource breakdown structure as the primary structure on a project. The primary planning
resource breakdown structure is used for project planning.
318
Related Topics
• Resource Classes: Explained
• Resource Formats and Resource Classes: How They Work Together to Create Planning Resources
Billing Resource Breakdown Structures: Explained

Use a billing resource breakdown structure to manage billing controls.
You need only a single level billing resource breakdown structures to create billing controls.
Predefined Billing Resource Breakdown Structures

Oracle Fusion Projects provides the following two predefined billing resource breakdown structures:
• Control Billing: Provides a list of resources you can reference when creating billing controls on regular contracts.
• Control Intercompany Billing: Provides a list of resources you can reference when creating billing controls on
intercompany and interproject contracts.
You cannot create or delete these billing resource breakdown structures. You can edit the resource formats and specify the
associated billing resources to meet the needs of your enterprise.
Resource Formats and Resource Classes: How They Work

Together to Create Planning Resources
The resources you can create for planning and billing resource breakdown structures are determined by a combination of
predefined resource classes and the resource format hierarchies you select for use.
Resource Formats and Resource Format Hierarchies

Before creating planning or billing resources, you must select the resource formats and resource format hierarchies you want
to use on your resource breakdown structure. For example, if you want to plan for project-related expenses such as air fare,
then you must select resource format hierarchies created using the resource type Expenditure Type.
Also, as resource format hierarchies support up to three levels, selecting from the available hierarchies enables you to
determine the granularity with which resources are created.
For example, for planning resource breakdown structures used for high-level or preliminary planning, you may decide to
enable only the Resource Class resource format. You can then create and use planning resources representing the four
resource classes: Labor, Equipment, Material Items, and Financial Resources.
To plan in greater detail, you may decide to use a two-level resource format hierarchy, such as Resource Class: Job or
a three-level hierarchy such as Resource Class: Job: Named Person. You can then create a resource such as Labor:
Electrical Engineer or Labor: Electrical Engineer: Chris Black.
Note
Selecting more granular resource formats automatically selects resource formats higher up within the same
hierarchy. For example, if you select the resource format Expenditure Type: Named Person: Job, then the
resource formats Expenditure Type: Named Person and Expenditure Type are automatically selected for use.
319
Resource Classes
Resource classes influence the creation of planning and billing resources in the following ways:
• Resource class as a resource format: As mentioned earlier, Resource Class is a resource type that is available for
use within resource format hierarchies on planning and billing resource breakdown structures.
• Predefined association with resource formats: For each resource format, you can create planning or billing resources
based on certain resource classes. For example, if the resource format contains Job, then the only available resource
class is Labor. However, if the resource format is Expenditure Category, then you can select any of the resource
classes (Labor, Material, Equipment, and Financial Resources) when you create a resource.
Related Topics
• Resource Classes: Explained
Resource Formats: Explained

Resource formats are predefined resource types or hierarchies of resource types. You create resources for planning or billing
resource breakdown structures based on resource formats.
Following is a description of resource types and resource format hierarchies.
Resource Types
Resource formats are created based on the following predefined resource types.
Name Description
Named Person Employee or a contingent worker who performs services

for the deploying enterprise.

Event Type Implementation-defined classification of events that

determines the revenue and invoice effect of an event.

Expenditure Category Implementation-defined grouping of expenditure types

by type of cost.

Expenditure Type Classification of cost assigned to each expenditure

item. Expenditure types are grouped into cost groups
(expenditure categories) and revenue groups (revenue
categories).

Item Category Categorization of inventory items that is used to track

the aggregate consumption of material.

Inventory Item An item that can be purchased or produced, and for

which you can budget and track the costs associated
with the consumption of the item.

320
Name Description
Job A set of duties to which an employee can be assigned.

Organization Divisions, groups, cost centers, or other organizational

units within a company.

System Person Type Distinguishes employees and contingent workers. For

example, assume that a project requires 100 hours of
labor effort and you have resources only for 80 hours.
You can plan 80 hours of employee time and 20 hours
of contingent worker time on the project.

Project Nonlabor Resource Implementation-defined asset or pool of assets. An

asset may represent actual pieces of equipment
whose time is consumed, or an asset whose output is
consumed.

Resource Class Higher-level grouping of planning resources, into labor,

equipment, material items, and financial resources, that
drives how resources are used.

Revenue Category Implementation-defined grouping of expenditure types

by type of revenue.

Supplier A business or individual that provides goods or services,

or both in return for payment.

Resource Format Hierarchies

Resource formats consist of one resource type or a hierarchy of up to three resource types. Before you add planning
resources to a planning or billing resource breakdown structure, you must select the resource formats you want to use. For
example, you can add the resource formats Job, Job: Organization, and Job: Organization: Named Person to your
resource breakdown structure.
The resource formats and resource format hierarchy determine how planning amounts roll up and are displayed when you
view financial and project plans by resource structure. Thus, each resource format hierarchy represents a separate structure.
For example, the resource format hierarchies Job: Expenditure Type: Organization and Organization: Expenditure
Type: Job are distinct.
Related Topics
• Resource Formats and Resource Classes: How They Work Together to Create Planning Resources
321
Resource Mapping: How It Is Calculated

The Update Mapping process matches actual costs and revenue to the latest, saved planning resources for project planning
and forecasting. Summarized actual costs and revenue are recalculated for project performance reporting.
Resource Mapping Considerations

Consider these points when using the Update Mapping process:
• You can update resource mappings after you change resource formats or add resources, and save the resource
breakdown structure.
• Baseline project plan values are not affected by the Update Mapping process.
• The Update Mapping process applies only if you do not allow resource changes at the project level.
Tip
If you allow resource changes at the project level, use the Update Actual Amounts action on the project
plan to update the actual amounts for all tasks on the project plan. Use the process monitor to start the
process to summarize project performance data for reporting.
• After running the Update Mapping process, regenerate forecast versions to reflect the new actual costs.
How Resource Mapping Is Calculated

You can track the cost impact of every resource that has been assigned to a project task and use the resource breakdown
structure to view the breakdown of these costs. Oracle Fusion Projects associates the costs of the resources used for
tasks with branches and levels in the resource breakdown structure. The process for determining the correct association is
managed by rules of precedence.
Oracle Fusion Projects uses the following rules to associate cost amounts with resources:
• Select the lowest level in the resource breakdown structure to which a transaction can map.
◦ If there is only one level to which the transaction maps, the cost amounts are mapped to that level.
◦ If the transaction maps to more than one level, Oracle Fusion Projects sums the precedence numbers for all
resource types in the branch, and gives precedence to the resource element in the branch with the lowest
sum.
◦ If more than one branch has the lowest precedence number at the lower level, the application uses the
precedence number of the next level up.
• If the sum of precedence numbers is the same for more than one branch, precedence is given to the branch with the
lowest number at the lowest level.
◦ If one branch contains a user-defined resource type, precedence is given to the branch that does not contain a
user-defined resource type.
Note
Oracle Fusion Projects gives more precedence to a lower precedence number. For example, a resource element
with a precedence number of 1 is given precedence over a resource element with a precedence number of 10.
Rules of precedence are listed in the following table:
322
Resource Type Precedence in Precedence Precedence in Precedence
Labor Resource in Equipment Material Items in Financial
Class Resource Class Resource Class Resources
Resource Class
Named Person 1 1 1 1

Project Nonlabor 3 3 3 3
Resource

Inventory Item 5 5 5 5

Job 6 6 6 6

Item Category 8 8 8 8

Expenditure Type 9 9 9 9

Event Type 10 10 10 10

Expenditure 11 11 11 11
Category

Revenue Category 12 12 12 12

Organization 13 13 15 15

System Person 14 14 14 14
Type

Supplier 15 15 13 13

Resource Class 16 16 16 16

323
Example of Resource Mapping Using Rules of Precedence

This example illustrates that precedence is given to the branch with the lowest number at the lowest level if the sum of
precedence numbers is the same for more than one branch.
In this example, a time card transaction for a principle consultant who incurs travel expenses maps to two branches.
• The first branch consists of two levels (1-Person Type: Employee and 1.1-Job: Principle Consultant). The highest
level has a precedence number of 14, and the lowest level has a precedence number of 6, for a sum of 20 for the
branch
• The second branch also consists of two levels (2-Expenditure Category: Expenses and 2.1-Expenditure Type:
Travel). The highest level has a precedence number of 11, and the lowest level has a precedence number of 9, for a
sum of 20 for the branch.
The transaction cost amount is mapped to the Job: Principle Consultant resource element because it has the lowest number
(6) at the lowest level.
Manage Reporting Resource Breakdown Structures
Reporting Resource Breakdown Structure Versions: Explained

Use reporting resource breakdown structures to view the rolled-up data in Oracle Fusion Project Performance Reporting. The
structure provides a method for viewing planned and actual cost and revenue for a project by resource, resource type, and
other resource groupings.
Versions
Reporting resource breakdown structure versions provide a history of resource breakdown structures used for resource
reporting.
When a resource breakdown structure is created, a working version is automatically created. You can have only one working
version at a time. You can make changes to the working version until you are ready to freeze it.
324
Only a frozen version can be associated with a project. When you freeze one version, a new working version is created on
which you can make further changes.
When you freeze a resource breakdown structure version, that version becomes the current reporting version the next
time project performance data is summarized. Although you can have multiple frozen versions, only one is used for current
reporting at any given time.
Resource Types and Resources

All planning resource breakdown structures can be used for reporting.
In addition, you can build reporting resource breakdown structures based on the resource types and resources already
defined in the system. Select the resource type and specify the associated resource for each level of the hierarchy. You
can create up to ten hierarchical levels in a reporting resource breakdown structure. This is different than planning resource
breakdown structures, which may contain up to three hierarchical levels.
The User Defined resource type enables you to define your own groups of resources. Select the User Defined resource type,
enter a free-form definition of the group, and then create hierarchical levels that link the actual resource types and resources.
Cost Allocations
Enable the Use For Allocations option if you want to allocate costs with this reporting resource breakdown structure.
If you enable this option, you can select this reporting resource breakdown structure when defining source and target details
for an allocation rule. In this situation, the reporting resource breakdown structure must be assigned to all source or target
projects.
FAQs for Define Project Resource Breakdown

Structures
Can I add new resource formats?

No. Oracle Fusion Project Portfolio Management provides a set of predefined resource formats. You select resource formats
as the basis for adding resources to planning and billing resource breakdown structures.
Can I add new billing resource breakdown structures?

No. You cannot create billing resource breakdown structures. However, you can add billing resources to the two predefined
billing resource breakdown structures, Control Billing and Control Intercompany Billing, as required.
What's a default planning resource breakdown structure?

A planning resource breakdown structure consisting of one resource format (resource class) with four associated planning
resources: Labor, Equipment, Material Items, and Financial Resources.
A default planning resource breakdown structure is created automatically for each project unit. When you create a project
template, the default planning resource breakdown structure is selected as primary, but you can designate any other one.
Once you designate, you cannot remove the planning resource breakdown structure from the project template or project.
325
What's a primary resource breakdown structure?

A planning resource breakdown structure that is selected as the primary at the project template or project level. The primary
planning resource breakdown structure is used for project planning.
When you create a project template, the default planning resource breakdown structure for the project unit is automatically
added and set as primary. You can add additional planning resource breakdown structures to the template and set any one
of them as primary. Projects inherit planning resource breakdown structures from the associated template. As with templates,
you can add or remove planning resource breakdown structures and change the primary designation as required.
What's the difference between a planning resource breakdown

structure, billing resource breakdown structure, and a
reporting resource breakdown structure?
Planning resource breakdown structures provide a list of resource formats and associated planning resources that you can
use for project and financial planning, and optionally, project reporting.
Billing resource breakdown structures are similar in organization to planning resource breakdown structures. However,
only two predefined billing resource breakdown structures exist and they provide a restricted set of implementation-defined
resource formats and billing resources that are used for invoicing and recognizing revenue for contracts.
Reporting resource breakdown structures provide a resource hierarchy consisting of resources, resource types, and other
resource groupings, which is used for reporting on planning and actual amounts on a project. Also, unlike planning and billing
resource breakdown structures, you can use reporting resource breakdown structures in allocation rules to determine the
allocation source and basis amounts.
What happens if I change a name used in a resource

combination on a resource breakdown structure?
You must run the Refresh Resource Breakdown Structure Element Names process to refresh the value that appears in
the combination.
For example, you have a resource that includes the Telephone Charges expenditure type in the resource combination and
you change the name from Telephone Charges to Communication Charges in the Manage Expenditure Types page. The
change will not appear in the resource combination until you run the process.
Why can't I change the name of a planning resource?

You cannot change the name of a planning resource after the planning resource breakdown structure is used to create a
control budget.
What's the difference between a planning resource breakdown

structure, billing resource breakdown structure, and a
reporting resource breakdown structure?
Planning resource breakdown structures provide a list of resource formats and associated planning resources that you can
use for project and financial planning, and optionally, project reporting.
326
Billing resource breakdown structures are similar in organization to planning resource breakdown structures. However,
only two predefined billing resource breakdown structures exist and they provide a restricted set of implementation-defined
resource formats and billing resources that are used for invoicing and recognizing revenue for contracts.
Reporting resource breakdown structures provide a resource hierarchy consisting of resources, resource types, and other
resource groupings, which is used for reporting on planning and actual amounts on a project. Also, unlike planning and billing
resource breakdown structures, you can use reporting resource breakdown structures in allocation rules to determine the
allocation source and basis amounts.
Why can't I find persons in the list of resources when I enter

team members, planning resources, or person rate schedules?
You can't find persons in the list of resources when you enter team members, planning resources, or person rate schedules
in the following situations:
• The administrator did not assign a department while creating users. Persons must have an active assignment and
be assigned to a department in Oracle Fusion Human Capital Management before they can be added as team
members or entered as resources on the planning resource breakdown structure or person rate schedule.
• The resource is not active in Oracle Fusion Human Capital Management because the current date is before the
effective date of the resource. If you want to include persons who will start in the future, select the Include people
with future-dated effective start dates option when you search for the person.
• Persons assigned as project managers are not active as of the project start date.
327
Implementing Project Financial Management Project Foundation Configuration: Define Burdening

Burdening
Manage Burden Cost Base Types, Bases, and Codes
Burden Costs: How They Are Calculated

Burdening provides a buildup of raw and burden costs to represent the total cost of doing business accurately. You can
calculate burdened costs as a buildup of costs using a precedence of multipliers. Taking the raw cost, Oracle Fusion Project
Costing performs a buildup of burden costs on raw costs to provide a true representation of costs. Using burdening, you can
perform internal costing, revenue accrual, and billing for any type of burdened costs that your company applies to raw costs.
Settings That Affect Burden Cost Calculation Processing

You define the projects that need to be burdened by enabling project types for burdening. When you specify that a project
type is burdened, you must then specify the burden schedule to be used. The burden schedule stores the burden multipliers
and indicates the transactions to be burdened, based on cost bases defined in the burden structure. You specify the
expenditure types that are included in each cost base. With burdening, you can use an unlimited number of burden cost
codes, easily revise burden schedules, and retroactively adjust multipliers. You can define different burden schedules for
costing, revenue, and billing purposes.
How Burden Costs Are Calculated

The calculation of burden cost includes the following processing decision logic and calculations:
328
The following is a diagram of the burden cost calculation process and its explanation:
1. Expenditure items with a raw cost amount are selected for processing.
2. The process determines if the related project type of the expenditure item is defined for burdening.
3. If the project type is enabled for burdening, then the process determines the burden schedule to be used.
4. If the project type is not enabled for burdening, then the expenditure item is not burdened. The process assumes
the burden multiplier is zero; therefore, burden cost is zero and thus burdened cost equals raw cost.
5. To determine which burden multiplier to use, the process determines if there is a burden schedule override for the
expenditure.
6. If a burden schedule override exists, then the process uses the task burden schedule override on the associated
task.
7. If no task burden schedule override exists on the associated task, then the process uses the project burden
schedule override on the associated project.
329
8. If there are no burden schedule overrides, the process determines the burden schedule to use for burden cost
calculations in the following order:
a. Burden schedule assigned at the task level
b. Burden schedule assigned at the project level
9. The process checks if a fixed date is specified for burdening. If yes, it uses the fixed date to determine the schedule
version.
10. If fixed date is not specified, then the process uses the expenditure item to determine the burden schedule version.
11. After a schedule version is determined, the process verifies that the expenditure type of the expenditure item is
found in any of the cost bases of the selected burden schedule version.
12. If an expenditure type is excluded from all cost bases in the burden structure, then the expenditure items that use
that expenditure type are not burdened (burden cost equals zero, thus burdened cost equals raw cost).
13. The application calculates burden cost and burdened cost amounts according to the following calculation formulas:
◦ Burden cost equals raw cost multiplied by a burden multiplier.
◦ Burdened cost equals the sum of raw cost and burden costs.
Cost Buildup
The burden structure assigned to the burden schedule version determines whether calculations are additive or based on the
precedence assigned to each cost code. A burden structure can be additive or precedence based.
If you have multiple burden cost codes, an additive burden structure applies each burden cost code to the raw costs in the
appropriate cost base. The examples in the following tables illustrate how Oracle Fusion Projects calculates burdened cost as
a buildup of raw and burden costs and how different burden structures using the same cost codes can result in different total
burdened costs:
The following table shows the cost codes and multipliers for calculating burdened cost using the additive burden structure.
Cost Code Precedence Multiplier
Overhead 1 .10

Material Handling 1 .10

General Administrative Costs 1 .10

Cost Type Calculation Amount
Raw Cost Not Applicable 1000.00

Overhead 1000.00 X 0.10 100.00

330
Material Handling 1000.00 X 0.10 100.00

General Administrative Costs 1000.00 X 0.10 100.00

Burdened Cost 1000. 00+100. 00+1000. 1300.00

00+100.00

A precedence burden structure is cumulative and applies each cost code to the running total of the raw costs, burdened with
all previous cost codes. The calculation applies the multiplier for the cost code with the lowest precedence number to the raw
cost amount.
The calculation applies the cost code with the next lowest precedence to the subtotal of the raw cost plus the burden cost for
the first multiplier. The calculation logic continues in the same way through the remaining cost codes. If two cost codes have
the same precedence number, then both are applied to the same subtotal amount.
The following table shows the cost codes and multipliers for calculating burdened cost using the precedence burden
structure for a nonrate-based expenditure item:
Cost Code Precedence Multiplier
Overhead 10 .10

Material Handling 20 .10

General Administrative Costs 30 .10

Raw Cost Not Applicable 1000.00

Overhead 1000.00 X 0.10 100.00

Material Handling (1000. 00+100.00) X 0.10 110.00

General Administrative Costs (1000. 00+100. 00+110.00) X 0.10 121.00

Burdened Cost 1000.00 +100.00 +110. 1331.00

00+121.00

331
Note
The order of the burden cost codes has no effect on the total burdened cost with either additive or precedence
burden structures.
Creating Burden Cost Bases: Example

You use burden cost bases in burden structures to group the burden cost codes with the expenditure types to which they
will be applied. As a result, you need to create burden cost bases to support each unique grouping of burden cost codes and
expenditure types.
The following scenario illustrates burden cost bases that are used to group raw costs for the purpose of calculating burdened
costs.
Burden Cost Bases

Burden cost bases with the type Burden Cost, as shown in the following table, are used to group raw costs for the purpose
of calculating burdened costs. Reports sort cost bases first by the report order value and then by the cost base name.
Cost Base Report Order Cost Base Type
Labor 10 Burden Cost

Material 20 Burden Cost

Expense 30 Burden Cost

Note
Oracle Fusion Projects predefines the cost base types Burden Cost and Other.
Creating Burden Cost Codes: Example

The following scenario illustrates burden cost codes that represent distinct types of burden to apply to raw costs.
Burden Cost Codes

Burden cost codes are created for each type of burden that will be applied to raw costs. In this example, assume that labor
raw costs are burdened with fringe benefits, overhead, and administrative costs. Material raw costs are burdened with
material handling fees and administrative costs. Expenses are burdened only with administrative costs.
You can optionally assign an expenditure type to any burden cost code to capture burden costs on separate, summarized
expenditure items. Only expenditure types with a Burden Transactions expenditure type class are available for assignment to
a burden cost code. The assigned expenditure type becomes the expenditure type for that type of burden cost.
Note
Expenditure types that you assign to burden cost codes must be classified as a Burden Transactions expenditure
type.
332
Note
Ensure that the expenditure types that you assign to burden cost codes are assigned to the reference data sets
for each project unit that will own projects receiving summarized burden transactions.
The following table shows burden cost codes that represent distinct types of burden to apply to raw costs.
Burden Cost Code Description Expenditure Type
Administrative Corporate expenses such as General and Administrative

corporate staff and marketing

Fringe - Faculty Employer paid payroll costs, Fringe Benefits

insurance, and pension for faculty

Fringe - Staff Employer paid payroll costs and Fringe Benefits

insurance for staff

Material Handling Material handling fees Material

Overhead Support staff, equipment rental, Overhead

supplies, building rent, and facilities

FAQs for Manage Burden Cost Base Types, Bases, and Codes
What's a cost base type?
Identifies if the burden cost base is used for burden cost calculations or grouping expenditure items. The application provides
two predefined cost base types:
• Burden Cost: Used for burden calculations.
• Other: Used for grouping expenditure types, for example in Billing extension calculations.
When do I assign an expenditure type to a burden cost code?

Burden cost codes are assigned to cost bases. When you assign an expenditure type to a burden cost code, burden cost is
processed as a separate, summarized burden transaction.
The expenditure type assigned to a burden cost code must be classified as a burden transaction and belong to the reference
data set for the project unit.
Note
To process burden cost on the same line expenditure item, you don't need to assign an expenditure type to a
burden cost code.
333
Manage Burden Structures
Defining Burden Structures: Example

The following scenario illustrates the relationship between expenditure types and burden cost codes in a burden structure.
This relationship determines what burden costs Oracle Fusion Project Costing applies to specific raw costs.
Note
Before you can define burden structures, you must define expenditure types, burden cost bases, and burden cost
codes.
334
Burden Structure
The following diagram shows the expenditure types and burden cost codes that are assigned to the Labor, Material, and
Expense burden cost bases.
The following table shows the multipliers that are used to calculate burden costs for raw costs in the Labor, Material,
and Expense cost bases. This is an additive burden structure that applies each burden cost code to the raw costs in the
appropriate cost base.
Note
Multipliers are defined on the burden schedule.
335
Burden Cost Raw Cost Administrative Labor Fringe Labor Material

Base Amount Cost Code Benefit Overhead Handling
(USD) Multiplier Cost Code Cost Code Cost Code
Multiplier Multiplier Multiplier
Labor 1,000 .20 .20 .40

Material 500 .20 .25

Expense 400 .20

The following diagram shows the resulting burdened costs for labor, material, and expenses.
336
Additive and Precedence Burden Structures: Examples

A burden structure can be additive or precedence based. If you have multiple burden cost codes, an additive burden
structure applies each burden cost code to the raw cost in the appropriate cost base. A precedence burden structure is
cumulative and applies each cost code to the running total of the raw cost, burdened with all previous cost codes. You
assign the multiplier on the burden schedule that Oracle Fusion Project Costing uses to perform the cost buildup for each
detailed transaction.
Additive Burden Structure

Create an additive burden structure to apply each burden cost code assigned to a cost base using the same precedence
when calculating burden costs, as shown in the following table.
Cost Code Precedence Multiplier Formula Amount (USD)
Raw Cost 100.00

Overhead 1 0.50 0.50 * 100.00 50.00

Fringe Benefits 1 0.30 0.30 * 100.00 30.00

General and 1 0.20 0.20 * 100.00 20.00

Administrative

Burdened Cost 200.00

Note
Each burden cost code in an additive burden structure is automatically assigned a default precedence value of 1.
Precedence Burden Structure

Create a precedence burden structure to specify the order in which each burden cost code assigned to a cost base is
applied to raw costs, as shown in the following table.
Raw Cost 100.00

Overhead 10 0.50 0.50 * 100.00 50.00

Fringe Benefits 20 0.30 0.30 * 150.00 45.00

337
General and 30 0.20 0.20 * 195.00 39.00

Administrative

Burdened Cost 234.00

Burden Structure Components: How They Work Together

You define the project cost buildup using a burden structure. A burden structure determines how you group expenditure
types into burden cost bases and establishes the method of applying burden costs to raw costs. Before creating burden
structures you must define expenditure types, cost bases, and burden cost codes, which are the main components of a
burden structure.
338
The diagram illustrates a burden structure with the following cost bases.
• Labor
◦ Includes the expenditure types Professional, Clerical, and Sales.
◦ Is assigned the burden cost codes Administrative, Fringe Benefits, Overhead.
• Material
◦ Includes the expenditure types Supplies and Construction Material.
◦ Is assigned the burden cost codes Administrative and Material Handling.
• Expense
◦ Includes the expenditure types Travel and Meals.
◦ Is assigned the burden cost code Administrative.
Cost Bases
Cost bases are the groups of raw costs used for applying burden costs. You assign cost bases to burden structures, and
then specify the types of raw costs, represented by expenditure types, that are included in the cost base, and the types of
burden costs that are applied to the cost base.
You can also use cost bases to group expenditure types for other purposes, such as in billing extension calculations. These
cost bases are not used for burdening, and are defined with a cost base type other than Burden Cost. When you assign cost
bases with a type other than Burden Cost to a burden structure, you can specify expenditure types for the cost base, but you
cannot specify burden cost codes for the cost base since the cost base is not used for burdening.
Burden Cost Codes

Burden cost codes represent the distinct type of burden to apply to raw costs. For example, if labor costs receive both
fringe benefits and overhead burden, then define a cost code for each type of burden. Assign an expenditure type to each
burden cost code that Oracle Fusion Project Costing processes as separate, summarized expenditure items. The assigned
expenditure type becomes the expenditure type for that type of burden cost.
Cost Base Types

Cost base types refer to the use of cost bases. Oracle Fusion Project Costing provides the following cost base types.
• Burden Cost: Assign to cost bases that are used to calculate burden costs.
• Other: Assign to cost bases that are used for other purposes than to calculate burden costs.
You can define additional cost base types to use for non-burden transactions.
Expenditure Types
Expenditure types classify raw costs and burden cost codes classify burden costs. The relationship between expenditure
types and burden cost codes within each cost base determines what burden costs are applied to specific raw costs, and the
order in which processing applies the burden costs.
339
In a burden structure, each expenditure type can belong to only one cost base with a cost base type of Burden Cost. This
restriction ensures that Oracle Fusion Project Costing does not burden an expenditure type more than once. If you do not
assign an expenditure type to a cost base, then burden costs are not applied to the raw costs with those expenditure types.
In other words, the burdened cost for these transactions is the same as the raw cost of the transaction.
FAQs for Manage Burden Structures

Why is burden cost missing on a transaction?
Burden costs are not applied to a transaction if either of these situations exist:
• The expenditure type associated with the transaction is not assigned to a cost base.
• The project type for the project is not enabled for burden calculation. In this situation, raw cost is equal to burdened
cost.
Manage Burden Schedules
Burden Schedule Components: How They Work Together

Burden schedules establish the multipliers used to calculate the burdened cost, revenue, or bill amount of each expenditure
item charged to a project. The burden schedule determines which transactions are burdened, based on burden cost bases
defined in the burden structure. The project type determines which projects are burdened and contains the default burden
schedule. A burden schedule type can be firm or provisional. Rates can be overridden by using a schedule of multipliers
negotiated for a specific project or task.
Burden Schedule Types

Use a firm burden schedule if you do not expect the multipliers to change. Firm burden schedules can have multiple versions,
but never more than one version for a date range.
Use a provisional burden schedule if the multipliers are based on estimates, such as a yearly forecast budget. Provisional
schedules can have provisional and actual versions active for the same date range. When the actual multipliers are available,
replace the provisional version with the actual version. When the actual burden schedule is built, the impacted expenditure
items are automatically reprocessed to adjust the burden cost amounts.
Multipliers
The multiplier specifies the rate by which to multiply the raw cost amount to obtain the burden cost amount. You assign a
multiplier to a combination of burden cost code and either a unique organization or a parent organization.
The organization hierarchy is used to cascade rates down to lower level organizations where multipliers are not explicitly
defined. If Oracle Fusion Projects finds a level in the hierarchy that does not have a multiplier defined, the application uses
the multipliers of the parent organization. Therefore, an organization multiplier schedule hierarchy is used to identify the
exceptions. You define the multipliers for an organization only if you want to override the multipliers of the parent organization.
The following diagram shows an example of multipliers that are used by organizations. The parent organization,
Headquarters, has two defined multipliers: Overhead with a multiplier of 2.0, and Administrative with a multiplier of 3.0.
• When the application processes transactions for the East organization, no multipliers are found. Therefore, the
application uses the multipliers from the parent organization, Headquarters.
340
• The Boston and New York City organizations are assigned an Administrative multiplier of 3.1, and no Overhead
multiplier. Therefore, the application uses the Administrative multiplier of 3.1, and the Overhead multiplier from the
Headquarters organization, when processing transactions for the Boston and New York City organizations.
• The West organization is assigned an Overhead multiplier of 2.3, and no Administrative multiplier. Therefore, the
application uses the Overhead multiplier of 2.3, and the Administrative multiplier from the Headquarters organization,
when processing transactions for the West organization.
• No multipliers are assigned to the San Francisco and Los Angeles organizations. Therefore, the application uses the
Overhead multiplier from the West organization, and the Administrative multiplier from the Headquarters organization,
when processing transactions for the San Francisco and Los Angeles organizations.
Burden Schedule Versions

Burden schedule versions define the date range within which multipliers are effective. You build the burden schedule to make
the burden schedule versions active and available for use.
Note
If an organization is added to the hierarchy after the schedule is built, then submit the Build New Organization
Burden Multipliers process. A burden schedule version must be active to add multipliers for a new organization.
341
Related Topics
• Editing Burden Schedule Multipliers: Points to Consider
Burden Multipliers for New Organizations: How They Are

Added to Burden Schedules
The Build New Organization Burden Multipliers process adds burden multipliers to burden schedules for an organization when
you add a new organization to your organization hierarchy. If you do not add the organization to a specific burden schedule
version, this process builds multipliers for the organization in all burden schedule versions using the multipliers of the parent
organization as defined in the organization hierarchy. A burden schedule version must be active to add multipliers for a new
organization.
Important
Run this process after you create the organization and before you charge transactions using this organization as
the expenditure organization.
Run this process for the parent organization before you run it for the child organization.
If the new organization requires multipliers that are different than the multipliers assigned to the parent organization, you can
manually add multipliers for each burden cost code on the burden schedule versions, and then rebuild the versions.
Settings That Affect Burden Multipliers for New Organizations

The process parameter is the new organization for which you want to build multipliers for existing burden schedule versions.
Typically you run this process during implementation as part of the Burden Definition setup task list.
Process results are summarized in the Build New Organization Burden Multipliers Execution Report that displays the
impacted burden schedules and burden schedule versions.
Related Topics
Recalculating Burden Costs: Points to Consider

Oracle Fusion Projects identifies existing transactions that are eligible for burden cost recalculation and marks the
transactions for reprocessing. For example, when a multiplier for an organization and burden cost code changes on a
burden schedule version, the application marks for recalculation all transactions for the organization that are charged to an
expenditure type that is linked to the burden cost code.
Burden Cost Recalculation is Required

Burden cost recalculation is required in any of the following situations:
• A build occurs on a burden schedule version that was previously built.

• An actual burden schedule version is built to replace a provisional burden schedule version.
• During recalculation, one or more transactions are not marked for recalculation of burden cost amounts, such as
when an expenditure item is locked by another unprocessed adjustment, or a technical error occurs in the process.
342
Select the Recalculate Burden Cost Amounts button on the burden schedule for the process to identify and mark eligible
transactions for burden cost recalculation.
Note
A burden schedule can have multiple versions. The Burden Cost Calculation Required button is available for
selection on the burden schedule if at least one version requires recalculation.
After the impacted transactions are marked for burden cost recalculation, the Recalculate Burden Cost Amounts process
starts the Import and Process Cost Transactions process to create expenditure items and cost distribution lines for the
transactions.
If burden cost recalculation is still required after the Recalculate Burden Cost Amounts process completes, then review the
process execution report to determine why the process did not mark eligible transactions for recalculation.
Burden Cost Recalculation is Not Required

Burden cost recalculation is not required in the following situations:
• All burden schedule versions for the build are in a new status.
• Changes are made to burden schedule versions prior to the build.
• The Recalculate Burden Cost Amounts process is complete and all impacted transactions are successfully marked
for burden cost recalculation.
If burden cost recalculation is not required, the Recalculate Burden Cost Amounts button is not available for selection on
the burden schedule.
Related Topics
Testing Burden Cost Calculations: Explained

Test burden cost calculations to view a breakdown of the total burdened cost for a specific project transaction and to verify
your burden structure and burden schedule implementation. The test emulates an actual burden cost transaction for a set of
criteria consisting of the project, task, burden schedule, expenditure type, expenditure organization, raw cost, quantity, and
transaction date.
The application uses the burden schedule that you specify as burden cost criteria to calculate burden amounts. If you specify
a project as burden cost criteria, and you do not specify a task or burden schedule, then the application uses the burden
schedule on the project. If you specify a project and task, and you do not specify a burden schedule, then the application
uses the burden schedule on the task.
Test burden cost calculations to:
• Verify that the amounts for each burden cost code and for the total burdened cost are calculated correctly according
to the specified criteria.
• Confirm that the correct schedule is used for the given project and task.
• Confirm that the desired burden cost codes and rates are used for the organization and expenditure type.
343
Note
When the Burden Cost Calculation Override extension is enabled, the transaction quantity is passed to the
extension. If you do not enter the quantity, the application considers the transaction quantity as one.
FAQs for Manage Burden Schedules

How can I prepare for creating burden schedules?
Before you create burden schedules, you must define business units, the organization hierarchy, implementation options, and
burden structures.
What's a burden schedule?

Establishes the multipliers that are applied to the raw cost of each expenditure item to calculate the burdened cost, revenue,
or bill amount charged to a project.
Assign burden schedules to project types, projects, or tasks. The project type provides the default burden schedule for a
project. You can override the default burden schedule for each project by using a schedule of multipliers negotiated for the
project or task.
In planning, when using planning rates, you assign a burden schedule in the project or financial planning options. If you use
Oracle Fusion Project Integration Gateway to export resource rates to a scheduling application, then specify you must specify
a burden schedule to use. The set of resources and rates are global and have no project context from which to derive a
burden schedule.
What's burden costing?

A method of applying burden costs to raw costs to track the burdened cost of your projects.
What's the difference between a firm burden schedule and a provisional burden schedule?
Use firm burden schedules if you do not expect your burden multipliers to change. Firm schedules are typically used for
internal costing or commercial billing schedules. Firm burden schedules can have multiple versions, but never more than one
version for an effective date range.
Use provisional multipliers if you do not know the burden multipliers at the time that you are calculating total burdened costs.
Provisional multipliers are typically estimates based on the annual forecast budget. When you determine the actual multipliers
to apply to raw costs, then you replace the provisional multipliers with the actual multipliers. Oracle Fusion Project Costing
processes the adjustments from provisional to actual changes for costing, revenue, and billing.
Note
The actual burden schedule version, when created, is automatically placed on hold. You must remove the hold
prior to building the actual rates and recalculating costs.
Manage Project Types: Burdening Options
Burdening Options for Project Types: Points to Consider

Burdening is a method of applying one or more burden cost components to the raw cost amount of each individual
transaction to calculate burden cost amounts. Use project types to control how burden transactions are created and
accounted. If you enable burdening for a project type, you can choose to account for the individual burden cost components
or the total burdened cost amount.
344
The following diagram illustrates the burden cost accounting options for project types.
You specify the following options when setting up burdening options for project types.
• Default Cost Burden Schedule

• Allow Cost Burden Schedule Change for Projects and Tasks
• Include Burden Cost on Same Expenditure Item
◦ Create Expenditure Items for Burden Cost Components

• Create Separate Expenditure Item for Burden Cost
• Create Burden Cost Accounting Journal Entries
• Create Burdened Cost Accounting Journal Entries
Default Cost Burden Schedule

If you enable burdening for the project type, you must select the burden schedule to use as the default cost burden schedule
for projects that are defined with this project type.
345
Allow Cost Burden Schedule Change for Projects and Tasks

Enable this option to allow a change of the default cost burden schedule when entering and maintaining projects and tasks.
Do not enable this option if you want all projects of a project type to use the same schedule for internal costing.
Include Burden Cost on Same Expenditure Item

Enable this option to include the burden cost amount in the same expenditure item. You can store the total burdened cost
amount as a value with the raw cost on each expenditure item. Oracle Fusion Projects displays the raw and burdened costs
of the expenditure items on windows and reports.
If you include burden cost amounts on the same expenditure item, but wish to see the burden cost details, enable the option
to create expenditure items for each burden cost amount on an indirect project and task.
Create Separate Expenditure Item for Burden Cost

Enable this option to account for burden cost amounts as separate expenditure items on the same project and task as the
raw expenditures. The expenditure items storing the burden cost components are identified with a different expenditure type
that is classified by the expenditure type class Burden Transaction. Oracle Fusion Projects summarizes the cost distributions
to create burden transactions for each applicable burden cost code. The most important summarization attributes are project,
lowest task, expenditure organization, expenditure classification, supplier, project accounting period, and burden cost code.
You can use the Burden Summarization Grouping Extension to further refine the grouping.
Create Burden Cost Accounting Journal Entries

Indicate whether to create an entry for the burden cost amount.
If burdened costs are calculated for reporting purposes only, and you do not want to interface burdened costs to the general
ledger, you can disable the creation of accounting journal entries. If you select this option, only the burden cost, which is the
difference between the burdened cost and raw cost, is interfaced to general ledger.
Create Burdened Cost Accounting Journal Entries

Indicate whether to account for the total burdened cost amount of the items. You typically use this option to track the total
burdened cost amount in a cost asset or cost work-in-progress account.
The burdened cost is the sum of raw and burden costs. Therefore, selecting this option may result in accounting for raw cost
twice. For example, assume that the raw cost of an item is 100 USD, the burden cost is 50 USD, and the burdened cost is
150 USD. When the application creates a journal entry for 150 USD, it accounts for the 100 USD that was already accounted
for as raw cost, plus the 50 USD burden cost.
346
Implementing Project Financial Management Project Foundation Configuration: Manage Project Types
19 Project Foundation Configuration: Manage

Project Types
Burdening Options for Project Types: Points to

Consider
Burdening is a method of applying one or more burden cost components to the raw cost amount of each individual
transaction to calculate burden cost amounts. Use project types to control how burden transactions are created and
accounted. If you enable burdening for a project type, you can choose to account for the individual burden cost components
or the total burdened cost amount.
The following diagram illustrates the burden cost accounting options for project types.
347
You specify the following options when setting up burdening options for project types.
• Default Cost Burden Schedule
• Allow Cost Burden Schedule Change for Projects and Tasks
• Include Burden Cost on Same Expenditure Item
◦ Create Expenditure Items for Burden Cost Components
• Create Separate Expenditure Item for Burden Cost
• Create Burden Cost Accounting Journal Entries
• Create Burdened Cost Accounting Journal Entries
Default Cost Burden Schedule

If you enable burdening for the project type, you must select the burden schedule to use as the default cost burden schedule
for projects that are defined with this project type.
Allow Cost Burden Schedule Change for Projects and Tasks

Enable this option to allow a change of the default cost burden schedule when entering and maintaining projects and tasks.
Do not enable this option if you want all projects of a project type to use the same schedule for internal costing.
Include Burden Cost on Same Expenditure Item

Enable this option to include the burden cost amount in the same expenditure item. You can store the total burdened cost
amount as a value with the raw cost on each expenditure item. Oracle Fusion Projects displays the raw and burdened costs
of the expenditure items on windows and reports.
If you include burden cost amounts on the same expenditure item, but wish to see the burden cost details, enable the option
to create expenditure items for each burden cost amount on an indirect project and task.
Create Separate Expenditure Item for Burden Cost

Enable this option to account for burden cost amounts as separate expenditure items on the same project and task as the
raw expenditures. The expenditure items storing the burden cost components are identified with a different expenditure type
that is classified by the expenditure type class Burden Transaction. Oracle Fusion Projects summarizes the cost distributions
to create burden transactions for each applicable burden cost code. The most important summarization attributes are project,
lowest task, expenditure organization, expenditure classification, supplier, project accounting period, and burden cost code.
You can use the Burden Summarization Grouping Extension to further refine the grouping.
Create Burden Cost Accounting Journal Entries

Indicate whether to create an entry for the burden cost amount.
If burdened costs are calculated for reporting purposes only, and you do not want to interface burdened costs to the general
ledger, you can disable the creation of accounting journal entries. If you select this option, only the burden cost, which is the
difference between the burdened cost and raw cost, is interfaced to general ledger.
Create Burdened Cost Accounting Journal Entries

Indicate whether to account for the total burdened cost amount of the items. You typically use this option to track the total
burdened cost amount in a cost asset or cost work-in-progress account.
348
The burdened cost is the sum of raw and burden costs. Therefore, selecting this option may result in accounting for raw cost
twice. For example, assume that the raw cost of an item is 100 USD, the burden cost is 50 USD, and the burdened cost is
150 USD. When the application creates a journal entry for 150 USD, it accounts for the 100 USD that was already accounted
for as raw cost, plus the 50 USD burden cost.
Capitalization Options for Project Types: Points to

Consider
You can assign assets to a project if capitalization is enabled for the project type. Use project types to enable capitalization
and configure capitalization options that are inherited by each project associated with that project type.
The following diagram illustrates the capitalization options for project types.
349
You specify the following information when setting up capitalization options for project types.
• Construction in Progress (CIP) Options
• Supplier Invoices Export Options
• Capitalized Interest Options
Construction in Progress Options

You specify the following Construction in Progress options when setting up capitalization options for project types.
Cost Type
Indicate whether to capitalize costs at the burdened or raw cost amount for projects with this project type.
Complete Asset Definition

Enable this option to require a complete asset definition in Oracle Fusion Project Portfolio Management before sending costs
to Oracle Fusion Assets. If you select this option, you don't need to enter information for the imported asset lines in Oracle
Fusion Assets. The Transfer Assets to Oracle Fusion Assets process places asset lines with complete definitions directly into
the post queue in Oracle Fusion Assets.
Asset Line Grouping Method

Specify one of the following methods to summarize asset lines.
• All, which is the highest level of summarization
• CIP Grouped by Client Extension
• Expenditure Category
• Expenditure Category Nonlabor Resource
• Expenditure Type
• Expenditure Type Nonlabor Resource
Asset Assignment Override

This option interacts with the assignment status of the asset to either use or disregard the Asset Assignment extension, as
shown in the following table:
Override Asset Assignment Asset Lines Assigned to Assets Application Uses Asset
Assignment Extension
No Override (option not selected) Not Assigned Yes

No Override Assigned No

350
Override Asset Assignment Asset Lines Assigned to Assets Application Uses Asset
Assignment Extension
Override Not Assigned Yes

Override Assigned Yes

You can set up the Asset Assignment extension to assign any unassigned asset lines that result from the Generate Asset
Lines process, or to override the current asset assignment for specified lines.
Asset Cost Allocation Method

Select one of the following predefined allocation methods to automatically distribute indirect and common costs across
multiple assets, or select no allocation method.
• Actual Units
• Current Cost
• Client Extension
• Estimated Cost
• Standard Unit Cost
• Spread Evenly
Event Processing Method

You can specify a capital event processing method to control how assets and costs are grouped over time. You can choose
to use either periodic or manual events, or no events.
Group Supplier Invoices

Enable this option to consolidate the expenditure items on a supplier invoice into one asset line according to the asset line
grouping method. Deselect this option to send the lines to Oracle Fusion Assets based on the supplier invoice export option.
Supplier Invoice Export Options

If you choose not to group supplier invoices, then select one of the following supplier invoice export options.
• As New Additions: Sends each expenditure item on a supplier invoice line to Oracle Fusion Assets as a separate
addition line with a status of New.
• As Merged Additions: Sends each supplier invoice line to Oracle Fusion Assets as a separate addition line with the
status of Merged.
Note
After the addition lines are sent to Oracle Fusion Assets, you can split, merge, or unmerge the lines manually in
Oracle Fusion Assets.
351
Capitalized Interest Options

Use this field to specify a default interest rate schedule for capitalized interest.
You can select the Allow Override option to allow an override of the default capitalized interest rate schedule for individual
projects.
Associating Project Types and Class Categories:

Examples
Project classifications group your projects according to categories and codes that you define. When you associate project
classifications with project types, the classification is available for selection on projects with that project type.
Use any of the following methods to associate class categories with project types:
• Add a classification to the project type definition
• Add a project type to the class category definition
• Enable the Assign to all Project Types option on the class category definition
Add Classification to Project Type Definition

The following diagram shows an example of three classifications that are associated with a project type definition. In this
example, the Industry Sector, Reporting Group, and Media Sector classifications are available for selection on projects with
the Sales Proposal project type.
For each classification that you associate with the project type, you can enable the Assign to All Projects option for the
application to automatically add the classification to the project definition for all new projects with the project type. When this
option is enabled, all projects with this project type must be assigned a class code for the class category.
352
Add Project Type to Class Category Definition

The following diagram shows an example of three project types that are associated with a class category definition. In
this example, the Industry Sector classification is available for selection when you create projects with the Sales Proposal,
Consulting, or Internal project types.
For each project type that you associate with the class category, you can enable the Assign to All Projects option for the
application to automatically add the class category to the project definition for all new projects with any of these project types.
When this option is enabled, all projects with this project type must be assigned a class code for the class category.
Assign to All Project Types

The following diagram shows an example of a class category definition with the Assign to All Project Types option enabled.
In this example, a code for the Industry Sector class category is required for all projects, regardless of the project type.
353
Asset Cost Allocation Methods: Explained

The asset cost allocation method determines how indirect or common costs incurred on a project are allocated to multiple
assets.
You can specify an asset cost allocation method to enable Oracle Fusion Projects to automatically allocate unassigned asset
lines and common costs across multiple assets. Unassigned asset lines typically occur when more than one asset is assigned
to an asset grouping level.
Project templates and projects inherit a default asset cost allocation method from the associated project type. You can
override the default at the project level. If you use capital events to allocate costs, then you can also override the asset cost
allocation method at the event level.
Asset Cost Allocation Methods

The following table describes the available asset cost allocation methods.
Method Basis of Cost Allocation
Actual Units Number of units defined for each asset

Client Extension Rules defined specifically for your organization

Current Cost Construction-in-process (CIP) cost of each asset

Estimated Cost Estimated cost of each asset

Standard Unit Cost Combination of the standard unit cost and the number
of units defined for each asset

Spread Evenly Equal allocation of cost to each asset

Related Topics
• What's a standard unit cost method?
354
Implementing Project Financial Management Project Foundation Configuration: Define Action Controls
20 Project Foundation Configuration: Define Action

Controls
Action Controls: Explained

Action controls control data that is imported from Microsoft Project to Project Financial Management applications in Oracle
Fusion Project Portfolio Management. An action control prevents you from performing an action in Oracle Fusion Project
Portfolio Management on a record that originated in Microsoft Project.
Available Action Controls

You can set controls on the following actions:
• Add Task
• Delete Task
• Update Project Dates
• Update Project Description
• Update Project Name
• Update Project Number
• Update Project Organization
• Update Project Status
• Update Task Dates
• Update Task Description
• Update Task Name
• Update Task Number
• Update Task Organization
For example, consider the following scenario:
• You imported a project from Microsoft Project.
• Your business rule states that project and task dates are always maintained in Microsoft Project.
• To ensure data integrity, you want to prevent projects and tasks that originate in Microsoft Project from being
deleted in Oracle Fusion Project Portfolio Management.
355
Implementing Project Financial Management Project Foundation Configuration: Define Action Controls
To enforce this rule, you enter the following action controls for the source Microsoft Project:
• Update Project Dates
• Update Task Dates
• Delete Task
356
Implementing Project Financial Management Project Foundation Configuration: Distribute and Install
Desktop Integrator Client
21 Project Foundation Configuration: Distribute

and Install Desktop Integrator Client
Project Cost Transactions: How They Are Imported to

Oracle Fusion Project Costing
Collect and import all types of project costs from Oracle Fusion and third-party applications. During this process you can
validate transactions to reduce corrections and rework. Before you import the transactions to Oracle Fusion Projects, you can
review the exceptions for third-party transactions and correct the errors.
Settings That Affect Transactions Import

Setup options in the transaction document and document entry specify how the transactions are imported and processed
How Transactions Are Imported

You create, validate, and transfer the transactions to the Oracle Fusion Project Costing interface as specified in the following
table.
Transactions Type Creating Transactions Validating Importing

Transactions Transactions
Oracle Fusion Projects Initially only in Excel Validation is compulsory Click the Export button
Costs templates. and is performed in Excel spreadsheet to
automatically during export, and optionally
• Uncosted labor You can later edit or transaction entry. process, transactions.
transactions add transactions in the
Manage Unreleased
• Uncosted nonlabor Expenditure Batches
transactions page.

357
Third-Party Application Web services, ADFDI If you are using the Excel Methods to import :
Costs Excel templates, or integration, optionally
Oracle Cloud templates. validate transactions • For Excel
• Uncosted labor during export. integration, click
transactions You can also create the Export button
transactions in the Note on the Excel
• Uncosted nonlabor Manage Unprocessed Validation is spreadsheet
transactions Transactions page. optional when you to export, and
enter or export optionally process,
• Costed or transactions but is transactions.
accounted labor always performed
or nonlabor when you run • Use Oracle
transactions the Import and Fusion Project
Process Costs Costing Web
Transactions services to transfer
process. transactions to
the Oracle Fusion
Project Costing
interface.
• For Oracle Cloud,

use the Load
Interface File for
Import process.
You can load data
to interface tables
using predefined
templates and the
Load Interface
File for Import
scheduled process,
which are both part
of the External Data
Integration Services
for Oracle Cloud
feature. For more
information, see
the Documentation
tab for the Load
Interface File for
Import process in
Oracle Enterprise
Repository for
Oracle Fusion
Applications.
358
Costs from Other Fusion Source applications Validation is compulsory. Use the Import
applications As transactions are and Process Cost
validated in their source Transactions process.
applications, they are
not validated again
during the Import
and Process Costs
Transactions process.
All transactions are validated but at various points, transaction entry or transfer, or processing. If you are exporting
transactions from desktop Excel integration spreadsheets, you can release the transactions directly from the spreadsheet
itself by selecting the Process Costs option. Costs are submitted for Import and Process Cost Transactions process
avoiding the need to do it from the application.
Restriction
The Process Costs option is not available in the Excel template, when you have separate duties for entering and
releasing Oracle Fusion Projects expenditure batches. You can review the expenditure batches in the Manage
Unreleased Expenditure Batches page and submit them for processing.
After the transactions are imported to Oracle Fusion Projects, the application tracks transactions with errors including the
details for the cause of the error and the action to be taken to fix the error. While the successful transactions are ready for
cost processing.
Related Topics
• Project Costs: How They're Validated
• Transaction Document Import and Accounting Options: Points to Consider
• Source, Document, and Document Entry Components: How They Work Together
Document and Document Entry Edit Options of

Predefined and Third-Party Sources: Explained
You can define the transaction document and document entry options for transactions that originate from predefined sources
and third-party applications sources. However, there is a limitation in editing these options. The options that you can edit for
each source depend on whether the document entry is predefined for use with Oracle Fusion Applications or defined during
implementation for use with third-party application sources.
Document Edit Options

The following table provides a list of document options that you can edit for predefined and third-party application source
transactions.
Note
For third-party application source transactions, the following table details whether the options are editable after
you have created and imported transactions for the source.
359
Document Options Predefined Sources Third-Party Application Sources
Archive After Import Editable Editable

Allow Duplicate Reference Not editable Not editable

Allow Override of Person Not editable Not editable

Organization

Import Raw Cost Amount Not editable Not editable

Import Burdened Amount Not editable Not editable

Accounted in Source Application Not editable Not editable

Create Raw Cost Accounting Not editable Not editable

Journal Entries

Create Adjustment Accounting Editable Editable

Journal Entries

Reconcile with Source Not editable Editable

Document Entry Edit Options

The following table provides a list of document entry options that you can edit for predefined and third-party application
source transactions.
Note
Document Entry Options Predefined Sources Third-Party Application Sources
Expenditure Type Class Not editable Not editable

Allow Adjustments Editable Editable

Allow Reversals Not editable Editable

360
Allow Interface Modifications Not editable Editable

Process Cross-Charge Editable Editable

Transactions

Create Related Items Editable Editable

Related Topics
• Source, Document, and Document Entry Components: How They Work Together
• Transaction Document Import and Accounting Options: Points to Consider
FAQs for Distribute and Install Desktop Integrator

Client
Can I change the source and document for transactions after

exporting them to Oracle Fusion Projects?
No. You can't change the source, document, and document entry after creating a transaction.
What's the difference between export and desktop integration

for Excel?
Use the Export button or menu option to download data from a table to view or analyze. You get a Microsoft Excel file, of any
type that Excel supports, with records from the table.
Use the desktop integration for Excel to create or edit records in an Excel workbook and upload the records back into the
application. It's helpful for mass updates or working offline. In most cases, you download the desktop integrated workbook
from a link in the regional area or from a table.
Related Topics
Why can't I find the business unit in the downloaded desktop

Excel integration spreadsheets?
If your access is revised, then you have to download the desktop Excel integration spreadsheets again. For example, if you
initially have access to Vision Operations business unit, then you view only this business unit listed in the Excel spreadsheets.
361
If new business units are assigned or removed, you must download the templates again to view the business units according
to your access in the Excel spreadsheets.
362
Implementing Project Financial Management Project Control Configuration: Overview
22 Project Control Configuration: Overview
Budgeting and Forecasting Security: Explained

Budget and forecast security is determined by a combination of project role, security roles (job and duty roles) and
entitlements, and workflow setup.
The following sections describe the entitlements required to perform various steps in the budget creation, submission, and
approval process. They also describe the impact of using workflow to manage status changes.
Note
The entitlements and workflow setup for forecasting mirrors that for budgeting.
Creating and Submitting a Budget Version

The following text and table describe the access required to create and submit a budget version.
Step Action Entitlement
1 Access budget versions for a Manage Project Budget

project

2 Create a budget version Create Project Budget

Note
The entitlement required
for editing budget versions
in Excel is Manage Project
Budget Excel Integration.

3 Submit working version Manage Project Budget Working

Version

4 Create baseline directly Create Baseline Version Data

Note
Project managers
may select to create a
baseline directly instead
of submitting a version for
approval first.

363
Creating a Baseline for a Budget Version

The following text and table describe the access required to create a baseline for a budget version or reject it.
1 If using workflow, receive NA (Approver e-mail ID is entered

notification of budget submission manually by users)

364

project

3 Create baseline or reject budget Create Baseline Version Data

365
Reworking a Rejected Budget Version

The following text and table describe the access required to required to rework a rejected version (set it back to Working
status) or delete it, if it is no longer required.

project

2 Rework working version Manage Project Budget Working

Version

3 Delete working version Manage Project Budget Working

Version

366
Related Topics
• Project Roles in Budgeting and Forecasting: Explained
Budget and Forecast Workflow: Explained

Use Business Process Engineering Language (BPEL) workflows to manage budget and forecast approvals. To do so, select
to use workflow for status changes when creating or editing a financial plan type.
The following is a description of security considerations, approval rules, and the workflow process.
Addressing Security and Setting Approval Rules

Project managers and project administrators can create budget or forecast versions and submit them for approval. However,
only the designated project manager for the project can approve budget or forecast versions.
367
Submitted versions undergo a single level of approval. However, during implementation, you can define approval rules based
on the following parameters:
• Total raw cost
• Total burdened cost
• Labor effort
• Equipment effort
• Margin percentage
• Margin
For example, set rules like the following:
• If total burdened cost is less than or equal to $50,000, then the project administrator can approve budget versions.
• If total burdened cost is greater than $50,000, then the project manager must approve budget versions.
Understanding the Budget and Forecast Status Flow

The following table and graphic describe the stages in the budget and forecast status flow.
Action Performed Status Notification Sent To Action Required
Create version Working Creator (requester) None.

Submit version Submitted Requester and approver Approver can approve or

reject version.

Approve version Approved or Baseline Requester and approver None.

Reject version Rejected Requester and approver None. Requester can

optionally rework version.

Rework version Working Requester and approver None.

368
Project Roles in Budgeting and Forecasting:

Explained
Default project roles, including project application administrator, project manager, and project administrator can perform
specific budgeting and forecasting tasks.
Default Access for Roles

The following table describes the default access for each role.
369

Administrator
Edit budget and Yes No No Project application

forecast planning administrators set
options planning options
for financial plan
types.

Project managers
and accountants
can view planning
options at the
version level.

Create versions No Yes Yes None

Generate versions No Yes Yes Applies to budgets

generated when
setting a baseline
for the project
plan.

Project
administrators
can't generate
forecasts from
progress (they
don't have
access to publish
progress.)

Edit versions in No Yes Yes None

Excel

Submit versions No Yes Yes None

370

Administrator
Approve versions No Yes No A team member

with project
manager security
role access must
be manually
designated as the
project manager
for the project.

Note
Project
creators
aren't
automatically
designated
as project
managers
for their
projects.

If workflow
is enabled,
then approval
occurs through a
notification. Menu
actions aren't
available on the
budgeting and
forecasting pages.

Review versions No Yes Yes None

FAQs for Project Control Configuration: Overview
What happens when a budget or forecast version is

submitted?
Several changes occur when you submit a current working version of a budget or forecast for approval.
• The version status changes to Submitted.
• If the project manager approves the version, the version status changes to either Current Baseline or Current
Approved.
371
Note
A new current working version is created simultaneously when you submit the current working version for
approval.
If you use Business Process Engineering Language (BPEL) workflow for status changes, then submitting a budget or forecast
triggers a notification to the project manager and the requesters must manually specify the approver details.
372
Implementing Project Financial Management Project Control Configuration: Manage Period Profiles
23 Project Control Configuration: Manage Period

Profiles
Period Profiles: Explained

Period profiles specify how periods are grouped and displayed when you edit financial or project plans that allow entry of
amounts based on a calendar.
Important
Period profiles don't affect the periods for which you enter amounts. That is determined by the start and end
dates of the financial or project plan line.
You select a period profile when specifying plan settings for a financial plan type or a project plan type. With the appropriate
access, you can override this selection when creating budget or forecast versions for a project. Similarly, you can override the
period profile associated with the project plan type at the project template or project level.
Period profiles are based on groups of periods from either an accounting calendar or a project accounting calendar. You can
define an unlimited number of period groupings of varying duration in a period profile.
Predefined Period Profiles

The Project Financial Management applications contain two predefined period profiles:
• One based on the accounting calendar
• One based on the project accounting calendar
Both have 52 single period groupings. That is, each period grouping contains one period of a week's duration.
Selecting a Current Period for a Period Profile:

Example
You designate one period grouping in a period profile as the current period. The current period provides a reference point for
grouping historical, current, and future period amounts.
When reviewing financial or project plans, the current planning period determines the period grouping with the current period.
Periods before and after the current period are grouped using the period groupings. Amounts for periods outside the range
specified by the period profile are summed and displayed as total amounts for a preceding period or succeeding period.
Scenario
The following table describes a period profile set up to accommodate detailed and summary-level planning for long-term
projects. This period profile enables entry of amounts for a mix of monthly, quarterly, semiannual, and annual periods for a
span of five years.
373
Period Grouping Number of Periods Year
1 12 1

2 6 2

3 3 2

4 3 2

5 1 3

6 (current period) 1 3

7 1 3

8 1 3

9 1 3

10 1 3

11 3 3

12 3 3

13 12 4

14 12 5

Assume that the period profile is associated with a project with the following details:
• Start Date: July 1, 2005
• Duration: 10 years
• Current Planning Period: Aug-2010
When you review financial or project plans, information appears as follows:
374
Period or Period Group Number of Periods Duration
Preceding 36 July 2005 to June 2008

1 12 July 2008 to June 2009

2 6 July 2009 to December 2009

3 3 January 2010 to March 2010

4 3 April 2010 to June 2010

5 1 July 2010

6 1 August 2010

7 1 September 2010

8 1 October 2010

9 1 November 2010

10 1 December 2010

11 3 January 2011 to March 2011

12 3 April 2011 to June 2011

13 12 July 2011 to June 2012

14 12 July 2012 to June 2013

Succeeding 36 July 2013 to June 2015

375
Using Period Profiles: Examples

Period profiles specify how periods are grouped and displayed when you edit financial or project plans that allow entry of
amounts based on a calendar.
The following are examples of defining period profiles for planning short-term and long-term projects. Both examples assume
the use of one-month periods from the accounting calendar.
Period Profiles for Short-Term Projects

The following table describes a period profile configuration that accommodates detailed planning for short-term projects. This
period profile enables entry of amounts by month for a period of one year.
Period Grouping Number of Periods
1 1

2 1

3 1

4 1

5 1

6 1

7 1

8 1

9 1

10 1

11 1

12 1

376
Period Profiles for Long-Term Projects

The following table describes a period profile configuration that accommodates detailed and summary-level planning for long-
term projects. This period profile enables entry of amounts for a mix of monthly, quarterly, semiannual, and annual periods for
a span of five years.
Period Grouping Number of Periods Year
1 12 1

2 6 2

3 3 2

4 3 2

5 1 3

6 1 3

7 1 3

8 1 3

9 1 3

10 1 3

11 3 3

12 3 3

13 12 4

14 12 5

377
Implementing Project Financial Management Project Control Configuration: Manage Spread Curves
24 Project Control Configuration: Manage Spread

Curves
Spread Curves: Explained
Spread curves let you distribute quantity, cost, and revenue amounts automatically across accounting or project accounting
periods. You assign a spread curve to each resource class. Planning resources (in the planning resource breakdown
structure) inherit the spread curve setting from the associated resource class. You can change the spread curve for the
planning resource and for any corresponding task assignments, or budget or forecast lines.
You can create spread curves, use predefined spread curves, or edit them as required. This topic describes the following
spread curve components:
• Spread curves
• Spread points
• Distribution factors
• Predefined spread curves
Spread Curves, Spread Points, and Distribution Factors

Spread curves other than Daily Spread Basis and Even contain 10 spread points. Specify distribution factors for any
combination of the spread points.
Note
When using a daily spread basis, the application allocates amounts to each period based on the ratio of the days
in the period to the duration of the task assignment.
Spread points are distributed proportionately across periods during financial or project planning. For example, if amounts
are to be spread across four periods, the application allocates the combined value of 2.5 spread points to each period. The
spread points for each period are the total number of spread points divided by the total number of periods (10 / 4).
Distribution factors are prorated according to the spread points allocated to each period. For example, if $100 is to be spread
across four months for a planning resource that uses an even spread curve (where amounts are distributed evenly), the
application assigns each period $25. The amount assigned to each period is the total amount multiplied by the spread points
for the period (2.5 * 10).
Important
Spread points without values are assigned a zero distribution factor and hence corresponding periods aren't
allocated any amounts.
Predefined Spread Curves

The following table lists the predefined spread curves:
Name Description Distribution Factors
Even Linear distribution of financial or 10-10-10-10-10-10-10-10-10-10

project plan values across periods.
378
Name Description Distribution Factors

Prorated Even Linear distribution of financial or 10-10-10-10-10-10-10-10-10-10

project plan values across periods,
with an exception of the first period
and last period in the financial plan.
Financial or project plan values for
the first period and last period are
prorated based on the number of
days in the period.

Back Loaded Back-loaded distribution of financial 0-5-10-15-20-25-30-35-40-45

or project plan values across
periods. Assigned amounts
increase over succeeding periods.

Front Loaded Front-loaded distribution of 45-40-35-30-25-20-15-10-5-0

financial or project plan values
across periods. Assigned amounts
decrease over succeeding periods.

S Curve S-shaped distribution of financial or 18-10-8-10-15-17-18-17-15-8

project plan values across periods.

Bell Curve Bell-shaped distribution of financial 0-4-10-12-14-12-10-4-0-0

or project plan values across
periods. Assignment of plan values
is highest in the middle periods.

Daily Spread Basis Spread is based upon the number None

of days in each financial period
throughout the duration of the
task assignment. Amounts
are proportionally distributed
throughout all periods for the
duration of the task assignment.

Project and Financial Plan Period Amounts: How They

Are Calculated Using Daily Spread Basis
Assign the Daily Spread Basis spread curve to a resource class or planning resource to proportionately distribute budget,
forecast, or project plan amounts across periods based on the ratio of the days in each period to the duration of the task
assignment.
379
Settings That Affect Amount Distribution

You can't define spread points for the Daily Spread Basis spread curve. Therefore, distribution factors aren't calculated.
Task assignment start and finish dates determine the number of days in each period, including the first and last periods, and
consequently the allocation factor for each period.
Note
Assignment start and finish dates are included in the number of days in the period.
How Daily Spread Basis Amounts Are Calculated

When calculating period amounts, Oracle Fusion Project Portfolio Management performs the following steps:
1. Determines the number of days in the first and last period within the task assignment duration using assignment
start and finish dates.
2. Determines the number of days in the other periods within the assignment duration.
3. Determines the total number of days for the duration of the task assignment.
4. Calculates the allocation factor for each period using the following formula:
Period Allocation Factor = Number of Days in Period / Task Assignment Duration
5. Calculates the periodic amount using the following formula:
Amount = Period Allocation Factor * Total Resource Cost or Revenue
Example: Standard Accounting Calendar

In this example, a company uses an accounting calendar with periods that are identical to calendar months. A resource is
assigned to a task for 121 days, from February 21 until June 21.
The following table shows how the task assignment days are determined, and the resulting allocation factors.
Month Period Dates Days in Period Task Period Allocation

Assignment Factor
Days
January January 1 through 31 0 0

January 31

February February 1 28 8 8 / 121 = 0.0661

through February
28

March March 1 through 31 31 31 / 121 = 0.2561

March 31

380
Month Period Dates Days in Period Task Period Allocation

Assignment Factor
Days
April April 1 through 30 30 30 / 121 = 0.2479

April 30

May May 1 through 31 31 31 / 121 = 0.2561

May 31

June June 1 through 30 21 21 / 121 = 0.1735

June 30

121 121 / 121 = 1

Example: 4-4-5 Accounting Calendar

In this example, a company uses a 4-4-5 accounting calendar, with four weeks in the first and second months of the quarter,
and five weeks in the third month of the quarter. A resource is assigned to a task from February 21 until June 21.
The following table shows how the task assignment days are determined, and the resulting allocation factors.
Month Weeks Week Ledger Ledger Days Days Task Period

in Number Start End in in Assignment Allocation
Period Date Date Period Ledger Days Factor
January 4 1 1 7 7

2 8 14 7

3 15 21 7

4 22 28 7 28 0 0

February 4 1 29 4 7

2 5 11 7

3 12 18 7

381

4 19 25 7 28 5 5/
121 =
0.0413

March 5 1 26 4 7

2 5 11 7

3 12 18 7

4 19 25 7

5 26 1 7 35 35 35 /
121 =
0.2892

April 4 1 2 8 7

2 9 15 7

3 16 22 7

4 23 29 7 28 28 28 /
121 =
0.2314

May 4 1 30 6 7

2 7 13 7

3 14 20 7

4 21 27 7 28 28 28 /
121 =
0.2314

382

June 5 1 28 3 7

2 4 10 7

3 11 17 7

4 18 24 7

5 25 1 7 35 25 25 /
121 =
0.2066

121 121/121
=1

Calculating Distribution Factors for Spread Curves:

Examples
Distribution factors are prorated according to the spread points allocated to each period.
For example, if $100 is to be spread across four months for a planning resource that uses a prorated even spread curve
(where amounts are distributed evenly), then each period is assigned $25 each. That is, 10 spread points spread over 4
months equals 2.5 spread points per period. Each spread point has a distribution factor of 10.
The following is a description of how distribution factors are calculated for full or partial periods.
Calculating Weighted Distribution Factors

To continue our previous example: Say our planning resource was using a back-loaded spread curve rather than a prorated
even spread curve.
Note
Default distribution factors for a back-loaded spread curve are as follows: 0-5-10-15-20-25-30-35-40-45. Hence
the total distribution for the spread curve is 225.
The following table describes how distribution factors are determined and amount allocated over the four planning periods.
383
Period Distribution Weighted Distribution Distributed

Factor Distribution Percentage Amount
Calculation Factor
1 Distribution factors 10.0 4.44%, (10.0/225) $4.44

assigned to
spread points 1
and 2 plus half of
the distribution
factor assigned to
spread point 3: 0
+ 5 + (0.5 * 10)

2 Half of distribution 40.0 17.78%, $17.78

factor assigned (40.0/225)
to spread point 3
plus distribution
factors assigned
to spread points 4
and 5: (0.5 * 10) +
15 + 20

3 Distribution factors 72.5 32.22%, $32.22

assigned to (72.5/225)
spread points 6
and 7 plus half of
the distribution
factor assigned to
spread point 8: 25
+ 30 + (0.5 * 35)

4 Half of distribution 102.5 45.56%, $45.56

factor assigned (102.5/225)
to spread point 8
plus distribution
factors assigned
to spread points 9
and 10: (0.5 * 35)
+ 40 + 45

Totals 225 100% $100

384
Deriving Spread Point Values and Prorating Distribution

Factors for Partial Periods
Transaction start dates associated with a planning resource or task frequently don't coincide with the start or end dates of a
period. In such a case, the actual number of planning resource or task transaction days determines how spread points and
constituent distribution factors are allocated to full and partial periods.
Assume that the dates for a task assignment cover only 15 days of the first month (a 30-day month) of a four-month planning
period. That first month represents the value of 0.5 spread points.
In such a case, the spread point value for each full period is calculated by dividing the total number of spread points (10) by
the number of periods corresponding to the transaction (3.5). In other words, spread point values are as follows:
• Full period : 10/3.5 = 2.8571
• Partial Period: (10/3.5) * 0.5 = 1.4287
Related Topics
• How are distribution factors calculated for forecast ETC periods?
385
Implementing Project Financial Management Project Control Configuration: Manage Financial and Project
Plan Types
25 Project Control Configuration: Manage Financial

and Project Plan Types
Financial and Project Plan Types: Explained

Financial plan types contain default setup information and planning options that you use for creating different types of
budgets or forecasts. Similarly, project plan types contain default information used for creating a project plan and capturing
progress.
When creating budget or forecast versions for a project, you must select an appropriate financial plan type. Versions inherit
planning options from the financial plan type. Depending on access levels, you can change some settings.
You associate one project plan type to a project template, and override planning options if required. Projects created using
the template inherit the updated planning options. You can revise these options at the project level, or even replace the
project plan type.
Financial and Project Plan Setup Options

The following is a description of the basic budget, forecast, or project plan setup options that determine how a plan type is
used in the context of a project. Except for third-party scheduling, you can't edit these options at the project level.
Option Location Description
Planning amounts Financial plan type Indicates that the financial plan type
supports the creation of versions
with the following amounts:
• Cost amounts
• Revenue amounts
• Both cost and revenue

amounts
• Either cost or revenue

amounts
Approved budget or primary Financial plan type Determines whether a financial plan
forecast type is used for creating approved
budget versions or primary forecast
versions that are used for plan
comparison or project performance
reporting.

Default financial plan type Financial plan type Determines whether the financial
plan type is the default selection
when you create budget or forecast
versions.
386
Plan Types
Option Location Description

Workflows Financial plan type Enables the use of a workflow for

managing budget or forecast status
changes.

Third-party scheduling software Project plan type Indicates whether project planning
is performed in Microsoft Project.

If third-party scheduling is disabled
in the project plan type, you can
use the associated project or
project template to create a project
in Microsoft Project. However, you
can't export the new project or link
it to one created in Oracle Fusion

Note
The third-party scheduling
option doesn't affect
integration with Primavera
P6 Enterprise Project
Portfolio Management.

Multiple transaction currencies Financial and project plan type Enables entry of plan amounts in
currencies other than the project
currency.

Budgetary control settings Financial plan type Manages options for creating
control budgets in Oracle Fusion
Budgetary Control.

Financial Plan Types and Project Budget Versions:

How They Work With Budgetary Controls
Financial plan types and budget versions in Oracle Fusion Project Control contain attributes that enable you to automatically
create control budgets in Oracle Fusion Budgetary Control. Configuring these attributes on a financial plan type enable the
budget versions that you create from that financial plan type to create control budgets.
This figure shows the components of a financial plan type that you must configure to enable a project budget version for
creating a control budget in Oracle Fusion Budgetary Control. The general budget information includes the plan class,
387
Plan Types
planning amounts, and the enable budgetary controls option. The budgetary control settings are the control budget, control
level, default rate type, and tolerance percentage.
General Information and Budget Options

Select the following options on the Edit Financial Plan Type page:
• Plan Class: Budget
• Planning Amounts: Costs
Enable the financial plan type for budgetary controls. If you don't select this option, the Budgetary Control Settings tab won't
be available in the Planning Options section of the financial plan type or budget versions.
Restriction
A project can have only one financial plan type that is enabled for budgetary controls. If a financial plan type that
is enabled for budgetary controls is used by a budget version on a project, then you can't create another budget
version with a different financial plan type enabled for budgetary controls.
Budgetary Control Settings

The Budgetary Control Settings tab in the Planning Options section of the financial plan type and budget version contains the
instructions for creating control budgets. The following table describes the attributes and their impact on control budgets.
Attribute Name Description
Control Budget The level in the project hierarchy at which you can enter
budgetary control amounts.

Enter amounts in the budget version at either the project
level or the top resource level. The control budget will
388
Plan Types
Attribute Name Description
contain those amounts, and Oracle Fusion Budgetary
Control will use the project and top resource information
to create the control budget account segments.

Control Level The level of funds reservation for expenditures that

impact the control budget.
The levels are:
• Absolute: Reserve funds for transactions that

impact the control budget only if funds are
available in the budget.
• Advisory: Reserve funds for transactions that

impact the control budget whether or not enough
funds are available in the budget. However, you
can review any exceptions that are generated if a
transaction exceeds the funded amount.
• Track: Reserve funds for all transactions that

impact the control budget. Don't issue a
notification if a transaction doesn't have enough
funds in the budget.
Default Rate Type The rate type that converts the amount of a transaction
to the currency used in the control budget before the
funds check.

Tolerance Percentage The percentage by which a transaction can exceed

the budgeted amount before Oracle Fusion Budgetary
Control issues a warning notice or restricts the funds
reservation.

Related Topics
• Why can't I edit the budgetary control settings for a budget version?
Planning Amounts in Financial Plan Versions: Critical

Choices
For each financial plan type, you select the planning amounts included in the financial plan versions created using the plan
type.
Options include the following:
• Cost amounts only

• Revenue amounts only
389
Plan Types
• Both cost and revenue amounts
• Either cost or revenue amounts
Planning for Cost Only or Revenue Only

If you select to plan only for cost or revenue, then all budget or forecast versions created for the financial plan type contain
only those amounts.
When you review versions created for cost-only financial plan types, margin values and other comparisons dependent on
revenue amounts aren't available. Similarly, cost amounts are unavailable during review of versions of revenue-only financial
plan types.
Planning for Both Cost and Revenue

You can select to plan for cost and revenue together. In such a case, each budget or forecast version created for the financial
plan type contains both cost and revenue amounts.
Planning for Either Cost or Revenue

If you select to plan for cost and revenue separately, then each budget or forecast version created for the financial plan type
can contain either cost or revenue amounts. When you review cost versions, select any revenue version created for the same
financial plan type as the source for revenue amount for use in plan comparison.
Summarized Financial Plan Types: Explained

Summarized financial plan types are financial plan types whose previous and current approved versions (for forecasts) or
original and current baseline versions (for budgets) are used in summarization of project performance data.
Particular financial plan types are included in summarization by default, while you must manually select others.
Default Financial Plan Types

Approved forecast and baseline budget versions of the following financial plan types are automatically included in
summarization of project performance data:
Important
A budget or forecast financial plan type may support both cost and revenue in one version.
User-Selected Financial Plan Types

Tip
You can include a financial plan type before it is used on a project for creating a version.
You can replace a user-selected financial plan type until project performance data is summarized for reporting. After that, you
can only disable the financial plan type to exclude it from further summarization.
390
Plan Types
Related Topics
• Performance Data Summarization: How It Is Calculated
Manage Financial and Project Plan Types: Set

General Planning Options
Associating Sets with Financial Plan Types: Example

You associate sets with financial or project plan types so that project managers can use them to create financial plans
(budget or forecast versions) or project plans for projects or project templates. Financial or project plan types are available for
selection only when projects or project templates are created for project units linked to selected sets.
The following example illustrates the relationship between financial plan types, sets, and project units. Project plan types
share an identical relationship with sets and project units.
Scenario
An organization has two designated project units for project creation: Project Unit 1 and Project Unit 2. Project Unit 1 is
associated with Set 1 and Project Unit 2 is associated with Set 2.
During implementation, two financial plan types were created: Financial Plan Type A and Financial Plan Type B. Financial Plan
Type A is associated with Set 1. However, Financial Plan Type B is associated with both Set 1 and Set 2.
In such a case, project managers working on projects for Project Unit 1 can use only Financial Plan Type A to create financial
plan versions. Project managers working on projects for Project Unit 2 can use both Financial Plan Type A and Financial Plan
Type B.
391
Plan Types
The following diagram further illustrates the relationship between financial plan types, sets, and projects. Project plan types
share the same relationship with sets.
Selecting Rate Schedules for Project and Financial Planning:

Points to Consider
When specifying rate settings for financial or project plan types, you select to use either actual or planning rates for calculating
cost or revenue for planning resources.
Actual rates are those that are used for calculating actual amounts for expenditure items. If you use planning rates, then you
can select rate schedules created specifically for planning purposes.
The following is a description of the points to consider when selecting actual or planning rate schedules for calculating raw
costs, burdened costs, and revenue.
392
Plan Types
Selecting Rate Schedules when Using Actual Rates

When using actual rates for project plan types and financial plan types that support cost amounts, you select cost rate
schedules at the resource class level. Similarly, for financial plan types that support revenue amounts, you select bill rate
schedules at the resource class level. If the application is unable to determine cost or bill rates for a planning resource, then it
uses the resource class rates schedules you specify here.
Selecting Rate Schedules when Using Planning Rates

Some of the reasons for using planning rates are as follows:
• Project planning extends into the future, beyond dates for which actual rates are available. Using planning rates
enables you to plan for future periods by making assumptions about potential rate increases or decreases.
• Planning is at a more summary level than when using actual rates. For example, use job-based rate schedules to
plan, but actually track labor costs using cost rates defined at the employee level.
When using planning rates, you select rate schedules at the resource, job, and resource class levels. The following table
summarizes the precedence order for determining cost or bill rates for a planning resource when deriving raw costs or
revenue for rate-based planning resources.
Rate Source Precedence Description
Override rate 1 Rate manually entered by users

in the budget, forecast, or project
plan

Labor or nonlabor rate schedules 2 Rate schedules selected for labor

or nonlabor resources

Job rate schedules 3 Applicable only for labor resources

Resource class rate schedules 4 Used when rates are not available
at the resource level. Specifying
a resource class rate schedule is
optional.

Specifying a Burden Schedule when Using Planning Rates

Optionally specify a burden schedule when specifying planning rate schedules. Project Financial Management applications
use this burden schedule to calculate the burdened cost for all planning resources (including those that are not rate-based).
If an expenditure type is not associated with the planning resource, then Project Financial Management applications use the
expenditure type defined for the associated resource class to determine the burden multiplier, and ultimately, the burdened
cost.
393
Plan Types
Manage Financial Plan Types: Set Forecasting

Options
Forecast Approval Options: Critical Choices

Forecast approval options determine the approval process for forecast versions created for a particular financial plan type.
Approval options determine whether you can do the following:
• Use workflow and notifications for approvals
• Automatically approve forecast versions
• Automatically submit forecasts for approval when creating baseline budgets
Using Workflow for Status Changes

Select this option if you want to use Business Process Execution Language (BPEL) workflows and notifications for forecast
approvals. Workflows enable you to define a chain of approvers for moving forecasts from the working to the approved
status.
Automatically Approving Forecasts

If you don't use workflow for forecast approvals, then you can select to approve forecast versions directly. The automatically
approve forecasts option applies even if you aren't entitled to approve forecasts.
Tip
Use this option to enable automatic approval for certain financial plan types while controlling the forecast approval
entitlement for others.
For example, disable this option for primary forecast financial plan types to ensure that only entitled users approve
corresponding versions. Enable the option for other financial plan types that don't require explicit approval, for example, those
whose versions are used for what-if analysis.
Important
The automatic approval option applies only when manually approving forecasts. To approve forecasts versions
that are generated automatically when publishing progress, you must be entitled to approve forecasts.
Automatically Submitting Forecast for Approval

Automatic submission for approval applies only to primary forecasts. If you select this option, the current working primary
forecast version is submitted for approval when you create a baseline for an approved budget version for a project.
Important
If you select to automatically approve forecasts, the newly created working version of the primary forecast is
directly approved.
The option to automatically submit forecasts for approval doesn't apply when manually creating forecasts.
394
Plan Types
Related Topics
• Budget and Forecast Workflow: Explained
Manage Project Plan Types: Set Project Plan Options
Task and Assignment Date Settings: How They Work Together

Task and task assignment date options are selected when specifying project planning options. Task and assignment
date settings interact to determine how planned and transaction dates are set for tasks and how dates are set for task
assignments.
Rolling Up Planned Dates for Tasks

You can select to roll planned dates for lowest-level subtasks up the task hierarchy. In this case, planned dates for summary
tasks, top tasks, and the project are not editable. Edit planned dates for lowest-level tasks as required. Updated dates roll up
the hierarchy to ensure that planned dates at the summary and project level are equal to the earliest start date and the latest
end date of lower-level tasks.
Conversely, if you select not to roll up planned dates, lowest-level subtask dates are editable but must be within the planned
date range for summary tasks and the project. You can also edit project or summary task dates as required.
Synchronizing Task Transaction Dates with Planned Dates

If you select to synchronize transaction dates with planned dates, then task transaction dates are not editable. Transaction
dates always match task planned dates, plus or minus the number of days specified as a date adjustment buffer.
Tip
Specify a positive buffer value to indicate the number of days before the planned start date and the number of
days after the planned finish date that a transaction can be charged to a task. Conversely, specify a negative
buffer value to indicate the number of days after the planned start date and the number of days before the
planned finish date that a transaction can be charged to a task. In other words, when specifying a negative buffer,
transaction dates are within the range of the planned dates.
If you select not to synchronize transaction dates with planned dates, then transaction dates are blank by default and can be
edited as required. Transaction dates entered at the summary-task level are used as the default transaction dates for tasks
at lower levels. Transaction dates specified for subtasks must be within the transaction dates for the summary task. If none
of the summary tasks in the hierarchy have transaction dates, then the new transaction date must be within the project date
range.
You can modify the date synchronization option until you charge transactions to a task. Implications of changing between
options are as follows:
• Deselected to selected: Existing transaction dates are replaced with dates calculated based on task planned dates
plus or minus the date adjustment buffer.
• Selected to deselected: Existing transaction dates can be edited. New tasks have blank transaction dates that are
editable. Existing transaction dates outside the project dates are cleared.
Setting Task Assignment Dates Using Planned Dates for Tasks

If you select to base task assignment dates on task planned dates, task assignments span the entire task duration. Task
assignment dates are not editable.
395
Plan Types
Note
You can override this option for individual task assignments.
Project Date Cascade Options: Explained

Use cascade options to determine whether your changes to project dates cascade to tasks.
You can select one of the following options:
• Do not cascade date changes: Both start and finish dates are editable. However, you must ensure the following:
◦ The project start date is not later than the earliest task date.
◦ The project finish date is not earlier than the latest task date.
• Cascade change to the start date: You can edit only the project start date.
• Cascade change to the finish date: You can edit only the project finish date.
Restriction
If you have selected to roll up planned dates for tasks or are using an external application for scheduling, then you
cannot modify the project start or finish dates.
Cascading Changes to Transaction Dates

If you have selected to synchronize transaction dates with planned dates, then transaction dates are updated automatically
when date changes cascade to tasks.
Note
If transactions are already charged to a task, then you must ensure that your new summary dates are before or
after the transaction date (depending on whether you are cascading start or finish dates.)
Cascading Changes to Assignment Dates

If you have selected to synchronize task assignment dates with task dates, then your changes to project dates will cascade
to assignments automatically. Otherwise, you must ensure that all task assignment dates are within the range of the new task
dates.
FAQs for Manage Financial and Project Plan Types
What happens if I edit a financial or project plan type after

using it on a project?
Once you associate a project plan type with a project or project template, or create budget or forecast versions using a
financial plan type, you can't edit certain financial or project plan setup options. These options include the primary forecast
and approved budget designations, use of workflow, and the use of multiple transaction currencies.
396
Plan Types
Also, changes made to a financial plan type apply only to new financial plan versions. Similarly, there is no impact on existing
project associations when you modify a project plan type.
Why can't I select some financial plan types when generating a

budget version while setting a baseline for the project plan?
For generating a budget when setting a baseline project plan, you can select any active budget financial plan type otherwise
available for budget creation. However, some financial plan types (including the default financial plan type selected in the
budget generation options of the project plan type) are unavailable for selection in the following circumstances:
• If your project plan contains costs in multiple planning currencies, then only financial plan types that support planning
in multiple transaction currencies are available.
• If you have already selected an approved cost or revenue budget financial plan type for creating a budget version,
then no other approved budget financial plan types are available.
Why can't I enable budgetary control on a financial plan type?

Certain conditions must exist for you to enable the budgetary controls option on a financial plan type. You can enable
budgetary controls if:
• Budgetary control is enabled for the Project Accounting Business Function. Manage this option in the Manage
Budgetary Control task of the Setup and Maintenance work area.
• The financial plan type isn't enabled for multiple transaction currencies.
• The plan class is Budget.
• The planning amounts contain a cost component.
Note
The option to enable budgetary controls isn't present on the financial plan type if the planning amounts
are for revenue only.
Can I create a version of a financial plan type before I run

summarization?
Yes.
FAQs for Manage Financial Plan Types: Set Financial Plan

Options
What's an approved budget?
You can designate budget financial plan types as approved cost budgets, approved revenue budgets, or both. You use
versions of such financial plan types for plan comparison when reviewing budgets or forecasts. Approved budget versions are
also used by default when reporting on project performance.
397
Plan Types
For each project, you can use only one financial plan type that is designated as an approved cost budget or an approved
revenue budget. Either select separate financial plan types (one approved cost budget and one approved revenue budget) or
a single financial plan type with both designations.
What's a primary forecast?

You can designate forecast financial plan types as primary cost forecasts, primary revenue forecasts, or both. You use
versions of such financial plan types for plan comparison when reviewing budgets or forecasts. Primary forecast versions are
also used by default when reporting on project performance.
For each project, you can use only one financial plan type that is designated as a primary cost forecast or a primary revenue
forecast. Either select separate financial plan types (one primary cost forecast and one primary revenue forecast) or a single
financial plan type with both designations.
FAQs for Manage Project Plan Types: Set Project

Plan Options
What happens if I use Microsoft Project as a third-party

scheduling application?
Your ability to modify project and task dates in Oracle Fusion Project Foundation is limited in several ways. The limitations are:
• You can't modify the start and finish dates for the project and existing tasks.
• You can enter start and finish date for new tasks, however these dates must be within the planned dates for the
summary task.
• You can modify transaction dates, however they must be within both the task planned dates and transaction dates
for the summary task or project.
What's a baseline project plan?

Key planned information for tasks and task assignments, including dates, costs, quantity, effort, and rates, that you can save
from current project plan values. Setting a baseline for a project plan doesn't create a new plan version. Rather, current plan
information is saved in baseline columns of the current project plan.
You must set a baseline for your project plan before capturing progress. Baseline amounts determine earned value for lowest-
level tasks, which in turn are used to roll up physical percent complete to summary tasks.
You can't delete baseline data, and baseline data doesn't change unless you override it when you next set a baseline for the
tasks.
Tip
By generating a budget version when you set a baseline for your project plan, you can maintain an historical
record of past baseline data.
398
Implementing Project Financial Management Project Integration Gateway Configuration: Overview
26 Project Integration Gateway Configuration:

Overview
Oracle Fusion Project Foundation and Oracle Fusion

Project Management: How They Work Together
Use Oracle Fusion Project Foundation and other Project Financial Management applications to centrally perform project
costing, billing, accounting, and executive reporting. Export projects to Oracle Fusion Project Management to plan, progress,
and execute projects.
The following is a brief overview of how the applications work together.
Managing Integration Options

When defining integration options you do the following:
• Specify the integration name and project unit.
• Select an integration planning resource breakdown structure.
• Define how rates are derived when exporting resources.
• Specify how data is processed during import and export.
Exporting Planning Resources

Export labor resources and financial resources from the integration planning resource breakdown structure to create project
enterprise resources.
Exporting Project and Task Information

Activate the integration and export your project and tasks to perform detailed resource planning, scheduling, and progress
collection.
Restriction
Projects you previously exported to Primavera P6 Enterprise Project Portfolio Management, cannot be exported to
Oracle Fusion Project Management.
The initial export links project and task information in the two applications, and enables you to incrementally export project
and task data to Oracle Fusion Project Management. In Oracle Fusion Project Management, you can add subtasks under the
exported tasks. You can also assign resources to the subtasks to complete detailed planning.
Restriction
After you export a project, you cannot delete the exported tasks, increase or decrease indent, or move the
exported tasks within the project plan in either application.
399
Importing Project Plan and Progress Information

After you export a project to Oracle Fusion Project Management, build out the project plan, add subtasks under integrated
tasks, assign resources, and complete planning to the desired detail. When you are ready, import the updated project plan
and progress information.
When you import a project, the application summarizes planning and progress information for each resource across all
subtasks within the hierarchy of each integrated task. Summarized amounts are imported into a single task assignment
created for each resource on the integrated task.
A baseline project plan is automatically created in Oracle Fusion Project Foundation and progress is captured and published.
Based on project plan planning options, a baseline budget version can be generated using baseline project plan values and a
forecast version generated based on published progress.
Note
The current date is always used as the progress as-of date for published progress.
Related Topics
• Oracle Fusion Project Management Integration Options: Points to Consider
• Planning Resources: How They are Exported to Oracle Fusion Project Management
• Project Plans: How They are Transferred from Oracle Fusion Project Management
Primavera P6 Enterprise Project Portfolio

Management and Oracle Fusion Project Portfolio
Management: How They Work Together
Use Oracle Fusion Project Integration Gateway to integrate Oracle Fusion Project Portfolio Management with Primavera
P6 Enterprise Project Portfolio Management. The integration enables project accountants, project billing specialists, and
executives to centrally perform project costing, billing, accounting, and executive reporting tasks in Oracle Fusion Project
Portfolio Management while enabling each project manager to perform detailed project planning and scheduling in Primavera
P6 Enterprise Project Portfolio Management.
Note
Oracle Fusion Project Integration Gateway is currently not available in Oracle Cloud implementations.
Oracle Fusion Project Integration Gateway ensures data security, integrity, and efficiency by defining a set framework in which
data is exported from and imported into Oracle Fusion Project Portfolio Management.
The following table and diagram provide an overview of the flow of information.
Information Type From Application To Application
Global integration information Oracle Fusion Project Portfolio Primavera P6 Enterprise Project
Management Portfolio Management

400
Information Type From Application To Application
Projects and task definition Oracle Fusion Project Portfolio Primavera P6 Enterprise Project

Summarized project actual quantity Oracle Fusion Project Portfolio Primavera P6 Enterprise Project
and cost Management Portfolio Management

Project plans and progress Primavera P6 Enterprise Project Oracle Fusion Project Portfolio
Portfolio Management Management

Billing events Oracle Fusion Project Portfolio Primavera P6 Enterprise Project


Event completion Primavera P6 Enterprise Project Oracle Fusion Project Portfolio

Portfolio Management Management

401
Global Integration Information

Export resources from the integration planning resource breakdown structure and associated rates to the global dictionary for
resource and roles in Primavera P6 Enterprise Project Portfolio Management. Before export, raw or burdened cost rates are
derived using logic for actual cost rates, increasing the accuracy of planned costs calculated for planned units.
Export either accounting or project accounting periods to use in Primavera P6 Enterprise Project Portfolio Management and
to enable import of periodic project plans into Oracle Fusion Project Portfolio Management.
Project and Task Information

Create projects and the task structure required for financial management and reporting in Oracle Fusion Project Portfolio
Management. You can then activate project integration and export project and tasks.
402
Tip
Define a template called Oracle Fusion Applications Integrated Project Template in Primavera P6 Enterprise
Project Portfolio Management to create projects based on your preferences.
Export processing creates links between the project and tasks in Oracle Fusion Project Portfolio Management and the project
and WBS created in Primavera P6 Enterprise Project Portfolio Management. All export and import processing is dependent
on these links.
Actual Amount Information

Export summarized actual amounts, as required, for comparing with planned amounts. For each integrated WBS that is
linked to a lowest-level task, a summary activity is created to store actual quantity and costs in Primavera P6 Enterprise
Project Plan and Progress Information

After exporting a project and its tasks to Primavera P6 Enterprise Project Portfolio Management, you can build out the project
structure, add WBS nodes and activities, assign resources, and complete planning to the desired detail. Use resources, roles,
and expense categories created in the global dictionary based on the integration planning resource breakdown structure.
Tip
Integration supports manual creation of resources or planning for labor or nonlabor amounts directly against
activities in Primavera P6 Enterprise Project Portfolio Management.
Import project plan information into Oracle Fusion Project Portfolio Management as required. Before import, planned amounts
for each resource are totaled across all activities and child WBSs within the hierarchy of an integrated WBS. The summarized
planning amounts are imported into a single task assignment that Oracle Fusion Project Portfolio Management creates for the
resource against the lowest-level task associated with the integrated WBS.
After import, a baseline project plan is automatically created in Oracle Fusion Project Portfolio Management and progress is
captured and published. A baseline budget version can be created simultaneously based on project plan planning options.
Billing Information
For contract-based projects, you can export billing events that are assigned to milestone tasks to create finish milestone
activities under the integrated WBS in Primavera P6 Enterprise Project Portfolio Management.
Import event completion information into Oracle Fusion Project Portfolio Management, as required, so that you can initiate
contract billing activities.
403
Implementing Project Financial Management Project Integration Gateway Configuration: Define Project
Management Integration

Define Project Management Integration
Oracle Fusion Project Management Integration
Options: Points to Consider
Project integration options determine how Oracle Fusion Project Foundation and Oracle Fusion Project Management interact.
When defining integration options you specify the following.
• Integration definition information including the integration name and project unit.
• Integration planning resource breakdown structure.
• Resource rate options.
• Data processing options.
Selecting a Project Unit

You create an integration for a project unit. The project unit you select determines which planning resource breakdown
structure you can select as the integration planning resource breakdown structure.
Selecting a Planning Resource Breakdown Structure

Select the integration planning resource breakdown structure that is the source of labor resources and financial resources
exported to Oracle Fusion Project Management to create project enterprise resources.
Restriction
You must select a planning resource breakdown structure that does not allow resource changes at the project
level.
All projects exported from Oracle Fusion Project Foundation must use the integration planning resource
breakdown structure as the primary planning resource breakdown structure.
Specifying Resource Rates

Specify the source of actual cost and bill rates for the resources you export to Oracle Fusion Project Management. The
following table describes rate options.
Integration Option Description
Default business unit Business unit used to derive the rate schedules that are
the source of rates for resources exported to Oracle
Fusion Project Management.

Determines the currency used to display amounts in
Oracle Fusion Project Management after you transfer
project and task information. This currency is the primary
ledger currency of the business unit.
404

Resource class rate schedule Default source of cost rates when actual rates can't be
derived for the resource.

Burden schedule Determines rate calculation if you assign burdened rates

to project enterprise resources.

Effective rate date Date as of which rates are retrieved and exported.

Specifying Processing Options

Specify the number of records to be processed in each set when exporting resources or projects, or when importing project
plans from Oracle Fusion Project Management.
Planning Resources: How They are Exported to

Oracle Fusion Project Management
Export labor resources and financial resources to Oracle Fusion Project Management to enable project managers to plan
project tasks using a consistent set of resources and facilitate integration of task assignments with Oracle Fusion Project
Foundation.
Settings That Affect theExport of Planning Resources

Oracle Fusion Project Management integration options determine how planning resources are exported to create project
enterprise resources.
• Integration planning resource breakdown structure: Determines the planning resources you can export.
• Resource rate options: Determine how rates are derived for the planning resources.
The planning resources exported depend on whether you're performing an initial export for your integration or a subsequent
one. When you first export resources, all planning resources from the integration planning resource breakdown structure are
exported. During subsequent exports, you can select an incremental or a full export, as described in the table below.
Processing Type Incremental Impact
Incremental Export only resources that were added or modified since

the last time you successfully exported resources.

Full Export all resources from the integration planning

resource breakdown structure irrespective of when they
were created or modified.

405
Processing Type Incremental Impact
Tip
Use full export if you want to export rates for
all resources (new and existing) for a revised
effective rate date in Oracle Fusion Project
Management integration options.

Note
If you delete a previously exported planning resource from the integrated planning resource breakdown structure,
task assignments for the resource are treated as unplanned resources when you next import project plan
information from Oracle Fusion Project Management.
How Planning Resources Are Exported

As illustrated in the following figure, planning resources are exported to Oracle Fusion Project Management based on
resource type.
• Labor resources: If the resource is an HCM person, that is, the Named Person resource type is part of the resource
format, then the planning resource is exported as a Person project enterprise labor resource
406
• Financial resources: Exported only if the resource type is Expenditure Type
• Material items and equipment: Not exported
407
Implementing Project Financial Management Project Integration Gateway Configuration: Define Primavera
P6 Enterprise Project Portfolio Management Integration

Define Primavera P6 Enterprise Project Portfolio
Primavera P6 Integration Options: How They Work
Together
Project integration options determine how Oracle Fusion Project Portfolio Management interacts with Primavera P6 Enterprise
Note
Use integration options to do the following.
• Specify integration definition information including the integration name, business unit, project unit, and the
integration language.
• Select the integration planning resource breakdown structure.
• Specify resource rate options.
• Select the actual amount information for export.
• Specify calendar and period options.
Specifying the Integration Definition

When defining integration options, first select an integration created previously in Oracle Fusion Topology Manager, and the
business unit and project unit for the integration.
Warning
You can't change the integration name, business unit, or project unit after exporting data from or importing data
into Oracle Fusion Project Portfolio Management.
The project unit determines the planning resource breakdown structure you can select as the source of planning resources
exported to Primavera P6.
The business unit determines the ledger currency (the primary ledger currency for the business unit, that is, the project ledger
currency). Primavera P6 stores amounts in a single base currency across all projects. So, integration processing uses the
ledger currency to:
• Export all actual costs and resource rates

• Import cost amounts for expense categories and nonintegrated material resources
You also select an integration language that is used to export translatable text and store translatable information imported
from Primavera P6.
408
Selecting a Planning Resource Breakdown Structure

You can export resources from the integration planning resource breakdown structure to create labor, nonlabor, and material
resources, roles, or expense categories for use in Primavera P6.
In Oracle Fusion Project Portfolio Management, you must use this planning resource breakdown structure as the primary
planning resource breakdown structure on all integrated projects.
Using a single set of planning resources facilitates the creation of task assignments when you import project plan information.
Restriction
You can't change the integration planning resource breakdown structure after you export resources.
Specifying Calendar and Period Options

Select a common set of periods for planning in Oracle Fusion Project Portfolio Management and Primavera P6 to exchange
periodic planned amounts. The following table describes the impact of your selection.
Calendar type and financial period from date Together determine the type of calendar (accounting or
project accounting) and the date from which you export
periods.

Restriction
You can't modify the calendar type after you
export financial periods.

Default period profile Default period profile to use if Oracle Fusion Project
Portfolio Management must change the calendar type
for a project when importing the project plan. Options
are limited to period profiles associated with the selected
calendar type.

Restriction
The calendar type selected on the planning
options of the associated project plan type
must match the calendar type you specify in
the integration options.

Selecting Resource Rate Options

You can select options for exporting cost rates associated with the resources from the integration planning resource
breakdown structure. Primavera P6 maintains rates as part of the global dictionary for resources and roles.
The following table describes rate options.
409
Resource class rate schedule Used to specify a default source of cost rates when
rates can't be derived for the resource using logic for
actual cost rates.

Restriction
You can only select rate schedules that are
available to the integration business unit.

Burden schedule Used as the source of burdened cost rates when

calculating the resource rate to export. If you don't
specify a burden schedule, then the burdened rate
equals the raw cost rate for the effective rate date.

Effective rate date Date as of which rates are retrieved and exported.

Note
For roles, Primavera P6 doesn't maintain
date effective rates. That is, only a single rate
is available for each role.

Selecting Project Plan and Progress Options

Use the following options to determine how project plan and progress information is exported from and imported into Oracle
Fusion Project Portfolio Management.
WBS Code Source Determine whether to generate the WBS code in

Primavera P6 based on the task number in Oracle
Fusion Project Portfolio Management.

Alternatively, select not to export a value. In this case,
the WBS code source is automatically generated in
Primavera P6 and never updated based on data you
export. However, you can manually edit the value in
Primavera P6.

410
Export Actual Amounts Determine whether you want to export burdened cost,
burdened cost and quantity, or if you don't want to
export actual amounts. Use exported actual amounts to
compare with planned amounts for the WBS.

If you export actual amounts, Primavera P6 creates
a summary activity to store these amounts for each
affected WBS.

Import Progress with Existing As-of Date Decide whether project managers can import progress
for a date as of which latest published progress already
exists in Oracle Fusion Project Portfolio Management.

If you allow import, then existing progress information
is deleted and replaced by progress imported from the
scheduling application. Else an error is reported.

Related Topics
• What's a primary resource breakdown structure?
Planning Resources: How They Are Exported

to Primavera P6 Enterprise Project Portfolio
Management
Export planning resources to Primavera P6 Enterprise Project Portfolio Management to enable project managers to plan
project activities using a consistent set of resources and facilitate integration of resource assignments with Oracle Fusion
Projects.
Note
Settings That Affect the Export of Planning Resources

The integration planning resource breakdown structure you select when defining project integration determines the planning
resources you can export. In addition, the planning resources exported depend on whether you are performing an initial
export for your integration or a subsequent one.
When you export resources for the first time, all planning resources from the integration planning resource breakdown
structure are exported. Primavera P6 Enterprise Project Portfolio Management creates corresponding resources, roles,
or expense categories. If you subsequently export planning resources, you can select an incremental or a full export, as
described in the table below.
411
Processing Type Impact
Incremental Oracle Fusion Project Integration Gateway exports only

resources that were added or modified since the last
time you successfully exported resources.

Full Oracle Fusion Project Integration Gateway exports

all resources from the integration planning resource
breakdown structure irrespective of when they were
created or modified.

Use the full export option to recreate resources that are
mistakenly deleted in Primavera P6 Enterprise Project
Portfolio Management and must be recreated. You can
also use full export if you want to export rates for all
resources (new and existing) for a revised effective rate
date in Oracle Fusion Projects integration options.

Note
If you delete a previously exported resource in Oracle Fusion Projects, then mapping information is deleted.
The corresponding resource is not deleted in Primavera P6 Enterprise Project Portfolio Management but is then
treated as a nonintegrated resource when you subsequently import project plan information.
How Planning Resources Are Exported

As illustrated in the following diagram, planning resources are exported to Primavera P6 Enterprise Project Portfolio
Management based on the associated resource class, and in the case of labor resources, on the associated resource format:
• Resources of the Labor resource class are exported as follows based on the resource format:
◦ If the resource format contains the Named Person resource type, it is exported as labor resource.
◦ All other resource formats are exported as roles.
• Resources of the Equipment resource class are exported as nonlabor resources.
• Resources of the Material Items resource class are exported as material resources.
412
• Resources of the Financial Resource resource class are exported as expense categories.
During export, Oracle Fusion Projects transfers information for each resource as appropriate. Exported information includes:
• Resource name
• Resource ID
• Resource class and format
• Resource enabled indicator
Warning
Resource and role names are limited to 100 characters and expense category names to 36 characters in
Primavera P6 Enterprise Project Portfolio Management. Therefore, resource, role, and expense category names
are truncated if their length is over the limit.
In Primavera P6 Enterprise Project Portfolio Management, other important resource attributes are defined as described in the
following table.
Resource Attribute Description
Resource calendar Set to the default global calendar

413
Resource Attribute Description
Resource currency Set to the base currency

Resource type (if not supplied during export) Set to Labor

Projects and Tasks: How They Are Exported

to Primavera P6 Enterprise Project Portfolio
Management
You export projects to Primavera P6 Enterprise Project Portfolio Management after you have completed high-level planning
(created tasks up to the desired financial planning and reporting level) in Oracle Fusion Project Portfolio Management.
Note
Settings That Affect the Export of Projects and Tasks

You must activate integration for a project before exporting it.
Tip
Define a template called Oracle Fusion Applications Integrated Project Template in Primavera P6 Enterprise
Project Portfolio Management to create projects based on your preferences.
For subsequent exports, you can export all information for the selected linked projects or only incremental changes since the
previous export.
Use the full export option to recreate an integrated WBS that was inadvertently deleted in Primavera P6 Enterprise Project
Portfolio Management or to restore the WBS hierarchy to match the task structure in Oracle Fusion Project Portfolio
Management.
How Projects and Tasks Are Exported

In Primavera P6 Enterprise Project Portfolio Management, exported projects are added to an enterprise project structure
(EPS) node called Imported Projects. Move the exported projects to a different EPS node as required.
As illustrated in the following diagram, during initial export, project information from Oracle Fusion Project Portfolio
Management is used to create a new project in Primavera P6 Enterprise Project Portfolio Management. Alternatively, if
the project number of a project matches the project ID of an existing project in Primavera P6 Enterprise Project Portfolio
Management, then the two projects are linked.
Similarly, WBSs are created for each task in the hierarchy, up to the lowest-level task. The tasks and WBS are linked. If you
build out your WBS in Primavera P6 Enterprise Project Management by adding further WBS and activities, all information
414
is summarized up to the integrated WBS before project plan information is imported into Oracle Fusion Project Portfolio
Management.
The following table describes how changes in the task structure in Oracle Fusion Project Portfolio Management affect the
WBS of a linked project during a subsequent export.
Change Impact to Project in Primavera P6 Enterprise

Project Portfolio Management
Create task New WBS created and integrated with task.

Note
If the task number of the new task matches
the WBS ID of an existing WBS, then it is
linked to the new task.

Delete task Integrated WBS is not deleted. You must manually

delete the WBS and revise planning, if required.

Move task Indent for integrated WBS is increased or decreased

accordingly.

Update task attributes Modified task attributes, including name, description,

and task manager, are used to update WBS information.

Create subtask for integrated task New WBS created for subtask. You must move planning
information from the parent WBS to the new WBS to
continue importing it into Oracle Fusion Project Portfolio
Management.

415
Project and Task Attributes Exported to Primavera P6

Enterprise Project Portfolio Management: Explained
When you export projects, project and task attribute values are used to update project and WBS information in Primavera P6
Enterprise Project Portfolio Management.
Note
Following is a description of the project and task attributes exported from Oracle Fusion Projects.
Exported Project Attributes

The following table describes some of the important project attributes exported from Oracle Fusion Projects.
Attribute in Oracle Fusion Projects Attribute in Primavera P6 Enterprise Project

Project name Project name

Project number Project ID

Project start date Project planned start date

Project finish date Project must finish by date

Project manager User-defined field

Project status Project status

Warning
Primavera P6 Enterprise Project Portfolio Management restricts the length of project names and project IDs to100
and 20 characters respectively. Therefore, project names and numbers from Oracle Fusion Projects are truncated
if their length is over the limit.
Project status in Oracle Fusion Projects is exported as follows:
416
System Status in Oracle Fusion Projects Status in Primavera P6 Enterprise Project Portfolio
Management
Unapproved Planned

Submitted Planned

Approved Active

Pending Close Active

Closed Inactive

Exported Task Attributes

When a WBS is created based on a task exported from Oracle Fusion Projects, the attribute Integrated Type is used to
indicate that the WBS is integrated. Other WBS attributes updated using information exported from Oracle Fusion Projects
are described below.

Task name WBS name

Task number WBS ID

Task number or outline number WBS code

Note
WBS code is set to the task number or
the last segment of the outline number
depending on the value of the WBS Code
Source integration option.

417
Outline number Sequence number

Note
Integration processing transforms the outline
number into a sequence number based on
the position of a task in comparison to peer
tasks. For example, the sequence number of
task 1.0 is 10, task 2.0 is 20, and task 3.0 is
30. Similarly, the sequence number of task
1.1 is 10, task 1.2 is 20, and task 2.1 is 10.

Task description Notebook topic at WBS level

Task manager User-defined field

Chargeable option WBS status

Important
The Chargeable option only impacts WBS
that are mapped to lowest-level tasks. If the
corresponding task is not chargeable, then
the integrated WBS is marked as inactive and
is not visible on the timesheet.

Warning
Primavera P6 Enterprise Project Portfolio Management restricts the length of WBS names and WBS IDs to 100
and 20 characters respectively. Therefore, task names and numbers from Oracle Fusion Projects are truncated if
their length is over the limit.
FAQs for Define Primavera P6 Enterprise Project

Portfolio Management Integration
Can I change the organization that owns a project or task?

Yes. You can change the project or task owning organization at any time, unless unprocessed transactions exist for
the project. You can also simultaneously reprocess transactions for the affected tasks. Since the project or task owning
organization has no effective as-of date, the new organization applies for the duration of the project.
418
Implementing Project Financial Management Microsoft Project Integration: Overview
29 Microsoft Project Integration: Overview
Microsoft Project and Project Financial Management

Applications: How They Work Together
Microsoft Project integration enables project managers to create projects, complete in-depth scheduling using dependencies
and constraints, and perform what-if analysis offline, before synchronizing project plan and progress information with Project
Financial Management applications in Oracle Fusion Project Portfolio Management.
Project executives, project accountants, and billing specialists can use the information exported to Oracle Fusion Project
Portfolio Management for financial planning, project costing, billing and revenue accrual, and performance reporting.
Microsoft Project integration enables you to do the following:
• Import templates or existing projects from Oracle Fusion Project Portfolio Management to create projects in
Microsoft Project.
• Export projects from Microsoft Project to create projects in Oracle Fusion Project Portfolio Management.
• Synchronize existing projects with Oracle Fusion Project Portfolio Management.
• Import resources from the primary planning resource breakdown structure to use for creating task assignments in
Microsoft Project.
• Plan and schedule projects, assign resources, and track progress.
• Import actual quantities and costs into Microsoft Project for progress collection.
• Export project plan and progress information to Oracle Fusion Project Portfolio Management.
Importing Projects
You can import a template or an existing project from Oracle Fusion Project Portfolio Management to create a new project
file in Microsoft Project. During import, select to import all project information or only planning resources. If you want to
subsequently export new task assignments for the project to Oracle Fusion Project Portfolio Management, you must import
resources from the primary planning resource breakdown structure.
Restriction
While importing from Oracle Fusion Project Portfolio Management, you cannot select templates whose primary
planning resource breakdown structure allows changes at the project level. This restriction does not apply when
importing projects.
When importing an existing project, retain the link if you intend to synchronize the project. If you only want to view project
details, or intend to export the project to Oracle Fusion Project Portfolio Management as a different project later, then do not
retain the project link.
Restriction
You cannot retain the project link if third-party scheduling is disabled for the project.
419
Exporting Projects
You can export a project from Microsoft Project to create a new project in Oracle Fusion Project Portfolio Management.
Exporting links the projects in the two applications. Optionally, set a baseline for the project plan, and simultaneously generate
a budget version and create a baseline.
When exporting a project, you must select a source project or template unless you had originally imported a project or
template from Oracle Fusion Project Portfolio Management. The source project or template must allow for third-party
scheduling and the associated primary planning resource breakdown structure must not allow changes at the project level.
Synchronizing Project Information

Use synchronization rules to transfer information from and to Microsoft Project. Select the required synchronization rule to
synchronize all information, or import or export selected information only. For example, you can select to only synchronize
schedule updates for the project. Depending on the synchronization rule, select synchronization options to determine how
information is transferred.
The following table describes the default direction in which attributes are transferred.
Attributes Imported into Microsoft Project Exported from Microsoft

Project
Task structure Yes Yes

Resources and resource rates Yes No

Task attributes Yes Yes

Actual quantities and costs Yes No

Scheduling and progress No Yes

Importing Resources and Rates

You can import all planning resources from the primary planning resource breakdown structure associated with the project in
Oracle Fusion Project Portfolio Management or import selected resources only.
Import rates from Oracle Fusion Project Portfolio Management to calculate planned costs in Microsoft Project. The Cost
Type synchronization option determines whether raw cost rates or burdened cost rates are imported.
Before import, rates are derived for each resource based on the actual or planning rate schedules specified on the associated
project plan type. Any override rates you specify on the project plan in Oracle Fusion Project Portfolio Management are not
imported.
Importing Actual Costs and Exporting Progress

You can import actual quantity and costs either from the latest summarized data or from draft progress. The source of actual
amounts determines how progress is exported, as described in the following table.
420
Source of Actual Amounts Impact on Importing Progress
Latest summarized data Actual amounts on the draft progress are refreshed
from the latest summarized data when you export
progress. Also, you specify the progress as-of date in
the synchronization options.

Draft progress Actual amounts on the draft progress are not refreshed
and hence, they match the actual amounts previously
imported into Microsoft Project.

When you export progress from Microsoft Project, the estimate-to-complete (ETC) method and physical percent complete
calculation method are set to Manual. Values for planned, actual, and estimated finish dates and physical percent complete
are exported at each level in the task hierarchy and do not roll up in Oracle Fusion Project Portfolio Management. Values for
all other attributes are transferred at the task assignment level and roll up in Oracle Fusion Project Portfolio Management.
After export, draft progress is published. A forecast version is generated depending on progress settings defined for the
associated project plan type.
Restriction
If burdening is not enabled on the project type, then you can export progress with raw cost. If burdening is
enabled, then you must use burdened cost to export progress. That is, set the Cost Type synchronization option
to Burdened cost.
421
Implementing Project Financial Management Project Costing Configuration: Define General Costing Setup
30 Project Costing Configuration: Define General

Costing Setup
Manage Project Transaction Sources
Transaction Sources: Explained

Transaction sources identify the source of transactions that you import into Oracle Fusion Project Costing. You control the
transaction import and processing by the specifying the source, document, and document entry options.
The transaction sources can be classified into two categories:
• Predefined sources
• Third-party application sources
Predefined Sources
Oracle Fusion Project Costing provides a set of predefined transaction sources that you use to import transactions from other
Oracle Fusion applications. The predefined sources and their associated document entries are as follows:
• Oracle Fusion Payables: Supplier costs, expense reports, intercompany invoices, and interproject invoices.
• Oracle Fusion Projects: Time cards, usage expenditures, miscellaneous expenditures, inventory expenditures,
burden expenditures, summarized burden expenditures, work-in-progress expenditures, capital interest
expenditures, and allocation expenditures.
• Oracle Fusion Cost Management: Purchase receipts and miscellaneous inventory cost.
• Oracle Fusion Purchasing: Purchase requisition and purchase order commitment costs.
Third-Party Application Sources

You can define additional transaction sources to import transactions from non-Oracle applications. For example, you can
define the transaction source Payroll to identify expenditure items imported from an external payroll system. Similarly, you
create documents for a specific transaction source and document entries for a specific document.
Source, Document, and Document Entry Components: How

They Work Together
When you create a transaction source, you select the transaction source options to control the transaction import processing.
Transaction source, document, and document entry definitions determine how the application handles validation, import,
processing, adjustment, and accounting of project cost transactions.
422
The following figure provides an example of a transaction source called Oracle Fusion Payables, associated documents called
Supplier Invoice and Expense Report, and their document entries such as Invoice Price Variance, Exchange Rate Variance,
Freight, Item Cost, and Nonrecoverable Tax.
Sources
At the transaction source level, you define the source, the processing set size, preprocessing, and postprocessing
extensions. The extensions record the internal identifiers of imported expenditure items in the source application or perform
other user-defined processing before and at the end of the Import and Process Cost Transactions process. Review and
update the transaction sources to call the transaction preprocessing and postprocessing extensions during the import and
process cost transactions process.
• Processing set size: When transferring large number of transactions, you can reduce the impact of unexpected
errors by processing transactions in sets. Define the set size by providing the set size.
423
• Preprocessing extension: Used for transaction validation before importing, uploading the transactions to Transaction
Import Interface, or for other processing tasks before importing.
• Postprocessing extension: Used to record the transaction number of the imported expenditure items in the source
application.
Documents
Documents represent the transactions that are imported to Oracle Fusion Project Costing. They are associated to a source.
You specify the import and accounting options for transactions. Some of the options are interdependent.
• If the document entry is associated with the expenditure type class, Supplier Invoice or Expense Report, you cannot
deselect the Accounted in Source Application and Import raw cost amounts options.
• If the document entry is associated with the expenditure type class, Burden Transactions, you cannot deselect the
Import raw cost amounts or Import burdened amounts options.
• You can select the Import burdened amounts option only when the Import raw cost amounts option is selected.
• You can select the Create raw cost accounting journal entries option, if the Accounted in Source Application option
is set to No.
• You cannot create a document for predefined transaction sources.
Document Entries
Document entries are a further breakdown of the document. They represent different types of transactions that come under
a single, specific document. For the Burden Transactions expenditure type class, you specify the Import raw cost amounts
and Import burdened amounts options at the document level; however, you cannot specify the Allow adjustments and Allow
reversals options at the document entry level. Therefore, to allow adjustments and reversals, you either change the document
options or select a different expenditure type class. You can define the following document entry options:
• Allow interface modifications: After importing the transactions, you can edit the unprocessed transactions.
• Create related items: When importing the transactions the Create Related Items extension is used to process the
related items.
• Cross-charge transaction processing: You can allow cross-charge transactions processing.
Related Topics
• Document and Document Entry Edit Options of Predefined and Third-Party Sources: Explained
Setting Up Transaction Sources: Points to Consider

Transaction sources identify the source of external transactions and determine how you import them into Project Financial
Management.
Consider the following aspects when you set up transaction sources:
• Transaction Source Options

• Document Options
• Document Entry Options
• Predefined Transaction Sources
424
Transaction Source Options

You specify the following options when setting up transaction sources.
Option Description
Processing Set Size Number of records processed in each set. When

processing a large amount of data, reduce the impact
of unexpected errors by processing transactions in sets.
The import process saves information to the database
after each set is complete. If an error occurs and a roll
back is issued, only transactions in the current set are
affected.

Preprocessing Extension Manage Transaction Sources: Preprocessing Extension

performs custom logic at the beginning of Import
and Process Cost Transactions process. You must
implement custom validation logic before processing
costs.

Postprocessing Extension Manage Transaction Sources: Postprocessing Extension

records the internal identifiers of imported expenditure
items in the source application or performs custom
processing at the end of the Import and Process Cost
Transactions process.

Document Options
You specify the following options when setting up transaction source documents.
Option Description
Commitment Source Identifies if the document is used for importing

commitment transactions.

Commitment Type Identifies type of the commitment transaction that you

can import using the document. Possible values are:
• Purchase order
• Purchase requisition
• Supplier invoice
• Any other commitment transaction
425
Option Description
Import Raw Cost Amounts Imports transactions with the raw costs already
calculated. The amount remains the same after you
import the transaction. Designating an imported
transaction as costed doesn't affect burdening or
accounting.

Note
If Burden Transaction is the expenditure type
class for one or more document entries, you
can't disable the Import Raw Cost Amounts
option for the document. If the Commitment
Source option is activated, then the Import
Raw Cost Amounts option is available, but
not available for editing.

Import Burdened Amounts Imports burdened costs for transactions. If selected,

transactions without a burdened cost amount are
rejected. When you select this option, the Import Raw
Cost Amounts option is automatically selected.

Note
class for one or more document entries, you
can't disable the Import Burden Amounts
option for the document.

Allow Duplicate Reference Allows the document to have multiple transactions with
the same original application reference.

Note
If you select this option, you can't uniquely
identify the item by:

Note
Source

Note
Document

Note
Original application reference

You can't edit the following options for commitment document if you activate the Commitment Source option.
426
Option Description
Allow Override of Person Organization Allows the external application to provide an

expenditure organization that is different from the
owning organization of the person. If no expenditure
organization is provided, the import process considers
the owning organization of the person as the
expenditure organization.

Reconcile with Source Reconciles transactions between the document and the
source application.

Archive After Import Automatically archives successfully imported

transactions when the import process completes.

Accounted in Source Application Controls the accounts that are imported and the
fields that are required from the transaction source
application.

Create Raw Cost Accounting Journal Entries Transfers cost accounting journals for the raw cost to
the general ledger.

Note
Settings on the project type determine
whether accounting journal entries for the
burden cost and burdened cost are sent to
the general ledger.

Create Adjustment Accounting Journal Entries Transfers adjustments to the general ledger.

Document Entry Options

You specify the following option when setting up transaction source document entries.
Option Description
Expenditure Type Class Expenditure type class used for the document entry.
If the document is a commitment document, then the
expenditure type class is set to Supplier Invoice and you
can't edit the expenditure type class.

You can't edit the following options if the document is a commitment document.
427
Option Description
Allow Adjustments Allows adjustments to imported transactions in Project

Financial Management after import.

Note
If Burden Transaction is the expenditure
type class, you can't disable the Allow
Adjustments option.

Allow Reversals Allow reversals of expenditure batches or expenditure

items for the document entry.

Note
To manage reversals between the
external application and Project Financial
Management:

Note
Create reversals in the external application.

Note
Import the raw costs. This process
creates reversal entries in Project Financial
Management.

Note
class, you can't select the Allow Reversals
option.

Allow Interface Modifications Allows modifications to rejected transactions after the

import process is completed. Allows modifications
to pending transactions after they are loaded to
the interface table and before the import process is
submitted.

Create Related Items Indicates that the Related Transaction Extension is used
to create related transactions for expenditure items
charged to projects.

Process Cross-Charge Transactions If you select this option for a document entry, Project
Financial Management performs cross-charge
processing for transactions that originate from the
source, document, and document entry.

428
Predefined Transaction Sources

Project Financial Management provides a set of predefined transaction sources that you use to import transactions from other
Oracle Fusion applications. In addition, Project Financial Management uses predefined transaction sources to import the
following:
• Project allocations
• Capitalized interest transactions
• Summarized burden transactions generated internally
You can define additional transaction sources to import transactions from third-party applications. For example, you can
define the transaction source Payroll to identify expenditure items imported from an external payroll application. You control
the transaction import processing by the options that you select for each transaction source.
Predefined transaction sources exist for the following:
• Payables
• Cost management
• Projects
• Purchasing
Transaction Document Import and Accounting Options: Points

to Consider
Specify the import and accounting options in the transaction document to define the way in which the transactions are
imported and processed.
Transaction Import Options

The import options that you define for documents impact how the application imports transactions for that document. You
specify the following import options for each document:
Import Options Description
Import raw cost amounts Select this option to import raw cost amounts on
transactions from this document.

Import burdened amounts Select this option to import burdened cost amounts on
429
Import Options Description

Allow duplicate reference Select this option to allow the same original application
reference for transactions from this document.

Allow override of person organization Select this option to override the primary human
resources assignment organization of the person on

Reconcile with source Select this option to reconcile transactions associated to

this document in the source application.

Archive after import Select this option to archive transactions from this
document after importing them successfully.

Transaction Accounting Options

The accounting options that you define for documents impact how the application accounts transactions for that document.
You specify the following accounting options for each document:
Accounting Options Description
Accounted in source application Select this option to specify that cost transactions can
be accounted in the source application. That is, you can
account for raw, burden, or burdened costs externally.

Restriction
If the raw cost, burden, or burdened cost is
accounted in the source, then the respective
general ledger accounts are required to
import the transactions successfully.

Create raw cost accounting journal entries Select this option to create raw cost accounting journal
entries on transactions.

Create adjustment accounting journal entries Select this option to create adjustment accounting
journals entries on transactions.

Related Topics
• Document and Document Entry Edit Options of Predefined and Third-Party Sources: Explained
430
Document and Document Entry Edit Options of Predefined and

Third-Party Sources: Explained
You can define the transaction document and document entry options for transactions that originate from predefined sources
and third-party applications sources. However, there is a limitation in editing these options. The options that you can edit for
each source depend on whether the document entry is predefined for use with Oracle Fusion Applications or defined during
implementation for use with third-party application sources.
Document Edit Options

The following table provides a list of document options that you can edit for predefined and third-party application source
transactions.
Note
Document Options Predefined Sources Third-Party Application Sources
Archive After Import Editable Editable

Allow Duplicate Reference Not editable Not editable

Allow Override of Person Not editable Not editable

Organization

Import Raw Cost Amount Not editable Not editable

Import Burdened Amount Not editable Not editable

Accounted in Source Application Not editable Not editable

Create Raw Cost Accounting Not editable Not editable

Journal Entries

Create Adjustment Accounting Editable Editable

Journal Entries

Reconcile with Source Not editable Editable

431
Document Entry Edit Options

The following table provides a list of document entry options that you can edit for predefined and third-party application
source transactions.
Note
Expenditure Type Class Not editable Not editable

Allow Adjustments Editable Editable

Allow Reversals Not editable Editable

Allow Interface Modifications Not editable Editable

Process Cross-Charge Editable Editable

Transactions

Create Related Items Editable Editable

FAQs for Manage Project Transaction Sources

Can I assign a document to multiple sources?
You can have a document with the same name in multiple sources but you cannot share documents across sources. For
example, a corporation with multiple time capture systems can associate a time card document with Oracle Fusion Projects
and a non-Oracle application as sources. The rules on how these transactions are treated may differ depending on how they
are processed in the source applications.
Can I create documents and document entries for predefined transactions sources?
No. You can create documents and document entries only for third-party transaction sources.
Can I delete transaction sources, documents, and document entries?

You can delete third-party transaction sources, documents, or document entries only if no cost transactions exist. However,
you can't delete the predefined transaction sources, documents, or document entries.
Can I allow adjustments and reversals for all transactions in thedocument entry?
No. You decide whether to allow transaction adjustments and reversals for each document entry that you create during
implementation. However, you can't define document entries to allow adjustments and reversals for transactions that are
432
generated by the application such as allocation transactions, capital interest expenditure transactions, summarized burden
transactions.
Can I change the source and document for transactions after exporting them to Oracle
Fusion Projects?
No. You can't change the source, document, and document entry after creating a transaction.
433
Implementing Project Financial Management Project Costing Configuration: Define Capital Projects
31 Project Costing Configuration: Define Capital

Projects
Asset Cost Allocation Methods: Explained

The asset cost allocation method determines how indirect or common costs incurred on a project are allocated to multiple
assets.
You can specify an asset cost allocation method to enable Oracle Fusion Projects to automatically allocate unassigned asset
lines and common costs across multiple assets. Unassigned asset lines typically occur when more than one asset is assigned
to an asset grouping level.
Project templates and projects inherit a default asset cost allocation method from the associated project type. You can
override the default at the project level. If you use capital events to allocate costs, then you can also override the asset cost
allocation method at the event level.
Asset Cost Allocation Methods

The following table describes the available asset cost allocation methods.
Method Basis of Cost Allocation
Actual Units Number of units defined for each asset

Client Extension Rules defined specifically for your organization

Current Cost Construction-in-process (CIP) cost of each asset

Estimated Cost Estimated cost of each asset

Standard Unit Cost Combination of the standard unit cost and the number
of units defined for each asset

Spread Evenly Equal allocation of cost to each asset

434
FAQs for Define Capital Projects
What's a standard unit cost method?

Standard unit cost method is one of the asset cost allocation methods that is used to allocate common and indirect costs to
different assets. For example, you can allocate amounts such as salaries, administrative overhead, and equipment charges
across several assets.
A standard unit cost is defined for an asset book and asset category combination. When you use this method, Oracle Fusion
Projects multiplies the standard unit cost times the actual units based on the asset book and asset category of each asset
and it determines the proration basis for allocating costs. Optionally, you can override the asset cost allocation method when
defining capital events.
Can I distinguish cost of removal and proceeds of sale

amounts when processing retirement costs?
Yes. When capturing retirement costs in a capital project, enter proceeds of sale amounts using expenditure types specifically
created for that purpose. Oracle Fusion Projects automatically classifies amounts for all other expenditure types associated
with the retirement cost task as cost of removal.
Define Capitalized Interest
Capitalized Interest Setup: Explained

To set up capitalized interest, you must specify the following capitalized interest options to calculate and capitalize interest on
construction-in-progress costs.
• Capitalized Interest Rate: Define thresholds when projects or tasks become eligible for interest calculation and
selecting the basis attributes used to calculate interest amounts.
• Capitalized Interest Rate Schedules: Create capitalized interest rate schedules with multipliers for organization and
interest rate combinations to calculate capitalized interest.
• Capitalized Interest Rate Schedules for Project Types: Review and update project types to specify the default rate
schedule for a capital project type. The rate schedule that you specify for a project type is the default rate schedule
for all projects that you create for this project type. You can specify to override the default rate schedule at the
project level.
• Capitalized Interest Generation on Project Status Controls: Use project status controls to determine the capitalized
interest calculation through the various stages of a project. You must determine the project statuses for which you
want to allow the calculation of capitalized interest and update project status controls accordingly. You can review
the statuses at a later stage and modify them as required.
• Capitalized Interest Extensions: Implement client extensions to customize and control how interest is capitalized and
recorded on capital projects.
435
Related Topics
• Capitalized Interest Rate Attributes: How They Work Together
Capitalized Interest Rate Schedule Components: How They

Work Together
Capitalized interest rate schedules help you maintain the interest rates at the organization level. If the capitalized interest rate
is not defined for the organization, the application automatically uses the next higher-level organization in the organization
hierarchy.
Capitalized Interest Rate Schedule Components

The following components work together to define a schedule for capitalized interest rates. Provide the rate schedule
attributes and then build new multipliers for the version to take effect. You can assign the interest rate schedule to a project
type and allow the override of the assigned capitalized interest rate schedule at the project level.
Rate Schedule Components Description
Default Organization Hierarchy Organization hierarchy to assign rates to organizations.

If there is no rate for an organization, the capitalized
interest calculation uses the rate for the next higher-level
organization in the organization hierarchy.

Hierarchy Version The default version of the organization hierarchy to be

applied to the schedule.

Hierarchy Start Organization Start organization to indicate which branch of the

organization hierarchy is used as the top of the hierarchy
for assigning capitalized interest rates to organizations.

Hold from Build Select this option to prevent the rate schedule version
from being built, if version is not yet ready for the build.

Rate Multipliers Specify rate multiplier for an organization and capitalized

interest rate combination. Optionally, copy multipliers
from other schedule version to this version and use it.

Note
To delete an interest rate schedule, you must build the schedule and then delete it.
Related Topics
• Capitalized Interest Rate Attributes: How They Work Together
436
Setting Up Capital Projects for Calculating Capitalized

Interest: Points to Consider
To correctly calculate capitalized interest, ensure that correct capitalization options are defined at the project type, project
template, and project levels. At the project level, verify the following:
• The project allows capitalized interest calculation
• The appropriate capital interest rate schedule and capitalized interest stop date are specified
Allowing Capitalized Interest for a Project

Indicate whether the project is eligible for capitalized interest. By default, this option is enabled for all capital projects.
However, you can update the option as required.
Selecting a Capital Interest Schedule and Capital Interest Stop Date

Capitalized interest rate schedules to define rates of interest calculation for each organization. The default interest schedule is
inherited from the project type. You can override it if the project type allows schedule changes at the project level.
Related Topics
• Asset Cost Allocation Methods: Explained
FAQs for Define Capitalized Interest

What's a capital interest stop date?
Date that determines the accounting period up to which capital interest is calculated for a project or task.
For example, assume the stop date for your project is December 27, 2010 and your accounting periods are weekly. That is,
the stop date falls in the fourth period of December. In such a case, capital interest is calculated only up to the third period in
December 2010.
437
Implementing Project Financial Management Project Costing Configuration: Define Borrowed and Lent
Accounting
32 Project Costing Configuration: Define Borrowed

and Lent Accounting
Define Borrowed and Lent Business Unit Options
Project Business Unit Cross-Charge Options: Critical Choices

Oracle Fusion Projects provides two methods to process cross-charge transactions.
• Borrowed and Lent Accounting: Creates accounting entries that move an amount equal to the transfer price
between the provider and receiver organizations within a legal entity. There is no formal internal invoice created with
this method. Costs or revenue are shared based on transfer price rules.
Use the Borrowed and Lent processing method to apply cross-charge transactions within a business unit or
between business units.
• Intercompany Billing: Enables the provider organization to present a formal invoice based on the transfer price to the
receiver organization and receive payment for services rendered and materials supplied. You can use this processing
method between legal entities.
You must set up the contract business unit to use the Intercompany Billing processing method.
This section describes the project business unit options for setting up cross-charge transactions for sharing costs and
revenue within and between business units in the same legal entity.
Transfer Price Currency Conversion

Select the date type, either transaction date or project accounting date, and rate type that the system uses by default to
determine the conversion rate to convert the transfer price amount from the transaction currency to the ledger currency.
You can override the default values by using the Transfer Price Currency Conversion Override extension.
Cross-Charge Transactions Within a Legal Entity

The method of creating cross-charge transactions can be different for transactions within a business unit than the method
used across business units. You can choose either the Borrowed and Lent Processing method of creating cross-charge
transactions, or specify that no cross-charge transactions will be created.
The processing method that you specify for cross-charge transactions between business units is the default method used
between the provider business unit and any other receiver business unit. You can override the default processing method for
specific receiver business units.
Note
If you delete the override of the default processing method for a specific receiver business unit, you must manually
adjust transactions to reflect the deleted controls.
438
Accounting
Prerequisites for Setting Up Business Unit Options for Cross-

Charge Transactions: Explained
Before you can set up the cross-charge options during business unit implementation to enable cross-charge transactions
within a business unit and between business units, you must complete prerequisite setup steps.
Prerequisites for Creating Cross-Charge Transactions

You must define the following objects before you can create cross-charge transactions.
• Legal entities, including setting up accounting and associating the balancing segment values to the legal entity.
• Business units with the project accounting business function.
• Organizations and organization hierarchies that will share resources.
Note
The application uses the project expenditure organization hierarchy, and the project and task owning
organization hierarchy, to determine the transfer price defined for the provider organization and receiver
organization combination.
Prerequisites for Borrowed and Lent Processing Method

You can implement the Borrowed and Lent processing method of creating cross-charge transactions after defining the
following objects.
• Transfer price rule and schedule
• Either a rate schedule or burden schedule, based on the transfer price rule
Prerequisites for Intercompany Billing Processing Method

For the Intercompany Billing processing method of creating cross-charge transactions, set up at least one of the following
schedules.
• Rate schedule
• Burden schedule
• Transfer price rule and schedule
FAQs for Define Borrowed and Lent Business Unit Options

What's the difference between intercompany billing and interproject billing?
Intercompany billing creates internal invoices and accounting entries to pass costs and share revenue across organizations
on an intercompany billing contract. A provider organization performs work and charges it a project owned by the receiver
439
Accounting
organization. The provider organization creates an invoice in Oracle Fusion Receivables and the receiver organization imports
the invoice from Oracle Fusion Payables. Accounting entries for revenue are created between the organizations.
Interproject billing creates internal invoices for costs incurred between a provider project and a receiver project defined on an
interproject billing contract. The provider project generates an Oracle Fusion Receivables invoice, which the receiver project
receives as an Oracle Payables invoice.
440
Implementing Project Financial Management Project Costing Configuration: Define Project Costing
Integrations
33 Project Costing Configuration: Define Project

Costing Integrations
Oracle Fusion Project Costing Integration with Oracle

Fusion Applications: How They Work Together
Oracle Fusion Project Costing fully integrates with Oracle Fusion Purchasing, Oracle Fusion Self Service Procurement, Oracle
Fusion Receipt Accounting, Oracle Fusion Expenses, Oracle Fusion Payables, Oracle Fusion Inventory Management, and
Oracle Fusion Cost Management and enables you to capture and transfer project-related transactions. For example when
you purchase goods, the project information is carried from the requisition to purchase orders to supplier invoices to finally
project expenditure items.
Oracle Fusion Project Costing also integrates with Oracle Fusion Assets to capture capital assets and retirement adjustment
costs. Oracle Fusion Project Costing fully integrates with Oracle Fusion Subledger Accounting so that you can create
accounting for your project-related transactions.
Implementing Oracle Fusion Payables

Implement Oracle Fusion Payables to enter project-related supplier invoices in Oracle Fusion Payables and to import project-
related expense reports from Oracle Fusion Expenses. You use supplier and invoice information in Oracle Fusion Payables to
create expenditure items for projects in Oracle Fusion Projects.
When the primary accounting method is accrual basis accounting, you transfer invoice distributions and payment discounts
as actual costs. When invoices are matched to receipt accrual purchase orders, Oracle Fusion Supply Chain Management
transfers invoice variances to Oracle Fusion Project Portfolio Management. For receipt accruals, Oracle Fusion Payables
transfers discounts to Oracle Fusion Project Portfolio Management.
Implementing Oracle Fusion Purchasing, Oracle Fusion Self Service

Purchasing, Oracle Fusion Receipt Accounting, and Oracle Fusion
Cost Management
Implement Oracle Fusion Purchasing and Oracle Fusion Self Service Purchasing to enter project-related requisitions, requests
for quotations, and purchase orders, and then report them as outstanding committed costs of requisitions and purchase
orders on your projects.
Implement Oracle Fusion Receipt Accounting to create receipts against purchase orders. Thereafter, Oracle Fusion Cost
Management transfers project-related receipt accruals as actual supplier costs. When the primary accounting method is
accrual basis accounting, you transfer the costs associated with the receipt as actual costs. Oracle Fusion Cost Management
transfers the variances for receipt accruals by accumulating the costs from Oracle Fusion Payables and then transfers them
to Oracle Fusion Project Portfolio Management.
Implementing Oracle Fusion Inventory Management

Implement Oracle Fusion Inventory Management to order and receive items into inventory before assigning them to a project.
You can capture project information for miscellaneous transactions and movement requests as you take items out of or
receive items into Oracle Fusion Inventory Management. When you enter project-related transactions in Oracle Fusion
Inventory Management, you enter the project information on the source transaction. Oracle Fusion Cost Management
transfers project-related miscellaneous inventory issues and move orders to Oracle Fusion Project Portfolio Management.
441
Integrations
Implementing Oracle Fusion Expenses

Employees and contingent workers can enter and submit expense reports.
Note
Oracle Fusion Expenses directly reimburses employees and contingent workers in the same manner. Oracle
Fusion Expenses doesn't reimburse the supplier associated with the contingent worker. To reimburse the supplier
directly, the contingent worker must not submit expenses through Oracle Fusion Expenses. Instead, the supplier
must submit an invoice for expenses to Oracle Fusion Payables.
Oracle Fusion Expenses integrates with Oracle Fusion Payables to provide quick processing of expense reports for payment.
You can create project-related expense reports in Oracle Fusion Expenses and transfer to Oracle Fusion Payables and then
to Oracle Fusion Project Costing.
Implementing Oracle Fusion Assets

Implement integration with Oracle Fusion Assets to collect construction-in-progress and expense costs in Oracle Fusion
Project Costing for each asset you're building. You can then update your fixed asset records when assets are ready to be
placed in service or retired. In addition, you can perform retirement cost processing to capture retirement-work-in progress
costs associated with the retirement of assets in Oracle Fusion Assets.
Implementing Oracle Fusion Subledger Accounting

Oracle Fusion Subledger Accounting is the single source of all internally derived accounting. Oracle Fusion Project Costing
seamlessly integrates with Oracle Fusion Subledger Accounting for accounting costs. After the accounting events are
generated in Oracle Fusion Project Portfolio Management, the subledger accounting entries are created and then transferred
to the Oracle Fusion General Ledger.
For transactions imported from other Oracle Fusion applications, such as Oracle Fusion Payables, Oracle Fusion Receipt
Accounting, and Oracle Fusion Cost Management, you can view accounting entries created in Oracle Fusion Subledger
Accounting without navigating to the source application. For transactions imported from non-Oracle applications, you can
view the accounts imported into Oracle Fusion Project Costing without navigating to the third-party application.
Capturing Project Costs: Explained

Capture project-related costs from both Oracle Fusion Applications and third-party applications and then transfer them to
Oracle Fusion Project Costing. You can capture costs manually by creating uncosted, costed, and accounted transactions for
third-party application sources in Oracle Fusion Project Costing.
Transaction Sources
Costs are created in internal and external applications before being processed. The following table lists cost types and the
corresponding source applications.
442
Integrations
Source Name Type of Transactions
Oracle Fusion Expenses Expense Reports

Note
Expense report transactions are imported
from Oracle Fusion Payables as actual costs
to Oracle Fusion Project Costing.

Oracle Fusion Payables Supplier Invoices

Oracle Fusion Purchasing • Purchase Orders

• Purchase Requisitions
Note
Purchase orders and purchase requisitions
are available as committed costs for reporting
in Oracle Fusion Project Costing.

Oracle Fusion Receiving Receipts

Oracle Fusion Inventory • Miscellaneous Transactions

• Movement Requests
Oracle Fusion Cost Management • Expense-Based Receipts

• Inventory Miscellaneous Transactions
• Inventory Movement Requests
Oracle Fusion Project Costing • Costs in Unreleased Expenditure Batches

• Adjustment Transactions
• Unprocessed Transactions
Third-Party Applications External Costs imported using desktop Excel integration,

Web services, or Oracle Cloud interface.

443
Integrations
Capture of Costs
Capture various types of costs from internal and external applications, and then transfer them to Oracle Fusion Project
Costing.
The following table shows various sources of transactions and how they are exported to Oracle Fusion Project Costing.
444
Integrations
Source of Transaction Description
Capture Costs from other Oracle Fusion applications Enter and process project-related transactions and
then submit the Import and Process Cost Transactions
process. For example, you enter invoices with project-
related distributions in Oracle Fusion Payables, validate,
account, and then import them to Oracle Fusion Project
Costing.

Capture Costs from Third-Party Applications Import costs using one of the following:

• Desktop Excel integration
• Web services
• Load data to the interface table in Oracle Cloud
Note
You can load data to interface tables
using predefined templates and the Load
Interface File for Import scheduled process,
which are both part of the External Data
Integration Services for Oracle Cloud
feature. For more information, see the
Documentation tab for the Load Interface
File for Import process in Oracle Enterprise
Repository for Oracle Fusion Applications.
Create individual third-party transactions in the You can create individual transactions with third-
application party application source directly from the Manage
Unprocessed Transactions page in Oracle Fusion
Project Costing.

For example, this approach works well if you are near
a period close and have to create a few individual
third-party transactions rather than waiting for the
transactions to come from the third-party application.

Capture of Additional Transaction Attributes

Use the Cost Collection flexfield to capture product-specific attributes on actual cost transactions and cost commitment
transactions. You can manage naming, validation, and ordering of these attributes within each of the documents that capture
them such as expense reports, purchase orders. You can capture, store, display, search, and report project-related attributes
in the transaction source applications.
Related Topics
• Project Cost Transactions: How They Are Imported to Oracle Fusion Project Costing
• Desktop Excel Integration Spreadsheets to Enter Project Cost Transactions: Explained
445
Integrations
Deriving Project-Related Accounts for Oracle Fusion

Applications: Explained
Account rules specify how the Account Combination is derived on subledger journal entry lines. You can specify the
conditions under which a rule becomes applicable. Using this feature, you can develop complex rules for deriving accounts
under different circumstances. Accounts imported from third-party applications or the Oracle Application Development
Framework Fusion Desktop Integration are available as sources in Oracle Fusion Subledger Accounting.
You can optionally create account rules with your specifications. If you define an account rule for an account combination,
then the rule determines each segment of the Accounting flexfield. If you define an account rule for a segment, then the
rule determines the value for a single Accounting flexfield segment. You can use both segment and account combination
rules to derive a single account. If you assign both types of account rules to a single journal line definition, then Oracle
Fusion Subledger Accounting uses the account segment rules first and then takes the remaining values from the account
combination rule.
Deriving Projects-Related Accounts

The only method to derive project-specific accounts is to use project sources in the accounting method. You define account
rules to derive project-related accounts for the following Oracle Fusion applications:
• Oracle Fusion Purchasing: Project-specific accounts, such as the purchasing charge account and accrual account,
are derived by using transaction account derivation rules
• Oracle Fusion Cost Management: All project-specific accounts are derived during accounting creation in Oracle
Fusion Subledger Accounting.
• Oracle Fusion Payables: The project-specific accounts are not derived until the journal entries are created within
Oracle Fusion Subledger Accounting. Oracle Fusion Expenses need not derive project-specific accounts because
they are derived after the records are transferred to Oracle Fusion Payables.
• Oracle Fusion Receivables: AutoAccounting does not generate accounts for invoices originating from Oracle Fusion
Projects. Project-specific accounts are derived during accounting creation in Oracle Fusion Subledger Accounting.
You must update the account rules to derive project-specific accounting. Create project-specific rules by evaluating the
Project Identifier. Derive a project-specific account combination or override a single account segment with a project-specific
value. Use more than 100 project-specific sources to create mapping sets and account rule conditions. Examples of these
sources include:
• Billable Indicator
• Capitalizable Indicator
• Retirement Indicator
• Project Type
• Expenditure Type
• Expenditure Type Descriptive Flexfield Attribute 1
• Task Descriptive Flexfield Attribute 1
446
Integrations
Related Topics
• Account Rules: Explained
FAQs for Define Purchasing Integration
Where do I provide project information for project-related

requisitions and supplier invoices?
You enter project information at the distribution line level for project-related requisitions and purchase orders in Oracle Fusion
Purchasing, and for project-related supplier invoices in Oracle Fusion Payables. For requisitions, the requisition distribution
attributes default from what is specified during the implementation. For purchase orders, the purchase order attributes default
from the purchase order line and the purchase order line attributes default from the purchase order header. The distribution
level values are used for validation and import.
FAQs for Define Payables Integration
How can I validate distribution sets for projects information?

Oracle Fusion Projects performs validations on Oracle Fusion Payables distribution sets for payables invoices at the time you
create the actual distribution set lines. It validates the project and task number during the invoice validation.
Distribution sets are typically used on recurring transactions, and the associated project does not have transaction controls.
When you create a distribution set in Oracle Fusion Payables, the distribution set line is not validated against the project
transaction controls in Oracle Fusion Projects because you do not enter an expenditure item date, which is required for
transaction control validation. The expenditure item date is not provided because you use the distribution sets for an indefinite
period of time.
FAQs for Define Inventory Integration
How can I define bill rates for inventory items?

You can enter cost markups in the nonlabor rate schedule instead of rates for expenditure types that are related to inventory
items.
Alternatively, if you enter a bill rate for an expenditure type that relates to inventory items, then the base unit of measure for
inventory transactions reported under the expenditure type must be the same as the unit of measure for the expenditure type.
If the base unit of measure for an inventory transaction differs from the unit of measure for the expenditure type, the Generate
Revenue process reports an error and doesn't process the transaction.
447
Implementing Project Financial Management Project Billing Configuration: Define Contracts Configuration
for Project Billing
34 Project Billing Configuration: Define Contracts

Configuration for Project Billing
Define Document Sequences
Document Sequences: Explained

In Oracle Fusion Applications, each business document or business event is uniquely identified by a document sequence
number that you assign to it. However, the document sequencing feature must be turned on (enabled) on the business
document or event to allow the assignment. For example, if document sequencing is enabled, you can assign a document
sequence number to an invoice that gets generated in response to a purchase order. You can use document sequences as
a proof to track successfully executed transactions as well as failed transactions. Additionally, a document sequence helps in
generating an audit trail, which can be used to identify how a particular transaction passed through various applications.
Document sequencing can be managed automatically, manually, and gaplessly.
Note
Plan your document sequencing carefully before you use the options available in the application to apply
sequence numbers. Avoid changes to the options 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 as it is generated, and this unique number is
stored in the database. The numbering is sequential by date and time of creation. If you define a sequence to automatically
number documents, you can provide an initial value to begin the sequence. In absence of a custom value, the default value 1
is used.
Manual Sequencing
Manual sequencing requires you to assign a unique number to each document before it is generated. In manual sequencing,
the numerical ordering and completeness of a transaction is not enforced. Users can skip or omit numbers when entering the
sequence value. However, each time that a number is assigned, 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. As a result, the sequence is maintained for all the documents that are
generated, and no sequence numbers are lost due to incomplete or failed document generation.
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 maintain the chronological order in which the documents are created and assigned sequence numbers. The sequence
numbers and the transaction dates are chronologically correlated to prevent any mismatch of a new document sequence
being assigned to an older document or vice-versa.
448
for Project Billing
Important
Use this type of sequencing only if necessary because it may affect the performance of the system and slow
down transaction processing.
Related Topics
• Viewing and Editing Profile Option Values: Points to Consider
Document Sequence Categories: Explained

A document sequence category is a set of documents that share similar characteristics and that are formed into a logical
group. Document sequence categories simplify the task of assigning number sequences to specific documents. Instead of
assigning a number to each document, you assign a document sequence to one or more document sequence categories.
The document sequence category automatically takes care of numbering the documents.
A document sequence category identifies the database table that stores documents resulting from transactions that your
users enter. When you assign a sequence to a category, the sequence numbers the documents that are stored in a particular
table. You must create document sequence categories to be able to manage the task of assigning document sequences.
Restriction
Once a document sequence category is created, you cannot 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 is available for use under the Document Sequences: Assignments
section on the Manage Document Sequences page. The Category field contains the name of the document sequence
category. After you create a document sequence, you can assign it to a document sequence category.
Document Sequences: Points to Consider

Sequencing documents is an important business and legal requirement. Certain aspects of the defining process are
permanent and cannot be modified later. Therefore, it is important that you first decide the appropriate document sequence
to use for a set of documents. You must also decide beforehand the type of document sequencing, because you are not
allowed to switch to other types once a sequence is assigned to a document sequence category. Make a note of the details
such as the document sequence and document sequence category so that you can refer to them at a later point in time. Also
note if there are any restrictions or configuration prerequisites before you define document sequencing.
Note
Products that implement document sequencing have specifications about its usage. Refer to the corresponding
product documentation for specific details and also to determine if there are any restrictions or configuration
prerequisites.
Creating and Editing Document Sequences

You can create document sequences that are automatic, manual, or gapless, depending on the business or legal
requirement. By default, the current date is considered as the start date. If the end date is left blank, it means that the
449
for Project Billing
sequence definition never expires. Among the several options used in creating and editing document sequences, the
following options are functionally more important and therefore need to be carefully determined:
• Determinant Type: Select to limit the document sequencing activity to certain documents that belong to a specific
business entity, such as Ledger, Tax Registration, and so on.
• Initial Value: Enter a value for the first document in your sequence. This field applies only to sequences with
automatic or gapless numbering types. Sequence numbers should not be greater than eight digits. If you leave this
field blank, the first document is automatically assigned a value of 1. Once a document sequence is defined, you
cannot change this initial value.
Creating and Editing Document Sequence Categories

Document sequence categories are defined to make it easy to assign document sequence definitions to a group of
documents instead of to individual documents. Each document sequence category is mapped to a specific table, where
the documents belonging to that category are stored. The table must already be enabled for document sequencing. When
specifying the table, you must consider the following points:
• When the sequential numbering feature checks for completeness or generates a report, it locates the category's
documents in the table.
• You can select only tables belonging to the application associated with the category.
• Once a category is defined, you cannot change the choice of table.
Assigning Document Sequences

Identify the documents to be numbered before assigning them a document sequence. For each document sequence,
there can be only one active assignment to a document sequence category, a method code, and a determinant value
(if applicable). As part of the assignment, specify whether the document is created automatically (for example, due to
a batch process, or manually through a form). If you do not specify an end date, the assignment continues to remain
active throughout the process cycle. If a determinant type was specified for the document sequence, then enter a specific
determinant value related to the selected determinant type.
At runtime, when users create documents, the document sequence to be assigned is determined by finding the active
assignment that matches the correct combination of category, numbering method, and the date range containing the
transaction date.
Auditing Document Sequences

You can audit document sequences, if required, to provide an audit trail of the document sequences used in a specific
product. However, before enabling the audit functionality for a document sequence, you must have created an audit table for
the specific document sequence, using appropriate details. Enabling the audit functionality is permitted only for newly created
document sequences. You cannot audit document sequences that are already in use by a specific product.
For more information about defining a document sequence audit table, see the Oracle Fusion Applications Developer's Guide.
Related Topics
• Managing Modules in Application Taxonomy: Points to Consider
450
for Project Billing
Define Project Contract Business Unit Options
Contract Components for Internal Billing: How They Work

Together
To use intercompany billing or interproject billing , your implementation team must configure a number of distinct features
within Oracle Fusion Enterprise Contracts. These features work in cohesion with financial and project features to create
internal invoices and transfer revenue between organizations.
Contract Type for Intercompany Billing

Select the intercompany billing option on a contract type to identify a contract as enabled for intercompany billing. This
option permits editing of the internal billing options of contracts of that contract type. These internal billing options include the
attributes required to create the intercompany payables invoice such as expenditure type, expenditure organization, receiver
project, receiver task, and the provider business unit.
Contract Type for Interproject Billing

Select the interproject billing option on a contract type to identify a contract as enabled for interproject billing. This option
permits editing of the internal billing options of contracts of that contract type. These internal billing options include the
attributes required to create the interproject payables invoice such as expenditure type, expenditure organization, receiver
project, and the receiver task.
Contract Business Unit Internal Billing Options

Review and update the customer contract management business function options to control the processing of interproject
billing. This table lists the internal billing options that must be defined for the contract business unit.
Feature Name Description
Invoice Numbering Method • If you want to enter invoice numbers manually,

select the manual option and either the
alphanumeric or numeric invoice number type.
• If you want the application to create invoice

numbers automatically, select the automatic
option, and enter a starting invoice number.
Invoice Batch Source Specify the invoice batch source for the interproject
contract invoices that are transferred to Oracle Fusion
Receivables.

Contract Line and Receiver Project

After you create an internal contract, link a contract line to the receiver project and task. This allows for the cross-charge
transactions that are charged to the project and task to be billed from the provider business unit to the receiver business unit.
451
for Project Billing
By default, the receiver project is also the associated project for the contract line, and you cannot add another associated
project or change the associated project for that contract line. However, the associated task and receiver task can be
different, so you can select another associated task for the project if necessary.
The receiver project must have the same legal entity as the internal customer.
Note
Only one receiver project can be linked to a contract line. The intercompany invoice generation process
automatically groups invoice lines by the contract lines. Interproject invoices have a fixed format.
Related Topics
• Creating a Contract for Intercompany Billing: Example
Project Components for Internal Billing: How They Work

Together
To use the intercompany billing or interproject billing functionality, your implementation team must configure a number of
distinct features within Oracle Fusion Projects. These features work in cohesion with contract and financial features to create
internal invoices and revenue transfers between organizations.
Invoice Formats
Define internal invoice formats for invoices generated by intercompany or interproject billing contracts. The invoice formats
control the grouping of transactions on invoice lines for intercompany contracts. Specify the grouping options to summarize
expenditure items and events, and the fields that should be displayed on the invoice line. Create different invoice formats for
intercompany labor, nonlabor, and event billing.
If you want the invoice format to be used for both customer and internal invoices, enable the invoice format for customer
invoices and internal invoices.
Restriction
All internal invoices must have a fixed format. Enable the fixed format feature to prevent the rearranging or
regrouping invoice line details on intercompany invoices.
Invoice Methods and Revenue Methods

Define invoice methods and revenue methods to determine the calculation method of invoice and revenue amounts for
intercompany contracts during invoice generation and revenue recognition. Enable the invoice methods and revenue methods
for intercompany billing.
Select from the following labor and nonlabor schedule types that are available for rate-based intercompany invoice generation
and revenue recognition:
• Bill rate
• Burden rate
• Transfer price
• Cost reimbursable
452
for Project Billing
Billing Resource Breakdown Structure

Enter resource formats and resource types for the intercompany billing resource structure that is shared by business units.
This billing resource breakdown structure defines the types of resources that can be referenced on billing controls for
Receiver Project
Create a receiver project in the receiver business unit.The receiver project can be a project that is linked to both and external
contract (for external billing) and intercompany contract (for creating internal cross-charge transactions). The receiver business
unit receives the supplier invoices.
Each receiver project can receive invoices from multiple internal contracts or from multiple contract lines of the same contract.
Enable the tasks on the receiver project that can be used for interproject billing and to allow cross-charge transactions.
Provider Project
Create a provider project to use during interproject billing. Each receiver project can have one or more provider projects. The
provider project can be in the same business unit or a different business unit as the receiver project.
Expenditures are charged to the provider project during interproject billing scenarios.
Related Topics
• Invoice Formats: Explained
FAQs for Define Project Contract Business Unit Options

Can I create a contract for intercompany billing with transfer price rules?
Yes, but only if you must derive rates for an intercompany contract based on an organization hierarchy structure instead of
the bill rates defined on a bill plan.
The contract line and bill plan architecture allows you to can specify a different bill plan for each provider and receiver
organization. Select a bill rate or burden rate schedule for each of your contract bill plans. However, if your rates are defined
at a very granular level, you may need to derive rates for an organization hierarchy structure using transfer price rules.
Why can't I see the internal billing details on a contract?

If you do not see the internal billing features on a contract, check the attributes on the contract type. The internal billing
options of a contract are only visible if the contract type is designated as either intercompany or interproject.
453
Implementing Project Financial Management Project Billing Configuration: Define Project Invoicing Options
35 Project Billing Configuration: Define Project

Invoicing Options
Invoice and Revenue Method Components: How They
Work Together
Invoice methods and revenue methods control the way you create invoices and recognize revenue for contracts. During
implementation you create the methods and assign them to bill plans and revenue plans. Any contract or contract line that
uses the bill or revenue plan calculates the invoice or revenue amount according to the instructions in the invoice or revenue
method.
Method Classification
Invoice method classifications and revenue method classifications are predefined by Oracle Fusion Projects. Select an invoice
or revenue method classification to set the approach for calculating invoice or revenue amounts.
This table lists the invoice method classifications and their descriptions.
Invoice Method Classification Description
Amount Based Generate invoices and revenue as billing events are

completed.

Percent Complete Generate invoices as progress is estimated.

• When you select the percent complete invoice
method classification, the percent complete billing
extension is automatically added to the invoice
method.
• The percent complete billing extension

automatically creates a billing event with the
percent complete invoice amount for an contract
line.
Percent Spent Generate invoices as progress is calculated, based on

actual cost to date over budget cost.
• When you select the percent spent invoice method

classification, the percent spent billing extension is
automatically assigned to the invoice method.
• The percent spent billing extension automatically

creates a billing event with the percent spent
amount for an invoice line.
454
Rate Based Generate invoices as costs are incurred, using an

invoice-specific set of bill rates, a burden schedule, or
transfer price rates.

Note
The cost reimbursable classification method
bills on cost directly, without applying any
rate or markups

This table lists the revenue method classifications and their descriptions.
Revenue Method Classification Description
Amount Based Recognize revenue as billing events are completed.

As Billed Recognize revenue as customers are invoiced, using a

common set of bill rates, a burden schedule, or transfer
pricing for both invoicing and revenue.

As Incurred Recognize revenue as costs are incurred, using a

revenue specific set of bill rates, a burden schedule, or
transfer pricing for both invoicing and revenue.

Percent Complete Recognize revenue as progress is estimated.

• When you select the percent complete revenue
extension is automatically added to the revenue
method.

percent complete revenue amount for a contract
line.
455
Percent Spent Recognize revenue as progress is calculated, based on

• When you select the percent spent revenue

method classification, the percent spent billing
extension is automatically assigned to the revenue
method.

revenue amount for a contract line.
Rate Based Recognize revenue as costs are incurred, using a

revenue-specific set of bill rates, a burden schedule, or

Tip
Use this revenue classification method if
you are using a fixed price for invoices, or if
you require different burden schedules for
invoices and revenue.

Intercompany Billing Option

If the invoice or revenue method will be used for intercompany contracts, enable the intercompany billing option to calculate
the intercompany invoice or revenue amounts. Intercompany invoices and revenue use a rate-based classification method.
Select a labor and nonlabor schedule for use when generating invoices or calculating revenue.
Important
An intercompany contract can use an invoice or revenue method that is not enabled for intercompany billing, or
an invoice or revenue method that is enabled for intercompany billing. Enable the intercompany billing option if the
invoice or revenue method will be used for intercompany contracts only.
Intercompany invoices can use any type of invoice method classification.
Rate Definition
Select schedules for labor and nonlabor if your invoice or revenue method uses a rate-based classification method.
Tip
The schedule types for labor are Person and Job.
Billing Extension Assignment

Optionally, assign custom billing extensions to automatically calculate the invoice or revenue amounts for contract lines that
use the bill plans and revenue plans associated with the invoice or revenue method.
456
If the invoice or revenue method is percent complete or percent spent, the extension creates the billing event based on the
calculation level for the billing extension specified in the bill plan or revenue plan. If the calculation level is contract line, the
event is created for the contract and contract line. If the calculation level is associated project, the event is created for the
contract line and its associated project and task.
Note
If the invoice or revenue method classification is percent complete or percent spent, the percent complete or
percent spent billing extension is automatically added to the invoice or revenue method. You cannot change the
status of the billing extension assignment to inactive, it must be active for a percent complete or percent spent
billing extension.
Project and Contract Invoice Components: How They

Work Together
Project and contract components work together to create invoice distributions. The contract contains the instructions for
calculating invoice amounts, and the project owns the cost transaction details. When you generate an invoice, invoice
distributions are created for the contract.
Expenditure items and events are the transactions for projects and contracts. Invoice method classifications determine how
transactions are invoiced.
The invoice method determines how invoice amounts are derived and which billing extensions, if applicable, calculate invoice
amounts. Enter an invoice method on a bill plan, which you create for a contract and assign to contract lines to provide a set
of instructions for creating an invoice.
Create billing controls for a contract or contract line to define the valid transaction dates, billing resources, and amount limits
for transactions associated with the contract.
Generate invoices to calculate the invoice amounts for a contract.
457
The following diagram illustrates the components of a project and a contract that determine invoice amounts, and the
relationships between the components.
Invoice Method Classification

Assign a predefined invoice method classification to an invoice method. The invoice method classification determines whether
the invoice amount is calculated based on rates, amounts, or progress.
Invoice Method
Create invoice methods for bill plans to use for determining the approach for generating invoice amounts. The invoice
methods contain invoice generation instructions in the form of the invoice method classification and rate definition schedule
458
types. Rate definition schedule types determines whether the rate source for invoicing comes from rate schedules, burden
schedules, or transfer price schedules.
The invoice methods also contain any applicable billing extensions. If you assign a billing extension to the invoice method, the
extension calculates the invoice amount and creates an automatic invoice event. The billing extension assignment must be
active to calculate the invoice amount and create an event.
You must assign an invoice method to a bill plan, which contains the invoice generation instructions for a specific contract or
contract line. An invoice method can be used by more than one bill plan.
Caution
Enable the invoice method for intercompany billing if it will be used for intercompany billing only.
Bill Plan
Create a bill plan within a contract that uses the invoice method you require. Assign the bill plan to one or more contract lines.
If the invoice method classification for the bill plan uses a billing extension, that billing extension is automatically added to the
bill plan.
Important
Oracle Fusion Project Billing does not create new invoices for:
• Contracts on hold
• Contract lines on hold
• Contract lines with a bill plan on hold
Previously generated invoices can still be updated, submitted for approval, approved, rejected, released, and
transferred when the contract, contract line, or bill plan is on hold.
Billing Control
A billing control defines the types of permitted transactions (using billing resources), transaction date range, and maximum
invoice (and revenue) amounts for a contract or contract line. Create a billing control within a contract at either the contract or
contract line level. The inception-to-date (ITD) invoice amount cannot exceed the hard limit amount of a billing control. If the
ITD invoice amount exceeds the soft limit, invoice generation will still occur, but you will receive a warning the first time this
occurs.
Expenditure Item
The project and task for an expenditure item are matched to the associated contract line during invoice generation. Invoicing
can occur if the transaction date, billing resource, and amount for the expenditure item pass the contract billing controls.
If the expenditure item is mapped to more than one eligible contract line, the processing order is determined as follows:
• The contract billing sequence determines the processing order of multiple contracts.
• The contract billing controls determine the processing order of multiple contract lines within a single contract.
• The contract contribution percentage determines the eligible invoice amount for each contract line.
459
Oracle Fusion Project Billing creates a billing transaction for each unique combination of expenditure item and contract line.
The billing transaction is the source for creating invoice distributions.
Event
Invoice events are automatically created during invoice generation if the bill plan for a contract line plan contains a billing
extension. The billing extension calculates the invoice event amount, and creates an invoice event.
Manual events are also processed during invoice generation. Oracle Fusion Project Billing creates a billing transaction for
each automatic or manual event. The billing transaction is the source for creating invoice distributions.
Related Topics
• Project and Contract Revenue Components: How They Work Together
Specifying the Unit of Measure for Invoice Lines Sent

to Oracle Fusion Receivables: Critical Choices
The Specify Unit of Measure for Invoice Lines Sent to Oracle Fusion Receivables profile option indicates the unit of measure to
use for all invoice lines transferred from Oracle Fusion Projects to Oracle Fusion Receivables. This profile option is required in
order to use Oracle Fusion Project Billing. If you are using Oracle Fusion Projects without Oracle Fusion Receivables, you do
not need to set this profile.
Oracle Fusion Receivables requires a unit of measure for each invoice line. Oracle Fusion Projects creates each invoice line
with a quantity of 1, a unit of the unit type you specify in your profile option, and an amount equal to the currency amount of
the invoice line as it appears in Oracle Fusion Projects.
Note
The internal name for this profile option is PJB_AR_INVOICE_UOM.
Unit of Measure Class

Define a unit of measure class before you define a unit of measure. Oracle Fusion Receivables requires that you associate
each unit of measure you define with a unit of measure class. You must define a unit of measure class before you can set the
profile option.
Unit of Measure
The default unit of measure value is Each. Define a unit of measure of Each in Oracle Fusion Receivables to use with this
profile option.
Invoice and Revenue Method Classifications: Critical

Choices
Only bill plans and revenue plans with certain combinations of invoice and revenue method classifications can be used on
the same contract line. If you add a bill plan and revenue plan with an invalid invoice and revenue method classification to the
same contract line, you will receive an error message when you submit the contract for approval.
460
The possible revenue method classifications are:
• Amount based
• As incurred
• As invoiced
• Percent complete
• Percent spent
• Rate based
The possible invoice method classifications are:
• Amount based
• Rate based
• Percent spent
Invoice and Revenue Method Combinations

Valid bill plan and revenue plan combinations for a contract line are dependent on the invoice method classification and
revenue method classification. Most invoice method and revenue method classifications are valid. The invalid combinations
are described in the table below.
Revenue Method Classification Invoice Method Classification Valid Combination?
As incurred Amount based No

As incurred Percent complete No

As incurred Percent spent No

As invoiced Amount based No

As invoiced Percent complete No

As invoiced Percent spent No

Rate based Rate based Yes, but a burden schedule is

required for the bill plan and
revenue plan.

461
Note
After the contract is approved, any changes to the bill plan including the revenue or invoice method classification
must go through the change management process.
Invoice Formats: Explained

An invoice format determines how Oracle Fusion Projects creates an invoice line. You can define different formats for labor,
nonlabor and event invoice line items, and specify if you want to use the format for customer invoices, internal invoices, or
both. Additionally, you can specify how you want to summarize expenditure items, and the fields you want an invoice line to
display. You can also include free-form text on an invoice line.
You can use customer invoice formats only for regular contract invoices, and internal invoice formats only for invoices
generated by intercompany and interproject contracts. You can also use an invoice format for both customer and internal
invoices.
You configure the following components of an invoice format:
• Format type
• From and to dates
• Grouping option
• Customer or internal invoice option
• Fixed format
• Start and end position
• Text column
Format Type
The format type controls the invoice formats you see for labor, nonlabor and events when you enter invoice formats using the
Projects window.
From and To Dates

The from and to dates determine the period during which the invoice format is active.
Grouping Option
A grouping option specifies the way invoice distribution lines are grouped together to form an invoice line.
Customer or Internal Invoice Option

If you are using intercompany or interproject billing, create an internal invoice format to summarize cross-charge transactions.
Depending on the requirements of the receiver business units, you may need to define several internal invoice formats. All
internal formats automatically have a fixed format.
If you create an internal invoice format, you must select contract line as an attribute. This is to ensure that no two contract
lines can be combined into a single invoice line, as they could be tied to different receiver projects or tasks, and would need
to be created as separate invoice lines in order to post to the correct receiver project or task.
462
Although one invoice format can support both customer and internal invoices, the list of values for the Field Name only
includes those values that are shared by the two formats.
Fixed Format
A fixed format prohibits distributions from being moved to other invoice lines. Intercompany and interproject invoices must
have a fixed format.
Start and End Positions

The start and end positions are values between 1 and 240 that specify where the text in the Field Name appears on the
invoice line.
Text Column
Enter the text in this column that you want to display on the invoice.
FAQs for Define Project Invoicing Options
What's an invoice method?

Rule defined by the implementation team that determines the calculation method of invoice amounts for contracts during
invoice generation.
What's an invoice method classification?

Predefined classification for an invoice method that determines the basis for calculating invoice amounts.
The predefined invoice method classifications are: amount based, percent complete, percent spent and rate based.
Assign an invoice method classification to an invoice method. The percent spent or percent complete billing extension
is automatically assigned to the invoice method when you select the percent spent or percent complete invoice method
classification.
What happens if I assign a billing extension to an invoice

method or revenue method?
If you assign a billing extension to an invoice method or revenue method, the billing extension is automatically added to bill
plans or revenue plans that use the method. The billing extension creates automatic invoice or revenue events for contract
lines or projects associated with that bill or revenue plan.
The event amounts are calculated at the calculation level selected on the bill plan or revenue plan.
Important
You must enter the funding amount for either the contract line or the project and contract association, depending
on the calculation level selected in the bill plan or revenue plan.
Note
Billing extensions are currently not available in Oracle Cloud implementations.
463
Implementing Project Financial Management Project Billing Configuration: Define Project Revenue Options

Revenue Options
Invoice and Revenue Method Components: How They
Work Together
Invoice methods and revenue methods control the way you create invoices and recognize revenue for contracts. During
implementation you create the methods and assign them to bill plans and revenue plans. Any contract or contract line that
uses the bill or revenue plan calculates the invoice or revenue amount according to the instructions in the invoice or revenue
method.
Method Classification
Invoice method classifications and revenue method classifications are predefined by Oracle Fusion Projects. Select an invoice
or revenue method classification to set the approach for calculating invoice or revenue amounts.
This table lists the invoice method classifications and their descriptions.
Amount Based Generate invoices and revenue as billing events are

completed.

Percent Complete Generate invoices as progress is estimated.

• When you select the percent complete invoice
extension is automatically added to the invoice
method.

percent complete invoice amount for an contract
line.
Percent Spent Generate invoices as progress is calculated, based on

• When you select the percent spent invoice method

classification, the percent spent billing extension is
automatically assigned to the invoice method.

amount for an invoice line.
464
Rate Based Generate invoices as costs are incurred, using an

invoice-specific set of bill rates, a burden schedule, or

Note
The cost reimbursable classification method
bills on cost directly, without applying any
rate or markups

This table lists the revenue method classifications and their descriptions.
Amount Based Recognize revenue as billing events are completed.

As Billed Recognize revenue as customers are invoiced, using a

common set of bill rates, a burden schedule, or transfer
pricing for both invoicing and revenue.

As Incurred Recognize revenue as costs are incurred, using a

revenue specific set of bill rates, a burden schedule, or
transfer pricing for both invoicing and revenue.

Percent Complete Recognize revenue as progress is estimated.

• When you select the percent complete revenue
extension is automatically added to the revenue
method.

percent complete revenue amount for a contract
line.
465
Percent Spent Recognize revenue as progress is calculated, based on

• When you select the percent spent revenue

method classification, the percent spent billing
extension is automatically assigned to the revenue
method.

revenue amount for a contract line.
Rate Based Recognize revenue as costs are incurred, using a

revenue-specific set of bill rates, a burden schedule, or

Tip
Use this revenue classification method if
you are using a fixed price for invoices, or if
you require different burden schedules for
invoices and revenue.

Intercompany Billing Option

If the invoice or revenue method will be used for intercompany contracts, enable the intercompany billing option to calculate
the intercompany invoice or revenue amounts. Intercompany invoices and revenue use a rate-based classification method.
Select a labor and nonlabor schedule for use when generating invoices or calculating revenue.
Important
An intercompany contract can use an invoice or revenue method that is not enabled for intercompany billing, or
an invoice or revenue method that is enabled for intercompany billing. Enable the intercompany billing option if the
invoice or revenue method will be used for intercompany contracts only.
Intercompany invoices can use any type of invoice method classification.
Rate Definition
Select schedules for labor and nonlabor if your invoice or revenue method uses a rate-based classification method.
Tip
The schedule types for labor are Person and Job.
Billing Extension Assignment

Optionally, assign custom billing extensions to automatically calculate the invoice or revenue amounts for contract lines that
use the bill plans and revenue plans associated with the invoice or revenue method.
466
If the invoice or revenue method is percent complete or percent spent, the extension creates the billing event based on the
calculation level for the billing extension specified in the bill plan or revenue plan. If the calculation level is contract line, the
event is created for the contract and contract line. If the calculation level is associated project, the event is created for the
contract line and its associated project and task.
Note
If the invoice or revenue method classification is percent complete or percent spent, the percent complete or
percent spent billing extension is automatically added to the invoice or revenue method. You cannot change the
status of the billing extension assignment to inactive, it must be active for a percent complete or percent spent
billing extension.
Related Topics
• What happens if I assign a billing extension to an invoice method or revenue method?
Project and Contract Revenue Components: How

They Work Together
Project and contract components work together to create revenue distributions. The contract contains the instructions for
calculating revenue amounts, and the associated project contains the cost transaction details. When you generate revenue,
revenue distributions are created for the contract.
Expenditure items and events are the transactions for projects and contracts. Revenue method classifications determine how
transactions recognize revenue.
The revenue method determines how revenue rates are derived and which billing extensions are called to calculate revenue.
Enter a revenue method on a revenue plan, which you create for a contract and assign to contract lines to provide a set of
instructions for recognizing revenue.
Create billing controls for a contract or contract line to define the valid transaction dates, billing resources, and amount limits
for transactions associated with the contract.
Generate revenue to calculate the revenue amounts for a contract.
467
The following diagram illustrates the components of a project and a contract that determine revenue amounts, and the
relationships between the components.
Revenue Method Classification

Assign a predefined revenue method classification to a revenue method. The revenue method classification determines
whether the revenue amount is calculated based on rates, amounts, or progress.
Revenue Method
Create revenue methods for revenue plans to use for recognizing revenue. The revenue methods contain revenue recognition
instructions in the form of the revenue method classification, rate definition schedule types and any applicable billing
468
extensions. If you assign a billing extension to the revenue method, the extension calculates the revenue amount and creates
an automatic revenue event. The billing extension assignment must be active to calculate revenue and create an event.
You must assign a revenue method to a revenue plan, which will give the revenue recognition instructions to a specific
contract or contract line. A revenue method can be used by more than one revenue plan.
Caution
Enable the revenue method for intercompany billing if it will be used for intercompany billing only.
Revenue Plan
A revenue plan contains a set of instructions for recognizing revenue on a contract or contract line. Create a revenue plan
within a contract that uses the revenue method you require. Assign the revenue plan to one or more contract lines that are
enabled for billing.
If the revenue method classification for the revenue plan uses a billing extension, that billing extension is automatically added
to the revenue plan.
Important
Revenue cannot be recognized for a revenue plan on hold.
Billing Control
A billing control defines the type of permitted transactions (using billing resources), transaction date range, and maximum
invoice and revenue amounts for a contract or contract line. Create a billing control within a contract at either the contract
or contract line level. The revenue amount cannot exceed the hard limit amount of a billing control. If the revenue amount
exceeds the soft limit, revenue recognition will still occur, but you will receive a warning.
Expenditure Item
The project and task for an expenditure item are matched to the associated contract line during revenue generation. Revenue
recognition can occur if the transaction date and billing resource for the expenditure item pass the contract billing controls.
If the expenditure item is mapped to more than one eligible contract line, the processing order is determined as follows:
• The contract billing sequence determines the processing order of multiple contracts.
• The contract billing controls determine the processing order of multiple contract lines within a single contract.
• The contract contribution percentage determines the eligible amount of revenue to recognize for each contract line.
Oracle Fusion Project Billing creates a billing transaction for each unique combination of expenditure item and contract line.
The billing transaction is the source for creating revenue distributions.
Event
Revenue events are automatically created during revenue generation if the revenue plan for a contract line plan contains a
billing extension. The billing extension calculates the revenue event amount, and creates a revenue distribution.
Manual events are also processed during revenue generation. Oracle Fusion Project Billing creates a billing transaction for
each event. The billing transaction is the source for creating revenue distributions.
Related Topics
• Invoice and Revenue Method Components: How They Work Together
469
• Event Components: How They Work Together
Invoice and Revenue Method Classifications: Critical

Choices
Only bill plans and revenue plans with certain combinations of invoice and revenue method classifications can be used on
the same contract line. If you add a bill plan and revenue plan with an invalid invoice and revenue method classification to the
same contract line, you will receive an error message when you submit the contract for approval.
The possible revenue method classifications are:
• Amount based
• As incurred
• As invoiced
• Percent spent
• Rate based
The possible invoice method classifications are:
• Amount based
• Rate based
• Percent spent
Invoice and Revenue Method Combinations

Valid bill plan and revenue plan combinations for a contract line are dependent on the invoice method classification and
revenue method classification. Most invoice method and revenue method classifications are valid. The invalid combinations
are described in the table below.
As incurred Amount based No

As incurred Percent complete No

As incurred Percent spent No

As invoiced Amount based No

470
As invoiced Percent complete No

As invoiced Percent spent No

Rate based Rate based Yes, but a burden schedule is

required for the bill plan and
revenue plan.

Note
After the contract is approved, any changes to the bill plan including the revenue or invoice method classification
must go through the change management process.
FAQs for Define Project Revenue Options
What's a revenue method?

Rule defined by the implementation team that determines the calculation method of revenue amounts for contracts during
revenue generation.
What's a revenue method classification?

Predefined classification for a revenue method that determines the basis for calculating revenue amounts.
The predefined revenue method classifications are as-billed, as-incurred, amount based, percent complete, percent spent,
and rate based.
Assign a revenue method classification to a revenue method. When you select the percent spent or percent complete
revenue method classification, the percent spent or percent complete billing extension is automatically assigned to the
revenue method.
What happens if I assign a billing extension to an invoice

method or revenue method?
If you assign a billing extension to an invoice method or revenue method, the billing extension is automatically added to bill
plans or revenue plans that use the method. The billing extension creates automatic invoice or revenue events for contract
lines or projects associated with that bill or revenue plan.
The event amounts are calculated at the calculation level selected on the bill plan or revenue plan.
Important
You must enter the funding amount for either the contract line or the project and contract association, depending
on the calculation level selected in the bill plan or revenue plan.
471
Note
472
Implementing Project Financial Management Project Billing Configuration: Define Project Billing Business
Unit Options

Billing Business Unit Options
Specify Customer Contract Management Business

Function Properties
Customer Contracts Business Unit Setup: Explained

Using the Specify Customer Contract Management Business Function Properties task, available by navigating to
Setup and Maintenance work area and searching on the task name, you can specify a wide variety of business function
settings for customer contracts in a specific business unit. The selections you make for these business functions impact how
Oracle Fusion Enterprise Contracts behaves during contract authoring.
Using the Specify Customer Contract Management Business Function Properties task, manage these business
function properties:
• Enable related accounts
• Set currency conversion details
Note
The customer must select a default currency in the customer or supplier business function properties
page, if not autopopulated from the ledger assigned to the business unit in the assign business function
setup task.
• Manage project billing options
• Set up clause numbering
• Set up the Contract Terms Library
The setup options available for the Contract Terms Library are applicable to both customer and supplier contracts,
and are described in the business unit setup topic for the Contract Terms Library. That topic is available as a related
link to this topic.
Enabling Related Customer Accounts

Contract authors can specify bill-to, ship-to, and other accounts for the parties in a contract. Enable the related customer
accounts option if you want accounts previously specified as related to the contract party to be available for selection.
Managing Currency Conversion Options

If your organization plans to transact project-related business in multiple currencies, then select the multicurrency option. This
allows a contract author to override a contract's currency, which defaults from the ledger currency of the business unit. It
473
Unit Options
also enables the contract author to specify currency conversion attributes to use when converting from the bill transaction
currency to the contract currency and from the invoice currency to the ledger currency.
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.
In the Invoice Currency to Ledger Currency region:
• Enter invoice transaction conversion details if the invoice and ledger currencies can be different.
• Enter revenue transaction conversion details if the revenue and ledger currencies can be different for as-incurred and
rate-based revenue.
Managing Project Billing Options

The options available for selection in the Project Billing region control the behavior of project invoicing and revenue recognition
for contracts with project-based work.
Project billing can behave differently for external contracts (customer billing) or intercompany and interproject contracts
(internal billing).
Set these options, which apply to all contracts:
• Select the Transfer Revenue to General Ledger option if you want to create revenue accounting events and
entries, and transfer revenue journals to the general ledger. If this option is not selected, then revenue can still be
generated, but will not be transferred to the general ledger.
• Indicate if a reason is required for credit memos that are applied to invoices.
There are two sets of the following options, 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.
• Select the Receivables batch source to use when transferring invoices to Receivables.
Set this option only for customer billing:
• Indicate if you want contract authors to manually enter the Receivables transaction type on the customer contracts
they create.
Managing Clause Numbering

You can choose to number clauses manually or automatically.
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.
474
Unit Options
Contract Terms Library Business Unit Setup: Explained

You can specify a wide variety of Contract Terms Library settings for either customer or supplier contracts within each
business unit, by using either the Specify Customer Contract Management Business Function Properties or the
Specify Supplier Contract Management Business Function Properties tasks. These tasks are available by navigating to
the Setup and Maintenance work area and searching on the task name.
For the Contract Terms Library in each business unit, you can:
• Enable clause and template adoption.
• Set the clause numbering method.
• Set the clause numbering level for automatic clause numbering of contracts.
• For a contract with no assigned ledger or legal entity, set the document sequence to Global or Business Unit level.
• Enable the Contract Expert enabling feature.
• Specify the layout for printed clauses and contract deviation reports.
Enabling Clause Adoption

If you plan to use clause adoption in your implementation, then set up the following:
• Specify a global business unit
You must designate one of the business units in your organization as the global business unit by selecting the
Global Business Unit option. This makes it possible for the other local business units to adopt and use approved
content from that global business unit. If the Global Business Unit option is not available for the business unit you
are setting up, this means that you already designated another business unit as global.
• Enable automatic adoption
If you are implementing the adoption feature, then you can have all the global clauses in the global business unit
automatically approved and available for use in the local business by selecting the Autoadopt Global Clauses
option. If you do not select this option, the employee designated as the Contract Terms Library Administrator must
approve all global clauses before they can be adopted and used in the local business unit. This option is available
only for local business units.
• Specify the administrator who approves clauses available for adoption
You must designate an employee as the Contract Terms Library administrator if you are using adoption. If you do not
enable automatic adoption, then the administrator must adopt individual clauses or localize them for use in the local
business unit. The administrator can also copy over any contract terms templates created in the global business unit.
The clauses and contract terms templates available for adoption are listed in the administrator's Terms Library work
area.
Setting Clause Numbering Options

You can set up automatic clause numbering for the clauses in the business unit by selecting Automatic in the Clause
Numbering field and setting the clause numbering level. Then select the appropriate clause sequence category for the
475
Unit Options
specified numbering level. You must have previously set up document sequences for the document sequence 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.
Enabling Contract Expert

You must select the Enable Contract Expert option to be able to use the Contract Expert feature in a business unit. This
setting takes precedence over enabling Contract Expert for individual contract terms templates.
Specifying the Printed Clause and Deviations Report Layouts

For each business unit, you can specify the Oracle BI Publisher RTF file that serves as the layout for:
• The printed contract terms
Enter the RTF file you want used for formatting the printed clauses in the Clause Layout Template field.
• The contract deviations report
The RTF file you select as the Deviations Layout Template determines the appearance of the contract deviations
report PDF. This PDF is attached to the approval notification sent to contract approvers.
Related Topics
• How the Selection of a Business Unit Affects Clauses and Other Objects in the Library
• Contract Expert: How It Works
• Contract Printing and Layout Templates: Explained
FAQs for Define Project Billing Business Unit Options
Why can't I locate an invoice?

Access to invoices is secured by the business unit. You only have access to invoices that belong to contracts in the business
unit assigned to your role. You can see all invoices for projects that are linked to the contracts which you can access.
476
Implementing Project Financial Management Project Billing Configuration: Define Intercompany Project
Billing
38 Project Billing Configuration: Define

Intercompany Project Billing
Intercompany Balancing Rules: Explained
Intercompany balancing rules are used to generate the accounts needed to balance journals that are out of balance by legal
entity or primary balancing segment values.
You specify the intercompany receivables and intercompany payables accounts you want to use. The intercompany
balancing feature then uses these rules to generate the accounts of the balancing lines it creates.
Defining Intercompany Balancing Rules

You can define intercompany balancing rules at the following rule levels:
1. Primary balancing segment

2. Legal entity
3. Ledger
4. Chart of accounts
The rules are evaluated in the order shown above. For example, you can define a Primary Balancing Segment rule and a
Legal Entity level rule. If both rules are used to balance a particular journal, the Primary Balancing Segment rule is used, as it
has a higher precedence.
You have flexibility in defining your intercompany balancing rules. You can have a simple setup in which you define one rule
for your chart of accounts. This rule is used for all intercompany balancing for all ledgers that use this chart of accounts.
Alternatively, you can have a more granular set of rules. For example, you can define a different rule for each legal entity and
one chart of accounts rule to cover any gaps in your rule definitions. You can gain even more granularity by defining rules for
specific journal and/or category combinations or intercompany transaction types.
Intercompany Balancing Rules: Examples

This topic provides examples of intercompany balancing rules and the intercompany balancing lines generated. These rules
are used to generate the accounts needed to balance journals that are out of balance by legal entity or primary balancing
segment values.
Simple Chart of Accounts

In this scenario you have one chart of accounts for all ledgers. The chart of accounts has an intercompany segment. You
are using this intercompany segment and the company segment to identify the intercompany trading partners for each
transaction. You do not have a need to track their intercompany activity at a granular level such as by journal source and
journal category or by intercompany transaction type.
Setup
• InFusion USA Chart of Accounts
477
Billing
Segment Primary Second Third Account Intercompany
Qualifier Balancing Balancing Balancing Segment
Segment Segment Segment
Segment Company Cost Center Product Account Intercompany

Name
(CO) (CC) (PROD) (ACCT) (IC)

• Ledger, Legal Entity, Primary Balancing Segment Value Assignments
Ledger Legal Entity Primary Balancing Segment

Value
InFusion USA InFusion Farms 3100, 3200, 3300, 3400, 3500

InFusion USA InFusion Textiles 4000

InFusion USA InFusion Products (East) 5000

InFusion USA InFusion Products (West) 6000

InFusion USA 1000, 9000

• Chart of Accounts Rule
Rule Chart of AR AP Source Category Transaction

Number Accounts Account Account Type
1 InFusion 1000 - 000 1000 - 000 Other Other None

USA - 0000 - - 0000 -
Chart of 13010 - 21010 -
Accounts 0000 0000

• Journal Balancing
◦ Journal before Balancing
Line Line Legal CO CC PROD ACCT IC Debit Credit

Type Entity
1 Expense InFusion 3100 100 1200 52330 0000 150

Farms
478
Billing
Type Entity

2 Liability InFusion 4000 500 1300 40118 0000 150

Textiles

◦ Journal after Balancing
Uses Line Line Legal Company Cost Product Account Intercompany

Debit Credit
Rule Type Entity Center

Farms


Textiles

1 3 IC InFusion 3100 100 1200 21010 4000 150

AP Farms

1 4 IC InFusion 4000 500 1300 13010 3100 150

AR Textiles

Legal Entity and Chart of Accounts Rules

In this example the legal Entity InFusion Textiles intercompany manufacturing activities are tracked separately from its non-
manufacturing activities. In order to achieve this legal entity level rules are defined specifically between the legal entity InFusion
Textiles and the two manufacturing legal entities, InFusion Products (East) and InFusion Products (West). A chart of accounts
rule is created to cover all other intercompany activities.
Setup


Name
479
Billing


Value







USA - 0000 - - 0000 -
Chart of 13050 - 21050 -
Accounts 0000 0000

• Legal Entity Level Rule
Rule No. From To Legal AR AP Source Category Transaction

Legal Entity Account Account Type
Entity
3 InFusion InFusion 1000 - 1000 - Other Other None

Textiles Products 000 - 000 -
(West) 0000 - 0000 -
13020 - 21020 -
0000 0000

480
Billing
Rule No. From To Legal AR AP Source Category Transaction
Legal Entity Account Account Type
Entity
4 InFusion InFusion 1000 - 1000 - Other Other None

Textiles Products 000 - 000 -
(East) 0000 - 0000 -
13030 - 21030 -
0000 0000


Type Entity

Farms


Products
(East)


Products
(West)


Textiles

Uses Line Line Legal CO CC PROD ACCT IC Debit Credit

Rule Type Entity

Farms

2 Expense InFusionProducts
5000 100 1200 52340 0000 200
(East)

481
Billing
Rule Type Entity
3 Expense InFusionProducts
6000 200 1300 52345 0000 300
(West)


Textiles

2 5 IC InFusion 4000 500 1300 13050 3100 150

AR Textiles

2 6 IC InFusion 3100 100 1200 21050 4000 150

AP Farms

4 7 IC InFusion 4000 500 1300 13030 5000 200

AR Textiles

2 8 IC InFusionProducts(East)
5000 100 1200 21050 4000 200
AP

3 9 IC InFusion 4000 500 1300 13020 6000 300

AR Textiles

2 10 IC InFusionProducts
6000 200 1300 21050 4000 300
AP (West)

Defining Ledger Balancing Options: Explained

Ledger balancing options are defined for the ledger to balance the second balancing segment and/or the third balancing
segment, when a transaction is unbalanced by one of these segments.
Ledger balancing options include the following settings:
• Oracle Fusion Receivables and Oracle Fusion Payables accounts used for ledger balancing
• Summarization options
• Clearing company options
Receivables and Payables Accounts used for Ledger Balancing

You can choose to specify the receivables and payables accounts to be used, if your chart of accounts has the second
balancing segment and/or the third balancing segment enabled. These accounts are used for the balancing lines generated
482
Billing
when a journal is balanced by its primary balancing segment values but is not balanced by its second balancing segment
and/or third balancing segment.
Summarization Options
You can choose to summarize balancing lines generated for a primary balancing segment out of balance scenario, where
all the primary balancing segment values are assigned to the same legal entity, by specifying the Summarization option of
Summary Net or Detail. You can choose to summarize by primary balancing segment value or alternatively have individual
balancing lines (that have not been summarized) generated. Note that summarization always applies to balancing lines
generated in a cross legal entity scenario.
Clearing Company Options

You can choose to set clearing company options to balance a journal with different primary balancing segment values that all
belong to a single legal entity. Set the following options to handle your clearing company balancing.
• Clearing Company Condition
◦ Choose to balance using a clearing company value for all journals or for journals with many legal entities on the
debit side and many legal entities on the credit side.
◦ The default value for this option is to error Many-to-Many journals.
• Clearing Company Source
◦ Choose how the clearing company value is derived for your balancing lines, from the following options:
• Default clearing balancing segment value.
◦ Choose this option if you want a single specific primary balancing segment value for your clearing
company.
• Default Rule.
◦ Choose this option if you want to allow the system to derive the clearing company value from a default
intercompany balancing rule.
• Manually entered clearing balancing segment value.
◦ Choose this option if you want to enter the clearing company value when you create a journal.
• Clearing Company Value
◦ If you chose the default clearing balancing segment value as your clearing company source, you can enter your
chosen primary balancing segment value in this field.
Defining Ledger Balancing Options: Examples

This topic provides examples of ledger balancing options, the setup required, and the journal before and after balancing.
483
Billing
Simple Ledger Balancing with no Clearing Company Options

In this scenario the enterprise has the second balancing segment and the third balancing segment enabled for its chart of
accounts. The journal is balanced by primary balancing segment but is out of balance by the second balancing segment and
the third balancing segment.
Setup


Name
(CO) (CC) (PROD) (ACCT) (IC)


Value





• Ledger Balancing Options
Rule Ledger Source Category Transaction AR AP

Number Type Account Account
1 InFusion Other Other None 1000 - 000 1000 - 000

USA - 0000 - - 0000 -
13010 - 21010 -
0000 0000
484
Billing

◦ Journal Before Balancing

Type Entity

Farms


Farms


Rule Type Entity

Farms


Farms

1 3 AP InFusion 3100 100 1200 21010 0000 150

Farms

1 4 AR InFusion 3100 500 1300 13010 0000 150

Farms

Ledger Balancing Options with Detail Summarization and

Clearing Company Options Set
In this scenario the enterprise has the second balancing segment and the third balancing segment enabled for its chart of
accounts. Management has decided to use a clearing company for balancing Many-to-Many journals only. Since the primary
485
Billing
balancing segment values in the journal are out of balance intercompany balancing is required. Additionally, since clearing
company options have been specified they will be used to balance the journal. Note that if the primary balancing segment
values were balanced and only the second balancing segment and the third balancing segment were out of balance, the
clearing company options would not be used.
Setup
• InFusion 1000, USA Chart of Accounts
Segment Primary Second Third Intercompany


Name


Value







USA - 0000 - - 0000 -
Chart of 13050 - 21050 -
Accounts 0000 0000

• Ledger Balancing Options
486
Billing
2 InFusion Other Other None 1000 - 000 1000 - 000

USA - 0000 - - 0000 -
13010 - 21010 -
0000 0000

• Clearing Company Options
Rule Ledger Source Category Transaction Condition Source Value

Number Type
2 InFusion Other Other None Use for Default 9000

USA many- clearing
to-many balancing
journals segment
only value

Note
The Ledger Balancing Options and Clearing Company Options appear as one line on the page.

Type Entity

Farms


Farms


Farms


Farms


Farms

487
Billing

Rule Type Entity

Farms


Farms


Farms


Farms


Farms

1 6 IC 9000 000 0000 13050 3100 150

AR

1 7 IC 3100 100 1200 21050 9000 150

AP

1 8 IC 9000 000 0000 13050 3100 200

AR

1 9 IC 3100 300 1200 21050 9000 200

AP

1 10 IC 9000 000 0000 13050 3300 300

AR

1 11 IC 3300 200 1300 21050 9000 300

AP

1 12 IC 3400 200 1300 13050 9000 320

AR

488
Billing
Rule Type Entity
1 13 IC 9000 000 000 21050 3400 320

AP

1 14 IC 3500 600 1400 13050 9000 330

AR

1 15 IC 9000 000 000 21050 3500 330

AP

Project Components for Internal Billing: How They

Work Together
Invoice Formats
Restriction

• Bill rate
• Burden rate
• Transfer price
489
Billing

Receiver Project
Provider Project
Related Topics
• Contract Components for Internal Billing: How They Work Together
Contract Components for Internal Billing: How They

Work Together


490
Billing



Receivables.


Note
Related Topics
• Project Components for Internal Billing: How They Work Together
• Why can't I see the internal billing details on a contract?
491
Billing
Define Invoicing Options
Invoice Options: Critical Choices

Invoice options are settings and default values that control how Oracle Fusion Payables processes invoices for an invoice
business unit. You can specify options for the following invoice areas on the Manage Invoice Options page:
• Invoice entry and matching

• Discounts
• Prepayments
• Approvals
• Interest
• Payment requests
• Self-service invoices
Invoice Entry and Matching

This table lists the options you can set for invoice entry and matching.
Option Description
Require invoice grouping Requires that you enter the name of a group when
creating an invoice.

Allow document category override Allows override of the document category that is
automatically assigned to an invoice if the ledger option
Sequencing By is set to Ledger or Legal entity. If the
Sequencing By option is set to No sequencing, the
application doesn't assign a document category to an
invoice, and you cannot set this invoice option or enter a
document category for the invoice.
Allow adjustments to paid invoices Lets you cancel or add lines to paid invoices. In addition,
you can unmatch an invoice from a purchase order
that is not finally matched, and match the invoice
to a different purchase order. You cannot modify
distributions because it would affect the accounting.

Allow remit-to supplier override for third-party payments Allow the override of remit-to supplier name and address
on invoice installments for suppliers with third-party
relationships.

Recalculate invoice installments Recalculates installments during the invoice validation

process.

492
Billing
Option Description
Hold unmatched invoices Applies a Matching required hold during invoice

validation on invoices that are not matched to a
purchase order or receipt. This option can be set on
a supplier to one of the following values: Yes, No, or
Default from Payables Options. The invoice option is
used only when the setting on a supplier site is Default
from Payables Options.
Receipt acceptance days Specifies the number of days added to the Goods
Received date when recalculating installments.
Accounting date basis Provides the basis for the default accounting date. If
you select Goods received or invoice date, and the
invoice does not have a date for goods received, then
the application uses the invoice date as the default
accounting date. If you select Goods received or
system date, and the invoice does not have a date for
goods received, then the application uses the system
date as the default accounting date.
Allow final matching Lets you perform a final match when you match an
invoice to a purchase order, or when you adjust a
matched invoice distribution. You cannot perform a final
match when matching invoices to receipts.

Allow matching distribution override Allows override of the invoice distribution created from
matching an invoice to a purchase order.

You cannot override the distribution for a matched
invoice if you accrue at receipt. In addition, you cannot
override the distribution if the purchase order is projects-
related, and the item destination for the purchase order
distribution is inventory.

Transfer PO distribution additional information Transfers descriptive flexfield information from the
purchase order distribution to the invoice distribution
when you match an invoice to a purchase order. If you
enable this option, make sure that the flexfield structure
is the same for the purchase order distributions and the
invoice distributions.

Budget date basis Provides the basis for the default budget date when you
create an invoice.

In addition to the options previously listed, you can specify default values for the following attributes on both the Manage
Invoice Options page and on the supplier setup. Payables uses the default values from the Manage Invoice Options page,
unless you specify a different value for the supplier.
• Invoice currency
493
Billing
• Payment currency
• Pay group
• Payment priority
• Payment terms
• Terms date basis
• Pay date basis
• Quantity tolerances
• Amount tolerances
Discounts
This table lists the options you can set for discounts. You can also set these options on the supplier setup, except for
Discount Allocation Method. The values for these options on the supplier setup are: Yes, No, Default from Payables
Options.
Option Description
Exclude tax from calculation Subtracts the tax amount from the invoice amount
during invoice entry, when calculating the discountable
amount for an installment. If you enable this option, you
cannot select a Discount Allocation Method of Tax
lines and single distribution.
Exclude freight from calculation Subtracts the freight amount from the invoice amount
during invoice entry, when calculating the discountable
amount for an installment.

Discount allocation method Allocates discounts across distributions.

Always take discount Takes the available discount for a supplier, regardless of
when you pay the invoice.

Prepayments
This table lists the options you can set for prepayments.
Option Description
Payment terms Represents default payment terms. For example, you

may want to have immediate payment terms for all
prepayment type invoices.

Settlement days Specifies the number of days to add to the system

date to calculate the default settlement date for a
494
Billing
Option Description
prepayment. You cannot apply a prepayment to an
invoice until on or after the settlement date.

You can also set this option on the supplier setup. The
value for the supplier setup determines if this option is
used.

Use distribution from purchase order Builds the distribution combination for the matched
invoice distribution by taking the purchase order
distribution combination and overriding the natural
account segment with the one from the supplier site
prepayment distribution or, if not defined, from the
common options prepayment distribution.

Show available prepayments during invoice entry Displays the number and amount of available
prepayments during invoice entry.

Approvals
You can use the invoice approval workflow to automate your invoice approval process. The workflow determines if an invoice
requires approval, and if so, automatically routes the invoice to the applicable approvers who then approve or reject the
invoice.
This table lists the options you can set for the invoice approval process.
Option Description
Enable invoice approval Processes invoices through the approval workflow. The
approval workflow is automatically initiated for payment
requests and self-service invoices that are created in
Oracle Fusion Supplier Portal and not matched to a
purchase order.

Require validation before approval Processes only invoices that are validated. Enable this
option if you need the invoice validation process to
create tax distributions for an invoice before approvers
review it. Payment requests and self-service invoices
created in Supplier Portal that are not matched to
a purchase order always require approval before
validation, regardless of the option selected.

Require accounting before approval Processes invoices that are accounted.

495
Billing
Option Description
Allow force approval Allows managers to override the workflow and manually
approve invoices. For example, you might want to force
approval of an invoice if the invoice approval workflow
does not complete, or if you have authority to pay an
invoice without using the workflow process.

Interest
This table lists the options you can set for interest on overdue invoices.
Option Description
Create interest invoices Calculates interest on overdue invoices and creates

interest invoices. You can also set this option on the
supplier setup. The values for this option on the supplier
setup are: Yes, No, Default from Payables Options.
Minimum interest amount Minimum amount of calculated interest below which an

interest invoice is not created.

Interest allocation method Allocates interest across distributions.

Interest expense distribution Distribution combination used if allocating interest

expense to a single distribution.

Payment Requests
You can specify the following default values for a payment request:
• Payment terms
• Pay group
• Payment priority
Self-Service Invoices
This table lists the options you can set for invoices created in Supplier Portal.
Option Description
Limit invoice to single purchase order Limits an invoice to the schedules belonging to a single
purchase order.

Allow invoice backdating Allows a supplier to enter an invoice for a date in the
past.

496
Billing
Option Description
Allow unit price change for quantity-based matches Allows a supplier to enter a unit price on the invoice that
is different from the unit price on the purchase order.

Note
You can use the Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheet task to
automate your invoice options setup.
Related Topics
• Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheets: Explained
• Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheets: How They Are Processed
Invoice Installments: How They Are Recalculated

During invoice entry, installments are automatically created using the payment terms and terms date information. You can
optionally configure your setup to recalculate installments during the invoice validation process.
Settings That Affect Installment Recalculation

Select the Recalculate invoice installments option on the Manage Invoice Options page to recalculate invoice installments
during validation
Note
If you enable the Exclude tax from calculation option on the Manage Invoice Options page and manually
change the tax amount, the application also recalculates invoice installments. This re-creation of the installments
isn't based on the setting of the Recalculate invoice installments option.
Restriction
Installments are aren't recalculated if you have manually edited or split any of the installments.
How Invoice Installments Are Recalculated

The recalculation uses the most recent applicable start date and the most favorable of the applicable payment terms. To
determine which terms are more favorable, the recalculation compares payment term ranks.
The following table shows the start dates and payment terms that the installment recalculation process uses for matched and
unmatched invoices.
Matched to a PO Start Date Payment Terms
No Most recent of the following: Invoice payment terms

• Invoice date
• Terms date
497
Billing
Matched to a PO Start Date Payment Terms
• Goods received date plus
receipt acceptance days
Yes Most recent of the following: More favorable of the following:

• Invoice date • Invoice payment terms
• Terms date • PO payment terms
• Goods received date plus

receipt acceptance days
Discount Allocation Methods: Critical Choices

Determine the method to use for distributing the discounts you take when making payments. Select one of the following
options:
• All invoice lines
• Tax lines and single distribution
• Single distribution
All Invoice Lines

Oracle Fusion Payables automatically prorates any discounts across all invoice lines. Payables assigns the discount to the
charge account unless the invoice is matched to a purchase order with Accrue at receipt enabled, in which case the
discount is assigned to the price variance account.
Note
If you exclude tax from the discount calculation and select this method, Payables allocates discounts only to
expense lines and not to the tax lines.
Tax Lines and Single Distribution

Payables automatically prorates a percentage of the discount across the tax lines. The percentage of discount prorated is
equal to the percentage of the tax lines. Payables credits the remaining discount amount to the Discount Taken distribution
on the Manage Common Options for Payables and Procurement page. For example, if your tax distributions are 10 percent
of the total invoice amount, Payables prorates 10 percent of the discount amount across the tax distributions and credits the
remaining 90 percent of the discount amount to the Discount Taken distribution.
You cannot select this method if you exclude tax from discount calculation.
Single Distribution
Payables credits all discounts to the Discount Taken distribution on the Manage Common Options for Payables and
Procurement page. If you enable automatic offsets, and want to distribute discount taken amounts across balancing
segments, select the Single distribution method.
498
Billing
Interest Invoices: Explained

Oracle Fusion Payables automatically creates invoices to pay interest for overdue invoices if you enable automatic interest
calculation for a supplier, and if you pay an overdue invoice in a payment process request or with a Quick payment. The
interest invoice is automatically paid along with the overdue invoice.
To use automatic interest rate calculation, define the interest rates and enable the Allow interest invoices option on the
Manage Invoice Options page and the Allow interest invoices option for the supplier. You can add, change, or delete a rate
at any time. If a rate is not defined, a zero rate is used.
Note
Payables does not create interest invoices when you pay overdue invoices with a Manual payment.
Interest invoices have the following components:
• Number
• Terms
• Amount
• Currency
Number
The interest invoice number is the same as the overdue invoice number, but with the suffix -INTx, where x is the count of
interest invoices that were created for the overdue invoice. For example, the third interest invoice created for an overdue
invoice has the suffix -INT3.
Terms
The payment terms on an interest invoice are Immediate. If you do not have Immediate terms defined, the interest invoice
payment terms are the same as the overdue invoice.
Amount
The amount of the interest invoice is the interest amount owed. Payables calculates interest based on the rate you enter on
the Manage Interest Rates page in accordance with the United States Prompt Payment Act. The formula used compounds
monthly, up to a maximum of 365 days interest.
Currency
Interest invoices have the same invoice currency and payment currency as the overdue invoice.
If an overdue invoice is in one currency and the payment for the overdue invoice is in another currency:
• The invoice currency for the interest invoice is the same as the invoice currency for the overdue invoice.
• The payment currency for the interest invoice is the same as the payment currency for the overdue invoice.
Related Topics
• Interest on Overdue Invoices: How It Is Calculated
499
Billing
Interest Allocation Methods: Critical Choices

Oracle Fusion Payables creates and accounts for interest invoices based on one of the following options:
• Single distribution
• All invoice lines
Single Distribution
Payables creates interest invoices with a single distribution using the Interest Expense distribution on the Manage Invoice
Options page.
All Invoice Lines

Payables uses the natural account segment from the Interest Expense distribution on the Manage Invoice Options page
when it builds expense distributions for an interest invoice.
Payment Requests: Explained

Oracle Fusion Receivables and Oracle Fusion Expenses can submit requests to Oracle Fusion Payables to disburse funds to
a payee who is not defined as a supplier. Payables records these requests as payment requests. You can disburse the funds
and manage the payment process using the payment management functionality that is available in Payables.
Create a payment request from Receivables for a customer refund or from Expenses for an expense report. Expenses
submits payment requests to request reimbursement of employee expenses to the employee or directly to the corporate
credit card provider. Once the Expense Report Auditor has completed their review and determined the expense report is
ready for reimbursement, they will submit the Process Expense Reimbursement program to create the payment request real
time in Payables. Any exceptions to this process are managed in Expenses.
Note
You can only submit a payment request from other applications; you cannot enter a payment request for a payee
directly in Payables.
Setting Up Payment Requests

There are no specific setup steps required to use payment requests however, the following setups do affect the payment
request process. Review these setups if you plan to use payment requests.
• Invoice options. Set the default options to be considered for payment requests such as payment terms, pay group,
and payment priority.
• Payment request document category. Comply with document sequencing policies using the predefined payment
request category or override the document category, if allowed. If the Sequence Numbering Enforced profile
is set to Partially Used or Always Used, ensure that you have assigned a sequence to the payment request
document category.
You can use the following Oracle Fusion Payments setups to manage payment requests separately from other payments:
• Payment method controls
• Payment method defaulting rules
500
Billing
• Payment file and report formats
• Payment attribute validations
Reporting on Payment Requests

Track progress of the payment request in the originating application. Once the payment request is approved, you can report
on and audit the payment request in Payables using the following reports:
• Payables Invoice Aging
• Payables Invoice Audit by Voucher Number Listing
• Payables Open Items Revaluation
• Payables Cash Requirement
Related Topics
• Issuing Manual Refunds: Explained
• Expense Report Payment Requests: How They Are Processed
FAQs for Define Intercompany Project Billing
Why can't I see the internal billing details on a contract?

If you do not see the internal billing features on a contract, check the attributes on the contract type. The internal billing
options of a contract are only visible if the contract type is designated as either intercompany or interproject.
501
Implementing Project Financial Management Project Billing Configuration: Define Transfer Pricing
39 Project Billing Configuration: Define Transfer

Pricing
Manage Transfer Price Rules
Transfer Price Rules: Critical Choices

Create rules to determine how transfer prices are calculated for cross-charge transactions that require borrowed and lent
processing or intercompany billing processing. Transfer price calculation can be based on the raw cost, burdened cost, or
revenue of the cross-charged transaction.
To set up transfer price rules, you need to understand the following components:
• Transfer price rule attributes
• Transfer price determination logic
• Transfer price extensions
Transfer Price Rule Attributes

To create a transfer price rule, you specify the rule name and description, and define these attributes:
• Type: Valid transfer price rule types are Labor or Nonlabor.
• Transfer Price Basis: The basis for transfer price calculation. Transfer price basis options are:
◦ Raw cost
◦ Burdened cost
◦ External recognized revenue

• Calculation Method: Transfer price calculation methods are:
◦ Basis only: Use the transfer price with no further adjustments
◦ Apply burden schedule: Specify the name of an existing burden schedule to apply to the basis
◦ Apply rate schedule: Specify the name of an existing rate schedule to apply to the basis
• Burden Schedule: The burden schedule to apply to the transfer price basis if the transfer price calculation method
is to apply a burden schedule. You can select any burden schedule from any set.
• Rate Schedule: The rate schedule to apply to the transfer price basis if the transfer price calculation method is to
apply a rate schedule. You can select any rate schedule from any set.
• Markup or Discount Percentage: A rate to apply to the transfer price amount that the rule calculates.
502
Transfer Price Determination Logic

The following table lists the valid combinations of transfer price basis and calculation methods, and the calculation logic used
to determine transfer price amounts based on transfer price rules.
Transfer Price Basis Calculation Method Calculation Logic Transfer Price

Transaction Currency
Raw cost Basis only Raw cost with no Same as transaction

multipliers applied currency of expenditure
item

Raw cost Apply burden schedule Burden multipliers are Same as transaction
applied to raw cost currency of expenditure
item

Raw cost Apply rate schedule If the rate schedule has Currency of the rate
a markup, the markup is schedule
applied to raw cost

If the rate schedule has a
multiplier, the multiplier is
applied to the amount

Burdened cost Basis only Burdened cost with no Same as transaction

multipliers applied currency of expenditure
item

Burdened cost Apply burden schedule Burden multipliers are Same as transaction
applied to burdened cost currency of expenditure
item

Burdened cost Apply rate schedule Rate multipliers are Currency of the rate
applied to burdened cost schedule

External recognized Basis only External recognized Regular recognized

revenue revenue with no revenue in ledger
multipliers applied currency, which is
an attribute of the
expenditure item

Transfer Price Extensions

Set up the following transfer price extensions as needed:
• The Transfer Price Determination Extension is called at the beginning of the pricing calculation to bypass the transfer
price amount that is calculated using the standard transfer price rule. If you use this extension, the transfer price
amount is calculated and cross-charge transactions are created based on the extension logic.
503
• The Transfer Price Override Extension is called at the end of the pricing calculation to override the transfer price
amount that is calculated using the standard transfer price rule. The calculated transfer price amount is a parameter
to the extension. If you use this extension, the transfer price amount is calculated and cross-charge transactions are
created based on the extension logic.
• The Transfer Price Currency Conversion Override Extension overrides the default currency conversion attributes
defined in the cross-charge implementation options for the business unit.
Related Topics
• Project Business Unit Cross-Charge Options: Critical Choices
• Transfer Price Determination Extension
• Transfer Price Override Extension
• Transfer Price Currency Conversion Override Extension
Contract Components for Internal Billing: How They Work

Together


504



Receivables.


Note
Related Topics
• Project Components for Internal Billing: How They Work Together
• Why can't I see the internal billing details on a contract?
Project Components for Internal Billing: How They Work

Together
505
Invoice Formats
Restriction

• Bill rate
• Burden rate
• Transfer price

Receiver Project
Provider Project
Related Topics
• Contract Components for Internal Billing: How They Work Together
506
Managing Transfer Price Rates: Examples

Use these examples to understand how to configure cross-charge options on bill plans and revenue plans to achieve various
interproject and intercompany billing scenarios.
One Cross-charge Rule or Rate, One Provider Business Unit, Any

Receiver Business Unit, All Projects
To share one cross-charge rule or rate between one provider business unit and any receiver business unit, and all projects
associated with the contract, configure your contract billing information as follows:
Bill Plan Bill Rate Schedule
Bill Plan 1 Assign the bill rate schedule you want to use for the
contract (provider) business unit to this bill plan.

One Cross-charge Rule or Rate, One Provider Business Unit, One

Receiver Business Unit, All Projects
To share one cross-charge rule or rate between one provider and receiver business unit, and all projects associated with the
contract, configure your contract billing information as follows:
Bill Plan Bill Rate Schedule
provider business unit to this bill plan.

receiver business unit to this bill plan.

Note
All contract lines associated with the receiver
projects can use this bill plan.

Override a Cross-charge Rule or Rate, One Provider Business Unit,

One Receiver Business Unit, One Project
To override a cross-charge rule or rate between a provider and receiver business unit for one project, configure your contract
billing and contract line details as follows:
507
Bill Plan Schedules and Overrides Associated Projects
Bill Plan 1 Create a rate override for the Project level

contract line associated with the
receiver project.


One Receiver Business Unit, Task
If a resource is assigned to multiple roles and has more than one rate on a project, you may need to create an override at
the project task level. To override a cross-charge rule or rate between a provider and receiver business unit, for the task on a
specific project, configure your contract billing and contract line details as follows:
Bill Plan 1 Create a job rate override for the Task level
contract line associated with the
receiver project.


One Receiver Business Unit, Resource
If you are invoicing for a contractor, you may want to create an override at the resource level. To override a cross-charge rule
or rate between a provider and receiver business unit, for a specific resource on a project, configure your contract billing and
contract line details as follows:
Bill Plan 1 Create a person rate override for Task level

the contract line associated with
the receiver project.

Project Business Unit Cross-Charge Options: Critical Choices

Oracle Fusion Projects provides two methods to process cross-charge transactions.
• Borrowed and Lent Accounting: Creates accounting entries that move an amount equal to the transfer price
between the provider and receiver organizations within a legal entity. There is no formal internal invoice created with
this method. Costs or revenue are shared based on transfer price rules.
Use the Borrowed and Lent processing method to apply cross-charge transactions within a business unit or
between business units.
• Intercompany Billing: Enables the provider organization to present a formal invoice based on the transfer price to the
receiver organization and receive payment for services rendered and materials supplied. You can use this processing
method between legal entities.
508
You must set up the contract business unit to use the Intercompany Billing processing method.
This section describes the project business unit options for setting up cross-charge transactions for sharing costs and
revenue within and between business units in the same legal entity.
Transfer Price Currency Conversion

Select the date type, either transaction date or project accounting date, and rate type that the system uses by default to
determine the conversion rate to convert the transfer price amount from the transaction currency to the ledger currency.
You can override the default values by using the Transfer Price Currency Conversion Override extension.
Cross-Charge Transactions Within a Legal Entity

The method of creating cross-charge transactions can be different for transactions within a business unit than the method
used across business units. You can choose either the Borrowed and Lent Processing method of creating cross-charge
transactions, or specify that no cross-charge transactions will be created.
The processing method that you specify for cross-charge transactions between business units is the default method used
between the provider business unit and any other receiver business unit. You can override the default processing method for
specific receiver business units.
Note
If you delete the override of the default processing method for a specific receiver business unit, you must manually
adjust transactions to reflect the deleted controls.
FAQs for Manage Transfer Price Rules

What's a transfer price rule?
A rule to calculate the transfer price of cross-charge transactions. The key aspects when you define the rule are as follows:
• Type of transaction to which the rule applies: labor or nonlabor
• Basis for the cross-charge transaction: raw cost, burdened cost, or revenue amount
• Method used to calculate the transfer price: rate schedule, burden schedule, or no further adjustment
• Markup or discount percentage to apply to the transfer amount calculated by the rule
• Applicable date range for the rule
Manage Transfer Price Schedules
Transfer Price Schedules: Explained

Transfer price schedules contain the rules to determine the transfer price amount for transactions charged from a provider
organization to a receiver organization. You create different transfer price schedules to use for various combinations of legal
entities, business units, and organizations. You can create different schedules to use different rules for various projects and
509
tasks between the same pairs of provider and receiver organizations. For example, you can define one schedule that contains
the rules for capital projects and another for contract projects.
Before you set up transfer price schedules, you must set up organizations and transfer price rules.
Transfer Price Schedule Lines

Transfer price schedule lines contain details about the provider and receiver organization, labor transfer price rule and markup
or discount percentage, nonlabor transfer price rule and markup or discount percentage, and amount type.
A transfer price schedule can contain provider and receiver organizations from any organization classification that is relevant
to projects. The available organization classifications are determined at implementation when setting up organization
hierarchies and classifications. If you do not select a receiver organization, the transfer price schedule applies to any receiver
organization that receives transactions from the specified provider organization.
A labor rule is valid transfer price rule with a type of labor. A nonlabor rule is a valid transfer price rule with a type of nonlabor.
A transfer price schedule must contain either a labor or nonlabor rule, or both. You can assign a markup or discount
percentage to each transfer price rule to apply to the transfer price amount that the rule calculates.
You assign cost transfer or revenue transfer as the amount type for the transfer price calculation.
Transfer Price Schedule Hierarchy

A transfer price schedule should be determined based on whether the cross-charge transaction is processed using the
borrowed and lent processing method or the intercompany billing method. If you use the borrowed and lent processing
method, a transfer price schedule should be assigned to the receiver task or the project. If you use the intercompany billing
method, the bill and the revenue plan can have a transfer price schedule.
Note
The interproject billing method does not use transfer price calculation logic. Only the billing methods based on bill
rate schedule or burden rate schedule are allowed for interproject billing.
You can define a transfer price schedule at any organization level and legal entity level. Oracle Fusion Projects uses the
following logic to identify the appropriate schedule line:
1. If a transfer price schedule line exists for the provider organization (the project expenditure organization) and the
receiver organization (the project and task owning organization), then the corresponding rule is used to calculate the
transfer price.
Note
The project expenditure organization hierarchy is defined in the implementation options for the provider
business unit. The project and task owning organization hierarchy is defined in the implementation
options for the receiver business unit.
2. If a schedule line is not found in the previous step, the application checks for a line with the provider organization
and a receiver parent organization.
If the receiver organization has multiple intermediate parents and schedule lines are defined for more than one of
the parents, the schedule line defined for the lowest level parent takes precedence over schedule lines defined for
parents higher in the organization hierarchy.
3. If a schedule line is not found in the previous step, the application checks for a line with the provider parent
organization and receiver parent organization.
If the provider organization has multiple intermediate parents and schedule lines are defined for more than one of
the parents, the schedule line defined for the lowest level parent takes precedence over schedule lines defined for
parents higher in the organization hierarchy.
510
Note
If there is a schedule line with only a provider organization, and another schedule line with both provider
and receiver organizations, the application gives precedence to the schedule line with both provider and
receiver organizations.
If there is a schedule line with only a provider organization, and another schedule line with the provider
organization and the receiver parent organization, the application gives precedence to the schedule line
with the provider organization and the receiver parent organization.
4. If a schedule line is not found in the previous step, the application checks for the default line for the transfer price
schedule.
5. If a schedule line is not found in the previous step, the process results in an error.
Related Topics
• Project Business Unit Cross-Charge Options: Critical Choices
• Setting Up Organizations for Oracle Fusion Project Portfolio Management: Worked Example
FAQs for Manage Transfer Price Schedules

What happens if I change a transfer price rule or transfer price schedule?
The revised transfer price rule and schedule is applicable to unprocessed transactions only. To change a previously
processed transaction, you must adjust the expenditure item.
511
Implementing Project Financial Management Project Billing Configuration: Define Customer Billing
40 Project Billing Configuration: Define Customer

Billing Configuration for Project Billing
Manage Transaction Sources
Managing Transaction Numbering: Points to Consider

Use the various options on the transaction source assigned to a transaction to manage your transaction numbering
requirements.
There are these points to consider when defining transaction numbering for transactions assigned to specific transaction
sources:
• Defining Document Sequences
• Using Automatic Transaction Numbering
• Copying Document Numbers to Transaction Numbers
• Allowing Duplicate Transaction Numbers
• Using the Credit Memo Transaction Source
Defining Document Sequences

If necessary, define document sequences to assign unique numbers to each transaction, in addition to the transaction
number automatically assigned by Oracle Fusion Receivables.
Using Automatic Transaction Numbering

To automatically number new transactions you create using a transaction source, enable the Automatic transaction
numbering option and enter a number in the Last Number field.
For example, to start numbering transactions with 1000, enter a last number of 999. Receivables automatically updates the
Last Number fields on transaction sources, so you can review the transaction source later to see the last transaction number
that was generated.
Note
The last transaction number on the transaction source is an approximation only, due to caching.
You can use automatic transaction numbering with both Imported and Manual transaction sources.
Copying Document Number to Transaction Number

If you are using document sequences and you want to use the same value for both the document number and the
transaction number for transactions assigned to a transaction source, enable the Copy document number to transaction
number option.
If you are using Gapless document sequences, you should enable this option if you require gapless transaction numbering.
This ensures that transaction numbers are generated sequentially and that there are no missing numbers.
512
Allowing Duplicate Transaction Numbers

Enable the Allow duplicate transaction numbers option to allow duplicate transaction numbers within a transaction
source.
You cannot use this option with automatic transaction numbering.
Using the Credit Memo Transaction Source

Assign a credit memo transaction source to an invoice transaction source, if you want to number credit memos differently
from the invoices that they credit.
Related Topics
• Document Sequences: Explained
Sales Credits on Imported Transactions: Explained

During AutoInvoice processing, whether you must provide sales credit information on imported transaction lines depends on
the settings of the Allow sales credits option on the transaction source and the Require salesperson system option.
These are the requirements for passing sales credit information on imported transaction lines:
• If the Require salesperson system option and the Allow sales credits option on the transaction source are both
enabled, you must provide sales credit information.
• If the Require salesperson system option is not enabled and the Allow sales credits option on the transaction
source is enabled, you can provide sales credit information, but it is not required.
• If the Require salesperson system option is enabled and the Allow sales credits option on the transaction source
is not enabled, you must provide sales credit information.
• If neither the Require salesperson system option nor the Allow sales credits option on the transaction source are
enabled, you cannot provide sales credit information. AutoInvoice ignores any values that you pass.
Validating Imported Transactions: How It Works

Use the AutoInvoice Options and Import Information regions of an Imported transaction source to define how AutoInvoice
validates imported transaction lines assigned a particular transaction source.
You do not have to pass values for all of the fields that are referenced in the transaction source. If you do not want
AutoInvoice to pass certain data, then where available you can set the related option to None.
Note
Even if you set a transaction source data option to None in order not to import this information into the interface
tables, AutoInvoice can still validate and reject transaction lines with invalid data.
Settings That Affect the Validation of Imported Transactions

These settings affect the validation of imported transactions:
• Invalid Line field: Indicate how AutoInvoice handles imported transactions with invalid lines by selecting either Reject
Invoice or Create Invoice.
◦ If you select Reject Invoice, AutoInvoice does not import this transaction or any of its lines into the interface
tables.
513
◦ If you select Create Invoice, AutoInvoice creates a transaction with valid lines only. For example, you import an
invoice with three invoice lines and one of the lines is invalid. AutoInvoice creates the invoice with only the two
valid lines and rejects the invalid line. You can use the Edit Transaction page to add the rejected line.
• Accounting Date in a Closed Period field: Indicate how AutoInvoice handles imported transactions that have lines
in the interface lines table that are in a closed period.
◦ Select Adjust to have AutoInvoice automatically adjust the accounting dates to the first accounting date of the
next open or future enterable period.
◦ Select Reject to reject these transaction lines.
• In the Import Information subregions, where applicable select Number, Value, Segment or ID for each option to
indicate how AutoInvoice validates information.
◦ Select Number to import a record into the interface tables using its assigned number.
◦ Select Value to import a record into the interface tables using its actual name.
Note
Use Value if you intend to use the transaction source to import data from a non-Oracle system.
◦ Select Segment to use the flexfield segment.
◦ Select ID to use the internal identifier of the record.
• Select Amount or Percent to indicate how AutoInvoice validates Sales Credits and Revenue Account Allocations on
transaction lines.
How Imported Transactions Are Validated

AutoInvoice validates imported data based on the settings of the applicable Imported transaction source. Transactions that
fail validation appear in the Import AutoInvoice Validation report.
AutoInvoice ensures that certain column values agree with each other. These values can be within an interface table or
multiple interface tables. For example, if the transaction source indicates not to use a revenue scheduling rule, AutoInvoice
ignores any values passed for invoicing rule, revenue scheduling rule, and revenue scheduling rule duration.
AutoInvoice performs these validations on transaction lines with revenue scheduling rules:
• Requires that these transactions also include an invoicing rule, if you import transactions that use revenue scheduling
rules.
• Rejects lines, if the revenue scheduling rule has overlapping periods.
• Rejects lines, if all of the accounting periods do not exist for the duration of the revenue scheduling rule.
Related Topics
• Why did AutoInvoice reject transactions?
514
FAQs for Manage Transaction Sources

What do I create before creating transaction sources?
You may want to create certain records before creating your transaction sources.
You can optionally create these objects for all transaction sources:
• Transaction types: Define the transaction types that you want to appear by default on transactions assigned to your
transaction sources.
• Invoice transaction flexfield: Define the reference information that you want to capture in the invoice transaction
flexfield and display on imported transactions, such as a purchase order number.
• Credit memo transaction source: Define a transaction source for credit memos before you define a transaction
source for invoices. Use this transaction source to number the credit memos created against invoices differently from
the invoices they are crediting.
You can optionally create these objects for Imported transaction sources:
• AutoInvoice grouping rule: Define the grouping rule to appear by default on imported transaction lines.
• AutoInvoice clearing account: Define an AutoInvoice clearing account, if you intend to enable the Create clearing
option. AutoInvoice puts any difference between the revenue amount and the selling price times the quantity for a
transaction into this account.
How can I manage credit memos with transaction sources?

Special conditions may apply to the creation of transaction sources for credit memos.
Review these considerations for transaction sources assigned to credit memos:
• Define Manual transaction sources for credit memos created by the credit memo request approval process.
• Enable the Copy transaction information flexfield to credit memo option on Manual transaction sources used
for credit memos, to copy the invoice transaction flexfield reference information to the credit memo that is crediting
the invoice.
• Define and assign transaction sources for credit memos to transaction sources for invoices, if you want to number
the credit memos created against invoices differently from the invoices they are crediting.
What happens if I don't enter an AutoInvoice grouping rule?

Assign the AutoInvoice grouping rule to Imported transaction sources that AutoInvoice uses to group imported transaction
lines.
If you do not assign a grouping rule to an Imported transaction source, AutoInvoice uses the following hierarchy to determine
which rule to use:
1. Grouping rule assigned to the transaction source of the transaction line.
2. Grouping rule assigned to the bill-to customer site profile of the transaction line.
515
3. Grouping rule assigned to the bill-to customer profile of the transaction line.
4. Grouping rule assigned to system options.
What happens if I don't create a clearing account?

If you do not use an AutoInvoice clearing account and enable the Create clearing option on the transaction source,
AutoInvoice requires that the revenue amount be equal to the selling price times the quantity for all of the transactions it
processes. AutoInvoice rejects any transaction line that does not meet this requirement.
516
Implementing Project Financial Management Project Billing Configuration: Define Taxes for Rapid
Implementation
41 Project Billing Configuration: Define Taxes for

Rapid Implementation
Define Tax Configuration: Overview

Oracle Fusion Tax provides a single-point solution for managing your transaction and withholding tax requirements. In the
Define Tax Configuration activity, you can manage the entire configuration and maintenance of tax content.
Oracle Fusion Tax:
• Uniformly delivers tax services to all Oracle Fusion application business flows through one application interface
• Provides a single integration point for third-party tax products and services
• Is configurable and scalable for adding and maintaining country-specific 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:
• Both simple and complex country-specific tax legislation
• Cross-border transactions, including exports and Intra-European Community transactions
• Intercompany transactions
• Local compliance requirements for recording and reporting
• Continual changes to tax legislation, such as:
◦ New taxes
◦ Local law changes
◦ Special tax rates
◦ Special exceptions for products and customers
Task Lists
The Define Tax Configuration activity contains the following task lists
• Define Tax Configuration: Use these tasks to create a basic tax configuration for each of your tax regimes.
517
Implementation
• Define Advanced Tax Configuration: Use these tasks to configure optional tax setup that addresses more complex
tax requirements, such as exceptions to standard tax calculations.
Defining Tax Configuration for Transaction Taxes:

Critical Choices
With Oracle Fusion Tax, you can model your transaction tax requirements according to the needs of local and international
tax requirements. To determine how to set up your tax configuration, you must first analyze your requirements.
Analyzing Your Transaction Tax Requirements

The following table represents key decisions that you must make when you analyze your transaction tax requirements and
use Oracle Fusion Tax and other Oracle Fusion applications to implement a solution.
Question Consideration Impact to Tax Configuration
Who am I? You must first answer questions

about yourself and your relationship
to the legal and regulatory agencies
that enable you to operate in one or
more counties.

Where do I have operations and Identify the countries: Use Oracle Fusion Legal Entity
businesses? Configurator to capture information
• Which you operate in about your legal entities and legal
registration.
• Where you are legally
registered
• Where you have subsidiary

companies that are legally
registered or have a legal
presence
What taxes am I subject to? Analyze your tax environment for Set up your tax regimes, taxes, and
each of the countries in which you tax jurisdictions according to the
operate. tax requirements for each country.

What are the operations and Consider the types of operations Use the classifications feature to
businesses that I have? and businesses in which you are categorize or classify your first
engaged and the countries where parties under various classification
you have legal entities or reporting schemes.
units. In analyzing your operations, you
The following may impact your can associate the three main
taxability: classifications of a transaction to:
• The type of industries that • What you do: Use transaction

you work under, for example, fiscal classifications.
mining, telecommunications,
and pharmaceuticals
518
Implementation
• The kind of operations • What products you buy
in which you engage, or sell: Use product fiscal
for example, trading, classifications.
manufacturing, and services
• Who your customers and
• The scale of your operations, suppliers are: Use party fiscal
for example, your turnover, classifications.
company size, and growth
What do I do? Identify and classify the Use Oracle Fusion Tax to create
transactions that you enter into. fiscal classifications to classify and
categorize your transactions in
For example, do you primarily sell a common manner across your
physical goods? If you do, do you organization. Use these fiscal
manufacture them, or do you buy classifications in tax rules to obtain
and sell them without additional the appropriate tax result.
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 Where Oracle Fusion Inventory
buy and sell as they impact the is installed use the Inventory
taxes to which you are subject. Catalog feature with Oracle Fusion
Tax product fiscal classifications
For example, you must register for, and intended use functionality to
and therefore collect and remit, classify the taxable nature and
service taxes only if you provide intended use of the items. You
taxable services. If you manufacture can then define tax rules using
goods for export, you may not be these classifications to obtain the
subject to taxes on the purchases appropriate tax result.
that are part of the manufacture of
such goods. Define product category and
noninventory-based intended use
fiscal classifications to address
classification needs for transactions
that do not use inventory items.

519
Implementation
Who are my customers and Determine the types of customers Use the party classifications feature
suppliers? and suppliers with whom you do to categorize or classify your
business. They can impact the customers and suppliers. You can
taxes to which you are subject use these classifications in your tax
or the tax status or tax rate that rules to derive the appropriate tax
applies. result.

For example, let's say that you are You create a party fiscal
a company in the UK that supplies classification by assigning an
physical goods to another country Oracle Fusion Trading Community
that is also a member of the Model class category to a party
European Union. The transaction fiscal classification type code that
rate for UK VAT is dependent on you define. The Trading Community
whether the customer is registered Model class codes defined under
for VAT in the country to which the the class category become fiscal
supply is made. classification codes belonging to
the party fiscal classification type.
You can create a hierarchy of party
fiscal classification types to reflect
the levels of codes and subcodes
within the Trading Community
Model classification.

Scope Values for Define Tax Configuration Task List:

Explained
The purpose of scope is to define the parameters of your implementation project by setting the context of a task list during
initial configuration. When exporting setup data based on setup migration services, the scope values serve as parameters to
control the data selected for export to the respective configuration package.
The foundation tax setup is an incremental setup where each step of the foundation configuration builds on the previous step.
The task list is organized sequentially to ensure that you perform setup tasks in the order required. You can define scope
values at incremental steps in the implementation project to pass to subsequent tasks to ensure:
• Continuity
• Ease of setup
Scope is a valuable tool when implementing, but tax scope values are not a required element of the implementation and you
do not need to define them.
Defining Scope
When implementing transaction or withholding tax, you can define scope values for taxes, tax jurisdictions, tax statuses, tax
rates, tax recovery rates, and tax rules. To set scope, you can:
• Select and add multiple values
• Create a new value
520
Implementation
When you select the scope value, that value defines 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 attributes on the Manage Tax page. That tax
regime's attributes are also populated in the Create Tax page. The same logic applies to the next step in the tax setup.
Scope Values
The following table identifies where you define the scope value in the Define Tax Configuration and Define Advanced Tax
Setup task lists:
Where Scope is Defined Scope Values
Manage Taxes Tax regime

Manage Tax Rates and Tax Recovery Rates • Tax regime

• Tax
• Tax status
Manage Tax Rules • Tax regime

• Tax
Manage Tax Jurisdictions • Tax regime

• Tax
Manage Tax Statuses • Tax regime

• Tax
Foundation Tax Configuration: Points to Consider

Use Oracle Fusion Tax to set up and maintain your transaction and withholding tax requirements in all geographic locations
where you do business. Foundation tax configuration refers to a set of tax setup components that you use to satisfy your tax
requirements.
At transaction time, Oracle Fusion Tax uses your tax configuration to determine the taxes that apply to each transaction and
to calculate the transaction tax and withholding tax amounts.
Foundation tax configuration components consist of:
• Tax regimes
• Taxes
521
Implementation
• Tax jurisdictions
• Tax statuses
• Tax rates
Foundation Tax Configuration

Complete the setup tasks to create a basic tax configuration for each of your tax regimes. A foundation tax configuration
contains the data applicable to the taxes belonging to a tax regime. The following table describes the appropriate levels
of specifying setup options for foundation tax components and provides a Canada Goods and Services Tax (GST) and
Harmonized Sales Tax (HST) example for each component.
Component Appropriate Level to: Typically, Not Canada GST and HST
Appropriate Level to: Example
Tax Regime • Share tax content • Define CA GST & HST

among legal configuration
entities and owner tax options.
business units.
• Define application
• Enable partner tax options.
integration.
• Define party tax
• Associate fiscal profiles.
classifications.
• Define tax reporting

types and codes.
• Define features to
influence setup
task list.
Tax • Enable controls • Share tax content. • CA GST

to influence tax
behavior. • Define integration • CA HST
with partners.
• Specify defaults
that are commonly
applicable.
• Define applicability
tax rules.
• Define customer
exemptions.
• Specify party
registrations.
Tax Jurisdictions • Define location- Specify tax rule defaults. • CA Alberta GST
based tax rates.
522
Implementation
Component Appropriate Level to: Typically, Not Canada GST and HST
Appropriate Level to: Example
• Define customer • CA BC HST
exemptions and
rate exceptions.
Tax Status • Define common • Specify tax rule • GST Standard

rules for tax rates. defaults.
• HST Standard
• Drive reporting • Define customer
needs. exemptions. • HST Reduced
• Allow manual • Specify party

override to tax registrations.
rates.
Tax Rates • Define tax rates by • Define customer • CA GST Standard

effective periods. exemptions.
• CA GST Reduced
• Specify tax account • Define applicability
variations. tax rules. • CA GST Exempt
• Define tax rate • Define taxable • CA HST Standard

exceptions. calculation
formulas.
• Define tax recovery
rates. • Share tax content.
Tax Rule Configuration: Points to Consider

Create a simple tax model using tax rule defaults that you define in setting up your foundation tax configuration. You can also
create tax rules for your complex tax requirements that consider each tax requirement related to a transaction before making
the final tax calculation.
When running the tax determination process, Oracle Fusion Tax evaluates, in order of priority, the tax rules that you defined
against the foundation tax configuration setup and the details on the transactions. If the first 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.
Tax Rule Configuration

The complexity of tax rule setup falls into three general categories:
• No tax rules required

• Simple tax rule regimes
• Complex tax regimes
523
Implementation
This table presents the scenarios and actions associated with each of these categories.
Category Scenario Action
No tax rules required The tax authority levies tax on all For the tax, define tax rule defaults
sales and purchase transactions for the tax status, tax rate, and tax
at the same rate. Neither tax recovery rate.
applicability nor the tax rates and
recovery rates vary by the: The tax determination process uses
the tax rule defaults to determine
• Parties to the transaction the tax.

• Products or services in the
transaction
• Business processes involved

in the transaction
Simple tax rule regimes The tax authority levies tax on your Create a simple set of rules, for
transactions at the same rate, example, to identify place of supply
with a simple set of identifiable and tax registration, and use the
exceptions. The exceptions either tax rule default values for the other
apply to: processes.

• One part of the transaction The tax determination process
only, such as to certain uses the tax rules and the tax rule
parties. defaults to determine the tax.

• A combination of parties,
products, and transaction
processes that you can
summarize in a simple way.
524
Implementation
Category Scenario Action
Complex tax regimes Tax regimes in certain countries Set up tax rule to define the logic
require a complex logic to necessary to identify each step of
determine the applicable taxes and the tax determination process.
rates on a transaction. Both tax
applicability and tax rates can vary, The tax determination process uses
for example, by: the tax rules to determine the tax.

• Place of origin
• Place of destination
• Party registration
• Tax status
• Service
• Combination of factors
In some cases, the taxable amount

of one tax may depend upon the
amount of another tax on the same
transaction. And in rare cases, the
tax amount itself may depend on
the tax amount of another tax.
Tax Account Configuration: Explained

Set up default tax accounts for the taxes in a tax regime to post the tax amounts derived from your transactions. The tax
accounts you define for tax serve as default accounting information for tax rates and tax jurisdictions. You can override the
defaulted accounts. Configure the tax recoverable or liability account for the tax recovery rate. Accounts assigned to the tax
rate and recovery rate are used when the taxes are applicable to the transaction.
Set up tax accounts for a primary ledger or in combination with a business unit. The calculated tax amounts are posted to
the accounts specified for a business unit. If those accounts are not available, tax accounts defined for the primary ledger are
used. These are default accounts and the actual accounts that are used for accounting depend on the subledger accounting
configuration.
For a tax, either assign new tax accounts or use accounts from an existing tax. This depends on the option selected in the
Tax Accounts Creation Method attribute for the tax. If you choose to use accounts from an existing tax, specify another
tax as the source tax. All the tax account details that you set up at the source tax level are copied into the Tax Accounts
region as read only values. You cannot edit the details or create new records.
Tax Accounts
Define tax accounts for a tax, tax rate, and tax jurisdiction. Tax accounts are:
• Tax Expense: A Payables tax account that records tax amounts from invoice distributions; or a Receivables
tax account that record net changes generated by adjustments, earned and unearned discounts, and finance
charges. Receivables activities such as discounts and adjustments reduce the receivable amount, and are therefore
considered an expense. This occurs only if the adjustment type has tax handling.
525
Implementation
• Tax Recoverable or Liability: An account that records tax recovery amounts or relieves tax liability amounts. If
you set up recovery rates for a tax that you also intend to self-assess, then define a tax recovery account for the
associated recovery rates and a tax liability account for the associated tax rates.
Note
If you intend to use different accounts for tax recovery and liability then set up the recovery account for
the tax recovery rate. This account is used to debit the recoverable tax amount while the account on the
tax rate is used to account for tax liability.
• Interim Tax: An account that records interim tax recovery or liability before the actual recovery or liability arises on a
payment of an invoice. You must set up an interim tax account for taxes and tax rates that have a deferred recovery
settlement.
• Accounts for Receivables activities:
◦ Finance Charge Tax Liability: An account that records tax amounts on finance charges that are used as a
deduction against overall tax liability.
◦ Nonrecoverable Tax Accounts: Accounts that record tax amounts on earned and unearned discounts and
adjustments that you cannot claim as a deduction against tax liability.
◦ Expense and Revenue Accounts: Accounts that record net changes generated by adjustments, earned and
unearned discounts, and finance charges. Receivables activities such as discounts and adjustments reduce
the receivable amount, and are therefore considered an expense.
Related Topics
• Accounting for Tax on Receivables Transactions: Explained
• Accounting for Payables Transactions: Explained
Manage Tax Regimes
Regimes to Rates: Explained

Regime to rate setup contains the details of a tax regime, including all taxes, tax jurisdictions, tax statuses, and tax rates. You
can update existing records or create new records at any point in the tax regime hierarchy.
Regime to rate setup tasks include:
• Tax regimes
• Taxes
• Tax statuses
• Tax rates
526
Implementation
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, fiscal classifications, and optionally, registrations, to one
or more taxes. For example, in the United States create a Sales and Use Tax tax regime to group taxes levied at the state,
county, and district levels.
The tax regime provides these functions:
• Groups similar taxes together
• Designates the geography within which taxes apply
• Applies as defaults the settings and values that you define for each tax in the tax regime
• Defines for which taxes the configuration options apply and a specific subscription option applies
• Provides a single registration for all taxes associated with the tax regime
• Defines the use of fiscal classifications as follows:
◦ Transaction fiscal classifications
◦ Product fiscal classifications
◦ Party fiscal classifications
The common tax regime setup is one tax regime per country per tax type, with the tax requirements administered by a
government tax authority for the entire country. There are also cases where tax regimes are defined for standard geographical
types or subdivisions within a country, such as a state, province, country, or city. In these cases, you base the tax regime on
the Oracle Fusion Trading Community Model standard geography.
There are more rare cases where a tax regime is based on disparate parts of a country or more than one country. In these
cases, you can create one or more tax zones and set up tax regimes for these tax zones. You can also set up a tax regime as
a parent tax regime to group related tax regimes together for reporting purposes.
You must set up a tax regime before you set up the taxes in the tax regime. Some tax regime values appear as defaults on
the taxes that belong to the tax regime in order to help minimize tax setup.
You must associate a tax regime with all of the first-party legal entities and business units that are subject to the tax
regulations of the tax regime. You can set up tax configuration options when you create or edit a tax regime or when you
create or edit a first-party legal entity tax profile. Both setup flows appear and maintain the same party and tax regime
configuration options.
Taxes
Set up details for the taxes of a tax regime. Each separate tax in a tax regimes includes records for the tax statuses, tax rates,
and tax rules that are used to calculate and report on the tax. Oracle Fusion Tax applies as defaults tax information from the
tax regime to each tax that you create under a tax regime. You can modify this information at the tax level according to your
needs, as well as add additional defaults and overrides. For tax rule defaults, specify values that apply to the majority of your
transactions. Use tax rules to configure exceptions to the tax rule defaults.
Identify what taxes you must define. Each tax appears as a single tax line on a transaction. If you need to show or report
more than one tax line per transaction line on a transaction, then you should set up more than one tax. For example, for US
Sales and Use Tax you would define a tax for each state, county, and city.
You can create a new tax, or create a tax that is based on an existing tax within the tax regime. You do this to minimize
setup by sharing tax jurisdictions and tax registrations. When you create a new tax based on an existing tax, the attributes
527
Implementation
that remain constant for all taxes derived from the source tax are not available for update. Attributes that are copied and are
display only include:
• Tax regime
• Tax
• Geography information
• Tax jurisdiction settings
Note
The enable tax settings are not selected, in the same way that they are not selected when you access the Create
Tax page.
You can enable a tax for simulation or for transactions only after you have completed all of the required setup.
Tax Jurisdictions
Set up tax jurisdictions for geographic regions or tax zones where a specific tax authority levies a tax. A tax jurisdiction
specifies the association between a tax and a geographic location. At transaction time, Oracle Fusion Tax derives the
jurisdiction or jurisdictions that apply to a transaction line based on the place of supply. You must set up at least one tax
jurisdiction for a tax before you can make the tax available on transactions.
You also use tax jurisdictions to define jurisdiction-based tax rates. A tax jurisdiction tax rate is a rate that is distinct to a
specific geographic region or tax zone for a specific tax. You can also create multiple jurisdictions at once using the mass
create functionality for taxes that relate to specific Trading Community Model geographic hierarchies. For example, create a
county jurisdiction for every county in the parent geography type of State and in the parent geography name of California.
The tax within a tax jurisdiction can have different rates for the parent and child geographies. For example, a city sales tax rate
can override a county rate for the same tax. In this case, you can set up an override geography type for the city and apply a
precedence level to the city and county tax jurisdictions to indicate which tax jurisdiction takes precedence.
In addition, in some cities a different city rate applies to the incorporated area of the city, called the inner city. In these cases,
you can set up an inner city tax jurisdiction with its own tax rate for the applicable customers and receivables tax. Inner city
tax jurisdictions are often based on postal code groupings.
Tax Statuses
Set up the tax statuses that you need for each tax that you create for a combination of tax regime, tax, and configuration
owner. A tax status is the taxable nature of a product in the context of a transaction and specific tax on the transaction. You
define a tax status to group one or more tax rates that are the same or similar in nature.
For example, one tax can have separate tax statuses for standard, zero, exemptions, and reduced rates. A zero rate tax
status may have multiple zero rates associated with it, such as Intra-EU, zero-rated products, or zero-rated exports.
You define a tax status under a tax and a configuration owner, and define all applicable tax rates and their effective periods
under the tax status. The tax status controls the defaulting of values to its tax rates.
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 identifies. For tax jurisdictions, set up tax rate records to identify the tax rate variations for a specific tax
within different tax jurisdictions. For example, a city sales tax for a state or province may contain separate city tax jurisdictions,
each with a specific tax rate for the same tax.
You can also define tax recovery rates to claim full or partial recovery of taxes paid.
528
Implementation
You can define tax jurisdiction and tax status rates as a percentage or as a value per unit of measure. For example, a city may
charge sales tax at a rate of 8 percent on most goods, but may levy a duty tax with a special rate of 0.55 USD per US gallon
on fuel. Values per unit of measure are in the tax currency defined for the tax.
You define tax rate codes and rate detail information per rate period. Rate periods account for changes in tax rates over time.
A tax rate code can also identify a corresponding General Ledger taxable journal entry.
Tax Recovery Rates

Set up tax recovery rate codes for the recovery types identified on the taxes within a tax regime. A tax recovery rate code
identifies the percentage of recovery designated by the tax authority for a specific transaction. In Canada, where more than
one type of recovery is possible for a given tax, you must set up the applicable tax recovery rate codes for both the primary
and secondary recovery types that can apply to a transaction.
If you set the Allow tax recovery option for a tax within a tax regime, then you must set up at least one recovery rate for the
tax in order to make the tax available on transactions. If the recovery rate can vary based on one or more factors, including
the parties, locations, product or product purpose, then set up tax rules to determine the appropriate recovery rate to use
on specific transactions. At transaction time, Oracle Fusion Tax uses the recovery rate derived from the recovery tax rules, or
uses instead the default recovery rate that you define, if no recovery rate rules are defined or if no existing recovery rate rule
applies to the transaction.
Related Topics
• What's the minimum setup to enable a tax for transactions or simulation?
Minimum Tax Configuration: Explained

The minimum tax configuration to meet the basic tax requirements of your transaction and withholding taxes comprise of
defining a tax regime and associated taxes.
The two steps in defining the minimum tax configuration are:
1. Define tax regime: This step includes the tax regime definition as well as the subscription by the appropriate legal
entity or business unit.
2. Define transaction and withholding taxes: This step includes the basic tax definition, controls and defaults, direct
and indirect tax rule defaults, and tax accounts.
The following prerequisite setups must be completed for minimum tax configuration:
• First parties, such as legal entities and business units

• Tax geographies and zones
• Ledger and accounts
A legal entity tax profile is automatically created when a legal entity is defined in the implementation. Similarly, a business
unit tax profile is automatically created when a business unit is defined. For the business unit, indicate whether it uses the
subscription of the legal entity instead of creating its own.
Define Tax Regime

The first step includes the tax regime definition and subscription by an appropriate legal entity or business unit. While creating
your tax regime, you can minimize configuration and maintenance costs by creating content that can be shared by more than
one entity. For example, legal entities can subscribe to the shared reference data instead of creating separate and repetitive
data. If the subscribing legal entities have some variations in their setup, you can create override data to meet the specific
exceptions that are applicable to these organizations.
529
Implementation
Define Transaction and Withholding Taxes

The second step includes basic tax definition, such as:
• Geographic information
• Controls and defaults
• Direct and indirect tax rule defaults
• Tax accounts
The basic tax definition 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 satisfies 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 define 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 defined in the Rapid Implementation for General Ledger spreadsheet upload. You can override
these values.
Related Topics
• Configuration Options: Explained
Minimum Tax Configuration: Points to Consider

Define the minimum tax configuration setup to handle the majority of your tax requirements. As part of defining transaction
and withholding taxes, decide the direct and indirect tax rule defaults for the tax and set up the associated tax accounts.
For complex tax requirements, create tax rules that consider each tax requirement related to a transaction before making the
final tax calculation.
Setting Up Direct Tax Rule Defaults

The direct tax rule defaults are the default values for the direct tax rule types, which include:
• Place of supply
• Tax applicability
• Tax registration
• Tax calculation formula
530
Implementation
• Taxable basis formula
The following table describes the direct tax rule defaults and examples:
Direct Tax Rule Default Usage Example
Place of Supply Indicates the specific tax In Canada, the place of supply
jurisdiction where the supply of for GST is typically the ship-to
goods or services is deemed to location. To handle the majority
have taken place. of Goods and Services Tax (GST)
transactions, select Ship to as your
default place of supply.
Note
The corresponding place
of supply differs based on
the type of transaction. For
example, a place of supply
of Ship to corresponds
to the location of your
first-party legal entity for
Payables transactions. For
Receivables transactions,
Ship to corresponds to the
location of your customer
site.

Tax Applicability Indicates whether the tax is The GST in Canada is a tax that
typically applicable or not applies to the supply of most
applicable on transactions. property and services in Canada.
When you create the GST tax,
select Applicable as your default
tax applicability.
Tax Registration Determines the party whose tax With a direct default of bill-to party,
registration status is considered the tax registration of the bill-to
for an applicable tax on the party is considered. The application
transaction. stamps their tax registration
number onto the transaction, along
with the tax registration number of
the first-party legal reporting unit.

Tax Calculation Formula Represents the typical calculation A common formula,

of tax for a transaction line. STANDARD_TC, is predefined,
where the tax amount is equal
to the tax rate multiplied by the
taxable basis.
Taxable Basis Formula Represents the amount on which The following common formulas are
the tax rate is applied. predefined:

• STANDARD_TB: The taxable
basis is equal to the line
531
Implementation
Direct Tax Rule Default Usage Example
amount of the transaction
line.
• STANDARD_QUANTITY:
The taxable basis is equal to
the quantity of the transaction
line.
• STANDARD_TB_DISCOUNT:
The taxable basis is the line
amount of the transaction line
less the cash discount.
Note
Use the Manage Tax Rules task to define exceptions to the direct tax rule defaults you define for the tax.
Setting Up Indirect Tax Rule Defaults

The indirect tax rule defaults for a tax include:
• Tax jurisdiction
• Tax status
• Tax recovery rate
• Tax rate
The following table describes the indirect tax rule defaults and examples:
Indirect Tax Rule Default Usage Example
Tax Jurisdiction Indicates the most common Value-added tax (VAT) is applicable
geographic area where a tax is to the supply of most goods
levied by a specific tax authority. and services in Portugal. For the
tax PT VAT, create the default
tax jurisdiction as the country
of Portugal. To address specific
tax regions such as Azores
and Madeira, which have lower
VAT rates than Portugal, define
jurisdiction rates with different VAT
rates.

Tax Status Indicates the taxable nature of the If your operations primarily include
majority of your transactions. zero-rated transactions, select the
default tax status as Zero instead
of Standard. This setting facilitates
tax determination when multiple
532
Implementation
Indirect Tax Rule Default Usage Example
zero rates are defined to handle
different reporting requirements for
zero rate usage, such as intra-EU,
zero-rated products, or zero-rated
exports.
Tax Recovery Indicates the recovery rate to In Canada, both federal and
apply to each recovery type for provincial components of
each applicable tax on a purchase Harmonized Sales Tax (HST)
transaction. 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.

Tax Rate Specifies the default tax rate that HST in Canada is applied at a 13%
is applicable to the majority of your rate in most provinces that have
transactions associated with this adopted HST. The exceptions are
tax. You can create additional tax British Columbia where the rate
setup, such as jurisdiction rates, is 12% and Nova Scotia where
or create tax rules to set alternate the rate is 15%. To satisfy this
values as required. requirement:

• Define a single rate of 13%
with no jurisdiction.
• Define a 12% rate and

associate it with the British
Columbia jurisdiction.
• Assign a 15% rate to Nova

Scotia.
This minimizes the setup required

by creating an exception-based
setup.
Note
Use the Manage Tax Rules task to define exceptions to the indirect tax rule defaults you define for the tax.
Setting Up Tax Accounts

Set up tax accounts at the tax level. The application automatically copies the tax account combination to the tax rate
accounts or tax jurisdiction accounts that you create for the tax for the same ledger and optionally, the same business unit.
Any subsequent changes you make to existing tax accounts at the tax level aren't copied to the tax rate or tax jurisdiction
level.
Define tax accounts at any of the following levels. The defaulting option is only available at the tax level.
• Tax
• Tax jurisdiction
533
Implementation
• Tax rate
• Tax recovery rate
Note
When you create your tax, the tax recoverable account and tax liability account may be prepopulated from default
account values defined in the Rapid Implementation for General Ledger spreadsheet upload. You can override
these values.
Set up tax accounts for the following:
Account Description
Ledger and Business Unit The ledger and business unit for which you are creating
the tax accounts.

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 settlement. Once you set up
an interim tax account for this tax rate, you can't change
the recovery settlement to Immediate.
Tax Recoverable Account An account that records tax recovery amounts. If you
set up recovery rates for a tax that you also self assess,
then define a tax recovery account for the associated
recovery rates.

Tax Liability Account An account that relieves tax liability amounts. If you set
up recovery rates for a tax that you also self assess,
then define a tax liability account for the associated tax
rates.

Finance Charge Tax Liability An account that records the tax liability associated with
finance charges that is used as a deduction against
overall tax liability.

Nonrecoverable Tax Accounts Accounts that record tax amounts on earned and
unearned discounts and adjustments that you can't
claim as a deduction against tax liability.

Expense and Revenue Accounts Accounts that record net changes generated by
adjustments, earned and unearned discounts, and
finance charges. Receivables activities such as
discounts and adjustments reduce the receivable
amount, and are therefore considered an expense.

534
Implementation
Defining a Minimum Tax Configuration: Worked Example

The following example illustrates the minimum tax configuration setup to meet the basic requirements in Canada for the
Goods and Services Tax (GST). Set up a tax regime for both GST and Harmonized Sales Tax (HST). Create one recovery type
for the fully recoverable status of the transaction.
In Canada, GST is a tax that applies to the supply of most property and services in Canada. The provinces of British
Columbia, Ontario, New Brunswick, Nova Scotia, and Newfoundland and Labrador, referred to as the participating provinces,
combine their provincial sales tax with GST to create HST. Generally, HST applies to the same base of property and services
as the GST. Every province in Canada except Alberta has implemented either provincial sales tax or the HST. In countries like
Canada, some or all taxes on business transactions for registered companies are recoverable taxes.
The following table summarizes key decisions for this scenario:
What province does ABC Corporation do business in? Alberta

What taxes are applicable? GST

Do you want to set up tax accounts at the tax level? Yes

The tax implications in this scenario are:
• Five percent (5%) GST is applicable on the sale of goods in Alberta

• Neither the HST nor provincial sales tax applies in Alberta
• Place of supply for GST tax is generally based on the place of delivery or ship-to location.
To determine the GST tax in Alberta, perform the following steps:
1. Define the tax regime

2. Define the transaction taxes
3. Create the direct tax rule defaults
4. Create the indirect tax rule defaults
5. Enable the tax
Defining the Tax Regime

1. In the Setup and Maintenance work area, search for the Manage Tax Regimes task. Click Go to Task.
2. Click Create.
3. On the Create Tax Regime page, complete the fields as shown in this table:
Column Value
Tax Regime Code CA GST and HST

535
Implementation
Column Value
Regime Level Country

Country Canada

Start Date 1/1/01

Note
Consider your tax planning carefully
before entering 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.

Tax Currency CAD

Allow cross regime compounding Select

4. On the Configuration Options tab, select the party name that identifies either the legal entity or the business unit or
both for which you define the configuration options.
5. For the Configuration of Taxes and Rules, select the subscription that defines the configuration owner setup that
is used for transactions of the legal entity and business unit for this tax regime.
6. Enter the effective start date for this configuration option. Enter a date range that is within the date range of both the
party tax profile and the tax regime.
Defining the Transaction Taxes

1. In the Setup and Maintenance work area, search for the Manage Taxes task. Click Go to Task.
2. Click Create.
3. On the Create Tax page, complete the fields as shown in this table:
Column Value
Tax Regime Code CA GST and HST

Configuration Owner Global configuration owner

Tax CA GST

536
Implementation
Column Value
Geography Type Province

Parent Geography Type Country

Compounding Precedence 10

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 Select

Primary Recovery Rate Standard

Assigning the Tax Accounts

1. Navigate to the Tax Accounts tab and click Create.
2. Complete the fields as shown in this table:
Column Value
Primary Ledger CA Ledger

Business Unit CA Operations

Tax Recoverable Account 0001-1500-1100-1000

Tax Liability Account 0001-1500-1100-1000

Creating the Direct Tax Rule Defaults

1. Navigate to the Tax Rule Defaults tab and click Create.
537
Implementation
2. Complete the fields as shown in this table:
Column Value
Place of Supply Ship to

Tax Applicability Applicable

Tax Registration Ship-from party

Tax Calculation Formula STANDARD_TC

Taxable Basis Formula STANDARD_TB

Creating the Indirect Tax Rule Defaults

1. On the Tax Rules Defaults tab, select Tax Jurisdiction as your rule type and click Create Default.
2. On the Create Tax Jurisdiction page, complete the fields as shown in this table:
Column Value
Tax Jurisdiction Code CA Alberta

Geography Type Province

Geography Name AB

Set as default jurisdiction Select

Default Start Date 1/1/01


4. Select Tax Status as your rule type and click Create Default.
5. On the Create Tax Status page, complete the fields as shown in this table:
Column Value
Tax Status Code CA GST STD

538
Implementation
Column Value
Set as default tax status Select



7. Select Tax Recovery Rate as your rule type and click Create Default.
8. On the Create Tax Recovery Rate page, complete the fields as shown in this table:
Column Value
Tax Recovery Rate Code CA GST STD REC RATE

Recovery Type STANDARD

Rate Percentage 100

Effective Start Date 1/1/01

Set as Default Rate Select



10. Select Tax Rate as your rule type and click Create Default.
11. Complete the fields on the Create Tax Rate page as shown in this table:
Column Value
Tax Status Code CA GST STD

Tax Rate Code CA GST STD RATE

Tax Rate Type Percentage

Rate Percentage 5

Set as Default Rate Select

539
Implementation
Column Value

Enabling the Tax

1. On the Create Tax page, click the Enable tax for simulation option. This lets you verify the tax configuration using
the Tax Simulator.
2. Once you have verified your tax configuration with simulated transactions, click the Enable tax for transactions
option. This lets you use this tax in transaction processing.
For ABC's transactions in the province of Alberta, the following is determined by default:
◦ GST tax is applicable and is calculated at a percentage rate of 5%.
◦ 100% of the GST can be recovered.
Associated Taxes Setup for a Tax Regime: Explained

When you create a tax regime, you specify the options and defaults available to the taxes associated with the tax regime. You
also enable the features that are applicable to the tax regime and its taxes.
The options appearing in the Associated Taxes Setup Information region on the Edit Tax Regime page are a result of the
features enabled and the options you selected at the tax level. These options include:
• Allow multiple jurisdictions
• Allow tax recovery
• Allow tax exceptions
• Allow tax exemptions
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 did not select the option
in one of the taxes, then 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, you must enable the Multiple Jurisdictions feature at the tax regime level and then select the
Allow multiple jurisdictions option at the tax level. When you access the Edit Tax Regime page, Associated Taxes Setup
Information region for this tax regime, the Allow multiple jurisdictions option appears as selected.
Tax Regime Controls and Defaults: Points to Consider

A tax regime associates a common set of default information, regulations, fiscal classifications, and optionally, registrations, to
one or more taxes. Set up tax regimes in each country and geographical region where you do business and where a separate
tax applies.
The tax regime setup details include:
• Designating the geography to which taxes within a tax regime apply
• Defining the controls and defaults that apply to taxes and associated lower level information
540
Implementation
• Specifying configuration options and service subscriptions
Designating the Geography

The common tax regime setup is one tax regime per country per tax type, but you can also have tax regimes based on parts
of a country or more than one country. Select the regime level as:
• Country: The tax regime is applicable to a specific country.
• Tax zone: The tax regime is applicable to parts of a country or more than one country. Enter the tax geography type
and tax geography name associate with the group of countries or the tax zone that you want. The tax geography
type and tax geography name correspond to the tax zone type and tax zone respectively.
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 defined as a parent tax regime to group other nonparent tax regimes for reporting purposes.
Defining Controls and Defaults

Set tax-level controls to enable the options that you want to make available to the taxes in this tax regime. If necessary, you
can disable the options that you enable here for individual taxes within the tax regime. Enter default values for the taxes in this
tax regime. You can update the default values at the tax level. If you disable a controlled option at the tax regime level it is not
available as an option at the tax level.
The following table describes the defaults and controls available at the tax regime level.
Defaults Region
Field Description Default Derived Default Appears Controls

from on
Tax Currency The default None Tax None

currency of the
taxes within this
tax regime

Minimal The minimal unit None Tax None

Accountable Unit of currency that
is reported to the
tax authority, for
example, 0.05
GBP indicates
that 5 pence is the
minimal unit

Tax Precision A one digit whole None Tax None

number to indicate
the decimal place
for tax rounding

Tax Inclusion A method that None Tax None

Method describes whether
the line amount
includes tax or
excludes tax

541
Implementation
from on
Conversion Rate The specific None Tax None

Type exchange rate
table that is
used to convert
one currency
into another, for
example, the
Association of
British Travel
Agents exchange
rate used in the
travel industry

Rounding Rule The rule that None Tax None

defines how
rounding is
performed on a
value, for example,
up to the next
highest value,
down to the next
lower value, or to
the nearest value

Allow tax rounding Allow the override None Tax None

override of the rounding
defined on the
tax registration
records

Reporting Tax The default tax None • Tax None

Authority authority to whom
the tax reports are • Tax
sent registration

Collecting Tax The default tax None • Tax None

Authority authority to whom
the tax is remitted • Tax
registration
542
Implementation
from on
Default Settlement A lookup code to None Tax None

Option indicate whether
an input tax is
recovered when
an invoice is
recorded or only
when the invoice is
paid and whether
an output tax is
due for settlement
when the invoice
is issued or only
when the payment
is received against
it

Use legal Option that None Tax None

registration controls whether
number the tax registration
number is the
same as the
legal registration
number of the
party

General Controls Region

from on
Allow override and Option that None Tax None

entry of inclusive controls whether
tax lines you can override
and enter inclusive
or exclusive line
amounts

Use tax reporting Option that None None Controls whether

configuration controls whether you can enter
the tax reporting tax reporting
details are configuration
available on the details on the tax
first-party tax registration for this
registration record tax regime for your
for this tax regime first parties

Compounding Level Controls Region
543
Implementation
from on
Allow cross regime Option that None None Controls whether

compounding controls whether this tax regime
cross regime is compounded
compounding is based on the tax
needed for this tax calculated from
regime another tax regime

Compounding Defines the None None Controls the order

Precedence order in which in which taxes
taxes within the within tax regimes
compound tax are calculated
regimes need to
be calculated.
A tax within a
tax regime with
a lower value is
calculated first.

Important
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.
Specifying Configuration Options and Service Subscriptions

Set up configuration options to associate tax regimes with the parties in your company that have a tax requirement under
these tax regimes. You can set up tax configuration options when you create a tax regime or when you create a party tax
profile for a first-party legal entity or business unit. Both tax regime and party tax profile setup flows appear and maintain the
same party and tax regime association. Configuration options only apply to tax regimes directly linked to taxes and not to tax
regimes that are used to group other tax regimes.
Oracle Fusion Tax lets you use the tax services of external service providers for tax calculation of US Sales and Use Tax on
receivables transactions. The setup for provider services is called a service subscription. A service subscription applies to the
transactions of one configuration option setup for a combination of tax regime and legal entity or business unit.
Note
The level of detail of tax rounding definitions for the taxes in the tax regime must equal or exceed the level of detail
of the service provider tax rounding definitions.
Related Topics
• Content Subscriptions: Critical Choices
• Tax Controls and Defaults: Points to Consider
• Specifying First-Party Tax Profile Options: Points to Consider
544
Implementation
FAQs for Manage Tax Regimes

What's a service subscription?
A service subscription is the setup for provider services. It applies to the transactions of one configuration option setup for a
combination of tax regime and legal entity or business unit. Oracle Fusion Tax lets you use the tax services of external service
providers for tax calculation of US Sales and Use Tax on Oracle Fusion Receivables transactions.
You can use the tax services of these external service providers:
• Taxware, LP: a First Data Company
• Vertex, Inc.
If you integrate with a tax service provider, these actions are not required for Receivables transactions:
• Entering tax classification codes on transaction lines.
• Entering transaction line attributes in the Additional Tax Determining Factors region.
Tax service provider integration returns the calculated tax lines to Oracle Fusion Tax. The tax lines for Receivables
transactions returned by tax service providers are stored in Oracle Fusion Tax similar to the way tax lines calculated by the
application itself are stored.
Why are controls and defaults important?

Throughout Oracle Fusion Tax care is taken to minimize your effort in creating setup. One way of doing this is the extensive
use of defaulting so that you can enter your data once and use the defaults that appear on the subordinate or child records
where applicable. For example, many values you enter on the tax regime appear as defaults on each tax that is associated to
that tax regime. Generally, you can override the data where necessary if the defaulted value is not correct.
Also, to ensure maximum flexibility, as well as to ensure that the accuracy and integrity of the data and transactions are
maintained, Oracle Fusion Use Tax makes extensive use of data-driven controls that enable and control how tax functionality
works. For example, you have the requirement to set up tax recovery for value-added tax (VAT) processing. Enable the Allow
tax recovery option on the tax record so you can set up tax recovery rates for this type of tax.
Manage Tax Rates
Tax Rates: Overview

The tax determination process identifies the tax rate when taxes are considered applicable to a transaction. Tax rates can
apply to a specific location or jurisdiction, for example, you define state, county, and city jurisdiction-based rates for a US
Sales and Use Tax regime. Tax rates can change over time, for example when a tax rate increase occurs, you end date one
rate period definition and create a rate period with an effective start date.
There can be tax exceptions or exemptions to tax rates based on:
• Specific items
• Third parties
• General ledger accounts
545
Implementation
• Other factors
You must set up tax rates for tax statuses and optionally for tax jurisdictions. For tax statuses, set up tax rate records for each
applicable tax rate that a tax status identifies. For tax jurisdictions, set up tax rate records to identify the tax rate variations
for a specified tax and tax status within different tax jurisdictions. Set up your tax rates in the Manage Tax Rates and Tax
Recovery Rates task.
Tax Rate Determination Process

The tax rate determination process can be viewed as a two step process:
• Tax rate determination, which includes:
◦ A default tax rate associated to the tax
◦ An effective rate period
◦ Jurisdiction-based rates
◦ Tax rules; direct rate rules, tax rate rules, and account-based direct rate rules
◦ Migrated tax classification codes and tax classification-based direct rate rules
• Tax rate modification, which includes:
◦ Item or product fiscal classification exceptions using special rates, discounts, or surcharges
◦ Third party and third-party site tax exemptions using special rates and full or partial exemptions
Related Topics
• Tax Exemptions: Choices to Consider
• Tax Exception on a Transaction Line: How Tax Is Calculated
Tax Rate Setup: Explained

Consider the applicable tax statuses and optionally, tax jurisdictions when defining the tax rate setup to determine applicable
tax rates on a transaction.
Tax Statuses
A tax status is the taxable nature of a product in the context of a transaction and a specific tax on the transaction. You define
a tax status to group one or more tax rates that are of the same or similar nature. Each tax must have at least one status
defined and one status assigned as a default. Create tax rules to set alternate values as required.
For example, one tax can have separate tax statuses for standard and manually entered tax rates.
Tax Jurisdictions
A tax jurisdiction is an incidence of a tax on a specific geographical area. A tax jurisdiction is limited by a geographical
boundary that encloses a contiguous political or administrative area, most commonly the borders of a country. Often this
546
Implementation
is represented by a state, province, city, county, or even a tax zone. In Oracle Fusion Tax, a tax jurisdiction can use the
geography setup from your Oracle Fusion Trading Community Model geography hierarchy to identify a tax rate. Taxes such
as Canada's Harmonize Sales Tax (HST) and Provincial Sales Tax may require tax rates at the jurisdiction level.
For example, US Sales and Use Tax are applicable based upon the jurisdictions you generally define for state, county, and
city geographies.
Tax Rates
You must set up at least one tax rate for each tax status. You may need to set up additional tax rates at the tax jurisdiction
level if the tax rate applicable for the tax is unique for a particular tax jurisdiction.
For example, in Canada, HST is applied at a 13% rate in most provinces that have adopted HST except for British Columbia
where the tax rate is 12% and Nova Scotia where the tax rate is 15%. To satisfy this requirement define a single tax rate of
13% with no tax jurisdiction associated and define 12% and 15% tax rates and associate them with the British Columbia and
Nova Scotia jurisdictions respectively. This minimizes setup by creating an exception-based setup and a default option for the
most commonly utilized tax rate percentage.
Tax Rate Types
You can express tax rates in terms of percentage or quantity. A quantity-based tax rate is based upon the number of items
purchased or events that occur. For example, a taxing jurisdiction passes a law that each package of cigarettes sold is
subject to a tax of 0.87 USD. This tax is considered a quantity-based tax as it is assessed based upon the number of
packages purchased not the price of the product.
Tax Classification Code Set Assignments
When defining a tax rate select the tax classification code set assignments of Order to cash, Procure to pay, and
Expenses. These assignments determine if the tax rate code you define is applicable within a specific product and
set assignment at transaction time. In addition the set assignment of tax classification codes is derived based on the
configuration owner that is part of the tax rate code definition.
When you create a tax rate code where the:
• Configuration owner is the global configuration owner: The tax classification code is assigned to all sets that have the
determinant type of business unit and contain the determinant value of the business units that have the subscription
of the legal entity. The tax classification code is also assigned to the business units that do not have the subscription
of the legal entity but subscribe to the global configuration owner data for this tax regime.
• Configuration owner is the legal entity: The tax classification code is assigned to all sets that have the determinant
type of business unit and contain the determinant value of the business units that use the subscription of legal entity.
The tax classification code is also assigned to business units that subscribe to this specific legal entity as a first-party
organization.
• Configuration owner is the business unit: The tax classification code is assigned to all sets that have the determinant
type of business unit and contain the determinant value of the business unit for which the content is created.
Note
The application does not assign the tax classification codes to the global set of COMMON for any of these
scenarios.
You can use the tax classification codes created as determining factors when defining tax rules. When you use the regime
determination method of standard tax classification code, the tax classification based direct rate rules can be defined with
these codes as factors for direct rate determination. Maintain the tax classification codes using the associated lookup types
of Party Tax Profile Input Tax Classification, Party Tax Profile Output Tax Classification, and Party Tax Profile Web
Expense Tax Classifications.
Rate Periods
547
Implementation
You can define one or more rate periods for a tax rate as long as the date ranges do not overlap. This allows for a change
in tax rates over time without requiring a new tax rate code definition. You can define default effective periods for tax rate
periods. This effectivity must be unique across tax regime, configuration owner, tax, and tax status. This allows flexibility if
there is a requirement to define a new tax rate code and identify the new rate period as a default when existing rate periods
exist on another tax rate code. Define tax rules as exceptions to default tax rates.
Tax Recovery
When the associated tax allows tax recovery you can define tax recovery or offset tax rates. Associate the offset tax or the
default tax recovery rate and tax rule defined for tax recovery to the tax rate code. If the tax rule does not evaluate to true at
transaction time then the default tax recovery rate is applicable. Ensure that the tax recovery rate and tax rate periods overlap
or the application does not calculate tax recovery.
Tax Accounts
Define tax accounting for the tax rate code either as a default from the tax setup or an override of values at the tax rate level.
Tax accounts are defined for the legal entity and optionally for the business unit. The accounts you define are tax expense
accounts, tax revenue accounts, tax finance charge accounts, and accounts specific to tax recovery.
Setting Up Tax Rates: Choices to Consider

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 identifies. For tax jurisdictions, set up tax rate records to identify the tax rate variations for a specific tax
within different tax jurisdictions. For example, a city sales tax for a state or province may contain separate city tax jurisdictions,
each with a specific rate for the same tax.
At transaction time, you can override tax rates on calculated tax lines depending on your setup.
Quantity-Based Tax Rates

You can define tax rates as a percentage or as a value per unit of measure. The UOM field is optional in the tax setup.
However, if you do enter the UOM there is validation that must be passed in order for the tax rate to be applied. This includes:
• If the UOM exists on the tax rate, the transaction must have a matching UOM or a blank UOM.
• Only one active tax rate can exist for any given tax rate period. You cannot create one tax rate for each UOM that
might be used within a single tax rate code.
You can define the quantity rate type for a tax rate code with the UOM field left as blank. At transaction time, the application
multiplies the quantity by the tax rate and the UOM is not taken into account.
Override of Tax Rates on Tax Lines

Part of the configuration options is to allow you to override the calculated tax rate on a tax line. The following controls should
be considered during setup:
• Allow override of calculated tax lines: This option exists on the Create Configuration Owner Tax Options page for
the configuration owner and event class. In order for you to manually override tax lines this option must selected for
the combination of configuration owner and event class. If a configuration owner tax option does not exist the value
on the predefined event class setting is used.
• Allow override of calculated tax lines: You must select this option on the associated tax record to be able to
override values on a calculated tax line.
• Allow tax rate override: You must select this option on the associated tax status record to be able to override tax
rates on a calculated tax line.
• Allow ad hoc tax rate: You must select this option on the tax rate record if you want to allow the flexibility of not
being restricted to predefined tax rates and allow user entered rates on calculated tax lines.
548
Implementation
If you allow ad hoc tax rates you must indicate if the adjustment to a tax amount updates the taxable basis or the tax
rate.
Note
You can set the Transaction Tax Line Override profile option to control which users can make changes to the
transaction line such as selecting a different tax status or tax rate.
Tax Rates Controls and Defaults: Points to Consider

Set up tax rates for your tax statuses and optionally for tax jurisdictions. For tax statuses, set up a tax rate record for each
applicable tax rate that a tax status identifies. For tax jurisdictions, optionally set up tax rate records to identify the tax rate
variations for a specific tax within different tax jurisdictions.
Defining Controls and Defaults for Tax Rates

The following table describes the defaults and controls available at the tax rate level.
Header Region

from on
Tax Rate Type Lookup code that None None Defines whether
controls the type the tax rate is
of tax rate. Values either percentage
are: or quantity based

• Percentage:
The tax
rate is a
percentage
based on the
line value
• Quantity:
The tax rate
is based on
the currency
per UOM
such as USD
per kilo
Tax Classification Controls where None None If selected then the

Code Set tax classification tax classification
Assignments codes that are code associated
created in parallel with this tax rate
• Order to to the creation of is available for use
cash the tax rate are in order to cash,
available for use procure to pay,
• Procure to and expenses
pay transactions

549
Implementation
from on
• Expenses
Rate Periods Region

from on
Set as Default Controls whether None None If selected then

Rate this tax rate is the this tax rate is the
default rate for the default tax rate
defined tax status for the defined
for the period tax status for the
specified period specified.
Where there
are no tax rate
rules applicable
at transaction
time then the tax
determination
process selects
this tax rate where
the associated tax
status is derived
during the period
specified.

Main Details Tab, Other Details Region
550
Implementation
from on
Tax Inclusion Defines whether None None Use this option in

Method the tax is: conjunction with
other setup on tax,
• Standard party tax profile,
noninclusive tax registration,
handling: and transaction
This option details to control
calculates the inclusiveness
the taxes of a line amount at
as exclusive transaction time
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
differs from
the standard
inclusive
process
551
Implementation
from on
Allow override and Controls whether Tax None Use this option in
entry of inclusive you can override conjunction with
tax lines and enter inclusive the Transaction
or exclusive line Tax Line Override
amounts profile option as
well as Allow
override of
calculated
tax lines and
Allow override
and entry of
inclusive tax
lines options for
the configuration
owner tax options
to allow you
to update the
Inclusive option
on tax line at
transaction time
Allow tax Controls whether Tax status None If this option

exceptions tax exceptions are is selected tax
allowed for this tax exceptions can
be processed at
transaction time

Allow tax Controls whether Tax status None Use this option
exemptions tax exemptions are in conjunction
allowed for this tax with the Allow
exemptions
option on the
configuration
owner tax options
and when both are
selected allows
tax exemptions to
be processed at
transaction time
552
Implementation
from on
Allow ad hoc tax Controls whether None None Use this option
rate you can enter ad in conjunction
hoc tax rates at with Transaction
transaction time Tax Line Override
profile option
and the Allow
override of
calculated tax
lines option for
the configuration
owner tax options.
If all are selected
allows you to enter
tax rates.
Adjustment for Ad Lookup code that None None When the Allow
Hoc Tax Amounts is used when you ad hoc tax
select the Allow rate option is
ad hoc tax rate selected the
option lookup value in this
field controls how
the application
controls the
change in tax
value, either as
a change to the
taxable basis or to
the tax rate value
used
Default Settlement Lookup code to Tax status None Defines whether

Option indicate whether the settlement
an input tax is is immediate,
recovered when for example, at
an invoice is invoice time,
recorded or only or deferred,
when the invoice is for example, at
paid and whether payment time
an output tax is
due for settlement
when the invoice
is issued or only
when the payment
is received against
it

Related Topics
• Inclusive Taxes: Explained
• Profile Options Controls and Defaults: Points to Consider
553
Implementation
• Tax Status Controls and Defaults: Points to Consider
Tax Rates for a Canadian Tax Regime: Examples

The following scenarios illustrate when you might want to use exceptions or tax rules to meet your Canadian tax
requirements.
Scenario
The first scenario includes tax calculation for a Canadian tax regime. Purchases made in Ontario are generally taxed for
Provincial Sales Tax (PST) at a tax rate of 8%. Accommodation purchases are generally taxed at 5% and food is generally
exempt from tax.
EDC Corporation's Ontario store has been invoiced for employee accommodations, including hotel facilitates and food for a
conference they attended. The invoice is for a hotel room, use of hotel office facilities, and food.
Set up tax rates to meet PST requirements for the store in Ontario as follows:
• Define a jurisdiction-based tax rate of 8% which is applicable to the hotel facilities usage. This is the standard tax
calculation for the jurisdiction of Ontario.
• Define a rate exception with a special rate of 5% for the hotel room. This exception can be driven by a product fiscal
classification.
• Define a Determine Tax Status rule which points to the exempt status of 0% rate for food based on a product fiscal
classification. Use the tax rule over an exception since you can use a specific tax status and the default rate of 0%
for that tax status.
Scenario
Another example of tax calculation for a Canadian tax regime is purchases of some items made on First Nation reserves have
a First Nations Tax that is applicable at a tax rate of 5%. Since the requirements drive the applicability of the tax as well as the
tax status and tax rate you can define a direct rate rule to handle both the applicability and the tax rate.
Manage Tax Recovery Rates
Tax Recovery: Explained

Tax recovery is the full or partial recovery of tax paid on purchases by a registered establishment to offset the tax collected
from sales transactions. There are usually many regulations surrounding the details of tax recovery. For example, in most
European countries, tax is fully recoverable on all purchases except for businesses that only sell nontaxable supplies, such as
financial institutions. In cases in which businesses only sell nontaxable supplies, value-added tax (VAT) on their purchases is
not recoverable. In certain countries like Canada, more than one type of recovery is possible. Tax authorities designate the tax
recovery rates that indicate the extent of recovery for a specific tax.
Tax recovery information on a transaction may be viewed on the invoice distributions level, including any pertinent information
for nonrecoverable and recoverable taxes where applicable.
If the recovery rate on a tax varies based on one or more transaction factors, set up recovery rate rules to determine the
appropriate recovery rate on the transaction. For example, most VAT-type taxes allow full recovery of taxes paid on goods
and services that relate to taxable business supplies. In cases where an organization makes purchases relating to both
taxable and exempt supplies, the tax authority can designate a partial recovery rate to reflect the proportion that relates to the
554
Implementation
taxable supplies. For instance, in the UK, Her Majesty's Revenue and Customs (HMRC) have two methods to work out the
tax recovery rate percentage:
• Standard method: Taxable supplies divided by the value of all supplies added together (both taxable and exempt).
This formula is based on a previous period with an adjustment when the actual proportions are known.
• Special method: A custom formula approved by HMRC that reflect a business's unique circumstances that must
produce a fair and reasonable result. Approval to use this special method is based on the business type, the types of
supplies, and the business's cost structure.
The Determine Recovery Rate process evaluates tax recovery for applicable taxes. The Determine Recovery Rate process
determines the recovery rate to apply to each recovery type for each applicable tax on the transaction.
Determine Recovery Rate

Tax rules use the tax configuration setup defined within Oracle Fusion Tax and the details on the transaction to determine
which taxes apply to the transaction and how to calculate the tax amount for each tax that applies to the transaction.
Tax rules let you create a tax determination model to reflect the tax regulations of different tax regimes and the tax
requirements of your business. You can create a simple tax model or a complex tax model. A simple tax model makes use
of the default values without extensive processing while a complex tax model considers each tax requirement related to a
transaction before making the final calculation.
The tax determination process evaluates, in order of priority, the tax rules that are defined and the details on the transaction. If
the first rule is successfully evaluated, the result associated with the rule is used. If not, the next rule is evaluated until either a
successful evaluation or default value is found.
The tax determination process is organized into rule types. Each rule type identifies a particular step in the determination
and calculation of taxes on transactions. The rule type and related process used for tax recovery determination is Determine
Recovery Rate. This is an optional setup that is applicable to taxes that have tax recovery enabled.
This process determines the recovery rate to apply to each recovery type for each applicable tax on the transaction that
allows for full, partial, or no recovery of the tax amount. In many cases, the tax determination process uses either the recovery
rate associated with the tax rate or the default recovery rate defined for the tax. However, if the tax recovery rate varies
according to determining factors, such as intended use, then create a Determine Recovery Rate tax rule to derive the
recovery rate.
You can only set up a Determine Recovery Rate tax rule for taxes that have the tax recovery option enabled. For countries
with more than one type of recovery, use primary and secondary recovery types to address this requirement. After the
recovery rate is determined for each recovery type, the tax determination process determines the recoverable amounts
against each recovery type for each tax line. The remaining tax amount becomes the nonrecoverable tax amount for the tax
line.
The following outlines the process that results in a recoverable tax amount for each recoverable tax distribution:
1. Allocate tax amount per item distributions. While taxes are determined at the transaction line level, tax recovery is
determined at the transaction line distribution, or item distribution, level.
2. Determine recovery types. The tax determination process determines for each tax and item distribution, whether
the primary and, if defined, secondary recovery types apply. The result of this process is a tax distribution for each
recovery type for each tax and item distribution. If recovery types are not defined, go to step 5.
3. Determine recovery rates. For each tax distribution, the tax determination process determines the recovery rate
based on the following:
a. Consider the Determine Recovery Rate tax rule for the first recoverable tax distribution.
b. Use the tax recovery rate derived from the tax rule.
555
Implementation
c. If the tax determination process cannot derive a tax rule based on the transaction values, use the tax
recovery rate associated with the tax rate for the tax line.
d. If there is no tax recovery rate associated with the tax rate, use the default tax recovery rate for the recovery
type and tax. If there is no default tax recovery rate for the recovery type and tax, use the default tax recovery
rate defined for the tax.
e. Repeat the above steps for each recoverable tax distribution, if applicable.
4. Determine the recoverable amounts. The tax determination process applies the recovery rates to the apportioned
tax amounts to determine the recoverable tax amounts. The result of this process is a recoverable tax amount for
each recoverable tax distribution.
5. Determine the nonrecoverable amount. Oracle Fusion Tax calculates the difference between the apportioned
tax amount of every tax line per item distribution and the sum of the recoverable tax distribution to arrive at the
nonrecoverable tax amount, and then creates a nonrecoverable tax distribution for this amount. If a primary
recovery type was not defined for a tax, the entire apportioned amount for the item distribution is designated as the
nonrecoverable tax amount.
Tax Recovery: Points to Consider

The tax determination process uses your tax configuration setup and the details on the transaction to determine which taxes
are recoverable.
You need to decide when to:
• Create Determine Recovery Rate rules

• Specify separate ledger accounts
• Manage tax distributions
• Specify settlement options
When to Create Determine Recovery Rate Rules

Use recovery rate rules to determine the applicable recovery rates when this determination is based on one or more
transaction factors, including the parties, locations, product or product purpose.
At transaction time, the tax determination process uses the recovery rate derived from the recovery tax rules. If no recovery
rate rules are defined or if no existing recovery rate rule applies to the transaction, the tax determination process uses the
default recovery rate that you define.
Commonly used factors that are used in tax recovery rules include:
• Intended use, such as resale or manufacturing

• Party fiscal classification, such as reseller or charitable organization
• Location, such as British Columbia or New Brunswick
When to Specify Separate Ledger Accounts

Recovery details are primarily captured and tracked through invoice distributions. If there is a requirement to capture the
recovery details into separate general ledger accounts for each tax, define the recovery account at the recovery rate level. If
the recovery and liability can be combined at the account level, the common account for liability or recovery defined at the tax
rate level can be used.
While generating the invoice distributions, the application first considers the recovery account defined at the recovery rate
level. If it is null, the liability or recovery account defined at the tax rate level is used.
556
Implementation
The nonrecoverable component of a tax gets registered into the expense account defined at the tax rate level. If no
specific expense account is given, the item charge account available on the transaction is used. There may be a need to
apportion the nonrecoverable component of the tax amount on the item cost. As such, you should consider all of the costing
requirements while setting up an expense account.
When to Manage Tax Distributions

Use the Tax Distributions window to review and update the tax recovery rate on tax distributions. Oracle Fusion Tax creates
recoverable distributions and calculates tax recovery rates when you save the line distribution, according to the Determine
Recovery Rate tax rule process or the default recovery rate.
You can update the recovery rate code if the Allow tax recovery rate override option is enabled for the tax.
You can update the recovery rate if the Allow ad hoc tax rate option is enabled for the recovery rate. The update method
differs according to the transaction application:
• Oracle Fusion Purchasing: You can either enter a new recovery rate or select another recovery rate that you
previously defined from the list of values.
• Oracle Fusion Payables: You can only select another rate that you previously defined. If you update the recovery
rate on a tax distribution, Oracle Fusion Tax also updates the related nonrecoverable rate and amount, and the
distribution for the tax line.
If there are tax rules defined based on the Accounting determining factor class, then changing or creating a distribution may
affect tax calculation.
When to Specify Settlement Options

Tax authorities allow tax recovery at different stages of a transaction life cycle. You can specify the settlement options to
indicate when tax recovery is possible:
Settlement Option Purpose
Immediate Tax recovery is settled after invoice validation.

Deferred Tax recovery is settled only after the invoice is paid.

If the recovery settlement is Deferred, you must set up an interim tax account for this tax to record the tax recoveries
or liabilities that accrue prior to the payment. Though this is an interim account the balance in this account represents a
contingent asset. As such, management and other reporting requirements need to be duly considered while setting up or
changing this account.
Tax Recovery Rates Controls and Defaults: Points to Consider

Define tax recovery rates to claim full or partial recovery of taxes paid. Set up tax recovery rate codes for the recovery types
identified on the taxes within a tax regime. A tax recovery rate code identifies the percentage of recovery designated by the
tax authority for a specific transaction.
Defining Controls and Defaults for Tax Recovery Rates

The following table describes the defaults and controls available at the tax recovery rate level.
Recovery Rate Periods Region
557
Implementation
from on
Set as Default Controls whether None None If selected then

Rate this tax recovery this recovery tax
rate is the default rate is the default
recovery rate rate for the period
for this tax at specified. Where
transaction time there are no tax
recovery rate
rules applicable
at transaction
time then the tax
determination
process selects
this tax recovery
rate.

Related Topics
• Tax Controls and Defaults: Points to Consider
Recoverable Taxes: Worked Example

The following example illustrates the tax setup and associated tax conditions that drive tax recovery. Set up tax rules to
assign specific recovery rates instead of using the default recovery rates defined for the tax. Two recovery types are used to
show the primary and secondary recovery type options for a tax.
In Canada, the Goods and Services Tax (GST) is a tax that applies to the supply of most property and services in Canada.
The provinces of British Columbia, Ontario, New Brunswick, Nova Scotia, and Newfoundland and Labrador, referred to as
the participating provinces, combined their provincial sales tax with the GST to create the Harmonized Sales Tax (HST).
Generally, HST applies to the same base of property and services as GST. In countries like Canada, some or all of the taxes
on business transactions for registered companies are recoverable taxes.
ABC Corporation is a business located in the province of British Columbia. The sales invoice indicates that ABC purchases
books for the purposes of resale. ABC has already created the following setup:
• CA GST and HST, a GST and HST based tax regime

• CA HST, an HST based tax
• CA HST STANDARD, the default HST based tax status for the CA HST tax
• CA HST ZERO FED REC RATE and CA HST ZERO PROV REC RATE, 0% recovery rates for HST, which are set as
the default recovery rates for the CA HST tax
• CA HST STANDARD RATE, the default HST based tax rate for the CA HST tax
The percentage rate is 13% for most provinces, and 12% for British Columbia.
The following tax implications are applicable in this scenario:
• Both federal and provincial components of HST are 100% recoverable on books bought for resale.
◦ Zero recovery rates for federal and provincial components of HST are required, and are set as the default
recovery rates for the HST tax.
558
Implementation
◦ Recovery rates for most of the participating provinces are required to address the full recovery of the 13% HST
rate.
◦ Recovery rates for British Columbia are required to address the 12% HST rate.
◦ Recovery rate rules are required to assign nondefault recovery rates for resale purchases.
• HST is not recoverable on consumable items, such as computers for use in ABC's store. Default zero recovery rates
apply in this case.
Perform the following steps:
• Create tax recovery rates

• Create an intended use fiscal classification
• Create recovery rate rules
Create Tax Recovery Rates

For most participating provinces in Canada, the HST is 13%, out of which 5% is the federal component and 8% is the
provincial component.
Create the tax recovery rates of 38.46% for the federal component of HST, and 61.54% for the provincial component of HST
for these provinces.
1. On the Create Tax Recovery Rate page, enter the name of the tax regime, CA GST and HST.
2. Select the configuration owner for this tax recovery rate. To minimize configuration and maintenance costs, select
Global Configuration Owner as the configuration owner.
3. Select the HST tax, CA HST.
4. Enter the name of the tax recovery rate you are defining, such as CA HST STD FED REC RATE.
5. Select PREC as the recovery type.
6. In the recovery rate periods table, enter 38.46 as the percentage recovery rate, and an effective start date.
8. Repeat steps 1 to 7 to create the tax recovery rate CA HST STD PROV REC RATE, with a recovery type of SREC,
and a percentage recovery rate of 61.54%.
For British Columbia, where the HST rate is 12%, you need one federal recovery rate to address the 5% federal component
and one provincial recovery rate to address the 7% provincial component. Create a tax recovery rate of 41.67% for the
federal component of HST, and a tax recovery rate of 58.33% for the provincial component of HST for British Columbia.
1. On the Create Tax Recovery Rate page, enter the name of the tax regime, CA GST and HST.
2. Select the configuration owner for this tax recovery rate. To minimize configuration and maintenance costs, select
Global Configuration Owner as the configuration owner.
3. Select the HST tax, CA HST.
4. Enter the name of the tax recovery rate you are creating, such as CA HST BC FED REC RATE.
5. Select PREC as the recovery type.
6. In the recovery rate periods table, enter 41.67 as the percentage recovery rate, and an effective start date.
559
Implementation
8. Repeat steps 1 to 7 to create the tax recovery rate CA HST BC PROV REC RATE, with a recovery type of SREC,
and a percentage recovery rate of 58.33%.
Create Intended Use Fiscal Classification

Create an intended use fiscal classification for Resale. An intended use fiscal classification is a tax classification based on the
purpose for which the product is used.
1. In the Create Fiscal Classification Code window of the Manage Intended Use Classification page, enter a code for
the classification, such as CA INTENDED USE RESALE.
2. Enter a name for this classification, such as CA Intended Use Resale.
3. Optionally, select Canada as the country and enter a start date, such as 1/01/2001.
Create Recovery Rate Rules

Create the recovery rate rules that apply for most participating provinces when the conditions for HST recovery are met.
Recall that by default, tax recovery on HST is 0% at the federal and provincial levels.
1. In the Create Determine Recovery Rate Rule page, select Global Configuration Owner as the configuration owner,
CA GST and HST as the tax regime, and CA HST as the tax.
2. Enter the code and name of the tax recovery rate rule you are creating, such CA HST FED RECOVERY RULE, the
start date, and a recovery type code of PREC.
3. Create or select a tax determining factor set and an associated tax condition set whereby the intended use of the
acquired product is the intended use fiscal classification you defined earlier, namely CA INTENDED USE RESALE.
When this condition is met, 100% recovery rate for the federal component is applicable.
4. For the tax condition set, assign the result of CA HST STD FED REC RATE.
5. Assign a rule order, such as 100.
7. Repeat steps 1 to 6 to create CA HST PROV RECOVERY RULE for the standard provincial recovery rule, with a
recovery type code of SREC, a result of CA HST STD PROV REC RATE, and a rule order of 110.
Create the recovery rate rules that apply for British Columbia when the conditions for HST recovery are met.
1. In the Create Determine Recovery Rate Rule page, select Global Configuration Owner as the configuration owner,
CA GST and HST as the tax regime, and CA HST as the tax.
2. Enter the code and name of the tax recovery rate rule you are creating, such CA HST BC FED RECOVERY RULE,
the start date, and a recovery type code of PREC.
3. Create or select a tax determining factor set and an associated tax condition set whereby the ship-to location is
British Columbia and the intended use of the acquired product is the intended use fiscal classification you defined
earlier, CA INTENDED USE RESALE.
When this condition is met, 100% recovery rate for the federal component is applicable.
4. For the tax condition set, assign the result of CA HST BC FED REC RATE.
5. Assign a rule order, such as 50, that gives a higher priority to this rule than the 2 rules you created previously.
7. Repeat steps 1 to 6 to create CA HST BC PROV RECOVERY RULE for British Columbia's provincial recovery rule,
with a recovery type code of SREC, a result of CA HST BC PROV REC RATE, and a rule order of 55.
560
Implementation
For ABC's transactions in Canada, the following is determined by the previous setup:
◦ HST tax is applicable and is calculated at a percentage rate of 13% for most participating provinces, and a
percentage rate of 12% in British Columbia.
◦ The intended resale of these books makes these transactions eligible for 100% tax recovery.
◦ For most participating provinces, tax recovery is calculated at a federal percentage rate of 38.46% and a
provincial rate of 61.54%.
◦ For British Columbia, tax recovery is calculated at a federal percentage rate of 41.67% and a provincial rate of
58.33%.
Tax Recovery Distributions: Explained

A recoverable tax is a tax that allows full or partial recovery of taxes paid on purchases, either as a recoverable payment or
as a balance against taxes owed. A tax recovery rate identifies the percentage of recovery for a tax designated by the tax
authority for a specific transaction line. You can review Oracle Fusion Payables tax distributions and, if applicable, update the
tax recovery rate on a tax distribution depending on your tax setup and security access. The component in Oracle Fusion
Purchasing is view-only.
Managing Tax Recovery Distributions

Oracle Fusion Tax creates recoverable distributions and calculates tax recovery rates when you save the line distribution,
according to the Determine Recovery Rate tax rule process or the default recovery rate. If self-assessment is enabled for the
applicable party, two distributions for each tax are created, one with a positive amount and the other with a negative amount.
One recoverable distribution for the primary recovery type and, if applicable, the secondary recovery type is created, for
each tax line for each of the item distributions into which the item line or expense line is distributed. The tax distributions are
displayed in this way:
• If the tax is nonrecoverable, one nonrecoverable tax distribution line for the tax is created, with the nonrecoverable
amount equal to the tax amount. You cannot update a nonrecoverable tax distribution nor create a manual
recoverable distribution.
• If the tax is recoverable, two or three distribution lines are displayed, one for the primary recoverable amount, one for
the secondary recoverable amount, if applicable, and another for the nonrecoverable amount.
If the tax is fully recoverable, then the recoverable distribution amount is equal to the tax amount and the
nonrecoverable distribution amount is equal to zero.
If the tax is recoverable and the recovery rate is zero, then the nonrecoverable distribution amount is equal to the tax
amount and the recoverable distribution amount is equal to zero.
• If self-assessment is enabled for the applicable party, the application creates two distributions for each tax, one with
a positive amount and the other with a negative amount.
If the tax applied on the transaction is self-assessed, then the corresponding recoverable and nonrecoverable
tax distributions are not visible in the distributions window, but the application does generate them at the time of
accounting for the invoice
• If the tax applied on the transaction is of the offset type, then the application creates two distributions for the
recovery and nonrecovery portions of the tax. Since they are intended to offset each other, they are created for the
same amount, but one with a positive value and the other with a negative value.
561
Implementation
In a Payables transaction you can update the recovery rate code if the Allow tax recovery rate override option is enabled
for the tax. You can update the recovery rate if the Allow ad hoc tax rate option is enabled for the recovery rate.
If you update the recovery rate on a tax distribution, Oracle Fusion Tax also updates the related nonrecoverable rate and
amount, and the distribution for the tax line. If the distribution status is frozen, you cannot update the tax distribution. In order
to change the distribution, you must reverse the tax distribution and enter a new distribution.
If applicable, accounting-related setups may affect tax calculation:
• If there are tax rules defined based on the Accounting determining factor class, then changing or creating a
distribution may affect tax calculation.
• If the Enforce tax from account option is enabled for the configuration owner and event class, this may affect the
tax calculation based on the distribution.
Tax Recovery Distributions: Example

Recoverable distributions are created and tax recovery rates are calculated when you save the line distribution, according to
the Determine Recovery Rate tax rule process or the default recovery rate. You can review tax distributions and, if applicable,
update the tax recovery rate on a tax distribution.
Note
The authorized user can update the tax recovery rate on the distribution in Oracle Fusion Payables. The
component in Oracle Fusion Purchasing is view-only.
Scenario
Your company is located in a Canadian province that has combined the provincial sales tax with the federal goods and
services tax (GST) into a harmonized sales tax (HST). They recently purchased books to sell in their stores. They also
purchased some computers to use in kiosks within the stores for customers to use to locate books.
Transaction Details
The transaction details are as follows:
• Total cost of books is 10,000 CAD
The invoice indicates the intended use as Resale.

• Total cost of computers is 5,000 CAD
The computers will be expensed as they do not meet the capitalization threshold.
• Tax rate applicable to each item is 13%
Analysis
In most tax regimes, a tax that is paid by a registered establishment can claim back 100% of taxes due from the tax authority,
except for specific designated purchases. Depending upon the details of a company's business purchases and tax authority
regulations, a number of exception regulations may accompany the details of tax recovery. Tax implications are:
• The HST associated with the cost of books to be sold in stores is 100% recoverable. Therefore, 1,300 CAD is
recoverable (10,000 CAD * 13%).
562
Implementation
• The HST associated with the cost of the computers to be used in kiosks within the stores is not recoverable.
Therefore, 650 CAD is nonrecoverable (5,000 CAD * 13%).
The HST tax configuration specifies that the recovery tax rate for zero 0% recoverable is used as a default. A tax rule is
defined to apply a 100% recoverable rate for products with an intended use of Resale.
Tax Recovery Distributions

Based on the analysis, the following distributions are created for the transaction:
Accounting Class Debit Credit
Item Expense 10,000

Item Expense 5,000

Recoverable Tax 1,300

Nonrecoverable Tax 650

Liability 10,000

Liability 5,000

Liability 1,300

Liability 650

Manage Tax Rules
Tax Determination: Explained

Taxes are levied on transactions as per the legislations in a country or region. They are seldom uniformly applied on all
transactions and tax legislation may seek differential levy, treatment, and administration of taxes based on various transaction
attributes. Configure Oracle Fusion Tax to evaluate transactions based on transaction attributes to determine which taxes
apply to a transaction and how to calculate tax amount for each tax that applies to the transaction.
The tax determination process evaluates transaction header and line information to derive tax lines for taxes applicable to the
transactions. The evaluation process is subdivided into the following processes:
• Determine Applicable Tax Regimes and Candidate Taxes

• Determine Place of Supply and Tax Jurisdiction
563
Implementation
• Determine Tax Applicability
• Determine Tax Registration
• Determine Tax Status
• Determine Tax Rate
• Determine Taxable Basis
• Determine Tax Calculation
• Determine Tax Recovery
The tax determination process utilizes the tax foundation configuration in conjunction with configuration options and tax rules
to process transactions for tax applicability and calculation. Tax configuration ranges from simple models that make use of
default values without extensive processing to complex models that consider each tax requirement related to a transaction
before making the final calculation.
When setting up a tax examine the regulations that govern the determination of the tax amount, from identifying applicability
drivers to how the tax is calculated. Organize the regulations into one or more rule types for each tax. When the regulations
indicate that more than one result is possible for a given rule type, then you need to define rules within that rule type.
Otherwise you can defer to a default value for that rule type associated to the tax.
The complexity of setup can be classified as follows:
• No tax rules required: Oracle Fusion Tax uses the default tax status, tax rate, and tax recovery rate defined for the
tax. Tax rules are not required but tax rates can vary by class of products set up using tax exceptions, location set
up using tax jurisdictions, and party set up using exemption definitions. In addition, applicability can still be controlled
without the use of tax rules such as through the party tax profile that you define for a supplier.
• Simple tax rule regimes: The tax authority levies tax on your transactions at the same rate, with a simple set of
identifiable exceptions. The exceptions either apply to one part of the transaction only, such as to certain parties, or
to a combination of parties, products, and transaction processes that you can summarize in a simple way. In such
cases, use a simple set of tax rules, for example, to identify place of supply and tax registration, and use default
values for other processes.
• Complex tax regimes: Tax regimes in certain countries require a complex logic to determine the applicable taxes
and rates on a transaction. Both tax applicability and tax rates can vary, for example, by place of origin and place of
destination, party registration, status, service, or a combination of factors. In some cases, the taxable amount of one
tax may depend upon the amount of another tax on the same transaction. And in rare cases, the tax amount itself
may depend on the tax amount of another tax. For all of these and similar situations, you set up tax rules to define
the logic necessary to identify each step of the tax determination process.
Tax Determination Steps

The first step of the determination process is to identify the first party of the transaction. The tax determination process looks
to the business unit on the transaction and identifies whether it is pointing to the configuration owner of the business unit or
legal entity depending on the Use subscription of the legal entity option on the party tax profile definition of the business
unit. The tax determination process checks to determine if there are configuration owner tax options associated to this party
or if the predefined event class option should be used.
The Determine Applicable Tax Regimes process can be the predefined TAXREGIME, STCC (standard tax classification code),
or another regime determination set that is user-defined. TAXREGIME or user-defined regime determination sets derive
the applicable tax regimes or tax regime through country or zone of the location identified in the processing of the regime
determination determining factor set location values. STCC determination is typically used for purposes of migrated data and
has a different processing logic driven by tax classification code. A third option of determination is third-party integration.
564
Implementation
Determine Applicable Tax Regimes and Candidate Taxes
Tax regimes are considered based on geography and subscription. Either a country or zone associated to the tax
regime definition must be the same as the country or zone identified via the location that evaluates to true on the regime
determination set of the first party of the transaction. In addition, the tax regime must have a subscription to the applicable
configuration owner. Once the tax determination process identifies the tax regimes the list of candidate taxes can be
evaluated based on the configuration option setting of the first party in the tax regime subscription definition:
• Common Configuration: Consider all taxes with the configuration owner of global configuration owner.
• Party Specific Configuration: Consider all taxes with the first party as configuration owner.
• Common Configuration with Party Overrides: Consider all taxes with the first party and the global configuration
owner as configuration owner. If a tax is defined by both the first party and the global configuration owner, then the
application only uses the tax defined by the first party.
• Parent First-Party Configuration with Party Overrides: Consider all taxes with the first party and the parent first party
as configuration owner. If a tax is defined by the first party and the parent first party then the application only uses
the tax defined by the first party.
Determine Tax Applicability and Place of Supply and Tax Jurisdiction

This process determines the tax applicability of each candidate tax based on direct rate determination, place of supply, tax
applicability, and tax jurisdiction. The first step in tax applicability is to process any direct rate rules defined for a tax regime,
configuration owner, and candidate taxes. If a direct rate rule evaluates to true then place of supply is processed for this
transaction tax. If successful the tax is applicable and the tax status and tax rate defined for the direct rate rule are used
in the tax calculation. If a direct rate rule does not evaluate to true for this tax regime, configuration owner, and tax the tax
applicability rules are processed next. After a tax is found applicable based on an applicability rule or a default value the
process verifies the place of supply and associated tax jurisdiction. This is required except in the cases of migrated taxes.
The place of supply process identifies the applicable location type and associated tax jurisdiction where the supply of goods
or services is deemed to have taken place for a specific tax. If the tax determination process cannot find a tax jurisdiction
for the location that corresponds to the place of supply location type, then the tax does not apply and it is removed as a
candidate tax for the transaction.
For example, the place of supply for UK value-added tax (VAT) on goods is generally the ship-from country. Thus, the place
of supply of a sale or purchase within the UK is the UK itself. However, if a UK legal entity supplies goods from its French
warehouse to a German customer, then the place of supply will not find a jurisdiction for UK VAT in France, and therefore UK
VAT does not apply.
Determine Tax Registration
This process determines the party whose tax registration is used for each tax on the transaction, and, if available, derives the
tax registration number.
Determine Tax Status
This process determines the tax status of each applicable tax on the transaction. If the process cannot find a tax status for an
applicable tax, then Tax raises an error.
Determine Tax Rate
This process determines the tax rate code for each tax and tax status derived from the previous process. First the application
looks for a rate based on rate code and tax jurisdiction. If this is not found then the application looks for a rate with no tax
jurisdiction. If applicable, the tax rate is then modified by any exception rate or tax exemption that applies. The result of this
process is a tax rate code and tax rate for each applicable tax.
Determine Taxable Basis
This process determines the taxable base for each tax rate code. Depending on the tax rate type the taxable basis is amount
based or quantity based. The tax determination process typically determines the tax by applying the tax rate to the taxable
565
Implementation
base amount. In some cases, the taxable basis either can include another tax or is based on the tax amount of another tax.
Define taxable basis formulas to manage these requirements.
Determine Tax Calculation
This process calculates the tax amount on the transaction. In most cases, the tax amount is computed by applying the
derived tax rate to the derived taxable basis. In some exceptional cases, the tax amount is altered by adding or subtracting
another tax. Define tax calculation formulas to manage these requirements.
Determine Tax Recovery
This process determines the recovery rate to use on procure-to-pay transactions when the tax allows for full or partial
recovery of the tax amount. For example, for UK manufacturing companies VAT on normal purchases used for company
business is 100% recoverable. However, if you are a financial institution which only makes VAT exempt on sales then you are
not allowed to recover any taxes and your recovery rate is zero percent on all purchases. The recovery process impacts the
distribution level, tax amounts, and inclusiveness of taxes. The resulting distribution amounts are adjusted as a result of the
recovery process. The recovery type is defined on the tax and identifies whether there are one or two recovery types; primary
and secondary. For each tax and recovery type the application determines the recovery rate based on a tax rule or default
value defined on the tax.
Tax Rules: Explained

Tax determination can be configured as a simple process with all default values for the determination points and it can be
enhanced with the definition of tax rules to identify and process any exceptions to the common treatment scenario.
The tax rules that are part of the tax determination process are organized into rule types. Each rule type identifies a particular
step in the determination and calculation of taxes on transactions. The tax determination process evaluates, in order of
priority, the tax rules that are defined against the tax configuration setup and the details on the transaction. The application
processes tax rules in order of evaluation until one evaluates successfully, then the process stops. If none of the rules defined
evaluate successfully the associated default value is used.
The tax line determination process uses the information of the transaction header and the transaction line and any information
derived by the transaction attributes such as party fiscal classification to determine the tax lines. The rule types and related
processes are used for tax line determination and tax calculation.
Tax rules have the following elements as part of the definition:
• Rule type and rule attributes:
◦ Tax regime, configuration owner, tax and optionally, tax status and tax recovery type
◦ Event class association
◦ Geography association
◦ Effective dates
• Determining factors and condition sets
• Rule order and status
A rule type associates a tax rule to a particular point in the determination process. The following are the possible tax rules you
can define:
• Place of Supply Rules
• Tax Applicability Rules
566
Implementation
• Tax Registration Determination Rules
• Tax Status Determination Rules
• Tax Rate Determination Rules
• Taxable Basis Rules
• Tax Calculation Rules
• Tax Recovery Rate Determination Rules
• Manage Direct Tax Rate Determination Rules
• Account Based Direct Tax Rate Determination Rules
• Tax Classification Based Direct Tax Rate Determination Rules
Define a tax rule in the context of a tax regime, configuration owner, tax. Define Tax Rate Determination Rules within the
context of a tax regime, configuration owner, tax, and tax status. Define Tax Recovery Rate Determination Rules within the
context of a tax regime, configuration owner, tax, and recovery type. When processing a transaction the transaction date
must be within the effective date of the rule.
Associate a tax rule with an event class or tax event class on the tax rule header to identify the tax rule as only being
applicable to a specific event class. The tax determination process evaluates event-specific rules and tax event-specific rules
before nonevent-specific rules for the same rule type, tax regime, configuration owner, and tax. Set up more specific event
classes to less specific tax event classes to generic tax rules applicable to all event classes. Include geography information on
the tax rule header as well as within the determining factor or condition set detail. Including geography detail does not change
evaluation order but improves the performance of tax rule processing. Include reference information, such as tax law or other
text, in the definition of the tax rule.
Tip
Always try to minimize tax rules and setup for tax regimes and taxes. Tax rules are specific to a tax regime and
tax, thus by minimizing the number of tax regimes and taxes, the number and complexity of the tax rules can be
minimized.
Tip
Move any complexity from the beginning to the end of the rule types and supporting setup. For example, it
is better to use tax recovery rate rules in preference to setting up specific tax rates with individual defaults
associated with tax recovery rates.
Tax reporting requirements adds some level of complexity to the pure tax setup needed to support the tax determination
and calculation processes, make every effort to minimize this additional level of complexity. Write tax reports wherever
possible to use tax reporting codes or use the determination factors that identify your reporting requirements. These reporting
determination factors should replace the need to create specific taxes, tax statuses, and tax rates purely defined to allow tax
reporting.
For extreme cases you may need to create a more complex tax setup to meet your tax reporting needs. For example,
currently there are no determining factors that can easily identify asset purchases. In many countries it is a requirement to
report the tax associated with asset purchases separately. In this case, create tax status and tax rate rules based on asset
account segments to uniquely allocate a specific tax status and tax rate to these asset purchases. These asset purchases
can then be reported by searching for the specific tax status and tax rate or specific tax reporting codes associated with the
specific tax status or tax rate.
567
Implementation
Related Topics
• Tax Determining Factor Sets and Condition Sets: Explained
Direct Tax Rate Rules: Explained

Define tax rules on an exception basis to handle requirements that cannot be addressed by foundation tax setup. You can
define tax status rules, tax rate rules, direct tax rate rules, account-based direct tax rate rules, or tax classification-based
direct tax rate rules to derive the applicable tax rate.
The tax determination process uses direct tax rate rules to determine tax applicability, tax status, and tax rate. The tax
determination process uses a tax rate rule to determine the tax rate once the tax status is determined. A direct tax rate
determination rule is a good choice if there are specific requirements to drive a specific tax, tax status, and tax rate and no
variation in tax status or tax rate is required.
Tip
If tax applicability is not impacted by a tax law but the tax rate is you can set up a tax status rule to point to a
different tax status and utilize a default tax rate associated to that tax status. If the tax status does not need to be
unique a tax rate rule can drive a specific tax rate but keep the tax applicability and tax status based on existing
rules.
Direct Tax Rate Determination

Use the Direct Tax Rate Determination rule type for situations where you do not need to create separate tax rules for tax
applicability, tax status, and tax rate. The following must occur for a Direct Tax Rate Determination rule to be applicable:
• The Direct Tax Rate Determination rule must evaluate to true

• The tax rate code must be defined for the product family
• The place of supply must evaluate successfully except in the case of migrated taxes when Allow multiple
jurisdictions is selected
If a Direct Tax Rate Determination rule is not evaluated successfully, then Determine Tax Applicability rules are processed to
determine if tax is applicable. If the tax is not applicable then the determination process ends for tax.
Account-Based Direct Tax Rate Determination

Account-based rules are direct rate rules that are driven by the line account of the transaction. A matching account drives
the applicability, tax status, and tax rate defined on the tax rule. These tax rules are only applicable when the regime
determination method is Determine applicable regimes and the configuration owner tax option for the event class has
the Enforce from account option selected. These tax rules are evaluated after standard applicability rules. If a standard
applicability rule evaluated the tax to Not applicable then it cannot be applicable through an Account-Based Direct Tax Rate
Determination rule.
Tax Classification-Based Direct Tax Rate Determination

Use the Tax Classification-Based Direct Tax Rate Determination rule when the regime determination for the configuration
owner tax option is defined as STCC (standard tax classification code). This setup is primarily intended for migrated tax
classification codes, specifically tax classification groups. The tax classification code populated on the transaction line drives
the tax determination and tax rate directly. A default tax rate associated to a tax rate code is not applicable in this case. Tax
classification codes are created automatically as user-extensible lookup codes when you save a tax rate definition. The Tax
Classification-Based Direct Tax Rate Determination rule is an extension to an existing migrated configuration where the tax
calculation was based on tax classification codes.
568
Implementation
Tax Setup Components in the Tax Determination Process:

How They Are Used
The tax determination process uses your tax configuration setup and the details on the transactions to determine which taxes
apply to the transaction and how to calculate the tax amount.
How Tax Is Calculated Using Tax Setup Components

Each step of the tax determination and tax calculation processes requires the completion of a certain number of setup tasks.
The number and complexity of your setups depends upon the requirements of the tax authorities where you do business.
569
Implementation
This table describes the order of tax determination processes that Oracle Fusion Tax uses to calculate taxes on transactions.
Use this table to review the details of each process and to identify the setups that you need to complete for each step in the
tax determination and tax calculation process.
Order Process Name Activities Components Used

and Rule Type (if
Applicable)
1 Determine Applicable • Determine the • Party tax profile

Tax Regimes and first party of the
Candidate Taxes transaction. • Regime
(preliminary step) determination set
• Identify location
types to derive • Configuration
candidate tax options
regimes.
• Identify tax
regimes.
• Identify taxes
using subscriber
configuration
option.
2 Determine Place • Identify location • Tax rule: Determine

of Supply and Tax type. Place of Supply, or
Jurisdiction the default value for
• Identify tax Place of Supply for
jurisdiction. the tax.
3 Determine Tax • Consider candidate Tax rule: Determine

Applicability taxes from the Tax Applicability and
previous process. the default value for
applicability for the tax.
• Eliminate taxes
based on tax
applicability rule for
each tax.
4 Determine Tax Determine the party type • Tax rule: Determine

Registration to use to derive the tax Tax Registration, or
registration for each the default value for
applicable tax. the tax.

• Party tax profile
570
Implementation
and Rule Type (if
Applicable)
• Tax registration
5 Determine Tax Status • Consider tax Tax rule: Determine Tax

statuses of Status, or the default
applicable taxes. value defined for the tax.

• Consider tax status
rules or use default
tax status.
6 Determine Tax Rate • Consider tax rates • Tax rule: Determine

of each applicable Tax Rate, or the
tax status of each default value
applicable tax. defined for the
tax status derived
• Determine the tax in the previous
rate code to use process.
for the tax status,
for each applicable • Tax rates
tax.
• Product tax
• Determine the tax exceptions
rate percentage or
per-unit tax amount • Customer tax
for a quantity exemptions
based tax.
• If a tax exception
applies, update the
tax rate for each
applicable tax.
• If a tax exemption
applies, update the
tax rate.
7 Determine Taxable Basis • Identify the taxable • Tax rule: Determine

basis formula for Taxable Basis, or
each applicable the default value for
tax. the tax.
• Determine the • Taxable basis

taxable basis and formula
compounding
details based on • Tax inclusive
the taxable basis settings at the tax
formula. rate level
571
Implementation
and Rule Type (if
Applicable)
• Consider the tax
inclusive settings
of the applicable
taxes.
8 Calculate Taxes • Identify the tax • Tax rule: Calculate

calculation formula. Tax Amounts
• Calculate taxes • Calculate tax

using the tax formula, if
calculation formula. applicable
• Perform applicable • Tax rounding

tax rounding. rule from tax
registration, party
tax profile, or tax
• Configuration
owner tax options
If tax recovery is Determine Recovery • Allocate tax • Tax rule: Determine

applicable Rate amount per item Recovery Rate, or
distributions. the default value
defined for the tax.
• Determine tax
recovery types. • Tax recovery rates
• Determine tax
recovery rates.
• Determine the
tax recoverable
amounts.
• Determine the
nonrecoverable
amount.
Tax Rule Qualifiers: Explained

Tax rules that have a rule qualifier are used only when the qualifier matches with the transaction line. Use the tax rule qualifiers
to restrict or apply specific tax rules to an event or geography.
572
Implementation
Event Qualifiers
The event qualifier is of two types: normal event and tax event.
Normal events comprise of the following events:
Event Name Oracle Fusion Application Name
Credit Card Expenses Expenses

Employee Expense Report Expenses

Expense Report Payables

Standard Invoices Payables

Prepayment Invoices Payables

Purchase Order and Agreement Purchasing

Change Orders Purchasing

Debit Memo Receivables

Invoice Receivables

Credit Memo Receivables

The event class qualifiers have a direct affect on the evaluation order of tax rules. The following list summarizes the affect:
1. When a normal event-based qualifier is used then it is used in preference to tax rules qualified by tax event qualifiers
or other nonevent-based qualified tax rules regardless of the rule priority.
2. When multiple normal event-based qualified tax rules are applicable, the application uses rule priority to define the
rule processing order.
3. When a tax event based qualifier is used then it is used in preference to other nonevent-based qualified rules
regardless of rule priority.
4. When multiple tax events-based qualified tax rules are applicable, the application uses rule priority to define the rule
processing order.
5. When no event-based qualifier, normal event or tax event-based, is used, tax rule evaluation is used for rule priority
order.
6. When a geography qualifier is used, it does not affect the tax rule evaluation order. That is, tax rules are evaluated
based on the above points regardless of whether a geography qualifier is used or not.
573
Implementation
The following table considers five tax rules, namely, A, B, C, D, and E with or without event qualifiers and rule order and the
resulting evaluation sequence:
Tax Rule Normal Event Tax Event Rule Order Evaluation

Qualified Qualified Sequence
A Yes No 100 2

B Yes No 50 1

C No No 10 5

D No Yes 20 3

E No Yes 30 4

Rule B is evaluated first because it is the highest priority rule with a normal event rule qualifier. Rule A is identified as second in
evaluation sequence it is the only other tax rule with a normal event rule qualifier. Rule D is third in evaluation sequence as it is
the highest priority rule with a tax event rule qualifier followed by rule E as the only other tax rule with a tax event rule qualifier.
Finally, the application evaluates rule C as it does not have any event rule qualifiers.
The use of normal event or tax event rule qualifiers alters the way in which the tax determination process processes the tax
rules. For an event class qualified tax rule, normal event or tax event-based, the tax rule is evaluated first in preference to tax
rules qualified by tax event qualifiers or a nonevent class qualified tax rule of higher priority.
Consider that you have two rules: rule A and rule C with rule priority 100 and 10 respectively. The rules are associated with
condition sets that match against the transaction line details. Rule A has a normal event class qualifier which is satisfied while
rule C does not have an event class qualifier, rule A is processed and used first regardless of the rule priority order, even
though rule A has a lower priority than rule C.
Tax rules qualified by tax event qualifiers are processed after normal event qualified tax rules but before tax rules with no
event or tax event qualifiers. When there are two or more rules with normal event class qualifiers that match the transaction
line details, the application uses rule priority to determine the order in which the tax rules are processed.
Note
Geography qualifiers do not function in this way. When a tax rule has a geography qualifier and no event class
qualifier, the tax determination process processes the tax rules based on the rule priority against other tax rules
that do not have any tax event rule qualifiers.
Geography Qualifiers
Enable the Set as geography specific rule option to use the geography qualifier. Once you enable this option you can enter
either a normal geography or a tax zone geography.
When you use a normal geography, select the parent geography type and parent geography to help restrict the list of
geography type and subsequently, the geography name fields. For example, when you want to select counties for a specific
state such as California, define the:
• Parent geography type as State

• Parent geography name as CA (California)
574
Implementation
• Geography type as County
This limits the list of values for the geography name field to the counties that are in the state of California instead of listing all of
the counties.
Tip
When selecting the normal geography qualifiers, use the parent geography to ensure that the correct geography
element is selected, as there are many multiple geography elements with the same name across the world. For
example, Richmond is a city in Canada's provinces of British Columbia, Ontario, and Quebec. Richmond is also a
city in the state of Virginia in the United States.
Order of Processing Within a Rule Type: How Tax Rules Are

Evaluated
During tax determination processing, Oracle Fusion Tax considers the tax rules belonging to each rule type in the order that
you defined them.
How Tax Rules Are Evaluated

The sequence of tax rules evaluation is:
• Generally, you define tax rules for a configuration owner, tax regime, tax, and rule type. If a tax regime is subscribed
to an entity as Common configuration, all the tax rules you defined for the Global configuration owner
are considered for rule evaluation. If it is subscribed as Party-specific configuration or Parent first-party
organization, then only the tax rules you defined for that entity or the reference entity are considered. If it is
Common configuration with party overrides then all the tax rules you defined for the entity as well as for the
Global configuration owner are combined and evaluated in the order specified. If the effective dates of a tax rule
does not cover the transaction date or if it is disabled, then the tax rule is ignored during rule evaluation.
• From the previous listed rules, if one or more tax rules belonging to a tax regime, tax, and rule type are defined for a
normal event class or tax event class, then such rules are evaluated first by normal event class and then by tax event
class regardless of the overall rule order. If more than one event class rule is listed for a rule type, then such set of
rules are further sequenced according to their corresponding rule orders
• Further to the previous sequencing, if one or more tax rules belonging to a tax regime, tax, and rule type are defined
for a tax event class, then such rules are next sequenced for evaluation, regardless of the overall rule order. If more
than one tax event class rule is listed for a rule type, then the set of rules are further sequenced according to their
given rule order.
• Finally, the tax rules belonging to a tax regime, tax, and rule type are listed according to their defined rule order for
evaluation.
While processing each tax rule in the evaluation sequence, the tax determination process evaluates the condition sets defined
within a tax rule according to the defined condition set order sequence. If a condition set criteria does not match with the
transaction details, the tax determination process evaluates the next condition set. If none of them match with the transaction
details, the next rule within the ordered rule set is considered. If a condition set criteria matches with the transaction details,
then the tax determination process considers the rule result defined against that condition set and the tax rule is marked as
successfully evaluated. If none of the defined rule conditions match the transaction details, then the tax determination process
considers the default result defined for that tax.
Example
The following is an example of a tax regime that is subscribed to by a business unit with common configuration treatment.
To meet the tax law requirements to determine the tax rates, the following tax rate rules are defined against the global
575
Implementation
configuration owner. The details shown below are a summary of the rate rules including rule order, geography specific details,
associated conditions sets, and the rate results associated to these condition sets:
Rule Order Normal Geography- Condition Condition Result

Event Class Specific Rule Set Set Order
10 Blank Blank • CS-1 • 10 • VAT10%

• CS-2 • 20 • VAT12%
• CS-3 • 30 • VAT15%
20 Purchase • Location CS-4 10 VAT12.5%

invoice type: Bill
from
• Geography
name:
California
30 Purchase Blank CS-5 10 VAT13%

invoice

Scenario 1
If a Payables invoice is involved and Texas is the bill-from party state, the tax rule processing sequence is as follows:
1. The tax rules are listed according to the sequencing logic. For example, the tax determination process evaluates tax
rules involving normal event class qualifiers first regardless of having a lower rule order.
2. The tax determination process further evaluates condition sets listed within each tax rule.
The tax determination process is represented as follows:
Rule Normal Geography- Condition Condition Result Evaluation Result

Order Event Specific Set Set Status
Class Rule Order
20 Purchase • Location CS-4 10 VAT12.5% • Condition Move to

invoice type: set: next tax
Bill Not rule
from evaluated
• Geography • Tax
name: rule:
California Fail,
because
the
bill-
from
party
576
Implementation
Class Rule Order
state
is
Texas
30 Purchase Blank CS-5 10 VAT13% • Condition Condition

invoice set: set result
Evaluated considered
and and
passed exit rule
evaluation
• Tax
rule:
Passed,
because
the
condition
set
values
match
with
the
transaction
details
10 Blank Blank • CS-1 • 10 • VAT10%

• CS-2 • 20 • VAT12%
• CS-3 • 30 • VAT15%
Scenario 2
If a Receivables invoice is involved, the tax rule processing sequence is as follows:
1. The tax rules are listed according to the sequencing logic. For example, the tax determination process evaluates tax
rules involving normal event class qualifiers first regardless of having a lower rule order.
2. The tax determination process further evaluates condition sets listed within each tax rule.

Class Rule Order
20 Purchase • Location CS-4 10 VAT12.5% • Condition Move to

invoice type: set: next tax
Bill Not rule
from evaluated
577
Implementation
Class Rule Order
• Geography • Tax
name: rule:
California Fail,
because
the
event
class
criteria
does
not
match
30 Purchase Blank CS-5 10 VAT13% • Condition Move to

invoice set: next tax
Not rule
evaluated
• Tax
rule:
Fail,
Passed,
because
the
event
class
criteria
does
not
match
10 Blank Blank • CS-1 • 10 • VAT10% For For

CS-1: CS-1:
• CS-2 • 20 • VAT12% Move
• Condition to next
• CS-3 • 30 • VAT15% set: condition
Fail set

• Tax For
rule: CS-2:
In Condition
process, set result
because considered
the and
condition exit rule
set evaluation
values
do
not
match
with
578
Implementation
Class Rule Order
transaction
details
For
CS-2:
• Condition
set:
Pass
• Tax
rule:
Pass,
because
the
condition
set
values
match
with
transaction
details
Setting Up Tax Rules: Points to Consider

The performance of the tax determination process is in inverse proportion to the number of tax rules and conditions that the
process needs to evaluate in order to arrive at a specific result.
Creating Tax Rules

Use these guidelines and examples to help plan your tax rules implementation:
• If the tax condition results and rule results always equal the default values, then you do not need a tax rule. You only
need to define a tax rule for a result that is different from the default value. For example, if more than one tax rate is
possible for a given tax and tax status, then you need to create at least one tax rule.
These qualifications apply to tax rules and default values:
◦ If you require many different results other than the default value for a given tax and rule type, it probably means
that the default value itself sometimes applies. In these cases, you should also define a tax rule for the default
value. Otherwise the tax determination process must always process and eliminate the tax rules defined for all
other values before arriving at the default.
◦ As an alternative to defining a tax rule for the default value, you can assign the least frequent result as the
default value. The tax determination process processes the maximum number of tax rules on the minimum
number of occasions. In this kind of an implementation, you must ensure that your tax rules and conditions
cover all of the more common results in order to prevent the tax determination process from using an incorrect
result as a default.
• If more than one tax rate is possible for a given tax this may be a consideration for a tax rule.
579
Implementation
• If you define multiple tax rules to derive distinct results for a process, assign the least frequent result as the default
value for the process. The most frequent value should be the first tax rule. There are occasions for the default to be
the most frequent value so you may want to define tax rules for exceptions, such as by item. In general, define tax
rules for exceptions, but if there are a lot of tax rules that you need to define, then you may want to define a tax rule
for the most common scenario to avoid processing all of the exceptions.
• When you define tax rules consider the need to repeat tax conditions in multiple rule types if the condition is part of
the applicability evaluation. For example, if you define a Determine Tax Applicability rule for UK VAT that only applies
when ship to is equal to United Kingdom, then you do not need to repeat this condition in a tax rule for a subsequent
tax determination process, such as a Determine Tax Status rule.
• Where possible, use the tax rule header information instead of creating tax conditions that arrive at the same result.
For example, if tax rules apply to the Purchase business process, set the tax event class to Purchase transaction
rather than defining a tax condition within the tax rule, such as tax event class is equal to Purchase transaction.
• When you order the tax condition sets within a tax rule, assign the higher priority to the set of conditions that occurs
more frequently. Similarly, when you order the tax rules within a rule type and tax, assign the higher priority to the tax
rule that gives the most frequently arrived at process result.
• Use product tax exceptions for special rates based on product fiscal classifications rather than defining a Determine
Tax Rate rule based on product fiscal classifications. For example, if three out of five product fiscal classifications
use a special rate, define three product tax exceptions based on the three product fiscal classifications that need a
special rate, and set the standard rate as the default rate.
• Define the minimum number of tax conditions necessary for a tax rule. For example, if a special rate applies to goods
shipped outside a state as opposed to within a state, define one tax condition as ship from state is not equal to ship
to state, rather than defining two separate tax conditions for each ship from and ship to location, such as ship from
state is equal to Nevada and ship to state is not equal to Nevada.
• Consider the reusability of determining factor sets during the creation process. Any determining factor not set as
required in the determining factor set definition can be set to ignore in the condition set so you do not have to
define the condition and it is not evaluated. This allows flexibility in the condition set definition not requiring a unique
determining factor set for every variation in condition set logic.
• For tax rules that involve the shipping to and from a tax zone, for example the European Union, define a tax condition
for all ship to countries within the tax zone rather than separate tax conditions for each country, such as ship to is
equal to Great Britain, ship to is equal to France, and so on.
• For tax rules that apply to a specific geographic area, define tax rules with the additional context of the geographic
area rather than adding location-based equal to tax conditions. For example, if you have a tax rule that only applies if
the ship to state is California, then define the tax rule such that it is only evaluated when the ship to state is California.
You can do this by associating geography during the first step of the tax rule definition at the tax rule header level.
• Define tax rules that are common across all legal entities or business units under the global configuration owner,
instead of creating the same tax rules for each legal entity or business unit. If all tax rules are not commonly
applicable to all legal entities or business units, then:
◦ Set the configuration option of the legal entities or business units that require additional rules to Common
configuration with party overrides
◦ Define supplementary party-specific rules under the applicable legal entities or business units. You can set
priority values for party-specific rules that complement the tax rules of the global configuration owner, in
accordance with the tax requirements.
Turning Tax Regulations into Tax Rules: Example

This example illustrates how to set up tax rules based on tax regulation in the Her Majesty's Revenue and Customs (HMRC)
VAT guide. It provides the detailed business conditions under which goods can be reverse charge (self-assessment) as part
of the Intra-EU Supply legislation.
580
Implementation
Scenario
You are a UK business registered for VAT in the UK. You purchase goods from other European Union (EU) countries and
therefore fall under the HMRC Tax Regulation Intra-EU Purchase of Goods legislation.
HMRC Tax Regulation

According to the HMRC VAT guide, if you purchase goods from a VAT-registered business in another EU country, and the
goods are moved to the UK, then you may be required to account for VAT in the UK on the acquisition of goods. This VAT
can be recovered as input tax on the same VAT return, subject to the normal rules for reclaiming input tax.
Analysis
Analyze the text of the legislation and identify the key phrases in the legislation.
The following figure shows an extract of the UK HMRC VAT guide regarding the Intra-EU Supply legislation.
581
Implementation
Break these phrases down into product, party, process, and place determining factors that describe under what conditions
the legislation is applicable. Look at the legislation and identify what is the outcome when the legislation is applicable and
determine which rule types are appropriate.
The following figure shows these determining factors and rule types in detail and how you can turn them into expressions that
can be modeled in Oracle Fusion Tax.
This table describes the phrases identified in this tax legislation as represented in the previous figure:
Legislation Phrase Text Requirement
1 If you purchase goods... The tax rule is limited to purchase

transactions.

582
Implementation
Legislation Phrase Text Requirement
2 ...from a VAT-registered The tax rule requires that the

business in another European supplier be registered in another
Community country... EU country.

3 ...and the goods are removed... The tax rule is limited to the Goods
product type.

4 ...are removed to the United The tax rule refers to goods

Kingdom... delivered to the United Kingdom
from another country in the EU
country.

5 ...you may be required to The party must reverse charge

account for... (self-assess) the tax.

6 ...for VAT in the United The tax is UK VAT.

Kingdom...
Resulting Tax Rules

Legislation Phrase 1
Tax legislation phrase 1 indicates that the determining factor that defines this specific tax rule is only applicable to purchase
transactions. This equates to a tax event class equal to purchase transactions. Use a tax event class rather than an event
class as the tax event class covers other products in the procure-to-pay flow. This covers Oracle Fusion Payables and Oracle
Fusion Purchasing processing with a single approach.
583
Implementation
The following figure shows that the determining factor that defines this specific tax rule is only applicable to purchase
transactions.
This table describes the contents of the tax condition set as represented in the previous figure:
Legislation Phrase Determining Factor Operator Value

Name
1 Tax Event Class Equal to Purchase transaction

Tip
Always look for the most generic approaches that cover more of the business requirements in a single tax rule.
For example, here the tax event class is used instead of a specific event class for Payables transactions and
another similar rule for Purchasing transactions.
It is determining factors like this that allows you to define tax rules that are only applicable to specific types of transactions.
The previous approach allows you a convenient way of splitting order-to-cash and procure-to-pay transactions. By using
event class you can make a more detailed refinement so that tax rules are only applicable to specific product transactions.
This flexibility drives the simplification of combining procure-to-pay tax setup with order-to-cash tax setup into a single model.
In the majority of cases you do not need to distinguish between procure-to-pay or order-to-cash transactions within the tax
rules, however, where there is a need create specific procure-to-pay or order-to-cash tax rules using this key design concept.
Tax legislation phrase 2 indicates that the determining factor that defines the supplier is registered in another EU. There are
several ways of modeling this but the approach that is recommended for you to take is to use a registration status on the tax
registration record set up for the GB tax regime. It is also recommended that a business process is in place and documentary
evidence retained to show that the supplier is validated as a true supplier registered in another EU country. Until you complete
this manual business process the supplier should not be marked with the registration status of registered in another EU
country.
The following figure shows the determining factor that defines that the supplier is registered in another EU country.
584
Implementation
Legislation Determining Class Qualifier Operator Value

Phrase Factor Name
2 Registration Status of supplier Equal to Registered in

another EU
country

Tip
Always look for approaches which coupled with business procedures provide the necessary controls. In this case
it is recommended that you devise and implement a business procedure to ensure that sufficient level of checking
is done before the supplier or supplier site tax registration record is created and that the correct registration status
entered. This business procedure ensures that the supplier is a valid supplier and that their tax registration number
is a valid tax registration number.
Tax legislation phrase 3 indicates that the determining factor that defines the product type is goods. Another way of modeling
this is to use a product fiscal classification which can automatically be derived from the item defined on the transaction.
However, in this case if an item is not specified on the transaction, for example in an unmatched purchase invoice being
processed, then there is no product fiscal classification derived. You need to create additional tax rules and setup to address
this situation.
The following figure shows the determining factor that defines that the product type is goods.
585
Implementation
Legislation Phrase Determining Factor Operator Value

Name
3 Product Type Equal to Goods

Tip
Always look for an approach which provides an automated process that covers as many transactions as possible.
For example, by using product type of Goods rather than a product fiscal classification then unmatched Purchase
invoice tax processing can also be covered by this one tax rule.
Tax legislation phrase 4 indicates that the determining factors that define the supply is from another EU country. This is
modeled by:
1. Goods are being shipped to UK
2. Goods are being shipped from an EU country
3. The shipped from country is not UK
You can take items 2 and 3 to ensure that the goods are being sent from another EU country outside the UK.
The following figure shows the determining factor that defines the supply is from another EU country.
586
Implementation

Phrase Factor Name
4 Country of ship to Equal to United Kingdom

4 Economic Region of ship from Equal to European

Economic
Community

4 Country of ship from Not equal to United Kingdom

587
Implementation
Tip
Geography and tax zones are powerful features of Oracle Fusion Tax and you should use them wherever possible
to identify tax jurisdictions and geography requirements in general. Use the geography or tax zone information for
tax reporting instead of trying to build geography information into concepts such as tax rates. For example, use
tax jurisdictions, such as over sea tax territories based on tax zone, to identify specific territories needed for tax
reporting rather than creating specific tax regimes, taxes, tax statuses, and tax rates.
Legislation Phrases 5 and 6

Tax legislation phrase 5 indicates how the determining factors discussed previously are brought together as the basis for
the Tax Registration tax rule which identified that the bill-to party registration be used in preference to the normal default bill-
from party registration. It is this bill-from party registration that triggers the reverse charge (self-assessment) for the type of
transaction.
Tax legislation phrase 6 indicates how the determining factors discussed previously are brought together as the basis for the
Place of Supply tax rule. This tax rule changes the normal place of supply to be the ship-to location, which in the context of
this setup means that at least for the reverse charge (self-assessment) side of this transaction it is deemed to have occurred
in the UK.
The following figure shows how you can bring together the determining factors discussed previously as the basis for the Tax
Registration and Place of Supply tax rules.
588
Implementation
This table describes the contents of the tax condition set for the Tax Registration and Place of Supply tax rules as
represented in the previous figure:

Phrase Factor Name
5 and 6 Tax Event Class Equal to Purchase

transaction

5 and 6 Registration Status of supplier Equal to Registered in

another EU
country

5 and 6 Product Type Equal to Goods

589
Implementation
Phrase Factor Name
5 and 6 Country of ship to Equal to United Kingdom

5 and 6 Economic Region of ship from Equal to European

Economic
Community

5 and 6 Country of ship from Not equal to United Kingdom

Tip
From this example you can see that a simple Tax Registration tax rule and Place of Supply tax rule is all that is
needed to define what is a complex scenario for the purchasing of goods from a another EU country, not the UK,
from an EU registered supplier by a UK registered business. The other tax rules that are used if these goods are
purchased in the UK, are the normal tax rules such as Tax Status, Tax Rate, and Tax Recovery tax rules.
FAQs for Manage Tax Rules

What's the difference between using tax exemptions or tax rules to modify the taxable
nature of a transaction?
You can modify the taxable nature of a transaction using tax exemptions, but you can also accomplish this through the use
of tax rules. Use tax rules, such as the Determine Tax Applicability rule, to exclude certain categories of transactions from
taxation. If you choose to implement tax rules to achieve your tax exemption requirements, the impacted transactions do not
appear on many tax reports as they do not have any tax lines.
If you must report on a transaction then set up a tax exemption on the customer's party tax profile which results in a tax
line being created with the modified tax rate. Use tax exemptions where certificates of exemption are issued for specific
customers, which is typical in tax regimes for US Sales and Use Tax.
You can create an exempt tax rate with a zero percentage rate as a method of applying exemptions. This achieves many of
the intended reporting objectives as the application generates a tax line. Reports that specifically refer to an item as exempt
may exclude items with a zero percentage rate from that portion of the report because the exempt indicator is blank.
If you define an exempt tax with a zero tax rate, the transaction shows as fully taxable on all reports. If you want reports to
show the full line amount as taxable you cannot add any exemption details, such as exempt reason codes, as this results in
an exemption being created on the customer record and a zero taxable amount on the reports.
Manage Tax Registrations
Setting Up Tax Registrations: Points to Consider

You must set up a separate tax registration to represent each distinct registration requirement for a first party. Optionally,
set up tax registrations for your customers and suppliers, as necessary, to support specific tax regulations or reporting
requirements. Oracle Fusion Tax uses tax registrations in tax determination and tax reporting.
590
Implementation
Tax Registration Options

Setting options at the tax registration level can override options set at different levels. The following table describes selective
options available and the impact of selecting these options:
Option Description Impact
Tax Regime Enter the tax regime for this The tax regime and optionally,
registration. Optionally, enter the tax and tax jurisdiction are used
tax and tax jurisdiction for this to determine the correct tax
registration. registration at transaction and
reporting time.

Registration Type If applicable, select a classification The predefined tax registration

of the tax registration. types are specified by the tax
authority. The tax registration types
are for reporting purposes only.

Registration Number Enter the company tax registration Where applicable, Oracle Fusion
number assigned by the tax Tax validates the number according
authority. to tax authority validation rules.
If you set the tax regime option to
use the legal registration number
as the tax registration number, then
select the registration number from
the legal registration numbers in the
list of values.
If you set the Allow duplicate tax
registration numbers option for
the tax, then multiple parties and
party sites can use the same tax
registration number for this tax.
Registration Status Enter the party's tax registration Use the tax registration status as a
status. Oracle Fusion Tax provides determining factor in tax rules.
these predefined registration
statuses:
• Agent: The party acts as a

withholding agent for the tax
authority for the applicable
tax.
• Registered: The party is

registered for the applicable
tax.
• Not registered: The party

is not registered for the
applicable tax.
591
Implementation
Source Identify if this party is: If the source is Explicit the tax
registration number is required.
• Explicit: The party is If the source is Implicit the tax
registered with the local registration number is not required.
tax authority and has a tax
registration number. In this
case, you know that the party
is registered and the details
including the tax registration
number.
• Implicit: The party is not

formally registered with the
tax authority, but the party
is considered to meet one
or more requirements for
reporting taxes because
of the level of business
conducted. In this case, you
determine that the party is
registered but you do not
know the tax registration
number.
Rounding Rule The rule that defines how the At transaction time, the values set
rounding should be performed at the tax registration level override
on a value involved in a taxable the values set at the party tax
transaction. For example, up to the profile level.
next highest value, down to the
next lowest value, or nearest.

Set as self-assessment (reverse Set to automatically self- You can set the self-assessment
charge) assess taxes on procure-to-pay option at the tax profile level to
transactions. A self-assessed tax default to the tax registrations that
is a tax calculated and remitted you create for this party. You can
for a transaction, where tax was also set it at the tax registration
not levied by the supplier but is level or on an individual tax line.
deemed as due and therefore,
needs to be paid by the purchaser. Oracle Fusion Tax applies self-
assessment to Payable invoices
received by the first party according
to the tax registration setting. The
specific tax registration record is
derived either from the Determine
Tax Registration rules or from the
default tax registration.

592
Implementation
Set Invoice Values as Tax Select if this party intends to send At transaction time, the values
Inclusive or receive invoices with invoice line set at the tax registration level
amount inclusive of the tax amount. override the values set at the party
tax profile level. In addition, this
option at the tax registration level
overrides the tax inclusive handling
setting at the tax level, but not at
the tax rate level.

Collecting Tax Authority and Enter the name of the tax If defined, the reporting and
Reporting Tax Authority authorities for: collecting tax authorities appear as
defaults from the tax jurisdiction
• Collecting Tax Authority: associated with this registration. If
The tax authority necessary, enter or update these
responsible for managing fields with tax authorities specific to
the administration of tax this tax registration.
remittances.
• Reporting Tax Authority:

The tax authority responsible
for receiving and processing
all company transaction tax
reports.
Tax Registrations: Explained

A tax registration contains information related to a party's transaction tax obligation with a tax authority for a tax jurisdiction
where it conducts business. In some cases a single location may need to file multiple registrations. Set up tax registrations for
your first-party legal reporting units and your third-party customers and customer sites and suppliers and supplier sites.
Registering the details of a business with the relevant tax authorities is a key legal requirement in many countries. A unique
tax registration number is generally assigned to the parties registering with the tax authorities and is used as a basis for
referencing and tracking the tax implications on that party. To enable this process, the registration numbers of the parties
involved in a transaction are generally referred to in tax documents like invoices and tax returns. In some cases, the tax
determination and its administration is also dependent on the nature of the registration of the parties involved in a transaction,
such as the requirements associated with intra-European Union (EU) reverse charge.
Setting Up a Tax Registration

You must set up a separate tax registration to represent each distinct registration requirement for a first party. You optionally
set up tax registrations for your third parties, as necessary, to support specific tax regulations or reporting requirements.
You can define tax registrations at three different levels of detail. At the:
• Tax regime level: The tax registration is used for all taxes and tax jurisdictions within the tax regime.
• Tax level: The tax registration is used for all tax jurisdictions where the tax regime and tax are applicable.
• Tax jurisdiction level: The tax registration is applicable for the locations covered under the tax jurisdictions defined for
the tax regime, tax, and tax jurisdiction.
593
Implementation
For each tax that you create, you must define either a default tax registration or a tax rule for the rule type Determine Tax
Registration. If a party has more than one tax registration under the same tax regime, then the tax determination process
considers the tax registrations in the order: tax jurisdiction; tax; and tax regime.
For some countries, the application performs a validation of the registration number you enter per the country algorithm.
You can define tax registrations as implicit. For example, the party is not formally registered with the tax authority, but the
party is considered to meet one or more requirements for reporting taxes because of the level of business conducted,
typically a minimum presence in the country and a minimum revenue threshold. Also, you can define the tax registration
with a status of not registered if the party is not registered for the applicable tax, but you want to use it as a tax condition
to process the tax rules. Similarly, you can use user-defined values and statuses, such as registered in EU but not UK, to
facilitate certain tax conditions. Apart from the core tax registration information, you define additional details to facilitate tax
processing. The invoice control attributes such as self-assessment and tax inclusiveness play a key role in tax processing. At
transaction time, the values set at the tax registration level override the values set at the party tax profile level.
Using Tax Registrations in the Tax Determination Process

The Determine Tax Registration process determines the party whose tax registration is used for each tax on the transaction,
and, if available, derives the tax registration number. Once the process identifies the tax registration or registrations, it stamps
the transaction with the tax registration numbers.
You can use the registration status to define various tax rules. For example, if the tax is applicable only if the supplier is
registered, define the tax applicability rule as follows:
• Determining factor class = Registration
• Tax class qualifier = Ship-from party
• Determining factor name = Registration Status
• Operator = Not equal to
• Value = Registered
• Result = Not applicable
On the detail tax lines, the tax determination process stamps two registration numbers. One is for the headquarters, the main
legal reporting unit of the legal entity of the document. The other is for the party or party site identified by the tax registration
rule. For example, if the registration rule has identified ship to as a party, then the tax determination process stamps the
registration number of the ship-to party on the transaction.
The tax determination process also considers these details of the derived tax registration for each tax:
• Tax inclusive handling: The inclusive option set at the tax registration level for the party identified by the tax
registration rule overrides the inclusive option set at the tax or party tax profile level for the tax line.
• Self-assessment (reverse charge) setting: The tax determination process considers the tax line as self-assessed if the
Set as self-assessment (reverse charge) option is selected at the tax registration level for the party identified by
the tax registration rule.
• Rounding rule: The rounding rule set at the tax registration level for the party identified by the tax registration rule
overrides the rounding rule set at the tax or party tax profile level for the tax line.
Manage Simulator Transactions
Tax Simulator: Explained

The Tax Simulator is a tool for simulating the tax determination process in your tax setup. The Tax Simulator lets you preview
the workings of your tax configuration before you perform tax calculations on live transactions in a subledger application.
The Tax Simulator also allows you to test new tax configuration in conjunction with existing tax configuration to preview
594
Implementation
the resulting tax calculation. The Tax Simulator is a useful tool to identify the root cause when tax calculation is not what is
expected on live data.
Run taxes from all applicable tax regimes against a sample transaction to verify that your tax configuration and tax rules were
created and applied according to your requirements. You can either create a sample transaction within Tax Simulator or copy
an existing transaction. The simulated tax calculations do not affect live data.
Principle aspects of the Tax Simulator include:
• Functions and verifications
• Analysis tools
• Restrictions
Tax Simulator Functions and Verifications

The Tax Simulator lets you simulate the tax determination process on transactions without creating live data.
The Tax Simulator enables you to complete these functions:
• Enter transactions to simulate tax calculation based on various scenarios.
• Simulate the characteristics of the Payables, Purchasing, and Receivables transactions and create the tax line for
each type of operation.
• View the detail tax lines generated for each transaction line.
• View the tax rules that were applied to a tax calculation and the processed result for each rule type.
The Tax Simulator provides these verifications:
• How the tax rules that you have defined for one or more taxes work in conjunction with the defaults that you have set
for them.
• Whether a tax rule that you expected to have a successful evaluation for a given set of transaction conditions
achieved the desired result.
• How the options that you have set at various levels are reflected in the results of tax determination processing. If a
certain transaction does not process taxes as you predicted, then you can use the simulated result to troubleshoot
the cause. For example:
◦ You thought that there were product tax exceptions, but they were not used on a transaction as expected. You
then discover that the Allow tax exceptions option was not enabled on the applicable tax rate record.
◦ Your supplier record has the option enabled to use offset taxes, but the offset taxes do not appear. You then
discover that the tax rate record does not have an offset tax rate associated with it.
Tax Simulator Analysis Tools

The Tax Simulator provides these pages to analyze the tax calculations on simulated transactions:
• Simulator Transaction page: View the details of the simulated transaction.
• Tax Line Details page: View the calculated tax lines for the simulated transaction. The page displays, for each
transaction line, the applicable tax and tax configuration details, as well as if the result was determined by a tax rule
or the default value. If a tax rule was applied, the page also displays the associated tax condition set.
• Rule Type page: View details of all enabled rules for a rule type. The page displays the processed result for each rule.
The page also displays the associated tax condition sets and their processing details and results.
Tax Simulator Restrictions

The following restrictions apply when using the Tax Simulator:
• Payables tax recovery processing cannot be simulated.
595
Implementation
• Application-specific actions on transactions or transaction lines, such as canceling, deleting, and reversing, are not
tested.
• User control settings are not tested or verified.
Simulating Subledger Transactions: What Is Copied

Copy transactions from Oracle Fusion Payables, Oracle Fusion Purchasing, and Oracle Fusion Receivables and use them
to test the entire tax and related configuration. Once the Tax Simulator copies data into the simulated transaction, you can
update and delete lines as needed.
Settings That Affect Subledger Transactions

Oracle Fusion Tax uses your search criteria defined for the application, legal entity, and business unit to provide a listing of
subledger transactions. The Tax Simulator copies the attributes of the selected transaction and populates them on the Create
Simulator Transaction page.
What Subledger Data Is Copied

The Tax Simulator copies the following data from the subledger transaction:
• Transaction header information, including supplier and customer information

• Tax lines with a line type of line or freight
• Calculated tax amount if you use an external service provider for tax calculation
• Line-level tax attributes
• Discounts and exceptions for Receivables transactions
• Ship-to information for Receivables transactions
The system does not copy:
• Any referencing, applied, or adjusted documents

• Tax-only lines
• Canceled lines
Update and delete lines and attributes as needed. The only fields that you cannot update are the document event class and
source document number.
Simulating Tax on Transaction Data: Explained

The Tax Simulator allows you to validate new and existing tax setup for procure-to-pay and order-to-cash transactions.
The format of the Tax Simulator interface is a lightweight version of the procure-to-pay and order-to-cash respective work
areas allowing ease of data entry and flow of item lines to tax calculation and tax lines. In addition to the required transaction
attributes the additional tax attributes that drive tax calculation are highly visible and available for your entry and update.
Simulated transactions do not impact live data and you can purge them from the application using a process request.
Use the Tax Simulator to create, duplicate, and simulate transactions. The interface also supports associating adjusting,
referencing, and applied documents on applicable event classes. In addition to simulating tax output for live transactions you
can test the tax calculation of taxes that are not yet active and see the standalone tax calculation or the impact of this tax with
taxes that are active. The Tax Simulator provides comprehensive information and a view into the tax processing logic to help
you implement and troubleshoot tax setup. One of the critical uses of the Tax Simulator is for you to be able to safely trigger
transactions without having a detailed knowledge of the core transaction systems or having to create transactions in these
applications that impact the core applications.
596
Implementation
Using the Tax Simulator

The Tax Simulator allows ease of data entry. The flow of transaction entry is similar to the respective work area so you
are familiar with the flow. There is partial page rendering for procure-to-pay and order-to-cash event classes to expose
the appropriate attributes. For example, when you enter a purchase order you are prompted for a supplier. When you
populate the supplier information, the Tax Simulator populates the default ship to and bill to information. When you enter a
Receivables sales invoice event class you are able to enter customer bill to and customer ship to details in a format similar
to the Receivables Invoice work area. Other attributes include warehouse, discounts, and exemptions for Receivables event
classes and line classes for Payables event classes.
The data you enter in the Tax Simulator is not live data, it is not accounted, reported, or visible from other product interfaces.
In addition to manual entry of transaction data, you can copy live data to view or modify in the Tax Simulator. The Manage
Tax Simulator Transactions page allows you to choose a source of Payables, Purchasing, Receivables, or Tax Simulator.
Search on the source of Tax Simulator for transactions entered or copied into the Tax Simulator. The other product sources
allow you to query and copy transactions from the respective subledgers.
For example, you have a Payables invoice where the tax calculation is not what you expect. Use the Tax Simulator to:
1. Search in the Manage Simulator Transactions page for a source of Payables, an event class of Purchase invoice,
and respective business unit, document number, and date information.
2. View the applicable transaction in the Search Results table. If needed there is Query by Example available in the
table for you to further identify the desired transaction.
3. Select the Purchase invoice and click Simulate Transaction to copy this transaction into the Tax Simulator.
4. Review the information on the Create Simulator Transaction page. The application populates the transaction details.
5. Populate the document number with the new number. The source document number is populated with the original
document number. You can update all attributes except the document event class and source document number.
6. Save the document and click View Tax Lines to view the tax output.
If you want to test multiple variations of the same transaction you can query the transaction with a source of Tax Simulator in
the Manage Tax Simulator Transactions page. Select the transaction in the search results and click the Duplicate action to
duplicate the transaction details into a new document leaving the previous transaction details intact.
Using Additional Tax Attributes

In addition to the required fields for transaction entry and tax calculation, such as Document Event Class, Document
Date, Legal Entity, Business Unit, Currency, Supplier, Customer, and Line Amount, the Tax Simulator gives you
visibility into additional tax attributes that are commonly used to drive tax calculation based on tax rules. The Tax Simulator
removes many of the attributes that do not impact tax calculation to simplify the page and let you focus on the needed
elements.
At the header level the Taxation Country is visible for entry and update. At the line level you can enter and update attributes
such as Line Class, Line Type, Item, and Product Type. Additional tax attributes, such as Tax Inclusive, Transaction
Business Category, Assessable Value, Tax Classification, Product Category, Intended Use, Product Fiscal
Classification, User-Defined Fiscal Classification, and Account, are organized in a tabbed region. All of these attributes
can drive tax determination or tax calculation directly based on tax rules and tax formulas. Almost every additional tax
attribute on the Tax Simulator interface directly impacts tax determination and tax calculation in a format that resembles the
work areas so it is easy for you to understand and navigate.
Using Reference, Adjusted, and Applied Documents

Reference, adjusted, and applied documents can have tax calculation impacted by the documents they are associated with.
The Tax Simulator presents information on some of the impacts. Others, such as variances in distributions, are not presented
since accounting is not part of the Tax Simulator functionality. Also, when a document is simulated or copied in the Tax
Simulator, the application does not copy referencing, adjusted, and applied documents. You must copy each document
separately and associate them in the Tax Simulator.
The following is a list of the available event classes and associations that can be made in the Tax Simulator:
597
Implementation
Application Header Item Line Reference, Reference, Reference, Reference,
Level Attribute Adjusted, Adjusted, Adjusted, Adjusted,
Document Line Class and and and and
Event Applied Applied Applied Applied
Class Tab: Tab: Tab: Tab:
Document Document Document Document
Event Number Date Line
Class Number
Payables Standard Invoice Purchase Select the Populated When you

Invoice Order (not purchase when the enter the
required) order document document
document number is number
number. selected of the
and it is purchase
read-only. order
this list is
available
with the
respective
invoice
lines.

Payables Standard Prepayment Prepayment Select the Populated When you

Invoice Invoice prepayment when the enter the
invoice document document
number. number is number
selected of the
and it is prepayment
read-only. invoice
this list is
available
with the
respective
prepay
invoice
lines.

Payables Standard Credit Standard Select Populated When you

Invoice Memo Invoice the credit when the enter the
memo document document
document number is number of
number. selected the invoice
and it is this list is
read-only. available
with the
respective
invoice
lines.

Payables Prepayment Column not Tab not Tab not Tab not Tab not
Invoice displayed displayed displayed displayed displayed

598
Implementation
Application Header Item Line Reference, Reference, Reference, Reference,
Level Attribute Adjusted, Adjusted, Adjusted, Adjusted,
Document Line Class and and and and
Event Applied Applied Applied Applied
Class Tab: Tab: Tab: Tab:
Document Document Document Document
Event Number Date Line
Class Number
Purchasing Purchase Column not Tab not Tab not Tab not Tab not
Order displayed displayed displayed displayed displayed

Receivables Invoice Column not Tab not Tab not Tab not Tab not
displayed displayed displayed displayed displayed

Receivables Credit Column not Invoice Required Populated When you

Memo displayed when the enter the
document document
number is number of
selected the invoice
and it is this list is
read-only available
with the
respective
invoice
lines.

An example of an applied document that impacts tax calculation is that of a Receivables credit memo that references an
invoice. In Receivables there can be standalone credit memos that drive tax calculation based on the tax attributes entered
on the credit memo and there are applied credit memos that drive tax calculation based on the referenced document; the
invoice. If there is a credit memo that is not calculating what you expected in Receivables, you can:
1. Copy the transaction into the Tax Simulator.
2. Simulate each document independently and associate them in the user interface. The Tax Simulator does not copy
associated documents
3. Review the credit memo tax lines independently before the transaction association and see that the tax calculation
is based on the attributes entered on the credit memo.
4. Associate the invoice in the Reference, Adjusted, and Applied tab with the appropriate document number and line
and drill to the tax lines. See that the result type value for the rule results is derived from the reference document.
This is indicating that the tax is not based on the credit memo attributes but those of the invoice.
Enabling Taxes for Transactions and Simulation: Explained

A feature of the Tax Simulator is the option for you to choose the status of the taxes to consider for evaluation. The
transaction header region in the Tax Simulator includes an Evaluate Taxes attribute. The options are: Enabled for
simulation, Enabled for transactions, and Enabled for transactions and simulation.
When you define a tax there are two different statuses the tax can have when the setup is complete. When you select
Enable tax for simulation the tax is available only for processing on Tax Simulator transactions and is not calculated on
599
Implementation
live transactions. When you select Enable tax for simulation and Enable tax for transactions then the tax is considered
active and is available for processing on both live transactions and Tax Simulator transactions.
When you create a Tax simulator transaction and the evaluate taxes status is set to:
• Enabled for simulation: Only taxes with the status Enable tax for simulation are selected for processing.
• Enabled for transactions: Only taxes that are live or have both Enable tax for simulation and Enable tax for
transactions selected on the tax record are considered for processing.
This mimics the behavior of the processing for active taxes in the subledgers and is the default value when simulating
or copying subledger transactions in the Tax Simulator.
• Enabled for transactions and simulation: Both taxes that have a status of Enable tax for simulation and taxes
that have a status of Enable tax for simulation and Enable tax for transactions selected are processed.
This allows you to see behavior of both active and not active taxes on the same transaction. This is a useful tool
when the calculation of one tax can impact another such as in the case of compounding tax formulas for tax
calculation.
Example
You have two taxes defined that both evaluate to true for a particular Purchase invoice.
The first tax, FUS_CA, is defined for the sales tax for the state of California. The tax status is set to Enable tax for
simulation and Enable tax for transactions. The second tax, FUS_ENV, is defined for an environmental tax. The tax status
is set to Enable tax for simulation.
Simulate a live transaction in the Tax Simulator with the Evaluate Taxes option set to Enabled for transactions. In this
case only taxes enabled for transactions are processed so the FUS_CA is the only tax calculated.
Next, update the Evaluate Taxes option set to Enabled for simulation. In this scenario only taxes that are enabled for
simulation are processed so FUS_ENV is the only tax calculated.
Finally, update the Evaluate Taxes option set to Enabled for transactions and simulation. In this scenario both taxes
enabled for simulation and enabled for both simulation and transactions are selected so both FUS_CA and FUS_ENV are
calculated.
Tax Rules Evaluation in the Tax Simulator: Explained

Transactions pass key tax drivers relating to parties, products, places, and processes captured on the transaction to Oracle
Fusion Tax for tax determination. Using these tax driver values as input, the tax determination process performs a series of
process steps utilizing the defined tax configuration, including various tax rules defined for each rule type and calculates the
taxes that are applicable on the transaction. Use the Tax Simulator to preview the workings of your tax configuration before
you perform tax calculations on live transactions in a subledger application.
From the transaction tax details it might not be clearly evident as to which tax rule from your defined tax setup got processed
or if the calculated tax is the result of the relevant rule condition. Using the Tax Simulator you can verify the tax determination
process breakdown, the details of the tax rules that are evaluated for each rule type, and other key factors that are analyzed
and applied during the tax determination process. The Tax Simulator is a tool that allows you to replicate the transaction
details directly or as a copy from the source transaction. The Tax Simulator provides a detailed analysis of the decision criteria
applied in the tax determination process, with reference to the defined tax configuration and displays the corresponding
results for each rule type.
The Tax Line Details page within the Tax Simulator captures and lists out the following key process results that the tax
determination process considers for each tax applied on the transaction:
• The tax determination methodology applied, such as regime determination or standard tax classification codes
600
Implementation
• The rounding criteria applied, including rounding rule, rounding level, minimum accountable unit, and tax precision
• The types of taxes evaluated, for example, those enabled for transactions or enabled for simulation
• The rule evaluation details for each rule type, such as:
◦ Result type, default or rule-based
◦ Rule result
◦ Sequence of the rule evaluation, the successful, unsuccessful and not evaluated tax rules and their
corresponding determining factor sets, condition sets, and detailed condition elements
This abstract gives you a snapshot of the key results returned from each tax determination process step and provides
pointers to validate it against the available tax setup. You can modify the tax setup if the key result areas are not as per the
requirements.
Details for Simulated Transaction Lines: Explained

Use the Tax Line Details page to review the transaction level details that influence all tax lines and view the calculated tax
lines for your simulated transaction. Each tax line for each transaction line number is listed in the Tax Line Details table with
the corresponding tax configuration details. Open the Tax Line Details page by clicking the View Tax Lines button on the
Simulator Transaction pages from the Manage Simulator Transactions task.
Attributes in tax line details include:
• Configuration owner, document event class, and source
• Allow tax applicability
• Regime determination set
• Default rounding level
Configuration Owner, Document Event Class, and Source

The configuration owner identifies the business unit or legal entity on the transaction that owns the tax configuration. For
example, if the business unit is subscribing to the legal entity's data, the legal entity is identified, rather than the business
unit. In order for a tax regime to be applicable on the transaction the configuration owner identified has to subscribe to the
applicable tax regime.
The source attribute can have a value of Event class or Configuration owner tax options. This indicates if the application
derives the event class-specific tax options from a configuration owner tax option that is defined for the combination of
configuration owner, event class, and date range or if the application derives the options from the default predefined values
for the event class. These tax options include the option to calculate tax, the regime determination set, options to allow
manual entry and override, rounding defaults, and details regarding tax calculation on referencing documents. If the value
is Event class then there are no configuration owner tax options defined for this combination of configuration owner,
event class, and date and the predefined values are used including the predefined value of TAXREGIME for the regime
determination set.
Allow Tax Applicability

The two allow tax applicability attributes identify whether the tax configuration setup provides for the calculation of taxes on
this transaction. Both attributes must be set to Yes to calculate tax.
601
Implementation
The two occurrences indicate the following:
• The first occurrence indicates if Allow Tax Applicability is selected on the predefined event class or applicable
configuration owner tax options setup. If you do not set up configuration owner tax options, then the default value is
set to Yes based on the event class mapping. A value of No appears if configuration owner tax options are set up
and the Allow Tax Applicability option is not selected.
• The second occurrence of Allow Tax Applicability validates the hierarchy of tax applicability from the supplier and
supplier site definitions for procure-to-pay transactions, to the party tax profile, and finally to the default option for the
predefined event class. If the Allow Tax Applicability option is not selected at any of the applicable levels then tax
is not calculated. If the Allow Tax Applicability option is selected at a lower level and not selected at a higher level
then tax is not applicable. If the Allow Tax Applicability option is set to No then you can drill down on the link to
see where this option is not selected.
Regime Determination Set

The regime determination set indicates how the application determines the tax regimes to use for this transaction.
There are two values for this attribute:
• When the regime determination set is a value other than STCC (standard tax classification code) it is a determining
factor set of type regime determination that includes transaction input factors of location types to derive the owning
country on the transaction for tax purposes. Tax regimes that you defined for the derived country have taxes
evaluated for calculation. The predefined regime determination set is TAXREGIME and this value always populates
if the source is Event class. Use the drill down to the regime determination set details to identify the precedence of
locations to determine the tax regime country.
• When the regime determination set is set to STCC, the additional tax attribute of Tax Classification set at the Line
Level Tax Attributes tab drives tax calculation either directly or based on the Tax Classification Based Direct Rate
Rules.
For example, if your simulated transaction does not have any tax lines, check the regime determination set value. If it is set
to STCC and the Tax Classification field on the Line Level Tax Attributes tab is blank, tax is not calculated. Review your
application tax options to verify that the defaulting hierarchy that specifies both the sources to use for tax classification codes
and the order in which the application searches these sources to find a valid tax classification code at transaction time.
Default Rounding Level

The default rounding level shows in order of precedence, the party type, source, and rounding level value. At a minimum, a
default value is set. The options are header level or line level rounding. Header level rounding applies rounding to calculated
tax amounts once for each tax rate per invoice. Line level applies rounding to the calculated tax amount on each invoice line.
The rounding rule is the method used to round off taxes to the minimum accountable unit. If there is any concern as to how
rounding is determined or if setup needs to be modified you can use the dialog details in conjunction with party information to
determine where the setup needs to be modified.
For example, on the Rounding Level dialog box for a purchase invoice you see the following:
Rounding Precedence Party Type Source Rounding Level
1 Bill-from party Supplier site

1 Bill-from party Party tax profile Header

2 Bill-to party Supplier site

602
Implementation
Rounding Precedence Party Type Source Rounding Level
2 Bill-to party Party tax profile Line

3 Ship-from party Supplier site

3 Ship-from party Party tax profile Line

4 Ship-to party Supplier site

4 Ship-to party Party tax profile Header

Default Header

The lowest level of 1 takes precedence over all other levels. The application uses, the default precedence only if none of
the other levels are populated. If the value is blank then there is no attribute set at this level. If the you determine that in this
example the bill-from party tax profile rounding level of Header is incorrect you can identify the bill-from party from the Tax
Line Details header information and query the appropriate party tax profile to modify the setup. This example is simple in that
the header level is the level used for rounding. If the value was Line there is more derivation logic starting with the party type
derived for the Determine Tax Registration rule.
Related Topics
• Rounding Precedence Hierarchy: How It Is Determined
Line Level Details for Simulated Transaction Lines: Explained

Use the Tax Line Details page to review the calculated tax lines with the corresponding tax configuration details for each
transaction line. Open the Tax Line Details page by clicking the View Tax Lines button on the Simulator Transaction pages
from the Manage Simulator Transactions task.
Details include:
• Tax regime, tax, tax jurisdiction, tax status, tax rate code, and tax rate
• Tax amount and taxable amount
• Tax enabled status
• Indicators such as: inclusive, self-assessed, manually entered, and tax only line
• Calculated tax amount and tax base modifier rate
• Legal justification text
• Place of supply
For the tax lines associated with each transaction line, you can review the attributes that are specific to each tax line, such as:
• Rounding rule
603
Implementation
• Inclusive
• Minimum accountable unit and tax precision
• Tax rate modification
Rounding Rule
The Rounding Rule dialog box shows the rounding details for the transaction line. The rounding rule is the method used
to round off taxes to the minimum accountable unit. The rounding rule is derived based on the rounding level specified in
the hierarchy visible in the dialog box with level one taking precedence over level 2 and so on. If the rounding level is at the
header level then rounding is applied to calculated tax amounts once for each tax rate per invoice. If the rounding level is at
the line level then rounding is applied to calculated tax amounts on each invoice line.
Inclusive
The Inclusive dialog box shows the setup related to enforcing inclusiveness or exclusiveness of tax on a transaction line by
order of precedence. The level 0 precedence is the highest overriding all other values with the level 5 precedence being
the lowest or the default if none others are populated. The values are Yes or blank with blank meaning an option was not
selected for inclusive handling.
In the scenario represented in the following table, tax is calculated as inclusive based on the setting for the tax rate. If you
needed to modify this you can update the inclusive handling on the appropriate tax rate. If the transaction input value tax
inclusive is set to Yes this means this option was overridden directly on the transaction.
Precedence Source Inclusive
0 Transaction input value tax inclusive

1 Tax rate Yes

2 Tax registration

3 Site party tax profile

4 Party tax profile Yes

5 Tax

Minimum Accountable Unit and Tax Precision

The Minimum Accountable Unit and Tax Precision dialog box shows the derivation of these values by precedence. The
minimum accountable unit is the smallest unit a tax amount can have. Tax precision is a one-digit number that indicates the
number of decimal places to which to calculate a tax.
For example, a precision of 0 rounds to a whole currency. To round off a calculated tax amount of 1.366 to 1.37, define a
tax precision of 2, a rounding rule of Up or Nearest and a minimum accountable unit of .01. If the results are not what you
expected the dialog window gives you more information as to the source of the definitions. The precedence of 1 is the highest
with the definition at the currency level superseding the definition at the tax level.
604
Implementation
The following table illustrates this example:
Precedence Source Minimum Accountable Precision

Unit
1 Currency 2

2 Tax .01 2

Tax Rate Modification

The Tax Rate Modification dialog box identifies if any applicable rate exceptions have been applied, and, in the case of
Receivables, if any exemptions are applicable. The rates before and after any modifications are also shown. The tax rate
modification value is Yes or No with a link for you to drill down to detail information. If the tax rate modification value is Yes
then there is a modification to the tax rate either from an exception or an exemption. The dialog box detail shows the tax rate
name, the tax rate before modification, attributes to identify if exemptions or exceptions or both are applied, and the tax rate
after each of these modifications.
In the following table the original tax rate was 5 percent with an exemption applied that reduced the tax rate to 2 percent.
Attribute Value
Tax Rate Name VAT 5%

Tax Rate Before Modification 5%

Exception Applied No

Tax Rate after Exception 5%

Exemption Applied Yes

Tax Rate after Exemption 2%

Tax Rule Details for Simulated Transaction Lines: Explained

For the tax lines associated with each transaction line, you can review the tax rule details that are specific to each tax line,
such as:
• Rule results
• Rule conditions
• Tax rules process results
605
Implementation
Rule Results
Use the Rule Results table to view the tax rules that are applied to each tax line for each tax calculation process. For each rule
type, you can view the processed result and verify whether the result was determined by a tax rule or the default value.
For example, the following table shows the attributes displayed in the Rule Results table:
Rule Type Result Type Result Rule Code Rule Order
Determine Place of Default Ship to

Supply

Determine Tax Default Applicable

Applicability

Determine Tax Rule based Ship-to party REGRULE2 20

Registration

Where a tax rule is applied, you can determine the associated tax rule from the Rule Results table. In the previous example,
the tax determination process uses defaults to determine the place of supply and tax applicability. However, the tax
determination process determines the tax registration based on a tax rule. The applicable tax rule code is REGRULE2.
Rule Conditions
By selecting the Determine Tax Registration row, you can review the rule conditions that are successfully evaluated in the
Determine Tax Registration: Rule Conditions table. The following table shows the attributes displayed:
Determining Class Tax Operator Value or To Range

Factor Class Qualifier Determining From Range
Factor Name
Registration Ship-from Registration Equal to Not

party Status Registered

For example, if your transaction is calculating tax lines for a tax that should not be applicable, review the Determine Tax
Applicability rule values in the Rule Results table for that tax line. If the Result Type is Default with a result of Applicable,
verify that you have a Determine Tax Applicability tax rule that evaluates your transaction as not applicable.
Tax Rules Process Results

Use the Tax Rules Process Results table to view the processing and evaluation of the rules associated with a rule type. For
each associated rule, the process result consists of one of the following:
• Failed
• Successful
• Not evaluated
606
Implementation
For example, the Determine Tax Registration rule type may have 3 associated tax rules as represented in the following table:
Rule Code Process Result Evaluation Order Rule Order
REGRULE1 Failed 1 10

REGRULE2 Successful 2 20

REGRULE3 Not evaluated 3 30

In this example, the tax rule with the highest rule order priority failed, while the rule with the next highest rule order priority is
successful. In this case of 3 associated tax rules, the tax determination process does not evaluate the remaining tax rule.
For each rule in the Tax Rules Process Results table, you can also review the following:
• Rule information: Provides a summary of details associated with the tax rule, such as configuration owner, tax
regime, tax, effectivity, rule order, and tax determining set code.
• Event information: Provides additional information for the event class if this rule was defined as applicable to a
specific event class.
• Geography information: Provides additional parent geography and geography details defined for a specific tax rule if
the rule is geography specific.
For each tax rule listed in the Tax Rules Process Results table, you can drill down to the associated rule conditions to review
the condition details.
For example, if your transaction is correctly using tax rules to calculate taxes but is applying an incorrect tax rule, use the Tax
Rules Process Results table to review the rule order and the associated rule conditions for each tax rule.
Using the Tax Simulator to Analyze Tax Not Calculating as

Expected: Example
Use the Tax Simulator to create a simulated transaction and analyze the tax calculations of your transaction before you enable
your setup for live data or to troubleshoot existing tax setup. Use the header level details in the Tax Simulator to troubleshoot
issues where tax is not calculated as expected.
The following scenario illustrates when you might want to use the Tax Simulator to evaluate a Payables invoice where you
expect tax to be calculated and it is not.
Scenario
If there is a transaction in the subledger work area that is not calculating tax you can simulate this transaction in the Tax
Simulator.
Note
The transaction date in the Tax Simulator is updated to the system date so modify the transaction date to the
expected date of tax calculation.
607
Implementation
The following represents each of the attributes in order to assist you in determining what information they can provide to
identify the issue:
• Document Date: Ensure that the document date is correct and that the regime to rate setup and applicable tax
rules are effective as of this date?
• Configuration Owner: Determine if the configuration owner is the legal entity or the business unit. Does the
respective configuration owner have a subscription definition to the tax regime where you are expecting tax to
calculate? Is the subscription effective on the document date?
• Document Event Class and Source: Determine if the source is accurately reflected. The source identifies if the tax
options are derived from the predefined event class or if they are derived from the configuration owner tax options
that are defined. If they are derived from the configuration owner tax options you can query the configuration owner
tax option definition by the configuration owner and document event class and view options based on transaction
date effectivity. Other attributes and options, such as Allow Tax Applicability, Tax Regime Determination, and
Enforce tax from reference document are included in configuration owner tax options. Issues with tax calculation
may stem from the regime determination definition not being what is expected either the standard tax classification
code and not the TAXREGIME determination or the reverse. If these are intercountry transactions ensure that the
precedence of regime determination points to the expected country of taxation.
• Allow Tax Applicability: Ensure that this option is set to Yes for tax to calculate. This is the value defined on the
source value in the previous attribute. There is another Allow Tax Applicability attribute in this region that checks
the value from the applicable party.
• Regime Determination Set: Ensure that the regime determination set is accurately specified. This attribute
indicates if tax calculation is determined by the standard tax classification code or if country of regime is evaluated as
in the case of the predefined TAXREGIME regime determination set.
• Default Rounding Level: This does not impact tax calculation but identifies the rounding derivation.
• Third-party location: Determine if the third-party locations are accurately reflected. These attributes help identify
locations on this transaction that may influence regime determination and tax calculation based on location. There
may be other locations set at a line level that may impact tax calculation as well.
• Allow Tax Applicability: Ensure that this option is set to Yes for tax to calculate. This option is derived from the
supplier, supplier site, third party, and third-party site tax profile depending on the event class. Tax applicability must
be set to Yes for all relevant party tax profiles in order for tax to calculate. If tax applicability is set to No for either
attribute then tax is not processed.
• Evaluate Taxes: Ensure the status of the tax you are expecting to calculate. Is it Enabled for transactions,
Enabled for simulation, or Enabled for transactions and simulation? This identifies what status of taxes is
evaluated for calculating tax.
608
Implementing Project Financial Management Project Performance Reporting Configuration: Manage Project
Units: Performance Reporting Options
42 Project Performance Reporting Configuration:

Manage Project Units: Performance Reporting
Options
Performance Data Summarization: How It Is

Calculated
Summarization is a systematic organization of information for purposes of project analysis and tracking. You use summarized
data to analyze the health of projects and drill down to the causes of any deviation from set thresholds. You can complete the
following tasks using summarized data:
• Analyzing project performance data
• Reviewing project performance
• Analyzing KPI categories and KPIs
• Tracking project progress
• Viewing revenue and invoice summaries
After you run summarization, the KPI related information is rendered out of date with respect to the latest summarized
information. Therefore, it is important that you generate KPI values once the summarization process is completed. You can
avoid generating KPI values manually, by enabling automatic generation of KPI values in the summarization options.
Settings That Affect Performance Data Summarization

You summarize data for a project unit or a business unit. You can also summarize performance data for a range of projects or
projects owned by a project manager. Besides this, you must specify the following parameters each time you want to run the
summarization process manually:
• Select the appropriate summarization method:
◦ Incremental, for general purpose summarization.
◦ Bulk, for summarizing large amounts of data all at once.
◦ Delete and resummarize, for correcting summary data when the source system data is changed outside the
regular transaction flow.
◦ Resource breakdown structure, for migrating all summary data from one resource breakdown structure version
to the next. If you select this option you must also specify the resource breakdown structure header.
• Specify whether to summarize budget and forecast, commitment, actual cost, revenue and invoice, and client
extension transactions.
609
How Performance Data Summarization Is Calculated

Performance data summarization collects data from various sources and assigns amounts to relevant tasks and resources
in the project. After data is summarized, you can view how much is being spent on, incurred by, or received by a task or
resource. Also, data is grouped according to periods so that it can be tracked across different time lines.
You can run the summarization process for different situations, such as:
• Your data is out of date and you want to update it.
• Your data is corrupt and you want to delete the existing data and resummarize.
• You have a large volume of data that is not yet summarized and want to summarize the entire bulk of data in one
run.
After you select the parameters for summarization and submit a request, the application performs the following steps to
generate the data that you view in the application:
• Scope summarization by determining the list of projects, contracts, and batches of transaction data for which to run
summarization.
• Extract data to be summarized from data sources, group it by periods, and ensure the data is prepared for resource
mapping.
• Populate summary data into designated tables before resource breakdown structure mapping.
• Populate business unit, project unit, and other lookup information.
• Populate performance reporting dimension data including time, task breakdown structure, and resource breakdown
structure.
• Look up resource breakdown structure mappings, scenario dimension members, period IDs, and prepare data for
Essbase load.
• Load data into Essbase and merge data into summary tables.
You can track the progress of summarization on the process monitor. If the process fails to complete, it continues from the
point of failure when you resubmit it.
Related Topics
• KPI Values: How They Are Generated
Setting Up the Planning Amount Allocation Basis:

Points to Consider
When you set up summarization options, you are required to specify the planning amount allocation basis. You can select
a planning amount allocation basis only if you have selected the budgets and forecast data source for summarization. The
following are the methods of allocating planning amounts:
• Period start date
• Period end date
• Daily proration
Note
You cannot change the planning amount allocation basis if summarized data exists.
610
Assume that a project includes a task for team members to undergo some product and soft skills training. A budget of $5900
is allocated to this task between 1 January 2011 and 28 February 2011. While summarizing using a monthly accounting
calendar, the application can allocate the planned amount in three ways.
Period Start Date Basis Method

Allocate the entire budget of $5900 to the first period of January 2011 regardless of when the training takes place. This
allocation method could impact period to date cost variance measures for January and February if the actual training costs
occur in February. The period start date basis method is the default option.
Period End Date Basis Method

Allocate the entire budget of $5900 to the last period of February 2011 regardless of when the training takes place. This
allocation method could impact period to date cost variance measures for January and February if the actual training costs
occur in January.
Daily Proration Basis Method

Distribute the budget of $5900 equally over the entire period so that $3100 is spent in January 2011 and $2800 is spent in
February 2011. The following shows how the budget is distributed:
• Allocate the total amount of $5900 and dividing it by the total number of days to arrive at the daily amount.
Total Number of Days = 31 + 28 = 59
Daily Amount = $5900 / 59 = $100
• Multiply daily amount by the number of days the task is active.

Amount for January 2011 = $100 x 31 = $3100
Amount for February 2011 = $100 x 28 = $2800
Summarizing project performance data using daily proration requires more system resources than summarizing project
performance data using the period start or end date basis. To distribute plan amounts evenly across plan duration, the
application creates a summarized record for each day for the affected projects and tasks in the project unit.
Using the daily proration basis method reduces the chances of impacting period to date cost variance measures for January
and February.
FAQs for Manage Project Units: Performance

Reporting Options
Can I specify the budgets and forecasts to include in

summarization?
Certain financial plan types are included in summarization by default, while you must manually select others. Approved
forecast and baseline budget versions of the following financial plan types are automatically included in summarization of
project performance data:
611
How can I update project performance data and generate KPI

values?
Project managers can use the action to update project performance data and generate KPI values from the Project
Performance Dashboard. Alternatively, they can run both processes for projects they manage from the Scheduled Processes
page.
Project administrators can update project performance data for all projects in a project unit only from the Scheduled
Processes page.
Tip
Enable the option to generate KPI values automatically after updating project performance data.
Related Topics
What actions trigger performance data summarization?

The following actions trigger performance data summarization:
• Run the Update Project Performance Data process for a project from the Project Performance Dashboard or
Projects Overview area.
• Run or schedule the Update Project Performance Data process from the process scheduler.
• Enable the reporting option on the project unit to summarize project data before generating key performance
indicators.
• Create revenue and invoice transactions.
Important
Summarized revenue and invoice transaction amounts appear in the revenue and invoice work area;
however, these transactions do not appear in summarized data on the Project Performance Dashboard
until the transactions are summarized using the Update Project Performance Data process.
What happens when I select a planning amount allocation

basis for the project unit?
The Period Start Date and Period End Date options allocate amounts based on the period start and end dates. The Daily
Proration option spreads plan amounts evenly across the plan.
612
Implementing Project Financial Management Project Performance Reporting Configuration: Define Key
Performance Indicators

Define Key Performance Indicators
Manage Trend Indicators
KPI Trends: How They Are Calculated

Trend indicators show whether the trend of a key performance indicator (KPI) is favorable or unfavorable for a project. When
you define KPIs you specify a value for tolerance percentage. The tolerance percentage is taken into account while calculating
trend indicators for a KPI.
Note
KPI trends may not be useful if KPI values are generated often. The reason is, if the tolerance percentage is 10
percent and KPI values are generated every day, the values decrease by 1 percent each day. In this scenario, no
change is observed in the trend as the decrease is well within the tolerance. However, if you generate KPI values
at the start and end of the month, a significant change is observed in the trend.
Settings That Affect KPI Trends

The trend indicator that appears for a KPI is based on the defaults set in the performance trend indicator setup. The different
trend indicators available are:
• Up, favorable: The project performance trend is increasing in value and is desirable.
• Up, unfavorable: The project performance trend is increasing in value and is undesirable.
• Down, favorable: The project performance trend is decreasing in value and is desirable.
• Down, unfavorable: The project performance trend is decreasing in value and is undesirable.
• Unchanged: The project performance trend is unchanged.
You can change the sort order of the trend indicators based on how you want to sequence KPIs in a table based on the
performance of KPIs in a project.
How KPI Trends Are Calculated

Trend Indicators are calculated based on the percentage increase or decrease in a KPI value, while taking into consideration
the tolerance percentage specified while creating the KPI. The following example illustrates how trend indicators are
calculated for a KPI.
Consider a scenario where KPI values are generated for the first time on January 15, 2011, and again on February 15 and
April 15. KPI trends are calculated when there are at least two values that exist for a KPI.
Note
All values in the following tables are percentages unless specified otherwise.
613
KPI Values Generated on January 15, 2011

KPI Tolerance Current KPI Previous KPI Trend Indicator
Percentage and Value and Status Value and Status
Trend Indicator Indicator Indicator
Setting
PTD Actual Spent 5 70 - -

Labor Effort
Percentage Up is Favorable On Track

PTD Actual Spent 5 30 - -

Equipment Effort
Percentage Up is Unfavorable On Track

PTD Actual Invoice 5 $5000 - -

Amount
Up is Favorable Warning

Actual Billable 2 90 - -
Cost Percentage
Up is Favorable On Track

PTD Actual Margin 2 30 - -

Percentage
Up is Favorable On Track

After generating KPI values on January 15, 2011, the most critical KPI is PTD Actual Invoice Amount. The overall project
health status is Warning, because the most critical KPI, PTD Actual Invoice Amount, has a status of Warning.
KPI Values Generated on February 15, 2011

KPI Tolerance Current Period Previous Period Trend Indicator
Percentage and KPI Value and KPI Value and based on
Trend Indicator Status Indicator Status Indicator Previous Period
Setting
PTD Actual Spent 5 71 70 Unchanged

Labor Effort
Percentage Up is Favorable On Track On Track

PTD Actual Spent 5 29 30 Unchanged

Equipment Effort
Percentage Up is Unfavorable On Track On Track

614
KPI Tolerance Current Period Previous Period Trend Indicator
Percentage and KPI Value and KPI Value and based on
Trend Indicator Status Indicator Status Indicator Previous Period
Setting
PTD Actual Invoice 5 $4800 $5000 Unchanged

Amount
Up is Favorable Warning Warning

Actual Billable 2 91 90 Unchanged

Cost Percentage
Up is Favorable On Track On Track

PTD Actual Margin 2 30.2 30 Unchanged

Percentage

This table shows how the trend indicator is calculated based on the previous period. Although the KPI values for the
current period are different from the previous period, the difference in the values is not significant enough to change the
trend indicator, based on the tolerance percentage defined for each KPI. For example, the PTD Actual Spent Labor Effort
Percentage is 71 percent, compared to the previous period KPI value of 70 percent. If the current period KPI value is more
than 73.5 percent, which is more than 5 percent higher than the previous period, then the trend indicator is Up, Favorable. If
the current period KPI value is less than 66.5 percent, which is more than 5 percent lower than the previous period, then the
trend indicator is Down, Unfavorable.
The overall project health status is Warning, based on the most critical of all KPI statuses. After generating KPI values on
February 15, 2011, the most critical KPI is PTD Actual Invoice Amount.
KPI Values Generated on April 15, 2011

KPI Tolerance Current Quarter Previous Quarter Trend Indicator
Percentage and KPI Value and KPI Value and Based on
Trend Indicator Status Indicator Status Indicator Previous Quarter
Setting
PTD Actual Spent 5 75 71 Up, Favorable

Labor Effort
Percentage Up is Favorable On Track On Track

PTD Actual Spent 5 25 29 Down, Favorable

Equipment Effort
Percentage Up is Unfavorable On Track On Track

PTD Actual Invoice 5 $3500 $4800 Down,

Amount Unfavorable
Up is Favorable Critical Warning

615
KPI Tolerance Current Quarter Previous Quarter Trend Indicator
Percentage and KPI Value and KPI Value and Based on
Trend Indicator Status Indicator Status Indicator Previous Quarter
Setting
Actual Billable 2 91 91 Unchanged

Cost Percentage

PTD Actual Margin 2 28.5 30.2 Down,

Percentage Unfavorable
Up is Favorable Warning On Track

This table shows how the trend indicator is calculated based on the previous quarter. The current KPI values are compared to
the latest generation date of KPIs for the previous quarter.
Note
It is possible that the previous period trend and the previous quarter trend are calculated based on KPI values
from the same generation date. This occurs when the previous period generation date is the same as the latest
generation date in the previous quarter.
The first three KPI values changed enough since the previous quarter to change the trend calculator. For example,
the current quarter value of PTD Actual Invoice Amount is $3,500, which exceeds the threshold tolerance of 5
percent from the previous quarter KPI value of $4,800. Therefore the KPI is in a Critical status, and the trend
indicator is Down, Unfavorable. If the current quarter value is greater than $5,040, which is more than 5 percent
higher than the previous quarter, then the trend indicator is Up, Favorable.
A project manager might review the KPI values, statuses, and trends shown in this table and determine that a transaction was
not billed, because the KPIs that are based on revenue and invoice amounts have both dropped.
The overall project health is critical because of the status of the PTD Actual Invoice Amount.
Related Topics
• Performance Trend Indicators: Explained
FAQs for Manage Trend Indicators

Why did the trend indicator show a downward trend when KPI performance is improving?
While defining key performance indicators (KPIs), you can determine if a positive increase between the current and previous
KPI value is a favorable or unfavorable trend. Therefore, an upward trend may not necessarily indicate that KPI performance is
improving.
For example, for a KPI based on a non-billable percentage of total costs, a low value for non-billable costs is preferred.
Hence, a downward trend is favorable.
616
FAQs for Manage Performance Measures
What's the difference between effort-based, amount-based,

and percentage-based performance measures?
Performance measures that are based on effort hours are effort-based. Examples are, actual spent labor effort and actual
spent equipment effort.
Performance measures that are based on currency values are amount-based. Examples are, actual revenue and actual raw
cost.
Performance measures that are based on percentages are percentage-based. Examples are, actual margin percentage and
actual nonbillable cost percentage.
Note
KPIs that are percentage-based can be tracked at the task, resource, and project levels.
What happens if I use period-to-date amount-based measures

for large projects?
Period-to-date amount-based measures use the same threshold values for all phases of the project. This may result in a
spike in the key performance indicator (KPI) values if the amounts used to calculate the KPI values vary widely throughout the
project. To avoid this problem, consider using different sets of threshold values for amount-based KPIs defined in small and
large projects.
Manage Key Performance Indicators
KPI Components: How They Work Together

A key performance indicator (KPI) enables you to define thresholds of possible values for a performance measure for any
project in a project unit. During KPI definition, you associate a performance status indicator with each threshold level. When
you generate KPI values, the application compares the value against the thresholds defined for the KPI. If the value falls within
any of the defined threshold levels, then the application associates the status indicator of that threshold with the performance
measure. The following are the KPI components we will discuss:
• Performance Measure
• Performance Status Indicator
• Threshold Level
• Trend Indicator
• Tolerance Percentage
• Project Performance Data
617
• Project Unit
Performance Measure
Oracle Fusion Project Performance Reporting provides both fundamental and derived measures that present an objective
insight into the performance of the project. In addition, you can create custom measures to meet the unique needs of your
organization. Use any delivered or custom performance measure to create a KPI.
Note
Applying algebraic formulas to existing accounts and creating new accounts and measures using the client
extension are not available in Oracle Cloud implementations.
Performance measures are available in the areas of budgets and forecasts, billing and revenue, costs, effort, margin,
capitalization, and more. Following are examples of predefined performance measures:
• EAC Budget Cost (the estimate at completion burdened cost from the current baseline budget)
• ITD Forecast Revenue Variance (the inception-to-date current baseline budget revenue - current approved forecast
revenue)
• Prior Period Margin Percentage Variance (the prior period current baseline budget margin percentage - actual margin
percentage)
A performance measure is associated with a time dimension. The following time dimensions are available:
• Estimate-at-completion (EAC)
• Inception-to-date (ITD)
• Prior Period
• Period-to-date (PTD)
• Quarter-to-date (QTD)
• Year-to-date (YTD)
A particular performance measure set, such as Budget Cost, can have as many as six performance measures: one for each
time dimension.
A performance measure can be expressed as a currency amount, as a percentage, or in time units such as hours when effort
is measured. If the KPI is used on projects that use different currencies, you can enter different thresholds levels for each
currency you need.
Performance Status Indicator

Performance status indicators give an immediate picture of the status of a project, such as critical, at risk, and on track. Icons
with unique colors and shapes indicate the status and severity of performance. During KPI definition, you first associate status
indicators with performance statuses:
• Critical
• Severe
618
• At risk
• On track
• Ahead
You then associate these statuses with threshold levels. When KPI values are generated for a project, each value is compared
to the defined thresholds and the corresponding status indicator for the KPI appears on project performance reports.
A status can identify negative performance so that you can take the appropriate actions to prevent or quickly resolve
problems. Conversely, a status can identify positive performance to help you track expected or excellent performance.
Threshold Level
During KPI definition, you define threshold levels to cover all possible values for a KPI. If a KPI value exceeds the range of
values defined for the KPI threshold levels, the closest threshold is used to determine the KPI status. For example, if a KPI
value falls below the lowest threshold level, the application assigns the status of the lowest threshold level to the KPI.
A status indicator can be associated with more than one threshold level. For example, both underutilization and overutilization
of resources can indicate a critical performance status.
Trend Indicator
Performance trend indicators give an immediate picture of improving or worsening KPI value trends on the project. Icons with
unique colors and shapes indicate whether an increasing performance trend has a positive or negative impact. For example,
an increase in nonbillable costs is considered unfavorable to organizations that are able to bill costs to their clients. In this
example, the performance trend indicator will show a negative impact.
Tolerance Percentage
A tolerance percentage is used to compare the previous KPI value to the current value to show if the performance trend
is increasing, decreasing, or staying the same. For example, if the tolerance percentage is 10 percent for a KPI, and the
difference between the previous KPI value and current value is greater than 10 percent, then the trend is increasing. If the
difference is greater than -10 percent, then the trend is decreasing. If the difference is between -10 percent and 10 percent,
then the trend shows no change. A single tolerance percentage value, such as 10 percent in this example, represents both
negative and positive tolerances.
Project Performance Data

The application provides programs that extract and update transaction data and maintain project performance data. The
process of generating KPI values uses this project performance data. Before you generate new KPI values, check the date
that the project performance data was last generated to make sure that the data includes all transactions that may impact
project performance results. Then decide if you must update project performance data before you generate KPI values. After
you run these programs you will have a true picture of project performance.
When you generate KPI values, the period for which KPI values are being generated is determined by the KPI Period
Determination Date. The data during that period is used to generate project performance data that will be populated on the
project performance dashboard.
Note
KPIs that are enabled for use in the KPI definition are included when KPI values are generated.
Project Unit
KPIs are created for specific project units. During project unit implementation you specify whether KPIs are tracked for the
project unit.
619
KPI Values: How They Are Generated

Key performance indicator (KPI) values are calculated when you generate KPI values. KPI values must be generated after
project data is updated.
Settings That Affect KPI Values

You must specify the following parameters:
Settings Description
KPI Period Determination Date Set the date used to derive the project calendar and
accounting calendar periods for performance measure
calculations when KPI values are generated.

Replace Current KPI Values Replace the current KPI values with the values that are
generated now.

Delete Previous KPI Values Delete the KPI values that were generated the previous
time the generate KPI values process was run.

Number of Days to Retain KPI Values Retain KPI values for the specified number of days
starting from the current date before deleting previous
KPI values.

For example, assume KPI values were generated on the following dates:
KPI Period Determination Date Generation Date
October 29, 2010 November 12, 2010

September 30, 2010 October 15, 2010

If you generate KPI values on November 18, 2010 and select to replace the current KPI values, the KPI values generated on
November 12, 2010 are deleted and replaced with KPI values generated on November 18, 2010. You must select to replace
the current KPI values for a given period if you want to retain one set of KPI values and review KPI values during the period.
You can also delete KPI values that are not required for reporting. The options, Delete Previous KPI Values and Number
of Days to Retain KPI Values, enable you to delete KPI values that were generated prior to a specific number of days. For
example, if today is November 18, and you want to remove all KPI values generated in the previous year, you must select to
delete previous KPI values, and set Number of Days to Retain KPI Values to 322. All KPI values created since January 1,
2010 are retained and KPI values generated before that period are deleted.
620
Important
Do not delete previous KPI values in the following cases:
• When you are generating KPI values for the first time in a period.
• If you want to see trending information for the KPIs over the life of the project.
When you generate KPI values, you can select to receive a notification by e-mail by enabling workflow notifications, once KPI
values are generated.
How KPI Values Are Generated

KPI values are calculated based on the value of the performance measure associated with the project. When you generate
KPI values, the KPI period determination date is compared to the current date to determine the period. KPI values are
generated for the period based on the options in the key performance indicator definition. Only one set of key performance
indicators is kept for a single KPI period determination date.
For example, KPI values are generated for a KPI period determination date of August 24 at 8:15 a.m. for Projects A and B.
Then KPI values are generated for a KPI period determination date of August 24 at 10:45 a.m. just for Project B. The KPI
values for Project B generated at 8:15 a.m. are deleted, but KPIs belonging to Project A are retained.
Note
To keep historical information, use a unique KPI period determination date.
Related Topics
• Calculating Current, Prior Period, and Prior Quarter KPI Values: Examples
Performance Status for Tasks and Resources: How It Is

Calculated
The application calculates performance status for individual tasks and resources for percentage-based key performance
indicator (KPI) values.
Settings That Affect Performance Status for Tasks and Resources

When you enable the Track by Task and Track by Resource options on the project definition, a status indicator appears
for the task and resource on project performance reports when the individual KPI value is not on track. Enabling this option
helps you easily identify the troubled tasks and resources in a hierarchical task and resource structure in a project.
Note
You can track performance by task and resource only for KPI values that are expressed as a percentage.
How Performance Status for Tasks and Resources Are Calculated

Performance status is individually calculated for all levels of the task and resource hierarchy based on the KPI threshold
definition. KPI threshold values are defined when KPIs are created. Based on the threshold values defined, the status for
tasks and resources are calculated for the KPI values that are based on a percentage. This example shows how the status of
621
tasks and resources are calculated. For example, assume that the KPI named ITD Nonbillable Cost as a Percentage of Total
Cost has the following threshold definition.
Threshold Level Threshold Range Threshold Range To Status Indicator

From
1 -99.00% -12.00% Critical

2 -11.99% -5.00% At Risk

3 -4.99% 4.99% On Track

4 5.00% 11.9% At Risk

5 12.00% 99% Critical

Example of System Implementation Task

In the example, we have a System Implementation task containing six subtasks.
Task Task ITD ITD Billable ITD Total ITD

Nonbillable Cost Cost Nonbillable
Cost Cost as a
Percentage
of Total Cost
System 20,000 105,000 125,000 16.00%

Implementation

Planning 0 21,000 21,000 0%

Definition 6,000 51,000 57,000 10.53%

Build 15,000 33,000 48,000 31.25%

Test 0 0 0 0%

Release 0 0 0 0%

Support 0 0 0 0%

622
The ITD Nonbillable Cost as a Percentage of Total Cost KPI value for the Definition task is 10.53% (6,000/57,000). Based on
the threshold levels defined for this KPI, the Definition task shows the At Risk status indicator.
Example of a Consulting Resource Breakdown Structure

In another example, the Consulting resource breakdown structure contains a Labor resource. Labor is a parent to the Project
Manager resource, which is a parent to resources Max Martin, Robert Altima, and Fred Jones. The ITD Nonbillable Cost as a
Percentage of Total Cost KPI value for Labor is 12.97% (15,700.00/121,015.00). The ITD Nonbillable Cost as a Percentage
of Total Cost KPI value for Fred Jones is 0%. Because the KPI value for each row in the hierarchical structure is calculated
separately, Labor has a status indicator of Critical and Fred Jones does not have a status indicator.
Resource Resource Resource Resource ITD ITD ITD ITD

Nonbillable Billable Total Nonbillable
Cost Cost Cost Cost
as a
Percentage
of Total
Cost
Consulting 19,776 105,315 125,091 15.81%

Labor 15,700 105,315 121,015 12.97%

Project 15,700 50,000 65,700 23.90%

Manager

Max 2,800 14,000 16,800 16.67%

Martin

Robert 8,400 0 8,400 100.00%

Altima

Fred 0 36,000 36,000 0%

Jones

If you track tasks and resources for a project, each task and resource with a KPI value that is not on track is designated as
an exception. The KPI value for the project does not impact the exception designation for individual tasks and resources.
For example, if a task has a Critical status indicator based on the KPI value and threshold definition, it is designated as an
exception even if the project has an On Track status indicator.
Important
Task and resource performance status is based on the latest summarized data, which may not be the same as
the summarized data used to generate the latest KPI values.
623
Tolerance Percentage: Explained

Tolerance percentages are used to compare the previous key performance indicator (KPI) value to the current value to arrive
at the performance trend.
Trend indicators are calculated based on the percentage increase or decrease in a KPI value and the tolerance percentage on
the KPI definition.
Example of Tolerance Percentage

When you create a KPI, you must enter a tolerance percentage that is used in determining the trend indicator to display for a
KPI. The percentage change in KPI value is calculated using the following formula:
Percentage Change in KPI Value = absolute value of (Current Value - Previous Value*100 / Previous Value)
The following example illustrates how tolerance percentage is used to calculate the trend indicator to display.
KPI Tolerance Current Previous Percentage Trend

Percentage Period Period Change Indicator
and Trend KPI Value KPI Value Based on
Indicator and Status and Status Previous
Setting Indicator Indicator Period
PTD Actual 5 percent $3500 $4800 27 percent Down,

Invoice Unfavorable
Amount Up is Critical Warning
Favorable

PTD Actual 5 75 71 5.6 percent Up, Favorable

Spent
Labor Effort Up is On Track On Track
Percentage Favorable

PTD Actual 2 percent 28.5 percent 30.2 percent 5.6 percent Down,
Margin Unfavorable
Percentage Up is Warning On Track
Favorable

Creating Different Threshold Levels for Each Currency:

Examples
You must define threshold levels for each currency for currency-based KPIs.
Scenario
A company is in the business of selling and installing human resource software. One of the standard KPIs used for the
installation projects is Period-to-Date (PTD) Invoice Amount. Installation projects are performed in different countries having
different project and ledger currencies, such as, United States dollars, Japanese yen, Mexican pesos, and Indian rupees.
624
Projects performed using currency in United States dollars have a higher threshold for criticality with respect to PTD invoice
amounts. This is reflected with unique currency threshold definitions.
Ledger Currency Definitions

For projects with a ledger currency in United States dollars, the PTD invoice amount is considered critical if the value is
between 0 and 3,000 USD. For projects with a ledger currency in Indian rupees, a critical PTD invoice amount would
be between 0 and 50,000 INR. The different currency thresholds do not have to necessarily correlate to exact currency
conversion.
FAQs for Manage Key Performance Indicators

What's the difference between key performance indicator and performance measure?
Key performance indicators (KPIs) measure how well an organization or individual performs an operational, tactical, or
strategic activity that is critical for the current and future success of the organization. Examples are: Period-to-Date (PTD)
Actual Spent Labor Effort Percentage, PTD Actual Spent Equipment Effort Percentage, and PTD Actual Margin Percentage.
Performance measures are singular data elements defined by a specific account, scenario, and time dimension combination.
For example, the performance measure, Quarter-to-Date (QTD) Forecast Labor Effort, references the account of labor hours,
in the scenario of primary forecast, and the quarter-to-date time dimension.
A KPI is created based on a performance measure, and specifies how a performance measure value is interpreted using
threshold levels. For example, the KPI PTD Actual Spent Equipment Effort is based on the measure actual spent equipment
effort.
What's the difference between key performance indicator and KPI category?
Key performance indicators (KPIs) measure how well an organization or individual performs an operational, tactical, or
strategic activity that is critical for the current and future success of the organization. Examples are: Period-to-Date (PTD)
Actual Spent Labor Effort Percentage, PTD Actual Spent Equipment Effort Percentage, and PTD Actual Margin Percentage.
A KPI category is a group of KPIs that belong to a specific performance area. Examples are: cost, profitability, financial, and
schedule.
From the examples above, PTD Actual Margin Percentage must be in the KPI category of profitability.
What's a KPI period determination date?

Date used to determine the accounting calendar and project accounting calendar periods for performance measure
calculations during key performance indicator (KPI) value generation.
For example, assume that your project uses a monthly accounting calendar and a weekly project accounting calendar. You
generate KPI values on December 8, 2010 with a KPI period determination date of November 30, 2010. The current period
for KPI generation is determined based on the type of calendar used. In the accounting calendar, the date November 30,
2010 falls into the November 2010 period. In the project accounting calendar, November 30, 2010 falls in the first week of
December 2010.
Note
The KPI period determination date must be a date in the past.
Why can't I create or edit a key performance indicator for a project unit?
Since the project unit is not enabled to track key performance indicators.
What happens if I attach different KPIs to a project for the same measure?
Overall project health is based on the most severe KPI status even if you have more than one KPI using the same
performance measure.
625
For example, a Financial category contains three KPIs, and two of those KPIs use the same performance measure with two
different threshold definitions. The overall project health is critical in both of these scenarios:
• The KPI status is critical and on track for the two KPIs that use the same performance measure, and the KPI status
is on track for the third KPI.
• The KPI status is on track for the two KPIs that use the same performance measure, and is critical for the third KPI.
Can I track KPI values at the task and resource level?

Yes. You can track key performance indicators that have a percentage measure format for a project by task and resource.
What happens if a KPI value exceeds the threshold limits defined for the KPI?
An up or down arrow appears in the Exceeds Threshold column of the KPI History table, and the closest threshold is used
to determine the key performance indicators (KPIs) status. If KPI values fall outside the threshold ranges, consider extending
the upper and lower threshold ranges.
Where do the currency type options for a key performance indicator come from?
The currency type appears for a selection only if the currency type is enabled for summarization for the project unit.
Where do the calendar type options for a key performance indicator come from?
The calendar type appears for a selection only if the calendar type is enabled for summarization for the project unit.
How can I evaluate project performance if KPIs are not tracked?

You must use the Review Project Performance page to perform more detailed financial performance analysis for a project
than is possible on the Project Performance Dashboard. You can review amounts at the task or resource level, and drill
down to individual expenditure items.
626
Implementing Project Financial Management Project Performance Reporting Configuration: FAQs for Define
Region Personalization

FAQs for Define Region Personalization
Can I choose the regions to appear on Project

Performance Reporting dashboard?
Yes. Select the Edit Current Page link in the Personalization menu to show or hide regions. You can also modify the
arrangement of the region layouts using the Change Layout option.
627
Implementing Project Financial Management Manage Project Templates
45 Manage Project Templates
Expenditure Item Chargeable Status: How It Is

Determined
Oracle Fusion Project Portfolio Management checks all levels of chargeable controls when you try to charge a transaction to a
project. The application checks the chargeable status when you enter a new cost transaction or transfer expenditure items to
another project or task, and you save the record.
.
Settings That Affect Chargeable Status

Use the exclusive and inclusive transaction control options to set the chargeable status for all expenditures charged to the
project.
Inclusive transaction controls prevent all charges to a project or task except the charges you specifically allow. Specify the
types of expenditures that you want to allow, and enable the Chargeable option.
By default, exclusive transaction controls allow all charges to a project or task. Specify the types of expenditures that you
don't want charged to the project or task.
628
How Chargeable Status Is Determined

The following illustration shows the steps that Project Portfolio Management uses to determine the chargeable status of an
expenditure item.
If the inclusive option is selected and applicable transaction controls don't exist, then the transaction isn't chargeable. If
applicable controls do exist, then the application checks whether the transaction controls allow charges.
If the exclusive option is selected and there are no applicable controls, then the transaction is chargeable. If applicable
controls do exist, then the application checks whether the transaction controls allow charges.
629
Note
For both inclusive and exclusive transaction controls, a transaction is chargeable if the Chargeable check box
is selected for an applicable control. If the Chargeable check box isn't selected, then the transaction isn't
chargeable.
Spaces: How They Work With Projects

Spaces provide an online location and collection of tools for teams to work together more effectively. Your projects can
contain spaces for collaboration among team members, which enable you to optimize the efficiency of managing, executing,
and controlling projects.
Each project has access to a private set of tools that includes:
• Announcements
• Calendar
• To Do lists
• Team members and roles
• Tool for creating Wikis
• Tool for creating blogs
• Discussion forums
• Document repository
• Tags and links
• Lists
To create a project space, a project space template must be part of the project template. Each time you create a project, you
can select the project space template to automatically create a project space with the project.
Project team members from the source project template or source project are copied and added to the project and project
space. New project team members are automatically added to the project space. Optionally, you can change project space
roles or remove members from the space.
Project Space Templates

Your implementation team can associate a project space template to a project template. The project space template is used
to automatically generate a project space during project creation.
Role Mappings
The project manager is assigned to the Moderator role in the project space. All other project team members are assigned to
the project space as Participants.
Project Quick Entry: Explained

You can configure quick entry fields while defining a project template. Oracle Fusion Project Portfolio Management prompts
you to enter information in quick entry fields when you create new projects from the template.
630
Quick Entry Fields

Select quick entry fields for project information that you want to enter (instead of accepting the template default) each time
you create a project. The following table describes the quick entry fields on a project template.
Name Description
Field Name The field to display in the Project Details when creating
a new project.
Specification Enter a specification for the following fields:

• Classification
◦ Select the class category to use for the

classification.
• Team Member
◦ Select the project role to use for the team

member.
Prompt Text for a field that appears only in the Project Details
while you're creating a new project. The prompt field
name isn't displayed after you create the project.
Tip
For example, if you want to add a quick entry
field for the project start date, update the
prompt that appears during project creation
to Enter the project start date. However
the field in the project for all other pages will
remain as Project Start Date.

631
Name Description
Required Choose whether you want to require entry for the field.

Note
The following fields are required on all
projects, and can't be optional quick entry
fields:

Note
Legal Entity

Note
Organization

Note
Project Name

Note
Project Number

The following table describes limitations for quick entry fields.
Field Name Quick Entry Maximum
Classification 20

Partner organization 5

Project customer 5

Supplier organization 5

Team member 15

You can allow entry of more than one team member per
role for all roles except Project Manager. You can enter
only one project manager for a project.

632
Note
After creating the project, you can add further values to the fields in the project.
Summarized Financial Plan Types: Explained

Summarized financial plan types are financial plan types whose previous and current approved versions (for forecasts) or
original and current baseline versions (for budgets) are used in summarization of project performance data.
Particular financial plan types are included in summarization by default, while you must manually select others.
Default Financial Plan Types

Approved forecast and baseline budget versions of the following financial plan types are automatically included in
summarization of project performance data:

Important
A budget or forecast financial plan type may support both cost and revenue in one version.
User-Selected Financial Plan Types

Tip
You can include a financial plan type before it is used on a project for creating a version.
You can replace a user-selected financial plan type until project performance data is summarized for reporting. After that, you
can only disable the financial plan type to exclude it from further summarization.
Related Topics
Transaction Controls: Explained

Define transaction controls to specify the types of transactions that are chargeable or nonchargeable for projects and tasks.
Use transaction controls to configure your projects and tasks to allow only charges that you expect or plan. You can also
define which items are billable and nonbillable on your projects that are enabled for billing. For capital projects, you can define
which items are capitalizable and noncapitalizable.
You create transaction controls by configuring the following components:
• Expenditure category
• Expenditure type
633
• Nonlabor resource
• Person
• Job and organization for the person
• Person type
• Chargeable status
• Billable or Capitalizable status
• From and To dates
You can create any combination of transaction controls that you want; for example, you can create a transaction control
for a specific person and expenditure type, or you can create a combination for a person, expenditure type, and nonlabor
resource. You also specify the date range to which each transaction control applies. If you do not enter transaction controls,
you can charge expenditure items from any person, expenditure category, expenditure type, and nonlabor resource to all
lowest tasks on the project.
Chargeable Status
You can further control charges for each transaction control record by specifying whether to allow charges. The default value
is to allow charges.
You usually select Chargeable when you are using inclusive transaction controls. For example, if you wanted to allow people
to charge only labor to your project, you would define a transaction control with the Labor expenditure category, and allow
charges to the project or task.
You usually do not select Chargeable when you are using exclusive transaction controls because exclusive transaction
controls list the exceptions to chargeable transactions.
System Person Type

You can use this control to specify whether transactions incurred by employees, contingent workers (contractors), or both are
chargeable.
The validation rules for system person type controls are described in the following table.
Transaction Control Type System Person Type Validation Rule
Inclusive No value Transactions incurred by

employees and contingent workers
are not chargeable.

Inclusive Employee Only transactions incurred by

employees are chargeable.

Inclusive Contingent worker Only transactions incurred by

contingent workers are chargeable.

Exclusive No value Transactions incurred by

employees and contingent workers
are not chargeable.

634
Transaction Control Type System Person Type Validation Rule
Exclusive Employee Transactions incurred by

employees are not chargeable.

Exclusive Contingent worker Transactions incurred by

contingent workers are not
chargeable.

Billable and Capitalizable Status

You can define billable transactions for billable projects and capitalizable transactions for capital projects by selecting the
billable or capitalizable option. You can choose between the options of No or Task Level. Select No if you want the charges
to be nonbillable or noncapitalizable. Select Task Level if you want the billable or capitalizable status to default from the task
to which the item is charged.
You define the billable or capitalizable status for a task in the Task Details.
Note
The billable or capitalizable status of an individual transaction takes precedence over the billable or capitalizable
status of a task.
From and To Dates

You can define transactions as chargeable for a given date range by entering a From Date and To Date for each transaction
control record.
Using Class Categories: Examples

Class categories and class codes enable you to classify projects. The following example illustrates how you can use project
classifications.
Scenario
InFusion Corporation designs and implements heavy engineering projects for government and private customers. Because
InFusion Corporation maintains a diverse portfolio of contracts, the ability to track sector and funding is very important to
corporate management.
Therefore, the organization classifies projects by market sector and funding source. The following table describes the two
class categories used.

Class Codes
Market Sector Yes Yes No Market sector in

which project work
takes place.
635

Class Codes

A single class
code must be
provided on the
project for the
class category.

Funding Source Yes No Yes Source of funding

for project.

At least one class
code must be
provided on the
project for the
class category.
Percentages
must be provided
to indicate
contribution for
each source.

The following table describes the class codes available for the categories specified above.
Funding Source Private Project funded by private

organizations

Funding Source Federal Project funded by the federal

government

Funding Source State or Local Project funded by a state or local

government

Funding Source Foreign Project funded by a foreign

government

Market Sector Utilities Project involves utility or power

plant construction

Market Sector Waste Project involves waste disposal or

recycling facility constructions

636
Market Sector Mechanical Project involves mechanical design


Market Sector Structural Project involves structural design


InFusion management can easily assess projects based on the above class categories and codes.
For example, you specify a class category Funding Source on your project. With this category, you select two class codes:
Private and Federal. If you assign 30 percent to Private and 70 percent to Federal, then you indicate the proportion of funding
received for your project from the two sources.
On the other hand, because you must select a single market sector, you indicate whether project work involves utilities,
waste, mechanical, or structural activities.
FAQs for Manage Project Templates
Can I override the billable status of an expenditure item?

Yes. Change the billable status of an expenditure item on an invoice, or in the Manage Expenditure Items page.
How are project space roles mapped to project resources?

The application automatically assigns each project resource to a project space role on the associated project space. The
project manager is assigned the role of project space moderator. All other project resources are project space participants.
Project space moderators can manually add additional participants or modify participant access, if required.
637
Implementing Project Financial Management Define Subledger Accounting Rules
46 Define Subledger Accounting Rules
Manage Accounting Methods
Creating Accounting Method: Explained

Accounting methods group subledger journal entry rule sets together to define a consistent accounting treatment for each
of the accounting event classes and accounting event types for all subledger applications. The grouping allows a set of
subledger journal entry rule sets to be assigned collectively to a ledger.
For example, a subledger accounting method entitled US GAAP can be defined to group subledger journal entry rule sets that
adhere to and comply with US Generally Accepted Accounting Principles (GAAP) criteria.
By assigning a different subledger accounting method to each related ledger, you can create multiple accounting
representations of transactions.
Accounting rules can be defined with either a top down, or a bottom up approach. When defining subledger accounting
rules from the top down, you will initially define the accounting method followed by components of each rule, which must be
assigned to it. When defining subledger accounting rules from the bottom up, you will initially define components for each rule
and then assign them as required.
The Create Accounting process uses the accounting method definition with active journal entry rule set assignments to create
subledger journal entries.
When an accounting method is initially defined, or after modifying a component of any accounting rule associated to the
assigned journal entry rule set, its status changes to Incomplete.
The accounting method must be completed, by activating its journal entry rule set assignments, so that it can be used to
create accounting.
The following definitions are used to define the journal entries, and are applied as updates to the accounting method:
• Updates to the predefined accounting method
• Assignment of journal entry rule sets for an accounting event class and accounting event type from the accounting
methods page
• Assignment of accounting methods to ledgers
• Activation of subledger journal entry rule set assignments
Updates on Predefined Accounting Method

You may update a predefined accounting method by end dating the existing assignment and creating an assignment with an
effective start date.
Assignment of Journal Entry Rule Set for Accounting Event Class and Accounting Event
Type
You create the assignment of a journal entry rule set for an accounting event class and accounting event type using the
accounting method page.
638
The following should be considered for assigning rule sets:
• If the accounting method has an assigned chart of accounts, you can select journal entry rule sets that use that
same chart of accounts, or that are not associated with any chart of accounts.
• Select an option to assign existing journal entry rule sets or create one.
Assignment of Accounting Methods to Ledgers

If the accounting method has an assigned chart of accounts, it may only be used by ledgers that use the same chart of
accounts.
If the accounting method does not have an assigned chart of accounts, the accounting method can be assigned to any
ledger.
Activation of Subledger Journal Entry Rule Set Assignments

You can activate the subledger journal entry rule set assignments from the Accounting Method page. You can also submit the
Activate Subledger Journal Entry Rule Set Assignments process to validate and activate your accounting set ups.
Fusion Setup Flow

The figure below shows the relationship of components making up an accounting method as described in the above text.
639
Creating Conditions: Examples

The following illustrates an example of defining an account rule with a condition.
Example 1: Custom Real Estate Application Account Rule Condition

Example
This is an example to define an account rule for assignment for a loan journal line. The account rule has two priorities, a
mapping set and a constant.
• The first priority will create an output for an account based on the mapping set rule definition.
◦ A condition is created using the first priority rule. This rule will only be used if the condition below is met.
• The condition is Credit Status must not be null.
• The accounts derived from the mapping set rule will be used if the Credit Status has a valid value.
Otherwise, the accounts derived from the entered constants value from the second priority will be used.
The following table describes the setup of the condition on the first priority:
( Source Operator Value )
( "Credit Status" is not null )

The second priority will create an output from a constant value (0.9100030.50034206331.0.0.0). There is no condition
associated with the second priority.
Example 2: Oracle Fusion Assets Account Rule Condition Example

This is an example of a rule for a capital purchase. The rule is to be applied only if the distribution account cost center is the
same as the liability account cost center and the asset tracking option is Yes. This condition can be expressed as:
• Where Distribution Cost Center = Liability Cost Center and Asset Tracking option = Yes
The following tables describe the setup of the condition:
( Source Delimiter Segment Operator Value Delimiter Segment ) And

Or
( "Distribution . "Cost = "Liability . "Cost ) 'AND'

Account" Center" Account" Center"

( "Asset = Yes )
Flag"

The following two rows of data are used in the accounting event, to which the account rule and condition applies.
640
Account Rule Condition Example: Accounting Event Data
Account Invoice 1 Invoice 2 Asset Flag
Distribution Account 02-640-2210-1234 01-780-6120-0000 Yes

Liability Account 01-640-2210-0000 02-782-2210-0000 Yes

In the Accounting Event Data table above, assume the cost center segment is the second segment. When the account
rule with this condition is used to derive the account for the transaction, the account rule is applied to derive the account of
Invoice 1 only. For Invoice 2, even though the assets tracking option is set to Yes, the cost center for the Distribution account
and Liability account are not the same. Both conditions must be met in order for the rule to apply.
Note
When an account source is selected or entered, you must also select or enter a specific segment. If an entire
account is required to be used in the condition instead of a specific segment, then select or enter All as the
segment for the account.
The condition uses the account source, Distribution Account, and a segment must be provided. In this example,
the cost center segment is provided.
Creating Supporting References: Explained

Supporting references are used to store additional source information about a subledger journal entry at the line level.
Supporting references with balances establish subledger balances for a particular source and account for a particular
combination of supporting references plus the account combination.
For example, if a supporting reference is to hold customer information with two sources, Customer Type and Customer
Name, and is assigned to a journal line, balances will be created for each combination of: account combination plus customer
name and customer type.
Examples of how you may want to use supporting reference balances are to:
• Facilitate reconciliation back to the subledgers and source systems by tagging journal entries with transaction and
reference attributes.
• Create balances by dimensions not captured in the chart of accounts.
• Reporting using dimensions not captured in the chart of accounts.
• Enrich Oracle Fusion Business Intelligence Applications reporting on subledger journals.
• Profit and loss balances by dimensions not captured in the chart of accounts
Define supporting references to hold additional supporting information for detailed account balance maintenance or
reconciliation/reporting requirements.
Supporting Reference Assignment

Supporting references are a powerful tool to allow capture of journal entries with transaction attributes. You can use these
tags to report on entries, reconcile entries back to source systems or even maintain balances at the attribute level.
• Define supporting references once and reuse by assigning sources of different event classes or source systems to
the same supporting reference.
641
• You can assign one source per event class to each supporting reference. The subledger or source system uses the
supporting reference name to store the source values. This standardizes supporting reference information, even if it
comes from disparate source systems.
Supporting references can be defined using either of these options (located on tabs):
• With Balances:
◦ Select the balances option in the definition of the supporting reference, to have balances only maintained when
the supporting reference is assigned.
◦ If balances are maintained for a supporting reference, they will be carried forward into the next fiscal year, for all
Profit and Loss account types.
◦ There is a limit of thirty supporting references with balances defined. You can consider adding more source
assignments to predefined supporting references, rather than creating a new one.
• Without Balances:
◦ There is no limit to the number of supporting references without balances.
Caution
If there is no balance to be maintained for a supporting reference and no slicing and dicing is needed for reports
on supporting references, consider using a journal entry header or line description instead of the supporting
reference feature.
This is recommended for accounting engine performance considerations. Using supporting references instead of
descriptions will impact the performance.
Related Topics
• Supporting Reference Assignments: Points to Consider
Accounting Event Model: Explained

Accounting events represent transactions that may have financial significance, for example, issuing a loan and disposing of an
asset. Financial accounting information can be recorded for these events and accounted by the Create Accounting process.
When you define accounting events, determine from a business perspective which activities or transactions that occur in your
source system may create a financial impact.
Events with significantly different fiscal or operational implications are classified into different accounting event types. Event
types are categorized into accounting event classes. Accounting definitions in the Oracle Fusion Accounting Hub are based
on event types. An event type must be unique within an application, process category, and event class.
Events are captured when transactions are committed in the subledgers, or they may be captured during end-of-day or
period-end processing. For example, a loan is originated, possibly adjusted, interest is accrued, and then the loan is paid
or canceled. The accounting events representing these activities can create one or more subledger journal entries, and
subsequently link the originating transaction to its corresponding journal entries.
642
The following is an example of an accounting event model for a loan application:
Process Categories
A process category consists of specific event classes and the event types within those classes. To restrict the events
selected for accounting, users can select a process category when they submit the Create Accounting process.
Event Classes
You can assign a transaction view, system transaction identifiers, and optionally user transaction identifiers and processing
predecessors for an event class in the Edit Event Class section. The transaction view should include all columns that have
been mapped to system transaction identifiers for the accounting event class as well as the user transaction identifiers.
System Transaction Identifiers
System transaction identifiers provide a link between an accounting event and its associated transaction or document. An
identifier is the primary key of the underlying subledger transaction, usually the name of the surrogate key column on the
transaction (header) associated with the accounting event. At least one system transaction identifier must be defined for the
accounting event class.
When an accounting event is captured, system transaction identifiers, along with other required event data, are validated for
completeness.
User Transaction Identifiers
User transaction identifiers constitute the user-oriented key of the underlying subledger transaction, and are typically drawn
from one or more database tables. These identifiers are primarily used in accounting events inquiry and on accounting event
reports, to uniquely identify transactions. You can specify up to ten columns from the transaction views that are available for
inquiry and reports.
The transaction data that identifies the transaction varies by accounting event class. Accounting event reports and inquiries
display the transaction identifiers and their labels appropriate for the corresponding event class. The user transaction
identifiers can be displayed for an event regardless of its status. This includes the case where the accounting event has
not been used to create subledger journal entries due to an error or the cases where it has not been processed. The user
transaction identifier values are displayed at the time that the accounting event reports and inquiries are run. If a transaction
identifier value has changed after the accounting event was captured, the accounting event reports and inquiries reflect the
change.
Processing Predecessors
643
The processing predecessor establishes an order in which the Create Accounting process processes events selected for
accounting.
Event Types
For accounting event types, specify whether their accounting events have accounting or tax impact. When the Create
Accounting process is submitted, it only accounts business events that are enabled for accounting.
Related Topics
• Subledger Journal Entries: How They Are Created and Processed
Transaction Objects: Points to Consider

You may assign transaction and reference objects for each accounting event class in the subledger application. Sources are
generated based on the transaction objects and are assigned to the corresponding accounting event classes.
Sources are used to create accounting rules. Subledgers pass information to the application by populating transaction object
tables. The columns in these tables are named after the source codes. Transaction and reference objects hold transaction
information that is useful when creating journal entry rules for accounting. The transaction and reference objects are defined
for an accounting event class so that source assignments to accounting event class can be generated using these objects.
Transaction Objects
Transaction objects refer to the tables or views from which the Create Accounting process takes the source values to create
subledger journal entries. Source values, along with accounting event identifiers, are stored in the transaction objects. The
Create Accounting process uses this information to create subledger journal entries.
You have several options. You can:
• Create new tables as the transaction objects and create a program to populate them.
• Use views of your transaction data as the transaction objects.
• Use your transaction data tables as the transaction objects.
The transaction objects and or views must be accessible to the Create Accounting process. Typically, an ETL (extract,
transformation, and load) program is used to take values from the source system and load them into the database used by
the Create Accounting process. The ETL process is done outside of the Create Accounting process.
The following are transaction object types:
• Header transaction objects
◦ Implementers need to provide at least one header transaction object for each accounting event class. Header
transaction objects store one row with untranslated header source values for each accounting event. The
primary key of a header transaction object is the event identifier.
Transaction details that are not translated, and whose values do not vary by transaction line or distribution,
should normally be stored in header transaction objects. Examples of sources normally stored in header
transaction objects include the Loan Number for a loan or the Contract Number for a contract.
• Line transaction objects
◦ Line transaction objects are relevant when there are details for the accounting event that vary based upon
transaction attributes. For example, a mortgage transaction for loan origination may have multiple amounts,
644
each related to different components of the loan. There may be a loan origination amount, closing cost
amounts, and escrow amounts. Each of these amounts could be captured as separate lines, along with an
indication of the amount type
Line transaction objects store untranslated line level source values. There should be one row per distribution,
identified by a unique line number. The primary key of a line transaction object is the event identifier and
transaction object line number. Transaction details that are not translated and whose values vary by transaction
line or distribution are normally stored in line transaction objects columns. Examples include the Loan Number
for a loan payment.
• Multi-Language Support (MLS) transaction objects
◦ MLS transaction objects are relevant to applications that support the MLS feature. MLS transaction objects
store translated source values. There should be one row per accounting event and language. The primary
key of a header MLS transaction object is the event identifier and language. The primary key of a line MLS
transaction object is the event identifier, transaction object line number, and language.
Transaction details that are translated, and whose values do not vary by transaction line or distribution, are
normally stored in header MLS transaction object columns. Examples include Loan Terms for a commercial
loan. Implementers can avoid having to store source values in header MLS transaction objects by using value
sets and lookup types.
Transaction details that are translated, and whose values vary by transaction line or distribution, should
normally be stored in the transaction object in columns defined in a line MLS transaction object.
Reference Objects
Reference objects are useful for storing information that is used for creating subledger journal entries. This information may
not be directly from the source system or may be used for many entries, thus making it redundant. Use reference objects to
share sources information across applications.
For example, store customer attributes, such as the customer class or credit rating in a reference object, and then, use it
to account for different journal entries in a loan cycle, such as loan origination or interest accrual. Store information, such
as bond ratings and terms, and use it to account for entries across the life of bonds, such as interest accruals or bond
retirement.
Reference objects can either have a direct relationship to transaction objects (primary reference object), or be related to other
reference objects (secondary).
Managing Accounting Sources: Critical Choices

Sources are a key component for setting up accounting rules. Sources represent transaction and reference information from
source systems. Contextual and reference data of transactions that are set up as sources can be used in accounting rules
definitions.
When determining what sources should be available, it is helpful to begin the analysis by considering which information from
your systems is accounting in nature. Examples of sources that are accounting in nature include general ledger accounts that
are entered on transactions, the currency of a transaction, and transaction amounts. Sources that are not always required for
accounting rules include items that are related to the transaction for other purposes than accounting. Examples of information
that may not be specifically for accounting, but which may be useful for creating subledger journal entries, are transaction
identification number (loan number, customer number, or billing account number), counter party information, and transaction
dates.
Provide a rich library of sources from your source systems for maximum flexibility when creating definitions for subledger
journal entries.
Sources are assigned to accounting event classes by submitting the Create and Assign Sources process.
645
There is a distinct difference between sources and source values. Sources represent the transaction attributes used to create
accounting rules. Source values are used by the Create Accounting process to create subledger journal entries based upon
source assignments to accounting rules.
Sources
Sources must be created prior to creating accounting rules. This is a predefined step which must be undertaken before the
application can be used to create subledger journal entries.
To set up appropriate subledger journal entry rule sets, users and those implementing need to understand the origins,
meaning, and context of sources. Use business oriented names for sources to allow accountants and analysts to effectively
create accounting rules.
• Enables users to easily identify a source.
• Ensures consistency in nomenclature.
Source Values
Source values are stored in transaction objects. They are the actual transaction attribute values from the source system and
are used in creation of the journal entries.
Accounting Attribute Assignments: Points to Consider

The Create Accounting process uses the values of sources assigned to accounting attributes plus accounting rules to
create subledger journal entries. Almost all accounting attributes have sources assigned at the accounting event class level.
Depending on the accounting attribute, the accounting attribute assignment defaulted from the accounting event class can be
overridden on journal line rules or subledger journal entry rule sets.
Once sources are assigned to accounting event classes, they are eligible for assignment to accounting attributes for the same
accounting event classes.
The Create Accounting process uses these assignments to copy values from transaction objects to subledger journal entries.
For example, you may map the invoice entered currency to the subledger journal entry entered currency.
Each accounting attribute is associated with a level:
1. Header: To be used when creating subledger journal entry headers.
2. Line: To be used when creating subledger journal entry lines.
The types of accounting attributes values are as follows:
Values that are Subject to Special Processing

You may have values that are subject to special processing or values that are stored in named columns in journal entry
headers and lines.
Examples of accounting attributes are Entered Currency Code and Entered Amount.
Values that Control the Behavior of the Create Accounting Process

You may have values that control the behavior of the Create Accounting process when processing a specific accounting
event or transaction object line.
An example of accounting attributes of this type is Accounting Reversal Indicator.
Minimum Required Accounting Attribute Assignments

In order to create a valid journal entry you must, at a minimum, set up the following accounting attribute assignments.
• Accounting Date
• Distribution Type
646
• Entered Amount
• Entered Currency Code
• First Distribution Identifier
The details and descriptions of these attributes are included in the Accounting Attributes section.
Accounting Attributes
Accounting attribute groups are represented in the tables below:
Accounted Amount Overwrite
• The accounted amount overwrite accounting attribute indicates whether the accounted amount calculated by the
Create Accounting process should be overwritten by the value of the accounted amount accounting attribute. If the
source value mapped to Accounted Amount Overwrite is 'Y', then an accounted amount must be provided.
Accounting Data Type Journal Entry Assignment Assignment Validation

Attributes Level to Rules Required? Rules
Accounted Alphanumeric Line Event Class No Y - Overwrite

Amount and Journal accounted
Overwrite Line Rule amount
Indicator
N - Not
overwrite
accounted
amount

Accounting Date
• The accounting date attribute is relevant to all applications. The Create Accounting process uses it to derive the
accounting date of journal entries. Typically, the event date system source is assigned to the accounting date
attribute.
• The Accrual Reversal GL Date accounting attribute is relevant to applications using the accrual reversal feature.
Users can assign system and standard date sources to the Accrual Reversal GL Date in the Accounting Attribute
Assignments page. When the Accrual Reversal GL Date accounting attribute returns a value, the Create Accounting
process generates an entry that reverses the accrual entry.

Accounting Date Header Event Class Yes Should be in

Date and Journal open general
Entry Rule Set ledger period

Accrual Date Header Event Class No Should be

Reversal GL and Journal later than the
Date Entry Rule Set
647

accounting
date

Accounting Reversal
• Accounting reversal accounting attributes are relevant to applications that wish to take advantage of the accounting
reversal feature. The Create Accounting process uses them to identify transaction (distributions) whose accounting
impact should be reversed. For the Create Accounting process to successfully create a line accounting reversal, the
accounting reversal indicator, distribution type, and first distribution identifier should always be assigned to sources.
The definition of the accounting reversal distribution type and distribution identifiers mirrors the definition of the
distribution identifiers.

Accounting Alphanumeric Line Event Class Yes, if another

Reversal accounting
Distribution reversal
Type accounting
attribute is
assigned.

Accounting Alphanumeric Line Event Class Yes, if another

Reversal First accounting
Distribution reversal
Identifier accounting
attribute is
assigned.

Accounting Alphanumeric Line Event Class No

Reversal
Second
Distribution
Identifier


Reversal Third
Distribution
Identifier


Reversal
Fourth
Distribution
Identifier

648


Reversal Fifth
Distribution
Identifier

Accounting Alphanumeric Line Event Class Yes, if another Y - Reverse

Reversal accounting without
Indicator reversal creating a
accounting replacement
attribute is line
assigned.
B - Reverse
and create a
new line as
replacement

N or Null - Not
a reversal

Transaction Alphanumeric Header Event Class No Y - Reversal

Accounting transaction
Reversal object header
Indicator
N or null -
Standard
transaction
object header

Business Flow
• The business flow accounting attributes are referred to as 'applied to' accounting attributes. If a transaction is
applied to a prior transaction in the business flow, the transaction object must populate sources assigned to 'applied
to' accounting attributes with sufficient information to allow the Create Accounting process to uniquely identify a
transaction object line for a prior event in the business flow. When deriving accounting data from a previous event
in the business flow, the Create Accounting process searches for a journal entry line for the prior event using a
combination of the 'applied to' accounting attributes and the business flow class of both journal entries.
The Applied to Amount accounting attribute is used to calculate the accounted amount and gain or loss in cross-
currency applications when business flows are implemented. This attribute value is used to calculate the accounted
amount when a source is mapped to the Applied to Amount attribute on a journal line type and the entered currency
is different than the original currency entered.
Note
When enabling business flow to link journal lines in the Journal Line Rule page, certain accounting attribute
values are unavailable for source assignment in the Accounting Attributes Assignments window of the same page
because they will be copied from the related prior journal entry.
649

Applied to Number Line Event Class No

Amount and Journal
Line Rule

Applied to Alphanumeric Line Event Class Yes, if another

First System and Journal accounting
Transaction Line Rule attribute in
Identifier the same
group has
assignment.

Applied to Alphanumeric Line Event Class No

Second and Journal
System Line Rule
Transaction
Identifier


Third System and Journal
Transaction Line Rule
Identifier


Fourth System and Journal
Transaction Line Rule
Identifier

Applied to Alphanumeric Line Event Class Yes, if another

Distribution and Journal accounting
Type Line Rule attribute in
the same
group has
assignment.

Applied Alphanumeric Line Event Class Yes, if another

to First and Journal accounting
Distribution Line Rule attribute in
Identifier the same
group has
assignment.


Second and Journal
Distribution Line Rule
Identifier

650

Applied Alphanumeric Line Event Class No

to Third and Journal
Identifier


to Fourth and Journal
Identifier


to Fifth and Journal
Identifier

Applied to Number Line Event Class Yes, if another Must be

Application ID and Journal accounting a valid
Line Rule attribute in application ID
the same
group has
assignment.

Applied to Alphanumeric Line Event Class Yes, if another Must be a

Entity Code and Journal accounting valid Entity for
Line Rule attribute in the application
the same selected in
group has Applied to
assignment. Application ID

Distribution Identifier
• Distribution identifiers accounting attributes are relevant to all applications. The distribution identifier information
links subledger transaction distributions to their corresponding journal entry lines. In addition, many of the Oracle
Fusion Subledger Accounting features, including accounting reversals, rely on the correct definition and storing
of distribution identifiers in the line transaction objects. The distribution type and first distribution identifiers are
always assigned to sources. If a transaction distribution is identified by a composite primary key, additional
distribution identifiers are assigned to standard sources, as appropriate. Values for the distribution type and
distribution identifiers are always stored in accounting transaction objects. The combinations of the values of the
system transaction identifiers with the values of the distribution identifiers uniquely identify a subledger transaction
distribution line.

Distribution Alphanumeric Line Event Class Yes

Type
651


First Alphanumeric Line Event Class Yes

Distribution
Identifier

Second Alphanumeric Line Event Class No

Distribution
Identifier

Third Alphanumeric Line Event Class No

Distribution
Identifier

Fourth Alphanumeric Line Event Class No

Distribution
Identifier

Fifth Alphanumeric Line Event Class No

Distribution
Identifier

Document Sequence
• The document sequence accounting attributes are relevant to applications that use the document sequencing
feature to assign sequence numbers to subledger transactions. The Create Accounting process uses them to
provide a user link between subledger transactions and their corresponding subledger journal entries. Assign all
document sequence accounting attributes to sources or do not assign any. In addition, the Document Sequence
Category Code is made available as an Accounting Sequence Numbering control attribute.

Subledger Alphanumeric Header Event Class Yes, if another

Document accounting
Sequence attribute in
Category the same
group has
assignment.

Subledger Number Header Event Class Yes, if another

Document accounting
Identifier the same

652

group has
assignment.

Subledger Number Header Event Class Yes, if another

Document accounting
Value the same
group has
assignment.

Entered Currency
• Entered currency accounting attributes are relevant to all applications. The Create Accounting process uses them to
populate the journal entry line entered currency code and amounts. The entered currency accounting attributes must
always be assigned to sources. The sources assigned to the entered currency accounting attributes must always
contain a value. For event classes that support cross currency transactions and therefore, more than one entered
currency and entered currency amount, multiple event class accounting attribute assignments are created.

Entered Alphanumeric Line Event Class Yes A valid

Currency and Journal currency code
Code Line Rule

Entered Number Line Event Class Yes

Amount and Journal
Line Rule

Ledger Currency
• Ledger currency accounting attributes are relevant to all applications that use the Create Accounting process.
The Create Accounting process uses them to populate journal entry accounted amounts. If a transaction's
entered currency is different from the ledger currency, the Create Accounting process copies the conversion date,
conversion rate, and conversion rate type to the corresponding journal entry lines. If the entered currency is the
same as the ledger currency, the Create Accounting process ignores the conversion type and conversion rate. For
event classes that support foreign currency transactions and therefore more than one exchange rate and reporting
currency amount, multiple event class accounting attribute assignments are created.

Accounted Number Line Event Class No

Amount and Journal
Line Rule

653

Conversion Date Line Event Class No

Date and Journal
Line Rule

Conversion Number Line Event Class No

Rate and Journal
Line Rule

Conversion Alphanumeric Line Event Class No A valid

Rate Type and Journal general ledger
Line Rule conversion
rate type or
User

Tax
• The tax accounting attributes are relevant to applications that uptake the tax initiative. The tax team uses the tax
accounting attributes to link subledger transaction tax distributions to their corresponding journal entry lines. Oracle
Fusion Tax specifies which tax reference values are mandatory in transaction objects and are assigned to standard
sources.

Detail Tax Number Line Event Class No

Distribution
Reference

Detail Tax Line Number Line Event Class No

Reference

Summary Number Line Event Class No

Tax Line
Reference

Third Party
• Third-party accounting attributes are relevant to subledger applications that use third-party control accounts. The
third-party accounting attributes link suppliers and customers to their corresponding subledger journal entry lines in
the supplier and customer subledgers. For all subledger transactions that represent financial transactions with third
parties, all third-party accounting attributes have sources assigned. If a transaction line is associated with a customer
or supplier, the transaction objects need to include values for all sources mapped to third-party accounting attributes
for the event class.
654

Party Identifier Number Line Event Class Yes, if another If party type C
and Journal accounting - Should be a
Line Rule attribute in valid customer
the same account
group has
assignment. If party type is
S - Should be
a valid supplier
identifier

Party Site Number Line Event Class Yes, if another If party type C
Identifier and Journal accounting - Should be a
Line Rule attribute in valid customer
the same account
group has
assignment. If party type is
S - Should be
a valid supplier
identifier

Party Type Alphanumeric Line Event Class Yes, if another C for

accounting Customer
attribute in
the same S for Supplier
group has
assignment.

Exchange Gain Account, Exchange Loss Account
• The Create Accounting process determines whether there is an exchange gain or loss and derives the account
combination based on whether the journal line rule is defined. If the gain or loss journal line rule is defined, the
account rule assigned to the journal line rule is used to determine the gain or loss account to use. If the gain or loss
journal line rule is not defined, the gain or loss account assigned to the Exchange Gain Account and Exchange Loss
Account accounting attributes is used.

Exchange Number Header Event Class No

Gain Account

Exchange Number Header Event Class No

Loss Account

655
Gain or Loss Reference
• The Gain or Loss Reference accounting attribute groups entry lines together when calculating exchange gain or loss.
The accounted debit and accounted credit amounts for lines with the same gain or loss reference are combined. The
total of accounted debit and total of accounted credit are compared to calculate the exchange gain or loss.

Gain or Loss Alphanumeric Line Event Class No

Reference

Transfer to GL Indicator
• The Transfer to GL accounting attribute is relevant to applications which create subledger journal entries that will
never be transferred to the general ledger. The Transfer to GL process uses this accounting attribute to determine
whether to transfer subledger journal entries to the general ledger.
If the Transfer to GL accounting attribute is not assigned to a source, the Transfer to GL process transfers journal
entries for the event class to the General Ledger.
If the Transfer to GL accounting attribute is assigned to a source and the source is not populated, the Transfer to GL
process transfers journal entries for the event class to the General Ledger.

Transfer to GL Alphanumeric Header Event Class No Should be Y

Indicator or N

Manage Subledger Journal Entry Rule Sets
Creating Subledger Journal Entry Rule Sets: Explained

Subledger journal entry rule sets provide the definition for generating a complete journal entry for an accounting event.
Select the option to define the subledger journal entry rule set for a particular accounting event class or accounting event
type.
If you are using multiple ledgers to meet divergent and mutually exclusive accounting requirements, you can vary journal entry
rule sets by ledger. Each of the subledger journal entry rule sets can meet a specific type of accounting requirements.
For example, use US Generally Accepted Accounting Principles (GAAP) oriented subledger journal entry rule sets for a ledger
dedicated to US GAAP reporting, and French statutory accounting conventions for a ledger dedicated to French statutory
reporting. These two sets of definitions have differences based on the setup of the various components that make up their
subledger journal entry rule sets.
656
Predefined subledger journal entry rule sets are provided for all Oracle subledgers. If specific requirements are not met by
predefined subledger journal entry rule sets, users can create a copy of the predefined definitions and then rename and
modify the copied definitions and their assignments.
Subledger journal entry rule set assignments can be made at two levels, header and line. The following are the
subcomponents of a subledger journal entry rule set:
• Description rules
• Journal line rules
• Account rules
Assignment at Header Level

Header assignments define subledger journal header information and line assignments define journal line accounting
treatment.
A header assignment includes the following:
• Accounting date (required)
• Accrual reversal accounting date (optional)
• Description rule (optional)
Assignment at Line Level

You can define multiple subledger journal entry rule sets for an accounting event class or accounting event type. A single
journal entry is generated per accounting event per ledger using the line assignments from the journal entry rule set assigned
to the accounting event class or accounting event type.
The following can be assigned to a journal entry line:
• Journal line description rule
• Journal line rule
• Account rule
• Supporting references
Assignment of Description Rules

If a description rule is defined with sources, the sources must also be assigned to the accounting event class that is assigned
to the journal entry rule set. The description rule may be assigned at either the header or line level of the journal entry or to
both levels.
Assignment of Journal Line Rules

When assigning the journal line rule, you must identify the line type: Gain, Loss, Gain or Loss, Credit, or Debit. The journal line
rule must be assigned to the same accounting event class as the one assigned to the subledger journal entry rule set.
657
When assigning a journal line rule that is enabled for accounting for a business flow, the account combination and certain
accounting attribute values are copied from its related journal line having the same business flow class as the current line.
Optionally, copy the description rule into the current line instead of assigning a separate description rule.
When assigning a journal line rule that is enabled to copy from the corresponding line within the same journal entry, you have
the option to copy the account combination, the segment value, or the line description from the corresponding line into the
current line.
Assignment of Account Rules

The account rule assignment will define which accounts will be used for the subledger journal line. If the account rule is setup
with a chart of accounts, it must have the same chart of accounts as the one assigned to the journal entry rule set. When
account rules are defined with sources, the sources must also be assigned to the accounting event class that is assigned the
journal entry rule set.
There are two types of account rules:
• Account Combination Rule: Assign an account combination rule to derive the account combination.
• Segment Rule: Assign a segment rule to derive a specific segment of an account. For example, a cost center or a
natural account segment.
Assignment of Supporting References

Supporting references may be used to capture transaction values on journal entry lines. A supporting reference can be used
on a journal entry rule set only if it is assigned a source from the event class of the journal entry rule set.
Manage Journal Line Rules
Journal Line Rules: Explained

Journal line rules are defined within the context of accounting event classes. A journal line rule can be used in a subledger
journal entry rule set that has the same event class. You may also assign conditions to the journal line rule.
Journal Line Rules

Journal line rules are assigned to journal entry rule sets.
To create a journal line rule, select values for options such as:
• Side (Debit, Credit, Gain or Loss)
For example, when an Oracle Fusion Payables invoice is generated, the liability account should normally be credited.
The journal line rule must therefore specify the Side option as Credit. On the other hand, the payment of the
Payables invoice must be accounted with a debit to the liability account. A separate journal line rule must be defined
to create this debit line.
• Merge Matching Lines: To summarize subledger journal entry lines within each subledger entry. Journal entry lines
with matching criteria are merged.
• Accounting Class
◦ Select an accounting class to classify journal entry lines.
658
◦ For example, when a validated Payables invoice is accounted, the Item Expense and Liability journal lines are
created. In this case, the journal line rules used in the accounting rules are assigned Item Expense and Liability
accounting classes respectively.
• Conditions: To restrict the use of a journal line rule by controlling when a particular journal line rule is used by the
Create Accounting process.
• Accounting Attributes: When creating a journal line rule, accounting attribute assignments are automatically
established based on the default accounting attribute assignments for that journal line rule's accounting event class.
You can override this default mapping of standard sources to accounting attributes. The list of values for the source
override includes all sources assigned to the accounting attribute for the event class associated with the journal line
rule.
• Advanced Options
◦ The Subledger Gain or Less Option: Applies only to amount calculations for the primary ledger. Gain or loss
amounts are not converted to reporting currency or non-valuation method secondary ledgers. If the option is
selected, the journal line holds the gain or loss amounts calculated by the subledger.
The gain or loss amount is calculated as the difference in applied amounts due to fluctuations in conversion
rates based upon conversion to the ledger currency. Foreign exchange gain or loss amounts occur when
two related transactions, such as an invoice and its payment, are entered in a currency other than the ledger
currency, and the conversion rate fluctuates between the times that the two are accounted.
◦ The Rounding Class Option: Along with the transaction rounding reference group journal lines together and
calculates transaction rounding. Subledger transaction rounding differences can occur when a transaction has
multiple related applied-to transactions, such as when a Receivables invoice has multiple associated receipts.
◦ The Link Journal Lines Option: Determines whether the journal line rule is set up to establish a link between
the accounting of transactions that are related both within the same application, and across applications. The
alternatives are described in this table:
Link Journal Lines Option Description
None No link is established.

Copy from corresponding line Build account for a journal line using segments from the
offsetting entry of the current journal line. For example,
when the business process requires that a cost center
incurring an expense must also bear the invoice liability
and cash outlay.

Business flow Link logically related business transactions. For example,

when recording the closing of a loan, you can link to
the account that was used to book the loan origination.
Journal line rules that are linked must also be assigned
the same business flow class.

659
Defining Conditions for Journal Line Rules

You may set conditions to specify whether the journal line rule will be used to create a subledger journal entry line. If the
conditions are true, the line rule is used to create a subledger journal entry line. Use sources to create these conditions.
For example, you can set up a condition that will create a journal line to record tax, only if there is tax for an invoice. The line
type and account class mentioned here are examples of sources.
• The condition for a Payables invoice tax journal line rule could be:
◦ Where Line Type = Tax
◦ When this condition is true, there is tax for a payables invoice line. A journal entry line is created to record the
accounting impact of the tax.
• Similarly, the condition for a Oracle Fusion Receivables invoice tax journal line rule could be:
◦ Where Account Class = Tax
◦ In this case, if there is an account class of Tax, the journal line is used to record the accounting impact of the
tax.
Another example is a condition that creates a journal line for freight when there are freight charges on an invoice.
Journal line rule conditions determine whether a journal line rule and its associated account rules and description rules, are
used to create the subledger journal entry line.
Note
Constant values that are used in any Conditions region must not contain the following characters:
• "
• ,
• &
• |
• (
• )
• '
For example, in the condition "Project Type" = ABC (123), the constant value following the equal sign, ABC (123),
contains restricted characters ( ) that enclose 123 and is invalid.
660
Manage Account Rules
Account Rules: Explained

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 defining accounts under different
circumstances to meet your specific requirements. You can define account rules for an account, segment, or value set.
Account Rules by Account

Define account rules by account to determine the entire account combination. For example, an account rule defined by
account can be used to determine the complete supplier liability account in Oracle Fusion Payables.
Account Rules by Segment

Define segment rules to derive a specific segment of the general ledger account. For example, a particular segment like the
company segment can be determined from the distribution account. Another segment can be determined with the use of a
constant value. Creating the account one segment at a time offers greater flexibility, but also requires more setup.
Use both segment based and account based rules to derive a single account. Segment specific rules are used, where they
are defined, and take the remaining values from an account based rule. For example, you can select an account rule which is
for all segments and also separately select a rule which is for one particular segment. Segment specific 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. However, if the segment rule has conditions associated with the priorities and none
of the conditions are met, no override occurs and therefore, 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 defined in Oracle Fusion General Ledger, an 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.
Account Rules by Value Sets

In the absence of a chart of accounts, you may define account rules based upon value sets. This enables you to share the
same rule between more than one chart of accounts if the segments in these charts of accounts share the same value set.
Sharing Account Rules across Applications

You may share account rules across applications in the following ways.
• Assign an account rule from the same or a different 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 by Oracle Fusion Projects 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 assigned in the
661
Priorities region. You may attach 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, and
verification occurs to confirm 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.
Account Rules and Mapping Sets

Mapping sets can be used to associate a specific output value for an account or segment. You can use mapping sets in
account rules to build the account.
Account Rules Conditions

In the account rules you may specify conditions for each rule detail line. Priorities determine the order in which account rule
conditions are examined. When the condition is met, the rule associated with that priority is used. Depending on which of the
defined conditions is met, a different account rule detail is employed to create the account.
The Create Accounting process evaluates conditions based on the priority of the rule detail. When the condition is met, the
rule detail is applied.
Creating Account Rules: Points to Consider

You can define an account rule using the following rule types:
• Account combination
• Segment
• Value set
Account Combination Rules

Set up account combination rules based upon the following value types:
1. Source Value Type: Derive the account combination by specifying a source. Sources that have been set up as
accounts can be assigned to an account combination rule. Oracle Fusion Subledger Accounting then obtains the
account combination identifier from the source.
2. Constant Value Type: Establish the account as a constant value.
For example, the constant could be a completed account combination from the chart of accounts specified. An
example is the account combination, 01.000.2210.0000.000. This is the simplest way to derive an account.
3. Mapping Set Value Type: Derive the account combination by referencing a mapping set. Set up a mapping set to
determine the complete account combination from the chart of accounts specified.
4. Account Rule Value Type: Derive the account by referencing another account rule.
The chart of accounts is optional when defining 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.
662
Note
A chart of accounts must be specified for rules using constants.
Segment Rules
Set up segment rules as follows:
• When a chart of accounts is specified, create a rule to derive the value for a specific segment from the chart of
accounts.
• If the chart of accounts is not specified, create a rule to derive the value for an account segment with a specific
qualifier.
Set up segment rules using the same methods discussed in the preceding Account Combination Rules section. By specifying
different value types, users can select the way in which the segment value is derived.
Note
A chart of accounts must be specified for rules using constants.
Value Set Rules

Value set based rules can be created when a chart of accounts is not specified. This enables you to share the same rule
between more than one chart of accounts if the segments in these charts of accounts share the same value set.
Set up value set based rules using the same methods discussed in the preceding Account Combination Rules section.
Manage Description Rules
Creating Description Rules: Explained

Use descriptions rules to define the elements of a description that appears on the subledger journal entry at the header or
the line. The definition determines both the content and sequence in which the elements of the description appear. You can
assign a condition to a description rule to determine that the description is selected for display if the condition is satisfied.
Description Rule Definition

A description rule can be defined with combinations of source and literal values. If sources are used in the rule, the
accounting event class associated with the sources determines in which subledger journal entry rule set the description rule
can be selected and used.
Build descriptions using the available sources for the application.
The following is the description details that have been entered, using a literal and a source:
• Loan Origination Date = Origination Date
◦ Literal = Loan Origination Date
◦ Source = Origination Date
663
Assuming that the source value of the Origination Date is 11/01/11, then a journal entry that has the above description rule
attached will have the description, Loan Origination Date 11/01/11.
664
Implementing Project Financial Management Define Approval Management
47 Define Approval Management
Approval Management: Highlights

Use approval management to define policies that apply to approval workflows. For example, to reflect your own corporate
policies, you can specify levels of approval for expense reports over a particular amount and determine how the approvals are
routed.
To define approval management, use these tasks in the Setup and Maintenance work area:
• Manage Task Configurations
• Manage Approval Groups
Task Configuration
Manage rule sets and rules that control approval flows.
• To configure a predefined approval policy, select the predefined rule set and click the Edit Task icon.
• To disable a predefined rule set, select the Ignore participant check box for that rule set.
• To edit the rules within a predefined rule set, you can insert, update, or delete while in edit mode.
• You can configure a specific 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).
◦ Set the Auto Action Enabled option to True.
◦ Enter APPROVE in the Auto Action field.
Approval Groups
Each approval group includes a set of users that you configure to act on tasks in a certain pattern. Task can be defined 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 defining the group:
◦ Static: Select the specific users to include in the group.
◦ Dynamic: Provide the logic to use to determine the users in the group.
Customization
You can also customize predefined approval workflows, for example add post-approval activities or additional stages (not
available for Oracle Cloud implementations).
• Refer to the Oracle Fusion Applications Extensibility Guide for Developers.
See: Customizing and Extending SOA Components
665
Implementing Project Financial Management Define Help Configuration
48 Define Help Configuration
Setting Up Help: Overview

Applications Help works without you having to set anything up. You can do the optional setup, mainly if you want to
customize help. Select the help features you want, perform tasks in the Define Help Configuration task list, and customize
help.
Help Feature Choices

Select help feature choices on the Configure Offerings page in the Setup and Maintenance work area, to determine:
• What's available in Applications Help
• What you can configure to set up help
The first feature choice for help is Local Installation of Help, and you must leave it selected. Other feature choices are:
• Access to Internet-Based Help Features
• Help Customization
• Custom Help Security
Define Help Configuration Task List

In the Setup and Maintenance work area, use these tasks in the Define Help Configuration task list to configure Applications
Help for all users:
• Set Help Options:
◦ Determine if certain features of Applications Help are available to users.
◦ Control how aspects of Applications Help work.
• Assign Help Text Administration Duty: Determine who can customize help.
• Manage Help Security Groups: Set up security to limit access to certain help files.
Help Customization
After you configure help, you can review the predefined help and see if you want to add or customize any content. You can
also customize help text that appears on the page, for example hints.
666
Related Topics
• Feature Choices: Explained
• Help File Customization: Overview
• Customizing Help That Appears on the Page: Highlights
Set Help Options
Setting Up Help Customization: Procedure

Users with the appropriate roles can customize predefined help or add their own files to help. To enable and set up help
customization, do the following steps in the Setup and Maintenance work area, in the specified order.
Selecting Feature Choices

Perform these steps:
1. On the Configure Offerings page, leave the Location Installation of Help feature choice selected.
2. Select the Help Customization feature choice.
3. Select the Custom Help Security feature choice if you want certain help files to be available only to a restricted set of
users.
Warning
Don't select this feature choice if you don't have this requirement, because the feature can affect
performance.
4. Save your work.
Setting Help Options

Perform these steps:
1. Open the Set Help Options task in the Setup and Maintenance work area.
2. Optionally set options in these sections:
◦ Help Site Customization:
• Determine how users can identify custom files in Applications Help.
• Upload your own image to use as the background picture on the help home page.
667
◦ Oracle User Productivity Kit (UPK): Add a link in the Navigator in Applications Help to your custom UPK
library.
◦ Privacy Statement: Give users a link to your own privacy statement when they click their user name in the
global area of Applications Help.
3. Save your work.
Providing Users Access to Help Customization

Only users with job roles containing the Application Help Text Administration duty role can customize help. The Assign Help
Text Administration Duty task is a reminder to make sure that the users you want to customize help have access to do so.
Setting Up Help File Security

If you selected the Custom Help Security feature choice, then go to the Manage Help Security Groups task and select job
roles to include in help security groups.
When you later customize a help file, you can select a group to determine which job roles have access to the file.
FAQs for Set Help Options

When do I link to the Oracle User Productivity Kit library from Applications Help?
If you license Oracle User Productivity Kit (UPK) and have custom UPK content to share with your users. UPK demos that you
add as custom help files in Applications Help are available only in the See It mode, but in the library, users can see the same
demo in other modes. If you have UPK versions earlier than 3.6.1, then you can't add UPK demos as custom help, so the link
is the only way for users to get custom UPK content from Applications Help.
What's the URL for my Oracle User Productivity Kit library?

The full path from the Web server where you're hosting your Oracle User Productivity Kit (UPK) content to the index.html file that
opens the table of contents for the library, for example, http://<your domain>.com/UPKcontent/PlayerPackage/index.html.
In this example, you or your UPK administrator published one UPK player package that contains all the content to be linked to
from Applications Help, including the index.html file, and placed the PlayerPackage folder in a folder called UPKcontent on the
Web server.
FAQs for Assign Help Text Administration Duty
Who can add and manage custom help?

Users with the Application Help Text Administration duty role can customize help in Applications Help and help windows, as
well as the pages in the Getting Started work area. This duty is assigned by default to the administrators for product families.
You can provision other users a job role that inherits the Application Help Text Administration duty role. If no existing job role
is appropriate, you must create a custom job role that inherits this duty role.
Related Topics
• How do I provision roles to users?
668
• Creating a Custom Job or Abstract Role: Procedure
Manage Help Security Groups
Creating Help Security Groups: Worked Example

This example shows how to create a help security group, which contains a set of job roles. You can later assign the help
security group to particular help files so that only users with any of the included job roles have access to the help.
What type of users do you need to limit help access to? Human resources (HR) specialists

Is there a specific time period for which this access is No, the help files should always be viewed only by the
needed? HR specialists

Where do you want this group to appear in the list of First

values for help security groups?

Define a help security group and assign a job role to the group.
Prerequisites
1. Open the Configure Offerings page in the Setup and Maintenance work area.
2. Make sure that the Location Installation of Help feature choice is selected.
Creating the Help Security Group

1. In the Setup and Maintenance work area, go to the Manage Help Security Groups task.
2. On the Manage Help Security Groups page, add a new row.
3. Complete the fields, as shown in this table. Leave the start and end dates blank.
Field Value
Help Security Group HR

Meaning HR Only

669
Field Value
Description Viewing by HR specialists only

Display Sequence 1

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.
When you create a help security group, you also automatically create:
◦ A new lookup code for the Help Security Groups lookup type, which is a standard lookup. The lookup code
has the name, meaning, and description that you defined for the help security group.
◦ A data security policy for the help database resource (ATK_KR_TOPICS), specifying that the Human Resource
Specialist role can view help that is defined with the HR security group.
On the Manage Database Resources and Policies page, ATK_KR_TOPICS would have a policy for the Human
Resource Specialist role, with the condition that the column name, SECURITY_CODE, is equal to the value HR.
Related Topics
• Lookups: Explained
• How can I edit lookups?
• Database Resources and Data Security Policies: How They Work Together
670
Implementing Project Financial Management Define Application Toolkit Configuration
49 Define Application Toolkit Configuration
Define Application Toolkit Configuration: Overview

Oracle Fusion Application Toolkit (ATK) provides many features that are available to users of all product families, including
Applications Help, the Reports and Analytics pane, and the Watchlist in the global area. In the Setup and Maintenance work
area, use the Define Application Toolkit Configuration task list to set up some of these components, and the Define Help
Configuration task list to set up Applications Help.
Note
The Define Application Toolkit Configuration task list is available in implementation projects only if the Application
Toolkit Component Maintenance feature choice is selected.
Related Topics
• Setting Up Help: Overview
Map Reports to Work Areas
Defining What's Available in the Reports and Analytics Pane:

Procedure
The Reports and Analytics pane provides access to analytics and reports. You can find the pane in many work areas, and
what you see in the pane depends on the work area. You can define what's available for a specific work area, by mapping
reports from the business intelligence (BI) catalog to that work area.
Note
• In this mapping context, reports refer to both analytics and reports.
• Your changes apply to all users who have access to the work area you're mapping.
Mapping Reports to the Work Area You're In

Follow these steps:
1. Click the Edit Settings icon in the Reports and Analytics pane.
You see all the reports that are currently mapped to your work area.
2. Click Select and Add.
671
3. Find the report in the catalog and select it.

4. Click OK.
5. To remove any mapping, select the report and click Remove.
6. Save your work.
Mapping Reports to Any Work Area You have Access To

Follow these steps:
1. Go to the Setup and Maintenance work area and open the Map Reports to Work Areas task.
2. Select the application of the work area you want to map to.
3. Select the work area.
4. Click Search and see all the reports that are currently mapped to that work area.
5. Click Select and Add.
6. Find the report in the catalog and select it.
7. Click OK.
8. To remove any mapping, select the report and click Remove.
Tip
Click the Synchronize button to remove all mappings to any reports that are no longer in the catalog.
You synchronize all work areas, not just the one you're mapping.
9. Save your work.
Related Topics
• Reports and Analytics Pane: Explained
Setting Up Reports for Scheduling in the Reports and Analytics

Pane: Procedure
You can set up reports as scheduled processes, which means users can submit them from the Scheduled Processes and
other work areas. If you want users to also submit these scheduled processes from the Reports and Analytics pane, then you
must configure properties for the corresponding reports.
Enabling a Report for Scheduling

To enable scheduling in the Reports and Analytics pane:
1. Select the report in the business intelligence catalog and click Edit.
2. Click Properties.
3. On the General tab in the Properties dialog box, enter the following fields:
672
Field Value
Enterprise Scheduler Job Package Name The path for the job definition, for example: / oracle/
apps/ ess/<product family>/ <product>/ <business
area>/ Jobs

Enterprise Scheduler Job Definition Name The job definition name (not display name), for example:
ABCDEFG

Related Topics
• Setting Reports Up to Run as Scheduled Processes: Points to Consider
• Accessing Report Components to Customize: Points to Consider
FAQs for Map Reports to Work Areas

Why can't I see reports when mapping reports to work areas for the Reports and Analytics
pane?
It's possible that no reports are currently mapped to the work area you select on the Map Reports to Work Areas page. Or,
reports are mapped, but you can't see them due to security.
Similarly, when you're selecting a report to map, you can see only the reports that you have access to. Ask your administrator
to either:
• Give you roles with access to the reports that you want to map.
• Grant the Reports and Analytics Region Administration Duty to someone who already has access to those reports.
Why can't I see reports when I edit settings for the Reports and Analytics pane?
In the Edit Settings window, you might not see a currently mapped report because you don't have access to it.
Similarly, when you're selecting a report to map, you can see only the reports that you have access to. Ask your administrator
to either:
• Give you roles with access to the reports that you want to map.
• Grant the Reports and Analytics Region Administration Duty to someone who already has access to those reports.
Set Watchlist Options
Disabling and Enabling Watchlist Categories and Items: Points

to Consider
You can disable or enable predefined Watchlist categories and items for all users. Use the Set Watchlist Options task in the
Setup and Maintenance work area.
673
Ultimately, what users see in their own Watchlist would be the categories and predefined 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 chooses to hide using Watchlist preferences
• Minus any items with no results found, if the user chooses to hide such items using Watchlist preferences
Any Category or Item

When you disable any category or item, you also disable the processes that calculate the Watchlist item counts. These
processes include creating data caches, performing security checks, invoking services across domains, running queries, and
so on.
Predefined Watchlist Items

An item with the Predefined type represents the actual predefined Watchlist item that appears in the Watchlist.
If you disable this type of Watchlist item, then:
• The item isn't available for users to display in their Watchlist.
• The item is removed from any Watchlist where it's currently displayed.
If you disable a Watchlist category, then the category is not available for users to include in their Watchlist, and all Watchlist
items within the category are also disabled.
User-Created Saved Search Watchlist Items

A Watchlist item with the User-Created Saved Search type doesn't appear in the Watchlist. It controls the display of the
Manage Watchlist button on pages with saved searches in the local area.
If you disable this type of Watchlist item, then:
• The Manage Watchlist option isn't available on the corresponding page, so users can't use their own saved
searches as Watchlist items.
• Any user-defined saved searches (from that page) already used as Watchlist items are removed from the users'
Watchlist. The saved searches are still available for searching, but not for the Watchlist.
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.
Related Topics
• Creating Watchlist Items: Procedure
674
• Displaying and Hiding Watchlist Items: Procedure
675
Implementing Project Financial Management Maintain Common Reference Objects
50 Maintain Common Reference Objects

Maintain Common Reference Objects: Overview
The Maintain Common Reference Objects task list contains Oracle Middleware Extensions for Applications (Applications
Core) tasks that support implementation of common behaviors, such as data security or reference data sets.
Use this task list to manage common reference objects that are defined centrally and shared across applications, in addition
to those that are specific to Applications Core functionality. You can access this task list by starting in the Setup and
Maintenance Overview page and searching for common reference object task lists.
For more information on configuring custom objects, see the Oracle Sales Extensibility Guide.
To make the Maintain Common Reference Objects task list available in your implementation project, go to Setup and
Maintenance Overview - Configure Offerings , and for a specific offering, select the Maintain Common Reference
Objects feature choice.
Related Topics
• Moving Common Reference Objects: Overview
Why can't I edit setup data?

The configuration of your setup data may be protected. Application developers mark some configurations as protected,
indicating that you can't edit them.
Some examples of configurations that may be protected are:
• Descriptive flexfields
• Extensible flexfield contexts
• Extensible flexfield pages
• Value sets
• Tree structures
Define Application Taxonomy
Application Taxonomy: Highlights

Application taxonomy is the organization of Oracle application components and functions in a hierarchical structure,
from product lines to logical business areas. This hierarchy represents a breakdown of products into units based on how
applications are installed and supported. Maintain this hierarchy on the Manage Taxonomy Hierarchy page, which you can
access by starting in the Setup and Maintenance Overview page and searching for the Manage Taxonomy Hierarchy task.
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.
676
See: Characteristics of the Level Categories
See: Benefits of a Logical Hierarchy
Usage
• Use application taxonomy to understand relationships among applications and between an application and its files.
This information is helpful in managing various phases of the product lifecycle.
See: How to Manage the Lifecycle
Modules in Application Taxonomy: Explained

A module is any node in the application taxonomy hierarchy. The top level of the hierarchy is product line, followed by product
family, application, and logical business area. There can be multiple levels of logical business areas, with one or more nested
within a parent logical business area.
Product Line
A product line is a collection of products under a single brand name, for example, Oracle Fusion.
Product Family
A product family is a collection of products associated with a functional area that may or may not be licensed together as a
single unit, for example Financials.
Application
An application is a single product within a product family, containing closely related features for a specific business solution,
for example General Ledger.
Logical Business Area

A logical business area is a collection of business object definitions organized into a logical grouping. It contains the model
objects, services, and UI components for those business objects. Logical business areas have their own hierarchy levels
and in some cases can be two or three levels deep. Each leaf node has at least one business object and service, up to a
maximum of four business objects and associated services. A logical business area with more than four business objects
are further refined with child logical business area levels. Each of these parent-child levels is represented by a directory in the
physical package hierarchy.
Managing Modules in Application Taxonomy: Points to

Consider
Manage modules on the Create Child Module or Edit Module page, which you can access by starting in the Setup and
Maintenance Overview page and searching for the Manage Taxonomy Hierarchy task. When you create a module, it is a child
of the currently selected node in the application taxonomy hierarchy. This determines which values are available, for example
for module type. Once created, you cannot delete the module or move it elsewhere in the hierarchy. As you create or edit
modules, consider the following points regarding specific fields.
Identifiers
Module ID is the unique primary key for nodes in the taxonomy table. When you create a module, an ID is automatically
generated. Once the module is created, you cannot update the ID.
Module key and alternative ID are additional identifiers of the module, presented in a way that is easier to read than the
module ID. The module key is a string identifier, for example AP for the Oracle Fusion Payables application. The alternative ID
677
is a numeric identifier, for example 1 for the Oracle Fusion product line. These IDs are provided for the product line, product
family, and application modules, but you can optionally add them for logical business areas and new custom modules.
Note
Do not change the module key or alternative ID for predefined modules.
The product code is relevant only to application and logical business area modules. You can leave the field 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 Middleware Extensions for Applications.
Names
Module name is the logical name for the module and is always available. The name must be unique among nodes in the same
hierarchy level with the same parent, but try to make it as unique in the whole hierarchy as possible.
The user name and description can appear to users in other parts of Oracle Fusion Applications, so make sure that the values
are something that users know to represent the module.
Usage Types
Though you can update the usage type to reflect the current state of the module, just doing so does not affect the actual
state. For example, setting a module as installed does not mean it is actually installed if the installation itself has not taken
place. Installation refers to operations related to laying down all the components needed to create an Oracle Fusion
Applications environment, while deployment is the process that starts the managed servers and clusters and facilitates the
actual use of product offerings. 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 seed data such as flexfields and lookups can be extracted for the module using seed data
loaders. By default, extract is allowed for all predefined modules of type application and logical business area.
Associations
You can associate a logical domain to modules of 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 Fusion Applications Functional Core (ASK) tables.
Define Reference Data Sharing
Reference Data Sharing: Explained

Reference data sharing facilitates sharing of configuration data such as jobs and payment terms, across organizational
divisions or business units. You define reference data sets and determine how the data is shared or partitioned. Use reference
data sets to reduce duplication and maintenance by sharing common data across business entities where appropriate.
Depending on the requirement (specific or common), each business unit can maintain its data at a central location, using a
set of values either specific to it or shared by other business units.
You can share reference data after it is filtered on the basis of sets. 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 cannot be assigned to an entity, you can create specific 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 managers in different
business units setting up the same grades, XYZ Corporation decides to create a set called Grades and assign the grades
reference data group for all business units in the organization to the Grades set, so that the grades can be shared.
678
Note
For specific information on configuring reference data sharing for a particular object or product, refer to its product
documentation.
Related Topics
• Reference Data Sets: Explained
• Assigning Reference Data Sets to Reference Objects: Points to Consider
Reference Data Sets: Explained

Reference data sets are logical groups of reference data that can be accessed by various transactional entities depending
on the business context. Oracle Fusion Applications contains a common reference data set as well as an enterprise set that
may be used as a default set. Depending on your business requirement you can create and maintain additional reference data
sets, while continuing to use the common reference data set.
Consider the following scenario.
Partitioning
The partitioning of reference data and creation of data sets enable you to create reference entities across tables or lookup
types, and share modular information and data processing options among business units. With the help of partitioning, you
can choose to create separate sets and subsets for each business unit depending upon its business requirement, or create
common sets or subsets to enable sharing reference data between several business units, without the need for duplicating
the reference data. Partitioning provides you the flexibility to handle the reference data in a way appropriate to your business
needs.
679
The following figure illustrates the reference data sharing method (assignment to one set only, with common values) where the
user can access the data assigned to a specific set in a particular business unit, as well as access the data assigned to the
common set.
Related Topics
• Defining Default Reference Data Sets : Points to Consider
• Assigning Reference Data Sets to Reference Objects: Points to Consider

Reference Data Sets

680

Note
Related Topics
• What reference data objects can be shared across project units?
• What reference data objects can be shared across cost organizations?
• What reference data objects can be shared across business units?
• Items and Supplier Site Reference Data Sharing: Explained
Assigning Reference Data Sets to Reference Objects: Points to

Consider
You can assign the reference data sets to reference objects on the Manage Reference Data Set Assignments page. For
multiple assignments, you can classify different types of reference data sets into groups and assign them to reference entity
objects. The assignment takes into consideration the determinant type, determinant, and reference group, if any.
681
Determinant Types
The partitioned reference data is shared based on a business context setting called the determinant type. It is the point of
reference used in the data assignment process. The following table lists the determinant types used in the reference data
assignment.
Type Description
Asset Book Information about the acquisition, depreciation, and

retirement of an asset that belongs to a ledger or a
business unit.

Business Unit The departments or organizations within an enterprise.

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

is responsible for enforcing consistent project
management practices.

Reference Data Set References to other shared reference data sets.

Determinant
The determinant or determinant value is the value that corresponds to the selected determinant type. The determinant is
one of the criteria for selecting the appropriate reference data set. For example, when managing set assignments for the set
determinant type, Reference Data Set is the determinant type, and you would enter the corresponding set code value as the
corresponding determinant value.
Reference Groups
A transactional entity may have multiple reference entities (generally considered to be setup data) that are treated in the same
manner because of commonness in implementing business policies and legal rules. Such reference entities in your application
are grouped into logical units called reference groups, based on the functional area and the partitioning requirements that
they have in common. For example, all tables and views that define Sales Order Type details might be part of the same
reference group.
Note
The reference groups are predefined in the reference groups table and are available for selection and assignment.
682
Define ISO Reference Data
Defining Currencies: Points to Consider

When creating or editing currencies, consider these points relevant to entering the currency code, date range, or symbol for
the currency.
Currency Codes
You cannot change a currency code after you enable the currency, even if you later disable that currency.
Date Ranges
Users can enter transactions denominated in the currency only for the dates within the specified range. If you do not enter a
start date, then the currency is valid immediately. If you do not enter an end date, then the currency is valid indefinitely.
Symbols
Even if you enter a symbol for a currency, the symbol is not always displayed when an amount is displayed in this currency.
Some applications use currency symbols when displaying amounts. Others, like Oracle Fusion General Ledger, do not.
Related Topics
• What's the difference between precision, extended precision, and minimum accountable unit for a currency?
• Euro Currency Derivation: Explained
Euro Currency Derivation: Explained

Use the Derivation Type, Derivation Factor, and Derivation Effective Date fields to define the relationship between the official
currency (Euro) of the European Monetary Union (EMU) and the national currencies of EMU member states. For each EMU
currency, you define its Euro-to-EMU fixed conversion rate and the effective starting date.
Note
If you need to use a different currency code for Euro, you can disable the predefined Euro currency and create a
new one.
Derivation Type
The Euro currency derivation type is used only for the Euro, and the Euro derived derivation type identifies national
currencies of EMU member states. All other currencies do not have derivation types.
Derivation Factor
The derivation factor is the fixed conversion rate by which you multiply one Euro to derive the equivalent EMU currency
amount. The Euro currency itself should not have a derivation factor.
Derivation Effective Date

The derivation effective date is the date on which the relationship between the EMU currency and the Euro begins.
683
Natural Languages: Points to Consider

Natural languages are all the languages that humans use, written and spoken. If a language is enabled, then users can
associate it with entities, for example as languages spoken by sales representatives. When managing natural languages,
consider tasks to perform and best practices for entering particular values.
Tasks
Once you add a language, it cannot be deleted, 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 prefix 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 should be the language name with territory name in parenthesis where needed, for example
English (Australia) and English (Canada).
FAQs for Define ISO Reference Data

When do I create or edit territories?
Edit territory descriptions to determine how they are displayed in lists of country values throughout Oracle Fusion
Applications. The predefined territories are all countries from the International Organization for Standardization (ISO) 3166
standard. You usually would not edit territory names or codes.
Do not edit National Language Support (NLS) territory codes, which are identifiers used in the system, unless you need to
change the association between ISO and system territory. You usually would not edit the default currency, which is the value
that defaults in the Currency field in Oracle Fusion Applications user preferences after the user first selects a territory.
Create territories if new countries emerge and the system has not yet been patched with the latest ISO country values.
When do I create or edit industries?

Edit industry descriptions to determine how they are displayed in Oracle Fusion Applications. You usually would not edit
industry names, which are from the North American Industry Classification System (NAICS). Enabled industries are mainly
used in the context of customization, though these values can also appear in any application.
Create industries if you have particular ones you need, for example for customization, that are not included in the NAICS
standard.
When do I associate industries with territories?

To meet specific business needs, you can associate industries with territories. For example, administrators can customize a
page in different ways for different sets of users of the same industry, but residing in different countries.
When do I create or enable currencies?

Create or enable any currency for displaying monetary amounts, assigning currency to ledgers, entering transactions,
recording balances, or for any reporting purpose. Oracle Fusion Applications supports all currencies from the International
Organization for Standardization (ISO) 4217 standard.
The default currency is set to United States Dollar (USD).
684
Related Topics
• Defining Currencies: Points to Consider
What's the difference between precision, extended precision, and minimum accountable
unit for a currency?
Precision is the number of digits to the right of the decimal point used in regular currency transactions. Extended precision
is the number of digits to the right of the decimal point used in calculations for this currency, and it must be greater than or
equal to the standard precision. For example, USD would have 2 for precision because amounts are transacted as such, for
example $1.00. For calculations, for example adding USD amounts, you might want the application to be more precise than
two decimal digits, and would enter an extended precision accordingly.
Note
Some applications use extended precision. Others, such as Oracle Fusion General Ledger, do not.
Minimum accountable unit is the smallest denomination for the currency. For example, for USD that would be .01 for the cent.
This unit does not necessarily correspond to the precision for all currencies.
What's a statistical unit currency type?

The statistical unit currency type denotes the Statistical (STAT) currency used to record financial statistics in the financial
reports, allocation formulas, and other calculations.
When do I create or edit ISO languages?

You can edit the names and descriptions of International Organization for Standardization (ISO) languages to determine how
they are displayed in lists of ISO language values in Oracle Fusion Applications. The ISO languages are from the ISO 639
standard. If there were changes to the ISO standard and the system has not yet been patched with the latest ISO values, you
can update the ISO alpha-2 code or add languages as needed.
When do I edit languages?

Installed languages automatically appear on the Manage Languages page, so you do not manually enter newly installed
languages. This page contains all languages available for installation and translation in Oracle Fusion Applications. Each
dialect is treated as a separate language. The language codes and names are values used by the system.
You generally would not edit any of the detailed fields unless you really need to and know what they are.
When do I create or edit time zones?

Though all standard time zones are provided, optionally enable only a subset for use in lists of time zone values in Oracle
Fusion Applications. You can add time zones if new zones became standard and the system has not yet been patched with
the latest values.
Manage Data Security Policies
Data Security in the Security Reference Implementation:

Explained
The reference implementation contains a set of data security policies that you can use, or copy and customize using the
Authorization Policy Manager (APM).
685
Your security implementation is likely a subset of the reference implementation. You provide the specific duty roles, data
security policies, and HCM security profiles.
The business objects registered as secure in the reference implementation are database tables and views.
Granting or revoking object entitlement to a particular user or group of users on an object instance or set of instances extends
the base Oracle Fusion Applications security reference implementation without requiring customization of the applications that
access the data.
Data Security Policies in the Security Reference Implementation

The data security policies in the reference implementation entitle the grantee (a role) to access data based on SQL predicates
in a WHERE clause.
Tip
When extending the reference implementation with additional data security policies, identify instance sets of data
representing the business objects that need to be secured, rather than a specific instance or all instances of the
business objects.
Predefined data security policies are stored in the data security policy store, managed in APM, and described in the Oracle
Fusion Applications Security Reference Manual for each offering. A data security policy for a duty role describes a permission
granted to any job role that includes that duty role.
Warning
Review but do not modify HCM data security policies in APM except as a custom implementation. Use the HCM
Manage Data Role And Security Profiles task to generate the necessary data security policies and data roles.
The reference implementation only enforces a portion of the data security policies in business intelligence that is considered
most critical to risk management without negatively affecting performance. For performance reasons it is not practical to
secure every level in every dimension. Your enterprise may have a different risk tolerance than assumed by the security
reference implementation.
HCM Security Profiles in the Security Reference Implementation

The security reference implementation includes some predefined HCM security profiles for initial usability. For example, a
predefined HCM security profile allows line managers to see the people that report to them.
The IT security manager uses HCM security profiles to define the sets of HCM data that can be accessed by the roles that are
provisioned to users
Data Roles
The security reference implementation includes no predefined data roles to ensure a fully secured initial environment.
The security reference implementation includes data role templates that you can use to generate a set of data roles with
privileges to perform predefined business functions within data dimensions such as business unit. Oracle Fusion Payables
invoicing and expense management are examples of predefined business functions. Accounts Payable Manager - US is a
data role you might generate from a predefined data role template for payables invoicing if you set up a business unit called
US.
HCM provides a mechanism for generating HCM related data roles.
Related Topics
• HCM Security Profiles: Explained
686
• HCM Data Roles: Explained
Data Security: Explained

By default, users are denied access to all data.
Data security makes data available to users by the following means.
• Policies that define grants available through provisioned roles

• Policies defined in application code
You secure data by provisioning roles that provide the necessary access. Enterprise roles provide access to data through
data security policies defined for the inherited application roles.
When setting up the enterprise with structures such as business units, data roles are automatically generated that inherit job
roles based on data role templates. Data roles also can be generated based on HCM security profiles. Data role templates
and HCM security profiles enable defining the instance sets specified in data security policies.
When you provision a job role to a user, the job role implicitly limits data access based on the data security policies of the
inherited duty roles. When you provision a data role to a user, the data role explicitly limits the data access of the inherited job
role to a dimension of data.
Data security consists of privileges conditionally granted to a role and used to control access to the data. A privilege is a
single, real world action on a single business object. A data security policy is a grant of a set of privileges to a principal on
an object or attribute group for a given condition. A grant authorizes a role, the grantee, to actions on a set of database
resources. A database resource is an object, object instance, or object instance set. An entitlement is one or more allowable
actions applied to a set of database resources.
Data is secured by the following means.
Data security feature Does what?
Data security policy Grants access to roles by means of entitlement

Role Applies data security policies with conditions to users

through role provisioning.

Data role template Defines the data roles generated based on enterprise
setup of data dimensions such as business unit.

HCM security profile Defines data security conditions on instances of object

types such as person records, positions, and document
types without requiring users to enter SQL code

Masking Hides private data on non-production database

instances

Encryption Scrambles data to prevent users without decryption

authorization from reading secured data

687
The sets of data that a user can access are defined by creating and provisioning data roles. Oracle data security integrates
with Oracle Platform Security Services (OPSS) to entitle users or roles (which are stored externally) with access to data.
Users are granted access through the privilege assigned to the roles or role hierarchy with which the user is provisioned.
Conditions are WHERE clauses that specify access within a particular dimension, such as by business unit to which the user
is authorized.
Data Security Policies

Data security policies articulate the security requirement "Who can do what on which set of data," where 'which set of data' is
an entire object or an object instance or object instance set and 'what' is the object privilege.
For example, accounts payable managers can view AP disbursements for their business unit.
Who can do what on which set of data
Accounts payable view AP disbursements for their business unit

managers

A data security policy is a statement in a natural language, such as English, that typically defines the grant by which a role
secures business objects. The grant records the following.
• Table or view
• Entitlement (actions expressed by privileges)
• Instance set (data identified by the condition)
For example, disbursement is a business object that an accounts payable manager can manage by payment function for any
employee expenses in the payment process.
Note
Some data security policies are not defined as grants but directly in applications code. The security reference
manuals for Oracle Fusion Applications offerings differentiate between data security policies that define a grant
and data security policies defined in Oracle Fusion applications code.
A business object participating in a data security policy is the database resource of the policy.
Data security policies that use job or duty roles refer to data security entitlement.
For example, the data security policy for the Accounts Payable Manager job role refers to the view action on AP
disbursements as the data security entitlement.
Important
The duty roles inherited by the job role can be moved and job roles reassembled without having to modify the
data security.
As a security guideline, data security policies based on user session context should entitle a duty role. This keeps both
function and data security policies at the duty role level, thus reducing errors.
For example, a Sales Party Management Duty can update Sales Party where the provisioned user is a member of the territory
associated with the sales account. Or the Sales Party Management Duty can update Sales Party where the provisioned user
is in the management chain of a resource who is on the sales account team with edit access. Or the Participant Interaction
Management Duty can view an Interaction where the provisioned user is a participant of the Interaction.
For example, the Disbursement Process Management Duty role includes entitlement to build documents payable into
payments. The Accounts Payable Manager job role inherits the Disbursement Process Management Duty role. Data security
688
policies for the Disbursement Process Management Duty role authorize access to data associated with business objects such
as AP disbursements within a business unit. As a result, the user provisioned with the Accounts Payable Manager job role is
authorized to view AP disbursements within their business unit.
A data security policy identifies the entitlement (the actions that can be made on logical business objects or dashboards),
the roles that can perform those actions, and the conditions that limit access. Conditions are readable WHERE clauses. The
WHERE clause is defined in the data as an instance set and this is then referenced on a grant that also records the table
name and required entitlement.
Data Roles
Data roles are implemented as job roles for a defined set of data.
A data role defines a dimension of data within which a job is performed. The data role inherits the job role that describes the
job. For example, a data role entitles a user to perform a job in a business unit.
The data role inherits abstract or job roles and is granted data security privileges. Data roles carry the function security
privileges inherited from job roles and also the data security privilege granted on database objects and table rows.
For example, an accounts payables specialist in the US Business Unit may be assigned the data role Accounts Payables
Specialist - US Business Unit. This data role inherits the job role Accounts Payables Specialist and grants access to
transactions in the US Business Unit.
A data role may be granted entitlement over a set people.
For example, a Benefits Administrator A-E is allowed to administer benefits for all people that have a surname that begins with
A-E.
Data roles are created using data role templates. You create and maintain data roles in the Authorization Policy Manager
(APM). Use the Manage Data Roles and Security Profiles task to create and maintain HCM data roles in Oracle Fusion HCM.
HCM Security Profiles

HCM security profiles are used to secure HCM data, such as people and departments. Data authorization for some roles,
such as the Manager role, is managed in HCM, even in ERP and SCM applications. You can use HCM security profiles to
generate grants for an enterprise role such as Manager. The resulting data role with its role hierarchy and grants operates in
the same way as any other data role.
For example, an HCM security profile identifies all employees in the Finance division.
Applications outside of HCM can use the HCM Data Roles UI pages to give roles access to HR people.
Database Resources and Data Security Policies: How They

Work Together
A data security policy applies a condition and allowable actions to a database resource for a role. When that role is
provisioned to a user, the user has access to data defined by the policy. In the case of the predefined security reference
implementation, this role is always a duty role. Data roles generated to inherit the job role based on data role templates limit
access to database resources in a particular dimension, such as the US business unit.
The database resource defines and instance of a data object. The data object is a table, view, or flexfield.
689
The following figure shows the database resource definition as the means by which a data security policy secures a data
object. The database resource names the data object. The data security policy grants to a role access to that database
resource based on the policy's action and condition.
Database Resources
A database resource specifies access to a table, view, or flexfield that is secured by a data security policy.
• Name providing a means of identifying the database resource

• Data object to which the database resource points
Data Security Policies

Data security policies consist of actions and conditions for accessing all, some, or a single row of a database resource.
• Condition identifying the instance set of values in the data object

• Action specifying the type of access allowed on the available values
Note
If the data security policy needs to be less restrictive than any available database resource for a data object,
define a new data security policy.
690
Actions
Actions correspond to privileges that entitle kinds of access to objects, such as view, edit, or delete. The actions allowed by a
data security policy include all or a subset of the actions that exist for the database resource.
Conditions
A condition is either a SQL predicate or an XML filter. A condition expresses the values in the data object by a search
operator or a relationship in a tree hierarchy. A SQL predicate, unlike an XML filter, is entered in a text field in the data security
user interface pages and supports more complex filtering than an XML filter, such as nesting of conditions or sub queries. An
XML filter, unlike a SQL predicate, is assembled from choices in the UI pages as an AND statement.
Tip
An XML filter can be effective in downstream processes such as business intelligence metrics. A SQL predicate
cannot be used in downstream metrics.
Securing Data Access: Points to Consider

Oracle Fusion Applications supports securing data through role-based access control (RBAC) by the following methods.
Method of securing data Reason Example
Data roles apply explicit data Appropriate for job and abstract Accounts Payable Manager
security policies on job and roles that should only access a - US data role to provide an
abstract roles subset of data, as defined by the accounts payable manager in the
data role template that generates US business unit with access to
the data role or by HCM security invoices in the US business unit.
profiles.

Data security policies Define data access for application Projects

roles and provide inheriting job and
abstract roles with implicit data
security

If a user has access to the same function through different roles that access different data sets, then the user has access to a
union of those data sets.
When a runtime session is created, Oracle Platform Security Services (OPSS) propagates only the necessary user to role
mapping based on Oracle Fusion Data Security grants. A grant can specify entitlement to the following.
• Specific rows of data (data object) identified by primary key
• Groups of data (instance set) based on a predicate that names a particular parameter
• Data objects or instance sets based on runtime user session variables
Data is identified by one of the following:
• The primary key value of the row in the table where the data is stored.
691
• A rule (SQL predicate) applied to the WHERE clause of a query against the table where the data is stored.
Grants
Oracle Fusion Data Security can be used to restrict the following.
• Rows that are returned by a given query based on the intended business operation
• Actions that are available for a given row
Grants control which data a user can access.
Note
Attribute level security using grants requires a data security policy to secure the attribute and the entitlement
check enforces that policy.
A grant logically joins a user or role and an entitlement with a static or parameterized object instance set. For example,
REGION='WEST' is a static object instance set and REGION=&GRANT_ALIAS.PARAMETER1 is a parameterized object instance set. In
the context of a specific object instance, grants specify the allowable actions on the set of accessible object instances. In the
database, grants are stored in FND_GRANTS and object instance sets are stored in FND_OBJECT_INSTANCE_SETS. Object
access can be tested using the privilege check application programming interface (API).
Securing a Business Object

A business object is a logical entity that is typically implemented as a table or view, and corresponds to a physical database
resource. The data security policies of the security reference implementation secure predefined database resources. Use the
Manage Data Security Policies task to define and register other database resources.
Data security policies identify sets of data on the registered business object and the actions that may be performed on the
business object by a role The grant can be made by data instance, instance set or at a global level..
Note
Use parameterized object instance sets whenever feasible to reduce the number of predicates the database
parses and the number of administrative intervention required as static object instances sets become obsolete. In
HCM, security profiles generate the instance sets.
Data Role Templates: Explained

You use data role templates to generate data roles. You generate data roles, and create and maintain data role templates in
the Authorization Policy Manager (APM).
Note
HCM data roles are generated using the Manage Data Roles and Security Profiles task, which uses HCM security
profiles, not data role templates, to define the data security condition.
The following attributes define a data role template.
• Template name
• Template description
• Template group ID
692
• Base roles
• Data dimension
• Data role naming rule
• Data security policies
The data role template specifies which base roles to combine with which dimension values for a set of data security policies.
The base roles are the parent job or abstract roles of the data roles.
Note
Abstract, job, and data roles are enterprise roles in Oracle Fusion Applications. Oracle Fusion Middleware
products such as Oracle Identity Manager (OIM) and Authorization Policy Manager (APM) refer to enterprise roles
as external roles. Duty roles are implemented as application roles in APM and scoped to individual Oracle Fusion
Applications.
The dimension expresses stripes of data, such as territorial or geographic information you use to partition enterprise data. For
example, business units are a type of dimension, and the values picked up for that dimension by the data role template as
it creates data roles are the business units defined for your enterprise. The data role template constrains the generated data
roles with grants of entitlement to access specific data resources with particular actions. The data role provides provisioned
users with access to a dimensional subset of the data granted by a data security policy.
An example of a dimension is a business unit. An example of a dimension value is a specific business unit defined in your
enterprise, such as US. An example of a data security policy is a grant to access a business object such as an invoice with a
view entitlement.
When you generate data roles, the template applies the values of the dimension and participant data security policies to the
group of base roles.
The template generates the data roles using a naming convention specified by the template's naming rule. The generated
data roles are stored in the Lightweight Directory Access Protocol (LDAP) store. Once a data role is generated, you provision
it to users. A user provisioned with a data role is granted permission to access the data defined by the dimension and data
security grant policies of the data role template.
For example, a data role template contains an Accounts Payable Specialist role and an Accounts Payable Manager role as its
base roles, and region, or business unit, as its dimension, with the dimension values US and UK. The naming convention is
[base-role-name]:[DIMENSION-CODE-NAME]. This data role template generates four data roles.
• Accounts Payable Specialist - US

• Accounts Payable Specialist - UK
• Accounts Payable Manager - US
• Accounts Payable Manager - UK
Making Changes To Data Role Templates

If you add a base role to an existing data role template, you can generate a new set of data roles. If the naming rule is
unchanged, existing data roles are overwritten.
If you remove a base role from a data role template and regenerate data roles, a resulting invalid role list gives you the option
to delete or disable the data roles that would be changed by that removal.
Making Changes to Dimension Values

If you add a dimension value to your enterprise that is used by a data role template, you must regenerate roles from that data
role template to create a data role for the new dimension. For example if you add a business unit to your enterprise, you must
regenerate data roles from the data role templates that include business unit as a dimension.
693
If you add or remove a dimension value from your enterprise that is used to generate data roles, regenerating the set of data
roles adds or removes the data roles for those dimension values. If your enterprise has scheduled regeneration as an Oracle
Enterprise Scheduler Services process, the changes are made automatically.
Set Activity Stream Options
Setting Activity Stream Preferences: Procedures

Activity Stream is a region on the Oracle Fusion Applications Welcome dashboard and other pages in various applications.
Users track the activities and transactions of other users in this region.
You can set options that affect all activity stream regions for all users across your site. Individual users can still override your
settings through Activity Stream preferences.
Setting Preferences
Using the activity stream preferences you can specify who can view your activity stream, for which users, services, and
spaces to track activities, and the activities to show in an activity stream task flow.
Perform the following steps to set the preferences.
1. In the Setup and Maintenance work area, search for the Set Activity Stream Options task and open it.
2. On the preferences page, click People and select one of the following options:
Tip
This setting relates only to the activities that stream from the people connections service. Such activities
include making connections, posting feedback and messages, adjusting your profile, and so on.
◦ Only Me - to display your own activities in your view of the activity stream.
◦ Me and My Connections - to display your activities and the activities of your connections in your view of the
activity stream.
◦ No Personal - to hide any user activity in your view of the activity stream, including your own.
3. Click Spaces and select one of the following options:
◦ All Spaces - to stream activities from all available spaces.
◦ My Spaces - to stream activities from the spaces of which you are a member.
◦ No Spaces - to avoid streaming any activities from spaces other than the home space.
4. Click Service Categories and select the services for which you want to track and display the activities.
Tip
If you select No Spaces under Spaces (in the earlier step), the services do not publish any activity to your
view of the activity stream, even if you select the services here.
694
5. Click Privacy and select one of the following options:
◦ Everyone - all users, whether they are signed in or not, can see your view of the activity stream.
◦ Authenticated Users - all users who are signed in can see your view of the activity stream.
◦ My Connections - everyone connected to you can see your view of the activity stream.
◦ Myself - only you can see your view of the activity stream.
6. Click Comments and Likes and select the required options.
7. Click Save.
Manage Menu Customizations
Menu Customization: Explained

You use the Manage Menu Customizations task to customize the navigator and home page menus. This task is available
from the Setup and Maintenance work area, which is accessible from the Administration menu in the Oracle Fusion
Applications global area. Select either Customize - Navigator or Customize - Homepage to proceed with the
customization activity.
Note
To perform menu customization at run time, it is important that you have the required privileges.
You customize the menus at the site level and your changes affect all users (or all users of a tenant if in a multi-tenant
environment).
Tip
If you are making minor changes, such as adding or editing one or two nodes, then you can hide the changes
until you have completed your customizations. However, if you are making more than minor changes, such as
rearranging several nodes, you might want to instead create a sandbox before customizing menus.
Navigator Menu Configuration

The navigator menu is the global menu that is accessible from the Oracle Fusion Applications global area. It allows users to
navigate directly to the pages inside Oracle Fusion Applications as well as to outside web pages. The menu is composed of
links (items) that are organized in a hierarchy of groups.
You can customize the navigator menu to address needs that are specific to your organization. For example, you might want
to add specialized groupings for cross-functional teams or add links to web pages or external applications. You can add
groups and links to the navigator menu, as well as hide and show them.
The Manage Menu Customizations task displays the menu groups as expandable nodes, with which you can traverse the
menu hierarchy.
Note
Not all Oracle Fusion Applications pages appear in the navigator menu, because some pages are accessible from
a work area or from other links in the global area such as the Home link.
695
The following table lists the Navigator menu customization tasks that you can perform at run time as well as the tasks that you
cannot perform.
Permitted Tasks Restricted Tasks
• Add and delete custom groups. • You cannot add menu items (links) as top-level
nodes. You can add nodes to only the groups in
• Edit any group. the top level and subgroups.
• Add and delete custom items. • You cannot delete nodes that are delivered with
the product. Instead, you can hide them.
• Edit any item.
• You cannot move nodes. Instead, you must
• Specify navigation for an item: duplicate the node and hide the original node.
◦ Specify navigation to a UI Shell page in an

Oracle Fusion application.
◦ Specify navigation to an external web page.
• Hide or show groups and items.
Home Page Menu Configuration

The home page menu is the set of tabs that are displayed in the Oracle Fusion Applications global area. The home page
menu displays tabs for all the items in the menu for which the end user has access privileges. You can add tabs to the home
page menu, as well as hide and show them.
The following table lists the Home page menu customization tasks that you can perform at run time as well as the tasks that
you cannot perform.
Permitted Tasks Restricted Tasks
• Add and delete custom items. • You cannot add menu items (links) as sub-nodes.
All nodes are top-level nodes.
• Edit any item.
• You cannot delete nodes that are delivered with
• Specify navigation to a UI Shell page in an Oracle the product. Instead, you can hide them.
Fusion application.
• You cannot move nodes. Instead, you must
• Hide or show items. duplicate the node and hide the original node.
Related Topics
• Managing Customizations Using Sandboxes: Explained
696
Adding Navigator Menu Group: Points to Consider

You arrange the navigator menu by building a hierarchy of nested groups.
Use the View menu to expand or collapse a group of nodes. You can also right-click a node and access similar actions to
facilitate tree navigation.
Adding Groups
To add a group, you can insert a group above or below a peer group or insert a child group. You edit a group by defining
a label and specifying whether the group should be rendered. You typically hide the group until all changes have been
completed.
Adding Menu Items: Points to Consider

The home page menu items are URL links to home pages in Oracle Fusion applications. The Navigator menu items can either
be links to UI Shell pages or links to external applications and web sites.
In the menu hierarchy, the home page menu items are always top-level items. Whereas, you can add Navigator menu items
to top-level groups and to their subgroups but you cannot add navigator menu items as top-level nodes.
Adding a Home Page Menu Item

To add a home page menu item, navigate to the place where you want the item to appear and insert it above or below the
existing item. You can also duplicate an existing menu item and position it at the required location. You must provide a label
for the menu and link the menu item to a UI Shell page.
Adding a Navigator Menu Item

To add a Navigator menu item, you navigate to the item's group and insert the item above or below another item.
You can also duplicate an existing item. You must provide a label for the menu and either link the menu item to a UI Shell
page or link it to an external web site or application.
You can link a Navigator menu item to the following:
• A UI Shell page in an Oracle Fusion application.

• A dynamic URL of a page outside of Oracle Fusion Applications where the host, port, or context root might change.
• A Static URL of a page outside of Oracle Fusion Applications where the host, port, or context root does not change.
• A Secure Token URL of a partner application, to which secure tokens are added for enhanced security.
Linking to a UI Shell Page

If the new item points to a UI Shell page in an application, then you must provide the name of the web application and the
view ID of the target page. The web application name and view ID can be obtained from an existing menu item that links to
the same UI Shell page.
In a non-Cloud implementation, you also can obtain the web application name from the context root for the application,
and you can obtain the view ID from the id attribute for the page's <view> tag in the product's public_html/WEB-INF/adfc-
config.xmlfile.
If you want secure access to the target UI Shell page from the menu item, then you must provide the name of the secured
resource and the name of the policy store's application stripe. When an end user clicks the link, the Oracle Fusion
Applications checks the secured resource and the Lightweight Directory Access Protocol (LDAP) policy store to determine
whether the user has the privilege to view the page.
If there is another menu item that points to the same page, then you can get the secured resource name and
application stripe from that item. In a non-Cloud implementation, you also can obtain the application stripe from the
697
jps.policystore.applicationid parameter in the application's weblogic-application.xml file. Examples of application stripes are crm,
fscm, and hcm.
For non-Cloud applications, you can determine the secured resource name by obtaining the name of the web page's page
definition file. By default, the page definition files are located in the view.PageDefs package in the Application Sources
directory of the view project. If the corresponding JavaServer Faces (JSF) page is saved to a directory other than the default
(public_html), or to a subdirectory of the default, then the page definition will also be saved to a package of the same name.
An example of a secured resource name is oracle.apps.view.pageDefs.CaseList_Form_Attach_ UIShellPagePageDef.
A UI Shell page might take parameters and display or act differently based on the parameters that are passed in. For
example, if accessing a page from one group in the menu hierarchy, the parameter might be set to status=Open and if
accessing the page from a different group, the parameter might be set to status=Closed. If the page takes parameters, you can
use the Page Parameters List text box to provide a semicolon-delimited string of name-value pairs, such as org=m1;context=s1.
You can use expression language (EL) to specify the parameters. If the EL evaluates to an Object, the toString value of that
Object is passed as the value of the parameter.
Linking to the Dynamic URL of an External Web Site or Application

Linking a menu item to a dynamic URL is beneficial in cases where the host, port, or context root to which you point
frequently changes. Instead of updating the link to each application, you can update the details of the web application in the
topology registration, and that change affects all menu items that contain dynamic links pointing to that web application. For
example, you would need a dynamic URL to link to a test version of an application and you will need to change the host and
port when you move the application from a test environment to a production environment.
To link to a page outside of Oracle Fusion Applications where the host, port, or context root might change, you must first
register the web application in the topology using the Register Enterprise Applications task.
While creating a new menu item on the Create Item Node dialog box, select the Dynamic URL option and provide the details
of the web application as per the following example.
When the complete URL to be linked is: http://example:9011/myApp/faces/Page1,
• The name of the web application added to topology would be: myApp (the value that would eventually appear in the
Web Application list) and the protocol host, port, and context root values of the URL would be: http://example:9011/
myApp
• The value to be provided in the Destination for Web Application field would be: /faces/Page1
Once the menu item is linked to the dynamic URL, the target page appears in a new browser window or tab when you click
the menu item.
Linking to a Static URL of an External Web Site or Application

This option is used when you link a menu item to a page outside Oracle Fusion Applications where the host, port, or context
root remains constant. For example, you can use a static URL to link to http://www.oracle.com.
Linking to a Secure Token URL of a Web Page or Application

This option is used when you link a menu item to a secure token URL of a partner application outside Oracle Fusion
Applications.
When you provide the secure token on the UI, your application code validates it and uses the secure token to authenticate
web services within the end user context. When this mode of customized access is used, a partner can directly perform an
action or display information to the specific user without any additional authentication.
698
Note
• A HTTPS protocol is required to access the application.
• The secure token expires if the user session is inactive. Refresh the page to regenerate the tokens.
Hiding or Displaying Menu Nodes: Points to Consider

While you are creating or working with a menu group or a menu item, you might want to prevent end users from accessing
the node. You can hide the menu group or menu item while you are working with it, and then show the node when you have
completed the task.
Working with Nodes

The Manage Menu Customizations page shows all nodes. The Rendered check box is selected by default for all nodes that
are added and are visible.
To hide a node, clear the Rendered check box. You can edit the node anytime to either display or hide it.
If you want a menu group or a menu item to appear only if certain conditions are met, you can use an expression language
(EL) command to make the node to appear. For example, #{securityContext.userInRole['ADMIN']}.
A node that appears in italics either contains an EL command or the Rendered check box beside it was cleared, and
therefore is hidden from end users.
Tip
For major changes that need to be tested and approved, you might want to use the sandbox manager instead of
hiding and showing nodes.
Related Topics
• Managing Customizations Using Sandboxes: Explained
Design Time Menu Customizations: Highlights

The menu customization feature provides several options to add, modify, and organize the Navigator and home page menus
during design time. You must have developer rights to perform these customizations.
Note
Design time menu customizations are not applicable to Oracle Cloud implementations.
An overview of customizing the Navigator menu and home page is provided in the Oracle Fusion Applications Extensibility
Guide.
Customizations
• Use Oracle JDeveloper to customize the Navigator and home page menus at design time.
See: Customizing Menus
• Define translations for your customizations in the locales you support.
699
See: Translating Menu Customizations

• Customize the page template to display the Navigator menu groups as separate menus, each of them displaying
their list of menu items. Refer to the Oracle Fusion Applications Developer's Guide.
See: Rendering the Navigator Menu as Dropdown Buttons
Troubleshooting Navigator Menu: Highlights

If the Navigator menu does not display customizations as expected, use the following troubleshooting tips to verify the
changes.
Issues and Resolutions

• If an expected menu item does not appear in the Navigator menu, verify whether the menu item has been hidden
from view.
• If a custom menu item was added and the browser does not display the page indicated by the URL, open the
Manage Menu Customizations task and verify whether the web application name is the same as the context root for
the application, and that the view ID is the id attribute for the page's <view> tag in the product's public_html/WEB-
INF/adfc-config.xml file. The URL should not contain the .JSPX suffix.
• If you see a "webApp value not define" error message when you choose an item in the Navigator menu, verify
whether the application is in the topology tables. Refer to the Oracle Fusion Applications Administrator's Guide.
See: Viewing the Routing Topology of an Oracle Fusion Applications Instance, Product Family, or Product
Manage Audit Policies
Managing Audit Policies: Explained

Auditing is used to monitor user activity and all configuration, security, and data changes that have been made to an
application. Auditing involves recording and retrieving information pertaining to the creation, modification, and removal
of business objects. All actions performed on the business objects and the modified values are also recorded. The audit
information is stored without any intervention of the user or any explicit user action.
Use audit policies to select specific business objects and attributes to be audited. The decision to create policies usually
depends on the type of information to be audited and to the level of detail that is required to be reported.
Enabling Audit Functionality

To enable audit, ensure that you have administrative privileges. For Oracle Fusion Applications, you must configure the
business objects and select the attributes before enabling audit. If you enable audit without configuring the business objects,
auditing remains inactive. By default, auditing is disabled for all applications.
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 predefined and contain the metadata and events to be audited. For more information, refer to
the Oracle Fusion Middleware documentation and also the Oracle Enterprise Repository for Oracle Fusion Applications at
http://fusionappsoer.oracle.com.
If you do not want an application to be audited, you can stop the audit process by setting the Audit Level option to None.
While viewing the audit report for that application, you can specify the period during which auditing remained enabled.
700
Configuring Audit Business Object Attributes: Points to

Consider
Audit allows you to track the change history of particular attributes of a business object. However, those objects and their
attributes must be selected for audit and auditing must be enabled for that application. Your configuration settings determine
which attributes to audit for a given object, and when the audit starts and ends. Auditing takes into account all the create or
insert, update, and delete operations performed on an object and its attributes.
To configure audit business object attributes, navigate to the Manage Audit Policies page in the Setup and Maintenance work
area.
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 object that you want to audit. Selecting a business object also displays its
attributes that are enabled for auditing.
Selecting Attributes
For each selected business object to be audited, select the corresponding attributes to include in the audit. All attributes that
belong to that object are by default selected for audit and appear on the user interface. However, you can add or remove
attributes from the list. When you remove an attribute from the list, you stop auditing it even when the parent object is
selected for audit. So, if you want an attribute to be audited, you must add it to the list.
Note
If the object selected in an audit hierarchy is also a part of several other audit hierarchies, the attribute
configuration for that object is applicable to all the hierarchies in that application.
Starting and Stopping Audit

The business object is ready for audit after you select its attributes and save the configuration changes. However, to start
auditing, the audit level for Oracle Fusion Applications must be set to Auditing on the Manage Audit Policies page.
To stop auditing an object, you can deselect the entire object and save the configuration. As a result, all its selected attributes
are automatically deselected and are not audited. To continue to audit the business object with select attributes, deselect
those attributes that are not to be audited.
When end-users view the audit history for an application, they can specify the period for which they want the results.
Therefore, it is important to note when you start and stop auditing an application. For example, today if end-users intend to
view the audit history of an object for the previous week, but auditing for that object was stopped last month, they would not
get any audit results for that week because during the entire month that object was not audited. Even if you enable audit for
that object today, end-users cannot get the wanted results because audit data until today is not available.
Configuring Audit: Highlights

You can set up auditing for Oracle Fusion Applications using the Manage Audit Policies page in the Setup and Maintenance
work area of Oracle Fusion Applications.
To set up auditing for Oracle Fusion Middleware products, you must select the level of auditing that maps to a predefined set
of metadata and events that have to be audited. Information on configuring audit for Oracle Fusion Middleware products is
provided in Oracle Fusion Middleware guides.
You can also create a configuration file and deploy it to audit a specific Oracle Fusion Middleware product. The configuration
details for Oracle Fusion Middleware products are available in the form of audit-specific assets that can be used to create the
701
configuration file (config.xml). For more information, see the Oracle Enterprise Repository for Oracle Fusion Applications at
http://fusionappsoer.oracle.com, and search with Audit as the Asset Type to get the list of audit-specific assets.
Oracle Fusion Middleware Products

• Configure business objects to enable auditing in Oracle Fusion Middleware products. Refer to the Oracle Fusion
Middleware Security and Administrator's Guide for Web Services.
See: Auditing Web Services
Oracle Fusion Security Products

• Configure business objects to enable auditing in Oracle Fusion security products. Refer to Oracle Fusion Middleware
Application Security Guide.
See: Oracle Fusion Middleware Audit Framework Reference
Related Topics
Audit Impersonation: Explained

Users can temporarily designate other users to impersonate their profiles and perform application tasks on their behalf. By
default, all impersonations are audited.
In the global area, click your user name and from the Settings and Actions menu, select Preferences.
At run time, audit setup tracks and stores information on all attributes, whether auditing is enabled for an attribute or not. As
a result, impersonation auditing is also active even when auditing is disabled for an application. The audit history captures the
impersonator information in addition to the actual user information. Therefore, while viewing audit history, users can retrieve
the audited information, filtered by an impersonated user.
To assign or modify impersonations, in the Tasks pane on the Preferences page, click Proxies. You can search for the users
who can be impersonated and switch the access to that user.
Related Topics
• Proxies: Explained
Manage Oracle Social Network Objects
Managing Oracle Social Network Objects: Explained

Use the Manage Oracle Social Network Objects task for managing the Oracle Social Network Objects. The integration
of Oracle Social Network with applications and business processes brings key attributes from the applications to share,
socialize, and update information. This helps in making better business decisions based on additional information that you
obtain and analyze within your social network environment.
Use the Manage Oracle Social Network Objects page to set up and define:
• The business objects and attributes to enable
702
• The enablement method for social network integration with Oracle Applications Cloud
You can access the Manage Oracle Social Network Objects page by starting in the Setup and Maintenance Overview
page and searching for the task named Manage Oracle Social Network Objects.
Use Oracle Social Network to:
• Discuss projects and plans in public forums

• Maintain:
◦ Membership groups
◦ Activity feeds of the people you choose

• Facilitate:
◦ One-on-one Conversations
◦ Reviews
◦ Document sharing
Note
Oracle Social Network is currently available in Cloud implementations only.
An important aspect of managing Oracle Social Network objects is enabling business objects for integration.
Enabling Business Objects for Integration

A business object can't be shared within social network until a functional administrator or implementor:
• Accesses the Manage Oracle Social Network Objects page in Oracle Applications Cloud
• Enables the business object for social network integration
Update Translations: Explained

The Update Translations process sends attribute labels and business object names to Oracle Social Network for use in the
user interface.
In social network, the attribute or business object labels appear in the language of your locale. If you change the locale in
social network, then the attribute or business object labels appear in the updated language. However, the data appears
in the language in which it was originally sent to social network. If you have previously sent an instance of the business
object to social network, then the instance data isn't updated. Clicking the Update Translations button on the Manage
Oracle Social Network Objects page sends translations for business objects with the enablement option as Manual or
Automatic.
Synchronize Business Objects: Explained

Use the Synchronize button on the Manage Oracle Social Network Objects page to synchronize business objects.
This re-sends the definitions of business objects having the enablement option as Manual or Automatic to Oracle Social
Network.
703
Use the Synchronize button at the:
• Business Objects table level: To re-send the definitions of a selected business object to social network. This
button is enabled only when you select a row for a business object with the enablement option as Manual or
Automatic.
• Manage Oracle Social Network Objects page level: To re-send the definitions of all business objects with the
enablement option as Manual or Automatic to social network.
Note
If you had modified any business object enabled for social network and not saved your changes, then on clicking
the Synchronize button, a warning message appears. This message informs you that you have not saved your
changes, and you can select one of the following options:
• Save and Synchronize: To save the modified business objects, and synchronize the unmodified business
objects.
• Synchronize: To ignore any unsaved business objects, and only synchronize the unmodified business objects.
• Cancel: To cancel the synchronization task.
FAQs for Manage Oracle Social Network Objects

What happens if I update translations?
When you update translations, you send translations for business objects with the enablement option as Manual or
Automatic to Oracle Social Network.
On updating translations, you also:
• Synchronize the newly translated text from Oracle Applications Cloud so that it can be used within social network.
This means you can:
◦ Install and enable a new language.
◦ Take a language patch at any time.

• Send attribute labels and business object names to social network for use in its user interface.
How can I update translations?

Use the Update Translations button on the Manage Oracle Social Network Objects page for subsequent updates to
labels and attributes.
Use the Update Translations button at the:
• Business Objects table level: To send translations for a selected business object to Oracle Social Network.
This button is enabled only when you select a row for a business object with the enablement option as Manual or
Automatic.
• Manage Oracle Social Network Objects page level: To send translations for all business objects with the
enablement option as Manual or Automatic to social network.
704
Note
When you save the enablement of a business object to social network, it sends the translations as well. Hence,
you need not click the Update Translations button after saving the enablement.
When do I update translations?

Run the Update Translations process only after you install a new language pack of Oracle Applications Cloud.
Updating translations synchronizes the newly translated text to Oracle Social Network for integration with Oracle Applications
Cloud.
Note
When you save the enablement of a business object to social network, it sends the translations as well. Hence,
you need not click the Update Translations button after saving the enablement.
What happens if I synchronize business objects?

When you synchronize business objects, you re-send the definitions of business objects having the enablement option as
Manual or Automatic to Oracle Social Network.
When do I synchronize business objects?

Run the Synchronize process after you use customization sets to import the setup from the Manage Oracle Social
Network Objects page in another environment.
You can also run the process any time you want to synchronize the settings of business objects with Oracle Social Network
without making any changes in the Manage Oracle Social Network objects page.
Related Topics
• Using Customization Migration to Move Customizations: Points to Consider
Manage Applications Core Common Reference

Objects
Define Applications Core Configuration: Overview

The Define Applications Core Configurations task list contains the Oracle Middleware Extensions for Applications (Applications
Core) tasks that support implementation of common functionality such as lookups, profile options, document sequences, and
so on.
Use this task list to manage configuration objects that are defined centrally and shared across applications, in addition to
those that are classified under the Maintain Common Reference Objects task list. You can search for this task list in the Setup
and Maintenance work area.
705
Manage Applications Core Messages

Messages: Highlights
The message dictionary contains messages that tell users about business rule errors, such as missing or incorrect data,
and how to resolve them, to warn users about the consequences of intended actions, and provide information in log files.
These messages are defined for specific applications and modules, but a few are common messages that can be used in any
application. All applications also use messages stored outside of the message dictionary.
The message dictionary is described in the Oracle Fusion Applications Developer's Guide.
Managing Messages
• Use the Manage Messages page to create and edit custom messages in the message dictionary, as well as edit
predefined messages. Do not delete predefined messages unless you are sure that they are not used anywhere.
Refer to the Oracle Fusion Applications Developer's Guide.
See: Introduction to Message Dictionary Messages
• Messages outside of the message dictionary, such as confirmations and field validations, are managed either in the
Oracle Application Development Framework or through message resource bundles used for translation.
Related Topics
• Creating and Editing Messages: Highlights
• Common Messages: Points to Consider

Message Properties
706

See: About Tokens
Related Topics
Common Messages: Points to Consider

Common messages, which have message names that begin with FND_CMN and message numbers between 0 and 999, are
used throughout Oracle Fusion Applications. Each common message can appear in multiple places in any product family. For
example, the FND_CMN_NEW_SRCH message can be used for any search to indicate that no results were found. Common
messages that are of type error or warning are part of the message dictionary.
Editing Common Messages

Because a common message can be used in any application, consider the ramifications if you edit any aspect of the
message, including incident and logging settings. Changes would be reflected in all instances where the message is used.
For example, if you change the message text, make sure that the text would make sense to all users across Oracle Fusion
Applications who might see it.
Creating Common Messages

You can create custom common messages for use in multiple places within a single product. Do not begin the message
name with FND_CMN, but use another suitable convention. The message number should be within the range that is
designated for the product.
Manage Applications Core Standard Lookups

Lookups: Explained
Lookups are lists of values in applications. You define 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 defined in the REQUIRED_INDICATOR lookup type.
In another example, a lookup type for marital status has lookup codes for users to specify married, single, or available legal
partnerships.
Lookup Type Lookup Code Meaning Tag
MAR_STATUS M Married
707
Lookup Type Lookup Code Meaning Tag

S Single

R Registered Partner +NL

DP Domestic Partner -FR, AU

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.
When managing lookups, you need to understand the following.
• Using lookups in applications

• Customization levels
• Accessing lookups
• Enabling lookups
• The three kinds of lookups: standard, common, and set enabled
Using Lookups in Applications

Use lookups to provide validation or a list of values for a user input field in a user interface.
An example of a lookup used for validation is a flexfield segment using a table-validated value set with values from a lookup
type. An example of a lookup in a list of values is a profile option's available values from which users select one to set the
profile option. Invoice Approval Status gives the option of including payables invoices of different approval statuses in a
report. The lookup code values include All so that users can report by all statuses: Approved, Resubmitted for approval,
Pending or rejected, and Rejected.
Customization Level
The customization 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 customization 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 meanings of
predefined lookup codes cannot be modified. Some predefined lookup codes can be changed during implementation or later,
as needed.
The customization levels are user, extensible, and system. The following table shows which lookup management tasks are
allowed at each customization level.
Allowed Task User Extensible System
Deleting a lookup type Yes No No

Inserting new codes Yes Yes No

708
Allowed Task User Extensible System
Updating start date, end Yes Yes, only if the code is No

date, and enabled fields not predefined data

Deleting codes Yes Yes, only if the code is No

not predefined data

Updating tags Yes No No

Updating module Yes No No

Predefined data means LAST_UPDATED_BY = SEED_DATA_FROM_APPLICATION.

If a product depends on a lookup, the customization level should be system or extensible to prevent deletion.
Once the customization level is set for a lookup type, it cannot be modified. The customization level for lookup types created
using the Define Lookups page is by default set at the User level.
Standard, Common, and Set-Enabled Lookups

The available kinds of lookups are as follows.
Lookup Description
Standard Lists the available codes and translated meanings

Set enabled Additionally associates a reference data set with the

lookup codes

Common Legacy lookups

Standard lookups are the simplest form of lookup types consisting only of codes and their translated meaning. They differ
from common lookups only in being defined in the standard lookup view.
Common lookups exist for reasons of backward compatibility and differ from standard lookups only in being defined in the
common lookup view.
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 identifies a reference data set in which the lookup code is present.
Accessing Lookups
Standard, set-enabled, and common lookups are defined in the Standard, Set-enabled, and Common views, respectively.
Applications development may define lookups in an application view to restrict the UI pages where they may appear.
709
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 specific task such as Manage Purchasing
Lookups.
Enabling Lookups
A lookup type is reusable for attributes stored in multiple tables.
Enable lookups based on the following.
• Selecting an Enabled check box

• Specifying an enabled start date, end date, or both
• Specifying a reference data setdeterminant
If you make changes to a lookup, users must sign out and back in before the changes take effect. When defining a list of
values for display rather than validation, limit the number of enabled lookup codes to a usable length.
For more information on the predefined lookups and lookup codes, see assets with the Lookup type in the Oracle Enterprise
Translating Lookups
You can translate the lookups that you defined 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 allowed
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.
Restriction
You can add the translation for only as many languages as are permitted by the administrator. The functionality to
limit the number of languages displayed on the dialog box is controlled through the Translation Editor Languages
profile option. It can be set at the SITE or USER level. If nothing is specified, all active languages are displayed.
Related Topics
Managing a Standard Lookup: Example

Creating a new standard lookup involves creating or selecting a lookup type to which the lookup code belongs, and
determining appropriate values for the lookup codes and their meanings.
Note
You can only create or edit the lookup codes for a particular lookup type if its customization level supports it.
Creating a Lookup Type Called COLORS

Your enterprise needs a list of values for status to be used on various objects such as processes or users. The lookups are
colors, so the lookup type you create is COLORS.
Lookup type parameters Value
Lookup type name COLORS
710
Lookup type parameters Value

Meaning Status

Description Status by color

Module Oracle Middleware Extensions for Applications

The lookup codes you define for the COLORS lookup type are, BLUE, RED, GREEN, and YELLOW.
Lookup Code Meaning Enabled Display Sequence
BLUE Urgent No 4

RED Stop Yes 1

GREEN Go Yes 3

YELLOW Caution Yes 2

Understanding the Resulting Data Entry List of Values

Users need to respond to a process question by indicating whether to stop it, use caution, go ahead, or complete it urgently.
The list of values for the COLORS lookup type includes the meanings for the enabled codes.
Displayed Value Hidden ID
Stop RED

Caution YELLOW

Go GREEN

Analysis
The BLUE lookup code was not enabled and does not appear in the list of values. The display sequence of values in the list
of values is alphabetical unless you enter a number manually to determine the order of appearance. Number 1 indicates the
value listed first in the list of values.
711
Note
Only lookups that are enabled and active, meaning between start and end dates, are visible.
Understanding the Transaction Table

When users enter one of the values from the list of values for the lookup type COLORS, the transaction table records the
lookup code. In this example, the code is stored in the Status column
Transaction number User name Status
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 does
not affect transaction records in which that code is stored. Data querying and reporting have access to disabled lookup
codes in transaction tables.
Managing Set-Enabled Lookups: Examples

Creating a new set-enabled lookup is similar to creating a standard lookup with the addition of specifying a reference data
setdeterminant for the lookup codes.
Note
You can only create or edit the lookup codes for a particular lookup type if its customization level supports it.
The reference data set for a set-enabled lookup code is part of its foreign key. This is unlike other set-enabled
entities.
Selecting a Reference Group for a Set-Enabled Lookup Type

By specifying a reference group for a set-enabled lookup type you indicate which reference data set assignments are
available for its lookup codes. For example a COLORS lookup type might be set enabled for a Countries reference group that
includes the US and EU reference data set assignments.
Selecting a Reference Data Set for a Set-Enabled Lookup

The reference data set determines which lookup code is included in the list of values. If a COLORS lookup type contains a
RED, YELLOW, ORANGE, and GREEN lookup code, you can enable one RED lookup as coming from the US reference data
set and another RED lookup as coming from the EU reference data set with divergent meanings.
Reference Data Set Lookup Code Lookup Meaning
US RED Red

712
US YELLOW Yellow

US GREEN Green

EU RED Rouge

EU ORANGE Orange

In addition to divergent meanings for lookup codes based on associated reference data set, 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 this example.
In another example, a lookup type called HOLD_REASON provides a list of reasons for applying a hold to a contract renewal.
Reference data sets determine which codes are included in the hold reason list of values.
US SEC SEC Compliance Review

US DIR Needs Director's Approval

US VP Needs Vice President's Approval

CHINA CSRC Pending China Securities

Regulatory Commission Review

CHINA PR Needs President's Approval

COMMON REQUESTED Customer Request

Using the Manage Set Assignments task, you have defined assignments that designate the China business unit to refer to the
CHINA and the US business unit to refer to the US and all business units to refer to the COMMON set. When end users place
a contract hold in the US business unit, only the three reason codes in US_SET are available. When placing a contract hold in
the China business, only the two codes in China_SET are available.
713
FAQs for Manage Applications Core Standard Lookups

How can I edit lookups?
On the Define Lookups page, you can edit the existing lookup codes of a lookup type or add new lookup codes. To access
the page, navigate to the Setup and Maintenance work area and search for the Define Lookup task.
You may not be able to edit a lookup if its customization level doesn't support editing.
Why can't I see my lookup types?

Lookups are listed by lookup type. Typically lookup types are managed using tasks that handle a group of related lookups,
such as Manage Geography Lookups. Each task gives you access only to certain lookup types. The generic tasks provide
access to all lookups types of a kind, such as all common lookups using the Manage Common Lookups task.
If existing lookups are not available to the tasks of the Define Lookups activity, they may be validated for use in a lookup view
that is not central to all applications or whose owning application has not been specified in a lookup view.
Lookups can only be managed in the Define Lookups tasks if the lookup's view application is the standard lookups view,
common lookups view, or set-enabled lookups view. Lookups defined in an application view can only be managed by
following instructions provided by the owning application.
Note
A lookup type and its codes can only be defined in one lookup view.
What's the difference between a lookup type and a value set?

A lookup type consists of lookup codes that are the values in a static list of values. Lookup code validation is a one to one
match.
A table-validated value set can consist of values that are validated through a SQL statement, which allows the list of values to
be dynamic.
Tip
A table validated value set can be defined based on any table, including the lookups table. This allows a lookup
type to be made into a table-validated value set that can be used in flexfields.
Area of Difference Lookup Type Value Set
List of values Static Dynamic if Table validation type

Validation of values One to one match of meaning to By format or inclusion in a table

code included in a lookup view,
or through the determinant of a
reference data set

Format type of values char varchar2, number, and so on

714
Area of Difference Lookup Type Value Set
Length of value Text string up to 30 characters Any type of variable length from 1
to 4000

Duplication of values Never. Values are unique. Duplicate values allowed

Management Managed by both administrators Maintained by administrators,

and end-users, except system except some product flexfield
lookups or predefined lookups at codes, such as GL for Oracle
the system customization level, Fusion General Ledger, which are
which cannot be modified. maintained by end users

A lookup type cannot make use of a value from a value set.

Value sets can make use of standard, common, or set-enabled lookups.
Both lookup types and value sets are used to create lists of values from which users select values.
What's a lookup tag used for?

Tags on lookup codes allow you to add a label to your lookup codes.
Lookup tags are unvalidated and uninterpreted by lookups. A tag can be used to categorize lookups based on facilitating
searches or guiding how a lookup should be used.
Document what the tag on a lookup represents and how to use it.
How can I search for a specific lookup code?

Use the Query By Example functionality to sort through hundreds of lookup codes for a lookup type, and display a specific
lookup code. Enter the first few characters of the lookup code value in any of the relevant fields to filter the records.
Note
The search functionality is case sensitive.
Manage Applications Core Profile Options

Profile Options: Explained
Profile options manage configuration data centrally and influence the behavior of applications. Profile options serve as
permanent user preferences and application configuration parameters. You configure profile options with settings for specific
contexts or groups of users. Users customize how their user interfaces look and behave by changing the values of available
profile options.
Profile options store the following kinds of information.
715
Type of Information Profile Option Example
User preferences Settings to provide access to social networking features

Installation information Setting to identify the location of a portal

Configuration choices Settings to change user interface skins and behaviors

Processing options Settings to affect how much information to log either for
an entire site or a specific user

You can add and configure new profile options in addition to configuring predefined profile options that are implemented as
updateable.
Profile Option Definition and Configuration

Application developers add new profile options and configure ones that are not to be updated by other users. Application
administrators and implementation consultants configure profile options with profile option values that are implemented as
updatable.
Profile option definitions consist of the following.
• Profile option name

• Application and module in the application taxonomy
• Profile option values
• Profile options categories
• Profile option levels
• Profile option level hierarchy
Profile options can appear on any user interface page without indication that a profile option is what is being set.
Profile Option Values

Some profile options have predefined profile option values.
The Manage Profile Option Values task flow allows an administrator to set updatable profile option values at the available
levels, including the user level. You can access the Manage Profile Option Values task starting in the Setup and Maintenance
Overview page and searching for profile option tasks.
You can set profile option values at different levels: site, product, and user. The following table provides examples.
Profile Option Level Value of the Profile Profile Option Value Effect
Option Level
User Manager1 UK pound sterling Access to site and all

products shows UK
pounds sterling in effect

716
Profile Option Level Value of the Profile Profile Option Value Effect
Option Level
User Manager2 US dollar Access to site and all

products shows US
dollars in effect

Product Financials for EMEA Euro Unless superseded by a

user level value, Euros in
effect for Financials for
EMEA applications

Site Site UK pound sterling UK pounds sterling in

effect for all other users
and products

Context such as user session or accessed product determines which profile option value is associated with the profile option
name. In the example, if manager1 does not set a profile option value for this profile option, access to Financials for EMEA
shows currency in Euros; and access to other products shows currency in UK pounds sterling.
Profile Option Categories

Categories group profile options based on their functional area. Profile option categories facilitate searching and defining data
security.
For example, in Oracle Fusion Receivables, the Transactions profile option category groups profile options related to setting
how Receivables transactions are to be processed, such as Require Adjustment Reason.
A profile option can be in more than one category.
Profile Option Hierarchies and Levels

Application developers specify at which hierarchy level a profile option is enabled. The predefined profile option hierarchy
levels are site, product, and user.
The hierarchy levels specified in the profile option definition determine the context in which a profile option value may be set. If
the profile option value at a particular level is updatable, an administrator can update the profile option value for that context.
Note
Profile options should only be enabled for context levels that are appropriate for that profile option. For example,
a profile option indicating a global configuration setting should not be enabled at the user level, if users cannot
choose a different value for that setting.
For security, one level in the hierarchy is designated as a user level. A profile option may be enabled at any or all hierarchy
levels. When enabled at all levels, the predefined ordering of profile option hierarchy levels gives precedence to the values that
are set at the user level over values set at the product and site levels, and precedence to values set at the product level to
values set at the site level. If there is no value for the current user, then the product value applies. If there is no value for the
user or product, then the site value applies.
The table shows the predefined profile option hierarchy and ordering.
717
Hierarchy Level Priority When Multiple Effect on Applications Example

Levels Set
Site Lowest Affect all applications for Currency for the site is
a given implementation set to Euros.

Product Supersedes Site Affect all applications of Currency for the

a product family such as Financials products set
Financials to UK pound sterling.

User Highest, supersedes Affect only the Currency for the user of
Product experience of the current Financials applications
user set to US dollars.

You can configure updatable values for profile options at one or more levels depending on which levels are enabled in
the profile option definition. When a profile is set at more than one level, higher levels of specificity override lower levels of
specificity.
In the example, if the currency setting for the site is UK pounds sterling, but the Financials division works in the Netherlands
using the Euro, a manager in the US can override that product level setting at the user level to use US dollars when accessing
Financials applications.
In another example, if a profile option called Printer is set only at the site and product levels. When a user logs on, the Printer
profile option assumes the value set at the product level, since it is the highest level setting for the profile.
Tip
Set site-level profile option values before specifying values at any other level. The profile option values specified at
the site-level work as defaults until profile option values are specified at the other levels.
For more information on the predefined profile options, see assets with the Profile Option type in the Oracle Enterprise
Related Topics
Planning Profile Options: Points to Consider

Plan profile options before defining and configuring them.
The following aspects assist you in better planning how to manage profile options.
• Profile option tasks

• Before creating a profile option
• Profile options data model
Profile Option Tasks

Users may be able to set their own profile options, depending on settings in the profile option definition. However, not all
profile options are visible to end users, and some profile options, while visible, may not be updated by end users.
The following table lists tasks and considerations relevant to planning profile options.
718
Tasks Role Considerations
Planning, creating, and editing a Applications developer Since profile options are for
new profile option permanent settings, do not use
profiles options to cache temporary
session attributes.

Add capacity for user preferences
and system configuration.
Customize profile options with
values, value behaviors, validation,
category values, and security.
Define the levels at which the profile
option is enabled.

Configure values in an existing Applications developer, application Manage the values for existing
profile option administrator, and implementation profile options.
consultant

Create and edit profile option Applications developer, application Manage categories for organizing
categories administrator, and implementation existing profile options.
consultant

Note
Since a profile option enables a behavior in an application user interface or across applications, a value change
made by an end user is reflected in the UI page for managing profile option values.
Before Creating a Profile Option

Profile options are best defined for managing configuration data centrally and influencing the behavior of applications.
If the purpose of a profile option setting is specific to a piece of data (typically setup data), it is best implemented as an
attribute of that data.
Do not use profile options for behavior that is not configurable.
Profile options exist independent of role.
Do not use profile options to implement function security. For example, an application should not check for a profile option
value set to yes to provide access to a page. Do not use profile options to implement data security, such as a profile option
value that must be set to a specific value to provide view access to an entity.
Do not use profile options to capture a dynamic system states, such as data stored in a temporary table. Use Global
Variables for temporary states instead.
Evaluate if there is a genuine need before creating a profile option. Do not force users to make a decision about an aspect of
their application use that is of no concern.
Evaluating need includes looking for duplicate or similar profile options, even in other products, before creating a new one.
For example, you do not need multiple profile options to choose a preferred currency.
719
Profile Options Data Model

The profile option data model illustrates the relationships among profile option elements.
The figure shows the data model of profile option entities.
For more information about planning profile options, see the Oracle Fusion Applications Developer's Guide.
Managing Profile Options: Points to Consider

A profile option definition consists of a name for the profile option and valid values. It is defined within a module of the
application taxonomy. Application developers manage profile options to create new profile options or modify existing profile
option definitions, which includes specifying the levels at which a profile option is enabled and defining values. Implementation
consultants and application administrators configure existing profile options by managing the profile option's updatable
values, and creating categories that group profile options.
Configuring a Profile Option

A profile option definition includes information about the owning application and module in the application taxonomy. A start
or end date, or both may limit when a profile option is active. The profile option definition may include an SQL validation
statement that determines which values are valid, and the hierarchy levels at which the profile option is enabled and
updatable.
To be visible to users, a profile option must be user enabled. You can also allow user updates of the profile option, which
means users can make changes to the validation and the profile option level information.
Profile option levels specify at which context level profile values may be enabled or updated
Profile options should only be enabled for context levels that are appropriate for that profile option. For example, a profile
option indicating a global configuration setting should not be enabled at the user level, if users cannot choose a different value
for that setting.
720
SQL Validation
The SQL validation of the profile option definition determines what valid profile option values are available. In the absence of
validation, any value is valid.
For example, SQL validation provides a means of defining a list of values for the valid values of the profile option. The SQL
validation can use lookups to provide the valid values for profile options, such as the lookup codes of the YES_NO lookup
type.
With a profile option called DEFAULT_LANGUAGE, you can configure the following validation.
SELECT DESCRIPTION Language, NLS_LANGUAGE
FROM FND_LANGUAGES_VL
WHERE INSTALLED_FLAG IN ('B','I')
ORDER BY DESCRIPTION
This results in the following list of values based on data in FND_LANUGUAGE_VL.
Display Value Hidden Value
American English US

French F

Spanish E

Hidden values must be varchar2(2000).

Profile options generally provide configuration values within a particular context. Though you can create a profile option to be
global, think of global values as default values to avoid storing inappropriate configuration information as profile option values.
Create global profile options that have corresponding contextual levels.
Managing Profile Option Categories: Points to Consider

Use profile option categories to group profile options.
Organizing Profile Options in Categories

As a guideline, group profile options in a single category if the profile options affect the same feature, or if an administrator
would likely want to see the profile options in the results of a single search.
Application developers are responsible for the initial groupings and then administrators can make changes based on their
specific needs. Administrators can categorize profile options and then easily search on profile options by category.
Tip
Define profile option categories first and assign new profile options to existing categories rather than defining
profile options first and then defining categories to categorize them.
721
Adding New Profile Option Categories

You can add new categories or add profiles to an existing category.
You can create a profile option category by duplicating an existing category and editing it for a new grouping of profile
options. You can add multiple profile options to a category. A profile option can exist in multiple categories.
Profile Option Order in a Category

Specify a profile option sequence to determine the order of profile options when queried by profile option category.
Viewing and Editing Profile Option Values: Points to Consider

A profile option value consists of the value and the context or level where the value is set. You specify the context with a
pairing of the profile option value's evel and level value, such as the product level and the level value GL for Oracle Fusion
General Ledger. Adding or modifying profile option values can include deciding which valid values are enabled or updatable at
which level.
The SQL validation of the profile option definition determines what valid profile option values are available. In the absence of
validation, any value is valid.
Profile Option Levels and User Session Context

Site level profile option values affect the way all applications run for a given implementation. Product level profile option values
affect the way applications owned by a particular product code behave. For example, a product may use profile options set
at the product level to determine how regions provided by a common module such as those available from Oracle Fusion
Trading Community Model or Customer Relationship Management (CRM) display in a particular work area or dashboard. User
level profile option values affect the way applications run for a specific application user
Whichever profile option value is most specific to a user session, that is the value at which the profile option is set for the user
session.
For example, the predefined FND_LANGUAGE profile option sets the default language. In addition to a site level value, you
can define a value for various product or user levels.
Level Name Level Value Profile Option Value
Site InFusion American English

Product Customer Center French

Product CRM Application Composer American English

User Application Administrator American English

User Hima Hindi

Values at the site level take effect for any user unless overridden by a different value set at the more specific levels of product
and user. Product level profile option values affect the way applications owned by a particular product code behave. In
addition to user level profile option values in applications, selections may be available in the user preferences workspace.
The following table demonstrates the FND_LANGUAGE profile option settings that would apply to specific users, based on
the example above. For example, the user Hima is using the CRM Application Composer product, in the InFusion site. The
722
example above shows that this profile option is set to Hindi at the user level for Hima. Because user is the highest applicable
level for Hima, the applicable profile option value is Hindi for Hima.
Site Product User Highest Active Profile

Available Level Option Value
InFusion CRM Application Hima User Hindi

Composer

Acme Payables Application User American English

Administrator

InFusion Customer Center Guillaume Product French

InFusion Payables Implementation Site American English

Consultant

Acme Payables Implementation none no value

Consultant

Note
More than one site level value is relevant in an enterprise with multiple tenants using a single instance of Oracle
Fusion Applications.
Effect of Changes to Profile Option Values

Any change you make to a user level profile option has an immediate effect on the way applications run for that session.
When you sign in again, changes made to your user level profile options in a previous session are still in effect. When you
change profile option value at the product level and no user level values are set, you see the update immediately, but other
users may not see the changed value until signing out and back in. When you change a profile option value and the new value
affects other users, the change takes effect only when users sign in the next time.
Changes to site level profile options take effect for any user session that is started after the setting has been changed.
Changes to site or user level profile options do not affect any user sessions that are already in progress when the change is
made.
Changes to site or user level profile options take effect for any C or PL/SQL processes, such as scheduled jobs, that are
launched after the setting has been changed. Profile option changes do not affect C or PL/SQL processes that are already
running.
Manage Applications Core Administrator Profile Values

723
Message Properties

See: About Tokens
Related Topics
Profile Options and Related General Preferences: How They Work Together
Some Oracle Middleware Extensions for Applications profile options are related to general preferences in the global area.
Preferences
The related general preferences are Default Application Language, Territory, Date Format, Time Format, Currency, and Time
Zone. When the user changes any of these preferences, the stored values in LDAP are updated accordingly.
Profile Options
The corresponding profile options are Default Language, Default Territory, Default Date Format, Default Time Format, Default
Currency, and Default User Time Zone. No matter what you set for these profile options at any level, the preferences settings,
or LDAP values, take precedence. The profile option value is used only if the LDAP value is not available. Updating the profile
option value does not automatically update the value in LDAP or preferences.
724
FAQs for Manage Applications Core Administrator Profile

Values
How can I enable the privacy statement?
In the Setup and Maintenance work area, open the Manage Applications Core Administrator Profile Values task and search
for the Privacy Statement URL profile option. Update the profile value with the full URL of the web page containing the
privacy content. Subsequently, the Privacy Statement menu item appears in the global area under your user name, and is
linked to the given URL.
Manage Applications Core Value Sets

Value Sets: Explained
A value set is a group of valid values that you assign to a flexfield segment to control the values that are stored for business
object attributes.
An end user enters a value for an attribute of a business object while using the application. The flexfield validates the value
against the set of valid values that you configured as a value set and assigned to the segment.
For example, you can define a required format, such as a five digit number, or a list of valid values, such as green, red, and
blue.
Flexfield segments are usually validated, and typically each segment in a given flexfield uses a different value set. You can
assign a single value set to more than one segment, and you can share value sets among different flexfields.
Caution
Be sure that changes to a shared value set are compatible with all flexfields segments using the value set.
The following aspects are important in understanding value sets:

• Managing value sets
• Validation
• Security
• Precision and scale
• Usage and deployment
• Protected value set data
Managing Value Sets

To access the Manage Value Sets page, use the Manage Value Sets task, or use the Manage Descriptive Flexfields and
Manage Extensible Flexfields tasks for configuring a segment, including its value set. To access the Manage Values page,
select the value set from the Manage Value Sets page, and click Manage Values. Alternatively, click Manage Values from
the Edit Value Set page.
Validation
The following types of validation are available for value sets:
• Format only, where end users enter data rather than 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
725
• 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
A segment that uses a format only value set doesn't present a list of valid values to users.
Note
Adding table validated value sets to the list of available value sets available for configuration is considered a
custom task.
Restriction
For the Accounting Key Flexfield 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 flexfield segments.
You can specify that data security be applied to the values in flexfield segments that use a value set. Based on the roles
provisioned to users, data security policies determine which values of the flexfield segment end users can view or modify.
Value set security applies 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 flexfield is secured. It isn't possible to disable security for individual usages of the same value
set.
Value set security applies to independent, dependent, or table-validated value sets.
Value set security applies mainly when data is being created or updated, and to key flexfield combinations tables for query
purposes. Value set security doesn't determine which descriptive flexfield data is shown upon querying.
Security conditions defined on value sets always use table aliases. When filters are used, table aliases are always used by
default. When predicates are defined for data security conditions, make sure that the predicates also use table aliases.
For key flexfields, the attributes in the view object that correspond to the code combination ID (CCID), structure instance
number (SIN), and data set number (DSN) cannot be transient. They must exist in the database table. For key flexfields, the
SIN segment is the discriminator attribute, and the CCID segment is the common attribute.
Precision and Scale

If the data type of a value set is Number, you can specify the precision (maximum number of digits user can enter) or scale
(maximum number of digits following the decimal point).
Usage and Deployment

The usage of a value set is the flexfields where that value set is used. The deployment status of flexfields in which the value
set is used indicates the deployment status of the value set instance.
726
The figure shows a value set used by a segment in a key flexfield and the context segment of a descriptive flexfield.
For most value sets, when you enter values into a flexfield 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 flexfield 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.
Protected Value Set Data

Application developers may mark some value sets as protected, indicating that you can't edit them.
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.
Note
There is no restriction on references to protected value sets. Value sets, protected or not, may be assigned to
any flexfield segment. Likewise, other value sets may reference protected value sets; for example, an unprotected
dependent value set may reference a protected independent value set.
727
Related Topics
• Flexfields and Value Sets: How They Work Together
• Chart of Accounts: How Its Components Fit Together
• Why can't I edit my flexfield or value set configuration?
• Defaulting and Deriving Segment Values: Explained
Defining Value Sets: Critical Choices

Validation and usage of value sets determine where and how end users access valid values for attributes represented by
flexfield segments.
Tip
As a flexfield guideline, define value sets before configuring the flexfield, because you can assign value sets to
each segment as you configure a flexfield. With descriptive and extensible flexfield segments, you can create value
sets when adding or editing a segment on the run time page where the flexfield appears.
The following aspects are important in defining value sets:
• Value sets for context segments

• Format-only validation
• Interdependent value sets
• Table validation
• Range
• Security
• Testing and maintenance

When assigning a value set to a context segment, you can only use table-validated or independent value sets.
Format Only Validation

The format only validation type enables end users to enter any value, as long as it meets your specified formatting rules. That
is, the value must not exceed the maximum length you define for your value set, and it must meet any format requirements for
that value set.
For example, if the value set allows only numeric characters, users can enter the value 456 (for a value set with maximum
length of three or more), but can't enter the value ABC. A format only value set doesn't otherwise restrict the range of
different values that users can enter. For numeric values, you can also specify if a numeric value should be zero filled or how
may digits should follow the radix separator.
Interdependent Value Sets

Use an independent value set to validate input against a list that isn't stored in an application table, and not dependent on a
subset of another independent value set.
You cannot specify a dependent value set for a given segment without having first defined an independent value set that you
apply to another segment in the same flexfield. Use a dependent value set to limit the list of values for a given segment based
728
on the value that the end user has chosen for a related independent segment. The available values in a dependent list and the
meaning of a given value depend on which value was selected for the independently validated segment.
For example, you could define an independent value set of U.S. states with values such as CA, NY, and so on. Then
you define a dependent value set of U.S. cities, with values such as San Francisco and Los Angeles that are valid for the
independent value CA, and New York City and Albany that are valid for the independent value NY. In the UI, only the valid
cities can be selected for a given state.
Because you define a subset value set from an existing independent value set, you must define the independent value set
first. End users don't need to choose a value for another segment first to have access to the subset value set.
Independent, dependent, and subset value sets require a customized 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 customize the Manage Value Sets page to capture additional attributes for each valid value by adding
context-sensitive segments in a new context for FND_VS_VALUES_B descriptive field.
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 vendor 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 flexfield saves the ID value, instead of the value from the value column, in the associated
flexfield 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 attribute of the underlying table. You should also define an ID column that is based
on an attribute that isn't language-dependent so that the value's invariant ID (an ID that doesn't change) is saved in the
transaction table. This allows the run time to display the corresponding translated text from the value column for the run time
session's locale.
Table validation lets you enable a segment to depend upon multiple prior segments in the same context structure. You
cannot reference other flexfield segments in the table-validated value set's WHERE clause. That is, the WHERE clause cannot
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.
Restriction
If you use table validated value sets for key flexfields, then you can't use all integration functionalities supported for
key flexfields, such as:
• Data security
• Oracle Transactional Business Intelligence (OTBI)
• Extended Spread Sheet Database (ESSbase)
• Tree or hierarchy integration
To use these integration functionalities for key flexfieds, you must use independent value sets only.
729
Range
In the case of format, independent, or dependent value sets, you can specify a range to further 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 flexfield
segment end users can view or modify.
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 filters or SQL predicates, and policies that associate roles with
conditions. You can use a filter for simple conditions. For more complex conditions, use a SQL predicate.
Value set data security policies and conditions differ from data security conditions and policies for business objects in the
following ways:
• You can grant only read access to end users. You cannot specify any other action.
• When defining a condition that is 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 define the table, such as &TABLE_ALIAS category=70.
When you enable security on table-validated value sets, the security rule that is defined 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 filter the value list to x, y and z from a list of x, y, z, xx, yy, zz. The data security rule
or filter written against the value set shouldn't assume anything about the bind variables; it must assume that the whole list
of values is available and write the rule, for example, to allow x, or to allow y and z. By default in data security, all values are
denied and show only rows to which access has been provided.
Testing and Maintenance

There is no need to define or maintain values for a table-validated value set, as the values are managed as part of the
referenced table or independent value set, respectively.
You cannot manage value sets in a sandbox.
When you change an existing value set, the deployment status for all affected flexfields changes to Edited. You must redeploy
all flexfields that use that value set to make the flexfields reflect the changes. In the UI pages for managing value sets, the
value set's usages show which flexfields are affected 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 cannot change this option if you decide to provide them later.
Related Topics
• Table-Validated Value Sets and Bind Variables: Points to Consider
• What happens if a value set is security enabled?
• Adding Attributes to the Manage Value Sets Page: Procedures
730
Manage Applications Core Descriptive Flexfields

Flexfields: Overview
A flexfield is an extensible set of placeholder fields in application pages that are associated with a business object. Each
segment of the flexfield corresponds to a single application field, such as a segment of a key identifying a particular purchase,
or the components of a student's contact information, or the features of a product in inventory.
Using descriptive and extensible flexfields, you can extend business objects to capture data that wouldn't otherwise
be tracked by the application. If you need to add custom fields to a business object to meet your enterprise-specific
requirements, configure the flexfield to have one segment for each needed field.
Flexfields let you meet enterprise requirements without changing the data model. Different data can be captured on the
same database table. Each segment captures a single atomic value, has a name, and maps to a pre-reserved column in the
application database.
You can use a flexfield to extend a business object if it has been registered for use on that object. Application developers
create a flexfield and register it so that it is available for configuration. Administrators and implementation consultants set up
or configure segments and other properties of the available flexfields. End users see flexfield segments as fields or attributes
of information displayed in the application user interface. They enter a value for the attribute. The value may be selected from
a list of valid values or entered as free-form text that complies with formatting rules.
The following aspects provide an overview of flexfields:
• Accessing flexfields and flexfield management tasks
• Types of flexfields
• Flexfield segments
• Value sets
• Structure and context
• Deployment
• Run time appearance
Accessing Flexfields and Flexfield Management Tasks

You can view flexfields on a page where they occur using the Highlight Flexfields feature. You can access flexfield
management tasks directly from a highlighted flexfield, through product-specific flexfield management tasks, or by starting in
the Setup and Maintenance Overview page which is available from the Navigator or the Administration menu.
For lists of flexfields, see assets with the Flexfield: Descriptive, Flexfield: Extensible, or Flexfield: Key type in Oracle Enterprise
Types of Flexfields
The following three types of flexfields are available in Oracle Fusion Applications and provide a means to customize
applications features without programming.
• Key
731
• Descriptive
• Extensible
For example, in Oracle Fusion Financials, key flexfields represent objects such as accounting codes and asset categories.
Generally, correct operations of a product depend on key flexfield setup. In Oracle Fusion Payables, a descriptive flexfield
lets you collect custom invoice details fields on an invoices page. You can implement these fields, which are descriptive
flexfield segments, as context-sensitive so they appear only when needed on a row-by-row basis when specific contextual
information is met. Extensible flexfields are similar to descriptive flexfields, but provide additional advanced features. Generally,
setup of descriptive and extensible flexfields is optional because their segments capture custom fields needed beyond the
predefined fields.
Segments
Each field that you configure using flexfields is a flexfield segment. Segments represent attributes of information. They can
appear globally wherever the flexfield is implemented, or based on a structure or context.
You define the appearance and meaning of individual segments when configuring a flexfield.
A key flexfield segment commonly describes a characteristic of the entity identified by the flexfield, such as a part number
structured to include information about the type, color, and size of an item. A descriptive flexfield segment represents an
attribute of information that describes a characteristic of the entity identified on the application page, such as details about a
device containing components, some of which are globally present on the page while others are contextually dependent on
the category of the device.
Value Sets
A value set is a named group of values that can be used to validate the content of a flexfield segment.
You configure a flexfield segment with a value set that establishes the valid values that an end user can enter for the segment.
You define the values in a value set, including such characteristics as the length and format of the values. You can specify
formatting rules, or specify values from an application table or predefined list. Multiple segments within a flexfield, or multiple
flexfields, can share a single value set.
Structure and Context

Key flexfields have structure. Descriptive flexfields and extensible flexfields have context.
Each key flexfield structure is a specific configuration of segments. Adding or removing segments, or rearranging their order,
produces a different structure. The database columns on which segments in different structures are based can be reused in
as many structures as desired.
Descriptive flexfield segments can be context-sensitive, which means available to an application based on a context value
rather than globally available wherever the flexfield appears. A descriptive flexfield context is a set of context-sensitive
segments that store information related to the same context value. You define contexts as part of configuring a descriptive
flexfield. End users see global segments, as well as any context-sensitive segments that apply to the selected context value.
Extensible flexfield segments are made available to an application based upon a category value. An extensible flexfield context
serves as a container for related segments, used to organize the various segments that are applicable to a category value.
You define contexts with context-sensitive segments and associate them to categories as part of configuring an extensible
flexfield. End users see the segments displayed in subregions, one for each context associated to the selected category
value.
In descriptive flexfields and extensible flexfields, the database columns on which context-sensitive segments are based can
be reused in as many contexts as desired.
Deployment
A flexfield must be deployed to display its current definition in a run time application user interface. For example, if the
deployment status is Edited, the flexfield segments may appear in the UI based on the flexfield definition at the time of last
deployment, rather than the current definition.
732
Run Time Appearance

In an application user interface, descriptive flexfield segments appear as label and field pairs or as a table of fields where the
column headers correspond to the labels. The fields represent the flexfield segments and accept entered input or a selection
from a list of choices that correspond to the segment's assigned value set. Extensible flexfield segments appear grouped
within labeled regions, where each grouping is a context and the region labels are the context names.
Use the Highlight Flexfields command in the Administration menu of the Setup and Maintenance work area to identify the
location of the flexfields on the run time page. Flexfields in highlight mode display:
• An Information icon button to access details about the flexfield

• A Configure Flexfield icon button to manage the flexfield
• Tools to add and edit flexfield segments for descriptive and extensible flexfields
All segments of a single flexfield are grouped together by default. The layout and positions of the flexfield segments depend
on where the application developer places the flexfield on the page. Flexfields may also be presented in a separate section of
the page, in a table, or on their own page or subwindow.
You can use Oracle Composer to edit the layout, position, or other display features of the flexfield segments.
Related Topics
• Descriptive Flexfields: Explained
• Accessing Flexfield Management Tasks: Procedures
Configuring Flexfields: Overview

Configuring a flexfield ranges from identifying the need for extending a business object with custom attributes to integrating
the custom attributes into the deployment. In the case of key flexfields, configuring the flexfield involves identifying value set
assignments and determining segment structures.
Overall Process for Configuring Custom Attributes

For descriptive and extensible flexfields, the overall configuration process involves the following:
business objects.
3. Plan flexfield validation.
4. Define the attributes by configuring the flexfield segments.
a. Use the Manage Extensible Flexfields or Manage Descriptive Flexfields tasks, or use the Configure Flexfield
icon button directly on the page where the flexfield is highlighted. For simple configurations, use the Add
Segment, Add Context Value, and Edit Segment icon buttons directly on the page where the flexfield is
highlighted.
733
5. Deploy the flexfield to the mainline to display the custom attributes on the application pages and to make them
available for integration with other tools such as Oracle Business Intelligence.
6. Perform the necessary steps to integrate the custom attributes into the technology stack.
A simple configuration is limited to such actions as adding a format-only field or adding a field with a basic list of values.
Overall Process for Configuring Custom Keys

For key flexfields, the overall configuration process involves the following:
business objects.
3. Plan the flexfield validation.
4. Define the value sets before configuring the key flexfield segments by going to the Manage Value Sets task.
5. Define the key flexfield structures and their segments, and define structure instances for each structure.
a. Use the Manage Key Flexfields task or the Configure Flexfield icon button directly on the page where the
flexfield is highlighted.
6. Deploy the flexfield to the mainline to display it on the application pages and to make it available for integration with
other tools such as Oracle Business Intelligence.
7. Perform the necessary steps to integrate the flexfield into the technology stack.
Related Topics
• Descriptive Flexfields: Explained
• Managing Flexfields: Points to Consider
Flexfields at Run Time: Explained

Many business objects in Oracle Fusion applications have an associated descriptive or extensible flexfield with which you
can create custom attributes for the business object. Some business objects have an associated key flexfield for configuring
flexible multiple part keys.
The following aspects are important in understanding flexfields at run time:
• Finding flexfields on a page

• Why no flexfields are on a page
734
Finding Flexfields on a Page

At run time, the custom attributes you define as extensible and descriptive flexfield segments appear in the application page
just like any other attribute. Key flexfields typically appear in the application page as a field with a key flexfield icon, where the
field's value is actually a collection of segments. In some pages, one or more key flexfield segments may be displayed in the
page like any other attribute. Thus, when viewing the page in standard mode, in many cases you may not be able to discern
which fields are flexfield segments, or whether flexfields are available to configure on the page.
Use the Highlight Flexfields feature to render the page in a special mode that lets you view:
• Where, if any, flexfields are available on your page

• Which, if any, of the fields on your page are flexfield segments rather than out-of-the-box fields
To obtain information about the flexfields on a page, open the page and choose Highlight Flexfields from the
Administration menu. Hover over the Information icon button next to the highlighted fields to display information about
the flexfield. Choose Unhighlight Flexfields from the Administration menu when you no longer want to see the highlighted
flexfields.
When you click the Configure Flexfield icon button for a highlighted flexfield, the applicable Manage Flexfields task is
displayed for that flexfield. For simple configurations of descriptive and extensible flexfields, you can click the Add Context
Value icon button to add a context value, or click the Add Segment or Edit Segment icon buttons to add or edit a global
segment or a context-sensitive segment that doesn't require advanced configuration.
Restriction
Not all flexfields are available for creating custom attributes. For example, some flexfields are protected, and you
either can't edit their configurations at all, or can do only limited changes to them. Consult the product-specific
documentation in Oracle Fusion Applications Help to verify whether there are any restrictions on using the flexfield.
Why No Flexfields Are on a Page

For a flexfield to be available in the page, it must be registered by developers. If a flexfield is available, you may configure
segments. The segments appear on the page only after you have successfully deployed the flexfield. For information about
registering flexfields, see the Oracle Fusion Applications Developer's Guide. Some business objects haven't been designed
to support flexfields. For information about how to enable business objects with flexfield capability, see Getting Started with
Flexfields in the Oracle Fusion Applications Developer's Guide.
Note
Oracle Sales Cloud doesn't support flexfields.
To add custom attributes to these applications, use Application Composer. For more information, see the "Editing an Object:
Explained" section in Oracle Sales Cloud: Extending Sales.
Related Topics
• Accessing Flexfield Management Tasks: Procedures
• Customizing Flexfields Using Page Composer: Explained
Customizing Flexfields Using Page Composer: Explained

Using Page Composer, you can create customizations to flexfields that are specific to a page.
In Page Composer, to customize:
• Extensible flexfields, open the page in Source view, and look for a region that is bound to an
EffContextsPageContainer task flow. This is the container for the extensible flexfield attributes and contexts. To view
735
the flexfield code and identifying information, open the properties panel for the region. To customize any component
within the region, select the desired tag and click Edit.
• Descriptive flexfields, open the page in Source view, and look for <descriptiveFlexfield> elements. Open the properties
panel for the element to view the flexfield code and identifying information. Within the properties panel, you may
customize properties for the global and context-sensitive segments or re-order the segments on the page.
Related Topics
• Flexfields at Run Time: Explained
Accessing Flexfield Management Tasks: Procedures

You can configure and manage flexfields by highlighting them on an application page and using the available on-screen
configuration tools. Alternatively, you can access product-specific flexfield tasks or global flexfield management tasks.
Accessing Flexfield Management Tasks through the Run time Page

You can identify flexfields on the run time application page where they are implemented.
1. Navigate to an application page.
2. Choose Highlight Flexfields from the Administration menu in the global area of Oracle Fusion Applications.
3. View the available flexfields highlighted on the page. If any of the fields on the page are custom fields configured as
part of a flexfield, they also appear highlighted.
4. To edit a flexfield, use the:
◦ Configure Flexfield icon button to access the flexfield management task pages for extensive configuration to
the flexfield and its segments.
◦ Add Segment icon button to access the subwindow for adding segments with limited configuration to
◦ Edit Segment icon button to access the subwindow for limited configuration changes to descriptive and
extensible flexfield segments.
Accessing Flexfield Management Tasks through Setup and Maintenance

Manage flexfields using tasks you access by starting in the Setup and Maintenance Overview page which is available from the
Navigator or the Administration menu.
To access tasks for configuring flexfields and value sets, you must be provisioned with roles that entitle you to access the
Define Flexfields task list or tasks for managing product-specific flexfields. Contact your security administrator for details. For
information about product-specific flexfield tasks, such as Manage Purchasing Descriptive Flexfields, consult the product-
specific documentation in Oracle Fusion Applications Help
To access the flexfield management tasks and search for existing flexfields, perform the following steps:
1. Choose Setup and Maintenance from the Administration menu in the global area of Oracle Fusion Applications.
2. Search for Define Flexfields in the All Tasks tab.
736
Tip
◦ Use the Business Object parameter to search:
• Application Key Flexfields, Application Descriptive Flexfields, and Application Extensible Flexfields
to find all tasks related to flexfields.
• Application Flexfield Value Set to find all tasks related to value sets.
◦ To manage any:
• Flexfield across all Oracle Fusion Applications products, search for the Define Flexfields task list
and access the Manage Descriptive Flexfields, Manage Extensible Flexfields, and Manage Key
Flexfields tasks.
• Value set across all Oracle Fusion Applications products, search for the Define Flexfields task list
and access the Manage Value Sets task.
Restriction
If you are configuring key flexfields, search for and access the Manage Value Sets task to set up value
sets before accessing the Manage Key Flexfields task.
3. Expand the task list to view the included tasks.

4. Click the Task icon button to open the manage flexfield pages.
5. Search for all or specific flexfields.
6. In the search results, select the flexfield.
7. Use the Edit action to open pages for viewing and configuring the flexfield. Access to managing value sets is
available within the tasks for managing descriptive and extensible flexfields.
Note
Access to managing value sets is:
• Available within the tasks for managing descriptive and extensible flexfields.
• Not available within the tasks for managing key flexfields. Therefore, configure value sets prior to configuring your
key flexfield.
Flexfields and Oracle Fusion Application Architecture: How They Work Together
Administrators configure flexfield segments to capture data that represents the values of attributes. Flexfield segments
represent attributes of entities (business objects). Most business objects are enabled for descriptive flexfields. Some business
objects are enabled for extensible flexfields.
737
For example, an airline manufacturer might require very specific attributes for their orders that aren't provided by the out-
of-the-box implementation of an order. Because a flexfield exists for the order business object, you can use it to create and
configure the desired attribute.
The figure shows the layers of a flexfield: the business entity table and metadata in the database, business components
that are Application Development Framework (ADF) objects or ADF business component (ADFbc) objects derived from the
metadata and stored in Oracle Metadata Services (MDS) Repository, and the user interface where the input fields defined
by the flexfield segments are rendered. The flexfield definition consists of all the metadata defined during configuration and
stored in the database.
Application developers create a flexfield and register it so that it is available for configuration. Administrators and
implementation consultants configure segments and other properties of the available flexfields. This information is stored
as additional flexfield metadata in the database. Deploying the flexfield generates ADF business components based on the
flexfield metadata in the database.
738
The following aspects are important in understanding how flexfields and Oracle Fusion Applications architecture work
together:
• Integration
• Deployment
• Import and Export
• Run time
• Patching
Integration
The attributes that you add by configuring flexfields are available throughout the Oracle Fusion Middleware technology
stack, allowing the flexfields to be used in user interface pages, incorporated into the service-oriented architecture (SOA)
infrastructure, and integrated with Oracle Business Intelligence. You identify flexfield segments for integration by the
segment's Application Programming Interface (API) name.
A flexfield affects the Web Services Description Language (WSDL) schemas exposed by ADF services and used by SOA
composites. The Web services that expose base entity data also expose flexfield segment data.
Attributes incorporate into SOA infrastructure (BPEL, Rules) and integrate with business intelligence (Oracle Business
Intelligence, Extended Spread Sheet Database (ESSbase)).
Flexfield configurations are preserved across Oracle Fusion Applications updates.
Deployment
The metadata for the flexfield is stored in the application database as soon as you save your configuration changes.
Deploying the flexfield generates the ADF business components so that the run time user interface reflects the latest definition
of the flexfield in the metadata.
Importing and Exporting

You can export and import flexfields with a deployment status of Deployed or Deployed to Sandbox across instances of
Oracle Fusion Applications using the Setup and Maintenance Overview page. Ensure a flexfield is eligible for migration (by
verifying that it has successfully deployed) prior to attempting the migration.
Run time
For a flexfield to reflect the latest flexfield definition at run time it must be deployed. The user interface accesses a business
object and the deployed flexfield definition indicates which business object attributes the flexfield captures values for. If you
add display customizations for a flexfield using Oracle Composer, these are customizations on the page so that the same
flexfield segments can appear differently on various different pages.
Values entered for segments are validated using value sets.
Patching
Flexfield configurations are preserved during patching and upgrading.
Related Topics
• Flexfield Deployment Status: How It Is Calculated
Flexfields and Value Sets: Highlights

Before you use flexfields to create custom attributes, you should be familiar with the Oracle Fusion application architecture
that enables customization, customization layers, and the customization lifecycle.
739
In addition to the extensive information in the Oracle Fusion Applications Help about configuring flexfields that are already
available for configuration, consider the resources below for adding flexfields to business components and alternatives to
flexfields where flexfields cannot be enabled.
To assess the flexfields available in a deployment of Oracle Fusion Applications, see assets of type: flexfield in the Oracle
Enterprise Repository at http://fusionappsoer.oracle.com.
For customization not available through the tasks and user interface pages available in Oracle Fusion Applications, contact
My Oracle Support at http://www.oracle.com/pls/topic/lookup?ctx=acc=info or visit http://www.oracle.com/pls/topic/lookup?
ctx=acc=trs if you are hearing impaired.
Restriction
Don't use Oracle JDeveloper to customize flexfields.
Before Configuring Flexfields

You can add custom attributes to a business object using a flexfield, if a flexfield has been registered for that object by
developers.
• For Oracle Sales Cloud, use Application Composer to add custom attributes instead of using descriptive and
extensible flexfields.
• For information about synchronizing the updated XML schema definition (XSD) files in Oracle Metadata Services
(MDS) Repositories for each service-oriented architecture (SOA) application, refer to the Oracle Fusion Applications
Developer's Guide.
See: Customizing SOA Composite Applications
◦ Oracle ADF services used by SOA composites expose the Web Services Description Language (WSDL)
schemas where deployed flexfields are stored.
Oracle Business Intelligence

• For information about importing business intelligence-enabled flexfield changes into the Oracle Business Intelligence
repository, refer to the Oracle Transactional Business Intelligence Administrator's Guide.
See: Designating Flexfields as BI-Enabled
See: Importing Changes to Flexfields Automatically
Related Topics
• Flexfields: Overview
• Exporting and Moving Customizations: Points to Consider
• Defining Fields: Explained
740
Manage Applications Core Descriptive Flexfields: Manage

Flexfields
Managing Flexfields: Points to Consider
Managing flexfields involves registering, planning, and configuring flexfields.
You plan and configure the registered flexfields provided in your applications by applications developers. How you configure
flexfield segments determines how the flexfield segments appear to end users. Optionally, you can customize the UI page to
change how the flexfield segments appear to end users on that page.
The figure shows the processes involved in making flexfields available to end users. The tasks in the Define Flexfields activity
let administrators configure and deploy flexfields. If you deploy a flexfield to a sandbox and decide to apply the configuration
741
to the mainline, select the flexfield in the Manage Flexfields tasks of the Define Flexfields activity and deploy the flexfield in the
mainline so that it is available to users.
Consider the following aspects of managing flexfields:
• Registering flexfields
• Planning flexfields
• Configuring flexfields
• Enabling a flexfields segment for business intelligence
• Deploying flexfields
• Optionally changing a flexfield segment's appearance in a user interface page
• Identifying flexfields on a run time page and troubleshooting
742
Registering Flexfields
Application development registers flexfields so they are available to administrators and implementation consultants for
configuration.
As part of registering a flexfield, application development reserves columns of entity tables for use in flexfields so an enterprise
can capture segments to meet their business needs. Many flexfields are registered in Oracle Fusion Applications.
A flexfield must be registered before it can be configured.
For more information on registering flexfields, see Oracle Fusion Applications Developer's Guide.
Planning Flexfields
Before you begin planning flexfields, determine what type is appropriate to your needs, and which business objects are
available for customizing flexfields.
All flexfields consist of segments which represent attributes of an entity. The values an end user inputs for an attribute are
stored in a column of the entity table.
Carefully plan flexfields before configuring them. Before configuring new segments for your flexfields, be sure to plan their
implementation carefully.
If you have determined that a business object supports flexfields, and those flexfields have been registered, you can begin
planning how to configure the flexfield for your needs. Note the code name of the flexfield you intend to configure so you can
find it easily in the Define Flexfield activity.
In some cases you can customize how the flexfield appears on the page.
See Oracle Fusion Applications Help for specific products to determine any restrictions on using product-specific flexfields.
Configuring Flexfields
Administrators or implementers configure flexfields so they meet the needs of the enterprise. Some flexfields require
configuration to make an application operate correctly.
You can configure flexfields using the following methods:
• Go to the manage flexfield tasks in the Setup and Maintenance work area.
• Use the Highlight Flexfields command in the Administration menu while viewing a run time page.
◦ Use the Configure Flexfield icon button to manage all aspects of a flexfield, such as change a segment's
sequence number, or configure a flexfield segment's business intelligence label.
◦ Use the Add Segment and Edit Segment icon buttons to add and edit descriptive or extensible flexfield
segments with simple configurations.
◦ Use the Add Context icon button to add descriptive or extensible flexfield context values.
Configuring a flexfield includes the following:
• Defining value sets against which the values entered by end users are validated
• Defining the structure or context of the segments in the flexfield
• Specifying the identifying information for each segment
• Specifying the display properties such as prompt, length and data type of each flexfield segment
743
• Specifying valid values for each segment, and the meaning of each value within the application
Tip
You can create value sets while creating descriptive and extensible flexfield segments. However, define value sets
before configuring key flexfield segments that use them, because you assign existing value sets while configuring
key flexfield segments.
When creating table-validated, independent, dependent, or subset value sets while creating descriptive and extensible
flexfield segments, you can optionally specify to display the description of the selected value to the right of the segment at run
time.
display is always in a fixed order based on the segments' sequence numbers. You cannot enter a number for one segment
that is already in use for a different segment.
Tip
Consider numbering the segments in multiples, such as 4, 5, or 10, to make it easy to insert new attributes.
A flexfield column is assigned to a new segment automatically, but you can change the assignment before saving the
segment. If you need to set a specific column assignment for a segment, create that segment first to ensure that the intended
column isn't automatically assigned to a different segment.
Enabling a Flexfield Segment for Business Intelligence

You can enable flexfield segments for business intelligence if the flexfield is registered in the database as an Oracle Business
Intelligence-enabled flexfield. For more information on enabling segments for business intelligence, see points to consider
when enabling descriptive, extensible, and key flexfield segments for business intelligence.
For extensible flexfield segments, you can't assign labels to equalize segments across contexts that are semantically
equivalent.
Once you have configured a flexfield,, you must deploy it to make the latest definition available to run time users.
In the Define Flexfields tasks, you can deploy a flexfield using either of the following commands:
• The Deploy Flexfield command to deploy a flexfield to mainline. This is for general use in a test or production
environment.
• The Deploy to Sandbox command to deploy a flexfield to sandbox. This is to confirm that the flexfield is correctly
configured before deploying it to the mainline.
In Highlight Flexfields mode, when using the:
• Add Context, Add Segment, and Edit Segment tools for extensible flexfields, use the Save command to save
your changes, and then use the Deploy command to deploy the flexfield to mainline
• Add Segment and Edit Segment tools for descriptive flexfields, use the Save and Deploy command to save your
changes and deploy the flexfield to mainline
Once deployed, the deployment status indicates the state of the currently configured flexfield relative to the last deployed
definition.
Optionally Changing a Flexfield Segment Appearance

The flexfield attributes that you define integrate with the user interface pages where users access the attributes' business
object. Application development determines the UI pages where business objects appear and the display patterns used by
default to render flexfield segments.
744
After a flexfield has been deployed to the mainline Oracle Metadata Services (MDS) Repository so that it appears on
application pages, you can customize it on a per-page basis using Page Composer. For example, you can hide a segment,
change its prompt or other properties, or reorder the custom global attributes so that they are interspersed with the core
attributes in the same parent layout.
You can only customize the appearance of descriptive and extensible flexfield segments in the UI page using Pge Composer
once the flexfield is deployed to the mainline.
If the Oracle Fusion applications are running in different locales, you can provide different translations for translatable text,
such as prompts and descriptions. Enter translations by signing in using the locale that requires the translated text. You do
this by selecting Settings and Actions - Personalization - Set Preferences in the global area and changing the text to
the translated text for that locale.
Identifying Flexfields on a Run Time Page

The Highlight Flexfields command in the Administration menu of the Setup and Maintenance work area identifies the
location of flexfields on the run time page by displaying an Information icon button for accessing details about each flexfield.
Even if a descriptive or extensible flexfield hasn't yet been deployed and no segments appear on the run time page in normal
view, the flexfield appears in the Highlight Flexfield view for that page. In the case of:
• Descriptive flexfields, the segments as of the last deployment appear
• Extensible flexfields, any segments and contexts that have been saved but not yet deployed also appear as disabled
Highlight Flexfields accesses the current flexfield metadata definition.

Use the highlighted flexfield's Configure Flexfield icon button to manage flexfields directly. Alternatively, note a highlighted
flexfield's name to search for it in the tasks for managing flexfields.
For more information on creating flexfields and adding them to a UI page, see the Oracle Fusion Applications Developer's
Guide.
For more information about customizing flexfield segment appearance with Oracle Composer, see guidance on customizing
existing pages in the Oracle Fusion Applications Extensibility Guide.
Related Topics
• Managing Descriptive Flexfields: Points to Consider
• Flexfield Segment Properties: Explained
• Value Sets: Explained
• Managing Key Flexfields: Points to Consider
Flexfield Segment Properties: Explained

Independent of the value set assigned to a segment, segments may have properties that affect how they are displayed and
how they behave.
The following aspects are important in understanding
• Display properties
• Properties related to segment values
745
• Properties related to search
• Range validation segments
• Rule validation of segment values
• Naming conventions
Display Properties
The following table summarizes display properties.
Enabled Whether the segment can be used.

Sequence The order the segment appears in relation to the other

configured segments.

Prompt The string to be used for the segment's label in the user
interface.

Display type The type of field in which to display the segment.

Checked and unchecked values If the display type is check box, the actual values to
save. For example, Y and N or 0 and 1.

Display size The character width of the field.

Display height The height of the field as measured in visible number of

lines when the display type is a text area.

Read only Whether the field should display as read-only, not

editable text.

Description help text The field-level description help text to display for the
field. Use description help text to display a field-level
description that expands on or clarifies the prompt
provided for the field.

If description help text is specified, a Help icon button
is displayed next to the field in the run time application.
The description help text is displayed when the user
hovers over the Help icon button.

Instruction help text The field-level instruction help text to display for the field.
746

Use instruction help text to provide directions on
using the field. If instruction help text is specified, it is
displayed in an in-field help note window that appears
when users give focus to or hover over the field.

Properties Related to Search

Extensible flexfield segments can be marked as selectively required in search using the indexed property. The indexed
property requires end users to enter a value before conducting a search on the attribute represented by the indexed segment.
A database administrator must create an index on the segment column representing the indexed attribute.
Range Validation of Segments

Range validation enables you to enforce an arithmetic inequality between two segments of a flexfield. For example, a product
must be ordered before it can be shipped. Therefore, the order date must be on or before the ship date, and consequently
the order date segment value must be less than or equal to the ship date segment value. You can use range validation to
ensure this relationship.
The conditions for range validation are as follows:
• Segments must be configured for range validation in pairs, one with the low value and one with the high value.
• Both segments must be of the same data type.
• Both segments must be parts of the same structure in a key flexfield or parts of the same context in a descriptive
flexfield or extensible flexfield.
• The low value segment must have a lower sequence number than the high value segment.
• Non-range validated segments can exist between a range validated pair, but range validated pairs cannot overlap or
be nested.
You can configure as many range validated pairs as you want within the same flexfield. Your application automatically detects
and applies range validation to the segment pairs that you define, in sequence order. It must encounter a low value segment
first, and the next range validated segment that it encounters 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.
Rule Validation of Segment Values

Validation rules on descriptive and extensible flexfield segments determine how an attribute is validated. The value entered for
an attribute on a business object may need to match a specified format or be restricted to a list of values. Use a value set to
specify the validation rules.
Value set validation is required for global segments and context-sensitive segments, and optional for context segments. In
the case of context segments, the application may validate an input value instead of the value set validating the input value
against the context segment. However the application input values must match exactly the valid context segment 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.
When you configure a descriptive flexfield segment, you can specify a constant to use for setting 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 end users. The API
name is used to identify the segment in various integration points including web services, rules, and business intelligence.
747
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 permitted. You can't change the API name after the segment has been created.
Related Topics
Flexfields Segments: How They Are Rendered

Flexfield segments appear on pages as attributes of business objects.
Settings That Affect Flexfield Segment Display

When you configure flexfield segments, the value you enter for the segment's display type determines how the segment
appears on the run time page.
How Display Type ValuesAppear

The figure shows how display types appear at run time.
In the following figure, identify the display type by letter when referring to the table of descriptions for check box, drop-down
list, list of values, pop-up list of values, and radio button group.
748
In the following figure, identify the display type by letter when referring to the table of descriptions for radio button group, text
area, text box, date/time, and rich text editor.
The table describes each display type. The Example column refers to the figures above.
Check Box A The field is displayed as a check

box. If the end user selects the
checkbox, the checked value is
used. Otherwise, the unchecked
value is used.

749
Drop-down List B The field displays a dropdown list of

select a value.

List of Values C The field displays a dropdown list of

select a value. The user can also
click Search to find more values.

Pop-up List of Values D The field displays as a text field

with a Search icon button. The end
users can type a value in the text
field or they can click the Search
icon button to open a subwindow
for searching.

Radio Button Group E The field is displayed as a set of

radio buttons. The end user can
select one button. Selecting a
button deselects any previously
selected button in the set.

Text Area F The field is displayed as a text area

in which the end user can type
multiple lines of text. The display
width and height specify the visible
width and number of lines in the
text area, respectively.

Text Box G The field is displayed as a text field

in which the end user can type a
single line of text. The display width
controls the width of the text box.

Date/Time H The field enables the end user to

enter a date if the data type is Date,
or a date and time if the data type
is Date Time. The user can select
the date from a calendar. If the data
type is Date Time, the field also
displays fields for specifying the
hour, minutes, seconds, AM or PM,
and time zone.

750
Rich Text Editor I The field is displayed as a text

area in which the end user can
enter and edit multiple lines of
formatted text. The display width
and height specify the visible width
and number of lines in the rich text
editor, respectively.

Restriction
This display type is
available for extensible
flexfields only.

Hidden The field isn't displayed.

Flexfields and Value Sets: How They Work Together

Value sets are specific to your enterprise. When gathering information using flexfields, your enterprise's value sets validate the
values that your users enter based on how you defined the value set.
You can assign a value set to any number of flexfield segments in the same or different flexfields. Value set usage information
indicates which flexfields use the value set.
The following aspects are important in understanding how flexfields and value sets work together:
• Defining value sets
• Shared value sets
• Deployment
Defining Value Sets

As a key flexfield guideline, define value sets before configuring the flexfield, because you assign value sets to each segment
as you configure a flexfield. With descriptive and extensible flexfields, you can define value sets when adding or editing a
segment.
Caution
Be sure that changes to a shared value set are compatible with all flexfield segments that use the value set.
Shared Value Sets

When you change a value in a shared value set, the change affects the value set for all flexfields that use that value set. The
advantage of a shared value set is that a single change propagates to all usages. The drawback is that the change shared
across usages may not be appropriate in every case.
Value Set Values

To configure custom attributes to be captured on the value set values screen in the Manage Value Sets task, configure the
Value Set Values descriptive flexfield. The object's code is FND_VS_VALUES_B.This flexfield expects the context code to
correspond to the value set code. For each value set, you can define a context whose code is the value set code, and whose
751
context-sensitive segments will be shown for the values of that value set. By default the context segment is hidden since it
defaults to the value set code and is not expected to be changed.
You can also define global segments that will be shown for all value sets. However, this would be quite unusual since it would
mean that you want to capture that attribute for all values for all value sets.
Deployment
When you deploy a flexfield, the value sets assigned to the segments of the flexfield provide end users with the valid values for
the attributes represented by the segments.
Related Topics
• Flexfield Deployment: Explained
• Flexfields and Oracle Fusion Application Architecture: How They Work Together
• Defining Value Sets: Critical Choices
Defaulting and Deriving Segment Values: Explained

To populate a flexfield segment with a default value when a row is created, specify a default type of constant or parameter
and a default value.
To synchronize a segment's value with another field's value whenever it changes, specify the derivation value to be the
flexfield parameter from which to derive the attribute's value. Whenever the parameter value changes, the attribute's value is
changed to match. If you derive an attribute from a parameter, consider making the attribute read-only, as values entered by
users are lost whenever the parameter value changes.
When defaulting or deriving a default value from a parameter, only those attributes designated by development as parameters
are available to be chosen.
Different combinations of making the segments read only or editable in combination with the default or derivation value or
both, have different effects.
Initial run time behavior corresponds to the row for the attribute value being created in the entity table. If the default value is
read only, it cannot 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-modified segment value is overwritten when the derivation value
changes.
parameter
changes
None No Yes No initial segment The changed

value parameter
derivation value
updates segment
value

Constant Yes No Default segment N/A

value

752
parameter
changes
Constant Yes Yes Default segment The changed

value parameter
derivation value
updates segment
value

Parameter Yes No The default N/A

segment value is
the parameter's
default value

Parameter Yes Yes, and same as The default The changed

default value segment value is parameter
the parameter's derivation value
default and updates segment
derivation value value

Parameter Yes Yes, and different The default The changed

from default value segment value is parameter default
the parameter's value doesn't
default value update segment
value. Only the
changed derivation
value updates the
segment value.

Related Topics
• How can I set a default value for a flexfield segment?
Flexfield Usages: Explained

Usage affects various aspects of flexfields. The usage of the flexfield is set when the flexfield is registered and specifies the
application and table with which the flexfield is associated.
Entity usage indicates the table containing the segments of a flexfield.
A flexfield can have multiple usages. The first table registered for a flexfield is the master usage. Segments are based on the
master usage, and other usages of the same table for the same flexfield use the same segment setup, though the column
names optionally may have a differentiating prefix.
Extensible Flexfields
You can configure different behavior for extensible flexfield contexts at the usage level. The usage of an extensible flexfield
context determines in which scenarios or user interfaces the segments of a context appear to end users. For example, if a
Supplier page displays an extensible flexfield's supplier usage and a buyer page displays that same extensible flexfield's buyer
753
usage, a context that is associated to the supplier usage but not the buyer usage displays only on the supplier page and not
the buyer page.
Value Sets
The usage of value sets specifies the flexfields having segments where the value set is assigned.
FAQs for Manage Applications Core Descriptive Flexfields:

Manage Flexfields
Why did my flexfield changes not appear in the run time UI?
The ADF business components or artifacts of a flexfield, which are generated into an Oracle Metadata Services (MDS)
Repository when the flexfield is deployed, are cached within a user session. You must sign out and sign back in again to view
flexfield definition changes reflected in the run time application user interface page.
A flexfield's deployment status indicates whether the flexfield segments as currently defined in the metadata are available
to end users. The flexfield segments seen by end users in the run time correspond to the flexfield definition that was last
deployed successfully.
Related Topics
How can I enable flexfield segments for Oracle Social Network Cloud Service?
Descriptive flexfield segments can be enabled for integration with Oracle Social Network Cloud Service. When you manage
Oracle Social Network Objects during setup and maintenance, search for the business object that includes descriptive
flexfields, and select the business object attributes that are defined as flexfield segments.
Manage Applications Core Descriptive Flexfields: Deploy

Flexfields
Flexfield Deployment: Explained
Deployment generates or refreshes the Application Development Framework (ADF) business component objects that
render the flexfield in a user interface. The deployment process adds the custom attributes to the Web Services Description
Language (WSDL) schemas that are exposed by Oracle ADF services and that are used by SOA composites. Flexfields are
deployed for the first time during the application provisioning process. After you configure or change a flexfield, you must
deploy it to make the latest definition available to end users.
If a descriptive flexfield is enabled for business intelligence, the deployment process redeploys the flexfield's business
intelligence artifacts.
You can deploy a flexfield to a sandbox for testing or to the mainline for use in a test or production run time environment. You
can deploy extensible flexfields as a background process.
After deployment, the custom attributes 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 custom attributes. You must
sign out and sign back in to Oracle Fusion Applications to see the changes you deployed in the run time.
The following aspects are important in understanding flexfield deployment:
• Deployment Status
754
• Initial Deployment Status

• Metadata Validations
• Metadata Synchronization
• Deployment as a Background Process
• Export of Artifacts from Flexfield MDS
Deployment Status
Every flexfield has a deployment status.
A flexfield can have the following deployment statuses:
Deployment Status Meaning
Edited The flexfield metadata definition hasn't been deployed

yet. Updates of the metadata definition aren't applied in
the run time environment yet.

Patched The flexfield metadata definition has been modified

through a patch or through a data migration action, but
the flexfield hasn't yet been deployed so the updated
definition isn't reflected in the run time environment.

Deployed to Sandbox The current metadata for the flexfield is deployed in ADF
artifacts and available as a flexfield-enabled sandbox.
The status of the sandbox is managed by the Manage
Sandboxes task available to the Administrator menu of
the Setup and Maintenance work area.

Deployed The current metadata for the flexfield is deployed in ADF

artifacts and available to end users. There haven't been
any changes to the flexfield since it was last deployed in
the mainline.

Error The deployment attempt in the mainline failed.

Note
Whenever a value set definition changes, the deployment status of a flexfield that uses that value set changes to
edited. If the change results from a patch, the deployment status of the flexfield changes to patched.
Initial Deployment Status of Flexfields

The Oracle Fusion Applications installation loads flexfield metadata into the database. This initial load sets the flexfield status
to Edited. The application provisioning process during installation deploys the flexfields of the provisioned applications, which
sets their status to Deployed if no errors are encountered.
When accessing a provisioned application, deployed flexfields are ready to use. In some cases, flexfield availability at run time
requires setup, such as defining key flexfields.
755
Metadata Validation
Use the Validate Metadata command to view possible metadata errors before attempting to deploy the flexfield. Metadata
validation is the initial phase of all flexfield deployment commands. By successfully validating metadata before running the
deployment commands, you can avoid failures in the metadata validation phase of a deployment attempt. The deployment
process aborts if it encounters an error during the metadata validation phase. Metadata validation results don't affect the
deployment status of a flexfield.
Metadata Synchronization
When an extensible or descriptive flexfield is deployed, the deployment process regenerates the XML schema definition
(XSD), which makes the custom attributes available to web services and the SOA infrastructure.
After deploying a flexfield configuration, you must synchronize the updated XML schema definition (XSD) files in the Oracle
Metadata Services (MDS) repositories for each SOA application.
Note
To synchronize the updated XSD files in the MDS repositories in Oracle Cloud implementations, log a service
request using My Oracle Support at http://support.com/
Deployment as a Background Process

You can deploy extensible flexfields or incremental changes made to extensible flexfields as a background process. You must
use this action to deploy extensible flexfields that have more than 30 categories. You can also use this action if you want to
deploy several extensible flexfields, or if you want to continue working in your session without having to wait for a deployment
to complete.
Export of Artifacts from Flexfield MDS

You can export business components from MDS for descriptive, extensible, or key flexfields, mainly for use in troubleshooting
issues with flexfields. Use Download Flexfield Archive on the Manage Flexfields page to export MDS artifacts of the
selected flexfield, and import them to an archive on your local machine. You can use these archived business components of
flexfields for troubleshooting purposes.
Alternatively, export the deployed artifacts using exportMetadata WLST.
Related Topics
• Deploying a Flexfield to a Sandbox: Points to Consider
• Deploying Flexfields Using the Command Line: Explained
• Why did my flexfield changes not appear in the run time UI?
Flexfield Deployment Status: How It Is Calculated

Flexfield deployment status indicates how the flexfield metadata definition in the Oracle Fusion Applications database relates
to the Application Development Framework (ADF) business components generated into an Oracle Metadata Services (MDS)
Repository.
The following aspects are important in understanding how flexfield deployment status is calculated:
• Settings that affect flexfield deployment status

• How deployment status is calculated
756
Settings That Affect Flexfield Deployment Status

If you have made a change to a flexfield and expect a changed deployment status, be sure you have saved your changes. No
settings affect flexfield deployment status.
How Deployment Status Is Calculated

If the flexfield definition has been edited through the Define Flexfields activity task flows, the status is Edited. The latest
flexfield metadata definition in the Oracle Fusion application diverges from the latest deployed flexfield definition. Any change,
including if a value set used in a flexfield changes, changes the deployment status to Edited. If a flexfield has never been
deployed, its status is Edited.
Note
When an application is provisioned, the provisioning framework attempts to deploy all flexfields in that application.
If you deploy the flexfield to a sandbox successfully, the status is Deployed to Sandbox. The latest flexfield metadata definition
in the Oracle Fusion application matches the metadata definition that generated ADF business components in a sandbox
MDS Repository. Whether the sandbox is active or not doesn't affect the deployment status. If the flexfield was deployed
to a sandbox and hasn't been edited or redeployed to the mainline 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 flexfield successfully to the mainline, the status is Deployed. The latest flexfield metadata definition in the
Oracle Fusion application matches the metadata definition that generated ADF business components in a mainline MDS
Repository. Change notifications are sent when a flexfield is deployed successfully to the mainline.
If either type of deployment fails so that the current flexfield definition isn't deployed, the status is Error. The deployment error
message gives details about the error. The latest flexfield metadata definition in the Oracle Fusion application likely diverges
from the latest successfully deployed flexfield definition.
If the flexfield definition has been modified by a patch, the status is Patched. The latest flexfield metadata definition in the
Oracle Fusion application diverges from the latest deployed flexfield definition. If the flexfield definition was Deployed before
the patch and then a patch was applied, the status changes to Patched. If the flexfield definition was Edited before the patch
and then a patch was applied, the status will remain at Edited to reflect that there are still changes (outside of the patch) that
aren't yet in effect.
When a deployment attempt fails, you can access the Deployment Error Message for details.
Related Topics
• Deploying Flexfields Using the Command Line: Explained
Deploying a Flexfield-Enabled Sandbox: How It Works With Mainline Metadata

The flexfield definition in a sandbox corresponds to the flexfield metadata definition in the Oracle Fusion Applications database
at the time the flexfield was deployed to the sandbox. When the flexfield is ready for end users, the flexfield must be deployed
to the mainline.
A flexfield-enabled sandbox uses the following components.
• Flexfield metadata in the Oracle Fusion Applications database

• Flexfield business components in a sandbox Oracle Metadata Services (MDS) Repository
• User interface customizations for the flexfield in the mainline MDS Repository
757
The figure shows the two types of deployment available in the Manage Flexfield tasks of the Define Flexfields activity.
Deploying a flexfield to a sandbox creates a sandbox MDS Repository for the sole purpose of testing flexfield behavior. The
sandbox is only accessible to the administrator who activates and accesses it, not to users generally. Deploying a flexfield to
the mainline applies the flexfield definition to the mainline MDS Repository where it is available to end users. After deploying
the flexfield to the mainline, customize the page where the flexfield segments appear. Customization of the page in the
sandbox MDS Repository cannot be published to the mainline MDS Repository.
Sandbox Metadata Services Repository Data

Deploying the flexfield to a sandbox generates the Application Development Framework (ADF) business components of a
flexfield in a sandbox MDS Repository for testing in isolation.
Warning
758
Mainline Metadata Services Repository Data

The Oracle Fusion Applications database stores the single source of truth about a flexfield. When the flexfield is deployed, the
ADF business component objects that implement the flexfield in the run time user interface are generated in the mainline MDS
Repository from this source.
Related Topics
Deploying a Flexfield to a Sandbox: Points to Consider

Deploying a flexfield to a sandbox creates a flexfield-enabled sandbox. Each flexfield-enabled sandbox contains only one
flexfield.
You can test the run time behavior of a flexfield in the flexfield-enabled sandbox. If changes are needed, you return to the
Define Flexfield tasks to change the flexfield definition.
When you deploy a flexfield to sandbox, the process reads the metadata about the segments from the database, generates
flexfield Application Development Framework (ADF) business component artifacts based on that definition, and stores in the
sandbox only the generated artifacts derived from the definition.
When you deploy a flexfield sandbox, the process generates the name of the flexfield sandbox, and that flexfield sandbox is
set as your current active sandbox. When you next sign in to the application, you can see the updated flexfield configurations.
The Oracle Fusion Applications global area displays your current session sandbox.
Note
Unlike a standalone sandbox created using the Manage Sandboxes tool, the sandbox deployed for a flexfield
contains only the single flexfield. You can manage flexfield sandboxes, such as setting an existing flexfield
sandbox as active or deleting it, using the Manage Sandboxes tool.
When you deploy a flexfield to the mainline after having deployed it to the sandbox, the sandbox-enabled flexfield is
Sandbox MDS Repository Data

The sandbox data lets you test the flexfield in isolation without first deploying it in the mainline where it could be accessed by
users.
Warning
Managing a Flexfield-Enabled Sandbox

When you deploy a flexfield as a sandbox, that flexfield-enabled sandbox automatically gets activated in your user session.
When you sign back in to see the changes, the sandbox is active in your session.
You can only deploy a flexfield to a sandbox using the Define Flexfields task flow pages.
You also can use the Manage Sandboxes feature in the Administration menu of the Setup and Maintenance work area to
activate and access a flexfield-enabled sandbox.
759
Note
Whether you use the Define Flexfields or Manage Sandboxes task flows to access a flexfield-enabled sandbox,
you must sign out and sign back in before you can see the changes you deployed in the run time.
You cannot publish the flexfield from the sandbox to the mainline. You must use the Define Flexfields task flow pages to
deploy the flexfield for access by users of the mainline because the flexfield configuration in the mainline is the single source of
truth.
Related Topics
• Deploying a Flexfield-Enabled Sandbox: How It Works With Mainline Metadata
• Why did my flexfield changes not appear in the run time UI?
Deploying Flexfields Using the Command Line: Explained

You can use the Manage Key Flexfields, Manage Descriptive Flexfields, and Manage Extensible Flexfields tasks to deploy
flexfields. You can also use WebLogic Server Tool (WLST) commands for priming the Oracle Metadata Services (MDS)
Repository with predefined flexfield artifacts and for deploying flexfields.
The table describes the available commands.
Deploys all flexfields for the specified enterprise

application. Only flexfields whose status is other than
deployed are affected by this command unless the
option is enabled to force all flexfields to be deployed
regardless of deployment status.

Initial application provisioning runs this command to
prime the MDS Repository with flexfield artifacts.

Deploy a single flexfield regardless of deployment status

Deploys flexfield changes that have been delivered using

a flexfield Seed Data Framework (SDF) patch. Deploys
flexfields that have a Patched deployment status.

Displays MDS label of flexfield changes for viewing and

deleting patching labels.

760
Displays list containing flexfields that aren't deployed or

failed deployment.

Executing these commands outputs a report at the command line. The report provides the following information for every
flexfield that is processed.
• Application identity (APPID)
• Flexfield code
• Deployment result, such as success or error
In case of errors, the report lists the usages for which the errors were encountered. If a run time exception occurs, the output
displays the traceback information. For each WLST flexfield command, adding the reportFormat='xml' argument returns the
report as an XML string.
Consider the following aspects of command line deployment.
• Preparing to use the WLST flexfield commands
• Using the deployFlexForApp command
• Using the deployFlex command
• Using the deployPatchedFlex command
• Using the deleteFlexPatchingLabels command
• Using the validateFlexDeploymentStatus command
• Exiting the WLST and checking the results
Preparing To Use the WLST Flexfield Commands

You can only execute the WLST flexfield commands on a WebLogic Administration Server for a domain that has a running
instance of the Oracle Fusion Middleware Extensions for Applications (Applications Core) Setup application.
For more information on deploying the Applications Core Setup application, see the Oracle Fusion Applications Developer's
Guide.
Ensure that the AppMasterDB data source is registered as a JDBC data source with the WebLogic Administration Server and
points to the same database as the ApplicationDB data source.
Start the WebLogic Server Tool (WLST) if it isn't currently running.
UNIX:
sh $JDEV_HOME/oracle_common/common/bin/wlst.sh
Windows:
wlst.cmd
Connect to the server, replacing the user name and password arguments with your WebLogic Server user name and
password.
761
connect('wls_username', 'wls_password', 'wls_uri')
The values must be wrapped in single-quotes. The wls_uri value is typically T3://localhost:7101.
For more information on the WLST scripting tool, see the Oracle Fusion Middleware Oracle WebLogic Scripting Tool.
Using the deployFlexForApp Command

The deployFlexForApp command translates the product application's predefined flexfield metadata into artifacts in the MDS
Repository.
Important
This command is run automatically when you provision applications. However, after custom applications
development, you must run the deployFlexForApp command after you configure your application to read the flexfield
artifacts from the MDS Repository and before you log into the application for the first time, even if there is no
predefined flexfield metadata.
This command doesn't deploy flexfields that have a status of Deployed unless the force parameter is set to 'true' (the default
setting is 'false').
For more information on priming the MDS partition with configured flexfield artifacts, see the Oracle Fusion Applications
Developer's Guide.
From the WLST tool, execute the following commands to deploy the artifacts to the MDS partition, replacing
product_application_shortname with the application's short name wrapped in single-quotes.
deployFlexForApp('product_application_shortname'[, 'enterprise_id'] [,'force'])
In a multi-tenant environment, replace enterprise_id with the Enterprise ID to which the flexfield is mapped. Otherwise, replace
with 'None' or don't provide a second argument.
To deploy all flexfields regardless of their deployment status, set force to 'true' (the default setting is 'false'). If you want to
deploy all flexfields in a single-tenant environment, you either can set enterprise_id to 'None', or you can use the following
signature:
deployFlexForApp(applicationShortName='product_application_shortname',force='true')
Tip
The application's short name is the same as the application's module name.
For more information about working with application taxonomy, see the Oracle Fusion Applications Developer's Guide.
Using the deployFlex Command

From the WLST tool, execute the following command to deploy a flexfield, replacing flex_code with the code that identifies
the flexfield, and replacing flex_type with the flexfield's type, which is either DFF, KFF, or EFF. The values must be wrapped in
single-quotes.
deployFlex('flex_code', 'flex_type')
Optionally, execute the following command if the flexfield is an extensible flexfield, and you want to deploy all the flexfield's
configurations.
Note
By default, extensible flexfields are partially deployed. That is, only the pages, contexts, or categories that had
recent changes, are deployed.
762
deployFlex('flex_code', 'flex_type', ['force_Complete_EFF_Deployment'])

where, forceCompleteEFFDeployment=None
Using the deployPatchedFlex Command

Use the deployPatchedFlex command for situations where the patching framework doesn't invoke the command, such as when
an application has been patched offline.
If the installation is multi-tenant enabled, the command deploys all patched flexfields for all enterprises. This command isn't
intended to be invoked manually.
Check with your provisioning or patching team, or the task flows for managing flexfields, to verify that the flexfield has a
Patched deployment status.
From the WLST tool, execute the following command to deploy the artifacts to the MDS partition.
deployPatchedFlex()
Execute the following command to deploy all flexfields that have either a READY status or an ERROR status.
deployPatchedFlex(mode='RETRY')
Using the deleteFlexPatchingLabels Command

Whenever you deploy flexfield changes to MDS using the deployPatchedFlex() WLST command, an MDS label is created in the
format FlexPatchingWatermarkdate+time. Use the deleteFlexPatchingLabels command to inquire about and delete these labels.
From the WLST tool, execute the deleteFlexPatchingLabels () command with no arguments to delete the flexfield patching labels.
To output a list of flexfield patching labels, execute the command with the infoOnly argument, as follows:
deleteFlexPatchingLabels(infoOnly='true')
Using the validateFlexDeploymentStatus Command

The validateFlexDeploymentStatus() WLST command checks the deployment status of all flexfields in an Oracle Fusion Applications
deployment.
validateFlexDeploymentStatus()
Use this command to verify that all flexfields in the current instance of provisioned Java EE applications are deployed.
Exiting the WLST and Checking the Results

To exit the tool, execute the following command.
disconnect()
Optionally, sign into the application, access user interface pages that contain flexfields, and confirm the presence of flexfields
for which configuration exists, such as value sets, segments, context, or structures.
Related Topics
763
Manage Applications Core Descriptive Flexfields: Manage

Descriptive Flexfields
Descriptive Flexfields: Explained
Descriptive flexfields provide a way to add custom attributes to entities, and define validation and display properties for them.
These attributes are generally standalone. They don't necessarily have anything to do with each other and aren't treated
together as a combination.
All Oracle Fusion Applications business entities that you can access are enabled for descriptive flexfields. Descriptive
flexfields are optional. You can choose whether or not to configure and expose segments for the descriptive flexfield defined
and registered in your database. For lists of descriptive flexfields, see assets with the Flexfield: Descriptive type in Oracle
Enterprise Repository for Oracle Fusion Applications (http://fusionappsoer.oracle.com).
A descriptive flexfield provides a set amount of segments for an entity. You make the segments of a descriptive flexfield
available to end users as individual fields in the application user interface.
Context
A descriptive flexfield can have only one context segment to provide context sensitivity.
The same underlying column can be used by different segments in different contexts. For example, you can define a
Dimensions context that uses the ATTRIBUTE1 column for height, the ATTRIBUTE2 column for width, and the ATTRIBUTE3
column for depth. You can also define a Measurements context that uses the same columns for other attributes: the
ATTRIBUTE1 column for weight, the ATTRIBUTE2 column for volume, and the ATTRIBUTE3 column for density.
Segments and Contexts

Descriptive flexfield segments are of the following types.
Global segment Always available

Context segment Determines which context-sensitive segments are

displayed

Context-sensitive segment Displayed depending on the value of the context

segment

764
In the figure, a descriptive flexfield has one context segment called Category for which there are three values: Resistor,
Battery, and Capacitor. In addition, the descriptive flexfield consists of two global segments that appear in each of the
contexts, and three context-sensitive segments that only appear in the context in which they are configured.
Application development determines the number of segments available for configuring. During implementation, you configure
the flexfield by determining the following:
• Which attributes to add using the available segments
• The context values
• The combination of attributes in each context
A segment can be used for different attributes, such as Height in Context1 and Color in Context2. Each segment of a
descriptive flexfield that you make available to end users is exposed in the user interface as an individual field.
Value Sets
For each global and context-sensitive segment, you configure the values allowed for the segment and how the values that
end users enter are validated, including interdependent validation among the segments.
Protected Descriptive Flexfield Data

Application developers may mark some data configurations in a descriptive flexfield as protected, indicating that you can't
edit them. You can't edit any portion of a protected descriptive flexfield.
765
Related Topics
• Managing Descriptive Flexfields: Points to Consider
• Managing Flexfields: Points to Consider
Planning Descriptive Flexfields: Points to Consider

Once you have identified a flexfield to configure, plan the configuration in advance. Compile a list of the UI pages and other
artifacts in your deployment that are affected by the configuration. Verify that you are provisioned with the roles needed to
view and configure the flexfield. View the flexfield using the Highlight Flexfields command in the Administration menu while
viewing the run time page where the flexfield appears. Plan how you will deploy the flexfield for test and production users.
Review the tools and tasks available for managing flexfields, such as the Define Flexfields task list, Manage Sandboxes, and
Highlight Flexfields for adding and editing flexfield segments.
Planning a descriptive flexfield can involve the following tasks:
1. Identify existing parameters.

2. Identify existing context values and whether the context value is derived.
3. Identify custom attributes and plan the descriptive flexfield segments, segment properties, and structure.
4. Plan validation rules.
5. Plan initial values.
6. Plan attribute mapping to Oracle Business Intelligence objects.
Identify Existing Descriptive Flexfield Parameters

Some descriptive flexfields provide parameters that can be used to specify the initial value of a descriptive flexfield segment.
The parameter is external reference data, such as a column value or a session variable. For example, if a flexfield has a user
email parameter, you can configure the initial value for a customer email attribute to be derived from that parameter.
Review the list of available parameters in the Derivation Value field in the Create Segment page for a descriptive flexfield. If
you decide to use one of the parameters to set an initial value, select that parameter from the Derivation Value drop-down
list when you add the descriptive flexfield segment.
Evaluate Whether the Context Value Is Derived

The context value for a descriptive flexfield might have been preconfigured to be derived from an external reference. For
example, if the context is Marriage Status, then the value might be derived from an attribute in the employee business object.
When the context value is derived, you might need to take the derived values and their source into consideration in your plan.
To determine whether the context value is derived, access the Edit Descriptive Flexfield task to view the list of configured
context values for the flexfield. The Derivation Value field in the Context Segment region displays a list of available parameters.
If context values have been preconfigured, see Oracle Fusion Applications Help for product-specific information about the use
of those values.
Plan the Segments, Segment Properties, and Structure

Identify the custom attributes you need for a business object to determine the segments of the descriptive flexfield. Determine
the segment properties such as the prompt, display type, or initial value.
The structure of the descriptive flexfield is determined by its global, context, and context-sensitive segments. Plan a global
segment that captures an attribute for every instance of the business object. Plan a context for segments that depend on
766
a condition of situation applying to a particular instance of the business object. Plan context-sensitive segments to capture
attributes that are relevant in the context.
There is only one context segment available for descriptive flexfields. If you have more than one group of custom attributes
where you could use the context segment, you will have to pick one group over the others, based on your company's needs
and priorities, and add the other custom attributes as global segments.
Plan Validation Rules

Define each segment's validation rules and check if value sets exist for those rules or you must create new ones. If you must
create a value set, you can create it either before configuring the flexfield or while creating or editing a segment.
When determining a segment's validation rules, consider the following questions:
• What is the data type - character, date, date and time, or number?
• Does the segment require any validation beyond data type and maximum length?
• Should a character type value be restricted to digits, or are alphabetic characters allowed?
• Should alphabetic characters automatically be changed to uppercase?
• Should numeric values be zero-filled?
• How many digits can follow the radix separator of a numeric value? In base ten numerical systems the radix
separator is decimal point.
• Does the value need to fall within a range?
• Should the value be selected from a list of valid values? If so, consider the following questions:
◦ Can you use an existing application table from which to obtain the list of valid values, or do you need to create
a custom list?
◦ If you are using an existing table, do you need to limit the list of values using a WHERE clause?
◦ Does the list of valid values depend on the value in another flexfield segment?
◦ Is the list of valid values a subset of another flexfield segment's list of values?
Plan Initial Values

For every segment, list the constant value or SQL statement, if any, to use for the initial value of the custom attribute.
Plan How Segments Map to Oracle Business Intelligence Objects

You can extend descriptive flexfields into Oracle Transactional Business Intelligence (OTBI) for ad hoc reporting purposes.
Determine the descriptive flexfield segments to be made available for reporting, and select the BI Enabled check box
accordingly on the Manage Descriptive Flexfields page. You must run a process to extend the BI enabled segments into
OTBI. For more information about extending the BI enabled segments into OTBI, see the Setup and Configuration chapter in
the Oracle Transactional Business Intelligence Administrator's Guide.
Depending on the reporting needs, you may map similar context-sensitive attributes from different contexts to the same
attribute in OTBI. For example, there may be a segment tracking the Product Color attribute in different contexts of a context
sensitive descriptive flexfield. You can use segment labels to map these context-sensitive attributes together by defining a
segment label and updating the BI Label list accordingly.
Related Topics
767
• Enabling Descriptive Flexfield Segments for Business Intelligence: Points to Consider
Managing Descriptive Flexfields: Points to Consider

Configuring descriptive flexfields involves managing the available flexfields registered with your Oracle Fusion Applications
database and configuring their flexfield-level properties, defining and managing descriptive flexfield contexts, and configuring
global and context-sensitive segments.
Every descriptive flexfield is registered to include a context segment, which you may choose to use or not.
In general, configuring descriptive flexfields involves:
1. Creating segment labels for business intelligence enabled flexfields.

2. Configuring global segments by providing identity information, the initial default value, and the display properties.
3. Configuring the context segment by specifying the prompt, whether the context segment should be displayed, and
whether a value is required.
4. Configuring contexts by specifying a context code, description, and name for each context value, and adding its
context-sensitive segments, each of which is configured to include identifying information, the column assignment,
the initial default value, and the display properties.
The following aspects are important in understanding descriptive flexfield management:
• Segments
• Adding Segments to a Highlighted Flexfield
• Usages
• Parameters
• Delimiters
• Initial Values
• Business Intelligence
Segments
display is always in a fixed order. You cannot enter a number for one segment that is already in use for a different segment.
Value sets are optional for context segments. The value set that you specify for a context segment consists of a set of
context codes, each of which corresponds to a context that is appropriate for the descriptive flexfield. 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 definition of each context segment specifies 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 cannot delete an existing context. Instead, you can disable the associated context value in
its own value set by setting its end date to a date in the past.
You can configure the individual global segments and context-sensitive segments in a descriptive flexfield. These segment
types are differentiated by their usage, but they are configured on application pages that use most of the same properties.
768
Adding Segments to a Highlighted Flexfield

When you highlight flexfields on a run time page and use an Add Segment icon button to create a segment, the segment
code, name, description, table column, and sequence number are set automatically. If you use an Add Segment icon button
to configure descriptive flexfield segments, you cannot use an existing value set. Value sets are created automatically when
you add the segments. You can enter the valid values, their descriptions, and the default value or specify the formatting
constraints for the value set, such as minimum and maximum values.
Depending on display type, the value set you create with the Add Segment icon button is either an independent value set
or a format-only value set. The table shows which type of value set is created depending on the segment display component
you select.
Display Component Value Set Created with Add Segment
Check box Independent

Drop-down list Independent

List of Values Independent

Radio Button Group Independent

Text Field With Search Independent

Text box Format Only

Text area Format Only

Date/Time Format Only

Tip
After you add a context value, refresh the page to see the new value.
Usages
Descriptive flexfield usages allow for the same definition to be applied to multiple entities or application tables, such as a
USER table and a USER_HISTORY table. Descriptive flexfield tables define the placeholder entity where the flexfield segment
values are stored once you have configured the descriptive flexfield. When you configure a flexfield, the configuration applies
to all its usages.
Parameters
Some descriptive flexfields provide parameters, which are attributes of the same or related entity objects. Parameters are
public arguments to a descriptive flexfield. Parameters provide outside values in descriptive flexfield validation. You use
parameters to set the initial value or derivation value of an attribute 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.
769
Delimiters
A segment delimiter or separator visually separates segment values when the flexfield is displayed as a string of concatenated
segments.
Initial Values
The SQL statement defining 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 the following bind variables in the WHERE clause of the SQL
statement.
◦ :{SEGMENT.<segment_code>}: Identifies a segment in the same context.

◦ :{CONTEXT.<context_code>;SEGMENT.<segment_code>}: Identifies a segment in a different context. The context
must be in the same category or in an ancestor category, and it cannot be a multiple-row context.
◦ :{VALUESET.<value_set_code>}: Identifies the closest prior segment in the same context that is assigned to the
specified value set.
◦ :{FLEXFIELD.<internal_code>}: Identifies a flexfield.
For more information about using bind variables, see the help for value sets.
Business Intelligence
Selecting a global, context, or context-sensitive segment's BI Enabled checkbox specifies that the segment is available for
use in Oracle Business Intelligence.
When the flexfield is imported into Oracle Business Intelligence, the label you selected from the BI Label dropdown list
equalizes the segment with segments in other contexts, and maps the segment to the logical object represented by the label.
Related Topics
• Defining Value Sets: Critical Choices
• Enabling Descriptive Flexfield Segments for Business Intelligence: Points to Consider
• Why can't I edit my flexfield or value set configuration?
Enabling Descriptive Flexfield Segments for Business Intelligence: Points to Consider

A descriptive flexfield that is registered in the database as enabled for Oracle Business Intelligence (BI) includes a BI Enabled
setting for each of its segments. When a global, context, or context-sensitive segment is BI-enabled, it is available for use in
Oracle Business Intelligence.
The following aspects are important in understanding BI-enabled flexfield segments:
• Flattening business components to use BI-enabled segments in Oracle BI

• Equalizing segments to prevent duplication and complexity in the flattened component
770
• Mapping attributes of flattened business components to logical objects in Oracle BI

• Managing the labels that map segments to logical objects in Oracle BI
After you deploy a business intelligence-enabled flexfield, use the Import Oracle Fusion Data Extensions for Transactional
Business Intelligence process to import the flexfield changes into the Oracle Business Intelligence repository. Users can make
use of the newly-generated attributes in business intelligence applications. For example, a user can generate a report that
includes attributes added by the descriptive flexfield. For additional information about logical objects and import, refer to the
Oracle Transactional Business Intelligence Administrator's Guide.
Flattening
When you deploy a business intelligence-enabled descriptive flexfield, the deployment process generates an additional
set of flattened 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 flattened business components
include attributes for business intelligence-enabled segments only. Flattening means each custom column in each context
shows up as an attribute in an Oracle Business Intelligence folder.
Flattened components include one attribute for the BI-enabled context-segment, and one attribute 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 flattened components include an additional single attribute representing
segments with that label.
• If you didn't assign a label, the flattened components include a discrete attribute for each BI-enabled context-
sensitive segment in each context.
Mapping to Logical Objects in Business Intelligence

You can simplify reporting by representing similar segments as a single logical object in Business Intelligence.
If you assign a label to any set of context-sensitive segments that serve the same purpose in different contexts, you can
consolidate or equalize the segments into a single attribute. This prevents duplication and the extra workload and complexity
that result from the flattening 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 attribute in the flattened business component.
Non-labeled context-sensitive segments aren't equalized across context values, so the flattened components include a
separate attribute for each context-sensitive segment for each context value.
Note
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 attribute in the
flattened components to a logical object in Oracle Business Intelligence. Using labels to map segments to BI logical objects
minimizes the steps for importing the flexfield into Oracle Business Intelligence.
Note
Assigning a label to a context-sensitive segment serves to equalize the attribute across contexts, as well as map
the equalized attribute to business intelligence.
Managing Labels
You may assign a predefined 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 field, 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
771
steps for importing the flexfield 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 flattened components
include a separate attribute for each non-labeled context-sensitive segment in each context.
Importing to Oracle Business Intelligence Repository

After you deploy a business intelligence-enabled flexfield, import the flexfield changes into the Oracle Business Intelligence
repository to make use of the newly flattened business components in business intelligence and then propagate the flexfield
object changes. When you import the metadata into the Oracle Business Intelligence repository, you must do so as the
FUSION_APPS_BI_APPID user.
Note
To import flexfield 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.
Tip
When you import a flexfield into the Oracle Business Intelligence repository, you see both <name>_ and <name>_c
attributes for each segment, along with some other optional attributes. The <name> attribute contains the value.
The <name>_c attribute 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 attributes.
Related Topics
FAQs for Manage Applications Core Descriptive Flexfields

Can I display the context segment in the project Cost Collection flexfield?
No. The context segment is predetermined for each page. Displaying it and changing the value may result in capture of data
that is not applicable for the current transaction.
Manage Applications Core Attachment Entities and Categories

Attachments: Explained
Attachments are pieces of supplementary information that users can associate with specific business objects such
as expense reports or purchase orders. Attachments can be URLs, desktop files, text, or in cases where available,
repository folders. For any given business object, a user may be able to only view attachments, or also create, delete, or
edit attachments, depending on security. For more information on an introduction to attachments, see the Oracle Fusion
Applications Developer's Guide.
Repository
Attachments are stored in a content management repository provided by Oracle WebCenter Content Server. Users managing
attachments have no real interaction with the repository unless the repository mode is enabled for attachments on specific
772
business objects. In that case, users can share attachments among objects, update attachments by checking them
out of and back into the repository, and perform other tasks. Access to attachment files is controlled by a digital signing
mechanism. Depending on security, users might have direct access to the repository.
Security
Data security that applies to a specific business object also applies to attachments for that object, as determined by the
attachment entity defined for the object. For example, if a user has no access to a specific expense report, then the same
user cannot access attachments for the expense report. You can also use attachment categories to control access and
actions on attachments, based on roles associated with the category. For more information on securing attachments, see the
Related Topics
• Attachment Entities: Explained
• What's an attachment category?
Attachment Entities: Explained

An attachment entity is usually a database entity, for example a table or view, that represents a business object attachments
can be associated with. Each attachment UI must be defined with a corresponding attachment entity, which not only
identifies the business object to attach to, but also controls what users can do. Attachment entities are used only in the
context of attachments and exist separately from the database entities that they are based on.
Edit and create attachment entities on the Manage Attachment Entities page, which you can access by starting in the Setup
and Maintenance Overview page and searching for the Manage Attachment Entities task. Though you would generally use
predefined attachment entities with attachment UIs, you might need to create new entities, for example when developing
custom UIs.
Entity Names
An attachment entity name should match the name of the table or view that represents the business object to attach to. The
name is also used in the repository folder that is automatically created to store attachments for the entity. The attachment
entity display name should be something that users know to represent the business object.
Database Resource
The data security policies associated with the database resource defined for the attachment entity would apply to
attachments for that entity. For example, based on the database resource for the expense reports attachment entity,
the same policies apply to attachments for expense reports. 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.
Enabling Security
Security based on the database resource associated with the attachment entity is always in effect. What you can enable or
disable is security based on attachment categories. If any of the attachment categories associated with the attachment entity
has data security defined, then that security applies to this entity only if enabled.
Related Topics
• Attachment Entities and Attachment Categories: How They Work Together
Attachment Entities and Attachment Categories: How They Work Together

The association between attachment entities and categories determines which categories can be used for an entity. For
example, categories associated with the expense report attachment entity are available to be implemented in attachment UIs
for expense reports. You can define these associations when managing either entities or categories. Any association changes
in either the Manage Attachment Entities or Manage Attachment Categories page are reflected on the other page. You can
access either page by starting in the Setup and Maintenance Overview page and searching for attachment tasks.
773
Managing Entities
You determine which attachment categories are relevant to a particular entity on the Manage Attachment Entities page, and
each entity must have at least one category. Depending on configuration, any or all of the available categories for that entity
are used. For example, you assign three categories to the expense reports attachment entity. For a particular expense report
page with attachments functionality, you can customize the attachments component to specify which of the three categories
are used. Based on your selection, the data security defined for each category, if any, is applied to attachments on that page
if the attachment entity has category-based security enabled.
Managing Categories
If you create an attachment category and need to assign it to multiple attachment entities, use the Manage Attachment
Categories page. The association means the same as the association on the Manage Attachment Entities page.
Related Topics
Attachments Troubleshooting: Explained

Attachments UIs for users to add and manage attachments are fully functional as is, and users usually would not encounter
issues. If you customize attachments in any way, for example by creating additional attachment categories and implementing
data security on them, then some issues might arise.
Issue: Unable to View, Add, Update, or Delete Attachments

Users encounter issues when trying to view attachments or perform actions such as adding attachments.
• Users can no longer see specific attachments that they were previously able to see.
• Likewise, they can no longer update or delete attachments.
• Users get an error stating that they do not have permission to add attachments.
Resolution
Use the Manage Attachment Entities page to ensure that attachment categories are associated to the relevant attachment
entity. For example, if users can no longer see attachments for an expense report, then search for the expense report
attachment entity and assign all necessary categories to it. You might need to check with your system administrator or help
desk to determine the exact entity used on the page with the expenses attachments or what categories to assign.
If data security is implemented on the categories for the attachment entity, then verify that the Enable Security check box is
selected in the Manage Attachment Entities page for that entity. Make sure that users have a role with the privileges shown in
the following table, to view, add, update, or delete attachments with a specific attachment category.
Action Privilege
View Read Application Attachment (FND_ READ_


Add or Update Update Application Attachment (FND_ UPDATE_


774
Action Privilege
Delete Delete Application Attachment (FND_ DELETE_


For example, if users have the Read Application Attachment privilege for all categories associated with the expense report
attachment entity, except the Receipts attachment category, then they can view all expense report attachments except
those created with the Receipts category. Likewise, if users do not have the Update Application Attachment privilege for
any attachment categories tied to the expense report attachment entity, then they cannot create any attachments at all for
expense reports.
For more information on attachment category data security, see the Oracle Fusion Applications Developer's Guide.
Issue: Missing Attachment Category

Users can see existing attachments, but the attachments no longer have an attachment category value.
Resolution
When the attachment was added, at least one category existed for the corresponding attachment entity, as otherwise the
attachment could not have been added. Since then, the entity was edited so that it no longer has any assigned categories, so
the user cannot see the category associated with that attachment.
Use the Manage Attachment Entities page to reassign attachment categories to the relevant attachment entity. For example,
if users can no longer see the Receipts attachment category for an attachment to an expense report, then search for
the expense report attachment entity and assign to it the Receipts category. You might need to check with your system
administrator or help desk to determine the exact entity used on the page with the expenses attachments or what additional
categories to assign.
Related Topics
FAQs for Manage Applications Core Attachment Entities and

Categories
What's an attachment category?
An attachment category is used to classify and secure attachments. Each attachment user interface must be defined with at
least one category for users to be able to add attachments. If there are multiple categories, users can view them and select
775
one when adding attachments. For example, attachments for an expense report can be categorized as receipts, scanned
invoice images, and so on.
You can also associate roles with categories to determine user access and actions for attachments, based on the categories
assigned to the attachment entity. For example, security for expense report attachments can be based in part on the
categories assigned to the expense report attachment entity. You can define multiple categories per module, and add and
manage custom categories for your own purposes. For more information on attachment category data security, see the
Use the Manage Attachment Categories page, which you can access by starting in the Setup and Maintenance Overview
page and searching for the Manage Attachment Categories task.
Related Topics
776
Implementing Project Financial Management Define WebLogic Communication Services Configuration
51 Define WebLogic Communication Services

Configuration
Oracle Sales Cloud CTI: Highlights
Oracle Sales Cloud Computer Telephony Integration (CTI) integrates with your telephony environment and must be manually
enabled in your deployment. This topic highlights what is required to set up the CTI feature and to implement logging of the
calls made using the CTI feature.
CTI is a feature of the customer contact process. You initiate phone communication to customers and employees with a
click of your mouse, leveraging your customer contact information and the application context. The CTI feature uses Oracle
WebLogic Communication Services, OWLCS, to enable communications. Applications that provide the CTI functionality do so
primarily through contextual actions.
Additionally, CTI utilizes Oracle Sales Cloud tasks as an optional transaction logging feature that will track information
about the call such as the customer, call participants, a timestamp noting the start time of the call, the direction of the
communication, in or outbound, and the resolution code.
Terms used in setting up these communications:
• PSTN: Public switched telephone network is the network of the world's public circuit-switched telephone networks.
• SIP: Session initiation protocol, an open signaling protocol standard that is used to set up phone calls
• TPCC: Third Party Call Control enables an application to control the telephony network to set up calls automatically.
• OWLCS: Oracle WebLogic Communication Services. Offers the TPCC service to Oracle applications and sets up the
calls via SIP integration with the telephony network.
The setup task list Define WebLogic Communication Services Configuration includes four tasks required for the correct
configuration and implementation of CTI. One optional task, separate from the setup task list, is required for implementing
task logging.
You can find information about implementing CTI in the Oracle Sales Cloud Administrator's Guide. Detailed information about
configuring and maintaining WebLogic Communication Services is found in the Oracle WebLogic Communication Services
Administrator's Guide
Configure and Deploy WebLogic Server

• Deploy WebLogic Communication Services: After the Oracle WebLogic communication server is deployed, this
manual task activates the server.
See: Oracle WebLogic Communication Services Administrator's Guide
Integrate Communications Services

• Integrate WebLogic Communication Services with Telephony Network: This manual task integrates communications
within the telephony environment. OWLCS must be configured to interface with the specific characteristics of the
telephony network.
See: Managing Oracle WebLogic Communication Services for CTI Functionality
Specify the Domain and Address

• Register a URL for the telephony gateway or soft switch for SIP domain: This task defines the Server protocol,
defaulted to http, the external server host address, and external server port address. The Associated Modules
777
section is not required for setup. You can also perform this as a manual task using Topology Manager to configure
the address of the SIP Public Switched Telephone Network (PSTN) gateway or SIP soft switch serving the users
within that domain. This address is needed by CTI to correctly form the SIP addresses required by WebLogic
Communication Services. See the link to Configuring PSTN Gateway Address Using Topology Manager: Worked
Example.
Enable Click-to-Dial
• After configuring the server and defining the SIP domain, perform the Enable Click-to-Dial task. This task sets the
value of the profile option Enable Click-to-Dial to 'Yes.'
Call Logging via Tasks

• To initiate the task based logging for CTI, set the profile option Call Interaction Logging Enabled to 'YES.'
Configuring PSTN Gateway Address Using Topology

Manager: Worked Example
This example demonstrates how, during the implementation of the Register URL for the telephony gateway
or soft switch for SIP domain task, you must manually configure the PSTN gateway address by registering
HzCTDPstnGatewayApp to a given environment using Oracle Fusion Topology Registration
These steps configure the address of the SIP Public Switched Telephone Network (PSTN) gateway or SIP soft switch
serving the users within that domain. This address is needed by Click-to-Dial to correctly form the SIP addresses required by
WebLogic Communication Services.
For example: SIP:+1650-555-1212@pstn_gateway.oracle.com;user=phone where pstn_gateway.oracle.com is the SIP domain. The SIP
domain can also be expressed in the format 10.1.1.1 (IP address).
Configuring PSTN using the Topology Manager

1. Sign in to Oracle Sales Cloud as a user that has application implementation consultant and WebLogic
Services administration roles.
2. In Setup and Maintenance, click Register Enterprise Applications from the regional area under Topology
Registration.
3. On the Register Enterprise Applications page, click the plus icon to add an enterprise application. An Add Enterprise
Application dialog box appears.
4. Enter the new application information: Click Search in the Enterprise Application list field. Enter
HzCTDPstnGatewayApp in the name field and click Search.
5. Click OK.
6. Enter the other fields in the Add Enterprise Application dialog box.
Field Value
Name HzCTDPstnGatewayApp

Server Protocol SIP
778
Field Value

This field is ignored by Click-to-Dial. Oracle
WebLogic Communication Service (OWLCS)
always uses the SIP protocol.

External Server Host 10.143.167.91 (Used as an example)

A host name can be used instead of an IP address.

External Server Port 0 (Used as an example)

This field is ignored by Click-to-Dial.

779
Implementing Project Financial Management Define Client Extensions
52 Define Client Extensions
Define Project Extensions
Project Status Change Workflow Enabled Extension

Use the Project Status Change Workflow Enabled Extension to determine whether to call the workflow process when the
project status changes.
Note
Project Status Change Workflow Enabled Extension is currently not available in Oracle Cloud implementations.
The extension is identified by the following items:
Extension Component Name
Body template pjf_ client_ extn_ proj_ status.pkb

Specification template pjf_ client_ extn_ proj_ status.pkh

Package pjf_ client_ extn_ proj_status

Important
Don't change the name of the extension procedure or parameters. Also, don't change the parameter types or
parameter order in the procedure. After you write a procedure, compile it and store it in the database.
Oracle Fusion Projects calls the Project Status Change Workflow Enabled Extension when a change of status is requested for
a project.
When designing Project Status Change Workflow Enabled Extensions, you determine what business rules to apply when a
project status change is selected for a project.
The name of this procedure is Check_Bpel_enabled. Oracle Fusion Projects determines whether to call workflow for a project
status change based on the Enable Workflow option on the project status definition.
Project Status Change Rules Extension

Use the Project Status Change Rules Extension to define rules to determine whether a project status can change.
Note
Project Status Change Rules Extension is currently not available in Oracle Cloud implementations.
780
Body template pjf_ client_ extn_ proj_ status.pkb

Specification template pjf_ client_ extn_ proj_ status.pkh

Package pjf_ client_ extn_ proj_status

Important
Oracle Fusion Projects calls the Project Status Change Rules Extension when a change of status is requested for a project.
When designing Project Status Change Rules Extensions, you determine what business rules to apply when a project status
change is selected for a project.
The name of this procedure is Verify_Project_Status_Change.
Organization Change Rules Extension

Use the Organization Change Rules Extension to build business rules to determine whether an organization change is allowed
for a project and task owning organization, and to define the error messages that are used when the rules are violated.
Note
Organization Change Rules Extension is currently not available in Oracle Cloud implementations.
Oracle Fusion Projects calls the Organization Change Rules Extension during the Change Project and Task Organizations
process, and in the project definition when you change the project and task owning organization.
This table shows the names of the extension components.
Body template pjf_ org_ client_ extn.pkb

Specification template pjf_ org_ client_ extn.pkh

Package PJF_ ORG_ CLIENT_EXTN

Procedure verify_ org_change

781
Important
Project Status Change Approver Extension

Use the Project Status Change Approver Extension to override the internal identifier of the project status change approver.
Note
Project Status Change Approver Extension is currently not available in Oracle Cloud implementations.
By default, the extension returns the internal identifier of the project manager. The default project workflow process calls the
Project Status Change Approver Extension to determine the project approver.
Body template pjf_ client_ extn_ project_ wf.pkb

Specification template pjf_ client_ extn_ project_ wf.pkh

Package pjf_ client_ extn_ project_wf

Important
Don't change the name of the extension procedures or parameters. Also, don't change the parameter types or
parameter order in your procedure. After you write a procedure, compile it and store it in the database.
The Select Project Approver (select_project_approver) procedure is included in the Project Status Change Approver
Extension. This procedure returns the project approver ID to the calling workflow process. You can modify the procedure to
add rules to determine who can approve a project. The default procedure returns the ID of the project manager.
Define Burdening Extensions
Burden Schedule Override Extension

Use the Burden Schedule Override Extension to override the default burden schedule version identifier for transactions
charged to a burdened project.
Note
Burden schedule override extensions are currently not available in Oracle Cloud implementations.
782
The costing processes refer to the Burden Schedule Override Extension to process cost transactions. You can modify the
extension to meet your business rules for assigning burden schedules.
Specification template pjf_ client_ extn_ burden.pkh

Body template pjf_ client_ extn_ burden.pkb

Package PJF_ CLIENT_ EXTN_BURDEN

Procedure override_ rate_rev_id

Important
Burden Summarization Grouping Extension

You can use the Burden Summarization Grouping Extension to control the reporting, accounting and display of burden
transactions. By including certain attributes in the grouping, you can also ensure that the summarized burden transactions are
rolled up to, and reported under, the same resource as the source transactions.
Note
Burden summarization grouping extensions are currently not available in Oracle Cloud implementations.
Specification template pjc_ client_ extn_ burden_ summary.pkh

Body template pjc_ client_ extn_ burden_ summary.pkb

Package PJC_ CLIENT_ EXTN_ BURDEN_ SUMMARY

The CLIENT_GROUPING function returns a VARCHAR2 value which is a concatenated string of the parameter values. You
can customize the function to create the return string using the attributes by which you want to group each transaction. This
string can be used as an additional grouping criterion.
783
The CLIENT_COLUMN_VALUES procedure works in conjunction with the CLIENT_GROUPING function to return NULL for
the parameters that are not used for additional grouping in the CLIENT_GROUPING function. This ensures that the attributes
used for the grouping are also included on the expenditure items created for burden transactions, and therefore impact how
these expenditure items are rolled up in the resource breakdown structures for reporting.
Important
Don't change the name of the extension procedures or parameters. Also, do not change the parameter types or
Burden Cost Calculation Override Extension

Use the Burden Cost Calculation Override Extension to override the default burden amounts calculated for each of the burden
cost codes. The extension is called after the burden amounts are calculated using the latest built multipliers. The extension
then overrides the burden costs using transaction attributes specified in the extension. These amounts are summed to derive
the burdened cost.
Note
Burden cost calculation override extensions are currently not available in Oracle Cloud implementations.
You can use the Burden Cost Calculation Override Extension when:
• You multiply the transaction quantity with a fixed rate instead of multiplying the raw cost with a multiplier. For
example, the number of hours a person has worked multiplied with a fixed rate is used instead of applying multipliers
to the transactions raw cost amount.
• You don't include a specific cost code or choose to override the multiplier. The Burden Cost Calculation Override
Extension can update the multiplier for a cost code to zero so that the cost code is not included for the transaction.
For example, don't apply a specific cost code after the actual cost for the project reaches a specified amount.
• You define a fixed burden rate for a cost code in the descriptive flex field and choose to use this rate for a specific
project or task.
Note
The extension is not called when calculating revenue and invoice amounts or when calculating rates for the Oracle
Fusion Project Integration Gateway or Oracle Fusion Projects Integration for Microsoft Project.
The extension is identified by the following components.
Specification template pjf_ client_ extn_ calc_ burden.pkh

Body template pjf_ client_ extn_ calc_ burden.pkb

Package pjf_ client_ extn_ calc_burden

Function is_ client_ extn_ implemented

784
Procedure override_ burden cost

The API details for the extension component, Function, are as follows:
• API Name: Is_client_extn_implemented
• API Type: Function
• API Purpose: Indicates whether Burden Cost Calculation Override Extension is enabled or not.
• Parameters: None
• Return Values:
◦ Y indicates that the client extension is enabled.
◦ N indicates that the client extension is not enabled. This is the default value hard coded in the function.
The API details for the extension component, Procedure, are as follows:
• API Name: Override_burden_cost
• API Type: Procedure
• API Purpose: Allow you to override the calculated burden cost amounts in PJF_BURDEN_RATE_EXTN table.
• Parameters
Parameter Name Parameter Data Type Description
p_ calling_ module VARCHAR2 Identifies the calling module,

which invokes the extension.
The valid values are:
◦ TEST-EXP: The extension

is called for an expenditure
item in View Burden Cost
Details window.
◦ TEST-STANDARD:
The extension is called
from Test Burden Cost
Calculations Page.
◦ TEST-BUDGET: The
extension is called for
project plan, budget and
forecast in View Burden
Cost Details window.
785
Parameter Name Parameter Data Type Description
◦ BUDGET-PROCESS: The
extension is called during
burdened cost calculation
in project plan, budget and
forecast.
◦ IMPORT-PROCESS: The
extension is called during
burdened cost calculation
for expenditure items that
have burdening on the
same line.
◦ BURDEN-PROCESS: The
extension is called when
Generate Summarized
Burden Transactions
process is run to
create separate burden
expenditure item lines.
p_ current_ run_id NUMBER This is the identifier of the set

of transactions that need to be
processed in a given run.

• Return Values: None
Note
To implement the extension, modify the function to enable the extension and modify the procedure to override
the burden amounts. Don't change the name of the extension procedures or parameters. Also, don't change the
parameter types or parameter order in your procedure. After you write or implement a written procedure, compile
it and store it in the database.
FAQs for Define Expenditure Extensions
How can I create related expenditure items?

When you define a document entry, select the Create related items option. You can create related items for any type of
transactions from third-party applications. The Import and Process Cost Transactions process creates related items based on
the user-defined specifications in the client extension. All related items are associated with a source transaction. Use related
items to process raw cost amount separately from the source transaction raw cost amount.
However, you cannot create related items, if the document entry is associated with allocation, capital interest, and
application-generated summarized burden expenditure transactions.
Note
Expenditure extensions are currently not available in Oracle Cloud implementations.
786
Define Labor Costing Extensions
Labor Costing Extension

Use Labor Costing Extensions to derive raw cost amounts for individual labor transactions. Examples of labor costing
extensions that you may define are:
• Standard cost rate by job
• Capped labor cost rates
• Multiple cost rates per employee
Note
Labor costing extensions are currently not available in Oracle Cloud implementations.
Body template pjf_ client_ extn_ costing.pkb

Specification template pjf_ client_ extn_ costing.pkh

Package PJF_ CLIENT_ EXTN_COSTING

Procedure calc_raw_cost

Important
Parameters
In the following table is information about parameters for this extension:
Parameter Name Description
Transaction type The default value is ACTUAL. Other values are BUDGET
and FORECAST.

Transaction interface identifier Passed in when the transaction type is ACTUAL.

787
Expenditure type class Refers to system linkage function.

Resource assignment identifier Passed in when the transaction type is BUDGET or

FORECAST and when invoked for labor planning
transactions when actual rates are used.

Transaction raw cost The raw cost amount that your procedure calculates is
assigned to the x_raw_cost parameter. Leave this value
blank to use the standard costing method which uses
the employee's hourly cost rate. If you pass a value to
this parameter, Oracle Fusion Projects calculates the
raw cost rate of the transaction using the x_ raw_ cost
parameter value divided by the number of hours.

Transaction currency Currency in which the transaction is incurred.

Status Use the x_status parameter to handle error conditions

for your procedure. This parameter indicates the
processing status of your extension as shown:
• x_status is 0: The extension executed successfully.
• x_status is less than 0: An application error

occurred and the process did not complete.
• x_status is greater than 0: An application error

occurred and the process did not complete.
Error details An application error occurs if the extension fails to return

a value for the raw cost rate or amount. Oracle Fusion
Projects writes an error message to the process log file.

Cost rate Parameter returned by the extension.

You can use Labor Costing Extensions to implement unique costing methods other than the standard method, which
calculates raw cost using the number of hours multiplied by the employee's hourly cost rate. For example, you may want to
calculate the raw cost using a capped labor rate for specific employees.
Oracle Fusion Projects processes Labor Costing Extensions before calculating standard raw cost amounts. If Oracle Fusion
Projects encounters a Labor Costing Extension that derives the raw cost amount of a labor transaction, it skips the standard
raw cost calculation section for that transaction.
Overtime Calculation Extension

Use the Overtime Calculation Extension to define your own rules to implement company-specific overtime calculation policies.
788
Note
Overtime calculation extensions are currently not available in Oracle Cloud implementations.
Body template pjc_ client_ extn_ calc_ overtime.pkb

Specification template pjc_ client_ extn_ calc_ overtime.pkh

Package pjc_ client_ extn_ calc_overtime

Oracle Fusion Projects provides sample business rules in the Overtime Calculation Extension. You can use the sample to
understand the extension, and then make appropriate changes to meet your business needs.
The sample business rules in the extension calculate overtime costs and charge them to an indirect project other than the
project where the labor is charged.
Note
If you want to charge overtime to the project where the labor is charged, consider creating items using the
Related Transaction Extension.
Points to consider when implementing the Overtime Calculation Extension:
• Define all overtime expenditure types with an end date.

• Base automatic overtime calculation on weekly overtime rules. Oracle Fusion Projects is designed to process weekly
time cards. All expenditure item dates on a time card must be within the expenditure week ending date of the time
card. Therefore, automatic overtime calculation is most easily performed based on weekly overtime rules.
The sample business rules in the Overtime Calculation Extension follows these steps to process overtime:
• Determines all employees and corresponding weeks which may include new overtime to process. The Overtime
Calculation Extension calculates and creates overtime only for employees with time cards processed in the Import
and Process Cost Transactions process that calls the Overtime Calculation Extension. These employees and weeks
are identified by the request ID of the straight time expenditure items that are costed before the Overtime Calculation
Extension is called.
• Sums the hours required to calculate overtime for identified employees and weeks. The standard Overtime
Calculation Extension sums the total hours for the week and the total hours for each day of the week, relying on the
time card entry validation rule that all labor expenditure item dates must be within the expenditure week ending date
of the time card.
• Calculates overtime hours based on the hours worked, the employee's labor costing rule, and other criteria you
specify. The standard Overtime Calculation Extension calculates overtime for an employee and a week based on the
employee's labor costing rule.
• Creates overtime expenditure items for each type of overtime for which the employee is eligible. The overtime item is
charged to the overtime project and appropriate overtime task that is specified in the Overtime Calculation Extension
using the overtime expenditure type defined for the employee's labor costing rule. The expenditure item date is set to
the week ending date.
789
The extension uses the same batch name as the source straight time expenditure items to create the new overtime
expenditure items.
• Lists overtime transactions created by this extension in the Import and Process Cost Transactions Execution Report.
The new overtime items are costed after the Overtime Calculation Extension completes, within the Costing stage in the Import
and Process Cost Transactions process.
Define Borrowed and Lent Extensions
Provider and Receiver Organizations Override Extension

Use this client extension to enforce cross-charge rules at a higher level in the organization hierarchy than the level at which
you assign resources and projects. Doing so provides a single place for you to enforce and maintain your business rules in all
organizations in your enterprise.
Note
Provider and receiver organizations override extensions are currently not available in Oracle Cloud
implementations.
Body template pjc_ client_ extn_ cc_ident.pkb

Specification template pjc_ client_ extn_ cc_ident.pkh

Package pjc_ client_ extn_cc_ident

Procedure override_ prvdr_recvr

Important
The application identifies cross-charged transactions based on the provider and receiver organizations for the transaction. It
derives default values for these organizations as follows:
• Provider organization: The expenditure organization or nonlabor resource organization for usage transactions.
• Receiver organization: The organization that owns the task or project to which the transaction is charged.
To override the cross-charge identification, code this extension to use a higher level in the organization hierarchy to derive the
appropriate provider and receiver organizations and then determine if a transaction is a cross-charge transaction.
790
This extension is called by the Identify Cross-Charge Transactions process. If you use the Borrowed and Lent Accounting
cross-charge processing method, the application automatically calls the Identify Cross-Charge Transactions process as part
of the Distribute Borrowed and Lent Amounts process. However, if you use the Intercompany Billing cross-charge processing
method, you must manually run the Identify Cross-Charge Transactions process.
Cross-Charge Processing Method Override Extension

Use the Cross-Charge Processing Method Override Extension to have custom business rules that help you identify how to
process cross-charged transactions.
Note
Cross-charge processing method override extensions are currently not available in Oracle Cloud implementations.
Use this extension to:
• Exclude certain cross-charged transactions from cross-charge processing
• Change the cross-charge processing method, such as from Intercompany Billing to Borrowed and Lent Accounting
Note
Use this extension only on cross-charged transactions.
Body template pjc_ client_ extn_ cc_ident.pkb

Specification template pjc_ client_ extn_ cc_ident.pkh

Package pjc_ client_ extn_cc_ident

Procedure override_ cc_ processing_ method

Important
The system validates the value returned for the cross-charge code to ensure that it meets the following rules:
Cross-Charge Transaction Type Allowed Processing Methods
Within a business unit Borrowed and Lent Accounting

791
Cross-Charge Transaction Type Allowed Processing Methods
Between business units Borrowed and Lent Accounting

Intercompany Billing

Between legal entities Intercompany Billing

This extension is called by the Identify Cross-Charge Transactions process. If you use the Borrowed and Lent Accounting
cross-charge processing method, the application automatically calls the Identify Cross-Charge Transactions process as part
of the Distribute Borrowed and Lent Amounts process. However, if you use the Intercompany Billing cross-charge processing
method, you must manually run the Identify Cross-Charge Transactions process.
The Identify Cross-Charge Transactions process:
1. Identifies the transaction as a cross-charged transaction.
2. Determines the cross-charge processing set method based on the cross-charge options.
3. Calls the extension to override the cross-charge processing method.
Internal Payables Invoice Attribute Override Extension

Use the Internal Payables Invoice Attribute Override Extension to override the default expenditure type and expenditure
organization attributes for intercompany and interproject invoices that are created in Oracle Fusion Receivables.
Note
Internal payables invoice attribute override extensions are currently not available in Oracle Cloud implementations.
The Update Invoice Details from Receivables process calls the Internal Payables Invoice Attribute Override Extension as it
creates Oracle Fusion Payables invoices for intercompany and interproject contracts.
Note
Use this extension only if you want to override the receiver expenditure organization and receiver expenditure type
on the Oracle Fusion Payables invoice. The source of the receiver expenditure organization and expenditure type
is the intercompany or interproject contract.
The extension is identified by the following items.
Body template pjb_ cc_ ap_ inv_ client_ extn.pkb

Specification template pjb_ cc_ ap_ inv_ client_ extn.pkh

Package pjb_ cc_ ap_ inv_ client_extn

792
Procedure override_ exp_ type_exp_org

This billing extension can derive the receiver expenditure type and receiver expenditure organization based on the parameters
you enter.
Parameters
Information about parameters for this billing extension are in the table below.
p_ internal_ billing_type Internal billing type

Valid values are:
• PA_IC_INVOICES (Intercompany contract)
• PA_IP_INVOICES (Interproject contract)
p_contract_id Contract ID for the Oracle Fusion Receivables invoice.

p_ contract_ line_id Contract line ID for the Oracle Fusion Receivables

invoice.

p_ receiver_ project_id Receiver project ID for the Oracle Fusion Payables

invoice.

p_ receiver_ task_id Receiver task ID for the Oracle Fusion Payables invoice.

p_ invoice_ number Invoice number from the pjb_ invoice_header table.

p_ draft_ invoice_ line_num Invoice_ line_num from pjb_ invoice_line.

p_invoice_date Invoice date

p_ ra_ invoice_ number Oracle Fusion Receivables invoice number. The

invoice number is either user-entered or created by the
application, as defined in the implementation options.

Refer to ra_ invoice_number from pjb_ invoice_ headers

793
p_ provider_ org_id Provider business unit ID

p_ receiver_ org_id Receiver project organization ID

p_ cc_ ar_invoice_id Customer transaction ID created in ra_ customer_ trx_

all.customer_ trx_id

p_ cc_ ar_ invoice_ line_num Line number from ra_ customer_ trx_ lines_ all.line_
number.

p_ contract_ line_ customer_id Customer ID on the bill plan associated with the contract
line.

p_vendor_id Supplier ID (poz_ suppliers. vendorid)

p_ vendor_ site_id Supplier site ID (poz_ supplier_ sites_ all_ m.vendor_

site_id)

p_ expenditure_ type Expenditure type defined on the contract line internal

attribute.

p_ expenditure_ type_id Expenditure type ID defined on the contract line internal

attribute.

p_ expenditure_ organization_ id Expenditure organization defined on the contract line

internal attribute.

x_ expenditure_ type_id Expenditure type ID returned by the extension.

x_ expenditure_ type Expenditure type returned by the extension.

x_ expenditure_ organization_ id Expenditure organization ID returned by the extension.

x_status Return status of the extension.

x_Error_Stage Error stage returned by the extension.

794
X_Error_Code Error code returned by the extension.

Define Transfer Pricing Extensions
Transfer Price Determination Extension

Use the Transfer Price Determination Extension to derive the transfer price for a cross-charge transaction. If a price is not
derived, the application uses the standard transfer price process.
Note
Transfer price determination extensions are currently not available in Oracle Cloud implementations.
The Distribute Borrowed and Lent Amounts process and Generate Invoices process call the extension before calling the
standard transfer price determination process.
Body template pjc_ client_ extn_ cc_tp.pkb

Specification template pjc_ client_ extn_ cc_tp.pkh

Package PJC_ CLIENT_ EXTN_CC_TP

Procedure determine_ transfer_ price

Important
The application validates that you provided a value for only one of the following output audit parameters:
• x_bill_rate
• x_bill_markup_percentage
If a value is not valid, a rejection message appears in the process execution report.
The extension procedure specifies a transfer price for the transaction being processed. If this extension returns a valid value
for the transfer price, Oracle Fusion Projects uses that value as the transfer price instead of computing the transfer price.
795
Transfer Price Override Extension

Use the Transfer Price Override Extension to override the price derived by the standard transfer price process.
Note
Transfer price override extensions are currently not available in Oracle Cloud implementations.
The Distribute Borrowed and Lent Amounts process and Generate Invoices process call the extension after calculating the
transfer price based on the transfer price rules and schedules.



Procedure override_ transfer_ price

Important
The application validates that you provided a value for only one of the following output audit parameters:
• x_bill_rate
• x_bill_markup_percentage
If a value is not valid, a rejection message appears in the process execution report.
The extension procedure overrides the transfer price for a transaction.
Transfer Price Currency Conversion Override Extension

Use this extension to override the default attributes used to convert the transfer price from the transaction currency to the
functional currency.
Note
Transfer price currency conversion override extensions are currently not available in Oracle Cloud
implementations.
796
The Distribute Borrowed and Lent Amounts process and Generate Invoices process call the extension after the processes
calculate the transfer price. The cross-charge transaction implementation options for the business unit determine the default
conversion attributes.



Procedure override_ curr_ conv_ attributes

Important
Oracle Fusion Projects validates that the values returned by the extension meet all conversion requirements.
Define Project Billing Extensions
Billing Extension Components: How They Work Together

Implement a billing extension to define a set of company-specific business rules that create automatic invoice and revenue
events. To use the billing extension functionality, create a billing extension and assign it to a bill plan or revenue plan.
Note
General Information
• Order
◦ If multiple billing extensions are assigned to a bill or revenue plan, enter a numeric value to determine when this
extension is called. Oracle Fusion Project Billing calls billing extensions in ascending order.
• Procedure
◦ To implement a company specific rule for creating automatic invoice and revenue events, you must first write
a PL/SQL procedure that calculates the event amount. Enter the name of the PL/SQL procedure on the billing
extension page.
797
• Transaction Independent
◦ Transaction independent billing extensions are called once for each contract line or associated project,
depending on the extension calculation level defined in the bill or revenue plan. They are usually defined to
import transactions from external applications. If the billing extension is for invoices, the extension is called
during the Generate Invoice process before the invoice preprocessor, which creates billing transactions. If the
billing extension is for revenue, the extension is called during the Generate Revenue process before revenue
transactions are processed.
Note
If you do not enable the transaction independent feature of a billing extension, it will be transaction
dependent. Transaction dependent billing extensions are called only if billable expenditure items and
events exist that need to be processed.
Call Process
The call process determines whether to call the PL/SQL procedure that calculates the amount during invoice generation or
revenue generation.
Note
If you require a procedure to create both automatic invoice and revenue events, you must create two separate
billing extensions.
Call Location
Select a location (time) within the invoice or revenue generation program where the billing extension is called. The predefined
locations are:
• Before billing transaction creation
◦ Select this location if you want to call the billing extension before any recognizing revenue or calculating invoice
amounts for the contract line or project and contract line combination.
◦ An example of a requirement for which you may want to use this call location is if you want to place all unbilled,
unpaid supplier invoice items on hold so they are not billed; and to release the billing hold on any unbilled, paid
supplier invoice transactions that are on hold. You can then bill the paid supplier invoice items during standard
invoice processing.
• After invoice and revenue distribution lines are created
◦ Select this option to call the billing extension after the revenue and invoice processing is complete.
◦ Examples of requirements for which you may want to use this call location are if you want to notify a project
manager when an invoice of a certain amount is created, or if you want to create a fixed fee event that is
dependent on the total transaction amount billed on the invoice.
• Before invoice deletion
◦ Select this option if you want to call the billing extension before deleting invoice distribution lines. This call
location is only valid for invoice billing extensions.
798
Required Input
Specify whether an amount or percentage is required for entry when you assign the billing extension to a bill or revenue plan.
When you define a bill or revenue plan that uses the billing extension, you must enter a specific amount or percentage that is
used when calculating the automatic invoice or revenue event.
Default Event Type

Specify an event type to determine the default event attributes to use for events created by the billing extension. You can
override the attributes for default event type in your procedure.
Default Plan Type

Specify a default financial cost plan type to use for calculations that use budgeted amounts. If the value is not provided for a
cost plan type, but is needed for the calculation, the process will error. You can override the attributes for default plan in your
procedure.
Related Topics
Planning Your Billing Extension Implementation: Explained

You must carefully design billing extensions before implementing them in Oracle Fusion Projects. Careful planning of your
billing extensions helps to ensure that you are calculating and generating revenue and invoices according to your company-
specific rules.
Note
Design Billing Extensions

Carefully plan the definition of billing extensions before you begin writing them. Typically, the logic of your billing extensions
are dependent on your company's implementation of Oracle Fusion Projects. Consider the following issues when designing
your billing extensions:
• Are you calculating a revenue amount or an invoice amount? Are the amounts generated during revenue generation
or invoice generation?
• How are the amounts calculated? What are the inputs to the calculation?
• How are the inputs derived?
• How are the amounts processed:
◦ For reporting purposes?
◦ For accounting purposes?
◦ For invoicing?
• How are the attributes of the automatic event set: event type, event organization, event description, completion
date?
799
• Under what conditions is this calculation used? What types of contracts? What types of billing terms?
• How is the billing extension processed for adjustments? Adjustments are defined as revenue credits or invoice credit
memos, based on other transactions.
• Can this billing extension be called with other billing extensions assigned to the same bill plan or revenue plan? If so,
what is the dependency and order of your billing extensions?
• What is the exception handling if some input values cannot be found?
• How is the logic affected if the inputs change over time?
• Is there a limit on the amount calculated? If so, what is the logic?
Once you answer these questions, you should have the appropriate information to define a billing extension in Oracle Fusion
Projects and to document the functional specifications for your technical resource to use in writing the PL/SQL procedure.
Write and Store PL/SQL Procedures

After you design your billing extensions, write the PL/SQL procedures that define the logic of the billing extensions.
After you write your procedures, store them in the database and test them to ensure that your billing extension logic works as
expected.
Define Billing Extensions

Define your billing extensions that specify the PL/SQL procedure name and additional information for Oracle Fusion Projects
to use when processing billing extensions.
You use the Create Billing Extensions page to define billing extensions.
Note
This step assumes that an event type has already been defined for the default event type.
Assign Billing Extensions to Invoice Methods and Revenue Methods

Assign billing extensions to the appropriate invoice methods and revenue methods. Your contract users will select these
invoice methods and revenue methods on bill plans and revenue plans. The assigned billing extensions are copied from the
methods to the plans.
Billing Extension
Use the Billing Extension to implement company-specific business rules to automatically create invoice or revenue events.
Billing extensions automatically calculate summary invoice or revenue amounts during invoice or revenue generation.
Note
To use the billing extension functionality, you must implement a billing extension and assign it to either an invoice method or
a revenue method. You can assign a billing extension to more than one invoice or revenue method. When you specify the
invoice or revenue method on a bill or revenue plan, the billing extensions assigned to that method are copied to the plan.
Depending on the definition of the assigned billing extension, you might be required to specify a percentage or amount to use
as input when calculating the event amount.
The extension is defined by the following items.
800
Body template pjb_ bill_ extn_ sample_pkg.pkb

Specification template pjb_ bill_ extn_ sample_ pkg.pkh

Package pjb_ bill_ extn_ sample_pkg

Procedure SampleExtn

Your extension procedure can call other procedures or views. These other procedures or views can be predefined or you can
write your own.
Parameters
p_bill_plan_id Bill plan or revenue plan identifier from pjb_ bill_plans_b

or okc_ k_lines_b.

p_contract_id Contract identifier from okc_ k_ headers_ all_b.

p_ contract_ line_id Contract line identifier from okc_ k_lines_b.

p_linkage_id Project and contract linkage identifier from pjb_ cntrct_

proj_ links. Pass the value when the calculation level
code is PROJECT_ CONTRACT_ LINKAGE.

p_ linked_ project_id Project identifier from pjb_ cntrct_ proj_links linked to the
contract. Pass the value when the calculation level code
is PROJECT_ CONTRACT_ LINKAGE.

p_ linked_ task_id Task identifier from pjb_ cntrct_ proj_links linked to the
contract. Pass the value when the calculation level code
is PROJECT_ CONTRACT_ LINKAGE.

801
p_ calling_ process Calling process for the billing extension. Valid values are:

• REV (for revenue)
• INV (for invoice)
p_ calculation_ level Calculation level code for the billing extension. Valid
values are:
• LINE
• PROJECT_CONTRACT_LINKAGE
p_ bill_frm_date Invoice or revenue from date.

p_bill_to_date Invoice or revenue to date.

p_amt Invoice amount or revenue amount. This is

generally used when the extension calling place is
AFTER_DRAFT.
p_percent Percentage

p_ assignment_ detail_id Assignment detail identifier pjb_ assignment_ details.

p_extension_id Billing extension identifier obtained from table pjb_

billing_ extensions.

p_ assignment_id Assignment identifier

p_ event_type_id Event type identifier from pjb_ event_ types_b.

p_ default_ event_ type_ description Event type description identifier from pjf_ event_
types_tl.

p_ cost_ fin_plan_type Cost financial plan type identifier. This is generally used
when the invoice or revenue method is Percent Spent.
p_invoice_id Invoice identifier

802
p_request_id Request identifier

p_ cont_ curr_code Contract currency code

p_ ledger_ curr_code Ledger currency code

X_ return_status Status of the procedure. Valid values are:

• S (for success)
• E (for expected error)
• U (for unexpected error)
X_msg_count Message count. Valid values are greater than or equal to

zero.

X_msg_data Actual message when there is an exception.

Implementing Billing Extensions for Your Company

To implement your company-specific billing methods, you first design and write rules to calculate billing amounts using PL/
SQL procedures. You then enter the billing extension definition in Oracle Fusion Project Financial Management to specify
additional information (such as the procedure name to call) that is used by the revenue and invoice programs to process the
extension.
You define billing extensions in the Create Billing Extensions page, and specify the following items:
• The name of the procedure to call.

• Whether the procedure is called during invoicing or revenue recognition.
• The call location within the invoice or revenue program where the extension is called.
• Whether an amount or percentage is required when the billing extension is assigned to a bill plan or revenue plan.
• The budget type to use as input for calculations that use budgeted amounts.
The values entered in the Create Billing Extensions page can be used in your billing extension procedure by accessing the
table pjb_billing_extensions. The values entered in the Billing Extensions tab of the Create Bill Plan or Create Revenue Plan
page can also be used in your billing extension procedure by accessing the table pjb_assignment_details.
Processing
When you run the revenue or invoice processes, the application looks for active billing extensions assigned to a bill plan or
revenue plan. When a billing extension is found, the processes read the billing extension definition and call the appropriate
procedure. If there are multiple active billing extensions assigned to a bill or revenue plan, the application calls the extensions
by the order entered on the Create Billing Extension page, and then by the order of the assignment to the bill or revenue plan.
Automatic Events
803
Your billing extension calculates revenue and invoice amounts and creates one or more automatic events. Oracle Fusion
Project Financial Management processes these events as it does other manually entered events. You can store audit
amounts and references for these events in the audit amount and reference columns of the Events table.
You can increase or decrease revenue and invoice amounts for automatic events. You can also place automatic events on
invoice or revenue hold indefinitely, and remove the holds later.
Automatic events are either only applicable to invoicing or only applicable to revenue recognition, but not both.
The billing extension uses the public procedure MyPackageName.insert_event to automatically create events.
Related Topics
• Invoice and Revenue Method Components: How They Work Together
Internal Payables Invoice Attribute Override Extension

Use the Internal Payables Invoice Attribute Override Extension to override the default expenditure type and expenditure
organization attributes for intercompany and interproject invoices that are created in Oracle Fusion Receivables.
Note
Internal payables invoice attribute override extensions are currently not available in Oracle Cloud implementations.
The Update Invoice Details from Receivables process calls the Internal Payables Invoice Attribute Override Extension as it
creates Oracle Fusion Payables invoices for intercompany and interproject contracts.
Note
Use this extension only if you want to override the receiver expenditure organization and receiver expenditure type
on the Oracle Fusion Payables invoice. The source of the receiver expenditure organization and expenditure type
is the intercompany or interproject contract.
The extension is identified by the following items.
Body template pjb_ cc_ ap_ inv_ client_ extn.pkb

Specification template pjb_ cc_ ap_ inv_ client_ extn.pkh

Package pjb_ cc_ ap_ inv_ client_extn

Procedure override_ exp_ type_exp_org

This billing extension can derive the receiver expenditure type and receiver expenditure organization based on the parameters
you enter.
Parameters
804
p_ internal_ billing_type Internal billing type

Valid values are:
• PA_IC_INVOICES (Intercompany contract)
• PA_IP_INVOICES (Interproject contract)
p_contract_id Contract ID for the Oracle Fusion Receivables invoice.

p_ contract_ line_id Contract line ID for the Oracle Fusion Receivables

invoice.

p_ receiver_ project_id Receiver project ID for the Oracle Fusion Payables

invoice.

p_ receiver_ task_id Receiver task ID for the Oracle Fusion Payables invoice.

p_ invoice_ number Invoice number from the pjb_ invoice_header table.

p_ draft_ invoice_ line_num Invoice_ line_num from pjb_ invoice_line.

p_invoice_date Invoice date

p_ ra_ invoice_ number Oracle Fusion Receivables invoice number. The

invoice number is either user-entered or created by the
application, as defined in the implementation options.

Refer to ra_ invoice_number from pjb_ invoice_ headers

p_ provider_ org_id Provider business unit ID

p_ receiver_ org_id Receiver project organization ID

p_ cc_ ar_invoice_id Customer transaction ID created in ra_ customer_ trx_

all.customer_ trx_id

805
p_ cc_ ar_ invoice_ line_num Line number from ra_ customer_ trx_ lines_ all.line_
number.

p_ contract_ line_ customer_id Customer ID on the bill plan associated with the contract
line.

p_vendor_id Supplier ID (poz_ suppliers. vendorid)

p_ vendor_ site_id Supplier site ID (poz_ supplier_ sites_ all_ m.vendor_

site_id)

p_ expenditure_ type Expenditure type defined on the contract line internal

attribute.

p_ expenditure_ type_id Expenditure type ID defined on the contract line internal

attribute.

p_ expenditure_ organization_ id Expenditure organization defined on the contract line

internal attribute.

x_ expenditure_ type_id Expenditure type ID returned by the extension.

x_ expenditure_ type Expenditure type returned by the extension.

x_ expenditure_ organization_ id Expenditure organization ID returned by the extension.

x_status Return status of the extension.

x_Error_Stage Error stage returned by the extension.

X_Error_Code Error code returned by the extension.

806
Labor Billing Extension

The Labor Billing Extension allows you to derive labor billing amounts for individual labor transactions.
Note
Labor billing extensions are currently not available in Oracle Cloud implementations.
You can use the labor billing extension to implement unique labor billing methods. Some examples of how you can use the
labor billing extension are to:
• Bill overtime premium hours at cost.
• Bill based on volume of work performed.
The Labor Billing Extension is called during the invoice or revenue generation process to determine labor revenue and billing
amounts.
The extension is defined by the following items:
Body template pjb_ client_ extn_ billing.pkb

Specification template pjb_ client_ extn_ billing.pkh

Package pjb_ client_ extn_billing

Procedure Calc_ Labor_ Bill_Amount

Important
Do not change the name of the extension procedures or parameters. Also, do not change the parameter types or
Parameters
p_ transaction_ type Varchar2

Valid values are:
• ACTUAL (default value)
• FORECAST
807
p_contract_id Number

p_ expenditure_ item_id Number

x_amount Number

No value is passed in to the x_amount parameter. Do
not expect an amount in this parameter when you create
calculations in the extension.

The billing extension must assign a value to the x_
amount parameter or else the extension will be ignored
by the calling program.

x_ bill_ rate_flag Varchar2

Return one of the following values as the x_bill_rate_flag
parameter value to specify if the amount that you have
derived is based on a bill rate or a percent markup:
• B (specifies bill rate)
• null or value other than B (specifies markup)
If you specify that your amount is based on a bill rate,

Oracle Fusion Projects populates the bill rate of the
expenditure item by dividing the bill amount by the
number of hours. If you specify that your amount is a
markup, Oracle Fusion Projects does not set the bill
rate.
x_ bill_ trans_ currency_code Varchar2

x_ bill_ txn_bill_rate Number

x_ markup_ percentage Number

If you specify that your amount is based on markup,
populate x_ markup_ percentage with the markup
percentage amount, so that the expenditure item record
will contain accurate data.

x_ rate_ source_id Number

x_ return_status Varchar2

808
x_msg_count Number

x_msg_data Varchar2

Oracle Fusion Projects uses the labor billing extension for rate-based invoice method classifications or rate-based and as-
incurred revenue method classifications during the invoice or revenue generation process. During processing, if Oracle
Fusion Projects encounters a transaction that has a derived bill amount from a labor billing extension, it skips the standard bill
amount and rate calculation section of the revenue generation process for that transaction.
Design Issues
Consider the following design issues for labor billing extensions:
• What are the conditions and circumstances in which you cannot use the standard, rate-based invoice and revenue
method classifications supported by Oracle Fusion Projects?
• How are the invoice and revenue amounts calculated in these cases?
• How do you identify labor transactions that meet these conditions?
• How do you store rates and other information that your calculations may require? How are the rates and other
information maintained?
• What are the exception conditions for your labor billing extension? What is the exception handling if you cannot find a
rate that should exist?
Nonlabor Billing Extension

The Nonlabor Billing Extension enables you to derive billing amounts for individual nonlabor transactions.
Note
Nonlabor billing extensions are currently not available in Oracle Cloud implementations.
You can use the Nonlabor Billing Extension to implement unique nonlabor invoice methods or revenue methods. Some
examples of how you can use the Nonlabor Billing Extension are for:
• A tiered pricing method

• External application rate derivation
The Nonlabor billing extension procedure Oracle provides can be called during either the invoice or revenue generation
process to determine the nonlabor invoice or revenue amounts.
Body template pjb_ client_ extn_ billing.pkb

Specification template pjb_ client_ extn_ billing.pkh

809
Package pjb_ client_ extn_billing

Procedure Calc_ NLBR_ Bill_Amount

Important
Parameters
Information about parameters for this client extension are below.
Bill Rate
Return one of the following values as the x_bill_rate_flag parameter value to specify if the amount that you have derived is
based on a bill rate or a percent markup:
• B (specifies bill rate)
• null or value other than B (specifies markup)
If you specify that your amount is based on a bill rate, Oracle Fusion Projects populates the bill rate of the expenditure item by
dividing the bill amount by the number of hours. If you specify that your amount is a markup, Oracle Fusion Projects does not
set the bill rate.
Status
Use the x_status parameter to handle error conditions for your procedure. This parameter indicates the processing status of
your extension as described in the following table.
Status Description
x_status = 0 The extension executed successfully.

x_status < 0 An Oracle error occurred and the process did not
complete. Oracle Fusion Projects writes an error
message to the process log file and rolls back the
transactions processed for the entire project.

x_status > 0 An application error occurred. Oracle Fusion Projects

writes a rejection reason to PA_ EXPENDITURE_
ITEMS.REV_ DIST_ REJECTION_ CODE and does not
mark items as revenue distributed. You can review the
rejection reason in the revenue generation exception
report.

810
Oracle Fusion Projects uses nonlabor billing extensions for rate-based invoice method classifications or rate-based and as-
incurred revenue method classifications during invoice or revenue generation. During processing, if Oracle Fusion Projects
encounters a transaction that has a derived bill amount from a nonlabor billing transaction, it skips the standard bill amount
and rate calculation section of the invoice or revenue process for that transaction.
Design Issues
Consider the following design issues for nonlabor billing extensions:
• What are the conditions and circumstances in which you cannot use the standard, rate-based invoice and revenue
method classifications supported by Oracle Fusion Projects?
• How are the invoice and revenue amounts calculated in these cases?
• How do you identify nonlabor transactions that meet these conditions?
• How do you store rates and other information that your calculations require? How are the rates and other information
maintained?
• What are the exception conditions for your nonlabor billing extension? What is the exception handling if you cannot
find a rate that should exist?
Output Tax Extension

You set up a hierarchy for Oracle Fusion Projects in the application tax options of Oracle E-Business Tax. The Generate
Invoice process uses the Application Tax Options hierarchy to determine the default tax classification codes on invoice lines.
The Output Tax billing extension is one of the default tax options in the Application Tax Options hierarchy.
Note
Output tax extensions are currently not available in Oracle Cloud implementations.
The Generate Invoice process calls the Output Tax extension if it does not find the default tax classification code from the
other tax options you defined in the application Tax Options hierarchy. You can use the extension to satisfy your business
rules in assigning the default tax classification code for invoice lines.
The name for this procedure is get_tax_codes. This procedure assigns a tax classification code to an invoice line.
Body template pjb_ client_ extn_ output_ tax.pkb

Specification template pjb_ client_ extn_ output_ tax.pkh

Package pjb_ client_ extn_ output_tax

Procedure get_tax_codes

811
Important
Parameters
p_Contract_Id Contract identifier, Number

p_Customer_Id Customer identifier, Number

p_ bill_ to_ site_use_id Bill-to Site identifier, Number

p_ ship_ to_ site_use_id Ship-to Site identifier, Number

p_ledger_id Ledger, Number

p_ expenditure_ item_id Expenditure item, Number

p_event_id Event, Number

p_line_type Default value is Null, Number

x_ output_ tax_code Tax ID

x_ return_status Return status of the procedure. Valid values are:

• S (Successful)
• E (Error)
Varchar2
x_msg_count Message count. Valid values are:

• >=0 (Greater than zero)
Number
812
x_msg_data Actual message in case of any errors. Default value is

Null.

Varchar2

Receivables Transaction Type Extension

The Receivables Transaction Type Extension enables you to determine the receivables transaction type when you transfer
invoices to Oracle Fusion Receivables.
Note
Receivables transaction type extensions are currently not available in Oracle Cloud implementations.
Oracle Fusion Projects calls the Receivables Transaction Type Extension during the Transfer Invoices to Oracle Fusion
Receivables process.
Body template pjb_ client_ extn_ inv_ transfer.pkb

Specification template pjb_ client_ extn_ inv_ transfer.pkh

Package pjb_ client_ extn_ inv_transfer

Procedure get_ ar_trx_type

Important
Parameters
813
p_Contract_Id Contract identifier, Number

Corresponds to column CONTRACT_ID in the OKC_ K_
HEADERS_ ALL_B table.

p_Invoice_Num Invoice number

Corresponds to column INVOICE_NUM in the PJB_
INVOICE_ HEADERS table.

p_ Invoice_Class Invoice class, Varchar2

Valid values are:
• INVOICE (Regular invoice)
• CREDIT_MEMO (Crediting invoice)
• WRITE_OFF (Write-off invoice)
• CANCEL (Canceling invoice)
p_ Contract_ Curr_Inv_Amt Sum of invoice amount in contract currency, Number

Corresponds to column CONTRACT_ CURR_INV_AMT
in the PJB_ INVOICE_LINES table.

p_ Contract_ Curr_Code Contract currency code, Varchar2

Corresponds to column Contract_ Currency_code in the
PJB_ INVOICE_ HEADERS table.

p_ Inv_Curr_Code Invoice currency code, Varchar2

Corresponds to the column Invoice_ Currency_code in
the PJB_ INVOICE_ HEADERS table.

p_ Inv_ Curr_Inv_amt Sum of invoice amount in invoice currency, Number

Corresponds to column Inv_ Curr_Line_Amt in the PJB_
INVOICE_ LINES table.

p_ Ar_ trx_type_Id Transaction Type ID, Number

Corresponds to column CUST_ TRX_TYPE_ID in the
RA_ CUST_ TRX_ TYPES table.

814
X_ ar_ trx_type_id Transaction type ID, Number

x_ return_Status Return status of the procedure, Varchar2

Valid values are:
• S (Successful)
• E (Error)
x_msg_count Message count, Number

Valid values are greater than zero.

X_msg_data Actual message when an error exists, Varchar2

Default value is Null.

X_ Validate_ Trx_Type Valid values are:

• Y (Yes)
• N (No)
Receivables Transaction Type Extension Validation Options:

Critical Choices
Select one of the following values as the validation option in the Receivables Transaction Type extension:
• Yes
• No
Note
Receivables transaction type extensions are currently not available in Oracle Cloud implementations.
Yes
Select Yes when you are ready to validate and transfer the invoice data to Oracle Fusion Receivables.
No
Select No when the invoices are generated in Oracle Fusion Project Billing from transactions fully invoiced and migrated from
a different source application and are not to be reported as open receivables in Oracle Fusion Receivables.
815
The No option instructs the Transfer Invoice Details to Receivables process to bypass the receivables transaction type
validation in Oracle Fusion Project Billing. Define the receivables transaction type to bypass the open receivable validation in
the automatic invoice process in Oracle Fusion Receivables.
Note
You cannot reverse or adjust the receivables transaction type for invoices already sent to Oracle Fusion
Receivables. Ensure that you select the correct validation option before you transfer invoices to Oracle Fusion
Receivables.
FAQs for Define Project Billing Extensions

What's the difference between transaction dependent and transaction independent billing
extensions?
Transaction dependent billing extensions are only executed when other transactions are processed. Transaction dependent
billing extensions are called only if billable expenditure items and events exist that need to be processed. For example, a
transaction dependent billing extension is not called when there are new transactions set to nonbillable status that are not
processed during revenue or invoice generation.
Transaction independent billing extensions are executed for each contract with an active billing assignment, even if there are
no transactions to process. This type of billing extension relies on input other than billable transactions on a contract.
Note
Transaction independent billing extensions are processed every time you generate revenue or invoices.
Note
Project billing extensions are currently not available in Oracle Cloud implementations.
816
Implementing Project Financial Management Other Common Setup and Maintenance Tasks
53 Other Common Setup and Maintenance Tasks
Define Transactional Business Intelligence

Configuration
Define Transactional Business Intelligence Configuration:

Highlights
Configure transactional business intelligence for ad hoc reporting. Setup includes making flexfields available for use in
analytics and defining currency settings.
Use the Define Transactional Business Intelligence Configuration task list in the Setup and Maintenance work area.
Performing the Tasks

• For details about the Define Transactional Business Intelligence Configuration tasks, refer to the Oracle Cloud:
Administering Transactional Analyses guide.
See: Functional Setup Tasks for Transactional Business Intelligence
Access to Person Data

Assigning Security Profiles to Job Roles for Oracle Fusion Transactional Business
Intelligence Users: Explained
Users of Oracle Fusion Transactional Business Intelligence (Transactional Business Intelligence) must access some person
data for reporting purposes. To provide this access, you assign a predefined security profile to relevant job or abstract roles.
Use the Oracle Fusion Human Capital Management (HCM) setup task Manage Data Role and Security Profiles in the Setup
and Maintenance work area. Select Navigator - Tools - Setup and Maintenance and search for the task.
On completion of this task, Oracle Fusion Data Security is updated automatically for roles being used to access Transactional
Business Intelligence.
Job or Abstract Roles and Related Security Profiles

This table identifies, by Oracle Fusion product, the roles that access person data and the predefined security profile that you
assign to each role.
Product Job or Abstract Role Security Profile
Oracle Fusion Assets Asset Accountant View All Workers

Oracle Fusion Assets Asset Accounting Manager View All Workers

817
Oracle Fusion Enterprise Planning Budget Analyst View All Workers

and Budgeting

Oracle Fusion Enterprise Planning Budget Manager View All Workers

and Budgeting

Oracle Fusion Financial Consolidation Accountant View All Workers

Consolidation Hub

Oracle Fusion Financial Consolidation Manager View All Workers

Consolidation Hub

Oracle Fusion Financials Common Intercompany Accountant View All Workers

Module

Oracle Fusion General Ledger Financial Analyst View All Workers

Oracle Fusion General Ledger General Accountant View All Workers

Oracle Fusion General Ledger General Accounting Manager View All Workers

Oracle Fusion Incentive Incentive Compensation Participant View Manager Hierarchy

Compensation Manager

Oracle Fusion Inventory Warehouse Manager View All Workers

Management

Oracle Fusion Project Foundation Project Accountant View All Workers

Oracle Fusion Project Foundation Project Administrator View All Workers

Oracle Fusion Project Foundation Project Billing Specialist View All Workers

Oracle Fusion Purchasing Buyer View All Workers

Oracle Fusion Sourcing Category Manager View All Workers

818
Oracle Fusion Sourcing Sourcing Project Collaborator View All Workers

For example, as part of their Transactional Business Intelligence setup:
• Oracle Fusion Assets implementors must assign the predefined security profile View All Workers to the Asset
Accountant and Asset Accounting Manager job roles.
• Oracle Fusion Incentive Compensation implementors must assign the predefined security profile View Manager
Hierarchy to the Incentive Compensation Participant Manager abstract role.
The security profiles that HCM roles use to access Transactional Business Intelligence are assigned during the setup of HCM
data security. No additional setup is required for Transactional Business Intelligence purposes.
Enabling an Oracle Fusion Transactional Business Intelligence User to Access Person Data:
Worked Example
This example shows how to assign a security profile to a job or abstract role to enable users with that role to access person
data. This task is required for users of Oracle Fusion Transactional Business Intelligence (Transactional Business Intelligence)
who don't also use Oracle Fusion Human Capital Management (HCM).
The table summarizes key decisions for this scenario. When performing this task, use the job or abstract role for your product
and the relevant predefined person security profile in place of those shown here.
What's the name of the job or abstract role? Warehouse Manager

What's the name of the person security profile? View All Workers

Summary of the Tasks

To perform these tasks, you must have the IT Security Manager role.
1. Select the task Manage Data Role and Security Profiles.
2. Search for the job or abstract role.
3. Assign the relevant predefined security profile to the job or abstract role.
Selecting the Manage Data Role and Security Profiles Task

1. Select Navigator - Tools - Setup and Maintenance .
2. On the Overview page, search for and select the Manage Data Role and Security Profiles task.
Searching for the Job or Abstract Role

1. On the Manage HCM Data Roles page, enter the job name Warehouse Manager in the Role field and click Search.
819
2. In the search results, select the entry for the Warehouse Manager job role and click Edit.
Assigning the Security Profile to the Job Role

1. On the Edit Data Role: Role Details page, click Next.
2. In the Person Security Profile field on the Edit Data Role: Security Criteria page, select the security profile View All
Workers.
3. Click Review.
4. On the Edit Data Role: Review page, click Submit.
Define Extensions: Define Custom Enterprise

Scheduler Jobs
Managing Job Definitions: Highlights

Users run scheduled processes based on Oracle Enterprise Scheduler jobs to process data and, in some cases, to provide
report output. A job definition contains the metadata that determines what the job does and what options are available to
users. You can create and edit job definitions in the Setup and Maintenance work area, using the Manage Custom Enterprise
Scheduler Jobs task for your application.
Viewing Job Definitions

• Use the Manage Job Definitions tab to access predefined and custom job definitions.
• The Name column shows an asterisk for predefined job definitions.
Creating Job Definitions

• You or a technical administrator can create jobs based on Java, PL/SQL, Oracle Business Intelligence (BI) Publisher,
or any other supported technology.
• Every predefined or custom job must have a job definition.
• For Oracle Cloud implementations, you can create custom job definitions only for custom jobs based on Oracle BI
Publisher reports.
• The Enable submission from Enterprise Manager check box is not applicable to Oracle Cloud implementations.
◦ If you don't select this check box, then the job can't be run from Enterprise Manager.
◦ If you select this check box, then you can define parameters for your job definition only in Enterprise Manager.
Save the rest of your work on the job definition, and then go to Enterprise Manager if you need to define
parameters.
Editing Job Definitions

• You can edit all aspects of custom job definitions.
• For predefined job definitions, you can:
◦ Determine if user properties are read-only or not.
◦ Edit what are described as job properties in the Oracle Fusion Applications Extensibility Guide for Developers.
820
See: Customizing Existing Oracle Enterprise Scheduler Job Properties
Related Topics
• Managing Job Sets: Highlights
• How can I see which applications a Manage Custom Enterprise Scheduler Jobs task includes?
Managing List of Values Sources: Highlights

A list of values source for Oracle Enterprise Scheduler job definitions determines where a list of values comes from and what
the specific values are. Use these lists for parameters and application defined properties, for example a list of countries that
users can choose from for a Country parameter.
Note
Since you can't edit parameters for predefined job definitions, list of values sources are only for parameters in
custom job definitions.
Accessing List of Values Sources

• Access list of values sources in the Setup and Maintenance work area, using the Manage Custom Enterprise
Scheduler Jobs task for your application.
• Open the Manage List of Values Sources tab.
Creating and Editing List of Values Sources

• Search for list of values sources to edit or delete, or to make sure a particular source doesn't already exist before
you create it.
• Create list of values sources to register them for use in job definitions.
Related Topics
• Managing Job Sets: Highlights
• How can I see which applications a Manage Custom Enterprise Scheduler Jobs task includes?
Contextual Addresses
Setting Up the Mapping Service for Contextual Addresses:

Points to Consider
A contextual address is marked with an orange square that users can click to display the address on a map. The Mapping
Service for Contextual Addresses profile option determines the mapping service to use to display the map. Use the Manage
Administrator Profile Values task in the Setup and Maintenance work area to set the profile option value.
821
Profile Option Default

By default, the Mapping Service for Contextual Addresses profile option has no value.
Warning
Until you enter a valid value for this profile option, users get an error when they try to open a map for any
contextual address.
Profile Option Value

After you find and select the Mapping Service for Contextual Addresses profile option, enter a mapping service URL in the
Profile Value column, for example:
• http://maps.google.com/maps?output=embed&q=
• http://maps.yahoo.com/maps_result.php?q1=
• http://maps.live.com/default.aspx?where1=
• http://bing.com/maps/?v=2&encType=1&where1=
Tip
You can include parameters in the URL. For example, to avoid a locator box in Google Maps, add &iwloc=& to
the URL. So you enter http://maps.google.com/maps?iwloc=&&output=embed&q= as the profile value.
Related Topics
FAQ for Privacy Statement
How can I enable the privacy statement?

In the Setup and Maintenance work area, open the Manage Applications Core Administrator Profile Values task and search
for the Privacy Statement URL profile option. Update the profile value with the full URL of the web page containing the
privacy content. Subsequently, the Privacy Statement menu item appears in the global area under your user name, and is
linked to the given URL.
Related Topics
822
Implementing Project Financial Management External Integration
54 External Integration
Web Services: Overview
Use web services to integrate web-based applications into your Oracle Fusion applications. Web services expose Oracle
Fusion Applications business objects and processes to other applications through the use open standards-based
technologies. Some of these technologies include Extensible Markup Language (XML), Simple Object Access Protocol
(SOAP), Business Process Execution Language (BPEL), Web Services Description Language (WSDL), and XML schema
definitions (XSD). Oracle Fusion Applications web services support development environments and clients that comply with
these open standards.
Oracle Fusion Applications includes two types of web services: Application Development Framework (ADF) services and
composite services. The following table describes the two types.
Web Service Type Description
ADF services ADF services usually represent business objects, such

as employees or purchase orders. ADF services typically
expose standard operations, such as create, update,
and delete. However, for locally-persisted objects, ADF
services are not limited to these operations.
Examples of ADF services include:
• - a service that updates the

Worker.changeHireDate
hire date of the worker business object.
• - a service that adds a task to

ProjectTask.createTask
the project task business object.
Composite services Composite services usually represent end-to-end

business process flows that act on business events
produced by the ADF services. Composite services
orchestrate multiple object-based services, rules
services, and human workflows. Examples of composite
services include:
• - a service that
ProjectStatusChangeApproval.process
accepts the change in project status.
• ScheduleOrchestrationOrderFulfillmentLineService.scheduleOrders
- a service that schedules resources used to fulfill
an order.
Access Oracle Enterprise Repository for Oracle Fusion Applications to find detailed information about integration assets, such
as web services. To view lists of web services, select these asset types:
• ADF Service
• ADF Service Data Object
823
• Composite Service
• Composite
Service methods and parameters, the service path, the WSDL URL and other technical data, appear on the Detail tab
of each web service. Step-by-step instructions regarding the invocation of a service and the service XSD appear on the
Documentation tab. For detailed documentation on using web services, refer to the Getting Started with Web Services guide.
Related Topics
Files for Import and Export
Files for Import and Export: Explained

You can import data into or export data out of Oracle Fusion Applications using repositories of content and processes for
import and export.
Integration specialists stage data for import and export. Application administrators run processes to import data in
repositories of content to application transaction tables, or retrieve data exported from applications.
Aspects of managing files for import and export involve the following.
• The File Import and Export page

• Interacting with content management
• Uploading for import
• Downloading for export
• File size
The File Import and Export Page

The File Import and Export page lets you upload content to or download content from the document repository of Oracle
WebCenter Content Management. For information or assistance regarding general access to content management (including
all metadata), to create and manage accounts, and to programmatically upload and download content, contact the
WebCenter Content Administrator.
Search criteria on the page are limited to the minimum metadata of content management records needed for file import and
export.
Navigation: Navigator > Tools > File Import and Export.
Interacting with Content Management

Everyone who uses the File Import and Export page is assigned to one or more accounts in content management.
Accounts organize and secure access to content items.
Uploading for Import

Uploading a file creates a record.
When you create a record, you must specify an account as well as the file. When you create a record, you must specify an
account as well as the file. The account you specify determines which import process picks up that file to import it.
824
You can upload any file formats that can be parsed by the content repository being used, such as any MIME or content
types. However, the format uploaded should conform to the requirements of the import process being used, such as a
comma-separated values (CSV) file for the Load Interface File for Import process.
Downloading for Export

Processes you run to export data result in files in content management. Records in the search results table of the File Import
and Export page provide links to the files for download.
Note
The owner of a data export file can be an application ID (APPID).
File Size
Upload and download does not intentionally apply the following:
• Data compression
• File chunking or splitting
The UPLOAD_MAX_DISK_SPACE parameter in the web.xml file determines the maximum allowable file size in content management.
The default maximum size is 10240000 (10MB).
Related Topics
Files for Import and Export: Points to Consider

Interaction between the File Import and Export page and Oracle WebCenter Content requires securing content in an account.
Oracle provides predefined accounts in Oracle WebCenter Content.
Areas of file import and export to consider involve the following.
• Security
• Searching records
• Accessing content in a new account
• Account names
• Deleting files
Security
The duty role needed for accessing the File Import and Export page is File Import and Export Management duty. This duty
role is included in the predefined 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 who have permission to a particular
account can work with content items that belong to that account. You can only upload and download files to and from
content management that are associated with accounts that you are entitled to access.
Oracle WebCenter Content does not support trailing slashes (/). Account names are appended with a $ to ensure each
account is unique. Account names are dynamic so that if they overlap (one name is completely contained in another, longer
name, such as US and USSales), each account is treated as discrete by access grants.
825
Security such as virus scanning is handled by the underlying integrated content management.
Searching Records
A record in Oracle WebCenter Content contains metadata used for accessing the file.
When a scheduled process has run to completion on a file, the ecord for the file includes a process ID.
Accessing Content in a New Account

When you create a new account in Oracle WebCenter Content and the content server is not restarted, access to content in
the new account from the File Import and Export page may be delayed until the policy store is updated.
Account Names
If you create custom accounts for importing or exporting data, use the following conventions for naming the account: Do
not include a slash "/" at the beginning or end End with "$" to avoid partial string matching Use "$/" as a separator in the
hierarchical structure.
For example: fin$/journal$/import$ The File Import and Export page transforms account names by removing the $s. For example
fin$/journal$/import$ displays as fin/journal/import. The Remote Introdoc Client (RIDC) HTTP command-line interface (CLI) transforms
the account name you specify without $ symbols to one that includes them. For example, fin/journal/import becomes fin$/
journal$/import$ in WebCenter Content.
Deleting Files
You can delete one file at a time when you use the File Import and Export page. To delete multiple files simultaneously from
the content repository, use the standard service page in Oracle WebCenter Content.
External Data Integration Services for Oracle Cloud
External Data Integration Services for Oracle Cloud: Overview

Use External Data Integration Services for Oracle Cloud to load data into Oracle Fusion Applications from external sources,
such as legacy systems and third-party applications.
Components of External Data Integration Services for Oracle Cloud include:
• Templates and control files for formatting, structuring, and generating the data file.
• A general file load process for loading values from the data file into interface tables.
• Application-specific data import processes for transferring data from interface tables to the application tables in your
Oracle Fusion Applications.
To use External Data Integration Services for Oracle Cloud to load data into Oracle Fusion Applications tables:
1. Prepare your data and generate a data file by using the product-specific templates and control files.
2. Transfer the data file to the integrated content management server.
3. Run the Load Interface File for Import process.
4. Correct data load errors, if necessary.
826
5. Run the appropriate application-specific process for validating and inserting the data into application tables.
6. Correct data import errors, if necessary.
For templates and control files, see assets with the File-Based Data Import type in Oracle Enterprise Repository for Oracle
Fusion Applications (http://fusionappsoer.oracle.com). For more information, see the Documentation tab for the Load
Interface File for Import process in Oracle Enterprise Repository.
Locating File Import Templates: Explained

External data that you integrate into your Oracle Fusion Applications must be structured and formatted according to the
properties of the fields and tables that store the data. To prepare external data so that data types, structural relationships,
and other properties of the data correctly align to the data types, structural relationships, and properties of the target tables,
use the product-specific templates and control files in Oracle Enterprise Repository for Oracle Fusion Applications.
You access these files from the Documentation tab of the scheduled process that corresponds to the interface tables that
store the data. To find the process, you can search the interface table or you can search the specific process, if you know it.
Aspects of preparing external data using templates involve these tasks.
• Finding templates and control files

• Downloading templates
• Opening XLS templates
Finding Templates and Control Files

To find the templates and control files:
1. Sign in to Oracle Enterprise Repository.

2. Enter the following information in the Search fields:
Field Value
Search String FBDI

Type Scheduled Process

FusionApps: Logical Business Area (Optional) Select the value relevant to your
implementation.

3. Click Search.
4. Select Load Interface File for Import from the results.
Downloading Templates
To download the templates:
1. Use the Search area to locate the Load Interface File for Import job and then select it from the search results.
827
2. Click the Documentation tab in the lower pane to see a list of links to application-specific import jobs.
3. Click a link to access the job.
4. Click the Documentation tab in the lower pane to see a list of links that access:
◦ Control files, which describe the logical flow of the data load process
◦ XLS templates, which include worksheets and macros that assist you in structuring, formatting, and generating
your data file
5. Click the link to download the file.
Opening the XLS Template

To prepare your data in a spreadsheet format, use XLS templates:
1. Open the XLS template.
The first worksheet in each file provides instructions for using the template.
Important
If you omit or fail to complete the instructions, data load errors and data import failure are likely.
2. Save a copy of the file.
3. Click the Generate CSV Filebutton.
The macro generates a comma-separated values (CSV) file and compresses it into a ZIP file; you must transfer the
ZIP file to the content management server.
Related Topics
Using Excel Integration Templates to Generate Data Files:

Points to Consider
Oracle Enterprise Repository for Oracle Fusion Applications includes integration templates to help you prepare external data
for loading and importing. Each template includes table-specific instructions, guidelines, formatted spreadsheets, and best
practices for preparing the data file for upload. Use the templates to ensure that your data conforms to the structure and
format of the target application tables.
Templates
This list details the characteristics of the templates:
• Each interface table is represented by a separate worksheet.
• Each interface table field is represented by a worksheet column with a header in the first row.
828
• Each column header contains bubble text, or comments, that include details about the column, such as the
expected data type, length, and, in some cases, other instructional text.
• The worksheet columns appear in the order that the control file processes the data file.
• The columns that you do not intend to use can be hidden, but not reordered or deleted.
Important
Deleting or reordering columns will cause the load process to fail and result in an unsuccessful data load.
• The external data must conform to the data type that the control file and process for the associated database
column accepts.
◦ Date column values must appear in the YYYY/MM/DD format.
◦ Amount column values must appear with no 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.
• Columns are formatted, where applicable, to match the target field data type to eliminate data entry errors.
• For columns that require internal ID values, refer to the bubble text for additional guidance about finding these values.
• When using Microsoft Excel to generate or update the CSV file, you must select YYYY/MM/DD as your regional
setting for date values.
Using XML Integration Templates to Generate Data Files:

Points to Consider
Use XML templates in Oracle Data Integrator to prepare your external data for loading and importing. Oracle Enterprise
Repository for Oracle Fusion Applications includes three types of XML templates that you import as target models in your
Oracle Data Integrator repository.
Oracle Enterprise Repository includes these three levels of XML files:
• Family-level
• Product-level
• Product
Family-Level XML Files

A family-level XML file is common to a group of product-level model folders and product models.
Consider the following points when you use family-level XML files:
• The family-level XML file supports all of the Oracle Enterprise Repository assets in the family, for example Oracle
Fusion Financials or Human Capital Management.
829
• You import the family-level XML file into your Oracle Data Integrator repository prior to importing the other XML files.
• You import one family-level XML file as a model folder for each family of products.
• You import each family-level XML file as a top-level model folder.
• You import the family-level XML file one time; it supports all subsumed product-level model folders.
• You select Synonym mode Insert Update as the import type.
Product-Level XML Files

A product-level XML file is common to a group of product models.
Consider the following points when you use product-level XML files:
• The product-level XML file supports all of the Oracle Enterprise Repository assets in the product line, for example
Fixed Assets, General Ledger, or Payables.
• You import one product-level XML file as a model folder for each line of products.
• You import the product-level XML file as a model folder into your Oracle Data Integrator repository after you import
the family-level XML file, but before you import product XML files.
• You import each product-level XML file as a midlevel model folder within the appropriate family-level model folder.
• You import the product-level XML file one time; it supports all subsumed product models.
Product XML Files

A product XML file represents a specific Oracle Enterprise Repository interface table asset.
Consider the following points when you use product XML files:
• You import one product XML file as a model for each interface table or set of tables, for example Mass Additions.
• You import the product XML file as a model into your Oracle Data Integrator repository after you import the product-
level XML file.
• You import each product XML file as a model within the appropriate product-level model folder.
• You import each product XML file one time.
• The model is based on File technology.
• After you import the product model, you connect the model to the correct logical schema.
Creating Integration Projects That Generate Data Files for

Import: Points to Consider
When you use Oracle Data Integrator (ODI) to generate import data files from external data sources, you must configure an
integration project. Integration projects are collections of ODI components that provide the procedural details of an integration
830
from a source to a target. In this scenario, the source is your external data and the target is the import data file that you load
and import into your Oracle Fusion Applications.
Configure these components to create your integration project.
• Knowledge modules
• Integration interfaces
Knowledge Modules
Knowledge modules contain the information that Oracle Data Integrator requires to perform a specific set of tasks against a
specific technology or set of technologies. Examples include Check knowledge modules, which ensure that constraints on
the sources and targets are not violated and integration knowledge modules, which load data to target tables.
Consider the following points about knowledge modules:
• The knowledge modules that you import into your integration project depend on the source and target technologies,
as well as other integration-specific rules and processes.
• Multiple types of knowledge modules exist in ODI.
• Use the SQL File to Append module to create the import data file.
Integration Interfaces
Integration interfaces comprise sets of rules that define the loading of data from one or more sources to the target.
Consider the following points about integration interfaces:
• The source is the datastore from your external data model.
• The target is the interface table datastore, which is the CSV file from your interface table model.
• After you set up the source and target datastores, map the target fields to the source fields.
• You can map source field values to target fields or constants.
Transferring Data Files to Target Accounts in Oracle

WebCenter Content: Explained
After you generate the ZIP file that contains the CSV data import file, transfer it to the content repository.
Use any of these methods to transfer file:
• File Import and Export page in Oracle Fusion Applications
• Oracle WebCenter Content Document Transfer Utility
• Oracle Fusion Financials Utility web service
Note
Consult Oracle Enterprise Repository for Oracle Fusion Applications for web service documentation.
831
Aspects of transferring data files to content management involve the following:
• Target accounts
• Accessing transferred content
Target Accounts
You must transfer files to these predefined account in content management that corresponds to the interface table or assets.
Interface Table Predefined Account
Payables Standard Invoice Import fin/ payables/ import

• AutoInvoice Import fin/ receivables/ import

• Receivables Standard Receipt Import
• Customer Import
• China Value Added Tax Invoice Import
• BAI2 Format Bank Statements Import fin/ cashManagement/ import

• EDIFACT FINSTA Format Bank Statements Import
• ISO200022 CAMT053 Format Bank Statements

Import
• SWIFT MT940 Format Bank Statements Import
• Fixed Asset Mass Additions Import fin/ assets/import

• Fixed Asset Mass Adjustments Import
• Fixed Asset Mass Retirements Import
• Fixed Asset Mass Transfers Import
• Fixed Asset Units of Production Import
Intercompany Transaction Import fin/ intercompany/ import

• Journal Import fin/ generalLedger/ import

• Chart Of Accounts Segment Values and
Hierarchies Import
832
General Ledger Budget Balance Import fin/ budgetBalance/ import

Supplier Bank Account Import fin/ payables/ import

Tax Configuration Content Import fin/tax/import

Import Blanket Purchase Agreements prc/ blanketPurchaseAgreement/ import

Import Contract Purchase Agreements prc/ contractPurchaseAgreement/ import

Import Purchase Orders prc/ purchaseOrder/ import

Import Requisitions prc/ requisition/ import

• Import Suppliers prc/ supplier/ import

• Import Supplier Sites
• Import Supplier Site Contacts
• Import Supplier Site Assignments
Project Enterprise Resource Import prj/ projectManagement/ import

Project Unprocessed Expenditure Item Import prj/ projectCosting/ import

Cycle Count Import scm/ cycleCount/ import

Inventory Reservation Import scm/ inventoryReservation/ import

Inventory Transaction Import scm/ inventoryTransaction/ import

Item Import scm/ item/import

Receiving Receipt Import scm/ receivingReceipt/ import

833
Shipment Request Import scm/ shipmentRequest/ import

You can create subaccounts to further organize your files. However, you must create the account subordinate to the
predefined account for the asset you are integrating.
Accessing Transferred Content

To access your transferred data you must access the account that corresponds to the interface table or asset appropriate for
the data.
Available data integration processes move the content into and out of Oracle Fusion Applications tables. Running an import or
export process creates a process ID in content management that you can use to identify the content you wish to overwrite or
extract.
Oracle Enterprise Scheduler import process jobs result in the following hierarchy of items in Oracle WebCenter Content:
• A root import job is a list of all unprocessed files in an account. This job submits the child jobs that process each
unprocessed file.
• A parent import job is a single file ID, account name, and the import steps (download, extract, import) for a
single job, job set, or subrequests. This type of job tags the file with its request ID, provided the file is not deleted
immediately after successful import.
• A child import job is a direct data load from a prepared file, typically a SQLLoader. Typically, the parent import job
submits this job.
Related Topics
Document Transfer Utility: Explained

The WebCenter Content Document Transfer Utility for Oracle Fusion Applications is a feature-set Java library that provides
programmatic access to the content repository. Use the utility to import and export documents, such as import files that
contain external data that you want to load into interface and application tables.
The library includes:
• Oracle WebCenter Content client command line tool

• Oracle Data Integrator (ODI) upload and download tools
• Oracle WebCenter Content remote intradoc client (RIDC)
• Oracle HTTPClient
• Oracle Fusion Applications branding and defaults
Options for the WebCenter Content Document Transfer Utility for Oracle Fusion Applications fall into these categories:
• DownloadTool program options

• UploadTool program options
834
• Debugging and silent invocation options
DownloadTool Program Options

This table describes the download tool program options:
Option Description
url Protocol-specific connection URL of content server

username Username to leverage

password Password, supplied in command line

passwordFile Password, supplied in text file on the first line of the file

dID ID of document revision to download

dID is unique across repository

dID changes with each revision

Note
Alternatively, specify the dDocName and
RevisionSelectionMethod to identify the dID
to leverage.

dDocName Content name

Multiple revisions of a document can share the same
dDocName value, otherwise it is unique.

Note
You should also provide
RevisionSelectionMethod value.

RevisionSelectionMethod Revision to download

Valid values: Latest, LatestReleased

Default value: Latest

outputFile Path and name of local file to write

835
Here you see a sample download invocation command:

java -classpath "oracle.ucm.fa_client_11.1.1.jar" oracle.ucm.client.DownloadTool
url=http://ucmserver.com:16200/cs/idcplg username=weblogic password=we1com3i
dID=21537 outputFile="/tmp/output.doc"
Here you see sample output:

Oracle WebCenter Content Document Transfer Utility
Oracle Fusion Applications
Copyright (c) 2013, Oracle. All rights reserved.
Performing download (GET_FILE) ...
Download successful.
UploadTool Program Options

This table describes the upload tool program options:
Option Description
url Protocol-specific connection URL of content server

username Username to leverage

password Password, supplied in command-line

passwordFile Password, supplied in text file on the first line of the file

primaryFile Fully-qualified path of local primary file to upload

dDocAccount Destination account

dDocTitle Document title

checkout If uploading a document revision, check out the

document from the repository before uploading the
revision

Valid values: true, false

Default value: false

ignoreCheckoutErrorNeg22 Ignore error -22 (user has already checked-out the

document) when checking-out the document.


Default value: true

836
Here you see a sample upload invocation command:

java -classpath "oracle.ucm.fa_client_11.1.1.jar" oracle.ucm.client.UploadTool
primaryFile="/tmp/resume.doc" dDocTitle="Resume of MSMITH" -dDocAccount=/acme/sales
Here you see sample output:

Performing upload (CHECKIN_UNIVERSAL) ...
Upload successful.
[dID=21537 | dDocName=UCMFA021487]
Debugging and Silent Invocation Options

This table describes the options which are common to all tools that the invoker can leverage.
Option Description
verbose Verbose output

Log filled with Request/ Response DataBinders

quiet Minimal output

version Print tool revision or version

log_file_name Send program output to specified log file instead of the

System.out log file

log_ file_append Append log to existing log file rather than overwrite it


Default value: false

socketTimeout Override time out of socket

Specify override time in seconds

You can use the tools to test the connection. Provide only the url, username, and password as you see in this sample test:
java -classpath "oracle.ucm.fa_client_11.1.1.jar" oracle.ucm.client.DownloadTool
Here you see the sample output:

Performing connection test (PING_SERVER) ...
837
Connection test successful.
Load Interface File for Import Process

Use to load external setup or transaction data from a data file in the content repository to interface tables. The process
prepares the data for import into application tables.
You run this process from the Scheduled Processes page. You can run it on a recurring basis.
Before running this process, you must:
1. Prepare your data file.
2. Transfer the data file to the content repository.
Parameters
Import Process
Select the target import process.
Data file
Enter the relative path and the file name of the *.zip data file in the content repository.
Importing Data into Application Tables: Procedure

The final destination for your external data is the application data tables of your Oracle Fusion Applications product.
Aspects of importing data into application tables involve the following:
• Loading data into interface tables
• Finding and submitting the import process
Loading Data into Interface Tables

Interface tables are intermediary tables that store your data temporarily while the system validates format and structure. Run
the Load Interface File for Import scheduled process to load data from the data file into the interface table that corresponds to
the template that you use to prepare the data.
To load your data into interface tables, submit the Load Interface File for Import scheduled process:
1. Sign in to Oracle Fusion Applications.
2. In the Navigator menu, select Tools, Scheduled Processes
3. Click the Schedule New Process button.
4. Search and select the Load Interface File for Import job.
5. When the Process Details page appears:
a. Select the target import process.
838
b. Enter the data file name.
Note
If the file exists in an account subordinate to the predefined account, you must enter the entire
path relative to the predefined account in the content repository. Include all subaccounts and the
file name.
6. Submit the process.
If no errors exist in the data file, then the process populates the interface tables.
Note
The data file remains in the content repository after the process ends.
Finding and Submitting the Import Process

Run the appropriate import process to import the data into the interface tables of your Oracle Fusion Applications product.
To import your data:
1. Sign in to Oracle Fusion Applications.
2. In the Navigator menu, select Tools, Scheduled Processes
3. Click the Schedule New Process button.
4. Find and select the import process that is specific to the target application tables.
5. When the Process Details page appears, select the process that corresponds to the data that you are importing.
If you prepared your data using the spreadsheet template, select the process named in the Overview section of the
spreadsheet.
6. Submit the process.
Note
For more detailed information on the process used for data prepared using the spreadsheet template,
see the Instructions and CSV Generation tab of the spreadsheet template.
Correcting Import Load Process Errors: Explained

The Load Interface File for Import process ends in error if the load of the data file fails on any row.
The following conditions apply when the process ends in error:
• The Load File to Interface child process ends in either warning or error.
• All rows that were loaded by the process are deleted, even those rows that loaded successfully.
839
To correct errors:
1. Review the error logs.
2. Change any formatting or structural anomalies that exist in the data.
3. Recreate the CSV and ZIP files.
4. Transfer the file to the content management server.
5. Submit the Load Interface File for Import job.
6. Repeat these steps until the process successfully loads the data.
7. Import the data using the appropriate product-specific process.
840
Implementing Project Financial Management Importing and Exporting Setup Data
55 Importing and Exporting Setup Data
Configuration Packages: Explained

Almost all Oracle Fusion application implementations require moving functional setup data from one instance into another
at various points in the lifecycle of the applications. For example, one of the typical cases in any enterprise application
implementation is to first implement in a development or test application instance and then deploy to a production application
instance after thorough testing. You can move functional setup configurations of applications from one application instance
into another by exporting and importing Configuration packages from the Manage Configuration Packages page.
A Configuration Package contains the setup import and export definition. The setup import and export definition is the list of
setup tasks and their associated business objects that identifies the setup data for export as well as the data itself. When you
create a configuration package only the setup export and import definition exists. Once you export the configuration package
appropriate setup data is added to the configuration package using the definition. Once a configuration package is exported,
the setup export and import definition is locked and cannot be changed.
You generate the setup export and import definition by selecting an implementation project and creating a configuration
package. The tasks and their associated business objects in the selected implementation project define the setup export and
import definition for the configuration package. In addition, the sequence of the tasks in the implementation project determine
the export and import sequence.
Exporting and Importing Setup Data: Explained

A configuration package is required to export setup data. You can export a configuration package once you create it, or at
any time in the future. During export, appropriate setup data will be identified based on the setup export definition and added
to the configuration package. The setup data in the configuration package is a snapshot of the data in the source application
instance at the time of export. After the export completes, you can download the configuration package as a zipped archive
of multiple XML files, move it to the target application instance, and upload and import it.
Export
You can export a configuration package multiple times by creating multiple versions. While the export definition remains the
same in each version, the setup data can be different if you modified the data in the time period between the different runs of
the export process. Since each version of the configuration package has a snapshot of the data in the source instance, you
can compare and analyze various versions of the configuration package to see how the setup data changed.
Import
In the target application instance, the setup import process will insert all new data from the source configuration package
that does not already exist and update any existing data with changes from the source. Setup data that exists in the target
instance but not in source will remain unchanged.
Export and Import Reports

You can review the results of the export and import processes using reports. The results appear ordered by business objects
and include information on any errors encountered during the export or import process. If a setup export or import process
paused due to errors encountered or for a manual task to be performed outside of the application, then you can resume the
paused process.
841
These reports show what setup data was exported or imported and by which specific process. You can change the reports
to validate the setup data as well as to compare or analyze it. A report is generated for each business object. These reports
show the same information as the export and import results seen directly in the application.
Process status details are available as text files showing the status of an export or import process including the errors
encountered during the process.
Moving Common Reference Objects
Moving Common Reference Objects: Overview

The common reference objects in Oracle Middleware Extensions for Applications are used by several setup tasks in the Setup
and Maintenance work area. The common reference objects become a part of the configuration package that is created for
an implementation project. While moving the application content, for example, from the test phase to the production phase of
an implementation, you must pay special attention to the nuances of these common reference objects.
Parameters
The common reference objects are represented as business objects. A single object can be referenced in multiple setup
tasks with different parameters. In the configuration package that is 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, it is necessary that all the dependencies are noted before the movement of objects so that there are no broken
references among the objects.
Business Objects for Moving Common Reference Objects:

Points to Consider
Common reference objects in Oracle Fusion Functional Setup Manager are represented by business objects. These business
objects are the agents that contain the application content and carry them across whenever the application setup is moved
from one environment to another, for example, test environment to production environment.
Choice of Parameters
The following table lists the business objects, the corresponding movement details, and the effect of the setup task parameter
on the scope of the movement.
Note
• Only the translation in the current user language is moved.
• The Oracle Social Network business objects and the Navigator menu customizations are moved using the
customization sets on the Customization Migration page instead of using the export and import function in the
Setup and Maintenance work area.
842
Business Object Name Moved Functional Item Effect on the Scope of

Movement
Application Message Messages and associated tokens No parameters: all messages are
moved.

moduleType/ moduleKey
only messages belonging to
the specified module and its
descendant modules in the
taxonomy hierarchy are moved.

messageName/ applicationId only
the specified message is moved.

Application Taxonomy Application taxonomy modules and No parameters: all taxonomy

components modules and components are
moved.

Application Attachment Entity Attachment entities No parameters: all attachment

entities are moved.

moduleType/ moduleKey only
attachment entities belonging
to the specified module and
its descendant modules in the

Application Attachment Category Attachment categories and No parameters: all attachment

category-to-entity mappings categories and category-to-entity
mappings are moved.

attachment categories belonging
taxonomy hierarchy along with
the respective category-to-entity
mappings are moved.

843

Movement
Application Document Sequence Document sequence categories No parameters: all categories are
Category moved.

only categories belonging to

code/ applicationId only the
specified document sequence
category code is moved.

Application Document Sequence Document sequences and their No parameters: all sequences are
assignments moved.

document sequences belonging
taxonomy hierarchy are moved

name: only the specified document
sequence is moved.

844

Movement
Application Descriptive Flexfield Descriptive flexfield registration No parameters: all descriptive

data and setup data flexfields are moved.

descriptive flexfields belonging

descriptiveFlexfieldCode/
applicationId only the specified
descriptive flexfield is moved.

Note
Importing a flexfield's
metadata can change
its deployment status
and therefore, the
affected flexfields must be
redeployed. The import
process automatically
submits affected flexfields
for redeployment.

Note
Only flexfields with a
deployment status of
Deployed or Deployed to
Sandbox are eligible to be
moved.

845

Movement
Application Extensible Flexfield Extensible flexfield registration No parameters: all extensible

data and setup data, including flexfields are moved
categories
extensible flexfields belonging

extensibleFlexfieldCode/
applicationId only the specified
extensible flexfield is moved.

Note
metadata can change
and therefore, the
for redeployment.

Note
moved.

846

Movement
Application Key Flexfield Key flexfield registration data and No parameters: all key flexfields are
setup data moved.

moduleType/ moduleKey only key
flexfields belonging to the specified
module and its descendant
modules in the taxonomy hierarchy
are moved.

keyFlexfieldCode/ applicationId only
the specified key flexfield is moved.

Note
metadata can change
and therefore, the
for redeployment.

Note
moved.

847

Movement
Application Flexfield Value Set Value set setup data No parameters: all value sets are
moved.

moduleType/ moduleKey only value
sets belonging to the specified
module and its descendant
modules in the taxonomy hierarchy
are moved.

valueSetCode: only the specified
value set is moved.

Note
Importing a value set's
metadata can change
the deployment status
of flexfields that use the
value set, and therefore
the affected flexfields must
be redeployed. The import
for redeployment.

Application Reference Currency Currency data No parameters: all currencies are

moved.

Application Reference ISO ISO language data No parameters: all ISO languages
Language are moved.

Application Reference Industry Industry data including industries in No parameters: all industries are
territories data moved.

Application Reference Language Language data No parameters: all languages are

moved.

Application Reference Natural Natural language data No parameters: all natural

Language languages are moved.

Application Reference Territory Territory data No parameters: all territories are

moved.

848

Movement
Application Reference Time zone Time zone data No parameters: all time zones are
moved.

Application Standard Lookup Standard lookup types and their No parameters: all standard
lookup codes lookups are moved.

standard lookups belonging

lookupType: only the specified
common lookup is moved.

Application Common Lookup Common lookup types and their No parameters: all common

moduleType/ moduleKey - only
common lookups belonging

lookupType: only the specified
common lookup is moved.

Application Set-Enabled Lookup Set-enabled lookup types and their No parameters: all set-enabled

set-enabled lookups belonging

lookupType: only the specified set-
enabled lookup is moved.

849

Movement
Application Profile Category Profile categories No parameters: all profile

categories are moved.

only categories belonging to

name/ applicationId only the
specified category is moved.

Application Profile Option Profile options and their values No parameters: all profile options
and their values are moved.

profile options and their values
belonging to the specified module
are moved.

profileOptionName: only the
specified profile option and its
values are moved.

Application Profile Value Profile options and their values No parameters: all profiles and their
values are moved.

profiles and their values belonging
to the specified module are moved.

categoryName/
categoryApplicationId only profiles
and their values belonging to the
specified category are moved.

profileOptionName: only the
specified profile and its values are
moved.

Application Reference Data Set Reference data sets No parameters: all sets are moved.

850

Movement
Application Reference Data Set Reference data set assignments determinantType: only assignments
Assignment for the specified determinant type
are moved.

determinantType/
referenceGroupName only
assignments for the specified
determinant type and reference
group are moved.

Application Tree Structure Tree structures and any labels No parameters: all tree structures
assigned to the tree structure (and their labels) are moved.

tree structures (and their labels)
are moved.

treeStructureCode: only the
specified tree structure (with its
labels) is moved.

Application Tree Tree codes and versions No parameters: all trees are
moved.

moduleType/ moduleKey only trees
are moved.

treeStructureCode: only trees
belonging to the specified tree
structure are moved.

TreeStructureCode/ TreeCode only
trees belonging to the specified tree
structure and tree code are moved.

Application Tree Label Tree structures and any labels No parameters: all tree structures
assigned to the tree structure (and their labels) are moved.

tree structures (and their labels)
and its descendant modules in the

treeStructureCode: only the
specified tree structure (with its
labels) is moved.

851

Movement
Application Data Security Policy Database resources, actions, No parameters: all database
conditions, and data security resources/ actions/ conditions/
policies policies are moved.

database resources/ actions/
conditions/ policies belonging

objName: only the specified
database resource along with its
actions/ conditions/ policies is
moved.

Note
If the policies being moved
contain reference to newly
created roles, move the
roles before moving the
policies.

Note
If the source and target
systems use different
LDAPs, manually perform
the GUID reconciliation
after moving the data
security policies.

Application Activity Stream Activity stream options No parameters: all activity stream
Configuration options are moved.

Moving Related Common Reference Objects: Points to

Consider
Certain common reference objects may use other common reference objects creating dependencies among the objects.
During the movement of common reference objects, these dependencies or references need to be taken care of.
Dependencies
The dependencies among the common reference objects may be caused by any of the following conditions.
• Flexfield segments use value sets

• Value sets may make use of standard, common, or set-enabled lookups
852
• Key flexfields may have an associated tree structure and key flexfield segments may have an associated tree code
• Tree codes and versions may be defined over values of a value set
• Data security policies may be defined for value sets that have been enabled for data security
You may choose to move one, some, or all of the business objects by including the ones you want to move in your
configuration package. For example, you may choose to move only value sets and not lookups, or you may choose to move
both value sets and their lookups as part of the same package. Whatever be the combination, it is recommended that during
the movement of objects, you follow an order that maintains the dependencies among the objects.
While moving the business objects, adhere to the guidelines and exactly follow the order as listed below.
1. Move created taxonomy modules before moving any objects that reference them, such as flexfields, lookups,
profiles, attachments, 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 profile options before moving any objects that reference them, such as profile categories or profile
values.
7. Move created attachment entities before moving any objects that reference them, such as attachment 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 being moved have dependencies on newly
created security roles, you must move the security roles before moving the security policies.
Using Seed Data Framework to Move Common Reference

Objects: Points to Consider
To move the common reference objects, you can use the Seed Data Framework (SDF). You can also use the command line
interface of SDF to move the object setup data. For more information about seed data loaders including common reference
object loaders, see Oracle Fusion Applications Developer's Guide.
Movement Dependencies
The seed data interface moves only the setup metadata. For example, if you use SDF to import flexfield metadata, the flexfield
setup metadata is imported into your database. However, you must invoke the flexfield deployment process separately after
seed data import to regenerate the runtime flexfield artifacts in the target environment. Similarly, if you use SDF to import
data security metadata, you must first move any new referenced roles and then manually run the GUID reconciliation where
required.
To ensure that the reference data is not lost during the movement, certain guidelines are prescribed. It is recommended that
you perform the movement of object data exactly in the order given below.
853
Note
Only the translation in the current user language is moved.
1. Move created taxonomy modules before moving any objects that reference them, such as flexfields, lookups,
profiles, attachments, 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 profile options before moving any objects that reference them, such as profile categories or profile
values.
7. Move created attachment entities before moving any objects that reference them, such as attachment 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.
12. Move created value sets before moving any objects that reference them, such as flexfields.
13. Move created trees before moving any objects that reference them, such as key flexfields.
854
Oracle Project Portfolio Management Cloud Glossary
Glossary
abstract role
A description of a person's function in the enterprise that is unrelated to the person's job (position), such as employee,
contingent worker, or line manager. A type of enterprise role.
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 attribute
Predefined fields that map to components of subledger journal entries. Sources are assigned to accounting attributes.
accounting event class

Categories that classify transaction types and group event types for accounting rules.
accounting event type

Represents a business operation that may have an accounting impact.
accounting method
A set of journal entry rules which determine how a subledger journal entry is created for each event class or event type.
accounting period
The fiscal period used to report financial results, such as a calendar month or fiscal period.
action
The kind of access named in a security policy, such as view or edit.
activity
A business action or task that uses a resource or incurs a cost. In Primavera P6 Enterprise Project Portfolio Management,
the fundamental executable work element in the work breakdown structure of a project. Activities contain all the information
necessary to perform the required work.
ADF
Acronym for Application Developer Framework. A set of programming principles and rules for developing software
applications.
ADFdi
Abbreviation for Application Development Framework Fusion Desktop Integration. A tool that allows you to export data from
spreadsheet application into Oracle Fusion applications.
855
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.
application identity
Predefined application level user with elevated privileges. An application identity authorizes jobs and transactions for which
other users are not authorized, such as a payroll run authorized to access a taxpayer ID while the user who initiated the job is
not authorized to access such personally identifiable information.
application role
A role specific to applications and stored in the policy store.
Applications Core
The short name for the product component Oracle Fusion Middleware Extensions for Oracle Application.
approved budget
Financial plan type designated as an approved cost budget, approved revenue budget, or both, whose versions are used for
specific purposes (for example, as default budget versions for project performance reporting).
ASN
Abbreviation for advance shipment notice. Electronic data interchange (EDI) or Extensible Markup Language (XML) from a
supplier that informs the receiving organization that a shipment is in transit. ASNs speed the receiving process by enabling
the receiver to check in entire shipments without entering individual line information. The ASN may contain details including
shipment date, time, and identification number; packing slip data; freight information; item detail including cumulative received
quantities; country of origin; purchase order number; and returnable packing unit information.
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.
856
automatic offset
A method for balancing invoice and payment journal entries that cross primary balancing segment values.
balancing segment
A chart of accounts segment used to automatically balance all journal entries for each value of this segment.
balancing segment value

The value of a balancing segment used to automatically balance journal entries.
baseline project plan

Key planned information for tasks and task assignments, including dates, costs, quantity, effort, and rates, that you can save
from current project plan values. Setting a baseline for a project plan doesn't create a new plan version. Rather, current plan
information is saved in baseline columns of the current project plan.
bill plan
A set of instructions on a contract that define how to invoice a customer. Multiple contract lines on a contract can use the
same or different bill plans.
billing control
Contract feature that controls the types of transactions, dates, and amounts a customer may be invoiced for and revenue can
be recognized for a contract or contract line. Define billing controls at the contract or contract line level.
billing extension
Company-specific business rule that creates automatic revenue or invoice events. You can assign a billing extension to a
revenue method or invoice method.
borrowed and lent processing method

A method of processing cross-charge transactions that generates accounting entries to transfer costs or share revenue from
the provider organization to the receiver organization within a legal entity.
BPEL
Business Process Execution Language; a standard language for defining how to send XML messages to remote services,
manipulate XML data structures, receive XML messages asynchronously from remote services, manage events and
exceptions, define parallel sequences of execution, and undo parts of processes when exceptions occur.
budgetary control
Set of options and validation processes that determine which transactions are subject to validation against budgets to
prevent overspending.
burden cost
Burden costs are legitimate costs of doing business that support raw costs and cannot be directly attributed to work
performed.
857
burden cost base

The grouping of raw costs to which burden costs are applied.
burden cost code

A classification of overhead costs. A burden cost code represents the type of burden cost that you want to apply to raw cost.
For each burden cost code in the burden structure, you specify what cost base it is applied to, the expenditure types it is
associated with, and the order in which it is applied to raw costs within the cost base.
burden structure
Determines how expenditure types are grouped into burden cost bases and what types of burden costs are applied to the
cost bases. A burden structure defines relationships between burden cost bases and burden cost codes, and between
burden cost bases and expenditure types.
burdened cost
Cost of an expenditure item, including the raw cost and burden costs.
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 intelligence catalog

The repository where all business intelligence objects, including analytics, reports, briefing books, and agents, are stored. The
catalog contains separate folders for personal, shared, and custom objects.
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.
chart of accounts
The account structure your organization uses to record transactions and maintain account balances.
class category
Method of classifying projects. For example, use class categories to define project funding sources, investment strategies, or
industry sectors. Class categories are associated with a set of values called class codes.
class code
Implementation-defined value within a class category that is used to classify projects. For example, a class category called
Industry Sector can have class codes such as Construction, Banking, and Health Care.
858
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.
clause localization
A type of clause adoption where the adopted clause is edited to suit the local business unit needs.
clause numbering level

Specifies the determinant type of the document sequence for automatic clause numbering
clearing company
The intercompany clearing entity used to balance the journal.
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 have a different set of context-sensitive
segments.
context-sensitive segment
A flexfield segment that may or may not appear depending upon a context such as other information that has been captured.
Context-sensitive segments are custom attributes that apply to certain entity rows based on the value of the context
segment.
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 that lets you create and evaluate business rules in the terms library such that the contract terms meet your business
standards, by suggesting contract changes or additional clauses.
859
Contract Terms Library

A repository of standard clauses, contract terms templates, and business rules built using Contract Expert.
control budget account segment

Budget dimensions that validate budgetary controls. Budget dimensions are limited to chart of account segments, project
attributes, and project resource attributes.
corporate rate type

Rate you define to standardize rates used in conversion of one currency to another over a period of time. This rate is generally
a standard market rate determined by senior financial management for use throughout the organization.
cost center
A unit of activity or a group of employees used to assign costs for accounting purposes.
cost organization
A grouping of inventory organizations that indicates legal and financial ownership of inventory, and which establishes common
costing and accounting policies.
country holding company

A legal entity that acts on behalf of several divisions within an enterprise, and is the legal employer in a country.
current planning period

The current project accounting period or accounting period (depending on the selected calendar type) for the purposes of
financial planning.
data dimension
A stripe of data accessed by a data role, such as the data controlled by a business unit.
data instance set

The set of HCM data, such as one or more persons, organizations, or payrolls, identified by an HCM security profile.
data role
A role for a defined set of data describing the job a user does within that defined set of data. A data role inherits job or
abstract roles and grants entitlement to access data within a specific dimension of data based on data security policies. A
type of enterprise role.
data role template

A set of instructions that specifies which base roles to combine with which dimension values to create a set of data security
policies.
860
data security
The control of access and action a user can take against which data.
data security policy

A grant of entitlement to a role on an object or attribute group for a given condition.
database resource
An applications data object at the instance, instance set, or global level, which is secured by data security policies.
department
A division of a business enterprise dealing with a particular area of activity.
description rule
The rule that defines description content that can appear on the subledger journal header and line.
descriptive flexfield
Customizable expansion space, such as fields used to capture additional descriptive information or attributes about an entity,
such as customer cases. Information collection and storage may be configured to vary based on conditions or 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.
distribution factor
Numeric value that determines the budget, forecast, or project plan amounts distributed to financial periods corresponding to
each of the ten spread points that make up a spread curve.
division
A business-oriented subdivision within an enterprise. Each division is organized to deliver products and services or address
different markets.
861
document
Business objects for which you import transactions from source applications. Examples of documents are time cards,
expense reports, usages, or miscellaneous transactions.
document category
A high level grouping of person documents such as visas, licences, and medical certificates. Document subcategories
provide further grouping of document categories.
document entry
Represents distinct type of transactions for a document that need to be processed in different ways.
document event class

Categorization of events within an application, such as Payables, Purchasing, or Receivables. For example, Payables event
classes include standard invoices, prepayment invoices, and credit memos.
document sequence
A unique number that is automatically or manually assigned to a created and saved document.
duty role
A group of function and data privileges representing one duty of a job. Duty roles are specific to applications, stored in the
policy store, and shared within an application instance.
employment terms
A set of information about a nonworker's or employee's job, position, pay, compensation, working hours, and work location
that all assignments associated with the employment terms inherit.
enterprise
An organization with one or more legal entities under common control.
enterprise role
Abstract, job, and data roles are shared across the enterprise. An enterprise role is an LDAP group. An enterprise role is
propagated and synchronized across Oracle Fusion Middleware, where it is considered to be an external role or role not
specifically defined within applications.
entitlement
Grant of access to functions and data. Oracle Fusion Middleware term for privilege.
expenditure item
The smallest logical unit of expenditure you can charge to a project and task. For example, a time card item or an expense
report item.
862
expenditure type
Classification of cost that you assign to each expenditure item in Project Financial Management applications.
expenditure type class

Specifies how an expenditure item is processed. For example, if you assign the Straight Time expenditure type class to an
expenditure type, Project Financial Management uses labor cost schedules to calculate the cost of an expenditure item with
that expenditure type and expenditure type class.
extensible flexfield
Customizable expansion space, as with descriptive flexfields, but able to capture multiple sets of information within a context
and multiple contexts grouped to appear in a named region of a user interface page. Some extensible flexfields let you group
contexts into categories.
feature choice
A selection you make when configuring offerings that modifies a setup task list, or a setup page, or both.
financial plan type

Category or collection of either project budgets or project forecasts.
financial resource
A resource that uses currency as its unit of measure.
firm burden schedule

A burden schedule of burden multipliers that will not change over time. This is compared to provisional schedules in which
actual multipliers are mapped to provisional multipliers after an audit.
fixed rate type

Rate you set between two currencies that remains constant. For example, a rate set between the euro currency and each
Economic and Monetary Union (EMU) currency during the conversion to the euro currency.
flexfield
A grouping of extensible data fields called segments, where each segment is used for capturing additional information.
flexfield segment
An extensible data field that represents an attribute on an entity and captures a single atomic value corresponding to a
predefined, single extension column in the Oracle Fusion Applications database. A segment appears globally or based on a
context of other captured information.
863
function security
The control of access to a page or a specific use of a page. Function security controls what a user can do.
global area
The region at the very top of the user interface that remains the same no matter which page you're on.
grade
A component of the employment model that defines the level of compensation for a worker.
HCM
Abbreviation for Human Capital Management.
HCM data role

A job role, such as benefits administrator, associated with instances of HCM data, such as all employees in a department.
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.
intercompany billing
Feature that enables you to bill an internal customer for work done on a receiver project and transfer internal revenue or costs
between provider and receiver organizations.
interface table
A database table used for transferring data between applications or from an external application or data file.
interproject billing
Feature that enables you to bill an internal customer for work done on a provider project. The cost of work performed is not
reflected on the receiver project until the project receives an invoice for the work.
inventory organization
An organization that tracks inventory transactions and balances, and can manufacture or distribute products.
invoice business unit

Business unit with the Payables Invoicing business function that is responsible for processing invoice transactions.
invoice distribution
Accounting information for an invoice line, such as accounting date, amount, and distribution combination.
invoice method
Rule defined by the implementation team that determines the calculation method of invoice amounts for contracts during
invoice generation.
864
invoice method classification

Predefined classification for an invoice method that determines the basis for calculating invoice amounts.
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.
job
A generic role that is 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 for a specific job consisting of duties, such as an accounts payable manager or application implementation consultant.
A type of enterprise role.
journal
An element of a journal entry consisting of the name, accounting date, category, ledger, and currency for single currency
journal entries. Used to group journal lines.
journal category
A name used to group journal entries with similar characteristics, such as adjustments, accruals, or reclassifications.
journal entry
Point of entry of business transactions into the accounting system. Chronological record, with an explanation of each
transaction, the accounts affected, and the amounts to increase or decrease each account.
journal line
An element of journal entries consisting of account combinations and credit or debit amounts. Optionally, contains statistical
quantities, currency information for multicurrency journals, and additional information.
journal line rule

A rule that includes options to convert transactional data into a subledger journal line. Conditions can be defined within the
rule so it's only used based on specific attributes of a transaction.
865
journal source
A name that indicates the origin of journal entries, such as payables, receivables, or manual. Used as an attribute in automatic
posting and journal import processes.
key flexfield
Configurable key consisting of multiple parts or segments, each of which have 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.
key flexfield structure

The arrangement of segments in a key flexfield. In some cases, multiple structures can be defined for a single key flexfield.
KPI
Abbreviation for key performance indicator. Key performance indicators (KPIs) measure how well an organization or
individual project meets an operational, tactical, or strategic objective that is critical for the current and future success of the
organization. Examples are: Period-to-Date (PTD) Actual Spent Labor Effort Percentage, PTD Actual Spent Equipment Effort
Percentage, and PTD Actual Margin Percentage.
KPI category
A group of key performance indicators that belong to a specific performance area. Examples are: cost, profitability, financial,
and schedule.
KPI period determination date

Date used to determine the accounting calendar and project accounting calendar periods for performance measure
calculations during key performance indicator (KPI) value generation.
labor costing rule

Determines the rule to process payment for labor resources, such as exempt, nonexempt, or hourly. It is also used for
planning, budgeting and forecasting transactions when the plan type is configured to use actual rates.
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.
legal employer
A legal entity that employs people.
legal entity
An entity identified and given rights and responsibilities under 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 under the purview
of a legal authority.
866
legal reporting unit

The lowest level component of a legal structure that requires registrations. Used to group workers for the purpose of tax and
social insurance reporting or represent a part of your enterprise with a specific statutory or tax reporting obligation.
legislative data group

A means of partitioning payroll and related data. At least one legislative data group is required for each country where the
enterprise operates. Each legislative data group is associated with one or more payroll statutory units.
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.
local area
The main part of the work area, where you perform most of your tasks.
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
A branch of data that serves as a single source of truth.
manual payment
A payment created outside of Oracle Fusion Payables and then recorded in Payables.
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.
natural account
Categorizes account segment values by account type, asset, liability, expense, revenue, or equity, and sets posting,
budgeting, and other options.
867
natural account segment

A chart of accounts segment used to categorize your accounting transactions by account type: asset, liability, owner's equity,
revenue, or expense.
nonlabor resource
An asset or pool of assets. For example, you can define a nonlabor resource with a name PC to represent multiple personal
computers that your business owns.
offering
A comprehensive grouping of business functions, such as Sales or Product Management, that is delivered as a unit to
support one or more business processes.
organization
A unit of an enterprise that provides the framework for performing legal, management, and financial control and reporting.
Organizations can represent departments, sections, divisions, business units, companies, contractors, and other internal
or external units of the enterprise. Organization can be classified as project and task owning organizations, and project
expenditure organizations in Project Financial Management applications.
organization classification
Controls the information that you can set up at the organization level. You can assign multiple classifications to one
organization, or define separate organizations to represent different types of entities. For example, you can classify an
organization as both a legal entity and a department.
organization costing rule

Maps labor costing rules and rate schedules to organizations for labor costing. Also maps rate schedules to organizations for
costing nonlabor items.
organization hierarchy
A tree structure that determines the relationship between organizations.
OWLCS
Abbreviation for Oracle WebLogic Communication Services. Offers the TPCC service to Oracle Sales Cloud and sets up the
calls via SIP integration with the telephony network.
party fiscal classification

A classification used by a tax authority to categorize a party for a tax.
payroll statutory unit

A legal entity registered to report payroll tax and social insurance. A legal employer can also be a payroll statutory unit, but a
payroll statutory unit can represent multiple legal employers.
performance measure
Performance measures are system-defined criterion for performance or schedule that are used to determine if a project is on
track.
868
PL/SQL
Abbreviation for procedural structured queried language.
planning amount allocation basis

Represents the method of distributing financial plan amounts to calendar periods for performance data summarization.
planning options
User-definable options, including plan settings, rate settings, currency settings, and generation options, used to control
planning scenarios. Budget or forecast versions inherit planning options defined for financial plan types. Similarly, project
plans at the project template or project level inherit planning options defined for project plan types.
position
A specific occurrence of one job that is fixed within one department. It is also often restricted to one location. For example,
the position Finance Manager is an instance of the job Manager in the Finance Department.
primary balancing segment value

A segment value used to represent a legal entity in the chart of accounts and automatically balance all intercompany and
intracompany transactions and journal entries.
primary forecast
Financial plan type designated as a primary cost forecast, primary revenue forecast, or both. The versions are used for
specific purposes, for example, as default forecast versions for project performance reporting.
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.
process category
Group of one or more logically related event classes that can be used to restrict which events are processed by the Create
Accounting process.
profile option
User preferences and system configuration options that users can configure to control application behavior at different levels
of an enterprise.
profile option level

The category or layer that defines a profile option. Site, Product, and User are the predefined levels.
profile option level hierarchy

The ordering of profile option levels, where Site is the lowest and User is the highest level. Among the enabled levels, the
preferences configured with the higher level profile option always take precedence.
869
profile option value

The setting mapped to the level of a profile option. A profile option may have multiple values set at different levels, such as
Site or User.
project accounting period

Periods that are maintained by business unit and used to track budgets and forecasts, summarize project amounts for
reporting, and track project status.
project and task owning organization

An organization that can own projects and tasks for the purpose of reporting, security, and accounting.
project enterprise labor resource

A labor resource that you can assign to multiple projects.
project expenditure organization

An organization that can incur expenditures and hold financial plans for projects.
project type
Controls basic project configuration options, such as burdening, billing, and capitalization options, and class categories that
are inherited by each project associated with the project type.
project unit
An operational subset of an enterprise, such as a line of business, that conducts business operations using projects, and
needs to enforce consistent project planning, management, analysis, and reporting.
provider business unit

Business unit with resources that provide services to another project (provider project) or business unit. For cross-charge
transactions, the provider business unit is the expenditure business unit; the project business unit owns the intercompany
billing project.
provider organization
Organization that provides services to a project owned by another organization.
provider project
Contract project that performs work on behalf of another (receiver) project. In interproject billing, the provider project bills the
receiver project through an Oracle Fusion Payables invoice generated by the Update Invoices from Oracle Fusion Receivables
process.
provisional burden schedule

A burden schedule of estimated burden multipliers that are later audited to determine actual rates. You apply actual rates to
provisional burden schedules by replacing the provisional burden multipliers with actual burden multipliers. The application
processes adjustments that account for the difference between the provisional and actual calculations.
870
PSTN
Abbreviation for public switched telephone network which is the network of the world's public circuit-switched telephone
networks.
quick payment
A single payment that you create for one more invoices without submitting a payment process request.
rate-based planning resource

Resource for which cost and revenue are calculated, based on a rate applied to the quantity that's entered in a unit of
measure other than currency.
raw cost
Costs that are directly attributable to work performed. Examples of raw costs are salaries and travel expenses.
receiver business unit

Business unit whose projects receive services from another project or business unit. For cross-charge transactions, the
receiver business unit is the business unit that owns the receiver project.
receiver organization
Organization that receives services provided by the provider organization.
receiver project
Project for which work is performed by another (provider) project. In interproject billing, the receiver project incurs costs from
an Oracle Fusion Payables invoice generated by the Update Invoice from Oracle Fusion Receivables process performed for
the provider project.
recognized revenue
Sum of all revenue distributions created for a billing transaction.
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 data object

Business objects such as project types, rates schedules, and financial plan types that can be shared across organizations.
Define reference data sets if you want to group the values you define for these objects and share them with certain or all
organizations.
reference data set

Contains reference data that can be shared across a number of business units or other determinant types. A set supports
common administration of that reference data.
871
reference data sharing

Facilitates sharing and reuse of common transactional data entities within the parts of a business flow or across
organizations.
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.
reference object
Standardized data model containing reference information owned by other subledger applications and used by the Create
Accounting process to create subledger journal entries from accounting events.
regional area
The collapsible region in the work area that lets you control what's in the local area, for example by selecting a task or running
a search.
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.
related expenditure item

An additional transaction created for an individual item charged to projects.
report
An output of select data in a predefined format that's optimized for printing.
resource breakdown structure

One or more hierarchies of resources, resource types, resource formats, or other resource groupings that are used for
financial and project planning and for viewing planned and actual amounts for a project.
revenue category
Source of revenue for an organization. Revenue categories group expenditure types and event types for revenue and
invoices. Also used to define accounting rules.
revenue method
Rule defined by the implementation team that determines the calculation method of revenue amounts for contracts during
revenue generation.
872
revenue method classification

Predefined classification for a revenue method that determines the basis for calculating revenue amounts.
revenue plan
Common set of instructions for recognizing revenue within a contract. Multiple contract lines on a contract can use the same
or different revenue plans.
reversal method
The method used to reverse an existing journal by switching debit and credit amount or by changing the sign on the amounts.
role
Controls access to application functions and data.
role mapping
A relationship between one or more roles and one or more assignment conditions. Users with at least one assignment that
matches the conditions qualify for the associated roles.
role provisioning
The automatic or manual allocation of a role to a user.
sandbox
A testing environment that isolates untested code changes from the mainline environment so that these changes don't affect
the mainline code or other sandboxes.
scenario dimension members

A scenario dimension is used to differentiate actual cost, current budget, original budget, prior forecast, current forecast, and
variances between different plan types within summarization.
scheduled process
A program that you run to process data and, in some cases, generate output as a report.
security profile
A set of criteria that identifies HCM objects of a single type for the purposes of securing access to those objects. The relevant
HCM objects are persons, organizations, positions, countries, LDGs, document types, payrolls, and payroll flows.
security reference implementation

Predefined function and data security that includes role based access control, and policies that protect functions, and data.
The reference implementation supports identity management, access provisioning, and security enforcement across the
tools, data transformations, access methods, and the information life cycle of an enterprise.
873
segment
See
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.
SOA
Abbreviation for service-oriented architecture.
source
The application from which a transaction originates.
source
Contextual and reference information from subledger applications used in conjunction with accounting rules to create
subledger journal entries.
source system
An external system from a non-Oracle software provider, or internally created, that generates events which are to be
accounted in the Oracle Fusion Accounting Hub.
space
A collaboration feature that supports people working on a common area of interest or goal. Space members can share
content, send messages to one another, track group events and tasks, and more.
spot rate type

Rate you enter to perform conversion based on this rate as of a specific date. This rate applies to the immediate delivery of a
currency.
SQL predicate
A type of condition using SQL to constrain the data secured by a data security policy.
subledger
A low-level ledger that stores and manages the details that substantiate the monetary value stored in the general ledger.
Oracle Fusion Receivables and Oracle Fusion Payables are examples of subledgers.
874
subledger journal entry

A detailed journal entry generated for a transaction in a subledger application.
subledger journal entry line

An individual debit or credit line that is part of a subledger journal entry.
subledger journal entry rule set

A set of rules defining how to generate a complete journal entry for an accounting event.
supporting reference
Stores additional source information about a subledger journal entry line which can be used to establish a subledger balance
for source values for an account.
tax
The classification of a charge imposed by a government through a fiscal or tax authority.
tax exception
A condition or combination of conditions that result in a change from the standard values for a particular product.
tax exemption
A full or partial exclusion from taxes within a given time period.
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, such as determining place of supply or tax
registration, in relation to a tax on a transaction.
875
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.
third-party application source

Non-Oracle application source of transactions.
trading partner
An external party, such as a supplier, in the Oracle B2B application for which electronic documents are sent or from which
documents are received. A trading partner in Oracle B2B corresponds to a supplier site.
transaction object
Standardized data model containing transaction information used by the Create Accounting process to create subledger
journal entries from accounting events.
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 rate type

Rate you enter at journal entry time to convert foreign currency transactions to your functional currency.
value set
A set of valid values against which values entered by an end user are validated. The set may be tree structured (hierarchical).
value-added tax (VAT)

An indirect tax on consumer expenditures that is collected on business transactions and imported goods. Value-added tax
(VAT) is added to products at each stage of their production. If customers are registered for VAT and use the supplies for
taxable business purposes, then they typically receive credit for the VAT that is paid.
WBS
Abbreviation of work breakdown structure. Represents the hierarchy of work that must be accomplished to complete the
project. In Primavera P6 Enterprise Project Portfolio Management, WBSs are structured in levels of work detail, starting with
the completed product and then broken down into identifiable work elements. WBSs correspond to tasks in Oracle Fusion
876
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.
XML filter
A type of condition using XML to constrain the data secured by a data security policy.
877

Implementating Project FInancial Management Rel 9 PDF

Uploaded by

Copyright:

Available Formats

Implementating Project FInancial Management Rel 9 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Implementating Project FInancial Management Rel 9 PDF

Uploaded by

Copyright:

Available Formats

What is the purpose of the document?

What is the purpose of the document?

What topics are covered in the glossary section?

What topics are covered in the glossary section?

Oracle

This guide also applies to on-premise

Part Number E53161-03

Copyright © 2011-2014, Oracle and/or its affiliates. All rights reserved.

2 Define Synchronization of Users and Roles from LDAP 12

3 Define Implementation Users 13

4 Define Enterprise Profile 14

5 Define Financial Reporting Structures 102

6 Define Project Organizations 175

7 Define Users and Security 202

8 Define Automated Governance, Risk, and Performance Controls 205

9 Define Project Portfolio Management Common Reference Objects 206

10 Project Foundation Configuration: Overview 269

11 Project Foundation Configuration: Define Project Calendars and Periods 271

12 Project Foundation Configuration: Define Types and Categorizations 274

13 Project Foundation Configuration: Define Project Roles 290

14 Project Foundation Configuration: FAQs for Enable Automated Project 293

15 Project Foundation Configuration: Define Project Resources 294

16 Project Foundation Configuration: Define Rate Schedules and Costing 304

17 Project Foundation Configuration: Define Project Resource Breakdown 315

18 Project Foundation Configuration: Define Burdening 328

19 Project Foundation Configuration: Manage Project Types 347

20 Project Foundation Configuration: Define Action Controls 355

21 Project Foundation Configuration: Distribute and Install Desktop 357

22 Project Control Configuration: Overview 363

23 Project Control Configuration: Manage Period Profiles 373

24 Project Control Configuration: Manage Spread Curves 378

26 Project Integration Gateway Configuration: Overview 399

27 Project Integration Gateway Configuration: Define Project Management 404

28 Project Integration Gateway Configuration: Define Primavera P6 408

29 Microsoft Project Integration: Overview 419

30 Project Costing Configuration: Define General Costing Setup 422

31 Project Costing Configuration: Define Capital Projects 434

32 Project Costing Configuration: Define Borrowed and Lent Accounting 438

33 Project Costing Configuration: Define Project Costing Integrations 441

34 Project Billing Configuration: Define Contracts Configuration for Project 448

35 Project Billing Configuration: Define Project Invoicing Options 454

36 Project Billing Configuration: Define Project Revenue Options 464

38 Project Billing Configuration: Define Intercompany Project Billing 477

39 Project Billing Configuration: Define Transfer Pricing 502

40 Project Billing Configuration: Define Customer Billing Configuration for 512

41 Project Billing Configuration: Define Taxes for Rapid Implementation 517

42 Project Performance Reporting Configuration: Manage Project Units: 609

43 Project Performance Reporting Configuration: Define Key Performance 613

44 Project Performance Reporting Configuration: FAQs for Define Region 627

45 Manage Project Templates 628

46 Define Subledger Accounting Rules 638

47 Define Approval Management 665

48 Define Help Configuration 666

49 Define Application Toolkit Configuration 671

50 Maintain Common Reference Objects 676

51 Define WebLogic Communication Services Configuration 777

52 Define Client Extensions 780

53 Other Common Setup and Maintenance Tasks 817

54 External Integration 823