Search Results init_security

Overview

CE_CEXTRXCD_XMLP_PKG is the packaged body behind the Oracle Cash Management XML Publisher (BI Publisher) report commonly identified as the Cash Transaction / Bank Account Detail extract. In Oracle E-Business Suite 12.1.1 and 12.2.2, packages following the _XMLP_PKG naming convention are generated as the PL/SQL data definition component of a concurrent program that is registered with an XML Publisher template. The package is responsible for gathering the report parameters, executing the query logic, and returning the result set to the XML Publisher engine, which then merges the data with an RTF or XSL-FO layout.

The public interface of the package is intentionally narrow. It exposes the standard report entry points BEFOREREPORT and AFTERREPORT, which are called by the XML Publisher runtime to initialise and clean up the report session. Its primary business function is to validate and resolve a bank account identifier supplied at submission time and to expose the descriptive attributes of that account—name, number, bank name, branch name, and currency—as report-level columns. When no specific account is passed, the report substitutes literal "ALL" values so that the extract can span every permitted account.

Key Procedures and Functions

BEFOREREPORT is the controlling routine. It captures the concurrent request identifier from FND_GLOBAL.CONC_REQUEST_ID, invokes INIT_SECURITY to establish the session's security context, and then resolves the account header data. Two error handlers are embedded: one wraps the enquiry of the company name header and raises CE_LOOKUP_ERR via SET_NAME/GET; the second traps failures resolving bank account details and raises CE_INVALID_BANK_ACC. Both terminate with RAISE_APPLICATION_ERROR(-20101, NULL).

AFTERREPORT is a stub returning TRUE, providing the required hook with no post-processing logic. G_BANK_ACCOUNTGROUPFILTER drives the group filter flag C_THE_END, used to control conditional formatting or the display of a summary line. The remaining functions—C_DATEFORMATFORMULA, C_THE_END_P, C_BANK_ACCOUNT_NAME_P, C_BANK_ACCOUNT_NUM_P, C_BANK_NAME_P, C_BANK_BRANCH_NAME_P, C_BANK_CURRENCY_CODE_P, and C_COMPANY_NAME_HEADER_P—are accessor functions that return the corresponding column values to the report layout. The message-handling utilities SET_NAME, RETRIEVE, CLEAR, GET_STRING, PARSE_ENCODED, SET_ENCODED, RAISE_ERROR, DEBUG, and ENABLE_DEBUG form a supporting framework for lookup-based error messages and optional diagnostic output.

Tables Accessed

The package references the APPS synonym FND_NEW_MESSAGES to store and retrieve application message text, predominantly for the L_MESSAGE variable populated during error handling. The account resolution logic additionally reads the Cash Management views CE_BANK_ACCTS_GT_V and CE_BANK_BRANCHES_V, joined on BRANCH_PARTY_ID = BANK_BRANCH_ID, to derive the bank account, bank, and branch attributes. The fallback "all accounts" branch uses CE_LOOKUPS with LOOKUP_TYPE = 'LITERAL' and LOOKUP_CODE = 'ALL'.

Usage Notes

The package is invoked exclusively by the XML Publisher concurrent program runtime; it is not referenced by any other database package (ETRM reports zero inbound package references). It should therefore be treated as report-internal implementation rather than a reusable API. Because BEFOREREPORT calls INIT_SECURITY, the report inherits the submitting user's Cash Management security profile, meaning the visible bank accounts are constrained by that responsibility's security configuration. Reports are submitted with P_BANK_ACCOUNT_ID and P_DEBUG_MODE parameters; supplying Y for debug enables diagnostic paths. Customisations should avoid altering the public function signatures, since the XML Publisher layout file binds directly to the report columns exposed by the accessor functions.