Search Results c_bank_currency_code_p

Overview

APPS.CE_CEXTRXCD_XMLP_PKG is the generated PL/SQL package associated with the Oracle Cash Management (CE) concurrent program and XML Publisher (BI Publisher) report definition CEXTRXCD. The suffix _XMLP_PKG identifies it as a report-support package produced by Oracle Reports/XML Publisher migration, containing the report's global variables, data-fetch logic, formatting formulas, and before/after report triggers. Its principal business purpose is to supply bank account identification and descriptive header attributes used by the Cash Management transaction/reconciliation document output — specifically the bank account number, bank account name, bank name, bank branch name, bank currency code, and company name header printed on the report.

The user's search term c_bank_account_num_p corresponds directly to the package function C_BANK_ACCOUNT_NUM_P (line 20 of the specification), a standard XML Publisher "P" (public getter) function that returns the value of the package global C_BANK_ACCOUNT_NUM VARCHAR2(80). This is the accessor exposed to the report layout template at runtime.

Key Procedures and Functions

• BEFOREREPORT — Executes initialisation logic before the report's main data query runs, typically resolving the concurrent request parameters and populating descriptive globals.
• AFTERREPORT — Post-processing trigger executed after the report body has been generated.
• G_BANK_ACCOUNTGROUPFILTER — Group filter function used to control inclusion of bank account records in the report output.
• C_DATEFORMATFORMULA — Returns a date format mask used by the layout, allowing the date display format to be driven at runtime.
• C_THE_END_P — Getter for the C_THE_END flag ('N' by default), used as an end-of-report/loop control indicator.
• C_BANK_ACCOUNT_NAME_P, C_BANK_ACCOUNT_NUM_P, C_BANK_NAME_P, C_BANK_BRANCH_NAME_P, C_BANK_CURRENCY_CODE_P, C_COMPANY_NAME_HEADER_P — Getter functions that expose the corresponding package globals to the XML Publisher layout. C_BANK_ACCOUNT_NUM_P returns C_BANK_ACCOUNT_NUM, the bank account number displayed on the report.
• SET_NAME — Stores an application/name pair, supporting FND message and name resolution.
• GET, GET_STRING — Retrieve message/string values by application and name from the FND message dictionary.
• RETRIEVE, CLEAR — Populate and reset the internal message-handling state.
• PARSE_ENCODED, SET_ENCODED — Encode and decode message payloads for the report's messaging layer.
• RAISE_ERROR — Raises a formatted error to the concurrent manager.
• DEBUG, ENABLE_DEBUG — Diagnostic helpers gated by the P_DEBUG_MODE and P_SQL_TRACE globals.
• INIT_SECURITY — Initialises the security context (organisation/access) for the report session.

Tables Accessed

The ETRM metadata documents a single referenced table, FND_NEW_MESSAGES (accessed through an APPS synonym). This table belongs to the Oracle Application Object Library message dictionary and is read by the GET/GET_STRING/RETRIEVE family of procedures to resolve translatable message text and by SET_NAME when storing named message lookups. The report's substantive bank, bank account, and transaction data is retrieved through the underlying report query on Cash Management base tables, not through direct references exposed in this package specification.

Usage Notes

This package is never called directly by end users. It is invoked automatically by the Oracle Reports/XML Publisher runtime when the CEXTRXCD Cash Management report is executed from the Submit Requests form or from the concurrent programs interface. The *_P getter functions are bound into the RTF/XML layout template as placeholder values — for example, C_BANK_ACCOUNT_NUM_P supplies the bank account number field — and are evaluated once per report invocation after BEFOREREPORT completes. The P_BANK_ACCOUNT_ID, P_DEBUG_MODE, P_SQL_TRACE, and P_CONC_REQUEST_ID globals are populated from the concurrent program parameter list. The package is declared AUTHID CURRENT_USER and executes with APPS schema privileges through the standard EBS synonym layer. Because it is referenced by zero other packages, it is effectively self-contained and should be treated as generated report-support code rather than as a reusable API; customisations should be limited to the underlying report definition, since the package is regenerated from the report source (header CEXTRXCDS.pls 120.0).