Oracle Fusion · Data dictionary
IBY_CREDITCARD
PaymentsUsed in 1 subject areas10 reporting columns
Payments (IBY).
Primary key: INSTRID
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| CARD_ISSUER_CODE | ● | Code identifying the card issuer. | |
| CARD_PURPOSE | ● | Card purpose. | |
| CHNAME | ● | Chname. | |
| DESCRIPTION | ● | Description. | |
| END_DATE | ● | End date. | |
| EXPIRYDATE | ● | Expirydate. | |
| FINAME | ● | Finame. | |
| INSTRID | PK | ○ | Instrid. |
| MASKED_CC_NUMBER | ● | Masked cc number. | |
| PURCHASECARD_FLAG | ● | Indicator (Y/N) for the purchasecard. | |
| START_DATE | ● | Start date. |
1 report read from this table
Change a column here and these are the reports that move with it, the blast radius for any change to IBY_CREDITCARD.
Where this surfaces in OTBI
The OTBI subject areas that expose this table. You can't join across them in OTBI, the owned conformed model joins them on shared keys.
Need the extract + dbt staging for IBY_CREDITCARD?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table