Search Results ap_web_credit_card_wf




Overview
Explore in AI Chat

Overview

AP_WEB_CREDIT_CARD_WF is an Oracle E-Business Suite PL/SQL package owned by APPS that supports the Oracle Payables credit card workflow for expense reports. Its primary business function is to generate and deliver Oracle Workflow notifications associated with corporate credit card processing, including payment notifications to employees and card issuers, dunning (past-due) notifications for outstanding card charges, alerts regarding unsubmitted and unapproved expense reports, and notices of disputed charges. The package also produces summary listings of credit card transactions used to drive those notifications. It is a supporting infrastructure component of the Oracle iExpenses / Payables credit card program, allowing organizations to communicate card balances, payment outcomes, and required employee actions through the Workflow notification framework.

Key Procedures and Functions

The package exposes 27 documented procedures and functions. Payment-related notification is handled by SENDPAYMENTNOTIFICATION, which sends a Workflow notification to an employee when Payables makes an expense report payment either to the employee or directly to the credit card issuer. Several procedures manage charge-related communications: SENDUNSUBMITTEDCHARGESNOTE flags charges not yet submitted on an expense report, SENDUNAPPROVEDEXPREPORTNOTE addresses expense reports awaiting approval, SENDDISPUTEDCHARGESNOTE handles disputed card transactions, and SENDDUNNINGNOTIFICATIONS issues past-due reminders. Supporting these are list-generation routines such as GENERATELIST, GENERATEUNSUBMITTEDLIST, GENERATEDUNNINGLIST, GENERATEDUNNINGCLOBLIST, GENERATEMANAGERDUNNINGLIST, and GENERATENEXTMANAGERDUNNINGLIST, which build the content and recipient hierarchies for notifications. Utility and control functions include GETNUMOFDUNNINGRECORDS, GETNUMOFUNSUBMITTEDRECORDS, GETEMPLOYEECURSOR, GETHIERARCHIALEMPLOYEECURSOR, GETTOTALOUTSTANDINGATTRIBUTE, GETHIERTOTALOUTSTANDINGATTR, ISNOTIFICATIONREPEATED, and ISFIRSTDUNNING; SENDNOTIFICATIONS acts as the dispatch routine. These routines collectively determine recipients, outstanding balances, escalation paths, and whether a notification should be sent.

Tables Accessed

The package reads and writes data from core Payables and Human Resources tables through APPS synonyms. Credit card setup and transactions are sourced from AP_CARD_PROGRAMS, AP_CARD_PROGRAMS_ALL, AP_CARDS, AP_CREDIT_CARD_TRXNS, and AP_CREDIT_CARD_TRXNS_ALL. Expense report context is derived from AP_EXPENSE_REPORT_HEADERS, AP_EXPENSE_REPORT_HEADERS_ALL, and AP_EXPENSE_REPORT_LINES_ALL. Employee and assignment information for recipients and hierarchy escalation comes from PER_ALL_ASSIGNMENTS_F and PER_PERIODS_OF_SERVICE. Payment and bank account details reference IBY_EXT_BANK_ACCOUNTS. Workflow notification state is tracked through WF_ITEM_ATTRIBUTE_VALUES, and unique notification identifiers are generated using the AP_CCARD_NOTIFICATION_ID_S sequence. The global temporary table AP_CCARD_ESC_NEXT_GT supports escalation processing, while DBMS_LOB is used to build large notification content such as dunning lists.

Usage Notes

This package is invoked in the context of the Oracle Payables credit card workflow rather than called directly by end users. It typically executes from Workflow background processes, concurrent programs, and database triggers within the credit card expense management flow. The SendPaymentNotification procedure accepts a deferred flag that should be set to TRUE when the routine is called from a database trigger, deferring notification delivery to a background Workflow process. Because payment may be directed to the employee or the card issuer, certain parameters—such as the card issuer name—are passed as NULL when payment is made to the employee. The package is referenced by four other packages, confirming its role as a shared service. Customizations should avoid modifying this package; extensions should instead invoke its documented procedures through supported interfaces, respecting the notification and escalation logic embedded in the procedures and functions listed above.