Search Results convert_currency_code




Overview
Explore in AI Chat

Overview

APPS.AP_WEB_CC_VALIDATIONS_PKG is an Oracle E-Business Suite PL/SQL package that supports the Oracle Payables credit card transaction processing flow, specifically the validation and defaulting of credit card records imported through the Payables credit card workbench. The package is declared with AUTHID CURRENT_USER, meaning its executable privileges are resolved against the invoking schema rather than the defining schema, which is consistent with its role as a set-based processing utility rather than a stored API with invoker/definer semantics. Its header comment (apwccvls.pls, version 120.4.12010000.4, dated 2010) describes four functional groupings: "set" routines that define the set of transaction records to process, defaulting/conversion routines, validation routines, and utility routines. Groups one through three work together: the set routines establish the working row set, the defaulting routines populate or transform values, and the validation routines then evaluate individual attributes of each record. The ETRM classification for this package is OTHER, indicating it is an internal processing package rather than a formal public API such as an Open Interface or a standard business API.

Key Procedures and Functions

The documented interface contains 33 procedures and functions. The "set" routines, SET_ALL_ROW_SET and SET_ROW_SET, define the population of credit card transaction records that subsequent defaulting and validation steps operate upon. The defaulting group includes DEFAULT_ORG_ID, SET_REQUEST_ID, SET_VALIDATE_REQUEST_ID, DEFAULT_FOLIO_TYPE, DEFAULT_DETAIL_FOLIO_TYPE, DEFAULT_COUNTRY_CODE, DEFAULT_PAYMENT_FLAG, CONVERT_CURRENCY_CODE, GET_LOCATIONS, SET_PAYMENT_SCENARIO, and DEFAULT_MERCHANT_NAME; these populate organizational, request-tracking, folio, geography, payment, currency, location, and merchant values on transaction records.

The validation group performs one check per attribute, including DUPLICATE_TRX, INVALID_BILLED_AMOUNT, INVALID_BILLED_CURRENCY_CODE, INVALID_BILLED_DATE, INACTIVE_CARD_NUMBER, INVALID_CARD_NUMBER, INVALID_MERCHANT_NAME, and INVALID_POSTED_CURRENCY_CODE. The INVALID_CARD_NUMBER function is directly relevant to the search term "invalid_card_number": it validates the card number on a credit card transaction, and it operates alongside INACTIVE_CARD_NUMBER, which tests whether the referenced card is inactive in the card setup tables. The package also documents additional validation routines such as INVALID_TRX_AMOUNT, INVALID_TRX_DATE, INVALID_SIC_CODE, CHECK_EMPLOYEE_TERMINATION, and VALID_TRX, the last of which is expressly noted in the header as a special routine that must be called last from the defaulting and validation groups. Per the header comment, all routines in the defaulting and validation groups accept a p_valid_only parameter; when passed TRUE, the routine restricts its operation to the subset of records that have not already failed validation.

Tables Accessed

The package references five documented tables through APPS synonyms. AP_CARDS_ALL stores the credit card definitions used by INACTIVE_CARD_NUMBER and INVALID_CARD_NUMBER to verify card existence and status. AP_CARD_DETAILS holds supplementary card attributes consulted during card-level validation. AP_CARD_EMP_CANDIDATES associates employees with candidate cards and supports employee-related checks such as CHECK_EMPLOYEE_TERMINATION. AP_CREDIT_CARD_TRXNS_ALL is the primary transaction table against which the set routines, defaulting routines, and per-attribute validators operate. FINANCIALS_SYSTEM_PARAMETERS provides system-level setup values used during defaulting and conversion, such as organizational and currency defaults.

Usage Notes

AP_WEB_CC_VALIDATIONS_PKG is invoked as part of the Oracle Payables credit card transaction processing flow, typically from the credit card workbench functionality in the Payables web user interface and from the concurrent programs that import and validate credit card transaction data. The ETRM metadata records that the package is referenced by one other package, indicating it is called programmatically by a higher-level credit card processing package rather than being exposed directly as an end-user API. Callers are expected to follow the documented sequence: first establish the row set, then apply defaulting routines, then execute the individual validation functions, and finally call VALID_TRX as the terminal validation step. The p_valid_only parameter allows callers to iterate only over records that remain valid, avoiding repeated processing of records already known to have failed. Custom code that extends or diagnoses credit card validation behavior should reference these procedures by name and preserve the documented ordering constraints.