Results for “pay_balance_attributes”

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

Overview

PAY_BALANCE_ATTRIBUTES is a payroll configuration table owned by the HR schema within the Oracle E-Business Suite PAY (Payroll) product. Its documented purpose is to hold mappings between attributes and defined balances. In practical terms, the table associates a balance attribute definition with a defined balance, allowing the payroll engine to determine which attribute drives the behaviour, storage, or calculation characteristics of a given defined balance. This mapping is central to how balances are declared, aggregated, and reported across a payroll run.

The object exists in both Oracle EBS 12.1.1 and 12.2.2, and the documented physical schema reflects the 12.2.2 Editioning model through the presence of the ZD_EDITION_NAME column. The heuristic Data Vault classification mined from the foreign key structure is a link. This is a modeling suggestion: the table resolves a many-to-many style relationship between attribute definitions and defined balances, which is the classic role of a link table in a Data Vault model.

Key Information Stored

The table contains eleven documented columns. The most significant are listed below.

• BALANCE_ATTRIBUTE_ID — the surrogate primary key, enforced by PAY_BALANCE_ATTRIBUTES_PK. It uniquely identifies each attribute-to-balance mapping.
• ATTRIBUTE_ID — foreign key to PAY_BAL_ATTRIBUTE_DEFINITIONS, identifying the balance attribute being mapped.
• DEFINED_BALANCE_ID — foreign key to PAY_DEFINED_BALANCES, identifying the defined balance to which the attribute is attached.
• BUSINESS_GROUP_ID — the enterprise or business group context, used to partition configuration data by organisation.
• LEGISLATION_CODE — the legislative context under which the mapping is valid, enabling country-specific balance behaviour.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns recording who last changed the row and when.
• CREATED_BY, CREATION_DATE — standard audit columns recording row creation.
• ZD_EDITION_NAME — the editioning column introduced in 12.2.2, supporting edition-based redefinition.

The business-key candidate is documented through the unique index PAY_BALANCE_ATTRIBUTES_UK, defined over ATTRIBUTE_ID, DEFINED_BALANCE_ID, BUSINESS_GROUP_ID, LEGISLATION_CODE, and ZD_EDITION_NAME. This confirms that the combination of attribute, balance, business group, and legislation must be unique, distinguishing it from the surrogate BALANCE_ATTRIBUTE_ID primary key.

Common Use Cases and Queries

The principal use case is configuration validation and impact analysis: identifying which attributes are attached to a defined balance before changing balance behaviour. A typical query joins the table to both parents:

• Retrieve all attributes for a defined balance: SELECT attribute_id FROM pay_balance_attributes WHERE defined_balance_id = :balance_id;
• Resolve attribute names via PAY_BAL_ATTRIBUTE_DEFINITIONS and balance names via PAY_DEFINED_BALANCES using ATTRIBUTE_ID and DEFINED_BALANCE_ID respectively.
• Filter by legislation and business group to scope configuration reports to a specific legislative environment.
• Audit recent configuration changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Related Objects

The following objects have the most significant relationships with PAY_BALANCE_ATTRIBUTES.

• PAY_BAL_ATTRIBUTE_DEFINITIONS — referenced via PAY_BALANCE_ATTRIBUTES.ATTRIBUTE_ID; supplies the attribute definition.
• PAY_DEFINED_BALANCES — referenced via PAY_BALANCE_ATTRIBUTES.DEFINED_BALANCE_ID; supplies the defined balance.
• PAY_BALANCE_ATTRIBUTES_PK — the primary key constraint on BALANCE_ATTRIBUTE_ID.
• PAY_BALANCE_ATTRIBUTES_UK — the unique business-key constraint on ATTRIBUTE_ID, DEFINED_BALANCE_ID, BUSINESS_GROUP_ID, LEGISLATION_CODE, and ZD_EDITION_NAME.