Results for “compensation_rule_set”

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

Overview

WIP.WIP_EMPLOYEE_LABOR_RATES is a Work in Process reference table that stores the hourly labor rates applied to individual employees within an inventory organization. It functions as a rate master used by WIP cost rollup and work-in-process valuation to charge labor to discrete jobs, repetitive schedules, and, indirectly, to flow labor cost into the general ledger. The table is organization-scoped: the same employee can carry different rates in different organizations, and rates are time-phased through an effective date so that historical transactions retain the rate that was in force when the labor was reported.

Under a heuristic Data Vault classification, the table leans toward a satellite. Its primary key, WIP_EMPLOYEE_LABOR_RATES_PK, is composed of EMPLOYEE_ID, ORGANIZATION_ID, and EFFECTIVE_DATE, and it carries descriptive, mutable measures — most notably HOURLY_LABOR_RATE and COMPENSATION_RULE_SET — rather than pure relationships. This suggests the employee/organization pairing behaves as a parent key and the effective-dated rows behave as its descriptive history. The classification is a modeling suggestion only, not a documented Oracle EBS design.

Key Information Stored

The 30 documented columns fall into three groups: key columns, business measures, and the standard EBS audit/descriptive flexfield tail.

• EMPLOYEE_ID, ORGANIZATION_ID, EFFECTIVE_DATE — the composite primary key and unique business-key candidate (WIP_EMPLOYEE_LABOR_RATES_U1). Together they identify a single rate version.
• HOURLY_LABOR_RATE — the rate applied when assigning labor cost to an employee's reported time.
• COMPENSATION_RULE_SET — the compensation rule set used for rate derivation or tie-back to compensation logic.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard who-columns for audit and extract-based incremental loads.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield segment columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context, useful for tracing which process inserted or updated a row.

There is no separately documented surrogate key; the three key columns serve as the primary key. The unique index WIP_EMPLOYEE_LABOR_RATES_U1 confirms a one-row-per-employee-per-organization-per-effective-date rule.

Common Use Cases and Queries

Typical reporting against this table includes effective-rate lookups, rate-change audits, and labor cost reconciliation between WIP and the general ledger. A common pattern is an as-of or point-in-time rate resolution, selecting the most recent effective date at or before the transaction date:

• Current rate per employee: select the row where EFFECTIVE_DATE is the maximum not exceeding SYSDATE for the given EMPLOYEE_ID and ORGANIZATION_ID.
• Rate history: order rows by EFFECTIVE_DATE to trace when a rate changed and who made the change via LAST_UPDATED_BY.
• Change audit: compare HOURLY_LABOR_RATE and COMPENSATION_RULE_SET across consecutive effective dates.

A representative SQL fragment for the latest effective rate is:

SELECT employee_id, organization_id, effective_date, hourly_labor_rate FROM wip.wip_employee_labor_rates r WHERE organization_id = :org AND employee_id = :emp AND effective_date = (SELECT MAX(effective_date) FROM wip.wip_employee_labor_rates WHERE employee_id = r.employee_id AND organization_id = r.organization_id AND effective_date <= :as_of_date);

For rate-change monitoring over a period, aggregate on last_update_date and last_updated_by, filtering by the standard audit columns. Because the table is organization-scoped, joins must always carry ORGANIZATION_ID.

Related Objects

The documented foreign key is WIP_EMPLOYEE_LABOR_RATES.ORGANIZATION_ID → WIP_PARAMETERS, tying each rate to the organization-level WIP parameters that govern cost management for that facility. Beyond that FK, the table interacts with the following significant objects:

• WIP_PARAMETERS — referenced organization master that owns the ORGANIZATION_ID foreign key; WIP cost flags and accounting class settings live here.
• HR_EMPLOYEES / PER_ALL_PEOPLE_F — source of the EMPLOYEE_ID value and employee descriptive data.
• WIP_TRANSACTIONS and WIP_TRANSACTION_ACCOUNTS — record the labor transactions whose costs are derived from employee labor rates.
• WIP_MOVE_TRANSACTIONS and WIP_JOBS / WIP_ENTITIES — discrete/repetitive work-in-process entities whose labor is valued using the rate.
• BOM_RESOURCES and BOM_DEPARTMENTS — the resource/department definitions that drive labor charging and may reference employee rates through overhead and rate rules.
• WIP_COST_ADJUSTMENTS and MTL_TRANSACTION_ACCOUNTS — downstream accounting records produced when labor cost is posted.

Because Oracle EBS maintains these relationships primarily through application logic and organization-scoped joins rather than declared constraints, queries should always constrain by ORGANIZATION_ID to avoid cross-organization rate leakage.