Results for “effective_date”

4 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WIP_EMPLOYEE_LABOR_RATES_EFC is a Work in Process (WIP) table in the Oracle E-Business Suite that stores employee labor rate information expressed in EURO as a functional currency. Its name follows Oracle's established EFC (Euro Functional Currency) naming convention, whereby the EFC object exists as the euro-denominated counterpart to the base WIP_EMPLOYEE_LABOR_RATES table. The base table holds labor rates in the ledger's primary functional currency, while this companion table maintains the equivalent rates where EURO serves as functional currency, allowing organizations operating under the euro to store and retrieve rate data without conversion during transactional processing.

The object resides in the WIP schema and is classified as VALID in the ETRM 12.2.2 repository. From a modeling perspective, the metadata's heuristic Data Vault classification indicates this object is standalone. Under that heuristic, it is best treated as a standalone satellite-like structure keyed by its own business dimensions rather than as a hub or link participating in a broader integration model. This classification reflects its role as a currency-specific derivative of the base labor rate table rather than a shared master or relationship entity.

Key Information Stored

The documented physical schema for ETRM 12.2.2 contains five columns, each of which is material to the table's purpose:

  • ORGANIZATION_ID — Identifies the manufacturing or costing organization for which the labor rate applies. Rates are organization-specific, so this column is a principal business-key candidate in combination with other dimensions.
  • EMPLOYEE_ID — The employee to whom the hourly labor rate applies. This is the column through which the table ties back to the employee master.
  • HOURLY_LABOR_RATE — The monetary rate expressed in EURO as functional currency. This is the core measure of the table and the value consumed by WIP costing and resource charging logic.
  • EFFECTIVE_DATE — The date from which a given rate becomes valid, enabling date-effective rate versioning so that historical transactions retain the rate in force at the time of processing.
  • SET_OF_BOOKS_ID — Identifies the set of books (ledger) under which the euro-functional rate is recorded, anchoring the rate to the correct accounting context.

No surrogate primary key column is enumerated in the documented column list. In practice, uniqueness is derived from the composite of the business-key columns — organization, employee, effective date, and set of books — rather than from a single generated identifier. Analysts should verify the physical unique index in the database before assuming a specific key structure.

Common Use Cases and Queries

Typical reporting scenarios involve answering: what hourly labor rate applies to an employee in a given organization on a given date, and how that rate translates for a euro-functional ledger. A representative query joining the base and EFC tables by organization, employee, and effective date allows comparison of functional and euro-denominated values:

SELECT e.ORGANIZATION_ID, e.EMPLOYEE_ID, e.HOURLY_LABOR_RATE AS EURO_RATE, e.EFFECTIVE_DATE, e.SET_OF_BOOKS_ID FROM WIP.WIP_EMPLOYEE_LABOR_RATES_EFC e WHERE e.SET_OF_BOOKS_ID = :ledger_id AND e.EFFECTIVE_DATE <= :as_of_date ORDER BY e.ORGANIZATION_ID, e.EMPLOYEE_ID, e.EFFECTIVE_DATE;

Additional use cases include labor cost analysis for euro-reporting entities, rate-history audits, and reconciliation of WIP resource charges against rate tables. Because the table is date-effective, reports should always filter on EFFECTIVE_DATE to select the correct rate version.

Related Objects