Results for “auth_reversal_flag”

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

Overview

IBY_CREDITCARD_ISSUERS_VL is a seeded, VALID database view owned by the APPS schema within the IBY (Payments) product of Oracle E-Business Suite. It is a language-specific ("_VL") view, meaning it exposes translated descriptive attributes alongside the base operational columns of a credit card issuer record, filtered to the session's current language. In the payments model, a "credit card issuer" represents an accepted card brand or issuing authority (for example, a processor or card network) against which the Oracle Payments engine validates and authorizes card transactions initiated through iPayment and related flows.

The view presents issuer setup data — such as the issuer code, whether the issuer is accepted, the authorization validity period, and whether digit checking (the Luhn-style modulus check) applies — together with the translated issuer name and description. Because it returns only the language-appropriate translation row, it is the appropriate source for user-facing reporting, LOV-driven lookups, and integration extracts that must display human-readable issuer text without duplicate language rows. The OBJECT_VERSION_NUMBER column additionally supports optimistic concurrency control where the row is consumed by OAF-based or programmatic update logic.

Underlying Base Objects

The view is documented as a join over two synonym-referenced base objects: IBY_CREDITCARD_ISSUERS_B (the base table) and IBY_CREDITCARD_ISSUERS_TL (the translation table). The join predicate is B.CARD_ISSUER_CODE = T.CARD_ISSUER_CODE AND T.LANGUAGE = USERENV('LANG').

• IBY_CREDITCARD_ISSUERS_B — supplies all non-translated, operational attributes, including audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE), OBJECT_VERSION_NUMBER, and the functional setup columns CARD_ISSUER_CODE, CARD_ISSUER_ACCEPTED_FLAG, AUTHORIZATION_VALIDITY_PERIOD, and DIGIT_CHECK_FLAG.
• IBY_CREDITCARD_ISSUERS_TL — supplies CARD_ISSUER_NAME and DESCRIPTION for the language identified by USERENV('LANG').

Both underlying objects are addressed through synonyms in the APPS schema, consistent with standard EBS multilanguage ("MLS") design, where the _B table holds language-independent data and the _TL table holds language-dependent text keyed by CARD_ISSUER_CODE and LANGUAGE.

Key Columns

• ROW_ID — the base table ROWID, retained for row-level addressing.
• CARD_ISSUER_CODE — the unique business key of the issuer, used to join the base and translation records.
• CARD_ISSUER_ACCEPTED_FLAG — indicates whether the issuer is currently accepted for processing.
• AUTHORIZATION_VALIDITY_PERIOD — the period for which an authorization against this issuer remains valid.
• DIGIT_CHECK_FLAG — indicates whether digit (modulus) checking is applied to card numbers for this issuer.
• CARD_ISSUER_NAME and DESCRIPTION — the translated, user-facing name and description of the issuer, returned for USERENV('LANG').
• OBJECT_VERSION_NUMBER — version token supporting optimistic locking.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE, providing standard EBS WHO-column traceability.

Common Use Cases and Queries

Typical usage includes setup validation reports, LOV population for card issuer selection, and integration extracts that require the translated issuer name. The view's automatic language filtering makes it ideal when only the current-session translation is required.

List all accepted issuers:

• SELECT card_issuer_code, card_issuer_name FROM iby_creditcard_issuers_vl WHERE card_issuer_accepted_flag = 'Y' ORDER BY card_issuer_name;

Retrieve full configuration detail for a specific issuer:

• SELECT card_issuer_code, card_issuer_name, description, authorization_validity_period, digit_check_flag FROM iby_creditcard_issuers_vl WHERE card_issuer_code = :p_issuer_code;

Check whether digit checking is enforced before card validation logic runs:

• SELECT card_issuer_code, digit_check_flag FROM iby_creditcard_issuers_vl WHERE digit_check_flag = 'Y';

Because the view is read-only with respect to DML and derives translated text via USERENV('LANG'), reports should be run in the intended language session to obtain the correct CARD_ISSUER_NAME. Cross-referencing IBY_CREDITCARD_ISSUERS_TL directly is required only when translations for languages other than the session language must be enumerated.