Results for “hr_assignment_set_amendmen_pk”

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

Overview

HR_ASSIGNMENT_SET_AMENDMENTS is an Oracle E-Business Suite table residing in the HR schema and belonging to the PER (Human Resources) product family. The table identifies explicit include and exclude rules applied to an assignment set. Assignment sets in Oracle HRMS are named collections of assignments used to scope processing, reporting, and security operations. While most assignment set membership is derived dynamically through assignment set criteria, HR_ASSIGNMENT_SET_AMENDMENTS stores the manual overrides — individual assignments that must be forcibly included in or excluded from the set regardless of whether the underlying criteria would otherwise capture them.

In Data Vault modeling terms, the relationship metadata suggests a satellite-leaning classification. This is appropriate because the table hangs off HR_ASSIGNMENT_SETS through a foreign key and records descriptive attributes (the include-or-exclude flag plus audit columns) rather than representing an independent business hub. In practice, it functions as a detail or exception table that enriches the parent assignment set definition.

Key Information Stored

The documented physical schema for release 12.2.2 contains eight columns. The most significant of these are described below.

• ASSIGNMENT_ID — Identifies the specific assignment being included in or excluded from the set. Together with ASSIGNMENT_SET_ID it forms the composite primary key.
• ASSIGNMENT_SET_ID — Foreign key to HR_ASSIGNMENT_SETS, identifying the parent assignment set to which the amendment applies.
• INCLUDE_OR_EXCLUDE — The core business attribute. This flag determines whether the referenced assignment is an explicit inclusion or an explicit exclusion relative to the set's dynamic criteria.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard Oracle EBS WHO-column audit attributes that capture creation and last modification metadata for each amendment row.

The surrogate primary key is defined by the constraint HR_ASSIGNMENT_SET_AMENDMEN_PK, implemented over the composite of ASSIGNMENT_ID and ASSIGNMENT_SET_ID. Because this same composite also serves as the table's unique index, it is the business-key candidate. No independent single-column surrogate key is documented; uniqueness is enforced at the assignment-plus-set grain.

Common Use Cases and Queries

A frequent scenario is diagnosing why a specific assignment does or does not appear in a given assignment set. Report developers and HRMS support analysts query this table to enumerate manual amendments and reconcile them against criteria-driven membership.

• Listing all amendments for a set: SELECT * FROM hr_assignment_set_amendments WHERE assignment_set_id = :p_set_id;
• Finding excluded assignments: SELECT assignment_id FROM hr_assignment_set_amendments WHERE assignment_set_id = :p_set_id AND include_or_exclude = 'E';
• Identifying which sets explicitly reference a given assignment: SELECT assignment_set_id FROM hr_assignment_set_amendments WHERE assignment_id = :p_assignment_id;
• Auditing recent changes using LAST_UPDATE_DATE and LAST_UPDATED_BY to trace who modified membership rules.

Because the table is narrow, it is commonly joined to HR_ASSIGNMENT_SETS for the set name and to HR_ALL_ASSIGNMENTS for assignment details, supporting security audit reports and payroll population verification.

Related Objects

The following objects are most significant in relation to this table, based on documented foreign key relationships and standard HRMS usage.

• HR_ASSIGNMENT_SETS — The parent table; joined on HR_ASSIGNMENT_SET_AMENDMENTS.ASSIGNMENT_SET_ID = HR_ASSIGNMENT_SETS.ASSIGNMENT_SET_ID. This is the only documented foreign key relationship.
• HR_ASSIGNMENT_SET_CRITERIA — Defines the dynamic criteria that amendments override; used alongside this table to compute effective membership.
• PER_ALL_ASSIGNMENTS_F — The assignent datable joining on ASSIGNMENT_ID to resolve assignment and person details.
• PER_ALL_PEOPLE_F — Provides person-level context for the assignment referenced in an amendment.
• Assignment set APIs and concurrent programs in the PER module that consume these amendment rules when resolving set membership.