Search Results payee_key

Overview

APPS.IBY_XML_FNDCPT_DEBITCARD_V is a dictionary view in the Oracle E-Business Suite payments schema (IBY) that assembles debit card payment instrument data into an XMLType document fragment. Its central purpose is to render payment instrument details in a structured XML form suitable for outbound payment message generation, integration payloads, and downstream reporting. The view is defined over transaction core records in IBY_TRXN_CORE together with debit card, credit card, and party/address reference data, and it applies Oracle XML SQL functions (XMLElement, XMLConcat, XMLForest) to produce a nested "PayerDebitCard" hierarchy containing card number, masked number, expiration, issuer, and cardholder billing information.

The presence of the view name in the currency of a search for "payee_key" reflects its dependence on a view parameter of that name. Where the payer instruction identifier and instrument number are both null, the view returns a NULL XML fragment; otherwise the ELEMENT is constructed, and card encryption is handled via IBY_UTILITY_PVT.GET_VIEW_PARAM('PAYEE_KEY'). This parameter supplies the encryption/decryption key material used by IBY_TRANSACTIONCC_PKG.UNENCRYPT_INSTR_NUM and IBY_CREDITCARD_PKG.UNCIPHER_CCNUMBER, meaning the view cannot resolve cleartext card numbers without the payee key context established by the calling session or application.

Underlying Base Objects

The documented base objects underlying the view span several schemas exposed through synonyms. Core transaction data is drawn from IBY_TRXN_CORE (SYNONYM) and IBY_TRXN_SUMMARIES_ALL (SYNONYM). Card-specific rows come from IBY_CREDITCARD (SYNONYM). Encryption and masking routines are invoked through IBY_TRANSACTIONCC_PKG, IBY_CREDITCARD_PKG, and IBY_UTILITY_PVT (PACKAGE). Cardholder and related party information is sourced from the HZ objects: HZ_PARTIES, HZ_PARTY_SITES, HZ_PARTY_SITE_USES, HZ_LOCATIONS, plus HZ_FORMAT_PUB and FND_TERRITORIES_VL for territory and address formatting. The XML output itself is typed using the XMLTYPE (TYPE) object. The view therefore bridges IBY payment transaction tables and HZ party/address data into a single canonical XML card representation.

Key Columns

The view does not expose flat relational columns so much as a generated XMLType with fixed element names. The primary root element is "PayerDebitCard", which contains:

• CardNumber — the decrypted instrument number, obtained via unencrypt_instr_num or uncipher_ccnumber using the PAYEE_KEY parameter.
• MaskedCardNumber — a masked representation produced by iby_creditcard_pkg.mask_card_number, retaining only limited digits for display.
• CardExpiration — formatted as YYYY-MM-DD from the instrument or card expiry date.
• SecurityValue — a placeholder element, typically null in the output.
• CardIssuer — derived from the instrument subtype.
• CardHolder — a nested structure comprising HolderName, a BillingAddress (AddressLine1-3, City, State, Country, PostalCode), PhoneNumber, and EmailAddress.
• CardSubtype — emitted from the card subtype code where available.

Because the shape is XML, consumers navigate via XPath rather than direct column selection.

Common Use Cases and Queries

Primary use cases include generating debit card payment payloads for bank or settlement integration, populating reporting extracts with masked or full card details, and validating cardholder billing data against HZ address records. A typical query retrieves the XML for a specific transaction:

• SELECT xml.column_value FROM APPS.IBY_XML_FNDCPT_DEBITCARD_V xml WHERE ... — subject to session FND view parameters such as PAYEE_KEY.
• Extracting individual elements: SELECT EXTRACT(x,'/PayerDebitCard/CardHolder/HolderName/text()') ...
• Reporting masked numbers only: reference MaskedCardNumber to avoid exposing cleartext PAN.

Note that successful retrieval of unmasked card data requires the correct PAYEE_KEY value to be set in the session view parameters; otherwise decryption or masking routines will not return usable values.