Search Results gen_xml_footer

Overview

PAY_MX_ANNUAL_WRI is an Oracle Applications (APPS) PL/SQL package that supports the Mexico statutory Annual Work Risk Incidents report. The package is defined with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking user rather than the definer, and it is classified under the ETRM schema as an "OTHER" API rather than a public or private business API. Its header carries the source annotation $Header: paymxannualwri.pkh 120.0.12000000.1 2007/02/22 16:24:53 vmehta noship $, and the change list records a single creation entry by sdahiya on 18-Oct-2006 at version 115.0. The package is therefore a legislative-reporting utility rather than a general-purpose payroll engine component.

The package is not referenced by any other packaged object in the ETRM inventory (referenced by 0 other packages), which indicates that it is invoked directly as an entry point — typically from a concurrent program or report driver — rather than as a shared service called by sibling packages. Its internal design follows a classic Oracle Reports/payroll action pattern: resolve a range of processable persons, create assignment actions for the payroll action, then emit an XML document whose header, body, and footer are produced by dedicated procedures.

Key Procedures and Functions

• RANGE_CURSOR — Prepares the range of persons to be processed for the report. It accepts a payroll action identifier and returns an outbound SQL string, which the calling environment uses to drive the population of the report data set.
• ACTION_CREATION — Creates assignment actions for the payroll action supplied by the caller, establishing the action rows against which results are later recorded and reported.
• INIT — Initializes package-level state and any report context required before processing begins.
• GEN_XML_HEADER — Generates the opening section of the XML output for the annual work risk incidents report.
• GENERATE_XML — Produces the main body of the XML document containing the report's data content.
• GEN_XML_FOOTER — Generates the closing section of the XML document. This is the procedure of interest to users searching on the term "gen_xml_footer", and it is the terminal step in the XML assembly sequence.

Tables Accessed

The package operates against payroll action and assignment action tables through APPS synonyms. PAY_PAYROLL_ACTIONS and PAY_ACTION_INFORMATION supply the payroll action context, including action parameters and status information, while PAY_PAYROLL_ACTIONS and PAY_ACTION_INTERLOCKS provide the interlock records that coordinate processing order. PAY_ASSIGNMENT_ACTIONS and its shadow table PAY_ASSIGNMENT_ACTIONS_S are used to create and read the assignment-level actions generated by ACTION_CREATION. PAY_POPULATION_RANGES supports the person range assembly performed in RANGE_CURSOR. DUAL is used for singleton evaluations, and DBMS_LOB and PLITBLM are employed for large-object manipulation and PL/SQL index-by table handling, which is consistent with constructing a potentially large XML document in memory.

Usage Notes

PAY_MX_ANNUAL_WRI is invoked as part of the Mexico Annual Work Risk Incidents reporting flow, usually by submitting the associated concurrent program from the Standard Request Submission (SRS) window on EBS 12.1.1 or 12.2.2. The driver submits a payroll action, calls RANGE_CURSOR to establish the population, executes ACTION_CREATION to materialize assignment actions, and then calls INIT, GEN_XML_HEADER, GENERATE_XML, and GEN_XML_FOOTER in sequence to produce the XML output. Because the package is documented with no inbound references from other packages, customizations should call it directly rather than expecting it to be triggered transitively. The header note "noship" and the version stamp 120.0.12000000.1 indicate the file has not been modified since the original 11i-era delivery, so behavior should be treated as stable across 12.1.1 and 12.2.2. Any modification or recompilation should preserve the AUTHID CURRENT_USER semantics, since changing them can alter how the APPS synonym resolution and privilege checks behave at runtime.