Results for “pa_org_labor_sch_rule_u1”

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

Overview

PA.PA_ORG_LABOR_SCH_RULE is a transaction-data table in the Oracle E-Business Suite Projects (PA) schema that stores labor costing rule and rate schedule assignments for organizations. Each row represents an effective-dated assignment that binds a specific organization and operating unit to a labor costing rule, a cost rate schedule, and a forecast cost rate schedule, along with the accounting rate derivation settings used for currency conversion. In releases 12.1.1 and 12.2.2 the table is owned by PA, is marked VALID, and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10.

Functionally, the table is the configuration anchor behind labor costing and cost distribution in Oracle Projects. When cost distribution lines are generated, the application resolves the applicable assignment by organization and transaction date, then applies the referenced costing rule and rate schedule to price labor. The documented physical schema records 20 columns and one primary key, PA_ORG_LABOR_SCH_RULE_PK, defined on ORG_LABOR_SCH_RULE_ID.

Based on the mined foreign-key structure, the heuristic Data Vault classification is satellite-leaning. This is a modeling suggestion only: the table carries descriptive and effective-dated attributes that hang off organization and implementation hubs rather than acting as a standalone hub or an associative link between two business entities.

Key Information Stored

The surrogate primary key is ORG_LABOR_SCH_RULE_ID, a system-generated number that uniquely identifies each assignment. It is also the sole documented business-key candidate, enforced by the unique index PA_ORG_LABOR_SCH_RULE_U1 on that column. No other unique index exists; PA_ORG_LABOR_SCH_RULE_N1 (ORGANIZATION_ID, ORG_ID, START_DATE_ACTIVE) and PA_ORG_LABOR_SCH_RULE_N2 (COST_RATE_SCH_ID, FORECAST_COST_RATE_SCH_ID, LABOR_COSTING_RULE) are non-unique and support lookup access paths.

• ORGANIZATION_ID — identifier of the organization that uses the assigned costing rule and rate schedule.
• ORG_ID — identifier of the operating unit that uses the assignment.
• LABOR_COSTING_RULE — the implementation-defined labor costing rule, stored as VARCHAR2(150).
• COST_RATE_SCH_ID — the cost rate schedule applied to the selected organization.
• FORECAST_COST_RATE_SCH_ID — the cost rate schedule used when forecasting cost and revenue.
• OVERTIME_PROJECT_ID and OVERTIME_TASK_ID — the project and task to which system-generated overtime items are charged.
• ACCT_RATE_DATE_CODE — indicates the date basis used to derive the account rate date.
• ACCT_RATE_TYPE — functional rate type override for currency conversion.
• ACCT_EXCHANGE_RATE — the exchange rate value stored for the schedule rule.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range of the assignment.
• BASE_HOURS and RBC_ELEMENT_TYPE_ID — additional attributes recorded in the documented column list.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The most frequent query pattern resolves the assignment in force for an organization on a given date. This is the same access path supported by PA_ORG_LABOR_SCH_RULE_N1.

• Retrieve the active rule and rate schedule for an organization and operating unit:

  SELECT org_labor_sch_rule_id, labor_costing_rule,
         cost_rate_sch_id, forecast_cost_rate_sch_id
  FROM   pa_org_labor_sch_rule
  WHERE  organization_id = :p_org_id
  AND    org_id = :p_org_id_operating_unit
  AND    :p_effective_date BETWEEN start_date_active
         AND NVL(end_date_active, :p_effective_date);

• Validate that no organization has overlapping effective-dated assignments, a common pre-implementation audit.
• Report which organizations reference a specific cost rate schedule by joining on COST_RATE_SCH_ID.
• Trace cost distribution lines back to their governing rule via PA_COST_DISTRIBUTION_LINES_ALL.ORG_LABOR_SCH_RULE_ID, which references this table.
• Review overtime charging defaults by listing OVERTIME_PROJECT_ID and OVERTIME_TASK_ID per organization.

When building extracts, note that the unique key to carry into downstream tables is ORG_LABOR_SCH_RULE_ID, and that the audit columns should be excluded from business-facing reports.

Related Objects

The table participates in several documented foreign-key relationships, both as a referencing and a referenced object.

• HR_ALL_ORGANIZATION_UNITS — joined on ORGANIZATION_ID; supplies the organization definition.
• PA_IMPLEMENTATIONS_ALL — joined on ORG_ID; defines the operating unit.
• PA_COMPENSATION_RULE_SETS — joined on LABOR_COSTING_RULE; resolves the costing rule definition.
• PA_PROJECTS_ALL — joined on OVERTIME_PROJECT_ID; identifies the overtime charging project.
• PA_TASKS — joined on OVERTIME_TASK_ID; identifies the overtime charging task.
• PA_COST_DISTRIBUTION_LINES_ALL — references this table through ORG_LABOR_SCH_RULE_ID; stores the labor cost distribution results derived from the assignment.
• PA_COST_DIST_LINES_AR — also references ORG_LABOR_SCH_RULE_ID where applicable. These dependent tables should be considered when deleting or re-dating assignments.