Search Results cp_void_type_exist_flag_p

Overview

APPS.JL_JLZZRCVI_XMLP_PKG is a PL/SQL package that belongs to the Oracle E-Business Suite Japan Localization (JL) schema and supports the concurrent-program/report execution model built around the Oracle XML Publisher (XMLP) framework. The naming convention JL_JLZZRCVI_XMLP_PKG identifies it as the generated package associated with a JL-localized concurrent report, where the "XMLP" suffix denotes the report's XML Publisher output (typically an XML/RTF template producing a PDF or Excel layout). The internal module prefix JLZZRCVI points to a receivables-related report — the dependencies on RA_CUSTOMER_TRX, RA_CUST_TRX_TYPES, RA_BATCH_SOURCES and RA_CUST_TRX_LINE_GL_DIST confirm that the package operates in the Oracle Receivables (AR) domain, dealing with customer transactions, transaction types, batch sources, and accounting distributions. In the context of the 12.1.1 and 12.2.2 releases, such packages are catalogued in ETRM with an API classification of OTHER and status VALID, indicating that the object compiles cleanly and forms part of the shipped APPS schema.

The package embodies both the standard XML Publisher report lifecycle (BEFOREREPORT, AFTERREPORT, AFTERPFORM and the associated *FORMULA functions) and the Japanese-localization-specific validations and data manipulation typical of JL receivables reports — transaction numbering, voiding, recurring transaction insertion and setup validation.

Key Procedures and Functions

The ETRM metadata documents 31 procedures and functions. The most significant groups are:

• Report lifecycle routines: BEFOREREPORT, AFTERREPORT and AFTERPFORM are the standard XML Publisher entry points invoked before the report runs, after it completes, and after the parameter form is submitted, respectively. REPORT_NAMEFORMULA and SUB_TITLEFORMULA supply the report title and subtitle text to the XML template at runtime.
• Validations: CHECK_SETUP, CHECK_VOID_TRX_TYPE, CHECK_AUTO_TRX_NUM, CHECK_TRANSACTIONS, CHECK_ORIG_INV_NOT_FOUND verify the configuration (automatic transaction numbering, void transaction type existence/uniqueness) and the integrity of the transactions to be processed before any write activity.
• Data manipulation: UPDATE_ORIGINAL_TRX, INSERT_RECUR_INTERIM, GET_HEADER_INFO perform the record-level work — updating the source transaction, inserting recurring/interim rows, and retrieving header data for the report.
• Report parameters: RP_COMPANY_NAME_P, RP_REPORT_NAME_P, RP_SUB_TITLE_P expose report parameters, while the CP_*_FLAG_P functions (CP_AUTO_TRX_NUM_FLAG_P, CP_DOC_SEQ_NUM_FLAG_P, CP_VOID_TYPE_EXIST_FLAG_P, CP_VOID_TYPE_UNIQ_FLAG_P) return control flags describing setup state.

Tables Accessed

• RA_CUSTOMER_TRX / RA_CUSTOMER_TRX_ALL — the primary customer transaction header tables; read for reporting and updated by UPDATE_ORIGINAL_TRX.
• RA_CUST_TRX_LINE_GL_DIST — distribution lines used to report accounting impact.
• RA_CUST_TRX_TYPES — transaction type lookup, including void/hierarchy validation.
• RA_BATCH_SOURCES — batch source definitions used in setup checks.
• FND_CONCURRENT_REQUESTS — accessed to identify the concurrent request context (e.g., parameters or program name).

Usage Notes

This package is not intended for direct invocation by end users or custom code. It is invoked internally by the Oracle Reports / XML Publisher concurrent program with which it is registered; the APPS schema references it via the concurrent manager when the associated JL receivables report is submitted. The report lifecycle procedures fire automatically. Because the ETRM record shows the package is referenced by no other packages and references only SYS.STANDARD plus itself, it is a self-contained report backing package. Customizations should be limited to the underlying report template or to the concurrent program definition rather than modifying the package body, which is shipped and supported as part of the APPS schema in both 12.1.1 and 12.2.2.