Search Results credit_card_code




Overview
Explore in AI Chat

Overview

APPS.SO_CREDIT_CARDS_V is a simple reporting and validation view in the Oracle E-Business Suite Order Management (ONT) schema. It exposes the set of credit card types (such as Visa, Mastercard, and American Express) that have been defined as lookup values under the seeded CREDIT_CARD lookup type. Rather than returning transactional credit card data or payment instrument details, the view surfaces the reference or "code list" of acceptable credit card codes used throughout order entry, order import, and payment processing flows.

Because the view is owned by APPS and is defined over the SO_LOOKUPS synonym, it is accessible to any responsibility or concurrent program operating under the APPS schema. It is commonly referenced by forms, PL/SQL packages, and custom reports that need to present a user-friendly list of credit card types or map a stored credit card code to its descriptive meaning. The view plays a supporting configuration role: when a new card type is added to the Credit Card lookup, it becomes immediately visible through this view without any code change.

Underlying Base Objects

The view is defined with a single SELECT statement over SO_LOOKUPS, filtered to the CREDIT_CARD lookup type:

SELECT MEANING CREDIT_CARD,
       LOOKUP_CODE CREDIT_CARD_CODE
FROM SO_LOOKUPS
WHERE LOOKUP_TYPE = 'CREDIT_CARD'

SO_LOOKUPS is itself a synonym pointing to the underlying Oracle Order Management lookup table (historically FND_LOOKUP_VALUES, the standard Oracle Application Object Library lookup table). The filtered predicate restricts the result set to values maintained under the Order Management CREDIT_CARD lookup type. FND_GLOBAL is listed among the referenced objects, reflecting the standard globalization/security context used by lookup-based SQL in an EBS multi-org environment; it ensures lookup results respect language and application context.

Key Columns

  • CREDIT_CARD — The descriptive MEANING of the lookup value, i.e., the user-facing name of the card type (for example, "Visa" or "Mastercard"). This is the value typically displayed to end users.
  • CREDIT_CARD_CODE — The LOOKUP_CODE associated with the lookup value. This is the stored, internal code used on order and payment records to identify the credit card type. It is the value most commonly referenced by the search term "credit_card_code" when developers or analysts look up how a credit card type is stored and displayed.

The view does not expose the lookup type, description, tag, or enabled/start/end date attributes of the underlying lookup rows. Only those entries present in SO_LOOKUPS under the CREDIT_CARD type at query time are returned.

Common Use Cases and Queries

The view is typically used in custom reports, LOV (List of Values) definitions, and validation routines requiring the populated set of credit card codes and their descriptions. A representative query to list all configured credit card types is:

SELECT CREDIT_CARD_CODE, CREDIT_CARD
FROM   APPS.SO_CREDIT_CARDS_V
ORDER BY CREDIT_CARD;

To translate a stored code back to its descriptive meaning — for example, when formatting order or payment data — a join can be constructed:

SELECT o.order_number,
       cc.CREDIT_CARD
FROM   oe_order_headers_all o,
       APPS.SO_CREDIT_CARDS_V cc
WHERE  o.credit_card_code = cc.CREDIT_CARD_CODE;

Because the view returns only the code and meaning, it is best treated as a lightweight reference source. Analysts should confirm the actual stored credit card code column on the relevant order or payment interface tables when joining, and should be aware that additions or end-dating of Credit Card lookup values occur in the underlying lookup maintenance screens, taking effect in this view immediately.