Search Results pay_retro_assignments
The PAY_RETRO_ASSIGNMENTS
table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a critical component of the Oracle Payroll module, specifically designed to manage retroactive payroll calculations. This table stores assignment-level data required for processing retroactive payments, ensuring accurate adjustments when payroll elements such as salary, bonuses, or deductions are modified after the original payroll run. Below is a detailed breakdown of its structure, functionality, and integration within Oracle EBS.
Purpose and Functionality
The primary purpose ofPAY_RETRO_ASSIGNMENTS
is to track assignments (employee-job associations) affected by retroactive changes. When payroll elements are retroactively updated—due to late approvals, corrections, or backdated adjustments—this table identifies the impacted assignments and ensures recalculations are applied correctly in subsequent payroll runs. It acts as a staging area for retro processing, linking retroactive events to specific assignments and payroll periods.
Key Columns and Data Structure
The table includes columns essential for retro processing:- RETRO_ASSIGNMENT_ID: Primary key uniquely identifying each retro assignment record.
- ASSIGNMENT_ID: References
PER_ALL_ASSIGNMENTS_F
, linking to the employee assignment. - EFFECTIVE_DATE: Date when the retroactive change takes effect.
- RETRO_COMPONENT_ID: Ties to
PAY_RETRO_COMPONENTS
, defining the type of retro calculation (e.g., salary, bonus). - STATUS: Indicates processing state (e.g., PENDING, PROCESSED, ERROR).
- CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE: Standard Oracle audit columns.
Integration with Payroll Processes
PAY_RETRO_ASSIGNMENTS
integrates with several core payroll tables and processes:
- Retro Payroll Calculation: During payroll runs, the Oracle RetroPay process queries this table to identify assignments needing recalculation. It pulls retroactive changes from
PAY_RETRO_ELEMENTS
and applies them to the current payroll cycle. - Element Links: Retroactive elements (stored in
PAY_ELEMENT_ENTRIES_F
) reference this table to ensure adjustments align with the correct assignments. - Rollback and Error Handling: If a retro calculation fails, the STATUS column is updated to flag errors, allowing administrators to troubleshoot via standard Oracle Payroll diagnostics.
Technical Considerations
- Performance: Indexes on
ASSIGNMENT_ID
andEFFECTIVE_DATE
optimize query performance during large-scale retro processing. - Data Retention Records are retained for audit purposes but may be archived post-processing to manage table growth.
- Custom Extensions: While Oracle discourages direct DML on this table, custom PL/SQL logic can leverage its data for advanced retro scenarios.
Conclusion
ThePAY_RETRO_ASSIGNMENTS
table is a cornerstone of Oracle Payroll's retroactive processing capability, ensuring compliance and accuracy in dynamic payroll environments. Its design supports traceability, scalability, and integration with other payroll modules, making it indispensable for organizations managing complex payroll adjustments in Oracle EBS 12.1.1 and 12.2.2.
-
Table: PAY_RETRO_ASSIGNMENTS
12.2.2
owner:HR, object_type:TABLE, fnd_design_data:PAY.PAY_RETRO_ASSIGNMENTS, object_name:PAY_RETRO_ASSIGNMENTS, status:VALID, product: PAY - Payroll , description: Identifies assignment for reprocessing , implementation_dba_data: HR.PAY_RETRO_ASSIGNMENTS ,
-
Table: PAY_RETRO_ASSIGNMENTS
12.1.1
owner:HR, object_type:TABLE, fnd_design_data:PAY.PAY_RETRO_ASSIGNMENTS, object_name:PAY_RETRO_ASSIGNMENTS, status:VALID, product: PAY - Payroll , description: Identifies assignment for reprocessing , implementation_dba_data: HR.PAY_RETRO_ASSIGNMENTS ,
-
APPS.PAY_RETRO_NOTIF_PKG dependencies on PAY_RETRO_ASSIGNMENTS
12.1.1
-
APPS.PY_ROLLBACK_PKG dependencies on PAY_RETRO_ASSIGNMENTS
12.1.1
-
APPS.PY_ROLLBACK_PKG dependencies on PAY_RETRO_ASSIGNMENTS
12.2.2
-
APPS.PAY_US_WORKFLOW_API_PKG dependencies on PAY_RETRO_ASSIGNMENTS
12.2.2
-
APPS.PAY_RETRO_NOTIF_PKG dependencies on PAY_RETRO_ASSIGNMENTS
12.2.2
-
APPS.PAY_RETRO_STATUS_INTERNAL dependencies on PAY_RETRO_ASSIGNMENTS
12.2.2
-
APPS.PAY_NL_GENERAL dependencies on PAY_RETRO_ASSIGNMENTS
12.2.2
-
APPS.PAY_RETRO_STATUS_INTERNAL dependencies on PAY_RETRO_ASSIGNMENTS
12.1.1
-
APPS.PAY_RETRO_PKG dependencies on PAY_RETRO_ASSIGNMENTS
12.1.1
-
APPS.PAY_RETRO_UTILS_PKG dependencies on PAY_RETRO_ASSIGNMENTS
12.1.1
-
APPS.HR_DELETE dependencies on PAY_RETRO_ASSIGNMENTS
12.2.2
-
APPS.HR_DELETE dependencies on PAY_RETRO_ASSIGNMENTS
12.1.1
-
APPS.PAY_US_RETRO_OVERLAP dependencies on PAY_RETRO_ASSIGNMENTS
12.2.2
-
APPS.PAY_RETRO_PKG dependencies on PAY_RETRO_ASSIGNMENTS
12.2.2
-
APPS.PAY_RETRO_UTILS_PKG dependencies on PAY_RETRO_ASSIGNMENTS
12.2.2
-
APPS.PAY_RETRO_UTILS_PKG SQL Statements
12.2.2
-
APPS.PAY_RETRO_STATUS_INTERNAL SQL Statements
12.2.2
-
APPS.PAY_RETRO_STATUS_INTERNAL SQL Statements
12.1.1
-
TABLE: HR.PAY_RETRO_ASSIGNMENTS
12.1.1
owner:HR, object_type:TABLE, fnd_design_data:PAY.PAY_RETRO_ASSIGNMENTS, object_name:PAY_RETRO_ASSIGNMENTS, status:VALID,
-
VIEW: HR.PAY_RETRO_ASSIGNMENTS#
12.2.2
owner:HR, object_type:VIEW, object_name:PAY_RETRO_ASSIGNMENTS#, status:VALID,
-
APPS.PAY_RETRO_UTILS_PKG SQL Statements
12.1.1
-
SYNONYM: PUBLIC.PAY_RETRO_ASSIGNMENTS
12.1.1
owner:PUBLIC, object_type:SYNONYM, object_name:PAY_RETRO_ASSIGNMENTS, status:VALID,
-
APPS.HR_DYNSQL dependencies on PAY_OBJECT_GROUPS
12.2.2
-
APPS.PY_ROLLBACK_PKG dependencies on PAY_RETRO_ENTRIES
12.2.2
-
SYNONYM: APPS.PAY_RETRO_ASSIGNMENTS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PAY_RETRO_ASSIGNMENTS, status:VALID,
-
SYNONYM: APPS.PAY_RETRO_ASSIGNMENTS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PAY_RETRO_ASSIGNMENTS, status:VALID,
-
VIEW: HR.PAY_RETRO_ASSIGNMENTS#
12.2.2
-
APPS.PY_ROLLBACK_PKG dependencies on PAY_RETRO_ENTRIES
12.1.1
-
TABLE: HR.PAY_RETRO_ASSIGNMENTS
12.2.2
owner:HR, object_type:TABLE, fnd_design_data:PAY.PAY_RETRO_ASSIGNMENTS, object_name:PAY_RETRO_ASSIGNMENTS, status:VALID,
-
APPS.HR_DYNSQL dependencies on PAY_OBJECT_GROUPS
12.1.1
-
APPS.PAY_RETRO_PKG dependencies on DUAL
12.1.1
-
APPS.HR_DELETE dependencies on PAY_RETRO_ENTRIES
12.2.2
-
APPS.PAY_US_RETRO_OVERLAP dependencies on PAY_ASSIGNMENT_ACTIONS
12.2.2
-
APPS.HR_DELETE dependencies on PAY_RETRO_ENTRIES
12.1.1
-
APPS.PAY_RETRO_NOTIF_PKG dependencies on PAY_RETRO_ENTRIES
12.2.2
-
TRIGGER: APPS.PAY_RETRO_ASSIGNMENTS_WHO
12.1.1
owner:APPS, object_type:TRIGGER, object_name:PAY_RETRO_ASSIGNMENTS_WHO, status:VALID,
-
APPS.PAY_RETRO_NOTIF_PKG dependencies on PAY_RETRO_ENTRIES
12.1.1
-
APPS.PAY_NL_GENERAL dependencies on PAY_RETRO_ENTRIES
12.2.2
-
APPS.PAY_US_WORKFLOW_API_PKG dependencies on PAY_PAYROLL_ACTIONS
12.2.2
-
APPS.PAY_NL_GENERAL dependencies on PER_ALL_ASSIGNMENTS_F
12.2.2
-
APPS.PAY_RETRO_STATUS_INTERNAL dependencies on FND_MESSAGE
12.2.2
-
PACKAGE BODY: APPS.PAY_US_RETRO_OVERLAP
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:PAY_US_RETRO_OVERLAP, status:VALID,
-
TRIGGER: APPS.PAY_RETRO_ASSIGNMENTS_WHO
12.2.2
owner:APPS, object_type:TRIGGER, object_name:PAY_RETRO_ASSIGNMENTS_WHO, status:VALID,
-
APPS.PAY_US_WORKFLOW_API_PKG dependencies on PAY_ASSIGNMENT_ACTIONS
12.2.2
-
APPS.PAY_RETRO_UTILS_PKG dependencies on DUAL
12.2.2
-
APPS.PAY_RETRO_UTILS_PKG dependencies on HR_API
12.2.2
-
PACKAGE BODY: APPS.PAY_RETRO_UTILS_PKG
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:PAY_RETRO_UTILS_PKG, status:VALID,
-
APPS.PAY_RETRO_UTILS_PKG dependencies on DUAL
12.1.1