Search Results p_request_id_main

Overview

APPS.AR_ARZCARPO_XMLP_PKG is a report-support PL/SQL package that underpins the Oracle Receivables AutoInvoice batch report concurrent program commonly identified by the short name ARZCARPO (AutoReceivables Processing). The package acts as the server-side companion for an Oracle Reports XML Publisher (XMLP) executable, supplying the bind variables, format triggers, and PL/SQL formulas that drive report output. The name convention _XMLP_PKG confirms the package was generated to satisfy the requirements of an XML Publisher report definition, where report formulas, group filters, and BeforeReport/AfterReport triggers are implemented as functions inside a database package rather than embedded directly in the report file.

The package version header indicates a build from 2007 and it carries the noship designation, meaning it is shipped independently of the core Receivables code family. It is owned by APPS and classified under API classification OTHER, indicating it is not a public programmable interface but an internal reporting adjunct.

Key Procedures and Functions

The package exposes ten documented functions and procedures. The user-visible parameter P_REQUEST_ID_MAIN, which prompted the search, is one of several NUMBER globals declared at package level; it holds the concurrent request identifier of the parent or main report submission and is the value the report uses to correlate its own processed data with the originating concurrent request.

• REPORT_NAMEFORMULA — Returns the report name used in the report header, controlled by the RP_REPORT_NAME package variable.
• SUB_TITLEFORMULA — Produces the report sub-title text, populating RP_SUB_TITLE.
• BEFOREREPORT — The BeforeReport trigger; performs initialization and derivation of package-level variables before data retrieval begins.
• AFTERREPORT — The AfterReport trigger; performs cleanup and sets the report completion flags (such as RP_DATA_FOUND) after the report completes.
• C_EXCEPTION_MEANINGFORMULA — Accepts exception and error context values (exception code, error code, error flag, error text, additional message) and returns a formatted, human-readable exception description for display on the report.
• CF_1FORMULA — A conditional format or display formula that interprets the CC_DISPLAY_FLAG and returns a single character used for display formatting.
• DESNAMEVALIDTRIGGER — A validation trigger that validates the report destination (DESNAME) before printing or transmission proceeds.
• RP_REPORT_NAME_P, RP_DATA_FOUND_P, RP_SUB_TITLE_P — Accessor functions that return the current values of the report name, data-found indicator, and sub-title variables, allowing the report layout to query them at runtime.

Tables Accessed

The package references two tables through APPS synonyms:

• AR_BATCHES — Stores AutoInvoice batch definitions and batch-level processing status. The report reads this table to select batches for the create, approve, or format processing modes implied by parameters such as P_BATCH_ID, P_PROCESS_TYPE, P_CREATE_FLAG, and P_APPROVE_FLAG, and to display batch name and status on the output.
• FND_CONCURRENT_REQUESTS — The concurrent manager request registry. The package correlates P_CONC_REQUEST_ID and the internal request identifiers with this table to determine request status, phase, and completion details that appear on the report.

Usage Notes

AR_ARZCARPO_XMLP_PKG is invoked implicitly: Oracle Reports and XML Publisher executables call the package functions automatically when the report is run as a concurrent program from the Receivables responsibility or submitted through the Standard Request Submission form. It is not called from Application Forms directly and, per the ETRM metadata, is referenced by zero other packages, confirming it sits at the terminus of the AR AutoInvoice batch reporting stack rather than in a shared utility role. Customizations should not modify the package; instead, report-level parameters such as P_REQUEST_ID_MAIN, P_BATCH_ID, and the processing flags should be supplied through the concurrent program definition. Because the package is marked noship, it is regenerated during patching and direct edits will be overwritten.