Search Results z1as_principal

Overview

XTR_XTRMTCPY_XMLP_PKG is an Oracle E-Business Suite PL/SQL package body owned by APPS and classified under the ETRM (Enterprise Treasury and Risk Management) product family. Its purpose is to support the XML Publisher (BI Publisher) report known internally as XTRMTCPY, which produces a trade counterparty listing. Rather than implementing business logic in the report template alone, the report definition delegates a number of derived values to PL/SQL functions and package-level global variables declared in this package. The functions resolve party and company codes to their display names, capture the current user as a report parameter, and initialize session and language information at report execution time. The package header references the original source revision "$Header: XTRMTCPYB.pls 120.1 2007/12/28 12:57:16 npannamp noship $", confirming it is a shipped, non-customized EBS file.

Key Procedures and Functions

• CPARTY_NAME1FORMULA — Accepts a counterparty party code and returns the corresponding short name from the parties view using dynamic SQL. This is the core counterparty name resolution routine used by the report.
• CPARTY_NAMEFORMULA — A placeholder function that simply returns NULL; it exists to satisfy the report's formula column definition where no value is required.
• COMPANY_NAME1FORMULA — Analogous to the counterparty routine, it accepts a company party code and returns the corresponding short name. This is the function most closely related to the "company_name_p" parameter used in the report definition.
• COMPANY_NAMEFORMULA — Another NULL-returning placeholder that backs an unused formula column.
• CF_SET_PARAFORMULA — Returns the first ten characters of the database USER value from DUAL, populating the CP_PARA global used elsewhere in the report.
• BEFOREREPORT — The report's before-report trigger. It retrieves the window session title, handles lookup errors by raising an application error, optionally evaluates the P_DISPLAY_DEBUG flag, and iterates the XTR_SYS_LANGUAGES_VL view to populate language-description globals such as Z1AS_PRINCIPAL, Z1CLIENT, Z1PRODUCT_TYPE, and Z1PORTFOLIO.
• AFTERREPORT — Post-report cleanup trigger.
• AFTERPFORM — Post-form trigger executed after the report's parameter form completes.
• COMPANY_NAME_P, CPARTY_NAME_P, CP_PARA_P — Package-level global variables that hold the resolved company name, counterparty name, and the current-user parameter respectively for use across formula columns.

Tables Accessed

• XTR_PARTIES_V (referenced in the source, exposed through an APPS synonym) — the parties view queried by both name-resolution functions to translate party codes into short names.
• FND_NEW_MESSAGES — used to declare a message text variable for error handling in BEFOREREPORT.
• DUAL — used by CF_SET_PARAFORMULA to select the current database user.
• FND_CONCURRENT_REQUESTS — recorded in the metadata as a referenced table, consistent with the package being executed from a concurrent program context.
• XTR_SYS_LANGUAGES_VL — the treasury language lookup view read in BEFOREREPORT to populate translated column headers.

Usage Notes

This package is not an application programming interface; the metadata classifies it as OTHER and records zero dependent packages. It is invoked indirectly whenever the XTRMTCPY XML Publisher report is run, typically from the Treasury responsibility or as a concurrent program. The report's data model references the formula functions and the package globals, so all name resolution and language setup occurs automatically at runtime without user interaction. Because the functions rely on dynamic SQL against XTR_PARTIES_V, any change to that view or to party code conventions will directly affect report output. The NULL-returning functions and the P_DISPLAY_DEBUG flag indicate the package is a generated report-support artifact, and it should not be called directly from custom code; developers extending the report should instead create a copy of the report definition and its supporting package. The package is unaffected by the 12.2.2 online patching model beyond standard editioning considerations, as it contains no DDL and performs no direct table writes.