G-Invoicing: Performance Obligation Failed To Push to G-invoicing With Invalid BETC – Error: ‘Invalid BETC AP’ and ‘Invalid Tas Betc Components’
(Doc ID 3048220.1)
Last updated on SEPTEMBER 18, 2024
Applies to:
Oracle Project Billing - Version 12.2.13 and laterInformation in this document applies to any platform.
Symptoms
A performance obligation was created with an incorrect BETC (Business Event Type Code) value, then approved and failed when interfaced to G-Invoicing.
The order is in a failed status, but cannot be updated to be corrected. The Servicing BETC needs to be corrected.
The pa_igt_order table will have the order with the error_descr containing
'Invalid BETC <invalid BETC value>'
'invalid Tas Betc Components'
The xml response log will contain
...
Status></ErrorDetail><ErrorDetail><ErrorDesc>ValidationFailedException message = Invalid BETC AP.</ErrorDesc><ErrorTitle>400 ValidationFailedException
Steps to Reproduce:
1. Log into a Projects G-Invoicing responsibility
2. Create a performance obligation with an incorrect BETC entered
3. Approve the performance
4. Submit the Intragovernmental Orders Interface Program
5. Note the order fails to interface to G-invoicing.
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 |