Search Results set_report_constants

Overview

XLA_XLAALEXP_XMLP_PKG is the package body that backs the Oracle E-Business Suite concurrent program XLAALEXP (Subledger Accounting Application Accounting Definition Export). Its purpose is to export Application Accounting Definitions (AADs) from the Subledger Accounting (SLA) repository into a portable XML representation, optionally versioned and written to a destination path, and to drive the report lifecycle through the standard Oracle Reports XML Publisher integration points BEFOREREPORT and AFTERREPORT. The package is owned by APPS and is classified as OTHER in the ETRM metadata; the header comment, dated 2007/12/27, identifies it as a non-shipped ("noship") revision maintained by the SLA development team.

The central business outcome is the creation of a transferable AAD definition file, which is used by implementation teams and by Oracle support to migrate accounting configurations between environments, to archive definitions for audit, and to reproduce configurations in a target instance.

Key Procedures and Functions

• BEFOREREPORT — Fires before the report is rendered. It captures the concurrent request ID, activates the SRS_DBP utility context for XLAALEXP, refreshes the SLA environment cache, clears prior export errors for the EXPORT request code, and invokes XLA_AAD_EXPORT_PVT.EXPORT to perform the actual export. The export status is captured in CP_RET_CODE; if the status is lower than 'SUCCESS', error rows are inserted for later reporting. Report constants are then initialized.
• AFTERREPORT — Fires after report output. It maps the captured CP_RET_CODE to the concurrent program completion status, setting 'WARNING' or 'ERROR' via FND_CONCURRENT.SET_COMPLETION_STATUS, and deactivates the XLAALEXP utility context. Both the normal and exception paths perform deactivation, ensuring the utility context is not left active.
• SET_REPORT_CONSTANTS — Populates the report-level constants used by the XML template, reading from FND_APPLICATION_VL and the AMB (Application Message Body / context) meaning tables.
• CP_RET_CODE_P — The getter/setter placeholder for the CP_RET_CODE package variable, which holds the export status returned by XLA_AAD_EXPORT_PVT.EXPORT and is interrogated by AFTERREPORT to determine the concurrent request completion status. This is the symbol matched by the searched term "cp_ret_code_p".
• CP_REQ_ID_P — Exposes the concurrent request ID captured from FND_GLOBAL.CONC_REQUEST_ID.
• CP_APPLICATION_NAME_P — Exposes the application name resolved by SET_REPORT_CONSTANTS.
• CP_AMB_CONTEXT_P — Exposes the context meaning associated with the export selection.
• CP_STATUS_P — Exposes the export status text reported on the XML output.

In Oracle Reports XML Publisher packages of this generation, these CP_*_P members are generated accessors for the package-level variables that the report query and template bind to. They carry no independent business logic; their role is to make the export status and identifying context available to the report layout and to the AFTERREPORT completion-status logic.

Tables Accessed

The documented excerpt shows FND_APPLICATION_VL (for application name lookup) and the AMB context meaning source inside SET_REPORT_CONSTANTS. The package delegates most data access to XLA_AAD_EXPORT_PVT and XLA_AAD_LOADER_UTIL_PVT, which read and write the SLA definition and error tables (including the XLA_AAD_LOADER_UTIL table populated by INSERT_ERRORS and cleared by RESET_ERRORS). Additional SLA repository tables are traversed indirectly by the export API. The package is referenced by no other documented packages.

Usage Notes

The package is invoked exclusively through the XLAALEXP concurrent program; it is not intended for direct call from forms or custom code. Typical invocation is from the Subledger Accounting responsibility, where a user selects an Application and Accounting Method, specifies a destination pathname, versioning mode, user version, and version comment, and submits the request. Programmatic callers should invoke the concurrent program rather than the package procedures, because BEFOREREPORT and AFTERREPORT rely on the FND_GLOBAL concurrent context and on FND_CONCURRENT.SET_COMPLETION_STATUS. Note that BEFOREREPORT raises APPLICATION_ERROR -20101 on any unhandled exception, and AFTERREPORT performs the corresponding deactivation and error raise, so failures surface as a request error rather than a partial success. Because CP_RET_CODE is compared lexically against 'SUCCESS', only the exact status values returned by XLA_AAD_EXPORT_PVT.EXPORT ('SUCCESS', 'WARNING', 'ERROR') are meaningful.