Results for “messages_exist”

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

Overview

PAY_PAYROLL_ACTIONS_V6 is a PL/SQL-based view in the APPS schema that belongs to the Oracle Payroll (PAY) product family. Per the Enterprise Technical Reference Manual (ETRM), its documented purpose is "to support user interface" — that is, it is not a standalone business entity but a presentation-layer construct that reformats and enriches the base payroll action data for display in the Oracle E-Business Suite Payroll forms and related self-service pages. It is particularly significant to users searching on action_type because the view exposes the ACTION_TYPE column directly and also derives human-readable action descriptions from it, which is precisely the column the Payroll run and action windows rely on to filter and describe payroll processes.

The view is versioned (_V6), which is a common Oracle EBS pattern: as the underlying business logic or UI requirements evolve, a new version of the view is created rather than altering the existing one, preserving backward compatibility for any dependent objects. This is consistent with the 12.1.1 / 12.2.2 code line, where the view must be present and VALID for the Payroll forms to function.

Underlying Base Objects

The ETRM documents the following referenced base objects:

• PAY_PAYROLL_ACTIONS (SYNONYM) — the primary driving table, aliased PAC1 in the view text. It holds the payroll run and related action records, including ACTION_TYPE, ACTION_STATUS, EFFECTIVE_DATE, and PAYROLL_ACTION_ID.
• PAY_PAYROLLS_F (VIEW) — the payroll definition table, joined with an outer join (+) to retrieve PRO.PAYROLL_NAME.
• PAY_ASSIGNMENT_ACTIONS (SYNONYM) — used in the correlated EXISTS sub-query that filters actions to those with associated assignment-level activity.
• PER_ASSIGNMENTS_F2 (VIEW) — also referenced in the EXISTS sub-query, linking actions to assignments for the current business group.
• PAY_PAYROLL_ACTIONS_PKG (PACKAGE) — supplies bind variable handling (GET_CHAR_BINDVAR, GET_NUM_BINDVAR) and display logic functions such as V_NAME, V_ACTION_STATUS, V_MESSAGES_EXIST, and DECODE_CHEQUE_TYPE.
• HR_GENERAL (PACKAGE) — provides DECODE_LOOKUP, used to translate lookup codes for ACTION_TYPE and TRANSFER_TO_LEDGER into display meanings.
• HR_PAYROLLS (PACKAGE) — provides DISPLAY_PERIOD_NAME to produce the period label.
• HR_SECURITY (PACKAGE) — participates in security filtering applied to assignment-linked actions.

Key Columns

• PAYROLL_ACTION_ID — the unique identifier of the payroll action; the primary join key.
• ACTION_TYPE — the code identifying the action (e.g., run, reversal, transfer to GL). Exposed directly and also fed into the MEANING decode.
• MEANING — the user-facing description of the action, derived via DECODE on ACTION_TYPE and DECODE_LOOKUP('ACTION_TYPE', …), with special handling for cheque ('H') and transfer-to-ledger ('T') types.
• NAME — a formatted action name produced by PAY_PAYROLL_ACTIONS_PKG.V_NAME.
• PERIOD_NAME — the payroll period label returned by HR_PAYROLLS.DISPLAY_PERIOD_NAME.
• ACTION_STATUS / STATUS_CODE — the raw status code and its descriptive equivalent (V_ACTION_STATUS).
• PAYROLL_NAME — the payroll definition name from PAY_PAYROLLS_F.
• ACTION_SEQUENCE, EFFECTIVE_DATE, REQUEST_ID — sequencing, dating, and concurrent request linkage.
• MESSAGES_EXIST — indicator from PAY_PAYROLL_ACTIONS_PKG.V_MESSAGES_EXIST.

Common Use Cases and Queries

The view's defining characteristic is that it only returns rows where ACTION_STATUS <> 'U' (not yet processed) and where ACTION_TYPE matches the value supplied through the bind variable GET_CHAR_BINDVAR('ACTION_TYPE') — when no bind value is supplied, the NVL causes all action types to be returned. This makes it ideal for action-oriented reporting.

A typical query filtering on the searched term would be:

SELECT payroll_action_id,
       action_type,
       meaning,
       name,
       period_name,
       action_status,
       payroll_name,
       effective_date
FROM   apps.pay_payroll_actions_v6
WHERE  action_type = 'R'
ORDER  BY effective_date DESC;

Other common scenarios include troubleshooting a payroll run by listing all actions for a given payroll name, extracting the MEANING column instead of the raw ACTION_TYPE for end-user reports, and auditing concurrent request linkage via REQUEST_ID. Note that because several SECURITY and bind-variable functions execute at query time, applications should avoid driving high-volume, unbounded queries against this view without an ACTION_TYPE or business group predicate.