Search Results iby_xml_fndcpt_debitcard_v




Overview
Explore in AI Chat

Overview

The IBY_XML_FNDCPT_DEBITCARD_V view is an Oracle Payments (IBY) XML-generation view owned by the APPS schema. Its purpose is to emit a canonical <PAYERDEBITCARD> XML fragment that captures payer debit-card or credit-card instrument data for a payment transaction. It sits at the boundary between the Payments instrument model and the outbound XML payloads consumed by payment systems, bank connectors, and settlement processors.

The view is not a conventional relational projection. Each row produced is an XMLTYPE instance constructed through SQL/XML operators (XMLELEMENT, XMLCONCAT, XMLFOREST). Because these are database-native XML constructors, the view can be queried with ordinary SQL and consumed directly by XML-aware integration layers, including the Oracle Payments funds capture and disbursement XML services.

The view exists in both Oracle E-Business Suite 12.1.1 and 12.2.2, with the latter documented in ETRM. It is marked VALID and its structure has remained functionally stable across these releases, making it a reliable integration point for card-based payment flows.

Underlying Base Objects

The view is defined over a mix of transaction, instrument, and party-model objects. The documented references fall into three groups:

The definition applies a CASE branch. When both PAYERINSTRID and INSTRNUMBER are null, the view returns NULL, effectively suppressing an empty element. Otherwise, it builds the card payload from either the stylized IBY_TRXN_CORE columns or the IBY_CREDITCARD join path.

Key Columns

The view exposes a single XML-generating expression rather than named relational columns. The embedded elements are the meaningful output fields:

  • CARDNUMBER — decrypted via IBY_TRANSACTIONCC_PKG.UNENCRYPT_INSTR_NUM or IBY_CREDITCARD_PKG.UNCIPHER_CCNUMBER, depending on the branch.
  • CARDEXPIRATION — expiry date formatted as YYYY-MM-DD.
  • SECURITYVALUE — emitted as NULL (not stored in the instrument model).
  • CARDISSUER — sourced from TXN.INSTRSUBTYPE.
  • CARDHOLDER — a nested element carrying HOLDERNAME and a BILLINGADDRESS block (address lines 1–3, city, state, country, postal code) plus optional phone and email.
  • CARDSUBTYPE — from CORE.CARD_SUBTYPE_CODE.

Common Use Cases and Queries

Typical scenarios include building payment instruction XML for card processors, debugging funds-capture payloads, and validating address/number unmasking logic. A sample query follows:

  • SELECT * FROM APPS.IBY_XML_FNDCPT_DEBITCARD_V WHERE ROWNUM <= 10; — inspect generated fragments.
  • Join to IBY_TRXN_CORE by transaction identifier to filter a specific payment.
  • Extract values in SQL using EXTRACTVALUE or XMLTABLE against the XMLTYPE output.

Because the view invokes encryption/decryption package calls, queries should be restricted to appropriately privileged users and tightly filtered transaction sets.