Oracle Fusion · Data dictionary
IBY_EXTERNAL_PAYERS_ALL
PaymentsUsed in 1 subject areas8 reporting columns
Payments (IBY), transaction table (rows scoped across all operating units).
Primary key: EXT_PAYER_ID
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| BANK_CHARGE_BEARER_CODE | ● | Code identifying the bank charge bearer. | |
| DEBIT_ADVICE_DELIVERY_METHOD | ● | Debit advice delivery method. | |
| DEBIT_ADVICE_EMAIL | ● | Debit advice email. | |
| DEBIT_ADVICE_FAX | ● | Debit advice fax. | |
| DIRDEB_INSTRUCTION_CODE | ● | Code identifying the dirdeb instruction. | |
| EXT_PAYER_ID | PK | ○ | Identifier for the ext payer. |
| LOCALINSTR | ● | Localinstr. | |
| PURPOSE_CODE | ● | Code identifying the purpose. | |
| SERVICE_LEVEL | ● | Service level. |
2 reports 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_EXTERNAL_PAYERS_ALL.
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_EXTERNAL_PAYERS_ALL?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table