Results for “recurring_period_id”

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

Overview

The HXC_APPROVAL_PERIOD_COMPS table is a core configuration object within the Oracle E-Business Suite Time and Labor Engine (HXC) product family. It stores the individual components that make up an Approval Period Set, associating a recurring period definition with a specific time recipient. In Oracle EBS Release 12.1.1 and 12.2.2, this table drives the period-based approval routing logic used by Time and Labor and related self-service modules, determining which supervisors or recipients must approve timecards for a defined time span.

The ETRM metadata classifies this object heuristically as a link in a Data Vault model. This is a modeling suggestion: the table resolves many-to-many style associations between approval period sets, recurring periods, and time recipients through its foreign key columns, rather than acting as a standalone business hub or as a pure descriptive satellite.

Key Information Stored

The most significant columns documented for this object are:

• APPROVAL_PERIOD_COMP_ID — Surrogate primary key, uniquely identifying each approval period component row through the HXC_APPROVAL_PERIOD_COMPS_PK constraint.
• APPROVAL_PERIOD_SET_ID — Foreign key to HXC_APPROVAL_PERIOD_SETS; identifies the parent approval period set to which this component belongs.
• RECURRING_PERIOD_ID — Foreign key to HXC_RECURRING_PERIODS; defines the recurring time period pattern (for example, weekly or biweekly) applied to this component.
• TIME_RECIPIENT_ID — Foreign key to HXC_TIME_RECIPIENTS; identifies the recipient who receives or approves time for the associated period.
• OBJECT_VERSION_NUMBER — Optimistic locking column used to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns capturing audit and user accountability information.
• ZD_EDITION_NAME — Editioning column supporting Online Patching (adoption in 12.2.2), included as part of the unique index key HXC_APPROVAL_PERIOD_COMPS_PK.

The unique index HXC_APPROVAL_PERIOD_COMPS_PK (APPROVAL_PERIOD_COMP_ID, ZD_EDITION_NAME) serves as the documented business-key candidate, combining the surrogate key with the editioning column required by the 12.2.x edition-based redefinition model.

Common Use Cases and Queries

Typical usage centers on resolving the approval routing configuration for a given recipient or period set, and auditing how periods are composed. A common reporting pattern joins the three parent tables:

• Identify all components for a set: SELECT * FROM hxc.hxc_approval_period_comps WHERE approval_period_set_id = :set_id;
• List recipients and their recurring periods: join to HXC_TIME_RECIPIENTS and HXC_RECURRING_PERIODS on the documented FK columns.
• Dependency impact analysis before modifying an approval period set.
• Audit queries filtering on LAST_UPDATE_DATE or LAST_UPDATED_BY to trace configuration changes.

Because the table is a link object, queries almost always involve joins to the referenced parent tables rather than standalone selection.

Related Objects

The following objects are most significant due to documented foreign key relationships:

• HXC_APPROVAL_PERIOD_SETS — Parent set definition; joined via APPROVAL_PERIOD_SET_ID.
• HXC_RECURRING_PERIODS — Recurring period definition; joined via RECURRING_PERIOD_ID.
• HXC_TIME_RECIPIENTS — Approval recipient records; joined via TIME_RECIPIENT_ID.
• HXC_APPROVAL_PERIOD_COMPS_PK — The primary key constraint enforcing uniqueness on APPROVAL_PERIOD_COMP_ID and ZD_EDITION_NAME.

These relationships make HXC_APPROVAL_PERIOD_COMPS a central junction in the Time and Labor approval configuration model, linking period sets, recurring schedule patterns, and recipients into a coherent approval routing definition.