Search Results z1valuation_reviews_before




Overview
Explore in AI Chat

Overview

APPS.XTR_XTRMILNS_XMLP_PKG is the PL/SQL package body that supports the Oracle E-Business Suite Treasury (ETRM) concurrent report known internally as XTRMILNS. Its name follows the standard Oracle Reports server-side packaging convention, where an ".xmlp" report definition is paired with a "_PKG" package that supplies report-level logic. In this case the package provides the PL/SQL building blocks invoked by the Oracle Reports runtime when the report executes in a concurrent manager environment.

Functionally, the package prepares the runtime context for the XTRMILNS report — a Treasury listing whose labels and column captions are language-driven. It populates display variables for fields such as account manager, party name, company, party code, valuer, valuation amount, valuation review thresholds, priority summary, and report footer text (issued by / end of report). These labels are not hard-coded; they are retrieved from a Treasury language repository, which lets the report render in the session language while presenting Treasury-specific terminology. This behaviour is central to why an end user searching on "xtr_factor" — a factor or lookup value surfaced through this family of Treasury reports — would land on this package. The package therefore acts as the report's presentation and session-support layer rather than as a business logic or data processing engine.

Key Procedures and Functions

  • CF_SET_PARAFORMULA — A report formula column function. It selects the current database user (truncated to ten characters) from DUAL into the package variable CP_PARA and returns that value. This supplies the concurrent request "parameters" display value used in the report header or layout.
  • BEFOREREPORT — The BeforeReport trigger handler. It establishes the report's runtime context: it retrieves the window session title through CEP_STANDARD.GET_WINDOW_SESSION_TITLE (with FND_MESSAGE-based error handling that raises application error -20101 on failure), optionally honours the P_DISPLAY_DEBUG parameter, and loops through XTR_SYS_LANGUAGES_VL for module 'XTRMILNS' to assign translated label variables (Z1ACCT_MGR, Z1NAME, Z1COMPANY, Z1ORDER_BY_PTY_MGR, Z1PARAMETERS, Z1PARTY_CODE, Z1PRIORITY_SUM, Z1VALUATION_AMOUNT, Z1VALUATION_REVIEWS_BEFORE, Z1VALUER, Z2COMPANY, Z2END_OF_REPORT, Z2ISSUED_BY, Z2PARTY_ACCT_MANAGER, and related items).
  • AFTERREPORT — The AfterReport trigger handler, invoked at report completion to perform end-of-run housekeeping.
  • AFTERPFORM — The AfterParameterForm trigger handler, executed after the report parameter form is submitted, used to finalise parameter-derived setup.
  • CP_PARA_P — The package-level variable associated with CP_PARA, holding the parameter display value returned by CF_SET_PARAFORMULA.

Tables Accessed

  • DUAL — Used by CF_SET_PARAFORMULA to obtain the current user value without touching application data.
  • XTR_SYS_LANGUAGES_VL — The Treasury system language view (not listed among the APPS-synonym tables but referenced directly in the source). BEFOREREPORT queries it for MODULE_NAME = 'XTRMILNS' to obtain language-specific label text for the report's Z1/Z2 caption variables.
  • FND_NEW_MESSAGES — Referenced through the declaration of L_MESSAGE, which is typed as FND_NEW_MESSAGES.MESSAGE_TEXT%TYPE; it underpins the FND_MESSAGE.SET_NAME/GET error path used when window-session title retrieval fails.
  • FND_CONCURRENT_REQUESTS — The concurrent request context table for the standard Oracle EBS report environment, associated with the concurrent manager invocation of XTRMILNS.

Usage Notes

This package is invoked automatically by the Oracle Reports runtime when the XTRMILNS Treasury report is submitted as a concurrent program; the BEFOREREPORT, AFTERPFORM, and AFTERREPORT functions map to the report's triggers and are not called directly by application code. CF_SET_PARAFORMULA is referenced as a formula column within the report layout. Because the package is classified as OTHER with no other packages referencing it, it should be treated as a report-private implementation detail: modifications should be made with care, retested against the concurrent program, and recompiled as the APPS schema. The P_DISPLAY_DEBUG parameter offers a diagnostic hook, but leaves no active behaviour in the shipped code. Note the embedded "noship" header comment, which identifies the source as a non-shipped internal file — reinforcing that this object belongs to the report's private support layer.