Recovery from an Unsuccessful Receivables Process FAQ [ ARUPDATE , etc.]
(Doc ID 1068495.1)
Last updated on MARCH 15, 2021
Applies to:PeopleSoft Enterprise FIN Receivables - Version 8.8 to 9.2 [Release 8.8 to 9]
Information in this document applies to any platform.
PeopleSoft Receivables Home 1299436.1 > PeopleSoft Receivables Troubleshooting Master Case Studies 1272622.1 > 1068495.1
When an Application Engine (AE) process runs, it locks tables for processing by stamping a non-zero value in process_instance fields and populates rows in run control tables. When a request ends abnormally, or goes to No Success, these tables will be left locked, and can lead to symptoms such as:
- Pending groups not posting or selected by ARUPDATE
- Payments not picked up by Payment Predictor
- Statements not generating
- Dunning Letters not generating
- Revenue Estimate and Budget Check not processing
- Customer accounts not aging
Unlocking and resetting the process instance to zero in the locked tables unlocks the rows in tables and enables you to rerun the process. This document lists the frequently asked questions about using the Reset Process function.
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
|PeopleSoft Receivables Home 1299436.1 > PeopleSoft Receivables Troubleshooting Master Case Studies 1272622.1 > 1068495.1|
|Questions and Answers|