Search Results set_line_status

Overview

PAYPLNK is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports the Paylink batch processing facility within Oracle Payroll. Its primary business function is to process payroll batches — most notably batches representing third-party payments or paylink transfers — by validating batch content, inserting element entries into the base payroll tables, and returning an outcome status to the concurrent manager. The package is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the invoking user rather than the definer, which is significant because the batch processing logic is normally driven through the standard Oracle Applications security model and the SRS (Standard Report Submission) concurrent program framework.

The header comment embedded in the source identifies run_process as "the main procedure called from the SRS screen, from which the paylink process is triggered for a particular batch," and confirms that the success or failure status of the process is returned to the SRS screen. This establishes PAYPLNK as a concurrent-program-callable API rather than a purely internal utility.

Key Procedures and Functions

The ETRM documentation records seven procedures for this package. Their documented purposes are:

• RUN_PROCESS — The main entry point invoked from the SRS screen, triggering the paylink process for a specified batch. It returns the success status (or otherwise) back to the SRS screen via the standard concurrent program errbuf/retcode outputs.
• VALIDATE — Given a batch id, validates the batch and inserts its element entries into the necessary base tables. Depending on the mode of operation passed (VALIDATE or TRANSFER), the inserted element entries are either rolled back or retained.
• SET_STATUS — Given a batch id and mode of operation, sets the status of the batch and its control totals.
• SET_LINE_STATUS — Updates the status of individual batch lines; used to reflect the processing outcome at line level.
• SET_HEADER_STATUS — Updates the status of the batch header record, typically the summary-level outcome of the batch run.
• PURGE — Removes obsolete or processed batch data, consistent with the housekeeping role common to payroll batch utilities.
• VALIDATE_LINES — Performs validation at the individual batch line level, feeding the overall batch validation logic.

No parameter lists beyond those shown in the documentation excerpt are asserted here; the documented signatures are limited to run_process (errbuf, retcode, business group id, batch operation, batch id) and validate/set_status (business group id, batch operation, batch id).

Tables Accessed

The documented table references (via APPS synonyms) map directly to the package's batch-processing role. Batch definition and control reside in PAY_BATCH_HEADERS, PAY_BATCH_LINES, and PAY_BATCH_CONTROL_TOTALS. Element entry creation and validation draw on PAY_ELEMENT_ENTRIES_F, PAY_ELEMENT_LINKS_F, PAY_ELEMENT_TYPES_F, PAY_ELEMENT_CLASSIFICATIONS, and PAY_INPUT_VALUES_F. Absence-related processing touches PER_ABSENCE_ATTENDANCES and PER_ABSENCE_ATTENDANCE_TYPES, while benefits classification data comes from BEN_BENEFIT_CLASSIFICATIONS. Messaging and status reporting use PAY_MESSAGE_LINES, PAY_MESSAGE_LINES_S, PAY_UPGRADE_STATUS, and FND_SESSIONS for session context.

Usage Notes

PAYPLNK is typically invoked from the concurrent program behind the Paylink SRS screen, with RUN_PROCESS acting as the driver and the remaining procedures called internally to validate, insert, set statuses, or purge. The documented "referenced by 8 other packages" indicates it is also called programmatically from other payroll APIs. Custom code should call the documented entry points rather than manipulating the base tables directly, and must respect the VALIDATE versus TRANSFER mode semantics that determine whether inserted element entries are rolled back.