Person Assignment Labor Schedules with Time Card Distribution
If the Distribute Using Time Cards option is enabled on a person assignment labor schedule, imported payroll costs are distributed to projects using existing time card transactions in Project Costing as the basis for the payroll distribution.
With the time card distribution method, payroll costs for a pay period are summarized and distributed to the target time cards in Project Costing for the same person, assignment, and date range as per the imported payroll period costs.
If you are importing payroll costs from Oracle Fusion Payroll to be distributed to time cards, you must specify a Time Card Distribution Basis value on each project payroll pay element that you’ve enabled to be imported into Project Costing using the Manage Project Payroll Pay Elements task. The Time Card Distribution Basis values are:
| Time Card Distribution Basis | Eligible Target Time Cards |
| All Hours | Target time cards with any expenditure type class are eligible to receive payroll pay element costs with this basis. |
| Straight Time Hours | Only target time cards with an expenditure type class of Straight Time are eligible to receive payroll pay element costs with this basis. |
| Overtime Hours | Only target time cards with an expenditure type class of Overtime are eligible to receive payroll pay element costs with this basis. |
Project payroll pay elements don’t have to be defined if you are importing payroll costs from a third-party external payroll system. In this case, you must specify a Time Card Distribution Basis on each payroll cost record loaded to the interface table if the payroll cost will be distributed to projects using time cards.
To be eligible for payroll costing, a project time card must meet the following criteria:
- The transaction must have an expenditure type class of Straight Time (ST) or Overtime (OT).
- The time card can be sourced from Oracle Fusion Time and Labor or any external third-party application.
- The Import Raw Cost Amounts option on the project transaction source document is No.
- The project time card isn’t a converted item.
- The project time card can’t be a net zero transaction.
- The project time card must be incurred by the same person and HCM assignment as the payroll costs, regardless of the expenditure business unit of the time card transaction.
- The project time card’s expenditure item date is within the effectivity dates of the labor schedule version with the time card distribution option enabled.
- The project time card’s expenditure item date is with the payroll period start and end dates on the labor cost records.*
*Note that the payroll period start and end dates on an imported labor cost from Oracle Fusion Payroll may not be the same as the start and end dates of the payroll. In the case of a payroll transfer, for example, Oracle Fusion Payroll considers the effectivity dates of the person’s payroll assignment relationship and adjusts the payroll period start and end dates accordingly for the imported labor cost.
When a time card is imported into Project Costing, if an active labor schedule version with the time card distribution option enabled exists for the person assignment, and the time card transaction date is within the effective dates of the version, then the time card is imported using a static cost rate of 0. When payroll actual costs are imported, then the raw cost of the time card is recalculated using the distributed payroll costs relevant for that time card transaction.
Whereas project-based labor distribution rules create a separate currency-based project cost transaction on each target project for each payroll pay element, the time card distribution method doesn’t create any new project costs. Instead, the raw cost on existing target time cards is recalculated when payroll is distributed to projects using the time card distribution method.
In the time card distribution method, all eligible payroll pay element costs applicable for a given target time card are summarized, and a raw cost rate is calculated for the target time card. This rate is then used to calculate the raw cost of the target time card by multiplying against the target time card’s quantity.
The following example illustrates the process:
Lance Mackenzie is a consultant for Vision City Operations. He reports his time worked against projects on a weekly basis using Oracle Fusion Time and Labor. He’s also a salaried employee paid on a weekly basis, and his payroll is calculated and processed using Oracle Fusion Payroll.
Vision City Operations wants the most accurate cost to be calculated for Lance’s reported time. Therefore, labor schedule version was created for Lance with the time card distribution option enabled so that Lance’s hours will be costed based on his actual payroll costs.
Vision City Operations uses Oracle Fusion Payroll and has defined the following payroll project pay elements in Labor Distribution so that payroll costs for these pay elements are eligible to be imported into Project Costing. Note that as costs for these pay elements may be distributed to projects using time cards, a Time Card Distribution Basis has been entered for each:
| Pay Element | Time Card Distribution Basis |
| Regular Salary | Straight Time Hours |
| Overtime | Overtime Hours |
| Bonus | All Hours |
Lance reports the following hours for the current week:
| Project | Expenditure Type Class | Quantity |
| Fox Stores HCM Implementation | Straight Time | 25 |
| DHHS Study | Straight Time | 15 |
| DHHS Study | Overtime | 4 |
For the same week, Lance’s payroll is:
| Pay Element | Time Card Distribution Basis | Amount (USD) |
| Regular Salary | Straight Time Hours | 2,000 |
| Overtime | Overtime Hours | 400 |
| Bonus | All Hours | 200 |
| Total: | 2,600 | |
Using the quantity of hours for Lance’s eligible target time cards, a raw cost rate is calculated for each pay element:
| Pay Element | Time Card Distribution Basis | Amount (USD) | Target Time Card Quantity | Rate = Cost/Quantity (Rounded) |
| Regular Salary | Straight Time Hours | 2,000 | 40 | 50 USD/Hour |
| Overtime | Overtime Hours | 400 | 4 | 100 USD/Hour |
| Bonus | All Hours | 200 | 44 | 4.54545 USD/Hour |
The raw cost for each of Lance’s time card entries is then calculated using the sum of the rates for each applicable pay element rate multiplied by the time entry transaction quantity:
| Project | Expenditure Type Class | Quantity | Calculated Raw Cost Rate (Rounded) | Raw Cost (Rounded) |
| Fox Stores HCM Implementation | Straight Time | 25 |
54.54545 USD/Hour (50 USD/Hour for Regular Salary pay element + 4.54545 USD/Hour for Bonus pay element) |
1,363.64 USD |
| DHHS Study | Straight Time | 15 |
54.54545 USD/Hour (50 USD/Hour for Regular Salary pay element + 4.54545 USD/Hour for Bonus pay element) |
818.18 USD |
| DHHS Study | Overtime | 4 |
104.54545 USD/Hour (100 USD/Hour for Overtime pay element + 4.54545 USD/Hour for Bonus pay element) |
418.18 USD |
| Total: | 2,600 USD | |||
Unit of Measure for Target Time Card Transactions
The unit of measure for target time card transactions isn’t considered when distributing payroll actual costs. When recording time using the predefined transaction sources Oracle Fusion Time and Labor or Oracle Fusion Projects, the unit of measure is always hours. Third party time card transactions, however, can be created using a unit of measure other than hours.
Distributing payroll actuals to time cards is based on the quantities of the target time cards. The unit of measure on the target time cards is not considered. Therefore, if you have different units of measure on your target time cards, the distribution of payroll actuals will not account for this.
For example, you are importing a pay element cost of 100 USD. The following would be the distribution results based on the target time cards in each example:
Example 1: All Target Time Cards with a Unit of Measure of Hours
| Transaction Source | Quantity | Unit of Measure | Resulting Raw Cost |
| Oracle Fusion Time and Labor | 8 | Hours | 50 USD |
| <Third party source> | 8 | Hours | 50 USD |
| Total: | 100 USD | ||
Example 1: All Target Time Cards with a Unit of Measure of Days
| Transaction Source | Quantity | Unit of Measure | Resulting Raw Cost |
| <Third party source> | 1 | Day | 50 USD |
| <Third party source> | 1 | Day | 50 USD |
| Total: | 100 USD | ||
Example 3: Target Time Cards with Different Units of Measure
| Transaction Source | Quantity | Unit of Measure | Resulting Raw Cost |
| Oracle Fusion Time and Labor | 8 | Hours | 88.89 USD |
| <Third party source> | 1 | Day | 11.11 USD |
| Total: | 100 USD | ||
Changes to Source Payroll Costs or Target Time Card Quantities
There can be changes to either payroll source costs or target time card quantities, or both, after payroll costs are initially successfully distributed to target time cards in Project Costing. Whenever there is a change in source payroll costs being imported in addition to previously distributed payroll costs, the target time cards are automatically adjusted to reflect the distribution of payroll actual costs which include the newest additions.
For example, a pay element cost of $4000 for a particular person assignment is successfully imported and distributed to target time cards in Project Costing. The distributed cost amounts after the initial payroll distribution are shown in the below table.
| Transaction Number | Project Number | Quantity | Raw Cost (USD) |
| 100 | Stark Industries HCM Implementation | 25 | 2,500 |
| 101 | DHHS Study | 15 | 1,500 |
| Totals: | 40 | 4,000 | |
If you subsequently import an additional payroll cost for the same person assignment and payroll dates as per the original import, then the Import Payroll Costs process redistributes the new total cost to all target time cards. The table below shows the redistributed results when there is an additional $500 of payroll costs imported for the same period as the originally-imported cost of $4,000.
| Transaction Number | Project Number | Quantity | Raw Cost (USD) |
| 100 | Stark Industries HCM Implementation | 25 | 2,812.50 |
| 101 | DHHS Study | 15 | 1,687.50 |
| Totals: | 40 | 4,500 | |
The total target time card quantities can also change after payroll costs have been successfully distributed. For example, a time reporter may revise his time card in Oracle Fusion Time and Labor to report more or less hours than were originally reported. Continuing with the example above, suppose an additional 10 hours were reported by the time reporter, and these additional hours were imported into Project Costing. There’s no change to the payroll costs for the period, but the previous distribution to target time cards is no longer accurate as the total target time card quantities have changed. In this scenario, the status of the relevant labor cost records in the Manage Labor Costs page changes to Needs Reprocessing. The table below shows the results after the successful reprocessing of the relevant labor costs.
| Transaction Number | Project Number | Quantity | Raw Cost (USD) |
| 100 | Stark Industries HCM Implementation | 25 | 2,250 |
| 101 | DHHS Study | 15 | 1,350 |
| 103 | Fox Stores SCM Upgrade | 10 | 900 |
| Totals: | 50 | 4,500 | |
Payroll Cost Currencies
All imported payroll costs distributed to the same target time cards must have the same currency. Project-based distribution rules in Labor Distribution result in a separate project cost transaction for each pay element. Therefore, project-based distribution rules allow for different currencies across imported pay element costs. With time card distribution, however, multiple pay element costs are summarized before distributing to target time cards. Each target time card is updated with a single distributed cost amount, which may have been sourced from multiple payroll pay elements. Pay element costs with different currencies targeting the same time cards are rejected by the Import Payroll Costs process.
Time Card Raw Cost Rounding
For project-based labor distribution rules, new project cost transactions are created against target projects with a unit of measure of Currency for each payroll pay element cost. For these rules, the Import Payroll Costs ensures that the sum of the new project cost transactions is the same as the original payroll pay element cost, both when displayed or accounted.
With time card distribution-based rules, however, no new project cost transactions are created as a result of the payroll distribution process. Instead, a raw cost rate is calculated based on the sum of pay element costs and the quantities of target time cards. Each target time card transaction’s raw cost is then calculated by multiplying the raw cost rate with the time card transaction’s quantity.
This calculated transaction raw cost is saved as an unrounded amount in the data store. However, when the time card transaction is queried in the Manage Project Costs page or when it is accounted, the unrounded amount is rounded using the half up rounding rule to the precision of the currency.
For example, a payroll cost of 2,000 USD is imported and distributed to target time cards which have a total quantity of 42 hours. The raw cost rate is calculated as 2,000 USD divided by 42 hours resulting in a raw cost rate of 47.6190476190476 USD/hour. This raw cost rate is then used to calculate the raw cost of each target time card transaction as shown in the below table.
| Transaction Number | Project Number | Quantity | Raw Cost Rate | Raw Cost (USD) - Unrounded | Raw Cost (USD) - Rounded |
| 100 | Stark Industries HCM Implementation | 18 | 47.6190476190476 | 857.142857142857 | 857.14 |
| 101 | DHHS Study | 17 | 47.6190476190476 | 809.52380952381 | 809.52 |
| 103 | Fox Stores SCM Upgrade | 7 | 47.6190476190476 | 333. 333333333333 | 333.33 |
| Totals: | 42 | 2,000 | 1,999 | ||