This chapter covers the following topics:
The Oracle E-Business Suite (EBS) solution for G-Invoicing works with the federal G-Invoicing application to facilitate the processing and accounting of intragovernmental buy and sell transactions. The solution is integrated with Oracle Contract Lifecycle Management for Public Sector, Oracle Purchasing, and Oracle Projects, and other products play supporting roles.
As a federal program agency, you can use the EBS G-Invoicing solution to:
Broker IGT buy and sell transactions through a common data repository.
Exchange data related to agencies and groups, General Terms and Conditions (GT&Cs), orders, modifications, and performance records.
Improve auditability by associating related transactions with a common identifier.
Integrate data from these activities into your accounting systems.
The following diagram shows the exchange of G-Invoicing data between the requesting agency, the federal G-Invoicing application, and the servicing agency.
Oracle EBS uses REST services to communicate with the federal G-Invoicing application. Federal agencies push and pull IGT data to and from the federal application. Data pulled into EBS is validated, and corresponding transactions are created within EBS.
The EBS G-Invoicing solution includes the following features:
Default attributes from GT&Cs for order creation and validation
Predefined and customizable user defined attribute (UDA) templates and document styles
A tracking mechanism for intragovernmental transactions
A request log
The overall sequence of events for an IGT is as follows:
A servicing or requesting agency creates GT&Cs in the federal G-Invoicing application.
Both agencies use the federal application to approve the GT&Cs.
The requesting agency pulls the approved GT&Cs from the federal application into EBS.
The requesting agency creates an order in Oracle CLM or Oracle Purchasing and then pushes the order to the federal application.
The servicing agency pulls the order from the federal application, uses Oracle Projects to add any required information and accept the order, and then pushes it back to the federal application.
The servicing agency fulfills or begins working on the order, reporting performance on the order upon fulfillment or over time.
The requesting agency records the received quantity against delivered performance and pushes the performance details to the federal G-Invoicing application.
Before you begin, refer to My Oracle Support Note ID 2600811.1, G-Invoicing Integration, for details about EBS G-Invoicing integration and patches.
You must be running Oracle E-Business Suite Release 12.2.7 or higher.
You must have implemented Oracle Contract Lifecycle Management for Public Sector (CLM) or Oracle Purchasing.
If you are using Oracle Purchasing rather than CLM then you must apply Patch 28654205:R12.PO.D.
You must implement Buyer Work Center for user defined attributes (UDAs).
You must implement Oracle General Ledger for integration with accounting, Oracle Federal Financials for TAS definition and related setup, Oracle Payables for invoices, receipts, and payments.
Note: Reimbursable orders are supported only in Buyer Work Center, and local blanket releases are not supported by the EBS G-Invoicing solution.
To set up the EBS G-Invoicing solution, complete the following tasks.
Set up access control for G-Invoicing.
See also the Bureau of the Fiscal Service resources website: https://www.fiscal.treasury.gov/g-invoice/resources.html
Enter security certificate and schema details and associate system IDs in the G-Invoicing Options page.
See G-Invoicing Options.
Set the following profile options.
Profile Option | Admin Update Levels | User | Required | Value | Description |
---|---|---|---|---|---|
G-Invoicing Service Host | Site | No | Yes | - | Use this profile option to set the service host and port details. Obtain the service host value from the document G-Invoicing System Interface Specifications - Pull for general terms and conditions, orders and performance at https://fiscal.treasury.gov/g-invoice/resources.html. Example host names: Production: ws.igt.fiscal.treasury.gov Quality Assurance Current: .ws.igt.fiscal.treasury.gov Quality Assurance Future: qaf.ws.igt.fiscal.treasury.gov Functional Test: ft.ws.igt.fiscal.treasury.gov |
G-Invoicing Service Path | Site | No | Yes | - | Use this profile option to set the service path details. Obtain the service host value from the document G-Invoicing System Interface Specifications - Pull for general terms and conditions, orders, and performance at https://fiscal.treasury.gov/g-invoice/resources.html. Example: /ginv/services |
G-Invoicing Integration Admin | Site, Application | No | Yes | - | Use this profile option to set the email address of the administrator who should be notified about problems communicating with the federal G-Invoicing application. |
FV: Federal Enabled | Responsibility | Yes | Yes | - | To display and use the Intragovernmental option in the Requisitions window, set this profile option to Yes at the responsibility or user level.
Note: You must enable this profile option in order for the funding official to approve IGT orders. |
MO: Default Operating Unit | Site, Application | - | - | - | Set this profile option to the operating unit that you want to use by default. |
Include lookup codes for the PO IGT Object Class Code exactly as they appear in the federal G-Invoicing application.
To find the object class codes, log in to the Treasury portal, click the Requesting Agency tab, and then navigate to Orders, Schedules, and then Funding Information. The lookup codes are listed in the Object Class Code drop-down list.
In EBS, switch to the Functional Administrator responsibility. Click the Core Services tab and then the Lookups tab. Search for the PO IGT Object Class Code lookup type in the Lookup Types page. Add the lookup codes that you require for your business.
For more information about lookups for G-Invoicing, See the table "Predefined User/Extensible Lookups in G-Invoicing" in Appendix A, "Predefined Lookups in CLM" in Oracle Contract Lifecycle Management for Public Sector Implementation Guide.
Check and, if necessary, update the document style for IGTs. This document style will be used for creating GT&Cs.
Switch to the CLM Purchasing Super User or the Purchasing, US Federal responsibility. Click Setup, then Purchasing, and then Document Styles.
To use the predefined document style, IGT Document Style:
If you are using Oracle Purchasing, then leave this document style as it is (unless you are using a custom workflow).
If you are using Oracle CLM, then you must select the CLM Enabled option. Document Styles page, enter IGT Document Style in the Name field. Select the CLM Enabled check box and click Apply.
To use a custom document style, use the Documents Styles page to create a new document style.
Select IGT Enabled. When you select this option, the document style is associated with IGTs and update is disabled.
In the Document Controls region, in the Approval Workflow field, select PO IGT APPROVAL.
In the Workflow Startup Process field, select PO IGT Approval Top Process.
Note: The line types used for G-Invoicing are Goods and Services. Temp Labor does not apply to IGTs. Therefore, the Commodities region on the Document Styles page includes only goods and services as purchase bases. By default, both types are selected.
For more information about custom document styles, see "Document Styles."
(Conditional) If you are using AME, configure an approval workflow.
Include the following elements:
Attribute: IGT_FLAG
Condition: IGT_FLAG (Y)
Approver group (approvers other than the funding and program officials, who are the "post approvers")
IGT Signature Group: IGT_SIGN_GROUP
Rule: IGT_SIGNATURE_RULE
Note: On the IGT Order page, you can enter program and funding officials as post approvers. After the approvers from the AME workflow approve the order, the approval notification is sent to the post approvers.
(Optional) Enable e-signature for program and funding officials.
If you use e-signatures for IGT order approval in Oracle CLM or Oracle Purchasing, then enable e-signature for the program and funding officials.
Using the CLM Purchasing Super User or the Purchasing, US Federal responsibility, click Setup, then Purchasing, and then Document Styles.
Select an IGT document style and click Update.
In the Document Controls region, select Enable e-Signature for Program and Funding Official.
Click Apply.
Set purchasing options.
Using the CLM Purchasing Super User or the Purchasing, US Federal responsibility, click Setup, then Organizations, and then Purchasing Options. The Purchasing Options page appears.
(Optional) If you want a specific buyer to be automatically assigned to all GT&Cs, specify that buyer in the Buyer field in the Document Defaults region.
Note: A default buyer is mandatory in the purchasing options. If you want to set up multiple buyers to be used depending on certain attributes, then use the custom hook PO_CUSTOM_IGT_PKG to populate buyer names.
In the Receipt Accounting region, specify when to accrue expense items: at period end, or at receipt.
In the G-Invoicing Defaults region, in the Document Style for Pull field, select the default document style that you created in the Document Styles page.
Note: All global and local styles that are related to the selected operating unit (OU) are available in this field. If you select a local document style, it must have the same OU as the one selected in the purchasing options.
.
Enter a default ship-to location in either the Supplier Details or the Financial Options.
Use the CLM Purchasing Super User or the Purchasing, US Federal responsibility.
Click Buyer Work Center, then Suppliers, and then Purchasing and then enter the ship-to location for the supplier site.
Search for a supplier and click Update.
In the side navigation panel, click Purchasing.
For financial options, click Suppliers and then Purchasing, and enter the ship-to location.
Review the predefined UDA templates and associated attributes, and compile each template before use.
From the home page, select either the CLM Purchasing Super User or the Purchasing, US Federal responsibility.
Click Setup, then Attribute Setup Workbench, then Attribute Templates.
If you are using the predefined template, verify that the template has all the applicable usages and attributes and that it is compiled.
The predefined attribute template for GT&Cs has only one header template. For IGT orders there are four templates: Header, Line, Schedule, and Distribution.
Note: If you use custom UDA templates, create each template by first selecting a predefined template and copying the usages, attributes, and groups. For modifications, you must also copy the document numbering and ensure that the template has modification context. If there is a change in an attribute group or template, then compile the template before you use it.
See Attributes and Attribute Groups for more information.
Create a servicing agency as a supplier and set the servicing agency location code (ALC) as the supplier site. Provide global details (the Trading Partner Agency Identifier) under Organizations, ALC for the bank account under Banking Details (click Show Bank Account Details) in the Edit Supplier page.
Enter the requesting ALC in the buying agency bank account details in the Federal Controls page.
Select the Payables Super User responsibility, then Setup, then Bank Account, then Account Controls, and then Federal Controls.
Add the Federal IGT UOM context to the UOM DFF, and set the IGT flag for the context to Yes.
Only the UOMs that you add to the Federal IGT UOM are used in intragovernmental transactions.
To set up a UOM that is published in the G-Invoicing portal and already exists in Oracle Purchasing, set the IGT flag to Yes for the Federal IGT UOM context.
To set up a UOM that is published in the G-Invoicing specification but does not exist in Oracle Purchasing, create the UOM in Oracle Purchasing and then set the IGT flag to Yes for the Federal IGT UOM context.
Note: According to the federal G-Invoicing specifications, only the UOMs that are published in the federal G-Invoicing Portal are accepted.
See: Defining Units of Measure, Oracle Inventory User's Guide.
Oracle CLM and Oracle Purchasing include a new lookup type, PO_IGT_UOM. You must enable either the IGT UOM Context attribute1 (if it is not being used for any other purpose) or add the UOM codes in the PO_IGT_UOM lookup type. The IGT requisition and order pages display these units of measure.
When you define a unit of measure in EBS, ensure that the value of the UOM field in EBS matches the UOM code in G-Invoicing, and the value of the UOM Name field in EBS matches the UOM Description in G-Invoicing.
For example, if the federal G-Invoicing application has the UOM code KG with the description kilogram, then in EBS you must enter KG in the UOM field and kilogram as the UOM name. If these values are not set correctly, then the pull process for seller facilitated orders (SFO) could fail.
Enter security certificate details and associate the system IDs that you received from the Treasury with the appropriate operating units. Do this on the G-Invoicing Options page.
See G-Invoicing Options for more information.
For more information about configuring keystore and truststore details and copying the Fiscal Service schema, refer to My Oracle Support Document 2600811.1, G-Invoicing Integration.
Conditional: Update line types.
If you are using Oracle CLM or Oracle Purchasing as a financial system and you pull approved orders to track obligations and performance, then you must set the default categories for goods and services line types. If the unit price is equal to $1 for all the schedules in an order line, then the lines are treated as amount-based lines. Otherwise, they are treated as goods-based lines. Based on the above condition, the system derives the first line type available that has an assigned category.
To set a default category for each line type, perform the following steps.
Select either the CLM Purchasing Super User or Purchasing US Federal responsibility.
Click Setup, then Purchasing, then Line Types.
Locate the Goods line type and click Update.
In the Update Line Type page, select a category and click Apply. The value specified in this page is used by default when an IGT order is created.
You can override the line type and category using the custom hook PO_IGTORD_CUSTOM.
Repeat Steps 3 and 4 for the Services line type.
Note: If the FOB point is Source or Origin, then two-way matching is used by default. If the FOB point is Destination or Other, then three-way matching is used.
The following tasks accomplish the actual exchange of data. Schedule concurrent programs to run regularly to maintain the flow of data.
Pull group definitions for requesting and servicing agency accounts from the federal G-Invoicing application by running the Intragovernmental Groups for Agency Interface Program. After you run this program, the application automatically runs another program to pull the TAS-BETCs.
See Pulling Organizational Groups and Data and Pulling TAS-BETCs for a Group for more information.
Pull GT&C data from the federal G-Invoicing application by running the Intragovernmental Agreements (GT&C) Interface Program. After you run this program, the application automatically runs another program to process the retrieved data and create the GT&Cs in EBS.
See: Pulling GT&Cs
Pull groups that are assigned to GT&Cs in the federal G-Invoicing application into Oracle EBS. When an agency user creates an IGT order and selects GT&Cs, only the groups and ALCs assigned to the selected GT&Cs are available.
Push order data from Oracle EBS to the federal G-Invoicing application by running the Intragovernmental Orders Interface Program.
See: Pushing or Pulling IGT Orders
Note: You do not need to schedule or run the PO IGT Order Generate & Push XML concurrent program manually. The PO IGT Order Generate & Push XML program generates the XML after the order is approved within the requesting agency.
Pull performance transactions into Oracle EBS.
Optionally, set up and maintain group security for IGT documents.
You can use the predefined securing attribute IGT_GROUP_ID to restrict a user's access only to documents for a specific group or groups. In the Users window, click the Securing Attributes tab, select the IGT_GROUP_ID attribute, and enter the group ID. You can grant a user access to multiple groups by associating the user with more than one group ID.
Note: You can get the group ID value from the federal G-Invoicing application or from a GT&C document.
See Organizational Groups in G-Invoicing and Oracle E-Business Suite for more information.
In the federal G-Invoicing application, administrators control access to intragovernmental transaction (IGT) documents by group assignment. Each user in the federal G-Invoicing application belongs to a group, and can only access IGT documents for that group. Documents with controlled access include GT&Cs, orders, and performance records, and attachments to those documents.
To push and pull IGT data to and from the federal G-Invoicing application, the group structures in your agency's system must mirror the group structures in the federal application. Oracle EBS accomplishes this through the association of a system ID with an agency and operating unit. See G-Invoicing Options for more information about this association.
After you pull group information (See Administering G-Invoicing and Pulling Organizational Groups and Data) the following information is available in Oracle EBS:
Groups for GT&Cs
Groups in agency accounts
TAS and BETCs details for groups
Oracle EBS uses operating units to control access to IGT documents in Oracle CLM, Oracle Purchasing, and Oracle Projects. Optionally, you can further restrict access at the user level by using the predefined IGT_GROUP_ID securing attribute to associate a user with a specific group or groups. If a user is not associated with a group, then the user can view IGT documents for all groups in the same operating unit.
Users at a requesting agency can view group information based on their security setup. The group information is available in the following locations:
GT&Cs tab: In the Controls region, the Requesting Group Information and Servicing Information regions display operational group names and agency location codes. When creating an IGT order, the user must select both requesting and servicing group details and ALC details.
IGT Orders: In the Headers subtab, the Requesting Group Information and Servicing Information regions display operational group names and agency location codes.
Access to Oracle G-Invoicing is set up using Role Based Access Control (RBAC).
The following roles, menus and functions control access to the G-Invoicing features.
Role Name | Role Code | Description |
---|---|---|
IGT Configuration Role | UMX|IGT_CONFIG | Allows the user to access and update the G-Invoicing Options, G-Invoicing Requisitions, and G-Invoicing Groups pages. |
IGT GTC Viewer Role | UMX|IGT_GTC_VIEWER | Allows the user to view GT&Cs in Oracle CLM and Oracle Purchasing. |
IGT Order Manager Role | UMX|IGT_ORDER_MANAGER | Allows the user to create, modify, and view orders in Oracle CLM and Oracle Purchasing. Allows the user to access the G-Invoicing Groups TAS/BETCs page. |
IGT Order Viewer Role | UMX|IGT_ORDER_VIEWER | Allows the user only to view orders. |
IGT Performance Manager Role | UMX|IGT_PERFORMANCE_MANGER | Allows the user to create and view performance transactions. |
Menu Name | Menu Code |
---|---|
PO IGT View GT&C Sub Tab | PO_IGT_GTNC_SUBTAB |
PO IGT Orders Sub Tab | PO_IGT_ORDERS_SUB_TAB |
PO IGT Order Modifications Sub Tab | PO_IGT_ORDER_MODS_SUB_TAB |
PO IGT Performance Sub Tab | PO_IGT_PERF_SUB_TAB |
PO Unprocessed IGT Request Sub Tab | PO_IGT_UNPRSSD_REQ_SUBTAB |
iProcurement: Non-Catalog Request IGT | ICXPOR_NONCATALOG_IGT |
User Function Name | Function Code |
---|---|
G-Invoicing Configuration Page | PO_IGT_CONFIG_FN |
PO GT&C Summary Page | PO_IGT_GTNC_SUMMARY |
PO GT&C Details Page | PO_IGT_GTNC_DTLS |
PO IGT Orders Summary Page | PO_IGT_ORDERS_SUMMARY |
PO IGT Order Modifications Summary Page | PO_IGT_ORDER_MOD_SUMMARY |
PO IGT Performance Summary Page | PO_IGT_PERF_SUMMARY |
PO IGT Performance View/Update Page | PO_IGT_PERF_VIEW_UPDATE |
iProcurement: Non-Catalog Page IGT | ICXPOR_NONCAT_PAGE_IGT |
PO IGT Notifications | PO_IGT_NOTIF |
Performance Notification | PO_IGT_PERF_NOTIF |
G-Invoicing Requests Page | PO_IGT_REQUESTS_FN |
G-Invoicing Groups Page | PO_IGT_GROUPSTREE_FN |
G-Invoicing TASBETC Page | PO_IGT_TASBETC_FN |
Permission Set Name | Permission Set Code |
---|---|
IGT Configuration Permission Set | IGT_CONFIG_PS |
PO IGT View GTC Permission Set | PO_IGT_VIEW_GTC_PS |
PO IGT Update Order Permission Set | PO_IGT_UPDATE_ORDER_PS |
PO IGT View Order Permission Set | PO_IGT_VIEW_ORDER_PS |
PO IGT Update Performance Permission Set | PO_IGT_UPDATE_PERFORMANCE_PS |
ICX Intragovernmental Request Permission Set | ICX_NONCAT_IGT_PS |
Grant Name | Permission Set Name | Access Role | Responsibility |
---|---|---|---|
IGT GTC Viewer Grant | PO IGT View GTC Permission Set | IGT GTC Viewer Role | CLM or Oracle Purchasing |
IGT Order Manager Grant | PO IGT Update Order Permission Set | IGT Order Manager Role | CLM or Oracle Purchasing |
IGT Order Viewer Grant | PO IGT View Order Permission Set | IGT Order Viewer Role | CLM or Oracle Purchasing |
IGT Configuration Grant | IGT Configuration Permission Set | IGT Configuration Role | CLM Purchasing Super User or Federal Purchasing |
IGT Performance Manager Grant | PO IGT Update Performance Permission Set | IGT Performance Manager Role | CLM Purchasing Super User or Federal Purchasing |
ICX: Intragovernmental Request Access Grant | ICX Intragovernmental Request Permission Set | ICX: Intragovernmental Request Access Role | iProcurement/CLM iProcurement |
Use the G-Invoicing Options page to add security certificate and schema details and to associate system IDs.
Prerequisites
You must complete the following steps before you add security certificate details:
Configure keystore and truststore details to integrate with the federal G-Invoicing application.
Copy the Fiscal Service schema to the Oracle E-Business Suite middle tier to enable REST services integration with the federal G-Invoicing application.
For more information, refer to My Oracle Support Document 2600811.1, G-Invoicing Integration.
To add security certificate details, perform the following steps:
From the home page, click the CLM Purchasing responsibility.
Click Setup, then Organizations, and then G-Invoicing Options.
In the Security Certificate Details region, enter a truststore path and a truststore password. The path is the location in which you store the certificate provided by US Treasury.
Enter a keystore path and a keystore password. The path is the location in which you store the certificate that you provide for verification.
In the Schema Details region, enter the order schema path. This is the location of the Order Schema XSD file.
Enter the performance schema path. This is the location of the Performance Schema XSD file.
Each federal agency has a system ID allocated to it. In Oracle EBS, agencies generally correlate with operating units. To ensure the accurate exchange of G-Invoicing data between Oracle EBS and the federal G-Invoicing application, you must associate each system ID with the appropriate agency and operating unit.
In the Associate System IDs region, select the agency type. If the requesting and servicing agencies share the same organization hierarchy and have the same system ID, then select Both. Otherwise, select Requesting Agency.
Select the operating unit to associate with the system ID.
Enter the system ID provided to you by the federal government.
In the Requesting Agency Order Creation and Approval list, select the initiation point or interface origin for your orders.
If you plan to create and approve intragovernmental orders in EBS, then select E-Business Suite. If you are using EBS as a financial system and the federal G-Invoicing application to create intragovernmental transactions, then select G-Invoicing. The default value is E-Business Suite.
You can switch the value from G-Invoicing to E-Business suite but not vice-versa. If you create a transaction using an operating unit and associate it to a system ID, then you cannot delete the row in the G-Invoicing Options page.
Note: It is recommended that you click save before proceeding when you are applying the latest consolidation patches.
Save your work.
To remove this mapping, click Delete. If you create a transaction in the operating unit associated with the system ID, then the delete option is disabled.
CLM provides a set of predefined attribute groups for G-Invoicing. The following sections describe the attributes in the groups and indicate whether they can be updated in modifications.
This list is a key to the values in the Updateable in Mod or Admin Mod column in the tables that follow.
Yes: The attribute can be updated for either a modification or an admin modification.
No: The attribute cannot be updated for either a modification or an admin modification.
Admin only: The attribute can be updated only for an admin modification.
Modification only: The attribute can be updated only for a modification, not for an admin modification.
Modification only, without performance: The attribute can be updated only for a modification for which no performance has been reported.
Admin only, without performance: The attribute can be updated only for an admin modification for which no performance has been reported.
Modification only, on approval: The attribute can be updated only for a modification. The funding and program approval attributes are finally updated when approval is complete.
Attribute Group Name: Header Information
Attribute Group Description: Header Information
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Operating Unit | OU Name | Required | LOV | Yes | No |
Agreement | This is the internal Requesting Agency tracking number for the agreement. | Required | Text | Yes | No |
GT&C Number | The unique agreement number that must be established between the Requesting Agency and Servicing Agency which will track each GT&C from the origination through the completion or termination. | Required | Text | Yes | No |
GT&C Title | The title of a given GT&C. | Optional | Text | Yes | No |
G-Invoicing Status | The current status of a GT&C. Appears on the GT&C Summary page. | Required | Text | Yes | No |
Agreement Start Date | The date when the agreement will begin. | Required | Date | Yes | No |
Agreement End Date | The date when the agreement will end and all Orders will be completed. | Required | Date | Yes | No |
Agreement Type | Identifies whether this GT&C will support one (SINGLE) or more than one (MULTIPLE) Orders (funding documents). | Required | Text | Yes | No |
Total Estimated Amount | Identifies Sum of Direct Cost Plus Overhead Fees & Charges. | Required | Number | Yes | No |
Termination Days | The number of days this IAA will take to terminate once written notice is given by either the Requesting Agency or Servicing Agency. | Optional | Number | Yes | No |
Attribute Group Name: Ordering Constraints
Attribute Group Description: Ordering Constraints
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Remaining Amount | Total Remaining Amount to Obligate. | Required | Number | Yes | No |
Enforce Total Remaining Amount Indicator | This indicator identifies whether Order(s) would be validated up against the GT&C and the Total Remaining Amount. | Required | Text | Yes | No |
Advance Payment Indicator | Identifies whether Advance Payments are allowed for the Orders supporting this GT&C. | Required | Boolean | Yes | No |
Assisted Acquisition Indicator | Identifies whether the GT&C will accommodate Assisted Acquisitions. The Servicing Agency provides acquisition support in awarding and managing contracts on behalf of the Requesting Agency's requirements for products or services. | Required | Boolean | Yes | No |
Order Originating Partner Indicator | Identifies the agency (requesting or servicing) that can initiate the order using this GT&C. | Yes | Text | Yes | No |
Attribute Group Name: Estimated Costs
Attribute Group Description: Estimated Costs
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Total Direct Cost Amount | Total agreed-upon direct cost for providing the products and/or services. | Optional | Number | Yes | No |
Total Overhead Fees & Charges Amount | The total agreed-upon overhead fees & charges for providing the products and/or services. | Optional | Number | Yes | No |
Explanation of Overhead Fees & Charges | A general explanation of how the overhead fees and charges are calculated. | Required | Text | Yes | No |
Attribute Group Name: Requesting Agency Information
Attribute Group Description: Requesting Agency Information
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Requesting Agency Identifier | This is the 3-digit Treasury-managed organizational ID of the Requesting Agency. | Required | Number | Yes | No |
Agency Location Code | Identifier for a federal agency buying goods, or services, or both. If this attribute contains more than one value, then this field displays all those attributes as comma separated values. | Required | Text | Yes | No |
Scope | Identify the high level scope of the work to be performed under this GT&C, for all related Orders, by the Servicing Agency. | Required | Text | Yes | No |
Roles | References the respective roles and responsibilities that the Requesting Agency must carry out to ensure the effective management and fulfillment of the IAA requirements. | Conditional | Text | Yes | No |
Assisted Acquisitions | The Requesting Agency lists or references the organizations (Offices, Bureaus, Divisions, etc.) that are authorized to request acquisition assistance for this IAA. | Conditional | Text | Yes | No |
Requesting Clauses | Identifies any additional Requesting Agency clause(s). | Optional | Text | Yes | No |
Restrictions | References the unique requirements and/or mission specific restrictions specific to this IAA. | Optional | Text | Yes | No |
Organizational Group Name | The group name provided in the GT&C is displayed here. | Yes | Text | Yes | No |
Document Inheritance Indicator | Identifies if all the child groups can use the GT&C created for the parent group. | Yes | Boolean | Yes | No |
Attribute Group Name: Servicing Agency Information
Attribute Group Description: Servicing Agency Information
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Agency Identifier | This is the 3-digit Treasury-managed organizational ID of the Servicing Agency. | Required | Number | Yes | No |
Agency Location Code | Identifier for a federal agency selling goods, or services, or both. If this attribute contains more than one value, then this field displays all those attributes as comma separated values. | Required | Text | Yes | No |
Agency Agreement Tracking Number | The internal Servicing Agency tracking number for the agreement. | Optional | Text | Yes | No |
Roles | References the respective roles and responsibilities that the Servicing Agency must carry out to ensure the effective management and fulfillment of the IAA requirements. | Conditional | Text | Yes | No |
Organizational Group Name | The group name provided in the GT&C is displayed here. | Yes | Text | Yes | No |
Document Inheritance Indicator | Identifies if all the child groups can use the GT&C created for the parent group. | Yes | Boolean | Yes | No |
Assisted Acquisitions | The Servicing Agency lists or references the organizations (Offices, Bureaus, Divisions, etc.) that are authorized to provide acquisition assistance for this IAA. | Conditional | Text | Yes | No |
Clauses | Identifies any additional Servicing Agency clause(s). | Optional | Text | Yes | No |
Attribute Group Name: Requesting Organization Structure
Attribute Group Description: Requesting Organization Structure
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Business Unit | One of three Requesting organization-based role access. | Optional | Text | Yes | No |
Cost Center | One of three Requesting organization-based role access. | Optional | Text | Yes | No |
Department Identifier | One of three Requesting organization-based role access. | Optional | Text | Yes | No |
Attribute Group Name: Servicing Organization Structure
Attribute Group Description: Servicing Organization Structure
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Business Unit | One of three Servicing organization-based role access | Optional | Text | Yes | No |
Cost Center | One of three Servicing organization-based role access. | Optional | Text | Yes | No |
Department Identifier | One of three Servicing organization-based role access. | Optional | Text | Yes | No |
Attribute Group Name: GT&C Attachments
Attribute Group Description: GT&C Attachments
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Name | The actual name of the attachment file. | Conditional | Text | Yes | No |
Alias | Descriptive name for an attachment. Different from the name assigned to the file itself. | Optional | Text | Yes | No |
Updated By | The user name or partner (Buyer or Seller) that uploaded the attachment. | Required | Text | Yes | No |
Date and Time | The time and date the file was uploaded into G-Invoicing. | Required | Date | Yes | No |
Name | The actual name of the attachment file. | Conditional | Text | Yes | No |
Alias | Descriptive name for an attachment. Different from the name assigned to the file itself. | Optional | Text | Yes | No |
Updated By | The user name or partner (Buyer or Seller) that uploaded the attachment. | Required | Text | Yes | No |
Date and Time | The time and date the file was uploaded into G-Invoicing. | Required | Date | Yes | No |
Buy or Sell Indicator | Indicator to differentiate requesting or servicing agency. | Required | Text | Yes | No |
Request ID | Request ID of the attachment file that was submitted to get the complete data of attachment. | Required | Number | Yes | No |
Attachment URL | Attachment URL of G-Invoicing portal. | Optional | Text | Yes | No |
Attachment ID | Attachment ID in G-Invoicing portal | Required | Number | Yes | No |
Status | Internal status to track attachment download status. | Required | Text | Yes | No |
Attribute Group Name: Approval Information
Attribute Group Description: Approval Information
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Name | The name of the Requesting Agency official who signed the GT&C. | Required | Text | Yes | No |
Title | The title of the Requesting Agency official who signed the GT&C. | Optional | Text | Yes | No |
Phone | The phone of the Requesting Agency official who signed the GT&C. | Required | Number | Yes | No |
Fax | The fax of the Requesting Agency official who signed the GT&C. | Required | Number | Yes | No |
The email of the Requesting Agency official who signed the GT&C. | Required | Text | Yes | No | |
Signed Date | The date the Requesting Agency official who signed the GT&C. | Required | Date | Yes | No |
Name | The name of the Requesting Agency official who signed the GT&C. | Required | Text | Yes | No |
Title | The title of the Requesting Agency official who signed the GT&C. | Optional | Text | Yes | No |
Phone | The phone of the Requesting Agency official who signed the GT&C. | Required | Number | Yes | No |
Fax | The fax of the Requesting Agency official who signed the GT&C. | Required | Number | Yes | No |
The email of the Requesting Agency official who signed the GT&C. | Required | Text | Yes | No | |
Signed Date | The date the Requesting Agency official who signed the GT&C. | Required | Date | Yes | No |
Name | The name of the Servicing Agency official who signed the GT&C. | Required | Text | Yes | No |
Title | The title of the Servicing Agency official who signed the GT&C. | Optional | Text | Yes | No |
Phone | The phone of the Servicing Agency who official signed the GT&C. | Required | Number | Yes | No |
Fax | The fax of the Servicing Agency official who signed the GT&C. | Required | Number | Yes | No |
The email of the Servicing Agency official who signed the GT&C. | Required | Text | Yes | No | |
Signed Date | The date the Servicing Agency official who signed the GT&C. | Required | Date | Yes | No |
Name | The name of the Servicing Agency official who signed the GT&C. | Required | Text | Yes | No |
Title | The title of the Servicing Agency official who signed the GT&C. | Optional | Text | Yes | No |
Phone | The phone of the Servicing Agency official who signed the GT&C. | Required | Number | Yes | No |
Fax | The fax of the Servicing Agency official who signed the GT&C. | Required | Number | Yes | No |
The email of the Servicing Agency official who signed the GT&C. | Required | Text | Yes | No | |
Signed Date | The date the Servicing Agency official who signed the GT&C. | Required | Date | Yes | No |
Attribute Group Name: Preparer Information
Attribute Group Description: Preparer Information
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Name | The name of the person who prepared the GT&C. | Required | Text | Yes | No |
Phone | The phone number of the person who prepared the GT&C. | Optional | Number | Yes | No |
The email of the person who prepared the GT&C. | Optional | Text | Yes | No |
Attribute Group Name: Closing Comments
Attribute Group Description: Closing Comments
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Closing Comments | Any comments associated with why the GT&C has been closed. | Optional | Text | Yes | No |
Attribute Group Name: Header Information
Attribute Group Description: Header Information
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Operating Unit | The operating Units as per MOAC access for the logged in user | Required | LOV | - | No |
GT&C | The unique agreement number that must be established between the Requesting Agency and Servicing Agency which will track each GT&C from the origination through the completion or termination. | Required | LOV | - | No |
Agreement | The IDV/Agreement number generated internally when GT&C is imported | Required | Display | Yes | No |
Order | This is the order number associated with the Requesting Agency's system. No specific syntax. Leverages the Component based syntax. | Required | Text | - | No |
Supplier | Supplier Name (full name) | Required | Display | Yes | No |
Supplier Site | Supplier Site Code | Required | Display | Yes | No |
Supplier Contact | Supplier Contact | Optional | LOV | - | No |
IGT Order | A unique number used to identify the order created from the General Terms and Conditions. | Required | Display | - | No |
Currency | Currency | Required | LOV | Yes | No |
Buyer | Buyer Name | Required | LOV | - | Modification |
Contracting Officer | Contracting Officer | Optional | LOV | - | Modification |
Award Administrator | Award Administrator | Optional | LOV | - | Modification |
Description | Comments associated with the Order. | Optional | Text | - | Admin only |
Performance Period Start Date | The date on which the performance will start. | Required | Date | - | Modification only, without performance |
Performance Period End Date | The date on which the performance will end. | Required | Date | - | Modification *Error: The performance period must fall within GT&C dates. |
Assisted Acquisitions Indicator | Identifies whether the document will accommodate Assisted Acquisitions. The Servicing Agency provides acquisition support in awarding and managing contracts on behalf of the Requesting Agency requirements for products or services. | Required | Enumeration | - | Modification only, without performance |
Total Advance Amount | The total of all Order line advance amounts. | - | Number | Yes | Not Applicable |
Total Net Order Amount | The total of all Order line Net Due Amounts | - | Number | Yes | Not Applicable |
Total Order Amount | Total Advance Amount plus Total Net Order Amount | - | Number | Yes | Not Applicable |
Order Acceptance Date | This is the date the order was accepted by the seller. | - | Date | Yes | Not Applicable |
Order Create Date | This is the date that the order was placed. | - | Date | Yes | Not Applicable |
Business Transaction Identifier | The Identifier for a business transaction. | - | Text | - | Not Applicable |
Order Modification Number | An identifier assigned to an order by the system when a modification is made to the original order record. | - | Number | - | Not Applicable |
Status | This code identifies the current status of the Order | - | Text | - | Not Applicable |
Attribute Group Name: Terms
Attribute Group Description: Terms
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Bill-To Location | Bill-To Location | Optional | LOV | - | Modification only |
Payment Terms | Payment Terms | Optional | LOV | - | Modification only |
Default Ship-to Location | Default Ship-to Location | Required | LOV | - | Modification only |
FOB | FOB | Optional | LOV | - | Modification only, without performance |
Attribute Group Name: Requesting Agency Information
Attribute Group Description: Requesting Agency Information
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Agency Location Code | Unique identifier Agency Location Code (ALC) for a federal agency buying goods and/or services. | Required | Text | Yes | Modification only, without performance |
Business Unit | One of three organization-based role access | Optional | Text | - | Modification only, without performance |
Cost Center | One of three organization-based role access | Optional | Text | - | Modification only, without performance |
Department ID | One of three organization-based role access | Optional | Text | - | Modification only, without performance |
Organizational Group Name | A unique and recognizable name for a organizational group. | Modification only, without performance | |||
Funding Office Code | The identification code for the office (or other organizational entity) that provided the requirement and the preponderance of the funds obligated by this transaction and contract action. This code is required for assisted acquisitions and supports requesting agency socioeconomic credit and post award reporting. | Modification only, without performance | |||
Funding Agency Code | The identification code for the agency that provided the requirement and the preponderance of the funds obligated by this transaction and contract action. This code is required for assisted acquisitions and supports requesting agency socioeconomic credit and post award reporting. | Modification only, without performance | |||
Unique Entity Identifier | A distinct number (UEI) or other identifier which is used to identify a specific commercial, nonprofit, or Government entity. | Modification only, without performance |
Attribute Group Name: Requesting Agency Authority
Attribute Group Description: Requesting Agency Authority
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Statutory Authority Fund Type Code | This identifies the authority that allows the Requesting Agency to purchase products and/or services from another Federal Agency. | Required | LOV | - | Modification only, without performance |
Statutory Authority Fund Type Title | This is the authority that allows the Requesting Agency to purchase products and/or services from another Federal Agency. | Optional | Text | - | Modification only, without performance |
Statutory Authority Fund Type Citation | This is the authority that allows the Requesting Agency to purchase products and/or services from another Federal Agency. | Optional | Text | - | Modification only, without performance |
Program Authority Title | This is the title associated with the authority that grants the Requesting Agency program authority | Optional | Text | - | Modification only, without performance |
Program Authority Citation | This is the citation associated with the authority that grants the Requesting Agency program authority | Optional | Text | - | Modification only, without performance |
Attribute Group Name: Servicing Agency Information
Attribute Group Description: Servicing Agency Information
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Agency Location Code | Unique identifier Agency Location Code (ALC) for a federal agency selling goods and/or services. | - | Text | Yes | Modification only, without performance |
Business Unit | One of three organization-based role access | - | Text | Yes | Modification only, without performance |
Cost Center | One of three organization-based role access | - | Text | Yes | |
Department ID | One of three organization-based role access | - | Text | Yes | Modification only, without performance |
Servicing Agency Order Number | This is the order number associated with the Servicing Agency's system. No specific syntax. Leverages the Component based syntax. | - | Text | Yes | No |
Organizational Group Name | A unique and recognizable name for a organizational group | Modification only, without performance | |||
Servicing Agency Comments | Comments associated with the order. | Admin only |
Attribute Group Name: Servicing Agency Authority
Attribute Group Description: Servicing Agency Authority
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Statutory Authority Fund Type Code | This identifies the authority that allows the Servicing Agency to provide products and/or services to another Federal agency. | - | Enumeration | Yes | Modification only, without performance |
Statutory Authority Fund Type Title | This is the authority that allows the Servicing Agency to provide products and/or services to another Federal agency. | - | Text | Yes | Modification only, without performance |
Statutory Authority Fund Type Citation | This is the authority that allows the Servicing Agency to provide products and/or services to another Federal agency. | - | Text | Yes | Modification only, without performance |
Program Authority Title | This is the title associated with the authority that grants the Servicing Agency program authority | - | Text | Yes | Modification only, without performance |
Program Authority Citation | This is the citation associated with the authority that grants the Servicing Agency program authority | - | Text | Yes | Modification only, without performance |
Attribute Group Name: Advance Information
Attribute Group Description: Advance Information
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Advance Revenue Recognition Methodology | Identification of the methodology used to account for the Requesting Agency's expense and the Servicing Agency's revenue. | - | Enumeration | Yes | Modification only, without performance |
Advance Revenue Recognition Description | When the Advance Revenue Recognition is other than Straight One, Accrual Per Work or Monthly, this field identifies the specific frequency. | - | Text | Yes | Modification only, without performance |
Servicing Agency's Advance Payment Authority Title | For agreements with Advance Payment allowed, free-form text stating the Servicing Agency's specific authority that allows advances | - | Text | Yes | Modification only, without performance |
Servicing Agency's Advance Payment Authority Citation | For agreements with Advance Payment allowed, free-form text stating the Servicing Agency's specific authority that allows advances | - | Text | Yes | Modification only, without performance |
Attribute Group Name: Billing Information
Attribute Group Description: Billing Information
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
CPIC Screening Indicator | Identifies whether the Information Technology (IT) goods or services have been screened to ensure compliance with CPIC (Capital Planning and Investment Control) requirements. | Optional | Enumeration | - | Admin only |
Priority Order Indicator | Identifies whether the Order is a high priority. | Optional | Enumeration | - | Admin only |
Billing Frequency | The frequency of an occurrence for an item e.g. collection, bill, invoice. | - | Enumeration | Yes | Modification only, without performance |
Billing Frequency other explanation | If "Other" is selected as the Billing Frequency, the user must add a free form text briefly explaining the Billing Frequency. | - | Text | Yes | Modification only, without performance |
Attribute Group Name: Delivery Information
Attribute Group Description: Delivery Information
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
FOB Point | Specifies at what point the seller transfers ownership of the goods to the buyer. | Required | Enumeration | - | Modification only, without performance |
Acceptance Point | This field identifies whether the acceptance point is Origin or Destination. | Optional | Enumeration | - | Modification only, without performance |
Inspection Point | This field identifies whether the inspection point is Origin or Destination. | Optional | Enumeration | - | Modification only, without performance |
Constructive Receipt Days | The number of elapsed days before requesting agency receipt is assumed to occur. | Conditional | Number | - | Modification only, without performance |
Place of Acceptance | This is the location at which the goods or services will be accepted | Optional | Text | - | Modification only, without performance |
Place of Inspection | This is the location at which the goods or services will be inspected | Optional | Text | - | Modification only, without performance |
Attribute Group Name: Preparer and Approvals Information
Attribute Group Description: Preparer and Approvals Information
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Requesting Agency Prepared Name | The name of the person who prepared the Order | Required | Text | - | Modification only |
Requesting Agency Prepared Phone | The phone number of the person who prepared the Order | Optional | Number | - | Modification only |
Requesting Agency Prepared Email | The email of the person who prepared the Order | Optional | Text | - | Modification only |
Requesting Agency POC Name | Enter the name of any additional POC, as determined by each agency | Required | Text | - | Admin only |
Requesting Agency POC Telephone Number | Enter the telephone number(s) of any additional POC, as determined by each agency | Optional | Number | - | Admin only |
Requesting Agency POC Email Address | Enter the email address any additional POC, as determined by each agency | Optional | Text | - | Admin only |
Requesting Agency POC Fax Number | Enter the fax number of the POC, as determined by each agency | Optional | Text | - | Admin only |
Requesting Agency Funding Official Title | Enter the title of the Funding Official. | Required | Text | - | Modification only, on approval |
Requesting Agency Funding Official Name | Enter the name of the Funding Official. | Required | Text | - | Modification only, on approval |
Requesting Agency Funding Official Telephone Number | Enter the telephone number(s) of the Funding Official. | Optional | Number | - | Modification only, on approval |
Requesting Agency Funding Official Email Address | Enter the email address for the Funding Official. | Optional | Text | - | Modification only, on approval |
Requesting Agency Funding Official Fax Number | Enter the fax number of the Funding Official. | Optional | Text | - | Modification only, on approval |
Requesting Agency Funding Official Date Signed | The Order becomes effective on the date it is signed by both the Requesting Agency and Servicing Agency Officials. | - | Date | Yes | Modification only, on approval |
Requesting Agency Program Official Title | Enter the title of the Program Official. | Required | Text | - | Modification only, on approval |
Requesting Agency Program Official Name | Enter the name of the Program Official. | Required | Text | - | Modification only, on approval |
Requesting Agency Program Official Telephone Number | Enter the telephone number(s) of the Program Official. | Optional | Number | - | Modification only, on approval |
Requesting Agency Program Official Email Address | Enter the email address for the Program Official. | Optional | Text | - | Modification only, on approval |
Requesting Agency Program Official Fax Number | Enter the fax number for the Program Official. | Optional | Text | - | Modification only, on approval |
Requesting Agency Program Official Date Signed | The Order becomes effective on the date it is signed by both the Requesting Agency and Servicing Agency Officials. | - | Date | Yes | Modification only, on approval |
Servicing Agency Prepared Name | The name of the person who prepared the Order | - | Text | Yes | Modification only |
Servicing Agency Prepared Phone | The phone number of the person who prepared the Order | - | Number | Yes | Modification only |
Servicing Agency Prepared Email | The email of the person who prepared the Order | - | Text | Yes | Modification only |
Servicing Agency POC Name | Enter the name of any additional POC, as determined by each agency | - | Text | Yes | Admin only |
Servicing Agency POC Telephone Number | Enter the telephone number(s) of any additional POC, as determined by each agency | - | Number | Yes | Admin only |
Servicing Agency POC Email Address | Enter the email address any additional POC, as determined by each agency | - | Text | Yes | Admin only |
Servicing Agency POC Fax Number | Enter the fax number of the POC, as determined by each agency | - | Text | Yes | Admin only |
Servicing Agency Funding Official Title | Enter the title of the Funding Official. | - | Text | Yes | Modification only, on approval |
Servicing Agency Funding Official Name | Enter the name of the Funding Official. | - | Text | Yes | Modification only, on approval |
Servicing Agency Funding Official Telephone Number | Enter the telephone number(s) of the Funding Official. | - | Number | Yes | Modification only, on approval |
Servicing Agency Funding Official Email Address | Enter the email address for the Funding Official. | - | Text | Yes | Modification only, on approval |
Servicing Agency Funding Official Fax Number | Enter the fax number for the Funding Official. | - | Text | Yes | Modification only, on approval |
Servicing Agency Funding Official Date Signed | The Order becomes effective on the date it is signed by both the Requesting Agency and Servicing Agency Officials. | - | Date | Yes | Modification only, on approval |
Servicing Agency Program Official Title | Enter the title of the Program Official. | - | Text | Yes | Modification only, on approval |
Servicing Agency Program Official Name | Enter the name of the Program Official. | - | Text | Yes | Modification only, on approval |
Servicing Agency Program Official Telephone Number | Enter the telephone number(s) of the Program Official. | - | Number | Yes | Modification only, on approval |
Servicing Agency Program Official Email Address | Enter the email address for the Program Official. | - | Text | Yes | Modification only, on approval |
Servicing Agency Program Official Fax Number | Enter the fax number for the Program Official. | - | Text | Yes | Modification only, on approval |
Servicing Agency Program Official Date Signed | The Order becomes effective on the date it is signed by both the Requesting Agency and Servicing Agency Officials. | - | Date | Yes | Modification only, on approval |
Attribute Group Name: Action History
Attribute Group Description: Action History
Applicable To: Header
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Rejection Reason | Comments associated with why the document was rejected. | - | Text | Yes | Modification only |
Close Comments | Comments associated with why the Order was closed or voided. | - | Text | Yes | Modification only |
Attribute Group Name: IGT Order Attachments
Attribute Group Description: IGT Order Attachments
Applicable To: Header and Attachments
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Buy or Sell Indicator | Designates whether the Order or Attachment originated from the Requesting or Servicing agency. | Optional | Enumeration | - | Not Applicable |
Request ID | Request ID of the attachment file that was submitted to get the complete data of attachment | - | Number | Yes | Not Applicable |
Attachment URL | Attachment URL of G-Invoicing portal | - | Text | Yes | Not Applicable |
Attachment ID | Attachment ID in G-Invoicing portal | - | Number | Yes | Not Applicable |
Status | Internal status to track attachment download status | - | Text | Yes | Not Applicable |
Attribute Group Name: Line Information
Attribute Group Description: Line Information
Applicable To: Line
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Line Number | Unique identifier for each line on the Order. | - | Number | Yes | No |
Item Description | This is the basic description of the item between exchanged. | Required | Text | - | Modification only, without performance |
Quantity | The total number of units of the corresponding schedules. | Required | Number | - | No |
Amount | The total price is the quantity x unit price. | - | Number | Yes | No |
Advance Amount | The total amount of the advance for this Order line, summed by adding Schedule Amount(s) where Advance Payment Indicator is True. | - | Number | Yes | No |
Net Due Amount | Total line costs minus advances (if any). | - | Number | Yes | No |
Status | Identifies whether the PO Line is still active or cancelled. | - | Enumeration | Yes | Modification only, without performance |
Unit of Measure | For Reimbursable Agreements, enter the unit of measure for each Order Line, if applicable. | Required | LOV | - | No |
Unit of Measure Description | The basic description of the unit of measure being exchanged. | - | Text | Yes | No |
Attribute Group Name: Additional Item Information
Attribute Group Description: Additional Item Information
Applicable To: Line
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Capitalized Asset Indicator | Specifies when the Seller considers the line item to be a capitalized asset (True). Otherwise False. | - | Enumeration | Yes | Modification only, without performance |
FSC or PSC Code | This is the Product Service Code/Federal Supply Code for the item or service associated with the order. | Required | Text | - | Modification only, without performance |
UID Required Identifier | Specifies whether or not the item requires a unique item identifier (UII) marking. | Required | LOV | - | Modification only, without performance |
Product or Service Identifier | This is the National Stock Number (NSN) or other pertinent information associated with the Order Line. | Conditional | Text | - | Modification only, without performance |
Severable Nonseverable Code | Severable Service, Non-severable Service, Not Applicable | Required | LOV | - | Modification only, without performance |
Attribute Group Name: Schedule Information
Attribute Group Description: Schedule Information
Applicable To: Schedule
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Schedule Number | The sequential sub-line structure below a Order Line. It contains the detailed financial information and shipping information. | - | Number | Yes | No |
Quantity | The total number of units for this schedule. | Required | Number | - | Modification with validation error: Quantity cannot be lower than performed quantity |
Unit Price | The cost of each unit for this schedule | Required | Number | - | Modification only, without performance |
Currency | The currency LOV for the price | - | Number | Yes | No |
Amount | The quantity x unit price for this schedule | - | Number | Yes | No |
Advance Payment Indicator | Controls whether the Schedule allows advances (true) or not (false). | Required | Enumeration | - | Modification only, without performance |
Status | This is the current status of a given Schedule Line. Permitted values: A (Active), C (Cancelled) | - | Enumeration | Yes | Modification only, without performance |
Attribute Group Name: Shipping Information
Attribute Group Description: Shipping Information
Applicable To: Schedule
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Address Identifier | A code that identifies the end point of the shipment or the location the service is being performed. | Optional | Text | - | Modification only, without performance |
Agency Title | The name of the Agency at the ship to location. | Optional | Text | - | Modification only, without performance |
Location Description | The Description of the Ship to Location. | Optional | Text | - | Modification only, without performance |
Address 1 | 1st address line associated with shipment | Optional | Text | - | Modification only, without performance |
Address 2 | 2nd address line associated with shipment | Optional | Text | - | Modification only, without performance |
Address 3 | 3rd address line associated with shipment | Optional | Text | - | Modification only, without performance |
City | The name of the city. | Optional | Text | - | Modification only, without performance |
Postal Code | The 10-digit (ZIP) code that geographically identifies individual Post Offices or metropolitan area delivery stations associated with every mailing address. | Optional | Text | - | Modification only, without performance |
State | The name of the state. | Optional | Text | - | Modification only, without performance |
Country | A code that identifies a country. | Optional | Text | - | Modification only, without performance |
Special Shipping Information | Optional text field to include additional Shipping Information for the Delivery of Products. Enter specific information for shipping, shipping company, date/time, special instructions, etc. | Optional | Text | - | Modification only, without performance |
Delivery POC Title | Optional text field to include the Point of Contact Title for additional Shipping Information on the Delivery of Products. | Optional | Text | - | Admin only, without performance |
Delivery POC Name | Optional text field to include the Point of Contact Name for additional Shipping Information on the Delivery of Products. | Optional | Text | - | Admin only, without performance |
Delivery POC Phone | Optional text field to include the Point of Contact Name and Title for additional Shipping Information on the Delivery of Products. | Optional | Text | - | Admin only, without performance |
Delivery POC Email | Optional text field to include the Point of Contact E-mail Address and Title for additional Shipping Information on the Delivery of Products. | Optional | Text | - | Admin only, without performance |
Attribute Group Name: Requesting Agency Funding Information
Attribute Group Description: Requesting Agency Funding Information
Applicable To: Schedule
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
TAS - SP | Sub Class of the Requesting Agency. Programmatic breakdown of the account for Treasury publication purposes. | - | Number | Yes | Modification only, without performance |
TAS - AID | The Treasury Account Symbol (TAS) component that identifies the department, agency or establishment of the U.S. Government that is responsible for the TAS. Agency Identifier is also used apart from the TAS to identify a major department or independent agency of the Federal government. | - | Number | Yes | Modification only, without performance |
TAS - EPOA | Ending Period of Availability (Fiscal Year) of the Requesting Agency. In annual and multiyear funds, identifies the last year of availability under law that an appropriation account may incur new obligations. | - | Number | Yes | Modification only, without performance |
TAS - MAIN | MAIN Account of the Requesting Agency. Identifies an available receipt of other Treasury defined subdivision of the MAIN Account Code. | - | Number | Yes | Modification only, without performance |
TAS - ATA | Department Transfer of the Requesting Agency. Agency identifier of the agency receiving funds through an allocation transfer. | - | Number | Yes | Modification only, without performance |
TAS - BPOA | The Treasury Account Symbol (TAS) component that identifies the first year of availability under law that an account may incur new obligations, in annual and multiyear accounts. | - | Number | Yes | Modification only, without performance |
TAS - SUB | The Treasury Account Symbol (TAS) component that identifies an available receipt or other Treasury-defined subdivision of the main account. | - | Number | Yes | Modification only, without performance |
Bona Fide Need | Sufficient information to describe and support the transaction. | Required | Text | - | Modification only, without performance |
Attribute Group Name: Requesting Agency Accounting Information
Attribute Group Description: Requesting Agency Accounting Information
Applicable To: Schedule
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Project Identifier | A planned undertaking of work to be performed or product to be produced having a finite beginning and end. | Optional | Text | - | Admin only, without performance |
Attribute Group Name: Additional Information
Attribute Group Description: Additional Information
Applicable To: Schedule
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Trading Partner BETC | BETC field used to identify the type of event that is recorded against a Treasury Account Symbol and to implement CARS business rules for the posting of events to the TAS. Required for ALCs designated as CARS Reporters. | Required | Text | - | No |
Attribute Group Name: Servicing Agency Funding Information
Attribute Group Description: Servicing Agency Funding Information
Applicable To: Schedule
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
TAS - SP | Sub Class of the Servicing Agency. Programmatic breakdown of the account for Treasury publication purposes. | - | Number | Yes | No |
TAS - ATA | Department Transfer of the Servicing Agency. Agency identifier of the agency receiving funds through an allocation transfer. | - | Number | Yes | No |
TAS - AID | The Treasury Account Symbol (TAS) component that identifies the department, agency or establishment of the U.S. Government that is responsible for the TAS. Agency Identifier is also used apart from the TAS to identify a major department or independent agency of the Federal government. | - | Number | Yes | No |
TAS - BPOA | The Treasury Account Symbol (TAS) component that identifies the first year of availability under law that an account may incur new obligations, in annual and multiyear accounts. | - | Number | Yes | No |
TAS - EPOA | Ending Period of Availability (Fiscal Year) of the Servicing Agency. In annual and multiyear funds, identifies the last year of availability under law that an appropriation account may incur new obligations. | - | Number | Yes | No |
TAS - A | Availability Type of the Servicing Agency. Identifies no-year accounts "X", clearing/suspense accounts "F", Treasury's central summary general ledger accounts "A" and merged-surplus accounts "M." | - | Enumeration | Yes | No |
TAS - MAIN | MAIN Account of the Servicing Agency. Identifies an available receipt of other Treasury defined subdivision of the MAIN Account Code. | - | Number | Yes | No |
TAS - SUB | The Treasury Account Symbol (TAS) component that identifies an available receipt or other Treasury-defined subdivision of the main account. | - | Number | Yes | No |
Additional Accounting Classification | Details additional accounting information used by the Agencies for internal tracking. | - | Text | Yes | No |
Additional Information | Any additional information not covered in other areas | - | Text | Yes | No |
Business Partner Network Plus 4 Number | Optional Field. BPN + 4 is the standard name for this data element, however, this may be a trading partner's DUNS + 4 or the Department of Defense Activity Address Code (DoDAAC) + 4. | - | Number | Yes | No |
Disbursing Identifier Code | The Agency Disbursing Identifier is assigned to each disbursing office by the Treasury Department. The Agency Disbursing Identifier is an identification number that indicates authority to receive and disburse public funds and issue checks on the United States Treasury. | - | Text | Yes | No |
Object Class Code | Optional field for additional accounting information. | - | Text | Yes | No |
Attribute Group Name: Servicing Agency Accounting Information
Attribute Group Description: Servicing Agency Accounting Information
Applicable To: Schedule
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Accounting Classification Reference Identifier | ACRN is the number associated with the Seller's line of Accounting/Accounting Classification | - | Text | Yes | - |
Accounting Identifier | The Agency Accounting Identifier Code identifies the accounting system responsible for recording the accounting event. The Agency Accounting Identifier Code is intended to be an accounting system identifier, and therefore must be assigned to only one accounting system. | - | Text | Yes | - |
Activity Address Code | The Activity Address Code (AAC) used for shipping location. | - | Text | Yes | - |
Activity Identifier | An Activity is a series of events, tasks, or units of work that are linked to perform a specific objective. | - | Text | Yes | - |
Budget Fiscal Year | The budget or financial year, as opposed to a calendar year. The U.S. Government's fiscal year runs from October 1 of the prior year through September 30 of the next year. For example, FY 2015 was from October 2014 through September 2015. | - | Text | Yes | - |
Budget Line Item | Identifies further subdivisions of the Treasury Account Fund Symbol appropriation, below the Budget Sub Activity Level. | - | Text | Yes | - |
Cost Center Identifier | A Cost Center is a clearly defined responsibility area where costs are incurred. | - | Text | Yes | - |
Project Identifier | A planned undertaking of work to be performed or product to be produced having a finite beginning and end. | - | Text | Yes | - |
Cost Element | Cost Element is a classification of an organization's revenues, expenses or consumable resources. Cost Element Code only relates to primary cost. Cost Element Code does not relate to secondary cost which is identified as agency specific and not enterprise-level. | - | Text | Yes | - |
Federal Award Identification Number | The Federal Award Identification Number (FAIN) is a unique number assigned to a financial assistance award by the awarding agency. This number will identify the award in several systems including: ASAP.gov, USASpending.gov, and Grants.gov. This number along with the CFDS will allow for more precise tracking of grant obligations and payments. | - | Text | Yes | - |
Functional Area | Functional Area is a logical division of a Component's business operations. It represents the Functions the Component performs. | - | Text | Yes | - |
Funding Center Identifier | Funding Center is a clearly defined responsibility area within an organizational unit to which budget authority is assigned. | - | Text | Yes | - |
Security Cooperation Case Designator | Security Cooperation Case Designator is used to reflect an FMS contractual sales agreement (Letter of Offer and Acceptance) between the U.S. and an eligible foreign country. | - | Text | Yes | - |
Security Cooperation | Security Cooperation Customer represents the country receiving the product and/or service. | - | Text | Yes | - |
Security Cooperation Case Line Item Identifier | The Security Cooperation Case Line Item Identifier is used to identify a detailed line item requirement contained within the (Letter of Offer and Acceptance). | - | Text | Yes | - |
Security Cooperation Implementing Agency | Security Cooperation Implementing Agency Code: A single character alpha code which identifies the US Military Department or Agency which has negotiated or facilitated a foreign military sales case on behalf of the US Government. The majority of FMS cases are implemented by the Army (IA Code B), Navy (IA Code P) or Air Force (IA Code D) | - | Text | Yes | - |
Sub Allocation | Sub-Allocation Holder Identifies an organization to which funds have been Sub-Allocated. | - | Text | Yes | - |
Unique Record Identifier | An agency defined identifier that (when provided) is unique for every reported action. | - | Text | Yes | - |
Work Order Number | Identifies an individual unit of work, batch, or lot of a distinct product or service. | - | Text | Yes | - |
Parent Award Identifier | The identifier of the procurement award under which the specific award is issued (such as a Federal Supply Schedule). Term currently applies to procurement actions only. | - | Text | Yes | - |
Procurement Instrument Identifier | The unique identifier for each contract, agreement or order. | - | Text | Yes | - |
Attribute Group Name: Billing
Attribute Group Description: Billing
Applicable To: Distribution
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
ACRN | ACRN is the number associated with the Buyer's line of Accounting/Accounting Classification | Required | Text | - | Admin only, without performance |
Attribute Group Name: Additional Information
Attribute Group Description: Additional Information
Applicable To: Distribution
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
BETC | BETC field used to identify the type of event that is recorded against a Treasury Account Symbol and to implement CARS business rules for the posting of events to the TAS. Required for ALCs designated as CARS Reporters. | Required | Text | - | No |
Attribute Group Name: Requesting Agency Funding Information
Attribute Group Description: Requesting Agency Funding Information
Applicable To: Distribution
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
TAS - A | Availability Type of the Requesting Agency. Identifies no-year accounts X, clearing/suspense accounts F, Treasury's central summary general ledger accounts A and merged-surplus accounts M. | - | Enumeration | Yes | Modification only, without performance |
Additional Accounting Classification | Details additional accounting information used by the Agencies for internal tracking. | Optional | Text | - | Admin only, without performance |
Additional Information | Any additional information not covered in other areas | Optional | Text | - | Admin only, without performance |
Business Partner Network Plus 4 Number | Optional Field. BPN + 4 is the standard name for this data element, however, this may be a trading partner's DUNS + 4 or the Department of Defense Activity Address Code (DoDAAC) + 4. | Optional | Number | - | - |
Disbursing Identifier Code | The Agency Disbursing Identifier is assigned to each disbursing office by the Treasury Department. The Agency Disbursing Identifier is an identification number that indicates authority to receive and disburse public funds and issue checks on the United States Treasury. | Optional | Text | - | Admin only, without performance |
Object Class Code | Optional field for additional accounting information. | Optional | Text | - | Admin only, without performance |
Attribute Group Name: Requesting Agency Accounting Information
Attribute Group Description: Requesting Agency Accounting Information
Applicable To: Distribution
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Agency Accounting Identifier | The Agency Accounting Identifier Code identifies the accounting system responsible for recording the accounting event. The Agency Accounting Identifier Code is intended to be an accounting system identifier, and therefore must be assigned to only one accounting system. | Optional | Text | - | Admin only, without performance |
Activity Address Code | The Activity Address Code (AAC) used for shipping location. | Optional | Text | - | Admin only, without performance |
Activity Identifier | An Activity is a series of events, tasks, or units of work that are linked to perform a specific objective. | Optional | Text | - | Admin only, without performance |
Fiscal Year | The budget or financial year, as opposed to a calendar year. The U.S. Government's fiscal year runs from October 1 of the prior year through September 30 of the next year. For example, fiscal year 2015 was from October 2014 through September 2015. | Optional | Text | - | Admin only, without performance |
Budget Line Item | Identifies further sub-divisions of the Treasury Account Fund Symbol appropriation, below the Budget Sub Activity Level. | Optional | Text | - | Admin only, without performance |
Cost Center Identifier | A Cost Center is a clearly defined responsibility area where costs are incurred. | Optional | Text | - | Admin only, without performance |
Cost Element Code | Cost Element is a classification of an organization's revenues, expenses or consumable resources. Cost Element Code only relates to primary cost. Cost Element Code does not relate to secondary cost which is identified as agency specific and not enterprise-level. | Optional | Text | - | Admin only, without performance |
Federal Award Identification Number | The Federal Award Identification Number (FAIN) is a unique number assigned to a financial assistance award by the awarding agency. This number will identify the award in several systems including: ASAP.gov, USASpending.gov, and Grants.gov. This number along with the CFDS will allow for more precise tracking of grant obligations and payments. | Optional | Text | - | Admin only, without performance |
Functional Area | Functional Area is a logical division of a Component's business operations. It represents the Functions the Component performs. | Optional | Text | - | Admin only, without performance |
Funding Center Identifier | Funding Center is a clearly defined responsibility area within an organizational unit to which budget authority is assigned. | Optional | Text | - | Admin only, without performance |
Reimbursable Flag Indicator | The Reimbursable Indicator is used to flag those expenditures incurred for a designated TAFS account that are considered reimbursable to the account. | Optional | LOV | - | Admin only, without performance |
Security Cooperation Case Designator | Security Cooperation Case Designator is used to reflect an FMS contractual sales agreement (Letter of Offer and Acceptance) between the U.S. and an eligible foreign country. | Optional | Text | - | Admin only, without performance |
Security Cooperation | Security Cooperation Customer represents the country receiving the product and/or service in the FMS transaction. | Optional | Text | - | Admin only, without performance |
Security Cooperation Case Line Item Identifier | The Security Cooperation Case Line Item Identifier is used to identify a detailed line item requirement contained within the (Letter of Offer and Acceptance). | Optional | Text | - | Admin only, without performance |
Security Cooperation Implementing Agency | Security Cooperation Implementing Agency Code: A single character alpha code which identifies the US Military Department or Agency which has negotiated or facilitated a foreign military sales case on behalf of the US Government. The majority of FMS cases are implemented by the Army (IA Code B), Navy (IA Code P) or Air Force (IA Code D) | Optional | Text | - | Admin only, without performance |
Sub Allocation | Sub-Allocation Holder Identifies an organization to which funds have been Sub-Allocated. | Optional | Text | - | Admin only, without performance |
Unique Record Identifier | An agency defined identifier that (when provided) is unique for every reported action. | Optional | Text | - | Admin only, without performance |
Work Order Number | Identifies an individual unit of work, batch, or lot of a distinct product or service. | Optional | Text | - | Admin only, without performance |
Parent Award Identifier | The identifier of the procurement award under which the specific award is issued (such as a Federal Supply Schedule). Term currently applies to procurement actions only. | Optional | Text | - | Admin only, without performance |
Procurement Instrument Identifier | The unique identifier for each contract, agreement or order. | Optional | Text | - | Admin only, without performance |
Attribute Group Name: Servicing Agency Accounting Information
Attribute Group Description: Servicing Agency Accounting Information
Applicable To: Distribution
Attribute | Attribute Description | Required Field | Displayed As | Display Only | Updateable in Mod or Admin Mod |
---|---|---|---|---|---|
Reimbursable Flag Indicator | The Reimbursable Indicator is used to flag those expenditures incurred for a designated TAFS account that are considered reimbursable to the account. | - | LOV | Yes | - |
To pull group definitions from the federal G-Invoicing application into Oracle EBS, run the Intragovernmental Groups for Agency Interface Program.
If you are in a different responsibility, switch to CLM Purchasing Super User.
On the home page, click Reports and then Schedule Requests.
The Schedule Request: Define page appears.
Select New Request.
In the Program Name field, enter Intragovernmental Groups for Agency Interface Program.
In the Parameters tab, enter the following details:
Agency Type: Select Requesting Agency.
Operating Unit: Select the operating unit for which you want to pull the group information.
Submit the concurrent request.
Note: Schedule this program to run as often as needed to keep the G-Invoicing data current.
When you run this program, the application automatically runs the Intragovernmental TAS-BETCs for Group Interface Program.
See Pulling TAS-BETCs Details for a Group for more information.
Normally, you do not need to perform this task because when you run the Intragovernmental Groups for Agency Interface Program, the application automatically runs the Intragovernmental TAS-BETCs for Group Interface Program to pull TAS-BETC details. However, if you encounter errors, then you can run this program manually.
If you are in a different responsibility, switch to CLM Purchasing Super User.
On the home page, click Reports and then click Schedule Requests. The Schedule Request: Define page appears.
Click New Request.
In the Program Name field, enter Intragovernmental TAS-BETCs for Group Interface Program.
In the Parameters tab, enter the following details:
Agency Type: Select Requesting Agency.
Operating Unit: Select the operating unit for which to pull TAS-BETCs details.
Group Name: Select the name of the group for which to pull TAS-BETCs details.
Submit the concurrent request.
Note: Schedule this program to run as often as required to keep the G-Invoicing data current.
After you pull TAS-BETC details, you can view the details for a specific group. Select the CLM Purchasing Super User or the Purchasing, US Federal responsibility. Click Setup, then Organizations, then G-Invoicing Groups TAS/BETCs, and search for a group.
When you pull GT&Cs, the program returns a list of GT&Cs and attachments, for which Oracle EBS then pulls the XML data and stores it locally.
Note: Oracle EBS pulls GT&C data based on the parameters available in the concurrent program.
If GT&Cs are subsequently modified then Oracle EBS pulls the data again, based on the last-modified date, to synchronize with previously created GT&Cs. Schedule the concurrent program to run regularly to keep the data current.
To pull GT&C data from the federal G-Invoicing application to Oracle EBS, run the Intragovernmental Agreements (GT&C) Interface Program
If you are in a different responsibility, switch to CLM Purchasing Super User.
On the home page, click Reports and then click Schedule Requests. The Schedule Request: Define page appears.
Click New Request.
In the Program Name field, enter Intragovernmental Agreements (GT&C) Interface Program.
In the Parameters tab, enter the following details:
Agency Type: Select Requesting Agency.
Request Mode: Keep the default value, which is Pull.
Request Type: Select Get GT&C List.
Operating Unit: Select the operating unit for which to pull GT&C data.
Agency Location Code: Optional. Specify an ALC for which to retrieve GT&Cs.
If you do not specify an ALC, then the application retrieves the data for all ALC codes mapped to the specified OU.
Document Number: Optional. Enter a GT&C number (from the federal G-Invoicing application) to retrieve GT&Cs for that document.
If you leave this field blank, then the application retrieves GT&Cs for all documents that are in the status that you select in the Document Status field.
Document Status: Select Closed or Open for Orders. The program retrieves data for GT&Cs in the selected status.
Process Error Documents: The default value is No. Select Yes to process error logs. If you select Yes and specify a GT&C number, then only that document is processed. If you do not specify a GT&C number, then all GT&Cs with errors are processed.
Submit the concurrent request.
Note: After you run the Intragovernmental Agreements (GT&C) Interface Program to retrieve GT&C data, the Intragovernmental Agreements (GT&C) Import Program runs automatically to process retrieved data and creates the GT&Cs in Oracle EBS. You do not need to submit a request to run the import program unless the first run ends with errors. In that case, correct the errors and then run the import program again with the Process Error Documents parameter set to Yes.
The requesting administrator receives a notification when this concurrent program has run. The notification contains a list of GT&Cs that were created or modified or that ended with errors. The administrator can review the errors and take appropriate action.
Note: Schedule this program to run as often as required to keep the G-Invoicing data current.
After you pull GT&Cs from the federal G-Invoicing application, you must pull information about the groups associated with each GT&C.
To pull groups for GT&Cs in Oracle EBS, run the Intragovernmental Groups for GT&C Interface Program
If you are in a different responsibility, switch to CLM Purchasing Super User.
On the home page, click Reports and then click Schedule Requests. The Schedule Request: Define page appears.
Select New Request.
In the Program Name field, enter Intragovernmental Groups for GT&C Interface Program.
In the Parameters tab, enter the following details:
Agency Type: Select Requesting Agency.
Operating Unit: Select the operating unit for which to pull GT&C data.
GTC Number: To pull group information for a specific GT&C, enter the GT&C number.
If you do not enter a number, then the application processes all the pending requests while pulling GT&Cs and GT&C modifications.
See Pulling GT&Cs for more information.
Process Error Documents: Select Yes to process error logs. If you select Yes and specify a GT&C number, then only that GT&C is processed. If you do not specify a GT&C number, then all GT&Cs with errors are processed. The default value is No.
Submit the concurrent request.
Note: Schedule this program to run as often as required to keep the G-Invoicing data current.
Requesting agencies create and preapprove orders in Oracle Purchasing or Oracle CLM and then push order data to the G-Invoicing application. Servicing agencies then pull the data into Oracle Projects, where they add and update their details as required. After a servicing agency provides the necessary information and approves an order in Oracle Projects, the servicing agency pushes the same order back to the federal G-Invoicing application using the same concurrent program. At that point, the order status in the federal G-Invoicing application changes to Open.
To pull or push performance transactions in XML format, run the Intragovernmental Performance Interface Program
If you are in a different, switch to CLM Purchasing Super User.
On the home page, click Reports and then click Schedule Requests. The Schedule Request: Define page appears.
Select New Request.
In the Program Name field, enter Intragovernmental Orders Interface Program.
In the Parameters tab, enter the following details:
Agency Type: Select Requesting Agency.
Request Mode: Select Push to send data to or Pull to retrieve data from the federal G-Invoicing application.
Request Type:
If the request mode is pull, then select from the following values:
Get Order Attachment
Get Order List
Get Order by ID
If the request mode is push, then select from the following values:
Post Attachments
Post Orders
Operating Unit: Specify the operating unit.
Agency Location Code: Optional: To retrieve data for a specific agency, select its agency location code (ALC).
Document Number: Optional: To run the program for a specific order, enter the document number.
Document Status: Optional: If you specify a status, then the program only processes documents that are in that status.
Process Error Documents: If you select Yes and specify an order number, then errors for only that order are processed. If you do not specify a order number, then all orders with errors are processed. The default value is No.
Submit the concurrent request.
Note: Schedule this program to run as often as required to keep the G-Invoicing data current.
Note: After an order is approved within the requesting agency, the PO IGT Order Generate & Push XML process generates the XML.
You need not run the program manually, because it runs automatically when the Intragovernmental Orders Interface Program runs successfully.
To pull or push performance transactions in XML format, run the Intragovernmental Performance Interface Program
If you are in a different responsibility, switch to CLM Purchasing Super User.
On the home page, click Reports and then click Schedule Requests. The Schedule Request: Define page appears.
Select New Request.
In the Program Name field, enter Intragovernmental Performance Interface Program.
In the Parameters tab, enter the following details:
Agency Type: Select either requesting agency or servicing agency.
Request Mode: Select the request mode for data processing.
Request Type: Select a request type from the list.
Operating Unit: Select the operating unit to retrieve data for that OU.
Agency Location Code: Select the agency location code to retrieve data for that agency. You can leave this parameter blank to retrieve data for all ALCs defined for the OU.
Order Number: Optionally, enter the order number to run the program for a specific order.
Performance Number: Optionally, enter the performance number to run the program for a specific order.
Performance Status: Optionally, select the performance status to run the program for a specific performance status.
Process Error Documents: If you select Yes and specify a performance number, then errors for only that document are processed. If you do not specify a document number, then all errors are processed. The default value is No.
Submit the concurrent request.
Note: Schedule this program to run as often as required to keep the G-Invoicing data current.
This concurrent program creates an invoice without invoice validation, accounting, and payment. The status in the history table displays Success Invoicing. If you use this concurrent program, then you will need to validate, account, and post to GL manually or using Oracle Payables programs.
To run the Intragovernmental Performance Integration to Payables concurrent program, perform the following
If you are in a different responsibility, switch to CLM Purchasing Super User.
Click Requests.
Click Submit a New Request.
In the Name field, enter Intragovernmental Performance Integration to Payables Program.
The Submit Requests: Define window appears.
Select your operating unit.
Optional. Select an order number.
Select an invoice type: Prepayment Invoice (advance performance), Standard Invoice (delivery performance), or Credit Memo.
In the Process Error Documents field, select Yes or No. If you select Yes and specify an order number, then only that order is processed. If you do not specify an order number, then all orders with errors are processed. The default value is No.
When FOB is Destination, this concurrent program creates receipts for delivery performance and corrections to receipts when there is an adjustment to a delivery performance.
To run this program, perform the following steps.
Navigate to the CLM Purchasing Super User responsibility or Purchasing responsibility.
Select Requests.
Select Submit a New Request. The Submit Requests: Define window appears.
Search for and select the Intragovernmental Performance Integration to Receiving Program.
Select your operating unit.
Optional. Select the order number.
In the Process Error Documents field, select Yes or No. If you select Yes and specify an order number, then only that order is processed. If you do not specify a document number, then all orders with errors are processed. The default value is No.
This concurrent program creates journal entries.
To run the program, perform the following steps
Select the CLM Purchasing Super User responsibility.
Click Requests.
In the Find Requests window, click Submit a New Request.
Query Intragovernmental Deferred Performance Integration Program. The Parameters window appears.
Enter your operating unit.
(Optional) To pull the deferred performance for a specific order, enter the order number.
In the Reverse Previous Period Pending Deferred Payments field, select Yes or No.
This option is used to reverse deferred payment performances on the requesting side as accrual reversal in the subsequent period.
If the servicing agency submits a deferred payment at the month end, and the requesting agency pulls it at the month end, and there is no subsequent deferred payment for the same order line schedule, then the deferred payment status will be Informational and will not change to Deleted.
If you select Yes, then the deferred payments that are pending in an Informational status at the end of the previous period are reversed and the reversal journal is created in the current period.
Indicate if you want to process documents that have errors. Transactions that error due to period validity or other issues are reprocessed to create journals and reversals.
If you select Yes and specify an order number, then errors for only that order are processed. If you do not specify an order number, then all orders with errors are processed. The default value is No.
Administrators can view G-Invoicing requests to track the request status of each exchange of data with the federal G-Invoicing application. You can also view request and response XML by document number. To view the request status along with the IGT document number and related parameters, navigate to the G-Invoicing Requests page.
Users with the Order Manager (Administrator) and Order Viewer roles can view TAS and BETC details on the G-Invoicing Groups TAS/BETCs page. This page displays the information that was defined in the federal G-Invoicing application and pulled into Oracle E-Business Suite.
You can access this page from the Order Summary page and the Update Order page.
This page displays the following details related to organizational group structure:
Group name
Description
ID
Status
Agency Location Code
Creation Date
Last Update Date
Deactivation Date
The TAS Filters region displays the following details:
Agency Identifier
Allocation Transfer Agency (ATA)
Subaccount
Main Aaccount
You must enter the agency type, the operating unit, and the group name to retrieve the TAS and BETC details. There may be multiple TAS and BETC combinations available for a group.
Viewing TAS and BETC Details
The G-Invoicing Groups TAS/BETCs page displays the following details:
Sublevel Prefix
Agency ID
Availability Type
Beginning Period of Availability (BPOA)
Ending Period of Availability (EPOA)
Main Account
Subaccount
Business Event Type Code (BETC)
You must add the DFF context code PR_IGT_AGENCY_INFO for the requisition header DFFs to capture GT&C and agency information. This is done in Oracle Purchasing.
Switch to the Purchasing, US Federal responsibility.
Click Setup, then Flexfields, then Descriptive, and then Segments. The Descriptive Flexfield Segments window appears.
In the Title field, query Requisition Headers.
Unfreeze the flexfield definition.
In the Context Field Values multi-record block, in a new record, enter PR_IGT_AGENCY_INFO in the Code field.
With the new record selected, click Segments.The Segments Summary window appears.
Add the following segments for the context you defined:
Number | Name | Window Prompt | Column | Value Set |
10 | SOURCE_DOC_ID | GT&C | ATTRIBUTE | PO_IGT_GTNC_DOC |
15 | REQ_GROUP_INFO | Requesting Group | ATTRIBUTE | PO_IGT_REQ_GROUP_F |
20 | REQ_ALC_INFO | Requesting ALC | ATTRIBUTE | PO_IGT_REQ_ALC_F |
25 | SER_GROUP_INFO | Servicing Group | ATTRIBUTE | PO_IGT_SERV_GROUP_F |
30 | SER_ALC_INFO | Servicing ALC | ATTRIBUTE | PO_IGT_SERV_ALC_F |
Defining Segments
Note: Ensure that the DFF attribute name is as given in the DFF Definitions for GT&C and Agency table above. In the Column field, enter any attribute available at your site. The value sets displayed in the table are predefined and you can use them when defining attributes. You must mark all the attributes as required and entered when creating IGT requisitions in Oracle Purchasing.
Define a DFF for GT&Cs and associate a value set as shown in the DFF Definitions for GT&C and Agency table above and in the Segments (Requisition Headers) image:
Segments (Requisition Headers)
Define a DFF for the requesting agency location code (ALC) and associate a value set as shown below:
Defining Value Sets for Requesting Agency Information
Define a DFF for Servicing agency location code (ALC) and associate a value set as shown below:
Defining Value Sets for Servicing Agency
You must add a custom validation and extension to validate TAS.
The TAS derived for the funding segment in the charge account must be validated against the requesting group entered for the DFF. You must retrieve the requesting group and the requesting ALC captured in DFFs and invoke the following program: icx_por_igt_validations.validate_igt_tas_betc
You must set up the following DFFs to maintain a link between performance transactions and the corresponding receiving transactions.
Note: You do not need to set up DFFs to link performance transactions with Oracle Payables invoices. That connection is already defined using the reference columns of the invoice tables.
Application | Title | Context | Segments | |||
Sequence Number | Name | Window Prompt | Column | |||
Purchasing | RCV_SHIPMENT_HEADERS | IGT Performance | 10 | Performance Number | Performance Number | ATTRIBUTE |
20 | Performance ID | Performance ID | ATTRIBUTE | |||
Purchasing | RCV_SHIPMENT_LINES | IGT Performance | 10 | Performance Number | Performance Number | ATTRIBUTE |
20 | Performance Detail Number | Performance Detail Number | ATTRIBUTE | |||
30 | Performance Detail ID | Performance Detail ID | ATTRIBUTE | |||
Purchasing | RCV_TRANSACTIONS | IGT Performance | 10 | Performance Number | Performance Number | ATTRIBUTE |
20 | Performance Detail Number | Performance Detail Number | ATTRIBUTE | |||
30 | Performance Detail ID | Performance Detail ID | ATTRIBUTE |
When you define each DFF for performance accounting, you must use the exact title, context, and name specified in the DFF Definitions for Performance Accounting Transactions table above. You can use any available attributes for the columns.
Define the RCV_SHIPMENT_HEADERS DFF.
Switch to the Application Developer, US Federal responsibility.
Click Flexfield, then Descriptive, and then Register.
The Descriptive Flexfields window appears.
Query for the Purchasing application, with the table name RCV_SHIPMENT_HEADERS.
Deselect the Protected option.
Copy the title and define the DFFs as shown in the DFF Definitions for Performance Accounting Transactions table above.
To verify the attributes registered for the title, click Columns.
The Columns window appears, displaying the column name attributes for the RCV_SHIPMENT_HEADERS table.
To create the receiving shipment headers DFF context:
Switch to the Purchasing, US Federal responsibility.
Select Setup, then Flexfield, then Descriptive, and then Segment.
In the Title field, query RCV_SHIPMENT_HEADERS.
The Descriptive Flexfield Segments window appears.
Unfreeze the flexfield definition.
In a new row in the Context Field Values multi-record block, enter IGT Performance.
This is the agency information defined as a DFF for the context.
Save your work.
Click Segments.
The Segments Summary window appears.
Add the segments for the DFF for the context you defined, as shown in the DFF Definitions for Performance Accounting Transactions table above.
Note: You can change the title for the table, so refer to subsequent instructions for the exact table and title for setting up the DFF.
Defining Receiving Shipment Lines (RCV_SHIPMENT_LINES)
Switch to the Application Developer, US Federal responsibility.
Select Flexfield, then Descriptive, and then Register.
The Descriptive Flexfields window appears.
Query for the Purchasing application, with the table name RCV_SHIPMENT_LINES.
Deselect the Protected option.
Copy the title and the DFF definition from the DFF Definitions for Performance Accounting Transactions table above.
Save your work.
To verify the attributes registered for the title, click Columns. The list of DFF attributes appears.
The Columns window appears, showing the columns attributes for the table.
To create the receiving shipment headers DFF context:
Switch to the Purchasing, US Federal responsibility.
Select Setup, then Flexfield, then Descriptive, and then Segment.
Query for the Purchasing application, with Shipment Lines Additional Information as the title.
The Descriptive Flexfield Segments window appears.
Unfreeze the descriptive flexfield to add the context.
Enter IGT Performance in the Context Field Values region.
This is the agency Information defined as DFF for the context.
Click the save icon to save.
Click Segments.
The Segments Summary window appears.
Add the segments for the context you have defined, as shown the in the DFF Definitions for Performance Accounting Transactions table above.
Defining Receiving Transactions (RCV_TRANSACTIONS)
Switch to the Application Developer, US Federal responsibility.
Select Flexfield, then Descriptive, and then Register.
The Descriptive Flexfields window appears.
Query the Purchasing application, with the table name as RCV_TRANSACTIONS.
Deselect the Protected option.
Copy the title and then define the DFF as shown in the DFF Definitions for Performance Accounting Transactions table above.
To verify the attributes registered for the title, click Columns. The list of DFF attributes appears.
The Columns window appears, showing the columns attributes for the table.
To create the receiving transaction DFF context:
Switch to the Purchasing,US Federal responsibility.
Click Setup, then Flexfield, then Descriptive, and then Segment.
Query the Purchasing application, with the title Receiving Transactions.
The Descriptive Flexfield Segments window appears.
Unfreeze the flexfield definition to add the context.
In the Context Field Values multi-record block, in a new record, enter IGT Performance.
This is the agency information defined as a DFF for the context.
Save your work.
Click Segments.
The Segments Summary window appears.
Add the segments for the context you have defined, as shown the in the DFF Definitions for Performance Accounting Transactions table above.