G-Invoicing: Order Mod Rejected by Servicing and Modified by Requesting Is Not Updated Successfully: ‘This action is restricted as the Project has an associated order.’
(Doc ID 2971295.1)
Last updated on NOVEMBER 12, 2024
Applies to:
Oracle Project Billing - Version 12.2.9 and laterInformation in this document applies to any platform.
Symptoms
Order modification rejected by Servicing and modified by Requesting is not updated successfully on Servicing side after the modification by Requesting side.
Run the load program to reflect the changes
Task funding is not equal to the budget total of the task.
To baseline a draft budget, the budget total must be as same as funding total.
The issue can be reproduced at will with the following steps:
Scenario: Order mod rejection after order is approved and is modified by Requesting agency.
Step 1: Order is approved on Servicing side
Step 2: Order is pushed to G-Invoicing and is in open status
Step 3: Order is updated by Requesting and shared with Servicing
Step 4: Pull order on Servicing side and execute ECC (Enterprise Command Center) load program
Step 5: Perform order modification uptake
Step 6: After uptake is completed
Step 7: Order rejected by the preparer
Step 8: Order is rejected in G-Invoicing
Step 9: Order is modified by Requesting and shared with Servicing
Step 10: Order is pulled on Servicing and ECC load is executed
Step 11: Error after order modification uptake
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 |