Search Results pay_balance_context_values_v1




Overview
Explore in AI Chat

Overview

PAY_BALANCE_CONTEXT_VALUES_V1 is a documented Oracle E-Business Suite view owned by the APPS schema and classified under the PAY (Payroll) product family. Its status is recorded as VALID in the ETRM repository for both 12.1.1 and 12.2.2 reference environments. The view presents the context value assignments associated with payroll balance records, exposing each balance context as an individual row of context identifier, balance identifier, and resolved value. The trailing "_V1" suffix indicates that this object belongs to the versioned view family Oracle introduced to support the multi-versioned balance model used by payroll processing, replacing or supplementing legacy single-version balance views.

Functionally, the view unifies two sources of context data. The first is the persisted context value store maintained against balance records. The second is derived on the fly from PAY_LATEST_BALANCES by decoding discrete balance attributes — jurisdiction code, tax unit, source identifiers, source text fields, tax group, original entry identifier, and payroll identifier — into the generic (CONTEXT_ID, LATEST_BALANCE_ID, VALUE) shape. This design allows downstream consumers to query a single, uniform structure regardless of whether a given context is explicitly stored or implicitly derived from the balance row itself.

Underlying Base Objects

The ETRM metadata records three referenced base objects, each accessed through APPS synonyms: FF_CONTEXTS, PAY_BALANCE_CONTEXT_VALUES, and PAY_LATEST_BALANCES. The view definition composes a UNION ALL of two branches. The first branch selects CONTEXT_ID, LATEST_BALANCE_ID, and VALUE directly from PAY_BALANCE_CONTEXT_VALUES, the table that stores explicit context-value pairs against balance records. The second branch joins PAY_LATEST_BALANCES to FF_CONTEXTS, restricting FF_CONTEXTS to a fixed set of context names and emitting a value only where the corresponding column on the latest-balance row is not null. The PAY_LATEST_BALANCES table supplies the authoritative current balance rows, while FF_CONTEXTS supplies the context identifiers that give each derived value its context_name identity.

Key Columns

  • CONTEXT_ID — Reference to the context definition (from FF_CONTEXTS) that qualifies the associated value. It determines how the VALUE column should be interpreted.
  • LATEST_BALANCE_ID — Identifier of the parent row in PAY_LATEST_BALANCES to which the context value belongs. This is the join key back to balance data.
  • VALUE — The context value itself. Its datatype and meaning depend on CONTEXT_ID; documented context names include JURISDICTION_CODE, TAX_UNIT_ID, SOURCE_ID, SOURCE_TEXT, SOURCE_NUMBER, SOURCE_TEXT2, TAX_GROUP, ORIGINAL_ENTRY_ID, and PAYROLL_ID.

Common Use Cases and Queries

Typical uses include balance reporting filtered by a specific context, such as jurisdiction or tax unit, and extraction of all context values for a given balance to support reconciliation or payroll-to-GL analysis. The uniform column layout makes the view convenient for federated queries and integration extracts. A representative query is:

SELECT CONTEXT_ID, LATEST_BALANCE_ID, VALUE
FROM APPS.PAY_BALANCE_CONTEXT_VALUES_V1
WHERE LATEST_BALANCE_ID = :p_balance_id;

Because the view contains a UNION ALL over PAY_LATEST_BALANCES and FF_CONTEXTS, queries should ideally filter on CONTEXT_ID or LATEST_BALANCE_ID to avoid full scans. Care should be taken that VALUE is a polymorphic column; consumers must resolve its semantics using CONTEXT_ID in conjunction with FF_CONTEXTS before applying type-specific logic.