Results for “pay_assignment_actions_v2”
34 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PAY_ASSIGNMENT_ACTIONS_V2 is an APPS-owned database view in the Oracle E-Business Suite Payroll (PAY) product, validated and available in both 12.1.1 and 12.2.2. It is defined specifically to support the UK Pay Advice Report and is built on top of the PAY_ASSIGNMENT_ACTIONS table, joining it to a broad set of payroll, assignment, and person entities. Rather than exposing raw assignment action rows, the view consolidates each assignment action with the corresponding prepayment and run payroll action context, the person's identifying details, the assignment's pay basis and salary, the job, and the full set of PAY_PEOPLE_GROUPS segments.
The view therefore serves as a reporting and integration surface for payroll advice generation, allowing a pay advice to be produced showing salary, pay basis, job title, and payment grouping information for completed payroll runs. The presence of RPPA.DATE_EARNED and the NVL over PAY_ADVICE_DATE and PTP.PAY_ADVICE_DATE confirms that the view is oriented toward payment advice dating.
Underlying Base Objects
The ETRM 12.2.2 metadata documents the referenced base objects as HR_GENERAL (package), HR_PERSON_NAME (package), HR_SECURITY (package), PAY_ACTION_INTERLOCKS (synonym), PAY_ASSIGNMENT_ACTIONS (synonym), PAY_GB_PAYROLL_ACTIONS_PKG (package), PAY_PAYROLL_ACTIONS (synonym), PAY_PEOPLE_GROUPS (synonym), PER_ALL_ASSIGNMENTS_F (synonym), PER_JOBS_TL (synonym), PER_PEOPLE_F (view), and PER_TIME_PERIODS (synonym).
Functionally, the from clause joins PAY_ASSIGNMENT_ACTIONS (aliased PAA, the prepayment assignment action), PAY_PAYROLL_ACTIONS (PPA, the prepayment payroll action), a second PAY_ASSIGNMENT_ACTIONS (RPAA, the run assignment action), PAY_PAYROLL_ACTIONS (RPPA, the run payroll action), PER_ALL_ASSIGNMENTS_F, PER_PEOPLE_F, PER_JOBS_TL, PAY_ACTION_INTERLOCKS, PER_TIME_PERIODS, and PAY_PEOPLE_GROUPS. The link between prepayment and run actions is made by joining PAA.PAYROLL_ACTION_ID = PPA.PAYROLL_ACTION_ID, restricted to ACTION_TYPE IN ('U','P') and ACTION_STATUS = 'C'. The HR_GENERAL and PER_PEOPLE_F packages support the decode and name logic, while HR_SECURITY supports row-level access restrictions.
Key Columns
- ROW_ID, ASSIGNMENT_ID, ASSIGNMENT_ACTION_ID — the surviving assignment action identifiers; RUN_ASSIGNMENT_ACTION_ID distinguishes the run action.
- PAYROLL_ACTION_ID and RUN_PAYROLL_ACTION_ID — link back to the prepayment and run payroll actions respectively. RUN_PAYROLL_ACTION_ID is the effective stand-in for the run_payroll_action_id concept used when filtering to a specific payroll run.
- SALARY, PAY_BASIS, JOB_TITLE, FULL_NAME, TITLE, INITIALS, LAST_NAME, ASSIGNMENT_NUMBER — descriptive attributes produced by PAY_GB_PAYROLL_ACTIONS_PKG.GET_SALARY, HR_GENERAL.DECODE_PAY_BASIS, and person name functions.
- NI_NUMBER, INTERNAL_ADDRESS_LINE, LOCATION_ID, EXPENSE_CHECK_SEND_TO_ADDRESS — UK pay advice address and National Insurance details.
- DATE_EARNED, TIME_PERIOD_ID, PAYROLL_ID, PAY_ADVICE_DATE — payroll timing and advice dating.
- SEGMENT1 through SEGMENT30 — the PAY_PEOPLE_GROUPS key flexfield segments, enabling payroll grouping and consolidation reporting.
Common Use Cases and Queries
The primary use case is the UK Pay Advice Report, retrieving advice data for a completed run and grouping by payroll action. A typical query filters by the run payroll action identifier and payroll:
SELECT assignment_id, run_assignment_action_id, full_name, salary, pay_basis, last_name, ni_number, date_earned, pay_advice_date FROM apps.pay_assignment_actions_v2 WHERE run_payroll_action_id = :p_run_payroll_action_id ORDER BY last_name, full_name;SELECT DISTINCT payroll_id, run_payroll_action_id, pay_advice_date FROM apps.pay_assignment_actions_v2 WHERE payroll_id = :p_payroll_id;SELECT assignment_number, full_name, internal_address_line, expense_check_send_to_address, ni_number FROM apps.pay_assignment_actions_v2 WHERE assignment_action_id = :p_assignment_action_id;
Because HR_SECURITY is referenced, results are implicitly subject to the applying security profile. Queries should join run_payroll_action_id to the run PAY_PAYROLL_ACTIONS row, not to the prepayment action, to schedule advice for the correct payroll run.
-
View for the UK Pay Advice Report based on the PAY_ASSIGNMENT_ACTIONS table.
APPS.PAY_ASSIGNMENT_ACTIONS_V2·↳ HR_GENERAL·↳ HR_PERSON_NAME·↳ HR_SECURITY·Explore PAY module →
-
View for the UK Pay Advice Report based on the PAY_ASSIGNMENT_ACTIONS table.
APPS.PAY_ASSIGNMENT_ACTIONS_V2·↳ HR_GENERAL·↳ HR_PERSON_NAME·↳ HR_SECURITY·Explore PAY module →
-
SYNONYM: APPS.PER_JOBS_TL 12.1.1
-
SYNONYM: APPS.PER_JOBS_TL 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
VIEW: APPS.PER_PEOPLE_F 12.1.1
-
VIEW: APPS.PER_PEOPLE_F 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.2.2
Temporary table used to hold invalid location addresses.
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.
-
eTRM - PAY Tables and Views 12.2.2
Temporary table used to hold invalid location addresses.
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person