Search Results prior_mr




Overview
Explore in AI Chat

Overview

APPS.PAY_PAYJPSDD_XMLP_PKG is an Oracle E-Business Suite PL/SQL package body that supports the Oracle Payroll Japanese legislative reporting extract commonly identified as the "Notification of Disqualification Checklist" (report code PAYJPSDD). It is an XML Publisher (BI Publisher) report package, as indicated by the _XMLP_PKG suffix, and is generated using the standard Oracle Reports-to-XML Publisher conversion pattern in which report-level logic and formula columns are migrated into a database package invoked at runtime by the concurrent program.

The package is used to produce a statutory output file for Japanese payroll operations relating to disqualification records maintained against employee work-related benefit information. During report execution, the package initializes global record counters, formats the preparation date, resolves business group-specific legislation and element information, and derives the output file name expected by the downstream filing process. The ETRM classification records this API as OTHER, with no publicly documented callable procedures and no packages referencing it, confirming that it is an internal, report-private package rather than a shared application programming interface.

Key Procedures and Functions

The ETRM documentation records no public procedures or functions for this package. The embedded source excerpt exposes a single report-lifecycle entry point, BeforeReport, which returns a boolean and is invoked by the XML Publisher engine before the data model is executed.

  • BeforeReport — Performs pre-processing for the report: normalizes the user-entered preparation date into a YYYY/MM/DD character representation, resets internal global counters (G_REC_COUNT, G_FD_COUNT, G_FD_SERIAL_NUMBER, G_COUNT_OF_RECORD, G_HEADER_OUT), sets the report title constant, captures the concurrent request identifier through FND_GLOBAL.CONC_REQUEST_ID, and derives the media/magnetic output file name (g_magfile_name).
  • Date and legislative resolution logic — Within BeforeReport, the package calls pay_jp_report_pkg.to_era to convert the preparation date into Japanese era components, then reduces the year to a two-digit value and pads the year, month, and day segments. It further calls pay_jp_balance_pkg.get_legislation_code and pay_jp_balance_pkg.get_element_type_id to resolve element type identifiers for COM_SI_INFO, COM_WP_QUALIFY_INFO, and COM_WP_SMR_INFO.
  • Input value identifier initialization — Global identifiers such as G_BASIC_PENSION_NUMBER_IV_ID, G_DISQUALIFIED_STATUS_IV_ID, and G_WP_COMP_DATE_APPLIED_IV_ID are populated via pay_jp_balance_pkg.get_input_value_id, allowing later report formulas to read specific element input values.

Tables Accessed

The ETRM metadata does not list direct table references for this package. The source excerpt shows indirect access to payroll business group data through the PER_BUSINESS_GROUPS anchored type declaration (LEGISLATION_CODE%TYPE). Element and input value metadata is obtained indirectly through calls to PAY_JP_BALANCE_PKG, which queries payroll element type and input value definitions on behalf of the report. The absence of documented APPS synonym references indicates that this package relies on helper packages rather than issuing its own SQL against base tables.

Usage Notes

This package is not intended for direct invocation by developers. It is executed automatically by the XML Publisher concurrent program infrastructure when the corresponding Japanese payroll report — Notification of Disqualification Checklist — is submitted through the Standard Request Submission form or scheduled by a payroll administrator. The report is typically run at period end as part of statutory Japanese payroll filing obligations.

Developers investigating data issues for the report, such as those searching for the prior_mr parameter or related month-rollover logic, should treat this package as read-only and extend it only through the supported XML Publisher report definition and its associated data template. Because the package derives the output file name from the concurrent request identifier and the business group legislation, customization should be limited to the report parameters and template rather than to the package body itself.