ELA: OPEX AGREEMENT NUMBER NOT POPULATED FOR LEASES IMPORTED BY RE_LS_IMPORT
(Doc ID 2653126.1)
Last updated on OCTOBER 12, 2020
Applies to:PeopleSoft Enterprise FIN Lease Administration - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
The Agreement Number (PS_RE_LS_TRM.AGREEMENT_NUM) does not get populated when leases are imported via the RE_LS_IMPORT process. The rows in the PS_RE_LS_TRM table are created for the lease but the agreement number field is left blank. If a lease is entered online, the agreement number is populated. When the lease is imported via the RE_LS_IMPORT process, the agreement number is left blank and there is no way to populate the agreement number for these rows on the online pages. However, if a new operating expense payment type is added to an imported lease, the agreement number is populated on that manually added row.
The import process should populate an agreement number for the Operating Expense Details.
The issue can be reproduced at will with the following steps:
1. Import a Lease via the online lease import process.
2. Review the Operating Expense Details on the imported lease. The agreement number has not been auto generated.
3. Add a Lease via the online pages.
4. Review the Operating Expense Details on the online created lease. The agreement number has been auto generated.
The replication steps can be reviewed here.
The supporting data can be reviewed here.
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