G-Invoicing: Order Approval Errors With 'The Agreement submission failed as Servicing Agency Advance and Billing attributes Advance Revenue Recognition Description contain values for the non-Advance enabled orders. Correct the values and retry...' (Doc ID 3075102.1)

Last updated on MARCH 06, 2025

Applies to:

Symptoms

General Terms and Conditions (GTC) is Advance based. Requesting Agency created an Advance based order and shared with the Servicing Agency. The Servicing Agency dissociated the project and rejected the order as the order was decided to be Non -Advance based. Requesting Agency updated the order to Non-Advance and shared with the Servicing Agency. The order then was interfaced and doesn't have the Advance Based Flag checked on. However, once the project is associated and order is submitted for Approval, and the error is being received.

These fields have become non updatable after the order was updated to Non-Adv and pulled back.

Advance Revenue Recognition Methodology
Servicing Agency's Advance Payment Authority Citation
Servicing Agency's Advance Payment Authority Title

Steps to Reproduce:

1) Create a Advance enabled buyer initiated order (BIO) order and pull into EBS Projects. The Advance Revenue Recognition Description (c_ext_attr36) field has default value of 'Please Update Description'.

2) Reject the order from Update Agreement page.

3) Now go to G-Invoicing and update the schedule as non-advance and share with servicing.

4) Pull the order into EBS and observe that it is still having the default value in Advance Revenue Recognition Description field.

Cause

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