Results for “compensation_rule_set”

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

Overview

PA_COMP_RULE_OT_DEFAULTS_ALL is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the overtime default project and task assignments associated with a Labor Costing Rule. Labor costing rules, defined in PA_COMPENSATION_RULE_SETS, control how expenditure and labor costs are distributed to projects and tasks. When overtime hours are processed, the costing engine requires a destination project and task to which those hours are charged; this table supplies that default mapping for each compensation rule set within a given operating unit.

The object is an "_ALL" table, meaning it is partitioned by operating unit through the ORG_ID column and typically has a corresponding multi-org view. Access to rows is therefore governed by MO: Operating Unit / MO: Security Profile, and any query executed outside a properly initialized session will return rows for all organizations or fail entirely depending on the client and date-tracked setup. The table is date-tracked only to the extent of standard WHO columns and does not carry effective-dated business attributes, so it holds a single current default per rule set rather than a history of changes.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is link. The table's grain is one row per compensation rule set per operating unit, and its foreign keys resolve to a compensation rule set, a project, and a task. This makes it behave as a relationship (link) entity connecting the labor costing rule to the project/task hierarchy it defaults to, rather than a descriptive satellite of any single parent. The ORG_ID and COMPENSATION_RULE_SET pairing forms the primary key, which further confirms its role as an associative object rather than an independent business entity.

Key Information Stored

The table contains nine documented columns. The most significant are:

• COMPENSATION_RULE_SET — the labor costing rule set identifier. This is the primary business reference and part of the composite primary key. It links each default back to the rule set that governs how overtime is costed.
• ORG_ID — the operating unit identifier. This is the second component of the composite primary key (PA_COMP_RULE_OT_DEFAULTS_PK) and enforces the multi-organization partition of the data.
• PROJECT_ID — the default project to which overtime costs are charged when the rule set applies. This is a foreign key to PA_PROJECTS_ALL.
• TASK_ID — the default task within the project for overtime charging. This is a foreign key to PA_TASKS and refines the destination to the task level.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard WHO audit columns recording who created and last modified each default and when.

The surrogate primary key PA_COMP_RULE_OT_DEFAULTS_PK is defined over (COMPENSATION_RULE_SET, ORG_ID), which together act as the natural business key as well. There is no separate single-column sequence-generated surrogate; the primary key is the business key. PROJECT_ID and TASK_ID are not part of the uniqueness constraint but are constrained logically by the referenced parent records.

Common Use Cases and Queries

Typical scenarios involve auditing which project and task overtime is defaulted to for a given labor costing rule, validating that those projects are active and open for cost collection, and troubleshooting costing failures caused by a missing or disabled default.

• Identify the overtime default destination for a rule set within an operating unit.
• Detect rule sets that have no overtime default configured, which can cause overtime expenditure to fail costing.
• Report the distribution of overtime defaults by project to support cost allocation analysis.
• Validate that referenced projects and tasks remain active before a costing run.
• Compare defaults across operating units by joining on ORG_ID.

A representative query joins the defaults to their parents:

SELECT r.COMPENSATION_RULE_SET, r.ORG_ID, p.PROJECT_NAME, t.TASK_NAME
FROM PA_COMP_RULE_OT_DEFAULTS_ALL r, PA_PROJECTS_ALL p, PA_TASKS t
WHERE r.PROJECT_ID = p.PROJECT_ID
AND r.TASK_ID = t.TASK_ID
AND r.ORG_ID = p.ORG_ID
AND r.COMPENSATION_RULE_SET = :rule_set;

For a left-outer audit of rules missing defaults, the driving table would instead be PA_COMPENSATION_RULE_SETS joined by COMPENSATION_RULE_SET and ORG_ID with a NULL check on PROJECT_ID.

Related Objects

• PA_COMPENSATION_RULE_SETS — parent of COMPENSATION_RULE_SET. Defines the labor costing rules to which these overtime defaults belong.
• PA_PROJECTS_ALL — parent of PROJECT_ID. Supplements the default project, its name, status, and organization.
• PA_TASKS — parent of TASK_ID. Supplies the default task and its attributes within the project.
• PA_EXPENDITURE_ITEMS_ALL / PA_COST_DISTRIBUTION_LINES_ALL — downstream cost collection tables that consume the default project and task when overtime is costed.
• PA_COMP_RULE_OT_DEFAULTS_V or the multi-org view of the same base table — the secured view through which the application normally reads these rows.

Because the object is written primarily by the Labor Costing Rule setup form, direct DML is generally discouraged; changes should be made through the Project Costing configuration UI so that dependent costing processes remain consistent.