Search Results card_expired_flag
Overview
APPS.IBY_FNDCPT_PAYER_ALL_INSTRS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as IBY.IBY_FNDCPT_PAYER_ALL_INSTRS_V. It belongs to the Oracle Payments (IBY) module and consolidates the payment instruments — credit cards and bank accounts — associated with a payer party. Because it is a view rather than a table, it exposes a unified, read-only projection across several underlying Payments entities, allowing reporting and integration queries to retrieve instrument details without navigating the separate credit card and external bank account structures.
The view carries the standard Oracle internal warning: it is intended for use by standard Oracle Applications programs, and Oracle Corporation does not support direct application-data access through it. In practice, however, it is widely referenced in custom reporting and diagnostics. Status is VALID, and the object type is listed as an Internal view. In Oracle EBS 12.1.1 and 12.2.2 the view is present with identical column layout, making queries portable across both releases.
Underlying Base Objects
The documented dependencies for this view are:
FND_GLOBAL(package) — supplies session context such asORG_IDand user identity used in the view's security and lookup logic.FND_LOOKUPS(view) — resolves lookup codes and meanings, for example payment instrument types and card subtypes.IBY_ACCOUNT_OWNERS(synonym) — links instruments to the owning party and defines the payer relationship.IBY_CREDITCARD(synonym) — the credit card instrument records, including card number, expiry, and holder details.IBY_CREDITCARD_ISSUERS_VL(view) — the issuers (card brands/issuing banks) associated with credit cards.IBY_EXT_BANKACCOUNTS_V/IBY_EXT_BANK_ACCOUNTS_V(view) — external bank account instruments, contributing account, bank, branch, and BIC information.
The view joins these so that a single row represents one instrument — either a card or a bank account — for a given party.
Key Columns
PARTY_ID— the payer party that owns the instrument.INSTRUMENT_TYPE— distinguishes credit card versus bank account instruments.INSTRUMENT_ID— the unique instrument identifier.CURRENCY_CODE— currency of the instrument.CARD_NUMBER,CC_NUMBER_HASH1,CC_NUMBER_HASH2— card number and its hash representations for secure matching.CARD_EXPIRYDATE(DATE) — the card expiry date. The ETRM documentation explicitly notes this column is Obsoleted as part of PA-DSS uptake, meaning it is retained structurally but no longer populated for PA-DSS compliance.MASKED_CARD_EXPIRYDATE(CHAR) — the PA-DSS-compliant, masked representation intended for display in place of the obsoleted full date.CARD_EXPIRED_FLAG— indicates whether the instrument has expired.- Card attributes:
CARD_ISSUER_CODE,CARD_ISSUER_NAME,PURCHASECARD_SUBTYPE,CARD_HOLDER_NAME,MASKED_CARD_HOLDER_NAME,CARD_BILLING_ADDRESS_ID,CARD_FI_NAME,CARD_SINGLE_USE_FLAG. - Bank attributes:
ACCOUNT_NUMBER,BANK_ACCT_NUM_HASH1,BANK_ACCT_NUM_HASH2,BANK_NAME,BANK_NUMBER,BRANCH_NAME,BRANCH_NUMBER,BIC_NUMBER. DESCRIPTION— free-text description of the instrument.
Common Use Cases and Queries
A frequent reporting need is to list all instruments for a payer, including masked card expiry. Note that because CARD_EXPIRYDATE was obsoleted for PA-DSS, MASKED_CARD_EXPIRYDATE should be used for display:
SELECT party_id
, instrument_id
, instrument_type
, card_number
, masked_card_expirydate
, card_expired_flag
FROM apps.iby_fndcpt_payer_all_instrs_v
WHERE party_id = :p_party_id;
To identify expired cards for a party, filter on the expired flag rather than the obsoleted date column:
SELECT instrument_id, card_number, masked_card_expirydate FROM apps.iby_fndcpt_payer_all_instrs_v WHERE instrument_type = 'CREDITCARD' AND card_expired_flag = 'Y';
Bank-only extracts use INSTRUMENT_TYPE to isolate account records and report bank and branch details. For integrations, join on INSTRUMENT_ID and PARTY_ID to reconcile instruments back to payment transactions. Because the view is unsupported for direct access, custom code should treat it as a diagnostic aid and prefer supported APIs where functional processing is required.
-
VIEW: APPS.IBY_FNDCPT_PAYER_ALL_INSTRS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_FNDCPT_PAYER_ALL_INSTRS_V, object_name:IBY_FNDCPT_PAYER_ALL_INSTRS_V, status:VALID,
-
VIEW: APPS.IBY_FNDCPT_PAYER_ALL_INSTRS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_FNDCPT_PAYER_ALL_INSTRS_V, object_name:IBY_FNDCPT_PAYER_ALL_INSTRS_V, status:VALID,
-
VIEW: APPS.IBY_TRXN_EXTENSIONS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_TRXN_EXTENSIONS_V, object_name:IBY_TRXN_EXTENSIONS_V, status:VALID,
-
VIEW: APPS.ASO_PAYMENTS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:ASO.ASO_PAYMENTS_V, object_name:ASO_PAYMENTS_V, status:VALID,
-
VIEW: APPS.IBY_FNDCPT_PAYER_ASSGN_INSTR_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_FNDCPT_PAYER_ASSGN_INSTR_V, object_name:IBY_FNDCPT_PAYER_ASSGN_INSTR_V, status:VALID,
-
VIEW: APPS.IBY_FNDCPT_PAYER_ASSGN_INSTR_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_FNDCPT_PAYER_ASSGN_INSTR_V, object_name:IBY_FNDCPT_PAYER_ASSGN_INSTR_V, status:VALID,
-
VIEW: APPS.IBY_TRXN_EXTENSIONS_V
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_TRXN_EXTENSIONS_V, object_name:IBY_TRXN_EXTENSIONS_V, status:VALID,
-
VIEW: APPS.IBY_EXTN_INSTR_DETAILS_V
12.2.2
owner:APPS, object_type:VIEW, object_name:IBY_EXTN_INSTR_DETAILS_V, status:VALID,
-
VIEW: APPS.ASO_OA_PAYMENTS_HDR_V
12.2.2
owner:APPS, object_type:VIEW, object_name:ASO_OA_PAYMENTS_HDR_V, status:VALID,
-
VIEW: APPS.ASO_OA_PAYMENTS_LINE_V
12.2.2
owner:APPS, object_type:VIEW, object_name:ASO_OA_PAYMENTS_LINE_V, status:VALID,
-
APPS.OKS_UTIL_PUB SQL Statements
12.2.2
-
APPS.OKS_ARFEEDER_PUB dependencies on IBY_TRXN_EXTENSIONS_V
12.2.2
-
APPS.OKS_ARFEEDER_PUB SQL Statements
12.2.2
-
APPS.OKS_UTIL_PUB dependencies on IBY_TRXN_EXTENSIONS_V
12.2.2
-
PACKAGE BODY: APPS.OKS_UTIL_PUB
12.2.2
-
PACKAGE BODY: APPS.OKS_ARFEEDER_PUB
12.2.2
-
eTRM - IBY Tables and Views
12.1.1
description: Stores the user privilege settings for viewing sensitive data in iPayment operations UI ,
-
eTRM - IBY Tables and Views
12.2.2
description: Stores the user privilege settings for viewing sensitive data in iPayment operations UI ,
-
eTRM - ASO Tables and Views
12.2.2
description: This tables is used to log messages during the migration in Order Capture. ,