Search Results org_info

Overview

PAY_BALANCE_VALUES_V is an APPS-owned database view in the Oracle E-Business Suite Payroll (PAY) product module. It is registered in ETRM as VALID and described as a "sales ADS DISCO workbook req," indicating it was created to satisfy a specific reporting requirement rather than as a general-purpose seeded object. The view presents calculated payroll balance values at the level of individual assignment actions, combining assignment-action context, payroll action context, balance type and dimension metadata, and the resolved numeric value produced by the payroll balance engine. In effect, it exposes the output of PAY_BALANCE_PKG.GET_VALUE joined to the descriptive attributes of the balance definition that produced it.

Because it is a view and not a table, it carries no independent storage. Its role is to flatten the complex relationships between payroll runs, run results, run result values, balance feeds, defined balances, and balance dimensions into a single queryable row set suitable for reporting, reconciliation, and downstream integration or data-warehouse extraction.

Underlying Base Objects

The view is defined over a set of APPS synonyms and packages, all documented in the 12.2.2 metadata:

• PAY_ASSIGNMENT_ACTIONS — drives the assignment action and payroll action identifiers.
• PAY_PAYROLL_ACTIONS — supplies effective date, payroll identifier, and business group context.
• PAY_BALANCE_TYPES — provides balance type and balance name.
• PAY_BALANCE_DIMENSIONS — provides dimension name, database item suffix, routing, and description.
• PAY_DEFINED_BALANCES — the defined balance being evaluated.
• PAY_BALANCE_FEEDS_F, PAY_RUN_RESULTS, and PAY_RUN_RESULT_VALUES — the underlying run result data that feeds balances.
• PAY_ACTION_CONTEXTS and FF_CONTEXTS — the action context values (jurisdiction, source, tax, org entry, time definition, balance date) used both as inputs to the balance call and as decoded output columns.
• HR_ORGANIZATION_INFORMATION — organization context referenced through the org entry attribute.
• FND_DATE — provides canonical-to-date conversion for balance date context values.
• PAY_BALANCE_PKG — the engine package invoked for both GET_VALUE and CHK_CONTEXT.

Key Columns

• ASSIGNMENT_ACTION_ID, ASSIGNMENT_ID, PAYROLL_ACTION_ID — identify the payroll action and assignment being evaluated.
• EFFECTIVE_DATE, PAYROLL_ID — the payroll run context.
• BALANCE_TYPE_ID, BALANCE_NAME — the balance being reported.
• BALANCE_DIMENSION_ID, DIMENSION_NAME, DATABASE_ITEM_SUFFIX, DIMENSION_DESCRIPTION — the dimension under which the balance is measured.
• DEFINED_BALANCE_ID, ROUTE_ID — the defined balance and its routing, which govern which contexts are relevant.
• VALUE — the numeric balance value returned by PAY_BALANCE_PKG.GET_VALUE.
• TAX_GROUP, JURISDICTION, SOURCE_ID, SOURCE_TEXT, SOURCE_TEXT2, ORIGINAL_ENTRY_ID, TIME_DEFINITION_ID, BALANCE_DATE — context attributes, each conditionally populated based on PAY_BALANCE_PKG.CHK_CONTEXT against the route.
• BUSINESS_GROUP_ID — the business group scope.

Common Use Cases and Queries

Typical uses include payroll balance reconciliation, validating run result values against defined balances, and extracting balance data for a data warehouse or third-party reporting tool. Because the underlying call to PAY_BALANCE_PKG.GET_VALUE is executed per row, queries against this view are expensive; filters on assignment action, payroll, balance type, and effective date should always be applied. The user's search term "org_info" corresponds to the organization information context (via HR_ORGANIZATION_INFORMATION and the org entry context), which is exposed through ORIGINAL_ENTRY_ID.

A representative query:

SELECT pbv.assignment_action_id,
       pbv.assignment_id,
       pbv.payroll_id,
       pbv.effective_date,
       pbv.balance_name,
       pbv.dimension_name,
       pbv.value,
       pbv.jurisdiction,
       pbv.balance_date
  FROM apps.pay_balance_values_v pbv
 WHERE pbv.payroll_id = :p_payroll_id
   AND pbv.effective_date = :p_effective_date
   AND pbv.balance_name = :p_balance_name
 ORDER BY pbv.assignment_id, pbv.dimension_name;