Search Results set_adp_extract_date

Overview

HR_ADP is an Oracle E-Business Suite PL/SQL package stored in the APPS schema that supports integration between Oracle HRMS and the ADP payroll and payment processing services. Its primary business function is to manage date-driven attributes required for ADP extracts and to support deduction and payment method processing on behalf of external payroll vendors. The package body is documented as VALID and is classified under the "OTHER" API category, meaning it is not part of the formally published public HRMS API set but is still relied upon internally by other EBS components. In Oracle EBS 12.1.1 and 12.2.2 environments, it acts as a utility layer between core HR/payroll tables and ADP-facing extraction routines. The ETRM documentation notes that HR_ADP is referenced by 21 other packages but does not itself reference any downstream database objects beyond its listed dependencies, positioning it as a low-level utility rather than a top-level orchestration module.

Key Procedures and Functions

Five documented procedures and functions are exposed by HR_ADP. Descriptions follow based strictly on their documented names and purpose:

• SET_ADP_EXTRACT_DATE — Establishes or updates the effective date used when building ADP extract data. It provides the anchor date that downstream extract logic references.
• GET_ADP_EXTRACT_DATE — Retrieves the currently stored ADP extract date, allowing callers to synchronize their processing windows with the value set by SET_ADP_EXTRACT_DATE.
• GET_EX_EMPLOYEE_DATE — Returns the termination or exit-related employee date associated with ADP processing, typically used to identify when an employee should no longer be included in active extracts.
• GET_END_DEDUCTION_DATE — Provides the end date for a deduction, allowing ADP integration logic to determine when a deduction should cease being transmitted.
• GET_MAX_PPM_PRIORITY — Returns the maximum priority value found among existing personal payment methods, which is useful when assigning a new payment method priority that must not collide with existing entries.

No parameter lists are documented in the ETRM metadata, and none are invented here.

Tables Accessed

The documented table reference for HR_ADP is PAY_PERSONAL_PAYMENT_METHODS_F, accessed through an APPS synonym. This table stores personal payment method records for employees and other payees, including priorities and effective dates. HR_ADP reads this table primarily to support GET_MAX_PPM_PRIORITY, which inspects existing priorities to return the highest value in use. Other procedures operate on package-level state rather than directly documented tables. HR_ADP also has a documented dependency on HR_PAY_INTERFACE_PKG, indicating that parts of its date and deduction logic interoperate with the payroll interface layer. Because HR_ADP is not referenced by any database object per the ETRM listing, its table access pattern is read-oriented and confined to payment method data plus whatever internal state the package maintains.

Usage Notes

HR_ADP is typically invoked from within HRMS payroll and ADP integration flows rather than directly by end users. The 21 packages that reference it include payroll interface and extract routines that call SET_ADP_EXTRACT_DATE and GET_ADP_EXTRACT_DATE to bracket an extraction run, consult GET_EX_EMPLOYEE_DATE to filter terminated employees, and use GET_END_DEDUCTION_DATE to close out deductions. GET_MAX_PPM_PRIORITY may be called from forms or concurrent programs that create or edit personal payment methods to ensure priority sequencing is respected. Because it is classified as OTHER and is not publicly documented as a formal API, customizations should avoid direct calls and instead use supported HRMS APIs where possible; if HR_ADP must be referenced, it should be treated as an internal implementation detail subject to change between 12.1.1 and 12.2.2.