G-Invoicing: Seller Facilitated Order (SFO) Modification Failed The Push To G-Invoicing Due To Validation Failed Exception (Doc ID 2970777.1)

Last updated on FEBRUARY 19, 2024

Applies to:

Symptoms

Seller Facilitated Order (SFO) modification failed the push to G-Invoicing due to Validation Failed Exception.
The errors occur when a modification was done on the original Order.

2 SFOs with 2 exceptions each.

SFO 1 - XML error:
ValidationFailedException message = Field cannot be modified, added, or removed on orders with existing performance: orderStartDt</ErrorDesc><ErrorTitle>400
ValidationFailedException message = Field cannot be modified, added, or removed on orders with existing performance: objectClassCd, Line 2, Schedule 1</ErrorDesc><ErrorTitle>400

SFO 2 - XML error:
ValidationFailedException message = Field cannot be modified, added, or removed on orders with existing performance: fundingOfficeCd</ErrorDesc><ErrorTitle>400
ValidationFailedException message = Field cannot be modified, added, or removed on orders with existing performance: statAuthFundTitle</ErrorDesc><ErrorTitle>400

Reproducible Steps
==============
1. Create SFO and push to G Invoicing
2. Requesting Agency approves Order
3. Servicing creates a modification for the Order and pushes to G Invoicing
4. Push completes in error

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.