Data validation (Detailed Validation) for the "Enterprise Resource Planning" "Financials AR Transactions" offering, shows 20 missing records. (Source Total Records 27, Warehouse Total Records 7, Source Unique Records 20). Investigation of the source transactions in OTBI/ Fusion shows that all the transactions appear to be fine and should have been imported. The only distinguishing factor, curiously, is that only the unaccounted transactions are imported and the properly accounted transactions are not imported. (This is the opposite of what one might expect). There is a mixture of transaction types, transaction dates and periods interspersed amongst both of the imported and failed to import transactions. Thus: - 7 transactions (2 credit memos, 5 invoices) which have been imported into FDI AR Transactions are "Transaction Distribution Details"."Accounted" = "No", "Subledger Accounting Journal Details"."Accounting Status" = "Draft" * - 20 transactions (2 credit memos, 5 invoices) which have been imported into FDI AR Transactions are "Transaction Distribution Details"."Accounted" = "Yes", "Subledger Accounting Journal Details"."Accounting Status" = "Final" I have tracked one or two of the resulting GL receivables journals and they also appear to be posted fine. Please note: * this is a test instance (hence the very low volume of transactions) and SLAM (sub-ledger accounting methodology) was changed recently * the other FDI 'offerings' (e.g. AP, FA, GL) appear to be importing data correctly What I have tried already: * Data Configuration/Pipeline Settings - Reset and Reload * For the Offering/functional areas of "Accounts Receivable", "Receivable Aging" and "AR Unaccounted Transactions"* Reload Data * Refresh Data * Deactivate / Reactivate * Checked that all transactions are "Complete" * Ensured that the "Earliest Extract Date" covers the period required (was set to "1 Apr, 2023", now set to "1 Apr, 2025"). I note some posts say that earlier versions (we are 26R1) included the interface tables which can be interrogated for more information using BIP/SQL, but the physical tables don't appear to be available as a data source. Can anyone please suggest what I should try next? Thank you!

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

FDI ERP Accounts Receivable Transactions not Importing Accounted Transactions

Simon Tomey

Data validation (Detailed Validation) for the "Enterprise Resource Planning" "Financials AR Transactions" offering, shows 20 missing records.
(Source Total Records 27, Warehouse Total Records 7, Source Unique Records 20).

Investigation of the source transactions in OTBI/ Fusion shows that all the transactions appear to be fine and should have been imported. The only distinguishing factor, curiously, is that only the unaccounted transactions are imported and the properly accounted transactions are not imported. (This is the opposite of what one might expect). There is a mixture of transaction types, transaction dates and periods interspersed amongst both of the imported and failed to import transactions.

Thus:
- 7 transactions (2 credit memos, 5 invoices) which have been imported into FDI AR Transactions are "Transaction Distribution Details"."Accounted" = "No", "Subledger Accounting Journal Details"."Accounting Status" = "Draft"

- 20 transactions (2 credit memos, 5 invoices) which have been imported into FDI AR Transactions are "Transaction Distribution Details"."Accounted" = "Yes", "Subledger Accounting Journal Details"."Accounting Status" = "Final"

I have tracked one or two of the resulting GL receivables journals and they also appear to be posted fine.

Please note:

this is a test instance (hence the very low volume of transactions) and SLAM (sub-ledger accounting methodology) was changed recently
the other FDI 'offerings' (e.g. AP, FA, GL) appear to be importing data correctly

What I have tried already:

Data Configuration/Pipeline Settings - Reset and Reload
For the Offering/functional areas of "Accounts Receivable", "Receivable Aging" and "AR Unaccounted Transactions"
- Reload Data
- Refresh Data
- Deactivate / Reactivate
Checked that all transactions are "Complete"
Ensured that the "Earliest Extract Date" covers the period required (was set to "1 Apr, 2023", now set to "1 Apr, 2025").

I note some posts say that earlier versions (we are 26R1) included the interface tables which can be interrogated for more information using BIP/SQL, but the physical tables don't appear to be available as a data source.

Can anyone please suggest what I should try next?

Thank you!

Find more posts tagged with

interface

Administration

Data Validation

records missing

Accepted answers

Simon Tomey

The reason we are getting no transactions in FDI once they are accounted is because we use multifund accounting and:

MFAR (Multifund Accounting) ledgers/transactions are not supported in Fusion Data Intelligence / Fusion Analytics Warehouse Accounts Receivables subject areas; MFAR-related AR transactions and receipts won’t appear (this is a product limitation, not a data load issue). AR Transactions and AR Revenue can include unaccounted transactions only if the AR Unaccounted Transactions functional area is activated; MFAR-ledger transactions that are visible are unaccounted and, once accounted, will not be available in the AR subject areas. The AR Aging and most other AR subject areas display only accounted receipts/invoices.

Sources:

Credit to the Oracle SR AI algorithm for this answer.

All comments

Arindam Sadhukhan-Oracle

Hi @Simon Tomey ,

The pattern you found is useful: the records loaded into FDI are Unaccounted / Draft, while the missing records are Accounted / Final.A practical next step is to compare one loaded transaction and one missing transaction using the Data Validation logs rather than doing more reset/reload cycles.

Checks:

In Detailed Validation, download the mismatch details and confirm the selected metric/column set is not indirectly scoped to AR Unaccounted Transactions.
Check the OTBI source query log and the OAC/FDI warehouse query log for the same validation run. Compare the filters for ledger, business unit, transaction date, accounting date, accounting status, and distribution grain.
Review Warehouse Refresh Statistics or rejected-record details for the AR pipeline to see whether the accounted transactions were rejected or skipped.
Since SLAM was changed recently, validate one missing transaction at the AR distribution and SLA accounting event level, not only at the posted GL journal level.
Confirm the Initial/Earliest Extract Date covers the relevant transaction date, accounting date, and related accounting event date.

If the logs do not show a clear filter, timing, security, or rejected-record reason, this is a good candidate for an SR. Include the validation export, OTBI/OAC query logs, pipeline run timestamp, sample transaction numbers, accounting status, ledger/BU, accounting dates, and details of the recent SLAM change.

Regards,

Arindam.

Simon Tomey

Thank you very much @Arindam Sadhukhan-Oracle for the comprehensive and timely response.

The issue is none of these things…apparently FDI does not support MFAR (Multi Fund Accounting for Receivables), which we are using. Credit to the AI tool in the SR as it gave me the answer and thanks again for your helpful response.

Simon Tomey

The reason we are getting no transactions in FDI once they are accounted is because we use multifund accounting and:

Sources:

Credit to the Oracle SR AI algorithm for this answer.