Import Business Applications and Conditions for GT&C and Other Intragovernmental Transactions

The Department of the Treasury G-Invoicing application lets you enable the following business application (BizApp) features such as 7600EZ, Constructive Order Acceptance, and Performance during an Order Modification, to be used with G-Invoicing. These features are components of business applications, and the respective conditions must be setup to use them in the Department of the Treasury G-Invoicing application.

You can use the Intragovernmental BizApps and Features Interface Program to to import the required setup (BizApps and BizApp features) into Oracle Contract Lifecycle Management for Public Sector and Oracle Purchasing to validate and process intragovernmental transactions.

This enhancement supports intragovernmental procurement by improving IGT order creation, change processing, G-Invoicing communication, partner information, performance transaction handling, and related 7600-series processes.
The main benefit is more reliable integration and reduced manual rekeying between CLM Purchasing and external federal procurement or financial systems.
 

Steps to enable and configure

• The servicing and requesting agencies can use the concurrent program, Intragovernmental BizApps and Features Interface Program, to pull the business application (BizApps) and feature details to Oracle EBS.
• Review and complete the CLM Public Sector and G-Invoicing setup for the operating units, trading partners, document styles, and integration credentials that will use this process.
• Configure any required document styles, attribute templates, value sets, agency identifiers, business application values, and workflow actions for the IGT order scenario.
• Test the full requesting/servicing agency process with representative GT&C, order, modification, performance, or invoice data before rollout.

Tips and considerations

• Coordinate testing with both requesting and servicing agency roles so order sharing, modification, performance, and rejection scenarios are understood end to end.
• Use controlled integration payloads first, then validate error handling and document status changes before broader enablement.

Key resources

• Oracle E-Business Suite G-Invoicing Process Guide
• Oracle Contract Lifecycle Management for Public Sector Implementation Guide
• Oracle Contract Lifecycle Management for Public Sector Purchasing User Guide

Transfer of Information
R12.2.14 TOI: Implement and Use Procurement - G-Invoicing