1. How do I implement time cards in Time and Labor?
  2. Time Attributes and the Data Dictionary

Time Attributes and the Data Dictionary

A time attribute reflects how time is paid, costed, billed, or recorded as an information entry by qualifying the linked time entry. For example, identify whether a time card entry is Regular or Public Holiday.

Here are some delivered time attributes and example values.

Oracle Fusion Cloud App Time Attribute Attribute Description Example Values
Global Payroll Payroll Time Type Identifies time for payroll processing according to the value selected Regular US, Overtime CAN, Vacation US, Public Holiday US, and Public Holiday CAN
Project Costing Expenditure Type Identifies time for costing and billing according to the value selected Billable and Nonbillable
Absence Management Absence Management Type Identifies time for absence processing according to the value selected. Paid Maternity and Vacation

Create payroll and custom time attributes to store and display quantities as hours or units.

  • Use hours-based time entries to reflect how to pay and cost reported time. For example:

    • 8 hours of regular time per workday
    • 8 hours of public holiday time for what would otherwise be a regular workday

  • Use units-based time entries to assign people a flat payment amount. For example:

    • Pay people 25 USD for each meal taken, up to three meals per day.
    • Pay people an extra 100 USD for each worked shift where they were in charge and handled related duties.

You can include both hours-based and units-based time card fields on a time entry layout.

The data dictionary is the place with all possible attributes regardless of the source, such as Oracle Fusion Cloud Global Payroll.

  • It includes the primary time attributes for payroll. You can load more payroll time attributes and your own custom time attributes.

  • It contains metadata that data sources and time consumers, such as Global Payroll use to present time data in a meaningful way. Time consumers also use it to process time data appropriately. Here are examples of the metadata:

    • What attributes to store, such as storing the configured display names of time attributes and attribute values as alternate names
    • Where the repository physically keeps the attributes
    • How to verify valid values