My Oracle Support Banner

G-Invoicing: Seller Facilitated Orders Rejected by the Requesting Agency Do Not Have REJ Status in the PA_IGT_ORDER Table. (Doc ID 2992973.1)

Last updated on DECEMBER 13, 2023

Applies to:

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


For Buyer Initiated Orders (BIO), when the order is rejected by the servicing agency, the Intragovernmental Transactions (IGT) Order in the PA_IGT_ORDER table is set to 'REJ' status to indicate the rejection (along with rejection reason). However for Seller Facilitated Orders (SFO) in SP2 status, when the requesting agency rejects the order, the REJ status is not recorded against the SFO order in the PA_IGT_ORDER table. The only place to see the Rejected status is from ECC dashboard in the order record. However, neither the IGT tables as well as the Agreement and Agreement Version tables record the rejection. There is no way to decipher the SFO order rejection other than to see the UDA data for the Rejection reason.

Steps to Reproduce:

1. SFO Order Created and Submitted to Requesting Agency for Approval
2. SFO Order Process Statuses - ORDER_STATUS_CODE is SP2
3. Order Rejected by the Requesting Agency
4. Order Status after “Intragovernmental Orders Interface Program”
5. Order imported with DR and SFO_NEW_UNFROZEN status. No REJ status to indicate rejection. ORDER_STATUS_CODE is DR
6. Only way to decipher SFO Order rejection is from “Rejection Reason” (No REJ status indicating rejection in PA_IGT_ORDER table. --DFF field C_EXT_ATTR36 shows the error


Look at the DFF values for the rejection code


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

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