I'm not sure if other organizations also face this issue, usually during amendments to the lease, users are unable to save the lease due to some SQL fatal error (refer the attached image). On setting up Peoplecode trace we notice, it looks for the pre-existing row in the RE_OPT_SCHED table, to resolve this, we usually end up inserting the data from the database backend based on the data we see in the other test/dev environment for particular SCHEDULE_KEY, and user can continue working on the lease. We would like to know what causes the row to get removed as it happens randomly for a lease not for every lease.
Do anybody else also face the same/similar issue? We are on PUM image 29 for the Lease Management module PS 9.2.
Beyond 9.2 PUM Image 29 there is only 1 bug fix [Bug 28269310] in Image 31 which modified this app package class. Try replicating this issue in 9.2 PUM Image 31 or later. If it gets replicated then certainly a bug that needs to be reported to Oracle Support in a SR.
For product specific questions you should post them in appropriate product communities for better response.
For Asset Management & Lease Administration related questions, please post a question in: Asset Lifecycle Management (ALM) - PSFT (MOSC)
Hope this helps!