My Oracle Support Banner

G-Invoice Order Status Does Not Match Between ECC Dashboard and G-Invoicing Due to an Invalid TAS BETC Code (Doc ID 2998465.1)

Last updated on JANUARY 16, 2024

Applies to:

Oracle Project Billing - Version 12.2.11 and later
Information in this document applies to any platform.

Symptoms

A G-Invoice order status does not match between Enterprise Command Center (ECC) and G-Invoice due to an invalid Treasury Account Symbol (TAS) / Business Event Type Code (BETC).
The order can not sync the rejected order back to G-Invoicing because it has an invalid TAS BETC code on the requesting side.
The correct requesting TAS BETC code is in the G-Invoice side for the order.

The G-Invoice order status is 'Closed' and in ECC the order status is 'Shared with Requesting'.
The rejected order created a Performance Obligation(POBG) entry and will not sync to G-Invoicing due to the invalid TAS BETC codes

The Agreement created by this order is missing the agreement version in the Update Agreement page.

To reproduce this issue, perform the following steps:

  1. Order is created by Requesting Agency and shared with Servicing
  2. Pull the order on the Servicing side and execute ECC (Enterprise Command Center) load program
  3. Order is Rejected by Servicing Agency
  4. Push Order to G-Invoicing with 'Intragovernmental Orders Interface Program'
  5. G-Invoice shows order as 'Closed' and ECC Dashboard shows order status of 'Shared with Requesting'
  6. Agreement that was created Resync us greyed out and will not allow resync.

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


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