My Oracle Support Banner

PMDSIMNT: Next Execution Date Repopulated With Start Date Even If User Does Not Amend Start Date (Doc ID 2899833.1)

Last updated on OCTOBER 01, 2022

Applies to:

Oracle Banking Payments - Version and later
Information in this document applies to any platform.


On : version, Implementation Support

SI Next Execution Date repopulated with Start Date even if user does not amend Start Date in PMDSIMNT

Earlier fix was given to repopulate SI Next Execution Date with the Start Date since users need to be able to amend SI Next Execution Date in some cases.

But now even if user does not amend Start Date system is repopulating Next Execution Date which means any amendment in PMDSIMNT screen will recalculate Next Execution Date. This is causing issues as original Start Dates in the past (sometimes 5 years old) are being populated as Next Execution Dates, SI job is then picking up these records and executing again 5 years.

Please provide a fix so that Next Execution Date is only recalculated if Start Date is being changed.

Next execution date should be populated only when it is modified or start date is modified

The issue can be reproduced at will with the following steps:
1. Do any amendment from PMDSIMNT screen.
2. Verify if start date and next execution date are amended.

The issue has the following business impact:
Due to this issue, execution dates are recomputed even if it is not amended.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.