Results for “display_run_number”

50+ results




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

Overview

PAY_PAYROLL_ACTIONS_V7 is a read-only view owned by the APPS schema within the Oracle E-Business Suite Payroll (PAY) product. It is documented in ETRM as a user-interface support object, meaning it is not intended as a general-purpose integration interface but rather as a presentation-layer query that backs Oracle Forms, OAF pages, and related payroll administrative screens. It exposes the master list of payroll actions — the discrete processing runs (such as payroll runs, prepayments, reversals, and consolidation) that a payroll administrator initiates against a payroll — enriched with lookup meanings, period names, and concurrent request status information. The view remains VALID in both 12.1.1 and 12.2.2, and its definition is stable across those releases. Typical consumers are Oracle's own Payroll processes and any custom reporting that needs to mirror the action list shown to end users, including the derived STATUS_CODE logic that maps a pending action to "E" (completed/error) when its concurrent request phase is closed.

Underlying Base Objects

The view is defined as a UNION ALL of two branches over the central action table. The primary branch joins PAY_PAYROLL_ACTIONS (exposed as a synonym) to PER_TIME_PERIODS (synonym) by PAYROLL_ID and effective date range, to PAY_PAYROLLS_F by PAYROLL_ID and effective dates, to HR_LOOKUPS on LOOKUP_TYPE = 'ACTION_TYPE', and outermost-joins FND_CONCURRENT_REQUESTS on REQUEST_ID (+). The second branch handles actions where PAYROLL_ID IS NULL, joining only HR_LOOKUPS and FND_CONCURRENT_REQUESTS. Both branches filter out ACTION_STATUS = 'U' (unprocessed) and ACTION_TYPE = 'I' (the reversal/initialization type used during upgrade). ETRM also lists HR_API, HR_GENERAL, HR_PAYROLLS, and HR_SECURITY as referenced objects; HR_PAYROLLS.DISPLAY_PERIOD_NAME is invoked directly in the SELECT list, while HR_API and HR_SECURITY typically support the security predicates and display formatting invoked by the underlying packages. The result is a denormalized projection that shields the caller from multi-table joins.

Key Columns

  • ROW_ID / PAYROLL_ACTION_ID: Row identifier and the primary key of the underlying action record.
  • BUSINESS_GROUP_ID, PAYROLL_ID: The business group and payroll context; PAYROLL_NAME resolves the payroll's descriptive name.
  • ACTION_TYPE / MEANING: The lookup code and its decoded meaning (e.g., Run, Reversal, Quick Pay).
  • EFFECTIVE_DATE, DATE_EARNED, PERIOD_NAME: Timing context; PERIOD_NAME is derived via HR_PAYROLLS.DISPLAY_PERIOD_NAME.
  • ACTION_STATUS / STATUS_CODE: Raw status and the UI-adjusted status, where 'P' plus a closed concurrent request phase ('C') is presented as 'E'.
  • REQUEST_ID: Links to FND_CONCURRENT_REQUESTS for job status, phase, and log access.
  • ACTION_SEQUENCE, DISPLAY_RUN_NUMBER: Ordering and run numbering used in the action list.
  • CONSOLIDATION_SET_ID, ASSIGNMENT_SET_ID, ELEMENT_SET_ID: Population scope identifiers for the run.
  • COMMENTS: Free-text notes entered by the administrator.

Common Use Cases and Queries

Typical uses include recreating the Payroll Actions window in custom reports, diagnosing why a run appears stuck, and joining action history to concurrent request logs. Because the view already resolves lookup meanings, period names, and request phase effects, it eliminates repetitive joins in ad hoc SQL.

List recent actions for a payroll:

SELECT payroll_name, period_name, meaning, status_code, display_run_number
FROM   apps.pay_payroll_actions_v7
WHERE  payroll_id = :p_payroll_id
AND    effective_date >= :p_from_date
ORDER  BY effective_date DESC, action_sequence DESC;

Interrogate a stalled or failed run via its concurrent request:

SELECT p.action_type, p.status_code, r.phase_code, r.status_code
FROM   apps.pay_payroll_actions_v7 p, fnd_concurrent_requests r
WHERE  p.request_id = r.request_id
AND    r.phase_code = 'R';

Reconcile actions lacking a payroll context (second UNION branch), which are typically non-payroll or setup-time actions:

SELECT action_type, effective_date, status_code
FROM   apps.pay_payroll_actions_v7
WHERE  payroll_id IS NULL
ORDER  BY effective_date DESC;

Because the view filters out ACTION_STATUS 'U' and ACTION_TYPE 'I', queries against it will not surface unprocessed or upgrade-generated rows; enumerate PAY_PAYROLL_ACTIONS directly when that granularity is required.