Disbursement Payment File Formats

Payments

The disbursement payment file formats configured in Payments — the electronic formats (ISO 20022 pain.001, NACHA, BACS, regional schemes) used to transmit payments to each bank, with their mapping and status.

Sample build of the Disbursement Payment File Formats — reconciled, and rendered tool-neutral so it runs in Power BI, ThoughtSpot, or Tableau.

Sample build · illustrative

Filters

Trxn Document Id

1003

Formats

Banks

Unmapped method

Format	Scheme	Bank	Payment Method	Status
Sample	Sample	Sample	Standard	Open
—	—	—	Corporate	Posted
Sample	Sample	Sample	Standard	Validated
—	—	—	Default	Open
Sample	Sample	Sample	Standard	Paid
Sample	Sample	Sample	Standard	Open

AI Analyst · active

reading

The report reads the configured disbursement formats and their bank and payment-method assignments.

flag

Two banks have a payment method with no format assigned — electronic payments to them won't generate a file and will fail the run.

root cause & next step

Assign a format to each active bank-and-method pair; an unmapped method is a guaranteed payment-file failure.

Illustrative data. The live interactive version — drill-through, filters, export, and the AI Analyst — runs on your warehouse. See it live →

This is the report's BI Publisher data model — the SQL data set BI Publisher runs against Oracle tables to produce the output. The same SQL becomes a dbt model in your warehouse, so one definition drives both the formatted report and the analytics layer.

Data sources

IBY_TRXN_DOCUMENTS
IBY_FORMATS_VL
IBY_PAYMENT_METHODS_TL

How it interconnects: this data set reads the physical tables above. Those same tables surface in OTBI as subject areas and in BICC as PVOs — three lenses on one source. Open any table to trace its subject areas and View Objects.

SQL data set · genericized · parameterized · no hardcoded segments

Show / hide SQL

SELECT XMLTYPE(DOCUMENT, NLS_CHARSET_ID('UTF8'))
FROM IBY_TRXN_DOCUMENTS WHERE TRXN_DOCUMENT_ID =:TRXN_DOCUMENT_ID

:TRXN_DOCUMENT_ID

The data-warehouse model — one fact surrounded by conformed dimensions (what you slice by) and measures (what you aggregate), expressed as dbt so it migrates with you. Grain: one row per source transaction.

●— fact → dimension join

Element	Type	Definition
IBY_FORMATS_VL	dimension	dimension
IBY_PAYMENT_METHODS_TL	dimension	dimension
Amount	measure	measure

Runs on your cloud warehouse — Snowflake, BigQuery, Redshift, or Synapse on AWS, Google Cloud, Azure, or any provider. Reconciled to the source control total — 0% variance by design. You own the code, the model, and the data.

How the data gets here: a BICC bulk extract of the source tables above, on the same pattern for every report. See the extraction pattern & data flow →

See the complete model

How this report's fact and dimensions fit the full picture, via conformed keys.

Payments data model →Enterprise model →

Every source object behind this report. Each linked table has its own page with full column descriptions, drawn from the Oracle BICC lineage and articulated for practitioners.

Table	Reporting columns	Subject areas
IBY_TRXN_DOCUMENTS	Setup / configuration table — joined for reference, not exposed for analytics
IBY_FORMATS_VL	Setup / configuration table — joined for reference, not exposed for analytics
IBY_PAYMENT_METHODS_TL	3	9

Reporting columns = fields the report selects that are exposed as analytics attributes; subject areas = the OTBI subject areas the table appears in. Setup and configuration tables (master data, ledger and book setup, lookups) are referenced by the report's joins but aren't exposed as analytics columns or subject areas — that's expected, not a gap.