Search Results run_xml_proc




Overview
Explore in AI Chat

Overview

APPS.PAY_MAG_TAPE is a PL/SQL package within the Oracle E-Business Suite Payroll module that supports the generation of magnetic media (tape) files for payroll payments and related regulatory submissions. It forms part of the infrastructure behind Oracle Payroll's magnetic tape and electronic funds transfer (EFT) processing, allowing payroll administrators to produce structured output files for transmission to banks, tax authorities, and other third parties. The package specification reveals a design centred on dynamically building parameter, context, and XML value collections, executing stored procedures by name, and handling large binary payloads. The declaration of g_blob_value blob and g_blob_file_id number is particularly significant: it indicates the package is designed to hold and manipulate binary large objects, typically the generated magnetic tape output or XML submission files stored against PAY_FILE_DETAILS records. The package is heavily integrated with the payroll action framework, as evidenced by its dependency on PAY_TEMP_OBJECT_ACTIONS and the use of pay_magtape_generic.get_parameter_value to resolve transfer payroll action and assignment identifiers.

Key Procedures and Functions

  • RUN_PROC — The primary execution entry point. It accepts a command parameter and drives the execution of the appropriate magnetic tape or EFT processing logic, fitting into the generic magnetic tape procedure framework defined in PAY_REPORT_MAGNETIC_PROCEDURES.
  • RUN_XML_PROC — Executes XML-based processing, supporting source identifier, source type, file name, and sequence as inputs. This supports newer electronic submission formats that supersede fixed-format magnetic media.
  • CALL_LEG_XML_PROC — Invokes the legacy XML procedure path, providing backward compatibility for XML payload generation or submission.

In addition to these three documented procedures, the specification declares internal collection types (host_array) and arrays for parameter names/values, context names/values, and XML names/values, which are populated at runtime to drive dynamic execution.

Tables Accessed

  • PAY_PAYROLL_ACTIONS — Read to resolve business group identifiers and payroll action context for header and footer generation.
  • PAY_TEMP_OBJECT_ACTIONS — Read to retrieve assignment-level action details and transfer action identifiers used to select the records included in the generated file.
  • PAY_FILE_DETAILS — Referenced for file metadata, including the BLOB content and file identifiers associated with generated outputs.
  • PAY_REPORT_GROUPS — Provides report grouping information that governs which magnetic media reports are produced.
  • PAY_REPORT_MAGNETIC_PROCEDURES — Supplies the registered procedure names that the package dynamically calls for each report.
  • DBMS_SQL — Used for dynamic SQL execution where procedure names and parameters are resolved at runtime.

Usage Notes

PAY_MAG_TAPE is typically invoked through Oracle Payroll's magnetic tape concurrent programs rather than being called directly by end users. The referencing of 23 other packages indicates deep integration with the payroll run, EFT, and statutory reporting infrastructure. In Oracle EBS 12.1.1 and 12.2.2, the package supports both legacy fixed-format tape generation and XML-based electronic submissions. Custom code should avoid direct invocation of internal procedures; instead, the supported concurrent program entry points should be used so that parameter arrays and BLOB handling are initialised correctly. The presence of g_blob_value as a package-level global means the BLOB is populated during a run and written to PAY_FILE_DETAILS, so any custom extension must respect the file lifetime and avoid concurrent execution against the same session state. Where the standard seeded magnetic formats are insufficient, Oracle recommends configuring additional formats through the magnetic tape setup rather than modifying this package.