3.1 Project Costing

Oracle Fusion Project Portfolio
Management
Project Costing
Release 10
Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Oracle Online Training Materials – Usage Agreement
1. Oracle is pleased to allow its business partner (“Partner”) to download the Materials found on this area of the Site. The Materials provided on or through this area of the Site are
confidential to Oracle and protected by intellectual property laws, and provided to Partner under and pursuant to the terms, conditions and restrictions of Partner’s agreement with Oracle
to participate in the applicable beta program pertaining to the Software (as defined below) (“Beta Trial License Agreement”), as well as any additional terms, conditions and restrictions set
forth in any area of this Site or in any Materials provided on or through this Site. In the event of any conflict or inconsistency between the terms, conditions and restrictions set forth in the
Beta Trial License Agreement and those set forth in any area of this Site on in any Materials provided on or through this Site, the former shall have precedence with respect to Partner’s
access and use of the Site and Materials, provided, however, that notwithstanding anything to the contrary in the Beta Trial License Agreement, Partner will restrict access to and
disclosure of Materials only to its employees who require access to Materials in connection with the Beta Trial License Agreement.
2. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
3. Oracle disclaims any warranties or representations as to the accuracy or completeness of any Materials. Materials are provided "as is" without warranty of any kind, either express,
implied or statutory, including without limitation the implied warranties of merchantability, satisfactory quality, fitness for a particular purpose, accuracy, timeliness and non-infringement
of third-party rights. The information contained herein is subject to change without notice.
4. Under no circumstances shall Oracle be liable for any loss, damage, liability or expense incurred or suffered which is claimed to have resulted from use of these Materials. As a condition of
use of the Materials, Partner agrees to indemnify Oracle from and against any and all actions, claims, losses, damages, liabilities and expenses (including reasonable attorneys' fees) arising
out of Partner’s use of the Materials.
Disclaimer:
This document is for informational purposes only and is intended solely for use in connection with the internal pre-production evaluation and testing of the Software. This is not a
commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or
functionality, and inclusion or not thereof in the commercially available version of the Software, if any, is always at Oracle’s sole discretion. This document is not considered part of the
applicable program documentation.
Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking significant destabilization of the code.
Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 3

Objectives
After completing this session, you should be able to:

 Setup cost collection and transaction sources
 Setup rate schedules
 Setup burdening
 Setup allocations
 Setup capital projects
 Understand capitalized interest
 Setup budgetary controls

Session Agenda
 Overview of Project Costing
 Key Concept - Project Cost Collection Flexfield
 Key Concept - Transaction Integrations
 Key Concept – Rate Schedules and Costing Rules
 Overview – Allocations
 Overview – Capital Projects
 Overview – Capitalized Interest
 Key Concept – Budgetary Controls
 Overview – Job Roles and Duties
 Student Activity
 Review and Discussion

Define Project Costing Configuration
Overview

Navigator > Tools > Setup and Administration > Implementation Projects tab > your implementation
project > Define Project Costing Configuration >

Set up Tasks
Task or Task List Description

Define Project Costing Common Configure descriptive flexfields, value sets, messages and attachments related to Oracle Fusion
Reference Objects Project Costing functionality.
Manage General Costing Setup Configure transaction sources, documents, profile options, and cost collection flexfields related to
Oracle Fusion Project Costing functionality.
Define Allocations Configure options used to allocate overhead costs such as salaries, administrative overhead, and
equipment charges to projects that benefited from the costs.
Define Capital Projects Configure options used to capitalize project costs and place assets in service.
Define Expenditure Extensions Implement client extensions to customize the expenditure transaction process.
Define Project Costing Configure options used to integrate Oracle Fusion Project Costing with Other Applications.
Integrations

Cost Collection Center
Key Concept

Project Cost Collection Center
Overview
• Standardized Cost Collection is

the effort in Fusion to standardize
the way in which project
attributes are captured, validated,
and displayed on documents in
the source applications

Project Cost Processing

Payables Project
. Purchase Order Purchase Order
. Requisitions
Collection
. Expenses Expenses
Inventory
Supply Chain Project Define
. Inventory Project
. Misc Issues Process Cost
Collection
Fields
Supplier Invoices
Time & Labor Project
Third Party
. Timecards Tieback
Excel Upload
• Every module had it’s own way of capturing • Standard cost collection and interface for all project
and interfacing project related costs. related expenditures.

Project Cost Collection Flexfield
Overview
The Cost Collection flexfield allows:
• Inclusion of industry-specific cost code or funding source
or organization-specific attributes in any or all the
documents.
• Greater level of flexibility on the naming, validation, and
ordering of the attributes within each of the documents
that capture them.
• User can specify the billable and capitalizable values in
specific documents, while hiding this value in other
document.

Feature Overview
Cost Collection - Consistent User Experience

Cost Collection - Flexfield Attributes
Project 32 Attributes
Task available for Cost
Expenditure Type Core Required Attributes Collection
Expenditure Organization
Expenditure Item Date
Work Type
Billable Core Attributes
(Derived during import if not entered on transaction document)
Capitalizable
Contract
Contract Line Industry Specific
Funding Allocation
User Defined Attributes 1..10 User Definable for your business process
Reserved Attributes 1..10 Reserved for Future Development
Context Category Sets the context for each document

Project Cost Collection Flexfield
Flexible Implementation Update the flexfield metadata to
change the prompts, validations, or
add additional segments to be
captured along with the standard
project attributes.

Feature Highlights
Standardized Cost Collection
Expenditure Batch
Supplier Invoice
Expense Report
Purchase Order
Segment
Inventory
Project, Task, Expenditure Item Date, Expenditure Type,
Expenditure Organization     
Billable 
Capitalizable 
Work Type 
User-Defined1  
User-Defined2 

Integration Points
Product Entity Context Name
Procurement User Preferences POR: User Preferences
Requisition POR: Requisition
Purchase Order Line PO: Purchase Order Line
Purchase Order Distribution PO: Purchase Order
Inventory Miscellaneous Inventory Transaction INV: Misc. Transactions
Expenses Expense Report Item EXM: Expense Report Line
Payables Distribution Set AP: Distribution Sets
Invoice Line AP: Invoice Line
Invoice Distribution AP: Invoice Distribution
Project Costing Expenditure Batch PJC: Expenditure Batch
Manage Expenditure Items PJC: All
Review Cost Distributions

Comparison with Accounting Flexfield
Accounting Key Project Costing

Feature
Flexfield Flexfield
Extensible to fit varying business requirements. ✓ ✓
Flexible naming and validation. ✓ ✓
Change behavior for each document using Contexts. ✗ ✓
Change behavior for each Ledger. ✓ ✗
Denormalized into code combination, requiring consuming
teams to provide only one attribute to capture ID. ✓ ✗
Inter-segment validations Flex Filter Transaction Controls,

LOV’s

Setup: Define General Costing Setup
Manage Project Standard Cost Collection Flexfield

Transaction Integrations
Key Concept

• The standardized cost interface is

the method used to standardize
the way in which transactions are
interfaced into PPM Cloud from
source applications.

Cost Interface Flow Diagram
START
Yes
Group Transactions
Call Execute Create EI (get next
into Expenditure Perform Perform
pre-processing Transaction item ID and update
Batch and Validations Derivations
extension Controls interface record)
Expenditures
Execute
Create Period-End
Perform Create Related Related New txn
Accrual Yes
Costing EI? Transaction created?
Transactions
Extensions
No No
No
No
Create Labor EI?
Create Cost
Accounting
Distributions
Events
Create Overtime
Yes
EI?
Expenditure Item
Yes Execute
No rejected?
Yes Overtime
Extension
Commit all
Perform Update status
Call Tieback for Call post- successful Reject
final of successfully
integrating processing EIs and related any associated
processing created items in
applications extension items to PA tables, records
steps PATI table
also CDLs
STOP
Process handled in
Indicates Standardized
Indicates a sub
process executes Push, Tiebacks
process
client extensions and Revaldiation
FDD

Transaction Integration
Standardized Interface Standardized Tieback
 Single method = push  Tieback service or API
 Same method for integrating  PPM Cloud sends status and messages
applications, spreadsheet uploads, third to integrating application
party integrations  Status codes have standard lookup –
 PPM Cloud will not read from other consistency across applications
teams data model

• Only one process to interface data
into PPM Cloud
• Less user training on the processes
• Ease of scheduling and monitoring

Cost Interface – Consuming Applications
• Payables
• Push API loads into interface table.
• Additional business logic performed before cost processing.
• Tieback API from Payables reads statuses from interface table and update their data model.
• Supply Chain Management
• Costing
– Push Service loads into interface table.
– Tieback Service sends status to SCM.
• Time and Labor
• Third-Party Applications
• Can use either API or Service for Push and Tieback.
Manage Transaction Sources: Project Documents

Derive Billable Status of Expenditure Items from Work Type
• Determine whether expenditure items are billable depending on the work type.

Derive Work Type for Project Expenditure Items
• Determine whether work type attribute should be derived for expenditure items.

Rate Schedules
Key Concept

Rate Schedules
Overview
• You can define rate schedules for costing, billing, and
planning purposes.
• A labor cost rate schedule maintains hourly cost rates for
employees or jobs
• Schedule types determine usage for rates within rate
schedules
• The schedule types are:
• Job
• Person
• Nonlabor
• Resource Class

Rate Schedules
Job Rate Schedules
Job rate schedules contain rates

used to calculate amounts for the
following types of labor
transactions:
• Actual Cost
• Invoiced Amount
• Revenue Amount
• Planned Cost
• Budgeted Cost
• Forecast Cost
• Borrowed and Lent Cost
The rate is based on the standard hourly rate assigned to a job title in Oracle Fusion
Human Capital Management.

Rate Schedules
Person Rate Schedules
Person rate schedules contain raw
cost rates and billing rates or
markup percentages for labor
transactions and transfer price
amounts. The rates are used in the
following types of labor
transactions:
• Actual Cost
• Invoiced Amount
• Revenue Amount
• Planned Cost
• Budgeted Cost
• Forecast Cost
• Borrowed and Lent Cost
The job or organization is based on the person's assignment in Oracle Fusion Human
Capital Management.

Rate Schedules
Non Labor Rate Schedules
• Define the nonlabor rates and then
associate them with the business
units or expenditure organizations or
both.
• These rate schedules are used to
calculate costs for nonlabor
transactions such as miscellaneous or
usage transactions.
• If the plan type is configured to use
actual rates, the pricing engine also
uses these rates for planning,
budgeting, and forecasting
transactions.

Rate Schedules
Resource Class Rate Schedule
• Create resource class rate schedules

for planning purposes.
• Define rate or markup percentage for
resource classes to use in planning,
budgeting, and forecasting.
• Optionally assign the rate or markup
percentage to a specific organization
for a resource class.
• Assign resource class rate schedules to
the project plan or financial plan
(budgets and forecasts) at the plan
type level or version level.
Note: Rate takes precedence for rate-based transactions where the unit of measure is not currency.
Markup percentage takes precedence for amount-based transaction where the unit of measure is
currency.

Rate Schedules
Labor Costing Multipliers
Use labor cost multipliers to calculate
costs for overtime expenditure item.
1. Assign the labor cost multiplier to
overtime expenditure types.
2. The costing process multiplies the
standard labor cost rate by this
multiplier to calculate the cost for
overtime expenditure items.
3. Specify the effective date range for
the multiplier on expenditure type.

Rate Schedules
Labor Costing Rules
Use the labor schedule type for assigning
and using labor rate schedules to
calculate costs for labor transactions such
as time cards.
Examples of labor costing rules:
• Exempt
• Nonexempt
• Hourly

Rate Schedules
Organization Costing Rules
Labor
• Define and assign labor organization
costing rules and cost rate schedules to
specific business units, to expenditure
organizations, or to both.
Nonlabor
• Each nonlabor resource is assigned an
expenditure type.
• Define rates for specific nonlabor
resources on the rate schedule.
• In a multi-organization environment,
set up nonlabor resources once and
share them across all organizations.
Each organization can have a distinct
rate for the resource that they own.

Rate Schedules
Labor Costing Overrides
Define override rates or rate schedules

for specific persons within specific
business units.
To set up override rates or rate schedules:
• Define a rate or rate schedule depending on the
override type: Rate, Rate Schedule, or
Extension.
• Associate the labor costing rule to a specific
override. If the costing rule is Extension, then
set the override type to Extension.
• Customize and define business-specific rules in
the labor costing client extension when using
the override type of Extension.
The application uses an override rule primarily to determine the labor rate for cost transactions. It
also used for planning, budgeting, and forecasting transactions when the plan type is set to use
actual rates

Burdening
Key Concept

Burdening
Overview
Burdening provides a buildup of raw and burden costs
to represent the total cost of doing business accurately.
• Calculate burdened costs as a buildup of costs using a
precedence of multipliers.
• Beginning with 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 to perform internal costing, revenue
accrual, and billing for any type of burdened costs that
your company applies to raw costs.

Burdening
Terminology
Common terms used:
• 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.
• Burden Structure: Determines how expenditure types are grouped into burden cost bases and what
types of burden costs are applied to the cost bases.
• Burden Schedule: A set of burden multipliers that are used to calculate the burdened cost, revenue,
or bill amount of each expenditure item.
• Burden Multiplier: A numeric multiplier associated with an organization for burden schedule
revisions, or with burden cost codes for projects or tasks

Burdening
Simple View of Burden Cost Calculation
• Raw costs are directly attributable to work
performed. Examples of raw costs are salaries
and travel expenses.
• Burden costs are legitimate costs of doing
business that support raw costs and cannot be
directly attributed to work performed.
• Total burdened cost is the cost of an expenditure
item, including the raw cost and burden costs.

Burdening
Storing Burden Costs
• Accounting and reporting requirements determine the
method to use for storing burden costs.
• The burden storage method is defined on each project
type. You cannot override the method on individual
projects.
• Options available:
1. Burden cost stored on the same expenditure item.
2. Burden cost stored as a separate expenditure item.
3. Burden cost on a separate project

Burdening
Burden Cost Base Types
The burden cost base type indicates how to use the cost bases.
• PPM Cloud provides two cost base types:
Optionally define additional cost base types for nonburden uses, such as billing extensions.

Burdening
Burden Cost Bases
• Group raw costs (represented by expenditure
types) against which to apply burden costs
(represented by burden cost codes).
• The grouping takes place on the burden
structure.
• Define as many costs bases as needed.

Burdening
Burden Cost Codes
A burden cost code is a classification of raw costs.
• For example, if labor costs receive both fringe and overhead

burden, then define a cost code for each type of burden.
• For each burden cost code in the burden structure, 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.
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.
• Assign the expenditure types to the appropriate reference data

sets. Note: The order of the burden cost codes has no effect on the total
burdened cost with either additive or precedence burden
• Assign the Burden Transaction expenditure type class to any structures.
expenditure types that you plan to assign to burden cost codes.

Burdening
Burden Structures
Burden structures determine how expenditure types are grouped
into burden cost bases and what types of burden costs are applied
to the cost bases. Components of a Burden Structure
• A burden structure defines relationships between burden cost
bases and burden cost codes, and between burden cost bases
and expenditure types.
• The burden structure assigned to the burden schedule version
determines whether calculations are additive or based on the
precedence assigned to each cost code.

Burdening
Additive Burden Structures
• An Additive burden structure to applies each burden
cost code assigned to a cost base where burden costs
are calculated with the same precedence.
• Additive schedules automatically provide a default Cost Type Calculation Amount
precedence value of 1 to each burden cost code in the
structure.
Raw Cost Not Applicable 1,000.00
Cost Code Precedence Multiplier Overhead 1,000 x 0.10 100.00
Overhead 1 0.10 Material Handling 1,000 x 0.10 100.00

Material Handling 1 0.10 General Administrative
1,000 x 0.10 100.00
Costs
General
Administrative Costs 1 0.10
Burdened Cost 1000 + 100 + 100 + 100 1,300.00

Burdening
Precedence Burden Structures
• A Precedence burden structure specifies the
order in which each burden cost code is applied
to raw costs.
Cost Type Calculation Amount
Raw Cost Not Applicable 1,000.00
Cost Code Precedence Multiplier Overhead 1,000 x 0.10 100.00
Overhead 10 0.10 Material Handling (1,000 +100) x 0.10 110.00

Material Handling 20 0.10 General Administrative
(1,000 +100+110) x 0.10 121.00
Costs
General
Administrative Costs 30 0.10
Burdened Cost 1000 + 100 + 110 + 121 1,331.00

Burdening
Burden Schedules
Assign multipliers to organization-burden cost
code combinations.
• The multiplier specifies the amount by which to multiply
the raw cost to obtain the burden cost amount. The
expenditure organization on an expenditure item
determines the multiplier for burden calculation.
Multipliers cascade down the selected organization
hierarchy for the version.
• If a multiplier is not available for a child organization, then
processing continues up the hierarchy until it finds a
parent organization with a multiplier.
• Note that an organization multiplier schedule hierarchy is Burden schedule versions define the date range within
really a hierarchy of exceptions. Define the multipliers for which multipliers are effective.
an organization only to override the multipliers of its Build the burden schedule to make the burden schedule
parent organization versions active and available for use.

Burdening
Firm and Provisional Burden Schedules
Firm Burden Schedule
• A burden schedule of burden multipliers that will not
change over time.
Provisional Burden Schedule
• A burden schedule of estimated burden multipliers
that are later audited to determine actual rates.
• Apply actual rates to provisional schedules by
replacing the provisional burden multipliers with
actual burden multipliers.
• Oracle Fusion Projects processes adjustments that
account for the difference between the provisional
and actual calculations.

Burdening
Burden Multiplier Example
The parent organization, Headquarters, has two defined
multipliers:
• Overhead with a multiplier of 2.0.
• Administrative with a multiplier of 3.0.
Child organizations can have override multipliers defined, or can

use the rates from their parent organizations.

Burdening
Project Status Controls
Use project status controls to determine whether
burden transactions are created at various stages
of a project.
• By default, all project statuses to which you
assign a system status of Approved allow the
creation of burden transactions.
• Identify the project statuses for which you want
to allow the creation of burden transactions,
and update the status controls accordingly.
Review and update project statuses to allow the
creation of burden transactions.

Burdening
Project Types: Burdening Options
A project type controls basic project configuration
options, such as burdening, billing, and capitalization
options, and class categories, and is a primary
classification for the projects your business manages.
• Configure burdening options when you set up a project
type.
• The burdening options are inherited by each project
associated with the project type.

Allocations
Overview

Allocations
Overview
Allocation is distribution of certain costs to projects

and tasks within or across organizational units.
 Overhead costs such as salaries, administrative
overhead, and equipment charges are allocated to
projects that benefit from the costs.
 To allocate across business units, ensure that target
projects are enabled for cross-charge processing and
the target selection of allocation rule is across business
units.
Note: You cannot allocate the source amount to projects in other

business units that are enabled for capitalization.

Allocations
Glossary
Term Definition
Allocation Rule A set of attributes that define how to allocate amounts in the source pool to target projects and
tasks.
Allocation Method Method that determines how an amount accumulated during the allocation generation period is
distributed to projects and tasks. The two allocation methods are full and incremental.
Basis Method The method that the allocation rule uses to allocate source pool amount to target projects and tasks.
Source Pool A combination of all source amounts defined by an allocation rule. These costs comprise
summarized projects costs, posted ledger account costs, or fixed amounts.
Targets The identified projects and tasks to receive allocation amounts. Allocation rules specify the targets.
Offsets Reversing transactions that balance allocation transactions with the source or other project.

Allocations
Allocation Rule Components
Term Definition
Allocation Rule Key Define the allocation rule header which includes key attributes such as the allocation method, basis
Attributes method, and other key attributes.
Allocation Transaction Define the allocation transaction attributes such as Expenditure Organization, Expenditure Type
Attributes Class, and Expenditure Type. All the generated transactions for this allocation rule have these
attributes.
Sources Define the source of amounts to allocate. The source amount class and source amount type
determine the amounts to be included into the source pool.
Targets Define the target projects and tasks to receive the allocation.
Basis Define the method to divide the source amount among the target projects and tasks.
Offsets Optionally, define offset transactions, which are reversing transactions, that are used to balance the
allocation transactions.

Allocations
Rule Components
Allocation Rule Key
Attributes
Allocation
Transaction
Attributes
Offsets
Source Basis
Targets

Allocation
Allocation Sources
Sources
• Project Sources: Specify source projects and tasks or use criteria
such as a project type or a classification to identify the eligible
source projects during generation. Specify a reporting resource
breakdown structure and resources to further detail the eligible
source amounts.
• Ledger Sources: Specify one or more ledger accounts as an
allocation source. Allocation generation considers posted
amounts for a ledger account when calculating source pool
amounts. Summary accounts cannot be used on allocation rules.
• Fixed Amount: Specify an amount to include in the source pool.

Allocation
Allocation Targets
Identify the projects

Specify the percentage
and tasks that receive
of the source pool to
the allocation
allocate to the target
Optionally add target
lines and select the
Exclude check box to
exclude projects or
tasks

Allocations
Allocation Basis
Define Allocation Basis

• The allocation rule uses the attributes on the Basis tab to apportion the source pool
among the target projects and tasks.
• Select a basis method from the list and specify the basis details:
• Spread Evenly
• Target Percentage and Spread Evenly
• Prorate
• Target Percentage and Prorate
• Client Extension (On Premise Only)
• Specify a value for the Allocation Method for Zero-Basis Amounts to determine
how to process a prorate-based allocation rule when the total basis amount is zero.
• Optionally, define offsets to balance the allocation transactions with the source or
another project.

Capital Projects
Overview

Setup: Define Capital Projects
Task Name
Manage Standard Unit Costs
Manage Expenditure Types: Proceeds of Sale Indicator

Manage Project Types: Capitalization Options
Manage Project Statuses: Asset Capitalization Status Control
Implement Project Asset Capitalization Extensions

Manage Standard Unit Costs
• Define standard unit costs for each asset book and asset category combination. This is used as an
asset cost allocation method to allocate costs among assets.

Manage Expenditure Types: Proceeds of Sale Indicator
• Define unique expenditure types to classify and account for the amounts to enter and record proceeds
of sale amounts for retirement cost processing.

• Configure how to capitalize assets for projects of this type.

• Configure how to capitalize assets for projects of this type.

Setup: Define Capitalized Interest
Manage Project Statuses: Asset Capitalization Status Control

Setup: Define Business Unit Implementation Options
Configure Project Accounting Business Function: Retirement Processing
Indicator
To enable retirement cost processing features, select the retirement cost processing option in the business
unit implementation options.

Capitalized Interest
Overview

Task Name
Manage Capitalized Interest Rates
Manage Capitalized Interest Rate Schedules
Manage Project Types: Default Interest Rate Schedule
Manage Project Statuses: Capitalized Interest Generation Status Control
Implement Capitalized Interest Extensions



Manage Capitalized Interest Rate Schedules

Manage Project Types: Default Interest Rate Schedule

Manage Project Statuses: Capitalized Interest Generation Status Control

Budgetary Controls
Key Concept

Budgetary Control and Encumbrance Accounting Separation
Account Structure: Dept-Account
Annual Calendar
Budgetary Control Fund Budgetary

Budgetary Control Transaction
Balances Control
Cube
Transactions
Budgetary Control
GL
SLA Journal GL Journal GL Balances
Cube
Encumbrance Accounting
Monthly Calendar Account Structure:

Fund-Dept-Account-Program-
Location
Budgetary Control Enabled for Each Business Unit
• Exceptions can be added to bypass budgetary control for specific

transaction sources and documents.
• Setup task: Manage Budgetary Control
Budgetary Control Enabled for Financial Plan Type
• Default Controls set at Project and Top Resource levels.

• Individual Top Resources can be given different control levels
using the supplemental rules on the control budget.
Roles and Duties
Overview

Job Roles & Associated Duty Roles
Job Role Associated Duty Role
Project Application Administrator Projects Administration Duty
• Project Costing Administration Duty
• Project Foundation Administration Duty
• Subledger Accounting Method
Maintenance Duty

Job Roles & Associated Duty Roles
Job Role Associated Duty Role
Financial Application Administrator Payables Administration Duty
Expense Manager Expense Policies and Rules Administration Duty
Warehouse Manager Inventory Administration Duty
• Inventory Transaction Sources and Types
Management Duty

Duty Roles & Tasks
Duty Role Associated Tasks
Project Costing Administration Duty • Manage Allocation Rules
• Manage Standard Unit Costs
• Manage Capitalized Interest Rates
• Manage Capitalized Interest Rate Schedules
Project Foundation Administration Duty • Manage Transaction Sources: Project Documents
• Manage Expenditure Types: Proceeds of Sale Indicator
• Manage Project Types: Capitalization Options
• Manage Project Statuses: Asset Capitalization Status Control
• Manage Project Types: Default Interest Rate Schedule
• Manage Project Statuses: Capitalized Interest Generation Status Control
• Manage Transaction Sources: Create Related Items Indicator
• Manage Transaction Sources: Third-Party Sources and Documents
• Configure Project Accounting Business Function: Retirement Processing
Indicator

Duty Roles & Tasks
Project Foundation Administration Duty • Manage Project Standard Cost Collection Flexfield: Purchasing
(continued) • Manage Project Standard Cost Collection Flexfield: Payables
• Manage Project Standard Cost Collection Flexfield: Expenses
• Manage Project Standard Cost Collection Flexfield: Inventory
• Manage Transaction Sources: Preprocessing Extension
• Manage Transaction Sources: Postprocessing Extension
• Manage Transaction Sources: Receiving Documents
• Manage Transaction Sources: Payables Documents
• Manage Transaction Sources: Expenses Documents
• Manage Transaction Sources: Inventory Documents

Duty Roles & Tasks
Subledger Accounting Method Maintenance • Manage Account Rules: Purchasing
Duty • Manage Account Rules: Receipt Accounting
• Manage Account Rules: Payables
• Manage Account Rules: Cost Management
Payables Administration Duty • Manage Distribution Sets
Expense Policies and Rules • Manage Expense Report Templates
Administration Duty
Inventory Administration Duty • Manage Inventory Transaction Sources and Types

Student Activity

Activities
1. Defining a Flexfield Segment Value Set
2. Creating Transaction Source, Document and Document Entry
3. Creating a Nonlabor Rate Schedule
4. Creating a Burden Cost Code
5. Creating a Burden Cost Structure
6. Creating a Burden Schedule

Review and Discussion

Define Project Costing Configuration Highlights
In this session, you should have learned how to:

 Setup cost collection and transaction sources
 Setup rate schedules
 Setup burdening
 Setup allocations
 Setup capital projects
 Understand capitalized interest
 Setup budgetary controls

3.1 Project Costing

Uploaded by

Copyright:

Available Formats

You might also like

3.1 Project Costing

Uploaded by

Document Information

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

3.1 Project Costing

Uploaded by

Copyright:

Available Formats

Oracle Fusion Project Portfolio

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 3

After completing this session, you should be able to:

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Task or Task List Description

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

• Standardized Cost Collection is

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Project Cost Processing

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Accounting Key Project Costing

Inter-segment validations Flex Filter Transaction Controls,

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

• The standardized cost interface is

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. |

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 29

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 30

Job rate schedules contain rates

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 31

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 32

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 33

• Create resource class rate schedules

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 34

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 35

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 36

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 37

Define override rates or rate schedules

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 38

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 39

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 40

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 41

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 42

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 43

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 44

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 45

• For example, if labor costs receive both fringe and overhead

Assign an expenditure type to each burden cost code when

• Assign the expenditure types to the appropriate reference data

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 46

Copyright © 2015 Oracle and/or its affiliates. All rights reserved. | 47