A user reported that their requisition was stuck waiting for a response from AIS integration. eVA showed 2 requisitions with the same PR number. One had a -V2 after it and the other did not. I verified that the requisition was processed in AIS and the reply was sent and then I resubmitted the reply but it still was not processed in eVA.
After contacting DGS they reported this:
the original requisition was denied, version 2 was created, re-submitted and denied, version 3 was created in Composing status, then the buyer clicked on the Undo button which caused version 3 to be deactivated in eVA and disappeared, then buyer re-submitted version 2 after the Undo for version 3. When the response was received from your ERP, eVA is unable to process it because it knows version 2 is no longer active since version 3 was created then deactivated when buyer clicked on the Undo button.
CGI was then contacted and reported that:
When the Undo changes button was hit Ariba did not delete the Req-V2 in composing status but inactivated it. A new Req-V2 is created when the change order is redone so the result is 2 Reqs in the system with the same UniqueName. (One active, one inactive)
This same scenario happened in AR-2463 and should be resolved by CSPL-1782 (hot fix patch) which is currently in UAT.
In order to fix this CGI had to rename the inactive requisition so that it would be unique.
DGS had to reset the flag in eVA that would cause the response from the ERP to be reprocessed against version 2.
DGS then resubmitted the reply.
NOTE: Per DGS - You know that this situation occurred when you see the 'Undo' action after V-2 PR is first denied by your ERP.