Results for “original_entry_id”

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

Overview

PAY_LATEST_BALANCES is a transactional table owned by the HR schema within the Oracle EBS Payroll (PAY) module. It stores the most current balance values for a person or assignment, acting as a snapshot layer that payroll processes, reporting engines, and balance inquiries read from without having to re-aggregate the underlying balance run results. Each row represents a single latest balance entry keyed by a surrogate identifier and tied back to the balance definition that governs its semantics.

From a dimensional modeling perspective, the ETRM relationship metadata classifies this object heuristically as satellite-leaning. In Data Vault terms, that suggests a design where the table hangs off a business hub or link (the person, assignment, and defined balance combination) and carries descriptive, time-variant attributes such as VALUE, EXPIRY_DATE, and PREV_BALANCE_VALUE. It is not a pure hub because the primary key is a surrogate, and it is not a full link because it carries measurements rather than purely representing associations.

Key Information Stored

The table contains 27 documented columns. The most consequential are:

• LATEST_BALANCE_ID — the surrogate primary key defined by PAY_LATEST_BALANCES_PK. It uniquely identifies each latest balance row and is the column downstream tables and APIs reference.
• DEFINED_BALANCE_ID — foreign key to PAY_DEFINED_BALANCES; identifies which balance definition (for example, gross pay or a deduction accumulator) the row represents.
• ASSIGNMENT_ACTION_ID — foreign key to PAY_ASSIGNMENT_ACTIONS; the payroll action that produced or updated the balance.
• PROCESS_GROUP_ID — foreign key to PAY_PROCESS_GROUPS; the process group under which the balance was calculated.
• VALUE — the current numeric balance amount for the person or assignment.
• PERSON_ID and ASSIGNMENT_ID — the party and assignment to which the balance belongs.
• EXPIRY_DATE and EXPIRED_VALUE / EXPIRED_DATE — track when the balance expired and the value at expiry.
• PREV_ASSIGNMENT_ACTION_ID, PREV_BALANCE_VALUE, and PREV_EXPIRY_DATE — retain the prior state for audit and retroactive comparison.
• TAX_UNIT_ID, JURISDICTION_CODE, LOCAL_UNIT_ID, and TAX_GROUP — statutory and localization context.
• SOURCE_ID, SOURCE_TEXT, SOURCE_TEXT2, SOURCE_NUMBER, SOURCE_NUMBER2, and ORIGINAL_ENTRY_ID — traceability back to the originating element or entry.
• PAYROLL_ID, ORGANIZATION_ID, and INSTANCE_ID — payroll run, organizational, and instance context.

The only documented unique index is the primary key on LATEST_BALANCE_ID; no separate business-key unique index is identified in the metadata.

Common Use Cases and Queries

A frequent pattern is retrieving the latest balance for a defined balance across a population of assignments:

• Balance inquiry screens and self-service payslip displays that read current accumulated values.
• Deduction and accrual reporting, joining PAY_DEFINED_BALANCES to resolve balance names.
• Audit reconciliation, comparing VALUE against PREV_BALANCE_VALUE to detect retroactive adjustments.
• Expiry tracking, filtering on EXPIRY_DATE to identify balances pending expiration.

A representative query joins the three foreign keys:

• SELECT lb.VALUE, db.BALANCE_NAME, lb.EXPIRY_DATE FROM PAY_LATEST_BALANCES lb JOIN PAY_DEFINED_BALANCES db ON db.DEFINED_BALANCE_ID = lb.DEFINED_BALANCE_ID WHERE lb.ASSIGNMENT_ID = :p_assignment_id.

Related Objects

• PAY_DEFINED_BALANCES — joined on DEFINED_BALANCE_ID; supplies balance name and classification.
• PAY_ASSIGNMENT_ACTIONS — joined on ASSIGNMENT_ACTION_ID; identifies the driving payroll action.
• PAY_PROCESS_GROUPS — joined on PROCESS_GROUP_ID; defines the calculation grouping.
• PER_ALL_ASSIGNMENTS_F and PER_ALL_PEOPLE_F — joined on ASSIGNMENT_ID and PERSON_ID for assignment and person detail.
• PAY_BALANCE_VALUES and balance run result tables — the transactional source from which latest values are derived.
• PAY_BALANCE_FEEDS / PAY_BALANCE_DIMENSIONS — provide the dimensional context used when a balance is calculated.

Together these relationships place PAY_LATEST_BALANCES as the read-optimized satellite of the payroll balance model, central to reporting and inquiry rather than to balance generation itself.