How to implement Document Sequencing for AR Direct Debit Transactions to an EFT file format
(Doc ID 2669137.1)
Last updated on MAY 17, 2020
Applies to:Oracle Fusion Receivables Cloud Service - Version 11.13.20.01.0 and later
Information in this document applies to any platform.
On : 11.13.20.01.0 version, Setup Module
How to implement Document Sequencing for AR Direct Debit Transactions to an EFT file format.
Customer is using an eText template in a report that runs against the 'Funds Capture Authorization and Settlement Formats' seeded Data Model that returns the output in the required format.
When they create and submit the settlement batches, will trigger the entire process and this file is transmitted to the bank.
The requirement is that one field in the output should be a 4 digit file creation number. This field should increment after every batch run all the way from 0001 - 9999 and rollover back to 0001.
There is a similar requirement in AP wherein it could simply configure a 'periodic sequence' with a minimum and a maximum value.
Customer implemented a logic where they would extract the last 4 digits of the 'InstructionInternalID' hoping that this field would increment by 1. The MBATCHID field in the iby_trxn_summaries_all table is the value that is used for the internal ID. The values are the generated for the same in order of creation date time:
Customer would like to know how exactly the MBATCHID is generated, how can be use for their requirement.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document