Search Results company_codevalidtrigger




Overview
Explore in AI Chat

Overview

APPS.XTR_XTRLIEXP_XMLP_PKG is an Oracle E-Business Treasury (ETRM) package body that backs the XML Publisher concurrent program used to report limit exceptions in Oracle Treasury. The package encapsulates the report-level logic for the "Limit Exceptions" report (XTRLIEXP), providing formula functions that the XML Publisher template engine invokes at runtime, validation triggers for report parameters, and the standard before/after report hooks. The package belongs to the APPS schema, is classified as OTHER in the ETRM documentation, and is not referenced by any other package, confirming that it is invoked exclusively through the concurrent manager and the XML Publisher runtime.

The object is identified by the source header XTRLIEXPB.pls (version 120.1, dated 2007/12/28), which places it within the long-standing Treasury reporting layer that has remained stable across the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

  • CF_SET_PARAFORMULA — Derives a value for the CP_PARA parameter, populated from the database USER and truncated to ten characters, so the report output can be attributed to the concurrent request's submitting user.
  • CF_DESCRIPTIONFORMULA — The function matched by the search term "cf_descriptionformula". It builds the human-readable descriptive text for each limit exception by mapping the limit check type (GLOBAL, SOVRN, CCY, DLR_DEAL, INTRA_DY, CPARTY, SETTLE) and the exception type (EXCEEDED, NO_LIMIT, NO_AUTHO) into a composed sentence, for example "Global limit was exceeded." or "Currency limit did not exist for these values."
  • COMPANY_CODEVALIDTRIGGER — Validation trigger for the Company Code report parameter that upper-cases the entered value and returns TRUE.
  • LIMIT_CODEVALIDTRIGGER — Validation trigger for the Limit Code parameter; performs the same upper-case normalisation and returns TRUE.
  • BEFOREREPORT — Before-report hook that performs report initialisation, including a check against XTR_SYS_LANGUAGES_VL to confirm the required language/module setup ('XTRLIEX...') is present and to prepare the message resources.
  • AFTERREPORT — Standard after-report hook invoked on completion of the report.
  • AFTERPFORM — Post-parameter-form hook, executed after the report's parameter form has been processed.
  • CP_PARA_P — Accessor associated with the CP_PARA package variable populated by CF_SET_PARAFORMULA.

Tables Accessed

  • FND_CONCURRENT_REQUESTS — Read to obtain concurrent request context, such as the submitting user and request parameters, that drive report initialisation.
  • FND_NEW_MESSAGES — Accessed for message text, referenced by the L_MESSAGE variable declared in BEFOREREPORT to surface the appropriate runtime message.
  • DUAL — Used by CF_SET_PARAFORMULA to select USER into the CP_PARA package variable.
  • XTR_SYS_LANGUAGES_VL (via the CHK_LANG cursor) — Queried for MODULE_NAME 'XTRLIEX' to validate that the language setup required by the report exists before the report is executed.

Usage Notes

XTR_XTRLIEXP_XMLP_PKG is not called from Oracle Forms or by other PL/SQL packages; the documented reference count is zero. It is invoked exclusively by the XML Publisher (BI Publisher) engine when the Limit Exceptions concurrent program is run from Oracle Treasury. The CF_*FORMULA functions are referenced directly in the RTF/XSL-FO report template to produce computed columns, while the validation triggers and BEFOREREPORT/AFTERREPORT/AFTERPFORM hooks are called by the concurrent program framework during submission and execution.

Because the package is report-specific and self-contained, any customisation—such as adding a new limit check type or exception type to CF_DESCRIPTIONFORMULA—should be performed by copying and extending the package in a custom schema rather than modifying the seeded APPS version, since the object is supported and may be patched during upgrades from 12.1.1 to 12.2.2.