Results for “cf_cp_currency_codeformula”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.AP_APXCCOUT_XMLP_PKG is the PL/SQL package body that implements the Oracle Payables corporate credit card expenditure output report in Oracle E-Business Suite 12.1.1 and 12.2.2. The package encapsulates the report-level logic required by the XML Publisher (BI Publisher) concurrent program definition APXCCOUT. It supports four operational report modes — CC_DETAIL_REPORT, CC_SUMMARY_REPORT, CC_AGING_REPORT, and CC_INACT_EMPL_REPORT — selected by the P_OPERATION_TYPE parameter. The package's primary responsibilities are the initialization of report parameters, the derivation of descriptive aging bucket labels, currency and company context, the retrieval of NLS strings, and notification of card administrators regarding cardholders with unsubmitted, manager-unapproved, or disputed transactions. The object is classified as OTHER in the ETRM metadata and is not referenced by any other package, indicating it functions as a top-level caller rather than a shared library.

Key Procedures and Functions

The documented package exposes 95 procedures and functions. The initialization routine BEFOREREPORT performs parameter validation and setup, including the aging bucket logic most relevant to the "aging_amount" search. It enforces that P_BUCKET1 does not exceed P_BUCKET2 or P_BUCKET3, and that P_BUCKET2 does not exceed P_BUCKET3, raising INIT_FAILURE on violation. It then resolves bucket display names through FND_MESSAGE using the SQLAP messages OIE_CC_BUCKET1_NAME through OIE_CC_BUCKET4_NAME, populating CP_BUCKET1_NAME through CP_BUCKET4_NAME for use as column headings. The function also sets P_CONC_REQUEST_ID, evaluates P_MIN_AMOUNT, and calls the helper routines.

• AFTERREPORT — performs post-processing cleanup after the report completes.
• GETNLSSTRINGS, GETCOMPANYNAME, GETBASECURRDATA, GETCARDPROGRAMNAME — retrieve NLS text, operating unit company name, base currency data, and the credit card program name respectively; each is validated in BEFOREREPORT and raises INIT_FAILURE on failure.
• SENDUNSUBMITTED, SENDMGRUNAPPROVED, SENDDISPUTED — generate notifications for unsubmitted card transactions, manager-unapproved transactions, and disputed transactions.
• CF_* formula functions — XML Publisher formula columns, including CF_REPORT_NUMFORMULA, CF_STATUSFORMULA, CF_CP_CURRENCY_CODEFORMULA, CF_EMP_CURRENCY_CODEFORMULA, CF_SUPERVISOR_NAMEFORMULA, CF_AGING_BUCKETSFORMULA, CF_AGING_SUP_NAMEFORMULA, CF_AGE_AMP_NAMEFORMULA, CF_EMP_NAME_SUMMFORMULA, CF_PENDING_AMOUNTSFORMULA, and CF_AGE_SUP_PEND_BUCKLET1FORMULA. These translate raw query columns into display values for currency codes, employee and supervisor names, aging buckets, and pending or aged amounts.

Tables Accessed

The package reads and, where required, writes the following documented tables through APPS synonyms:

• AP_CARDS and AP_CARDS_ALL — credit card definitions assigned to employees.
• AP_CARD_PROGRAMS and AP_CARD_PROGRAMS_ALL — card program setup supplying the program name and currency context.
• AP_CREDIT_CARD_TRXNS — the core credit card transaction data driving detail, summary, and aging output.
• AP_EXPENSE_REPORT_HEADERS and AP_EXPENSE_REPORT_HEADERS_ALL, with AP_EXPENSE_REPORT_LINES — expense report header and line data for reconciling card transactions.
• AP_SYSTEM_PARAMETERS — Payables system options, including base currency.
• PER_ASSIGNMENT_STATUS_TYPES — assignment status for identifying inactive employees.
• AP_CCARD_NOTIFICATION_ID_S — sequence used when generating cardholder notifications.

Usage Notes

AP_APXCCOUT_XMLP_PKG is invoked exclusively through the concurrent program definition of the same base name, executed from the Payables responsibility or scheduled as a request set. The XML Publisher template associated with APXCCOUT references the package's formula columns and the CP_BUCKET*_NAME variables to render aging column headings. Because the package has no reverse dependencies, it should not be called directly from custom forms or APIs; customizations should instead wrap the concurrent program or clone the package body under a distinct name. The bucket range parameters P_BUCKET1 through P_BUCKET3 are user-supplied and must be provided in ascending order to avoid INIT_FAILURE.