Nost Recon - Auto Reconciliation Incorrect Behavior For Outgoing Payments
(Doc ID 2889698.1)
Last updated on AUGUST 16, 2022
Applies to:
Oracle FLEXCUBE Universal Banking - Version 14.5.0.0.0 to 14.5.0.0.0 [Release 14]Information in this document applies to any platform.
Symptoms
On : 14.5.0.0.0 version, Implementation Support
ACTUAL BEHAVIOR
---------------
Nost Recon - Auto reconciliation incorrect behavior for outgoing payments
The auto reconciliation not working for the outgoing payments contract, The MT-103/202 messages are generating with the payments reference number and the same is received as part of MT-950.
The reconciliation is processed with the payments reference number for external entry and flexcube reference number for the internal entry so the match is not happening during the auto reconciliation process.
We are in 14.5.0.1.0 august maintenance line patch set.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Outgoing:
1. Booked an outgoing payments contract with payments reference number.
2. Processed the corresponding MT-950 message and we can see entry in mstb_dly_msg_in table.
3. Ran the following batches:
i) RESWIFT -> The messages are parsed successfully and posted the entries in RETB_UPLOAD_ENTRY and RETB_UPLOAD_STATEMENT.
ii) RESTMUL -> After running this job the entries are posted in RETB_EXTERNAL_ENTRY with the internal reference number(2217201342924000) from the MT-950 file.
iii) REINTCP -> This job captures the internal entries and posted in the RETB_INTERNAL_ENTRY table with internal_ref_no as trn_ref_no from actb_daily_log.
After this we ran the run the job for automatic matching(REAUTMC) and verified in the REDXSTIN screen we can see the corresponding entries are not matched as the reference number in the
RETB_EXTERNAL_ENTRY is not same as RETB_INTERNAL_ENTRY. Attached the simulation document with the complete screen shots.
Changes
Suggested to make auto_gen as Y in ACTM_INTERFACE_PARAM and Also remove the remove the external ref num from the rule maintaining screen
Cause
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
Symptoms |
Changes |
Cause |
Solution |