Results for “pay_balance_attributes_pk”

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

Overview

PAY_BALANCE_ATTRIBUTES is an Oracle EBS Human Resources (HR) schema table that stores the mapping between balance attributes and defined balances within the Oracle Payroll balance model. Its FND Design Data reference is PAY.PAY_BALANCE_ATTRIBUTES, and it resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. The table is classified as VALID and functions as a configuration-level construct that links the attribute definitions available for balance processing to the actual defined balances against which those attributes are evaluated.

From a Data Vault modeling perspective, the mined foreign key structure suggests this object behaves as a link table. It resolves a many-to-many association between two independent reference entities — balance attribute definitions and defined balances — and carries no independent descriptive payload beyond the association itself and its legislative/business group scoping. This classification is offered as a heuristic modeling suggestion based on the FK topology, not as a documented Oracle attribute.

Key Information Stored

The table is governed by a single-column surrogate primary key and a composite unique key that together enforce uniqueness of the attribute-to-balance mapping.

• BALANCE_ATTRIBUTE_ID — Numeric surrogate primary key (PAY_BALANCE_ATTRIBUTES_PK). It uniquely identifies each mapping row.
• ATTRIBUTE_ID — Foreign key to PAY_BAL_ATTRIBUTE_DEFINITIONS. Identifies the balance attribute participating in the mapping.
• DEFINED_BALANCE_ID — Foreign key to PAY_DEFINED_BALANCES. Identifies the defined balance to which the attribute is mapped.
• BUSINESS_GROUP_ID — Business group scoping column (NUMBER, length 15). Restricts the mapping to a specific enterprise business group.
• LEGISLATION_CODE — Legislation code (VARCHAR2, 30). Scopes the mapping to a particular legislative context.
• ZD_EDITION_NAME — Editioning column present in the 12.2.2 physical schema, supporting online patching and edition-based redefinition.
• Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE provide audit trail information, with LAST_UPDATED_BY and CREATED_BY optionally referencing FND_USER.USER_ID.

The business-key candidate is the composite unique key PAY_BALANCE_ATTRIBUTES_UK, defined across ATTRIBUTE_ID, DEFINED_BALANCE_ID, BUSINESS_GROUP_ID, LEGISLATION_CODE, and ZD_EDITION_NAME, ensuring no duplicate mapping exists for the same attribute, balance, business group, and legislation combination. Both the primary key and the unique key are implemented as NORMAL UNIQUE indexes in the APPS_TS_TX_IDX tablespace.

Common Use Cases and Queries

The primary reporting scenario is enumerating which attributes apply to a given defined balance, or conversely which balances consume a given attribute. A typical join pattern is:

• Join PAY_BALANCE_ATTRIBUTES to PAY_DEFINED_BALANCES on DEFINED_BALANCE_ID to resolve balance names for a set of attribute mappings.
• Join PAY_BALANCE_ATTRIBUTES to PAY_BAL_ATTRIBUTE_DEFINITIONS on ATTRIBUTE_ID to resolve attribute metadata.
• Filter by BUSINESS_GROUP_ID and LEGISLATION_CODE to constrain results to a single enterprise and legislative scope.
• Use BALANCE_ATTRIBUTE_ID lookups for direct point queries when the surrogate key is already known.

Typical SQL patterns select BALANCE_ATTRIBUTE_ID, ATTRIBUTE_ID, DEFINED_BALANCE_ID, BUSINESS_GROUP_ID, and LEGISLATION_CODE (the columns shown in the documented query text) and join outward to the two referenced definition tables. Payroll configuration analysts use these queries to audit attribute coverage, validate balance definitions after legislative patches, and reconcile mappings following business group or legislation changes.

Related Objects

The following objects are most significant in relation to PAY_BALANCE_ATTRIBUTES, based on the documented foreign key and key constraints:

• PAY_BAL_ATTRIBUTE_DEFINITIONS — Referenced via ATTRIBUTE_ID; supplies the attribute definition for each mapping row.
• PAY_DEFINED_BALANCES — Referenced via DEFINED_BALANCE_ID; supplies the defined balance for each mapping row.
• FND_USER — Referenced indirectly through the WHO columns LAST_UPDATED_BY and CREATED_BY (USER_ID).
• FND_LOGINS — Referenced through LAST_UPDATE_LOGIN (LOGIN_ID) for session-level audit.
• PAY_BALANCE_ATTRIBUTES_PK and PAY_BALANCE_ATTRIBUTES_UK — The unique indexes enforcing surrogate and business-key uniqueness in APPS_TS_TX_IDX.

Together these objects form the reference and audit perimeter around the attribute-to-balance mapping, and they are the primary targets for joins when building balance configuration reports or validating payroll balance setup.