Submit Agreement API Generates MGT:Push XML With Blank Tags And UPDATE_ORDER Fails
(Doc ID 2900415.1)
Last updated on OCTOBER 03, 2022
Applies to:
Oracle Project Billing - Version 12.2.11 and laterInformation in this document applies to any platform.
Symptoms
The IGT Submit Integration APIs are completing with “Success” Status but when the UPDATE_ORDER fires it is failing when the G-Invoicing System User_id does not have proper grants given in G-Invoicing. There is no way to re-submit the IGT Submit Agreement API after the issue is resolved.
When user tries to re-submit Submit Agreement API it starts generating MGT:Push XML with blank tags and then again the UPDATE_ORDER fails.
The Status in IGT ORDER TABLE needs to be reset so that Submit Agreement API can be submitted again without errors.
Values above with [hidden value] are customer specific values.
Reproduce By Steps
1. The system_id has an incorrect value after order is downloaded.
2. The following process failed and the status was updated to NULL in the IGT Orders table
PO_IGT_SERVICE_INVOKER_ORDER: Intragovernmental Orders Interface Program
3.The system_id was corrected and the process was resubmitted.
4. The process no longer picks up the order.
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 |