Search Results source_text2




Overview
Explore in AI Chat

Overview

APPS.PAY_BALANCE_CONTEXT_VALUES_V1 is a reporting view in the Oracle E-Business Suite (EBS) HRMS/Payroll schema, documented in ETRM for releases 12.1.1 and 12.2.2. It presents the context dimension values that qualify payroll balance records, exposing a normalized (entity-attribute-value style) projection of balance context information onto a single (CONTEXT_ID, LATEST_BALANCE_ID, VALUE) tuple. Each row associates a specific context identifier with a specific balance and the corresponding context value.

The view is defined as a UNION ALL of two branches. The first branch selects directly from PAY_BALANCE_CONTEXT_VALUES, returning stored context rows with CONTEXT_ID, LATEST_BALANCE_ID and VALUE. The second branch synthesizes context rows dynamically from PAY_LATEST_BALANCES, cross-referenced to FF_CONTEXTS, decoding the appropriate PLB column for each context name. The result is a complete, consolidated picture of balance context values regardless of whether a context value is explicitly persisted in the context-values table or derived from the current state of the latest-balances record.

This structure makes the view valuable for reporting, reconciliation, and integration where consumers require a uniform context-value interface rather than dealing with the individual columns of PAY_LATEST_BALANCES.

Underlying Base Objects

The documented base objects are three synonyms resolving to APPS-owned tables/synonyms:

The second branch filters FC.CONTEXT_NAME to the enumerated set of supported contexts and applies an IS NOT NULL predicate per context, ensuring only populated context values are emitted.

Key Columns

  • CONTEXT_ID — identifier of the balance context (from FF_CONTEXTS in the derived branch).
  • LATEST_BALANCE_ID — the balance record the context value qualifies.
  • VALUE — the context value itself, sourced either from the stored table or from the decoded PLB column. The DECODE maps JURISDICTION_CODE, TAX_UNIT_ID, SOURCE_ID, SOURCE_TEXT, SOURCE_NUMBER, SOURCE_TEXT2, TAX_GROUP, ORIGINAL_ENTRY_ID and PAYROLL_ID to their respective columns.

Notably, the search term source_text2 corresponds to context name 'SOURCE_TEXT2', decoded from PLB.SOURCE_TEXT2 and included in the FC.CONTEXT_NAME IN list and the per-context null check.

Common Use Cases and Queries

Typical uses include reporting balance context detail, verifying whether a context value is stored versus derived, and building integrations that require a generic context-value feed.

  • Retrieve all context values for a given balance:
    SELECT context_id, latest_balance_id, value FROM apps.pay_balance_context_values_v1 WHERE latest_balance_id = :p_balance_id;
  • Filter for a specific source text attribute:
    SELECT latest_balance_id, value FROM apps.pay_balance_context_values_v1 WHERE context_id = (SELECT context_id FROM ff_contexts WHERE context_name = 'SOURCE_TEXT2');
  • Join to FF_CONTEXTS to label context names:
    SELECT c.context_name, v.latest_balance_id, v.value FROM apps.pay_balance_context_values_v1 v, apps.ff_contexts c WHERE v.context_id = c.context_id;

Because the view unions stored and derived sources, queries should account for potential duplicate logical context entries; DISTINCT or aggregation may be required depending on the reporting requirement.