Professional Documents
Culture Documents
DISCLAIMER
This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle.
Your access to and use of this confidential material is subject to the terms and conditions of your Oracle software license and service
agreement, which has been executed and with which you agree to comply. This document and information contained herein may not
be disclosed, copied, reproduced or distributed to anyone outside Oracle without prior written consent of Oracle. This document is
not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or
affiliates.
This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade
of the product features described. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or functionality described in this document
remains at the sole discretion of Oracle.
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.
2 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
TABLE OF CONTENTS
Purpose Statement 2
Disclaimer 2
Distribute Payroll Amounts Using Labor Schedules 5
Overview 5
Labor Schedules 5
Manage Labor Schedules 8
Import & Distribute Payroll 9
Processing Logic 10
Process Parameters 11
Manage Labor Costs 12
Labor Distribution Costs Management Matrix 13
Manage Labor Costs - Resolve Errors 13
Manage Labor Costs – Make Adjustments 14
Retrieving data for Analysis 14
Labor Distribution Oracle Transactional Business Intelligence (OTBI) 14
Excel Utility 16
Assumptions / Pre-Requisites 32
Frequently Asked Questions 33
Does Labor Distribution replace Timecards? 33
Cannot find the Non-Project Labor Costs in General Ledger? 33
Non-Project Labor Costs not being picked up in Create Accounting? 33
Labor Distribution Labor Costs not displaying in Manage Unprocessed Costs? 33
User with Labor Distribution Administrator role is not seeing the right list of people based on the
security setup? 33
3 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
4 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
DISTRIBUTE PAYROLL AMOUNTS USING LABOR SCHEDULES
The ‘Distribute Payroll Amounts Using Labor Schedules’ feature is commonly referred to as ‘Labor Distribution.’
Labor distribution capabilities provide for a rule-based distribution of payroll costs to project / award or general ledger accounts. The
core component of the feature is the Labor Schedule. These labor schedules specify a time period and percentage to distribute a
person’s labor cost to a project / award or general ledger account combination. Payroll information from any source system is
imported and distributed efficiently via the labor schedules.
This independent and efficient, percentage-based distribution of high-volume labor costs reduces the effort on individual project
resources and administrators.
This feature is available for both sponsored and non-sponsored projects.
Overview
The image below is an illustration of the scope of the Labor Distribution business processes:
Labor Schedules
Labor schedules are the core object to the entire process and have three components: (1) Labor Schedule Header, (2) Labor Schedule
Version, and (3) Labor Schedule Version Distribution Rules. The labor schedule headers define the highest level of a labor schedule
and relate to the “type” by ensuring the attributes required are properly defined. The attributes are used to evaluate the payroll cost
to determine the applicable version and rules for distributing the cost. Since there are multiple types of labor schedules, an order of
precedence is imposed on payroll costs imported to decide which labor schedule to apply, when more than one type is applicable for
the same day. First, understanding the key business rules at each level is important:
1. Headers
a. Defines the “type” of labor schedule
b. The types available are:
a. Assignment
b. Assignment Element
c. Element
1. The ability to create and maintain these labor schedule types can be removed. See Remove
Element Level Labor Schedule Maintenance Privilege section for more information.
2. Versions
a. Only one Version can be in a status of “Active” for any given day within a type
a. For example, Assignment type for July 1, 2020 to June 30, 2021 can be “Active” and Assignment
Element type can also be “Active” for the same or overlapping time period (see image below that
illustrates this overlap)
b. If set to status of “Active”, start and end dates cannot be changed and cannot be set back to New
c. If set to status of “Inactive”, start and end dates cannot be changed and cannot be set back to “New”
a. Inactive versions can be set to status of “Active” as long as it does not overlap dates with another active
labor schedule
3. Distribution Rules
a. Total of all Distribution Rules can be less then 100% but cannot be greater
5 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
a. The Import Payroll Costs process will generate a “differential” cost to distribute the total payroll cost
b. Each Distribution Rule percentage must be greater than 0 and less than or equal to 100%
The image below illustrates a set of Labor Schedules and their components.
Distribution Rule
Version
P1-T1-A1 (50%)
Header Version 1 : July 1st 2019 -
June 30th 2020 : ACTIVE
GL: 000-001-0400 (50%)
Larry Scanlon - Analyst
Assignment (20B)
June 30th 2020 : INACTIVE
GL: 000-001-0400 (50%)
P1-T1-A1 (50%)
Hector Campos - Project
Manager Version 2 : July 1st 2019 -
June 30th 2020 : ACTIVE
GL: 000-001-0400 (50%)
P2-T1-A1 (50%)
Version 1 : July 1st 2019 -
June 30th 2020 : ACTIVE
GL: 000-001-0510 (50%)
Larry Scanlon - Analyst -
Parking
There are three Labor Schedule Types illustrated in the image above – (1) Assignment, (2) Assignment Element, and (3) Element.
Enabling labor schedules at an “Assignment Element” level will allow for different distribution rules for a specific person, assignment,
and pay element. Illustrated in the image, is that Larry Scanlon would have a specific labor schedule for “Parking” payroll costs,
defined by a different pay element on the imported payroll cost record(s). The “Element” type allows for all payroll costs, regardless
of person assignment to be distributed to specified rules during certain time periods for an entire business unit.
The Import Payroll Costs process order of precedence used to decide which labor schedule to apply to a payroll cost is:
1. Assignment Element
2. Element
3. Assignment
The table below describes the distribution of payroll based on the labor schedules illustrated above. The Import Payroll Costs process
evaluates the cost records matching the attribute combination to labor schedule Versions and distribution rules that apply. View the
recorded demo available here for reference.
Larry Scanlon Version 1 1. Project1- This version is in an ACTIVE status and will be used in the Import
(Analyst) Task1- Payroll Costs process to distribute applicable payroll costs.
Start = July 1st,
Award1
Assignment 2019 Payroll costs imported that match Larry Scanlon and his assignment
(50%)
type of Analyst with pay period start and end dates between July 1st, 2019
End = June 30th,
and June 30th, 2020 will be distributed as defined by the rules.
2020
6 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
Header Version Distribution Explanation of Use
Rules
Larry Scanlon Version 1 1. Project2- This version is in an ACTIVE status and will be used in the Import
(Analyst – Task1- Payroll Costs process to distribute applicable payroll costs with the
Parking) Start = July 1st, Award1 matching Pay Element attribute of “Parking”.
2019 (50%)
Payroll costs imported that match Larry Scanlon, his assignment of
Assignment /
End = June 30th, 2. GL: 000- Analyst, and Pay Element of “Parking” with pay period start and end
Element type
2020 001-0510 dates between July 1st, 2019 and June 30th, 2020 will be distributed
(50%) as defined by the rules.
Status = ACTIVE
Based on the precedence, this rule takes precedence for these specific
payroll records.
Larry Scanlon Version 2 1. GL: 000- This version is in a NEW status and will NOT be used in the Import
(Analyst) 001-0510 Payroll Costs process to distribute applicable payroll costs.
Start = July 1st,
(100%)
Assignment 2020 Payroll costs imported that match Larry Scanlon and his assignment
type of Analyst and the pay period start and end dates are between July
End = June 30th,
1st, 2020 and June 30th, 2021 will be rejected.
2021
Status = NEW
Larry Scanlon Version 2 1. GL: 000- This version is in an ACTIVE status and will be used in the Import
(Analyst – 001-0510 Payroll Costs process to distribute applicable payroll costs with the
Parking) Start = July 1st, (100%) matching Pay Element attribute of “Parking”.
2019
Payroll costs imported that match Larry Scanlon, his assignment of
Assignment /
End = June 30th, Analyst, and Pay Element of “Parking” with pay period start and end
Element type
2020 dates between July 1st, 2020 and June 30th, 2021 will be distributed
as defined by the rules.
Status = ACTIVE
Based on the precedence, this rule takes precedence for these specific
payroll records and other pay elements will be rejected as defined in
the row above.
Hector Campos Version 1 1. Project4- This version is in an INACTIVE status and will NOT be used in the
(Project Task2- Import Payroll Costs process to distribute applicable payroll costs.
Start = July 1st,
Manager) Award4
2019
(50%)
End = June 30th,
2. GL: 000-
2020
001-0400
Status = INACTIVE (50%)
Hector Campos Version 2 1. Project1- This version is in an ACTIVE status and will be used in the Import
(Project Task1- Payroll Costs process to distribute applicable payroll costs.
Start = July 1st,
Manager) Award1
2019 Payroll costs imported that match Hector Campos and his assignment
(50%)
of Project Manager with pay period start and end dates between July
End = June 30th,
2. GL: 000- 1st, 2019 and June 30th, 2020 will be distributed as defined by the
2020
001-0400 rules.
Status = ACTIVE (50%)
Hector Campos Version 3 1. GL: 000- This version is in an ACTIVE status and will be used in the Import
(Project 001-0510 Payroll Costs process to distribute applicable payroll costs.
Manager) (100%)
7 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
Header Version Distribution Explanation of Use
Rules
Start = July 1st, Payroll costs imported that match Hector Campos and his assignment
2020 of Project Manager with pay period start and end dates between July
1st, 2020 and June 30th, 2021 will be distributed as defined by the
End = June 30th,
rules.
2021
Status = ACTIVE
Hector Campos NONE EXIST There is no Labor Schedule for this person and assignment to be used
(Director) in the Import Payroll Costs process to distribute applicable payroll
costs.
Payroll costs imported that match Hector Campos and his assignment
of Project Manager will be rejected.
Car Allowance Version 1 1. GL: 000- The Import Payroll Costs process will distribute any payroll costs for
(Vision City 410-0000 assignments in the business unit of Vision City Operations that have
Start = July 1st,
Operations) (100%) a pay element of Car Allowance. This type of labor schedule is the
2019
second order of precedence, so if any labor schedules for Car
End = June 30th, Allowance exist at a person assignment element level for the same
2020 days, those labor schedules will take precedence for the applicable
days.
Status = INACTIVE
Payroll Costs for Hector Campos and Larry Scanlon imported that
have Car Allowance as the pay element with pay period start and end
dates between July 1st, 2019 and June 30th, 2020 will be distributed
as defined by the rules.
Parking Version 1 1. GL: 000- The Import Payroll Costs process will distribute any payroll costs for
(Vision City 710-0000 assignments in the business unit of Vision City Operations that have
Start = July 1 , st
Operations) (100%) a pay element of Parking. This type of labor schedule is the second
2019
order of precedence, so if any labor schedules for Parking exist at a
End = June 30th, person assignment element level for the same days, those labor
2020 schedules will take precedence for the applicable days.
Status = INACTIVE
Payroll Costs for Hector Campos imported that have Parking as the
pay element with pay period start and end dates between July 1st,
2019 and June 30th, 2020 will be distributed as defined by these
rules.
Payroll Costs for Larry Scanlon imported that have Parking as the
pay element with pay period start and end dates between July 1st,
2019 and June 30th, 2020 will be distributed as defined by the
Assignment Element labor schedule above for Larry.
The Labor Schedule Type radio button defaults to Assignment in the find page. The user can switch to Element labor schedule
management.
1. Once a person and assignment combination or element is selected, the user will navigate to the Manage Labor Schedules
page.
8 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
a. This page is in the context of a person and assignment or element.
b. Person Assignment ()
1. If the person chosen has multiple assignments, the user can switch between assignments by using the
drop-down menu in the page heading section.
2. The Element attribute on the page provides the user with the list of assignment element labor schedules
that exist.
1. User can add an Assignment Element labor schedule by using the “+” icon to add an element
labor schedule within the person assignment.
3. The “View All” button provides the user a read-only view of all labor schedules associated to this person
assignment for analysis and exporting if needed.
1. This provides for viewing multiple labor schedule versions to see the succession of dates and
any gaps that may exist that will cause rejections of imported payroll costs.
2. This will also display any Element level labor schedules for the person assignment business
unit, so the user is aware they will take precedence of any Assignment or Assignment Element
labor schedules of overlapping dates.
c. Element
1. If the element chosen has multiple existing labor schedules for multiple business units, the user can
switch by using the drop-down option in the Business Unit field.
2. Users can add an Element labor schedule by using the “+” icon to add an element labor schedule within
business units the user has access to (see the security section below for assignment business unit access to
Labor Distribution Administrator role).
3. The “View All” button provides the user a read-only view of all labor schedules associated to this
element for analysis across business units and exporting if needed.
1. This provides for viewing multiple labor schedule versions to see the succession of dates and
any gaps that may exist that will cause rejections of imported payroll costs.
d. Once a labor schedule version is saved, regardless of type, the user can change the Status by double clicking the
value. While entering the distribution rules, validations will occur ensuring:
1. Project, task, or award minimum start date is less than the end date of the labor schedule version.
2. Project, task, or award minimum end date is greater than the start date of the labor schedule version.
Labor Schedules can be interfaced from an external system by using the File-Based Data Interface for Labor Schedules. See
Assignment Labor Schedules FBDI.
1. Initiate the import and distribute process by loading the transactions to the interface table.
9 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
a. For more information on the interface process, see the Import Payroll Costs section of the File Based Data Import
for Oracle Project Portfolio Management Cloud guide.
2. After the interface table is loaded, the Import Payroll Costs process will be executed. The Import Payroll Costs process
imports from the interface table, validates and processes the transactions to create project cost distributions. The exceptions
for invalid transactions are tracked in the Manage Labor Costs page and in the Import Payroll Costs Report. Fix the errors
and resubmit the process.
a. For more information on this topic, see Manage Labor Costs section below.
Processing Logic
The Import Payroll Costs process order of precedence used to decide which labor schedule to apply to a payroll cost is:
1. Assignment Element
2. Element
3. Assignment
See the Labor Schedules overview section above for more detail explanation.
The pay period defined on the payroll cost must be able to be fully distributed by one or the combination of more than one Active
labor schedules start and end dates, as well as the Project, Task, or Award start and end dates. The persons assignment start date or
end date are used if needed to calculate a daily rate. For Example, if the person assignment is terminated 5 days into a 10 day pay
period, the daily rate will be calculated for 5 days only and the processing end date will be the assignment end date.
The labor cost status depends on the status of all distributions. If any one of the distributions fails, the labor cost will be in an Error
status. This is to ensure that the labor cost is completely distributed before its status is set to Success.
Key attributes to the processing are:
ii. The start date and end date will be matched to the Pay Period Start and End Dates of the payroll cost to
see if it covers the span or another Active labor schedule in combination covers the entire pay period.
a. Must be able to be fully distributed based on one or more labor schedule versions start and end dates, and any
project, task, or award start and end dates.
i. This applies to all “types” of Labor Schedules
b. Net working days between Pay Period start and end date is used to calculate the daily rate
i. Net working days are weekdays only
ii. Example:
1. Start Date = Monday April 13th, 2020
2. End Date = Friday April 24th, 2020
3. Net working days = 10 days
3. Project, Task, and / or Award start and end dates
10 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
a. Used in conjunction with the start and end date of the labor schedules to ensure full distribution of cost.
Payroll Cost
Expenditures
DOD Project September 1, 2019 $476.19 10 Net-working days at daily rate of $47.62
NSF Project September 16, 2019 $523.81 11 Net-working days at daily rate of $47.62
Process Parameters
The Import Payroll Costs parameters are:
1. Business Unit
a. Business Unit of the Person / Assignment associated to the payroll cost
2. Process Mode
a. All
i. Interface records in a status of Error or New will be processed
b. Error
i. Interface records that failed the import process and based on an attribute of the labor schedule, such as
failing funds check on the project being distributed
c. New
i. Interface records that have not been processed at all
11 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
4. Assignment (Error Mode Only)
a. Choose a person assignment combination that has records in the interface table in an error status
5. Batch Name
a. Choose a batch name that exists in the interface table to import and distribute the costs
a. Define a pay period end date to process all records in the interface table that match that date
The Import Payroll Costs Report is available to be run independently of the Import Payroll Costs process. This is to be used in case of
an error that causes the interface records to get into an unexpected status. This process will rerun based on the prior Process ID
provided and clean up the interface records if needed.
b. These attributes will be validated during the import process and if not found the payroll record will be rejected
2. Pay Element
a. With release 20D, the Pay Element will be validated to the Pay Element object in the Human Capital Management
(HCM) Payroll object if Element.
i. The 20B initial release of the labor distribution feature allowed for Person / Assignment labor schedules
with any value in the Element Type attribute.
b. To create Elements, use the Element HCM setup task.
Page Components:
1. Analytic
a. The analytic is a static graph, that reflects the count and amount of total errors as well as the last three pay periods.
12 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
2. Filters
a. Use one or more filter options to analyze data.
b. Recommended to create a Saved Search that will be applied when the page opens.
3. Key Attributes
a. Transaction Number
i. The Transaction Number on the Distribution Rule record can be used to look up the expenditure and see
the resulting accounting that occurred
Labor Cost (Status) Manage Labor Costs page Manage Project Costs page Period Close Exceptions
Report
Project Cost (Error) • View errors • Not available • Not available
• Process Cost
Non-Project Cost (Error) • View errors • Not available • Not available
• Process Cost
Project Cost (Success) • View results • View project cost details • Pending transaction
• Process Cost (reversal and • *Adjustments available until Create
re-import of parent Labor except for: Accounting process
Cost) • Split complete for these
• Transfer project costs
• Split and
Transfer
• Reverse
Non-Project Cost (Success) • View results • Not available • Not available
• Process Cost – reversal and (Available in Sub-Ledger
re-import of parent Labor Accounting work area)
Cost
* These adjustments are not allowed in Manage Project Costs because the source labor costs could be redistributed in Labor Distribution causing the
costs to get reversed in different sources. Resolving issues of labor costs at the source is recommended.
13 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
Reminder, if any one of the distributions has errors, the labor cost will be in an error status. This ensures that full distribution of the
labor cost.
14 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
This data allows for detail and summary or trend analysis as well as analytics that can be used to prevent issues. For example,
reporting on projects ending in the next 30, 60, or 90 days that have labor schedules associated will prevent labor cost errors.
With the volume of labor costs, the ability to summarize to analyze and troubleshoot errors in the payroll costs distribution process
will be essential.
If the system generated roles were used to create custom roles prior to the release of the OTBI subject areas, you will need to add the
privileges below to the appropriate custom roles to enable access to these subject areas:
• In the Public Person option chose View All People to allow user to see Person Names in OTBI when looking at Labor Costs
15 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
Excel Utility
Leveraging the labor distribution related REST services and this tool will provide an additional flexibility to evaluate data. The four
REST services are defined in more detail in the “REST API for Oracle Project Portfolio Management Cloud” documentation here -
https://docs.oracle.com/en/cloud/saas/project-management/20b/fapap/index.html.
The four REST Services are:
Overview
For Labor Distribution, there are multiple seeded accounting objects.
There is a new Event Class of Non-Project Labor Costs created for this feature. To incorporate the new event class into the Project
Costing subledger, run the Update Subledger Application Options. Background on this process can be found in the Implementation
Guide “Oracle Financials Cloud Implementing Subledger Accounting”. The information below is an excerpt:
1. Manage Subledger Accounting Options
• This task is accessed from the Setup and Maintenance work area. The page is displayed in the context of a primary
or secondary ledger. All registered subledger applications are displayed. If you created additional accounting event
classes after initial ledger setup, run the Update Subledger Application Options process to incorporate these event
classes.
There is a seeded Subledger Journal Entry Rule Set named Non-Project Labor cost. This is to account for the two types of non-project
costs generated from the labor distribution Import Payroll Costs process:
1. Non-project labor costs specified on the labor schedule:
a. GL Account specified labor schedule distribution rule
b. Journal Line Rule = Imported Non-Project Labor Cost
16 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
2. Non-project labor costs generated to complete the differential between the labor schedule distributions total and 100%,
ensuring full distribution of the payroll cost:
a. If an Active Version has Distribution Rules that do not total 100%, the Import Payroll Costs process will create a
cost distribution to equal the differential.
b. Journal Line Rules = Non-Project Labor Cost, Non-Project Labor Cost Clearing, Non-Project Labor Cost Reversal,
and Non-Project Labor Cost Clearing Reversal
To simply add the new Event Class of Non-Project Labor Costs to your Sub-ledger Accounting Method using the seeded Rule set
Non-Project Labor Cost, you will need to:
1. Manage Mapping Sets to set the account values for the credit and debit of the Journal Rules
2. Add this Rule Set (or make a copy of it and add) to your subledger accounting method in the Manage Accounting Methods
for Project Costing.
Note: A best practice is to make a copy of the seeded Journal Entry Rule Set to maintain the standard seeded rule set for reference.
An overview of the seeded objects and an example for payroll clearing are provided below.
Imported Non-Project Journal line for non-project related labor cost when account is defined on the Labor Schedule
Labor Cost (debit) Distribution Rule.
Non-Project Labor Cost Journal line for non-project related labor cost when account is not defined.
(debit)
17 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
JOURNAL LINE RULE DESCRIPTION
NAME
These are the Differential distributions (i.e. "Cost Account"."Natural Account Segment" Is null) that
are generated if the total Labor Schedule Distribution Rules are less the 100%. This will fully
distribute the imported payroll cost.
Non-Project Labor Cost This rule will be used to create the credit side of the accounting for both the Imported Non-Project
Clearing (credit) Labor Cost and the Non-Project Labor Cost debits.
Journal line for non-project related labor cost clearing when account is not defined.
Non-Project Labor Cost Reversal Journal line for non-project related labor cost clearing.
Clearing Reversal
(credit)
Non-Project Labor Cost Reversal Journal line for non-project related labor cost.
Reversal (debit)
Mapping Sets
2 new Mapping Sets.
The Imported Non-Project Labor Cost Journal Line Rule does NOT need a mapping set, because it will be an account combination
passed directly from the labor schedule version distribution.
Example:
18 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
b. Mappings to a specified account code combination
a. Example below of defining an account for the Non-Project Labor Cost Clearing Mapping Set.
b. For efficiency, this would likely be the same account that you define for the payroll costs that are sent to distribute
through labor schedules (see Example Step 4 in Table 6 in section Summary Flow)
19 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
c.
Account Rules
3 new Account Rules.
The Imported Non-Project Labor Cost Account uses the Cost Account source to capture the account.
The other two rules are setup to use the Mapping Sets defined above of the same name.
We have also seeded a Journal Entry Rule Set that specifies how to process the debit and credit line types specific to all 5 of the new
Journal Entry Rules.
20 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
Manage Accounting Methods
The Manage Accounting Methods task is documented here for reference and is an accounting setup step that is required to be done by
customers. The step is to add the Journal Entry Rule Set to the necessary sub-ledger accounting method. The example below displays
an accounting method called “Vision City Accrual with Encumbrance Accounting”.
REMINDER - After adding the Journal Entry Rule Set to the sub-ledger accounting method, be sure to run the process Activate
Subledger Journal Entry Rule Set Assignments.
a.
Add the Journal Entry Rule Set Assignment to the Accounting Method
21 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
b.
Overview
A common accounting flow is to send the payroll transactions that are sent to Projects for Labor Distribution, to a clearing account.
These transactions will then be credited after they flow through the Import Payroll Costs process. Managing this clearing account
ensures the payroll costs are processed successfully through to the general ledger and are properly accounted.
Summary Flow
In this example, payroll is run and costed for two employees. These payroll costs are imported and distributed to projects/awards and
the general ledger via subledger accounting processes.
1. Two employees are on the monthly payroll at Oracle University. They are John Smith with a monthly salary of $2,500 and
Mary Marshall with a monthly salary of $3,600. The one element is Regular Salary. Total payroll costs are $6,000 for the
current month. These costs are processed and costed from Payroll to General Ledger as shown in Table 1 below.
Table 1
Account Total Payroll Costs Debit/Credit
2. Labor schedules are established at the employee assignment level for each employee.
Table 2
John Smith – Labor Schedule Distribution Rule Distribution Rule Percent
Table 3
Mary Marshall – Labor Schedule Distribution Rule Distribution Rule Percent
22 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
3. The Import Payroll Costs process in Projects is run and creates the project and non-project costs that can be reviewed in the
Manage Labor Costs pages.
Table 4
Employee Distribution Rule Distribution Amount
4. The Create Accounting for Projects process will generate the appropriate journal entries based on the subledger accounting
rules.
Table 5
Non-Project Journal Entries Amount Debit/Credit
GL 10.200.6010 $500 Debit
GL 10.300.6010 $1,440 Debit
Payroll Clearing $1,940 Credit
Table 6
Project Journal Entries Amount Debit/Credit
GL 20.000.6000 * $4,160 Debit
Payroll Clearing $4,160 Credit
* This is assumed to be the account assigned to the debit for all project related labor costs in the accounting rules. Total of
DOD Project $2,000 and NSF Project of $2,160 that results in $4,160.
5. The table below illustrates the consolidated view of the general ledger entries after the labor distribution and accounting
processes are complete. The payroll clearing has a zero balance and appropriate general ledger accounts show debit balances
for labor expenditures. The payroll clearing will NOT net to zero if any of the project costs errored in the Import Payroll
Costs process in projects.
Table 7
Account Example Step Debit Credit
00.000.1500, Payroll Clearing 1. $6,100
4. $1,940
4. $4,160
00.000.2100, Payroll Liability 1. $6,100
10.200.6010, General 4. $500
Fund.Engineering.Salary
10.300.6010, General 4. $1,440
Fund.Cardiology.Salary
20.000.0600, Restricted 4. $4,160
Fund.General.Salary
Summary Flow
The pay element of “Car Allowance” needs to be routed to a different account segment then the other pay elements. To accomplish
this the accountant will:
23 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
1. Create a mapping set with the Output Type = Segment
2. Specify the account in the Mappings section on the lower part of the page
3. The Journal Entry Rule Set in use has an existing Segment Rule for the associated Labor Cost journal lines.
4. The Account Rule being used for this segment is modified to leverage the new mapping set and apply it specifically for
the Condition of Labor Distribution
24 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
5. After Accounting processes are run, these costs are accounted to the specified segment based on the pay element, while
other pay elements use the other segment rules.
Roles
There are two roles:
1. Labor Distribution Administrator
a. Labor Distribution work area access to create and maintain labor schedules via the Find Assignment or Element
and Create and Maintain Labor Schedules pages.
25 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
i. Load Interface File for Import
ii. Import Payroll Costs
If both roles are assigned to the same user, the Labor Distributions work area will default to the Find Assignment or Element page and
have a button on the Create and Maintain page for the user to be able to switch to the Manage Labor Costs page and back.
b. After assigning the role to a user, navigate to Setup and Maintenance -> Manage Data Access for Users and assign a
security context for the user and role.
i. Example
1.
c. To see person names in OTBI, you should assign a Person Security Profile to this role for Public Persons
i. Navigate to Assign Security Profiles to Role setup task
iv. In the Public Person option chose View All People to allow user to see Person Names in OTBI when
looking at Labor Costs
2. Labor Distribution Administrator - Leverages two security frameworks for the different types of labor schedules:
a. Human Capital Management security framework
b. Manage Data Access object
i. Element level labor schedules are defined by business unit, so the Labor Distribution Administrator role
needs business unit access defined
ii. After assigning the role to a user, navigate to Setup and Maintenance -> Manage Data Access for Users
and assign a security context for the user and role.
1. Example
a.
c. Human Capital Management (HCM) security framework to allows for segregation of persons across an enterprise
26 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
i. The following set of steps describe how to setup the role for use with the person area of responsibility.
The role can be assigned any one of the person security profiles available in the Assign Security Profiles
to Role task.
1. Based on the profile assigned other steps may or may not be needed
2. Example:
a. Assigning the “View All People” to the role does not require other steps. This will
allow any user with this role to see all people in the Find Person page within Labor
Distribution.
ii. To learn more, see "Securing HCM" documentation, specifically Securing Person Records by Area of
Responsibility
iii. Setup the Role for Person Security
1. Create a Responsibility Type
c. Example
i.
2. Create a Person Security Profile
a. FSM Task = Manage Person Security Profile
ii.
3. Assign Security Profiles to Role
a. FSM Task = Assign Security Profiles to Role
b. Search for the role Labor Distribution Administrator (or custom role you created)
c. Click Edit
d. Navigate to Security Criteria and:
27 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
i. For Person security criteria choose the Person Security Profile created in the
prior step
ii. For Public Person choose a value to secure publicly available person data
1. Suggested View All People to be able to see the person name when
needed (for example, in OTBI)
iii. With the addition of Assignment Element labor schedules in 20D, an
additional data security requirement to gain access to the Elements from the
HCM Payroll area is required
1. Suggest using View All Legislative Data Groups to define the LDG
security profile unless there are requirements for restricting access
e. Navigate through the train stops till you get to Submit
f. Example
i.
g. The role is now secured for Person data leveraging the Area of Responsibility assigned
to the person / user dynamically when the user navigates to the Labor Distribution
work area to create and maintain labor schedules.
4. To assign the area of responsibility to the person (this is in the User Setup section below as
well, but here for the entire flow):
a. Navigate to Person Management work area
b. Find Person
c. Open panel drawer and select Areas of Responsibility
d. Click the plus icon to Create
e. Name the responsibility being created for this person
f. Choose the Responsibility Type: Lookup Code created above
g. Example:
i. This Person has both a Business Unit and a Hierarchy Type assigned. The
Person Security Profile -> Area of Responsibility defined above and assigned
to the Role defines what Scope of Responsibility value to use. The person
could have many roles with different Person Security Profiles with different
Area of Responsibility being applied.
28 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
ii.
User Setup
These are the standard user setup steps to ensure the Labor Distribution Accountant and Labor Distribution Administrator roles
provide access to data. The user setup steps should be done after the Roles are configured as defined above.
1. User Creation
a. No changes to user creation
b. Users need the or similar abstract role of Employee to enable proper access to the person data
2. Assigning Role to Users
a.
b. Labor Distribution Administrator
i. Uses the Person Security Profile and Manage Data Access settings.
29 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
ii. Manage Data Access
1. After assigning the role to a user, navigate to Setup and Maintenance -> Manage Data Access
for Users and assign a security context for the user and role.
a. Example
i.
iii. Person Security Profile
1. All steps above for the role and Person Security need to be completed to take effect, but the
User / Person steps below can be done at any time
i. This Person has both a Business Unit and a Hierarchy Type assigned. The
Person Security Profile -> Area of Responsibility defined above and assigned
to the Role defines what Scope of Responsibility value to use. The person
could have many roles with different Person Security Profiles with different
Area of Responsibility being applied.
ii.
30 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
Overview
A pay element is a type of pay a person and assignment can receive. For example, “Bonus” is a common pay element that may or may
not be on a person and assignment combination of pay. Labor schedules are able to be defined for pay elements. In order to ensure
accuracy and be used as an accounting attribute, the Labor Distribution solution is leveraging the Human Capital Management
(HCM) Payroll element object.
4. Click Continue
31 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
You can load Elements from a separate payroll system by using the HCM data loader solution. For information on how to load
Elements see “Integrating with HCM” at docs.oracle.com. Elements are in the “Loading Payroll Setup Objects” section.
For information on the interface process, see the Import Payroll Costs section of the File Based Data Import for Oracle Project
Portfolio Management Cloud guide.
The Assignment Labor Schedules FBDI process flattens the three levels of the labor schedule to increase the efficiency of automation.
Flattening the Header, Version, and Distributions into one row and duplicating the Header and Version attributes allows for more
effective automation from third party solutions.
This Interface allows for creation of new Header, Version, and Distribution combinations, as well as creation of new Versions within
an existing Header.
For information on the interface process, see the Import Assignment Labor Schedules section of the File Based Data Import for Oracle
Project Portfolio Management Cloud guide.
ASSUMPTIONS / PRE-REQUISITES
The objects below are assumed to be setup prior to the use of Labor Distribution capabilities:
1. Human Capital Management (HCM)
a. Elements
b. Assignments
ii. Departments
iii. Trees
2. Project Financials
a. Projects / Tasks / Awards
b. Organizations
c. Expenditure Types
i. Labor Schedule Distribution Rules leverage expenditure types in the Category of Labor and Expenditure
Type Class of Straight Time.
32 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
FREQUENTLY ASKED QUESTIONS
This is a list of questions that are asked and their associated answer.
a. This task is accessed from the Setup and Maintenance work area. The page is displayed in the context of a primary
or secondary ledger. All registered subledger applications are displayed. If you created additional accounting event
classes after initial ledger setup, run the Update Subledger Application Options process to incorporate these event
classes.
User with Labor Distribution Administrator role is not seeing the right list of people based
on the security setup?
If the user was logged in and was already viewing people in the Find Person page, please have the user clear the cache in the browser
and refresh the page. If that does not resolve this problem, a security administrator should be sure to run the scheduled processes
below to make sure the users and roles have been updated effectively.
33 Early Adopter Information | Distribute Labor Amounts Using Labor Schedules | Version 1.6
Copyright © 2021, Oracle and/or its affiliates | Confidential – Public
CONNECT WITH US
Call +1.800.ORACLE1 or visit oracle.com.
Outside North America, find your local office at oracle.com/contact.
Copyright © 2021, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without notice. This
document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of
merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, an d no contractual obligations are formed either directly or indirectly by
this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
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. 0120