Search Results secondary_status_code

Overview

The PAYBV_ASSIGNMENT_ACTION view is a business intelligence (BIS) reporting view owned by the APPS schema in Oracle E-Business Suite. It is registered against the Payroll (PAY) product and holds a VALID status in both release 12.1.1 and 12.2.2. The view presents payroll assignment action data in a decoded, presentation-ready form, supplementing the raw status identifiers stored in the underlying transaction table with human-readable equivalents.

Assignment actions represent discrete payroll processing events performed against an assignment — for example, a payroll run, a reversal, a quick pay, or a balance adjustment. Each action carries an action status that describes where it stands in the processing lifecycle (such as Unprocessed, Marked for Retry, Processed, or Reversed). The view exposes both the raw status code and the decoded meaning side by side, which makes it suitable for reporting layers, extracts, and integration interfaces that must not embed EBS lookup decoding logic themselves.

The view is defined as a read-only projection over the base synonym and includes the WITH READ ONLY clause, confirming that it is intended strictly for query and reporting purposes. No DML is permitted through it.

Underlying Base Objects

The documented base objects for this view are:

• PAY_ASSIGNMENT_ACTIONS (SYNONYM) — the primary source of all assignment action rows, aliased as PAA in the view text.
• HR_BIS (PACKAGE) — supplies the BIS_DECODE_LOOKUP function used to translate status codes into descriptive text.

The select list references PAA for every column, with the exception of the two decoded status columns, which are produced by calls to HR_BIS.BIS_DECODE_LOOKUP('ACTION_STATUS', ...). Two separate decode calls are made: one against ACTION_STATUS and one against SECONDARY_STATUS. The view therefore performs a lookup translation at query time rather than storing decoded values, which means the returned description reflects the current lookup definition for the ACTION_STATUS lookup type.

Key Columns

• ACTION_STATUS — the decoded, descriptive form of the primary action status.
• ACTION_STATUS_CODE — the raw lookup code for the primary status. This is the column most commonly targeted when users search for action_status_code.
• SECONDARY_STATUS / SECONDARY_STATUS_CODE — the decoded and raw forms of the secondary status, used where an action carries an additional qualifying state.
• ASSIGNMENT_ACTION_ID — the unique identifier of the assignment action; the primary key of the base record.
• ASSIGNMENT_ID — the assignment against which the action was performed.
• PAYROLL_ACTION_ID — the parent payroll action that groups this assignment action.
• SOURCE_ACTION_ID — the originating action, populated for reversal and correction records.
• PRE_PAYMENT_ID — the prepayment associated with the action, where applicable.
• TAX_UNIT_ID — the tax unit under which the action was processed.
• RUN_TYPE_ID — the run type of the payroll run.
• CHUNK_NUMBER, ACTION_SEQUENCE, SERIAL_NUMBER — sequencing attributes used to order and partition actions within a payroll process.
• START_DATE, END_DATE — the effective date range of the action.
• OBJECT_TYPE, OBJECT_ID, OBJECT_VERSION_NUMBER — standard EBS object-versioning and entity identification columns.

Common Use Cases and Queries

Typical uses include payroll processing dashboards, reconciliation reports that compare action statuses across runs, and integration extracts that feed downstream payroll analytics. Because both codes and descriptions are exposed, the view supports filters written against either form:

• Locating all assignment actions in a given status, for example SELECT assignment_action_id, assignment_id, action_status FROM paybv_assignment_action WHERE action_status_code = 'U';
• Joining to PAY_ASSIGNMENT_ACTIONS or PAY_PAYROLL_ACTIONS on ASSIGNMENT_ACTION_ID or PAYROLL_ACTION_ID to enrich the decoded status with additional payroll context.
• Identifying reversal records by filtering on a non-null SOURCE_ACTION_ID.
• Reporting secondary status distribution through SECONDARY_STATUS_CODE and SECONDARY_STATUS.

Because the decode is performed at runtime, report authors should confirm that the ACTION_STATUS lookup contains the codes they intend to filter on, and should prefer ACTION_STATUS_CODE in WHERE predicates for index-friendly and stable results.