Search Results record_4712

Overview

PAY_NL_IZA_REPORT is an Oracle EBS Payroll (PAY) package owned by the APPS schema and declared with AUTHID CURRENT_USER. It serves the Dutch localization (NL) by generating the Annual Tax Statement Report, commonly referred to as the IZA report (Inkomstenverhouding / Jaaropgave). This report provides employees and tax authorities with a consolidated summary of taxable wages, allowances, and deductions accumulated over a reporting year. The package header carries the identifier paynliza.pkh 120.0, dated 2005/05/29, which places it among the long-standing Dutch statutory reporting objects that have been carried forward across EBS 12.1.1 and 12.2.2 without structural change to the public interface. The package is classified as OTHER in the ETRM metadata, meaning it is not designated as a public API, and it is not referenced by any other documented package, so its callers sit outside the PL/SQL dependency graph — typically concurrent program definitions, XML Publisher templates, or localization-specific report drivers. The body transforms payroll results into an XML representation suitable for XFDF/BI Publisher output.

Key Procedures and Functions

• POPULATE_IZA_REPORT_DATA — The principal entry point. It gathers the data required for the Annual Tax Statement Report and then writes the resulting XML content as a CLOB. Its parameters address the reporting context: a business group identifier and name, an effective date, an organization structure identifier and name, a process month, an employer identifier and name, and an output BLOB used for the generated XFDF document. The BLOB is declared OUT NOCOPY for efficiency, allowing the procedure to populate the large payload without an intermediate copy. This procedure encapsulates the full extraction, formatting, and rendering workflow for the statement.
• RECORD_4712 — A supporting procedure that accepts a file identifier. The naming references the Dutch tax form number 4712, the annual statement form on which employer-reported wage data is submitted. Its role is to register or persist status information associated with a generated output file, working in conjunction with the upload status table described below. No additional parameters are documented, and the procedure is not exposed as an API for external consumption.

Tables Accessed

• FND_LOBS — Stores large binary objects produced during report generation, including the XML/XFDF content written as a CLOB or BLOB. The file identifier passed to RECORD_4712 corresponds to a record in this repository.
• PAY_NL_IZA_UPLD_STATUS — A localization-specific status table that tracks the state of generated or uploaded IZA files, allowing the report to be marked as produced, transmitted, or acknowledged.
• PER_GB_XDO_TEMPLATES — Holds the XML Publisher (BI Publisher) template definitions used to render the extracted payroll data into the final report layout.
• PLITBLM — The PL/SQL index-by table of BLOB/CLOB structures used as an internal staging mechanism for assembling large character or binary content within PL/SQL before it is written out.

Usage Notes

PAY_NL_IZA_REPORT is normally invoked through a Dutch payroll concurrent program or a localization-specific report submission, not through direct calls from customer code. The concurrent program passes the business group, effective date, organization structure, process month, and employer context, and receives the generated XFDF in the BLOB output parameter; the same request typically triggers RECORD_4712 so that the resulting file is logged in PAY_NL_IZA_UPLD_STATUS. Because the package is AUTHID CURRENT_USER and is not documented as a public API, customizations should avoid calling its procedures directly and should instead submit the delivered concurrent program or wrap the logic. When extending the report, developers may add or replace templates in PER_GB_XDO_TEMPLATES without altering the package, and should verify that FND_LOBS cleanup routines account for the generated output. Any changes require regression testing against Dutch statutory formatting, since the IZA/annual statement layout is regulated and version-sensitive.