Results for “standard_deinit”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PAY_CORE_XDO_UTILS is a PL/SQL utility package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its primary business function is to support the generation and lifecycle management of Oracle Payroll reports rendered through the Oracle XML Publisher (XDO) engine. In E-Business Suite, XML Publisher, also known as BI Publisher, separates report data extraction from template-based rendering. The payroll product line relies on this architecture for statutory reports, payslips, costing reports, and regulatory filings delivered from seeded and customer-defined report definitions.

This package provides the plumbing that prepares a concurrent request context, resolves report definitions and their associated XML templates, then performs orderly cleanup once the report interaction has completed. It is classified as an OTHER API in the ETRM repository and is considered an internal utility rather than a formally published business API. It maintains no direct user interface and is not itself exposed as a concurrent program; it is invoked by other payroll packages that orchestrate report output.

Key Procedures and Functions

Two documented routines are recorded for this package within ETRM 12.2.2 metadata:

• ARCHIVE_DEINIT — Performs de-initialization of the archiving context associated with an XML Publisher-driven payroll report run. It is the resource-release counterpart to the setup work performed before a report is rendered, clearing state such as locks and transient references held during the report lifecycle.
• STANDARD_DEINIT — Executes the standard de-initialization path for report processing, releasing locks and package-level state once the report generation cycle is finished. It ensures that concurrent request processing leaves no residual context behind.

Although the naming convention implies matching initialization routines, only the DEINIT procedures are recorded in the documented metadata. Parameter signatures are not exposed in ETRM and are consequently not reproduced here.

Tables Accessed

The package reads and writes against the following application tables, referenced through APPS synonyms:

• PAY_REPORT_DEFINITIONS, PAY_REPORT_GROUPS, PAY_REPORT_CATEGORIES, PAY_REPORT_CATEGORY_COMPONENTS, PAY_REPORT_VARIABLES — Define the payroll report inventory used to resolve which report is being generated and which template and data source apply.
• PAY_FILE_DETAILS, PAY_ASSIGNMENT_ACTIONS, PAY_PAYROLL_ACTIONS — Support payroll process and archive run context so the correct payroll action or archive run is associated with the report output.
• XDO_TEMPLATES_B and XDO_TEMPLATES_TL — XML Publisher template base and translation tables, used to locate the appropriate report template and its language-specific overrides.
• FND_CONCURRENT_REQUESTS and FND_CONCURRENT_PROGRAMS — Provide the concurrent request context, including the request identifier and program metadata needed for de-initialization.
• DBMS_LOCK and PLITBLM — Used at runtime for lock acquisition and release and the PL/SQL implementation of DBMS_LOB routines, supporting BLOB handling for XML output.

Usage Notes

PAY_CORE_XDO_UTILS is invoked indirectly by payroll report packages executing XML Publisher output. ETRM records that it is referenced by PAY_JP_DEF_REPORT_PKG, PAY_JP_ITWB_REPORT_PKG, and PAY_JP_SPR_EFILE_PKG, indicating that the Japanese statutory reporting suite in Oracle Payroll depends heavily on this utility for template resolution and orderly report finalization. The DEINIT procedures should be called by calling code at the conclusion of report processing, ideally within an exception handler so that locks and package state are released even when an error occurs. Because the package is not a public API, customizations should avoid calling it directly and instead invoke the payroll report packages that already manage its lifecycle.