Results for “pay_assignment_actions_v”

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

Overview

PAY_ASSIGNMENT_ACTIONS_V is a PL/SQL-based view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PAY (Payroll) product family. In both 12.1.1 and 12.2.2, its documented purpose is to support the Payroll user interface rather than to serve as a public integration interface. The view joins the payroll action header retained in PAY_PAYROLL_ACTIONS with the assignment-level action rows stored in PAY_ASSIGNMENT_ACTIONS, and enriches each row with assignment, person, and lookup context so that the forms and OAF pages rendering the Payroll Processes, Assignment Processes, and related status windows can present human-readable values without additional round trips.

Because the view is code-based, on-line, and driven by DECODE and packaged function calls, its content is highly dynamic. The WHERE clause excludes action types 'Z', 'X', and 'BEE', and restricts processed actions to those whose effective date falls within the effective date ranges of the assignment and person records, ensuring only currently applicable assignment and person versions are returned. Tables such as PER_ASSIGNMENTS_F2 and PER_PEOPLE_F are date-effective views, so consumers must expect the join to be resolved against the appropriate versioned rows. The view is not intended for high-volume batch reporting; the underlying hints (INDEX on PAY_PAYROLL_ACTIONS_PK with USE_NL) and function invocation per row make row-by-row form-style retrieval the optimal access pattern.

Underlying Base Objects

The documented base objects reveal a three-tier dependency. The transactional core consists of PAY_PAYROLL_ACTIONS (via synonym) and PAY_ASSIGNMENT_ACTIONS (via synonym), joined on PAYROLL_ACTION_ID. Context comes from PER_ASSIGNMENTS_F2 and PER_PEOPLE_F, which supply ASSIGNMENT_NUMBER, person full name, and effective date boundaries. Reference data is drawn from HR_LOOKUPS, filtered to LOOKUP_TYPE = 'ACTION_TYPE', to translate the ACTION_TYPE code into its meaning.

Functionality is layered through PL/SQL packages. PAY_ASSIGNMENT_ACTIONS_PKG.GET_ACTION_STATUS derives the displayed action status, and MESSAGE_LINE_EXISTS flags the presence of messages for the assignment action. HR_GENERAL.DECODE_LOOKUP resolves lookup meanings, including the SLA versus GL variant for transfer-to-ledger actions. HR_PAYROLLS.DISPLAY_PERIOD_NAME renders the payroll period name. HR_PERSON_NAME, HR_API, HR_SECURITY, and PAY_BATCH_LINES further support display and security filtering. A UNION ALL branch duplicates the structure to combine two retrieval paths, which is why consumers should treat duplicate-looking rows as distinct ROW_ID values.

Key Columns

• ROW_ID — AAC.ROWID of the underlying assignment action row; unique within each union branch.
• ASSIGNMENT_ACTION_ID / PAYROLL_ACTION_ID — Primary and foreign keys linking to PAY_ASSIGNMENT_ACTIONS and PAY_PAYROLL_ACTIONS.
• ASSIGNMENT_ID, ASSIGNMENT_NUMBER — Assignment identity, with ASG_START_DATE and ASG_END_DATE showing the effective version used.
• FULL_NAME, PEO_START_DATE, PEO_END_DATE — Person name and the person effective dates applied.
• ACTION_TYPE / TYPE — Raw action type code and its decoded meaning, with the SLA/GL distinction for transfers.
• ACTION_STATUS (ACTION_STATUS) / STATUS_CODE — Decoded status label and raw ACTION_STATUS code.
• EFFECTIVE_DATE, DATE_EARNED, PERIOD_NAME — Process date, date earned, and displayed payroll period.
• PRE_PAYMENT_ID, ACTION_SEQUENCE, SECONDARY_STATUS, PURGE_PHASE — Prepayment linkage, ordering within the payroll action, secondary state, and purge phase.
• MESSAGES_EXIST — Indicator that a message line exists for the assignment action.
• BUSINESS_GROUP_ID — Business group for security and multi-org filtering.

Common Use Cases and Queries

Typical uses include locating the actions created by a given payroll action for troubleshooting, listing the assignments and people included in a payroll run, checking decoded action status during concurrent request monitoring, and surfacing message existence indicators in custom reports.

• List all assignment actions for a payroll action: SELECT assignment_action_id, assignment_number, full_name, action_status, period_name FROM pay_assignment_actions_v WHERE payroll_action_id = :p_payroll_action_id ORDER BY action_sequence;
• Find failed or unprocessed actions by status: SELECT assignment_action_id, full_name, status_code, action_status FROM pay_assignment_actions_v WHERE status_code NOT IN ('P','C') AND business_group_id = :p_bg_id;
• Identify actions with messages: SELECT assignment_action_id, full_name, action_status FROM pay_assignment_actions_v WHERE messages_exist = 'Y';
• Actions by effective date range: SELECT assignment_number, full_name, action_type, type, effective_date FROM pay_assignment_actions_v WHERE effective_date BETWEEN :p_start AND :p_end;

Because the view invokes PL/SQL functions per row and depends on date-effective person and assignment views, joins to it should be restricted by PAYROLL_ACTION_ID or an equivalent selective predicate. For bulk data extraction, querying PAY_ASSIGNMENT_ACTIONS and PAY_PAYROLL_ACTIONS directly, applying the same decode and lookup logic, will generally outperform the view.