C1-PEPL2: CUST_ID Field Not Populated On The Payment Event Tender Screen
(Doc ID 1960893.1)
Last updated on OCTOBER 06, 2022
Applies to:
Oracle Public Sector Revenue Management - Version 2.3.1.2.0 to 2.4.0.1.0 [Release 2.3 to 2.4]Information in this document applies to any platform.
Symptoms
After running C1-PEPL2, CUST_ID field is not populated on the Payment Event - Tenders tab.
CUST_ID field on is expected to be populated from the Payment Event Upload Staging
STEPS
-----------------------
1- Payment Event Upload Staging has CUST_ID field populated.
2- Run batches C1-PEPL1 then C1-PEPL2.
3- The resulting Payment Event - Tenders tab does not have the CUST_ID field populated.
Changes
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 |
| References |