R12: AP: A Payment Process Request (PPR) Submitted in Payments Manager Stopped Unexpectedly in Status: New, and it is Stuck
(Doc ID 1937637.1)
Last updated on MARCH 31, 2020
Applies to:Oracle Payables - Version 12.0.0 and later
Oracle Payments - Version 12.0.0 and later
Information in this document applies to any platform.
Sporadically, a newly-submitted PPR stops quickly and unexpectedly in Status: New. There is nothing the user can do from the UI to progress it or Terminate it.
Such a PPR is actually "empty", since it contains no selected scheduled payments, and it has not acquired a lock on a Payment Document setup.
However, to the user, the PPR appears as being in-work. And the PPR gets included in Processing count in the Payments Dashboard in the Home tabbed region of Payments Manager.
While there is no technical impact from such an empty, stuck payment batch, the inability to Terminate it can still become source of uncertainty and concern for users.
The existing table data for a Status: "New" PPR can be verified using the PPR Data Collector Diagnostic (see Doc ID 463728.1 or Doc ID 732167.1), or using the Check_IBY.sql script (Doc ID 759037.1), or using the EBS Payments (IBY) Funds Disbursement Analyzer tool (Doc ID 1587455.1). You will find only a single row of table data for the PPR. Specifically, look for one row from table AP_INV_SELECTION_CRITERIA_ALL, in which status='UNSTARTED" (which gets displayed as "New" in Payments Manager).
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