G-Invoicing: Rejection Reason Is Not Mandatory on the Workflow Notification When an Approver Rejects the Order but Is a Required Field in G-Invoicing.
(Doc ID 3056178.1)
Last updated on DECEMBER 12, 2024
Applies to:
Oracle Project Billing - Version 12.2.10 and laterInformation in this document applies to any platform.
Symptoms
When the Agreement Approvers reject the Agreement/ IGT Order and the workflow notification is received, the rejection reason is not mandatory. Oracle is setting it to the default 'Order Rejected'. When the Agreement preparer rejects the Agreement, the rejection reason is mandatory in G-Invoicing. Users would like to have the rejection reason mandatory when rejecting the agreement through the workflow.
The User is testing this flow for first time, and seeing that the order is pushed to G-Invoicing even if a rejection status was not identified. In G-Invoicing, the rejection reason is mandatory. The customer's developer looked into the seeded workflow and looks like the seeded functionality in the workflow is if REASON is NOT communicated, is NOT set, then the l_comments is set to ‘Order Rejected’. The expected behavior is not to set the l_comments but require a reason for the rejection.
Steps to Reproduce:
1. Use a G-Invoicing responsibility
2. Update and submit the IGT Order and related Agreement for Approval.
3. Approver rejects the Agreement through the workflow and the rejection reason is not given.
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 |
Cause |
Solution |
References |