Using G-Invoicing in Oracle Projects

This chapter describes how a servicing (selling) agency uses Oracle Projects to carry out intragovernmental transactions in accordance with the federal government's G-Invoicing requirements.

This chapter covers the following topics:

Overview

The Oracle E-Business Suite (EBS) solution for G-Invoicing works with the federal G-Invoicing application to facilitate the exchange and processing of buy and sell data related to intragovernmental transactions (IGTs). The solution is integrated with Oracle Contract Lifecycle Management for Public Sector (CLM), Oracle Purchasing, and Oracle Projects, and other products play supporting roles.

As a federal program agency you can use the G-Invoicing solution to:

The G-Invoicing solution uses REST services to communicate with the federal G-Invoicing application. Requesting (buying) and servicing (selling) agencies push (send) and pull (retrieve) IGT data to and from the G-Invoicing application. Data retrieved from the G-Invoicing application is validated, and corresponding transactions are created within EBS.

The G-Invoicing solution includes:

For more information about setting up and using G-Invoicing in Oracle E-Business Suite, see:

G-Invoicing Flow

The EBS G-Invoicing flow includes the following integration between the requesting side, the servicing side, and the federal G-Invoicing application. The following steps describe what the overall flow looks like from the perspective of the servicing agency.

  1. Either agency creates an order. After the order has been updated as needed and approved, the requesting agency shares it with the servicing agency. The status of the order is Shared with Servicing Agency (SSA).

  2. Both agencies pull and push GT&Cs, orders, and performances between the federal G-Invoicing application and EBS.

  3. The servicing agency pulls approved orders and updates them with required attributes such as create and associate projects and agreements.

  4. Servicing agencies can also define additional attributes for agreements and performance obligation lines.

  5. The servicing agency can review orders and accept or reject them. When orders are accepted, they are marked Received (REC) and the status in the G-Invoicing application changes to Open.

  6. Agreements are approved, funds are allocated and budget is baselined based on funds availability.

  7. To derive accurate progress and delivery against orders to manage performances and enable settlement, the servicing agency can submit performance. Oracle Projects supports advance, deferred, and delivery performance types.

Running Interface Programs

Loading Projects Command Center Data

Before you can use G-Invoicing with EBS, you must retrieve and load the Projects G-Invoicing Enterprise Command Center (ECC) data.

  1. From the Home page, select the Projects Super User responsibility.

  2. Select Projects, then Requests, and then Run or Schedule.

    The Submit Request window appears.

  3. Query the concurrent program Projects G-Invoicing ECC Data Load.

    The Parameters window appears.

  4. Enter a value in the System Name field.

  5. From the Load Type list, select either Full Load or Incremental Load.

    • Use a full load to load all existing data into Oracle Projects Enterprise Command Center.

    • Use an incremental load to load only data that has been modified since the previous run. Schedule incremental loads to run as often as required to keep your data current.

  6. Enter a value in the Language code field.

  7. Select a value for the Log Level you want the program to report.

  8. Select a value to set the SQL Trace On.

  9. Click OK.

  10. Click Submit to run the concurrent program.

Importing General Terms and Conditions Data from G-Invoicing Application

To keep the GT&C data on the G-Invoicing dashboard current, schedule the Intragovernmental Agreements (GT&C) Interface concurrent program to run periodically.

To run the concurrent program, perform the following steps:

  1. From the Home page, select the Projects Super User responsibility.

  2. Select Projects, then Requests, and then Run or Schedule.

    The Submit Request window appears.

  3. Query the Intragovernmental Agreements (GT&C) Interface concurrent program.

    The Parameters window appears.

  4. From the Agency Type list, select Servicing Agency.

  5. From the Request Mode list, select either Pull or Push.

  6. In the Request Type field, select Get GTC List.

  7. Select your operating unit.

  8. Select an agency location code (mandatory).

  9. Optionally, enter a document number and a document status.

  10. Optionally, indicate whether to process documents with errors.

  11. Click OK.

  12. Click Submit.

This program pulls the GT&C list and extracts the GT&Cs based on the date and agency location code. Oracle Projects submits the concurrent request for each GT&C. After a response is received from the G-Invoicing application for all the GT&Cs, a business event is invoked with the parent request ID. Subscription to this business event can create GT&C documents in the system.

Interfacing Orders to and from G-Invoicing Application

Once an order is created and approved, you can pull it into the G-Invoicing dashboard in the Projects Enterprise Command Center. You must run the load program to display the order data in the G-Invoicing dashboard. You can schedule this program to run periodically.

To pull eligible orders into the G-Invoicing Dashboard or to push approved orders back to the federal G-Invoicing application, perform the following steps:

  1. From the Home page select the Projects Super User responsibility.

  2. Select Projects, then Requests, and then Run or Schedule.

    The Submit Request window appears.

  3. Query the Intragovernmental Orders Interface concurrent program. The Parameters window appears.

  4. From the Agency Type list, select Servicing Agency.

  5. Set the request mode.

    • Use Pull mode to retrieve a list of eligible orders.

      For each eligible order, the program extracts the order from the federal G-Invoicing application . The program synchronize order data into the Projects Command Center and automatically creates an agreement.

    • Use Push mode when your agency has approved an agreement. The order status must be Pending.

  6. Select the request type. If you set the request mode to Pull, then set the request type to Get Order List.

    The following options are supported:

    • Get Order Attachment

    • Get Order List

    • Get Order by ID

    • Post Attachments

    • Post Orders

  7. (Optional) Select an operating unit.

  8. Select an agency location code.

  9. Optionally, enter a document number, document status, or attachment number.

  10. Indicate whether to process documents with errors.

  11. Click OK and then click Submit.

Interfacing Performances to and from the G-Invoicing Application

To pull or push performances into the G-Invoicing dashboard, perform the following steps:

  1. Select the Projects Super User responsibility.

  2. Select Projects, then Requests, and then Run or Schedule.

    The Submit Request window appears.

  3. Query the Intragovernmental Performance Interface concurrent program.

    The Parameters window appears.

  4. From the Agency Type list, select Servicing Agency.

  5. Set the request mode.

    • Use Pull to retrieve a list of approved performances.

    • Use Push to post performances.

  6. Set the request type.

    • To retrieve performance data from the federal G-Invoicing application, use Get Performance.

    • To submit performance, use Post Performances.

  7. Select an operating unit. If you leave this field empty, then performances are pulled from all IGT operating units.

  8. (Conditional) If you specified an operating unit, then select an agency location code. If you did not specify an operating unit, then this field is disabled.

  9. (Optional) Enter an order number to pull performances only for that order. Leave the field empty if you want to pull performances across all orders.

  10. (Optional) Enter a performance number. Leave the field empty if you want to pull all performances.

  11. Select a performance status: Informational, Pending or Settled.

  12. Click OK and then click Submit.

Submitting Performance for Multiple Orders

To submit multiple performances at once for advance and non-advance orders, use the PRC: Mass Submission Performances for G-Invoicing concurrent program.

If the orders are advance-enabled, then the concurrent program submits the advance performance and then the delivery performance. If orders are non-advance-enabled, then the concurrent program submits the deferred performance and then the delivery performance.

When the performance lines result in failure, the concurrent program resubmits these lines the next time it runs.

To submit performance for a range of orders, perform the following steps:

  1. From the Home page select the Projects Super User responsibility.

  2. Click Projects, then Requests, and then Run or Schedule.

    The Submit Request window appears.

  3. Query the PRC: Mass Submission Performances for G-Invoicing concurrent program.

    The Parameters window appears.

  4. Select an operating unit.

  5. Select an agency location code. This is a mandatory field.

  6. Enter a value in the From Order field.

  7. Enter a value in the To Order field.

  8. Select the performance type: Advance, Deffered, or Delivery.

    If you leave the field empty, then the concurrent program submits all the performances in an appropriate order.

  9. Enter the preparer name. The name must be at least 7 characters long. If you have set up the preparer details in the G-Invoicing Setup page, then the system uses those values.

  10. Enter the preparer's Email ID. The email must be a valid email address. If you have set up the preparer details in the G-Invoicing Setup page, then the application defaults this value.

  11. Enter the preparer's contact number. Phone number must be a valid number. If you have set up the preparer details in the G-Invoicing Setup page, then the application defaults that value.

  12. Enter a date for the Performance Date field. The performance date must be in the current open accounting period.

  13. Enter a comment.

  14. Select a performance indicator: Final or Partial.

  15. Enter either Yes or No for Error Documents field. This is an optional field. Set the value to Yes to process all documents that have error records from pulling open orders due to setup, server issues, or handshake issues. If there is any error while pulling the order from G-Invoicing, the agency administrator or buyer will get a notification about the failure. You can then correct and reprocess these orders.

  16. Click OK and then click Submit.

Generating 7600B Reporting

To generate and print a 7600B report, run the MGT Generate 7600B Federal Report concurrent report.

To generate the 7600B report, perform the following steps:

  1. Navigate to the Projects Super User, US Federal responsibility.

  2. Select Requests, and then Schedule.

  3. Query the concurrent program, MGT Generate 7600B Federal Report.

  4. Select the concurrent program and click Select.

  5. Click the Parameter tab.

  6. Enter or choose an operating unit.

  7. Enter or choose the order Number.

  8. Click Continue.

  9. Review the request and click Submit.

Using the G-Invoicing Dashboard in Projects

Overview

Costing Managers can use Oracle Projects Command Center to establish a programmatic strategy for tracking, monitoring, and controlling project costs. Projects Command Center contains key performance indicators of the project and enables users to view metrics, drill down into details, analyze deviations, and take appropriate and corrective measures as required. Project controls measure actual progress versus planned, and enables users to take corrective actions. Projects Command Center provides visibility to measures using, metrics, KPI's, charts, summarized data, and a detailed level view of data in the form of results sets.

Note: Oracle Projects Command Center dashboards do not consider sponsored projects (grants). In addition, only active projects are considered for display in ECC, and projects where users are an active project manager display on the dashboard. (Oracle Grants Accounting is a separate Oracle application that is not related to Oracle Enterprise Command Center).

The following dashboards are available for Project Costing using Oracle E-Business Suite Enterprise Command Center integration:

Note: The Oracle Projects application configuration and setup must be completed after the installation and common configurations are completed as described in My Oracle Support Knowledge Document 2495053.1, Installing Oracle Enterprise Command Center Framework. For additional ECC Overview information, see Overview of Oracle Enterprise Command Center Framework, Oracle E-Business Suite User's Guide.

Searching Enterprise Command Center Dashboards

Use the dashboard sidebar to refine (filter) the data on each dashboard. You can also Search using a keyword, value, or a specific record. The type-ahead feature suggests matches for your entry that correspond to the selected data set. When you submit a search, the search term is added to the Selected Refinements list, and the dashboard data is refined to include only records that match the search. You can add multiple refinements and remove any of them at any time. Using Saved Searches, you can create and save your searches and refer to them later. You can also edit and delete saved searches.

You can also search using Descriptive Flexfield (DFF) attributes. For a list of Oracle Projects Costing flexfields, refer to Configuring Descriptive Flexfields for Search.

Use an asterisk (*) or percent sign (%) to perform a partial keyword or record search that matches any string of zero or more characters. You can also use a question mark (?) to perform a partial search that matches any single character.

Additional Information: For additional information about searching and refining data in Oracle Enterprise Command Centers, see Search in Highlights of an Enterprise Command Center, Oracle E-Business Suite User's Guide.

G-Invoicing Dashboard

The G-Invoicing dashboard displays G-Invoicing data for all orders. This dashboard provides information to the servicing agency and key members for managing orders. The dashboard displays G-Invoicing elements that include General Terms and Conditions (GT&Cs), orders, exceptions, funding, and performance metrics across all orders and projects. From the dashboard, you can navigate to individual projects, tasks, and resource assignment levels. Dashboard metrics include:

Based on your Role Based Access Control (RBAC) setup, navigate to the Projects Command Center.

As an example, from the Projects SU, US Federal responsibility: Projects Command Center > G-Invoicing (tab)

The following is a partial display of the G-Invoicing dashboard.

the picture is described in the document text

the picture is described in the document text

The following table describes the G-Invoicing dashboard components.

Component Description
Summary (tab layout)
GT&C (tab)		 The GT&C summary bar displays the following metrics:

  • Currency

    This metric displays the servicing agency currency.

  • Active

    This metric displays the number of GT&Cs with the active status code Open for Orders. Click this metric to further refine the dashboard data.

  • Ordered Value

    This metric displays ordered value calculated as (total estimated amount less total remaining amount). Click this metric to further refine the dashboard data.

  • Remaining Value

    This metric displays the remaining value. Click this metric to further refine the dashboard data.

  • Latest Validity

    This metric displays the most recent dates for valid GT&Cs.
Summary (tab layout)
Orders (tab)		 The Orders summary bar displays the following metrics:

  • New

    This metric displays the number of new orders that are in progress and have the active status Open for Order, and have associated projects and accepted orders. Click this metric to further refine the dashboard data.

  • Pending Approval Submission

    This metric displays the number of orders that have not been accepted or approved by the requesting agency. This value includes agreements with the status Work In Progress. Click this metric to further refine the dashboard data.

  • Pending Approval

    This metric displays the number of orders submitted and pending approval. Click this metric to further refine the dashboard data.

  • Approved

    This metric displays the number of approved orders. Click this metric to further refine the dashboard data.

  • Rejected

    This metric displays the number of rejected orders. Click this metric to further refine the dashboard data.

  • Modified

    This metric displays the number of modified orders. Click this metric to further refine the dashboard data.

  • Pending Close

    This metric displays the total number of orders in Pending Close status.
Summary (tab layout)
Exceptions (tab)		 The Exceptions summary bar displays the following metrics:

  • Failed Pulls

    This metric displays the number of orders that have not met the criteria for creating an agreement. Therefore, agreements could not be created. Click this metric to further refine the dashboard data.

  • Failed Push

    This metric displays the number of orders that have been approved in Oracle Projects through the agreement approval stage, but that could not be pushed to G-Invoicing for technical reasons. Click this metric to further refine the dashboard data.

  • Advance Performance Failed Push

    This metric displays the total value of advance performance that has not been pushed to G-Invoicing when submitting for technical reasons. Click this metric to further refine the dashboard data.

  • Deferred Performance Failed Push

    This metric displays the total value of deferred performance that has not been pushed to G-Invoicing when submitting for technical reasons. Click this metric to further refine the dashboard data.

  • Delivery Performance Failed Push

    This metric displays the total value of delivery performance that has not been pushed to G-Invoicing when submitting for technical reasons. Click this metric to further refine the dashboard data.
Summary (tab layout)
Funding (tab)		 The Funding summary bar displays the following metrics:

  • Funding

    This metric displays the total amount of funding from all approved orders. This value is calculated as the sum of advance receipt and non-advance order value.

  • Non-Advance Order Value

    This metric displays the total approved value of non-advance orders. The value for funding against non-advance order value remains the same as order value. Click this metric to refine the dashboard data.

  • Advance-Enabled Order Value

    This metric displays the total approved order value of advance-enabled orders. Click this metric to refine the dashboard data.

  • Advance Performance

    This metric displays the total value of advance receipts that have been applied and processed to G-Invoicing. This metric provides the value of advance performance against orders that are paid by the requesting agency, and received and acknowledged by the servicing agency. Click this metric to refine the dashboard data.

  • Advance Pending

    This metric displays the total value of advance-enabled orders minus advance receipts. Click this metric to refine the dashboard data.

  • Balance Funding

    This metric displays active funding minus accepted delivery performance.
Summary (tab layout)
Performance (tab)		 The Performance summary bar displays the following metrics:

  • Deferred Performance (Pending Submission)

    This metric displays the total value of deferred performance. This is the value of work that has been completed but for which the funds have been deferred for settlement at a later date. This metric provides value of deferred performance against orders between the servicing agency and the requesting agency.

  • Delivery Performance (Pending Submission)

    This metric displays the total value of delivered performance, which represents the completion of work or the transfer of goods to the requesting agency. This metric provides value of delivery performance against the orders between the servicing agency and the requesting agency.

  • Delivery Performance (Submitted)

    This metric displays the total amount of approved invoices submitted to G-Invoicing and awaiting acceptance by the requesting agency.

  • Accepted Performance

    This metric displays the delivery performance value accepted by the requesting agency and marked as final.

  • Rejected Performance

    This metric displays the total value of rejected performance reported from G-Invoicing. A requesting agency may reject all or a part of the delivery by the servicing agency. This metric provides a value of rejected performance against the orders between the servicing agency and the requesting agency.
Customer Status (tab layout)
GT&C (tab)		 The GT&C chart displays buying agency details for total ordered amount and total remaining amount of the active GT&C between the servicing agency and the buying agencies. Click a requesting agency GT&C number in the chart to view the individual GT&C of the selected buying agency and its associated GT&C's with the servicing agency.
Click a Requesting Agency Location Code in the chart to refine the data and display all GT&C numbers that belong to the requesting agency.
Customer Status (tab layout)
Orders (tab)		 The Orders chart displays the total value of orders for each order status against each buying agency which the servicing agency is conducting business with. You can click an agency order number in the chart or the order value bar to view individual order details between the servicing agency and the buying agency.
Click a Requesting Agency in the chart to refine the data and display all Order Numbers that belong to the requesting agency.
Customer Status (tab layout)
Funding (tab)		 The Funding chart displays the overall amount of funding by Non-Advance orders, funding through Advance Receipts, and funding Advance Pending orders.
Customer Status (tab layout)
Performance (tab)		 The Advance Orders chart displays an overview of advance order values in terms of overall performance amounts.
The Non-Advance Orders chart displays an overview of non-advance orders in terms of overall performance amounts.
Header (tab layout)
GT&C (tab)		 The GT&C results table displays data grouped by GT&C attribute groups. You can view data grouped by:

  • GT&C Information

  • Agreement Amount Information

  • Additional Information

  • Agency Information

  • Preparer Information

  • Requesting Approval Information

  • Servicing Approval Information


You can also click values in the GT&C Number, Title, Agreement Type, Status, Termination Days, Requesting Group Name, and Servicing Group Name columns to filter and refine dashboard data for the selected values.
Header (tab layout)
Orders (tab)		 The Orders results table displays data grouped by Order attribute groups. You can view data grouped by:

  • Order Details

  • Advance

  • Billing and Delivery Information

  • Funding Details

  • Partner Information

  • Performance


You can click values in the columns to filter and refine dashboard data for the selected values.

Note: This results table includes the following action-enabled attributes:

  • Update Agreement - Click this action icon to navigate to the Update Agreement page where you can update and create agreements.

  • Create Project - Click this action icon to navigate to the Create Project page to create a new project.

  • Associate Project - Click this action icon to navigate to the Associate Project window where you can search for and associate projects.

  • View Performance Obligation - Click this action icon to navigate to the Performance Obligations page to view performance obligation details.


You can also click the Options link to perform the following actions:

  • Create Agreement - This action allows you to create agreements manually for those orders that failed to create agreements automatically.

  • Order Modification Uptake - Enables order modifications.

  • Resynchronize Orders - Allows you to push approved orders that previously failed push to G-Invoicing.

  • Close Order - Closes the selected order(s) that are in Pending Close status.
Details (tab layout)
Order Lines (tab)		 The Order Lines results table displays data grouped by Order Line attribute groups.
From the drop-down list, you can select views to display details by:

  • Order Line Details

  • Performance


You can click values in the columns to filter and refine dashboard data for the selected values.
Details (tab layout)
Order Line Schedules (tab)		 The Order Line Schedules results table displays data grouped by Order Line Schedules attribute groups.
From the drop-down list, you can select views to display details by:

  • Schedule Details

  • Servicing Agency

  • Requesting Agency

  • Performance


You can click values in the columns to filter and refine dashboard data for the selected values.
Details (tab layout)
Performance Details (tab)		 The Performance Details results table displays data grouped by performance attribute groups.
From the drop-down list, you can select views to display details by:

  • Performance Details

  • Preparer

  • Receipt


Click the View action link to navigate to the View Performance History page to view and update performance detail. The page displays by Order Number, Order Line Number, Schedule Line Number, Performance Type, and Accounting Period.
You can also click on values within the columns to filter and refine dashboard data for the selected values.

Managing and Maintaining GT&Cs and Orders

Manage and Maintain General Terms and Conditions

GT&C are the terms and conditions of a transaction, agreed upon between the seller and the buyer. The Intragovernmental Agreements (GT&C) Interface concurrent program pulls GT&C with approved and closed statuses, and their corresponding projects and details, from the federal G-Invoicing application. The details can then be displayed on the G-Invoicing dashboard of the Projects Command Center.

To view requesting agency location code, servicing agency location code, requesting group name and servicing group name, select Agency Information from the GT&C tab or Partner Information from the Orders tab.

Manage and Maintain Orders

An order is an agreement between trading parties to deliver goods and services within a certain timelines and according to certain specifications. The agency (both requesting and servicing) creates an order, approves it internally, and shares it with the servicing agency. The servicing agency can then update order details or accepts or rejects the order.

Order Mapping to Project Entities

Orders are mapped to different entities in Oracle Projects. The order header is mapped to an agreement, order lines are mapped to performance obligation, and order line schedules are mapped to performance obligation lines. You can view these details on the G-Invoicing dashboard in the Projects Command Center (ECC).

Refer to "G-Invoicing Business Objects Mapping in Oracle EBS" for more details.

Generating Draft Agreement and Initiate Workflow

Servicing agencies update agreements and submit them for requesting agency's approval. Orders with the Shared with Servicing Agency (SSA) status are pulled into the G-Invoicing dashboard. Agreements are automatically created with the Work In Progress status.

Agreements inherit the agreement type from the implementation options. The operating unit on an agreement is the seller's agency location code (ALC) based on the ALC mapping on the Bank Accounts page of the Oracle Federal Administration module. One ALC is mapped to one operating unit. The pull program defaults the agreement type and operating unit on the draft agreement. You can change the operating unit on an agreement until it is approved.

If the automatic agreement creation fails, then errors display in the G-Invoicing dashboard. Agreement creation can fail due to some of these conditions:

After errors are resolved, agreements are recreated when the pull orders program is run.

Order Approval Flow

When IGT orders are pulled by servicing agencies, the system creates agreements with the Work In Progress (WIP) status in Oracle Projects.

You can associate a project with an order at any time, and one WIP agreement exists for that project in both the order creation processing and the update flow.

The order approval happens at the agreement level. When the order is submitted for approval, all order lines and order line schedules are associated with a project. You must enter all the mandatory attributes for servicing agencies.

On Approval

When an agreement is approved, performance obligations (POBG) are published with funding, revenue budgets are created and baselined, and accounting entries are created in Oracle General Ledger (GL). This is performed for both first and incremental approvals.

On Rejection

When an agreement is rejected and the order has been associated with a project but has not been updated or incremented, the order is disassociated from the project. For an incremental order or an order with updates, the delta is rolled-back and original status is restored.

Pulling General Terms and Conditions Attachments into EBS

You can pull attachments in to EBS. The G-Invoicing dashboard, in the GT&C header region, includes a new column, Attachment.

To pull the attachments, perform the following steps:

  1. From the Home page, select the Projects Super User, US Federal responsibility.

  2. Select Enterprise Command Center and then Projects Command Center.

  3. Click the G-Invoicing dashboard tab.

  4. From the GT&C Header region, click the Attachments (link) icon.

    The General Terms and Conditions Attachments page appears.

  5. Click the Pull Attachments option.

    The system pulls all attachments from the federal G-invoicing application and displays them in the Attachment region.

General Terms and Conditions Attachments

The General Terms and Conditions Attachments page shows the following attachment details.

  1. The general terms and conditions header region shows GT&C Number, agreement type, GT&C start and end date range, advance payment indicator, total estimated amount and the remaining amount.

  2. The General Terms and Conditions Attachment region in the header, shows the details of an attachment such as whether the attachment is from the servicing or requesting agency, name of the attachment, date the attachment is added, the URL of the attachment and the attachment status if it has been downloaded.

  3. The Attachment region shows more details of the attachment displayed above.

Order Attachments

Because an order is a contract, the order has attachments reinforcing the order requirements. Both buyers and sellers provide attachments. You can download and view the attachments from the Agreements page.

You can manually pull pending attachments using the Pull Attachments option in the Action list on the Update Agreement page. Until the Pull Attachments option is run, attachments are in the Download Pending status and display the URL in the attachment table.

To download (pull) pending attachments for an order through the G-Invoicing dashboard:

  1. Navigate to the Projects Command Center.

  2. On the G-Invoicing dashboard, search by Order Number.

  3. Scroll to the Order Result Set.

  4. Click the Update Agreement link.

  5. Click Actions and then Pull Attachment.

To download pending attachments from Oracle Project Billing:

  1. From the Projects Super User responsibility, click Billing.

  2. Query an agreement.

  3. Click Update Agreement, and then click Pull Attachment.

Order Modification and Uptake

Modifications to orders are considered against mapped order entities. You can track changes to orders, order lines, and order line schedules.

When modified orders are pulled into Oracle Projects, the agreement status changes to Work in Progress.

To access the changes you must uptake the modification. Run the Order Modification Uptake from the Action list on the G-Invoicing dashboard. You can uptake only one modified order at a time. Since POBG and POBG lines are mapped to order line and order line schedules, the addition or deletion or rows is performed during the Order Modification flow. Therefore, you cannot add or delete POBG or POBG lines.

When an order line schedule is deleted, the quantity becomes zero and a negative funding line is generated to negate the corresponding value.

Note: You can only update orders that have associated GT&C in an approved status.

Resynchronizing Orders

If an order does not meet the requirements for creating an agreement that is pulled and stored in the shared structures, the order fails agreement creation. Orders that fail are displayed on the G-Invoicing dashboard with the option to create agreements manually after resolving errors.

Similarly, when an order (agreement) approved by the servicing agency is pushed to the G-Invoicing application, the push could fail with errors. If that happens, correct the errors and then run the Resync Order option (from the Action list) to push the corrected orders back to the G-Invoicing application.

Using Agreements and Agreement Additional Attributes

Updating Agreement

To update agreements, perform the following steps:

  1. Login to E-Business Suite application.

  2. Select Projects Super User, US Federal responsibility.

  3. Click Enterprise Command Center, and then click Projects Command Center.

  4. Click the G-Invoicing dashboard tab.

  5. Scroll down to the Headers region and click Orders tab.

  6. Click the Update Agreement (link) icon.

    The Update Agreement page appears.

  7. The Actions menu on the Update Agreement page includes the following options for G-Invoicing:

    1. Additional Agreement Attributes

    2. Pull Attachments

    3. View Agreement Versions

    4. View Funding

  8. Following changes have been made to the Update Agreement header region:

    • You can change the value for the Operating Unit .

    • Acceptance Point: Displays the acceptance point value.

    • Includes new fields, Servicing Organization Group and Requesting Organization Group.

      Depending on the selected servicing agency ALC, the list of values appear.

    • Requesting Organization Group field cannot be edited.

    • Intragovermental Order field indicates if the order is intragovernmental orders. This field is enabled for an IGT order.

    • Confirm Fund Availability field when checked, the system verifies if enough funds are available before they can be settled. Only if the funds are available the agreement can be submitted for approval.

  9. Following new fields are added on the Update Agreement page:

    • Order Creation Date: Displays the calendar date the order was created.

    • Order Status: Displays the current status of the order, such as, Shared with Service Agency SSA.

      Note: Oracle Projects pulls closed orders from the G-Invoicing application. On the update agreement page, the order status includes Closed.

    • Billing Frequency: Defines the frequency used for billing. Valid values are, Monthly, Other, Quarterly, Weekly. If you select Other, then the Billing Frequency Other field is enabled. It is a mandatory field.

    • Billing Frequency Other: Enter the frequency of billing.

    • Order Acceptance Date: Displays the Acceptance date of the order.

    • Total Net Order Amount: Displays the sum of the ordered amount.

    • Servicing Agency ALC: Displays the Service Agency's ALC contained in the GT&C.

    • Click Additional Agreement Attributes in the Actions menu and click Go.

    • Approval Status Displays the status of the order approval such as work in Progress or Approved.

    • Internal Status Displays the status of the order tracked internally at various stages of the order approval.

Creating Additional Agreement Attributes

In the Update Agreement page, select the Additional Agreement Attributes option from the Actions list.

Enter the following details for Servicing Agencies:

  1. Navigate to the Agreement Additional Attribute page.

    The Additional Agreement Attributes page appears.

    The Agreement Details region defaults and displays the values selected for the agreement.

    The Header region defaults and displays the values selected displays the values specified for the order.

    The system defaults and displays values specified for requesting agency. You cannot modify them.

  2. In the Partner Information region, select or enter values for the following fields for a servicing agency:

    1. Servicing Business Unit: Enter a value that matches the Business Unit value provided in the parent GT&C.

    2. Servicing Cost Center: Enter a value that matches the Cost Center value provided in the parent GT&C.

    3. Servicing Department ID: Enter a value that matches the Department ID value provided in the parent GT&C.

    4. Servicing Unique Entity Identifier: Enter the unique ID for the servicing entity.

    5. Servicing Comment: Enter a comment for the order.

    6. Requesting Funding Office Code

    7. Business Transaction Identifier

  3. In the Authority region, select or enter values for the following fields for a servicing agency:

    1. Servicing Program Authority Citation: Select or enter the servicing program authority citation.

    2. Servicing Program Authority Title: Enter the title of the authority for the servicing agency.

  4. In the Delivery region, select or enter values for the following fields for a servicing agency:

    1. FOB Point: Enter a value for the Freight on Board (FOB) point. Valid values are Source or Destination.

    2. Point of Acceptance:Select or enter the point of acceptance of the freight.

    3. Inspection Point: Enter details of the inspection.

    4. Place of Inspection: Enter the place where the inspection will be performed.

  5. In the Advance and Billing region, select or enter values for the following fields for a servicing agency:

    1. Advance Revenue Recognition Methodology: Select or enter the advance revenue recognition methodology being used.

    2. Servicing Agency's Advance Payment Authority Citation: Enter the details of the advance payment authority for the servicing agency.

    3. Servicing Agency's Advance Payment Authority Title: Enter the title of the advance payment authority.

    You must enter the values in the above fields, if Advance is enabled in the Performance Obligation (PoBG) lines. If advance is not enabled, then fields must not contain values.

  6. In the Point of Contact region, select or enter values for the following fields for a servicing agency:

    1. Serving Agency POC Email: Enter the Email ID of the point-of-contact for the servicing agency. The value must contain a minimum of 7 characters.

    2. Serving Agency POC Fax: Enter the fax number for the point-of-contact person. The value must contain a minimum of 1 character.

    3. Serving Agency POC Name: Enter the name of the point-of-contact person. The value must contain a minimum of 1 character.

    4. Serving Agency POC Phone: Enter the phone number of the point-of-contact person. The value must contain a minimum of 1 character.

  7. In the Approval region, select or enter values for the following fields for a servicing agency:

    1. Rejection Reason: Enter the reason for rejecting the agreement.

    2. Void or Close Comments: Add void or closing comments.

  8. In the Funding Approval region, select or enter values for the following fields for a servicing agency:

    1. Servicing Agency Funding Official Email Enter the Email id of Funding official. The value must contain a minimum of 7 characters.

    2. Servicing Agency Funding Official Fax: Enter the fax number of the Funding official. The value must contain a minimum of 1 character.

    3. Servicing Agency Funding Official Name: Enter the name of the Funding official. The value must contain a minimum of 1 character.

    4. Servicing Agency Funding Official Phone: Enter the phone number of the Funding official. The value must contain a minimum of 1 character.

    5. Servicing Agency Funding Official Date Signed: Enter the date when the Funding official approved the agreement. This is a mandatory field.

    6. Servicing Agency Funding Official Title: Enter the title of the funding official for the servicing agency. The value must contain a minimum of 1 character.

  9. In the Program Approval region, select or enter values for the following fields for a servicing agency:

    1. Servicing Agency Program Official Email: Enter the Email ID of the Program approver. The value must contain a minimum of 7 characters.

    2. Servicing Agency Program Official Fax: Enter the fax number of the Program approver. The value must contain a minimum of 1 character.

    3. Servicing Agency Program Official Name: Enter the name of the Program approver. The value must contain a minimum of 1 character.

    4. Servicing Agency Program Official Phone: Enter the phone number of the Program approver. The value must contain a minimum of 1 character.

    5. Servicing Agency Program Official Title: Enter the title of the Program approver. The value must contain a minimum of 1 character.

    6. Servicing Agency Program Official Date Signed: Enter the date when the Program official approved the agreement. This is a mandatory field.

  10. In the Preparer region, select or enter values for the following fields for a servicing agency:

    1. Servicing Agency Prepared Email: Enter the Email of the person who prepared the Order. The value must contain a minimum of 7 characters.

    2. Servicing Agency Prepared Name: Enter the name of the person who prepared the Order. The value must contain a minimum of 1 character.

    3. Servicing Agency Prepared Phone:Enter the phone number of the person who prepared the Order. The value must contain a minimum of 1 character.

Creating or Associating Projects and Updating Performance Obligations

Create or Associate a Project with an Order

After you pull orders into the Projects G-Invoicing dashboard, you can perform the following tasks:

When orders are imported into EBS, Oracle Projects maps the order details to new entities in the project, the performance obligation and corresponding order line schedules are mapped to the performance obligation lines. After you create a new project, the Performance Obligations (Update) window appears. The performance obligation is published when the agreement is approved.

Requirements for Associating a Project with an Order

To associate an order with a project, the following conditions must be met. Oracle Projects verifies that the following conditions are met, and displays an error if any condition is not met:

Select a Project to Associate

Create a project against an order or associate an existing project to the order.

  1. From Home, select the Projects Super User, US Federal responsibility.

  2. Click Enterprise Command Center and then Projects Command Center.

  3. Click G-Invoicing dashboard tab.

  4. In the Orders tab, select Order Details from the list.

  5. Locate an order to edit.

    The presence of a link icon in either the Create Project or the Associate Project column in the same row indicates that the order is available for the named activity.

To associate an existing project with the order, see "Associate a Project".

To create a new project associated with the order, see "Create a Project".

Associate a Project

To associate an existing project with an order, do these steps:

  1. From Home, select the Projects Super User, US Federal responsibility.

  2. Click Enterprise Command Center and then Projects Command Center.

  3. Click G-Invoicing dashboard tab.

  4. In the Headers region, select Orders tab.

  5. Click the Associate Project (link) icon.

    The Associate Project window appears.

  6. Either enter information in the Project field and then click Go, or click Advanced Search for more search options.

  7. Search a project by Project Name or Number.

  8. In the results table, select a project to associate.

  9. Click Associate.

    The Associate Flow runs and the Performance Obligation page appears.

Create a Project

To create an existing project with an order, do these steps:

  1. From Home, select the Projects Super User, US Federal responsibility.

  2. Click Enterprise Command Center and then Projects Command Center.

  3. Click G-Invoicing dashboard tab.

  4. In the Headers region, select Orders tab.

  5. Click the Create Project (link) icon for an order.

    The Select Source window appears.

  6. In the Copy From list, select either Template or Project.

  7. Click Advance Search.

  8. Search for a project or template by an operating unit, name or number.

  9. Select a project or template to copy for your new project.

  10. Click Continue.

    The Create Project: Details page appears.

  11. Enter the project number.

  12. Enter the project name.

  13. Enter or select the project start and end dates.

  14. Click Finish.

The Processing: Creating Project may appear. After the project has been created, the Performance Obligations page appears.

Order Rejection before Associating to a Project

You can perform an outright rejection of an imported order from federal G-Invoicing before associating the project to the order.

To reject the order, perform the following steps:

  1. From Home, select the Projects Super User, US Federal responsibility.

  2. Click Enterprise Command Center and then Projects Command Center.

  3. Click the G-Invoicing dashboard tab.

  4. In the Headers region, click the Orders tab.

  5. Click the Update Agreement icon.

  6. From the Actions menu, click Reject.

The rejected order is pushed back to federal G-Invoicing with the reject status. Once a project is associated with an order, you cannot reject that order.

Disassociate a Project

You can disassociate a project from an order. If an order has not been submitted for approval, then you can disassociate the project from the order. But when the order is submitted for approval or has been approved even once, you cannot disassociate the project and the disassociate option is disabled.

To disassociate an order from a project, perform the following steps:

  1. Log in to Projects Super User, US Federal responsibility.

  2. Select Enterprise Command Center and then Projects Command Center.

  3. Click the G-Invoicing dahsboard tab.

  4. In the Headers region, select Orders tab.

  5. Identify the order to disassociate the project from it.

  6. Click the Update Agreement (link) icon.

    The Update Agreement page appears.

    This page contains the project details region with an option to disassociate the project from the order.

  7. Click the Disassociate option.

  8. In the confirmation dialog box, click Yes to disassociate the project.

The project is delinked, and the performance obligation lines are deleted, and the intragovernmental order option is not selected. If the order has been submitted for approval or approved at least once, then the disassociate option is disabled.

Updating Performance Obligations

When you click Update, the Performance Obligation region displays performance obligations with order line attributes. Oracle Projects displays performance obligations with agreement lines and performance obligation order lines.

Agreement Lines

  1. Number represents the order line number.

  2. Agreement Number indicates the assigned agreement number.

  3. The customer associated with the agreement is the requesting agency.

  4. Item Code displays the code associated with the item.

  5. Item Description displays the description of the selected item.

  6. Quantity displays the number of quantity.

  7. Unit of Measure displays the UOM of the Servicing Agency.

  8. Currency indicates the currency used by the agency.

  9. The transaction amount is the line level amount - the sum of all transaction amount of order line schedules on the performance obligation level.

  10. Net Due Amount appears.

  11. Status displays the status of the agreement.

  12. Capitalized Asset Indicator displays the asset indicator value, True or False. A value must be chosen.

Performance Obligation Order Line Schedules

Treasury Account Symbol (TAS) and Business Event Type Code (BETC) attributes are available at the performance obligation line level; these values are sourced from the US Federal Admin module. These values flow to Accounts Receivables for further processing. Requesting Agency's TAS, BETC, and additional information attributes are sent along with invoice details to Receivables.

The performance obligation order lines display several attributes that are non-editable. You can enter a few fields as explained here:

  1. Select or enter the Top Task Number for each PoBG Order line schedule. Assigning Top task to PoBG Line is mandatory. A unique top task number must be chosen.

  2. Select or enter TAS for Servicing Agency for each order line. This value transfers to AR for further processing. This is a mandatory field.

  3. BETC (Servicing Agency) is auto-selected on selecting the TAS value. This value transfers to AR for further processing.

    TAS and BETC values are populated depending on the Servicing Agency's Agency Location Code (ALC). With the Organization Group Hierarchy, the associated group with orders drive TAS and BETC values available for selection. You can modify the group for the agreement until the performance obligation is published.

  4. Click Additional Attributes (User Defined Attributes - UDA).

  5. Click Receipts icon to view receipt details.

  6. Save.

Oracle Projects publishes performance obligations. Publishing of PoBG generates funding.

Defining Performance Obligation Additional Attributes

The system defaults and displays values specified for requesting agency. You cannot modify them.

  1. In the Schedule Funding region, select or enter the following information:

    • Servicing agency Object Class Code

    • Servicing Agency Additional Accounting Classification

    • Description of products Including BonaFide Need for this Order.

  2. In the SLOA region, select or enter the following fields for a servicing agency:

    1. Servicing Agency Federal Award Identification Number (FAIN)

    2. Servicing Agency Unique Record Identifier (URI)

    3. Servicing Agency Activity Address Code - This field is optional. If you specify a value, then it must be a minimum of 6 characters.

    4. Servicing Agency Budget Line Item

    5. Servicing Agency Budget Fiscal Year

    6. Servicing Agency Security Cooperation

    7. Servicing Agency Budget Fiscal Year

    8. Servicing Agency Sub-Allocation

    9. Servicing Agency Accounting Identifier

    10. Servicing Agency Funding Center Identifier

    11. Servicing Agency Cost Center Identifier - This field is optional. If you enter a value, the value must match the Cost Center value provided in the parent GT&C.

    12. Servicing Agency Cost Element Code

    13. Servicing Agency Work Order Number

    14. Servicing Agency Functional Area

    15. Servicing Agency Cooperation Case Designator

    16. Servicing Parent Award Identifier (PAID)

    17. Servicing Procurement Instrument Identifier (PIID)

    18. Servicing Security Cooperation Case Line Item Identifier

    19. Servicing Agency Disbursing Identifier Code

    20. Servicing Agency Accounting Classification Reference Identifier - This field is optional. If you specify a value, then it must be a minimum of 2 characters.

    21. Servicing Agency Project identifier

    22. Servicing Agency Reimbursable Flag

  3. In the Schedule Shipping Information region, select or enter the following fields for a Servicing Agency Additional Information:

    1. Ship to Address Identifier

    2. Ship to Address 1

    3. Ship to Address 3

    4. Ship to Postal Code

    5. Ship to Country Code

    6. Special Shipping Information for Product

    7. Shipping Information for Product POC Title

    8. Shipping Information for Product POC Phone

    In the Schedule Shipping Information region, select or enter the following fields for the Requesting Agency Additional Information:

    1. Ship to Agency Title

    2. Ship to Address 2

    3. Ship to City

    4. Ship to State

    5. Ship to Location Description

    6. Shipping Info for Product POC Name

    7. Shipping Information for Product POC Email

Retain Project Association on the Rejected Order

Oracle EBS G-Invoicing now allows retaining project associations for a rejected order. When an agreement is submitted for approval, the approver can reject the order. When the approver rejects an agreement, the agreement status shows rejected but the project association is retained for the rejected order as shown in the Update Agreement page. The rejected order status is pushed to federal G-Invoicing. The requesting agency can modify the draft and approve. Similarly, you can also perform the reject order for order modifications by retaining the project association.

Prerequisite: The agreement must be submitted for approval.

To reject an order, perform the following:

  1. Log in as the workflow approver or use your email notification.

  2. Open the respective agreement approval notification.

  3. Click Reject to reject the agreement.

  4. In federal G-Invoicing, the requesting agency can select Return to Draft and modify the order.

    The version number is unchanged for such orders.

  5. After modifying the order, submit it for requesting agency approval.

  6. The requesting agency approves the order and shares it with the servicing agency.

  7. From the Projects Super User responsibility, run the Intragovernmental Order Interface Program to pull the order into EBS. (Navigation: Select Requests, then Schedule, then Submit a Request.

    The order is pulled in to EBS as an updated order with all the project association details retained.

G-Invoicing Order Approval – Funds Check and Allocation

Oracle E-Business Suite G-Invoicing provides a facility to enable funds availability confirmation to allocate and fulfill an order. If funds are available, then the system confirms funds allocation, baselines funding and pushes order to the federal G-Invoicing application.

When the agreement approval is initiated, the system validates funds availability and allocation status by calling the client extension, PA_Client_Extn_IGT_Cust.Return_Ord_Fund_available(). If funds are available, then the system approves the agreement, baselines funding and the order is pushed to the federal G-Invoicing application. If funds are not available or allocated, then the system approves the agreement, allocates funding, and the Internal Status displays Pending Funds Check.

In such cases, agencies must manually manage the funding allocation and indicate funds availability. The Update Agreement page includes Confirm Funds Availability in the Actions dropdown list.

You can also use the public API PA_IGT_EXT_API_PUB.CONFIRM_FUNDS_AVAILABLE(), to confirm funds availability.

To confirm funds availability manually for orders with Pending Funds Check status, perform the following steps:

  1. From Home, select the Projects Super User, US Federal responsibility.

  2. Click Enterprise Command Center and then Projects Command Center.

  3. Click G-Invoicing dashboard tab.

  4. In the G-Invoicing dashboard, refine your search to retrieve orders with the internal status as Pending Funds Check.

  5. Click the Update Agreement icon.

    The Confirm Funds Availability option in the Actions menu is activated for such orders.

  6. From the Actions drop down list, select Confirm Funds Availability.

  7. Click Go.

Funds Check and Allocations for Non-Advance Enabled Orders

Following is the funds check and funds allocation flow for non-advance enabled orders:

the picture is described in the document text

For non-advance enabled orders, perform the following:

Funds Check and Allocations for Advance Enabled Orders

Following is the funds check and funds allocation flow for advance-enabled orders:

the picture is described in the document text

For advance-enabled orders, perform the following:

After the funds are available, the funding is baselined, and the order is pushed to the federal G-Invoicing application with the REC status. You can then request for advance performance against the order and settle the same in iPAC. After advance is settled, funding is allocated, and budget is baselined.

Funds Check and Allocations for API Support Flow

Following is the funds check and funds allocation flow for API Supported orders:

the picture is described in the document text

For advance-enabled orders, perform the following:

Funds Check and Allocations for Buyer Initiated orders (Non-Advance) Flow

Following is the funds check and funds allocation flow for buyer initiated new orders (BIOs):

the picture is described in the document text

For non-advance enabled orders, perform the following:

Rules and Validations

API Support for G-Invoicing Flows

Oracle Projects provides following Application Programming Interface (APIs) to create and update agreements, create and associate projects, and perform additional attribute changes to performance obligation lines and uptake order modifications. These APIs provide alternative methods to perform various actions from the Enterprise Command Centers.

Oracle Projects provides the following APIs:

Create IGT Agreement API

Use this API to create an intragovernmental (IGT) agreement and link it with an IGT order.

This API has the following technical name:

Update IGT Agreement API

Use this API to update an intragovernmental (IGT) agreement.

This API has the following technical name:

Associate Project to IGT Order API

Use this API to associate a project with an IGT order. The specified IGT order must not have an associated project already.

This API has the following technical name, prerequisite, and outcome:

Update Order Header/Line Schedule and Additional Attributes (UDAs) API

Use this API to update additional attributes maintained in the UDA (User Defined Attributes) framework. This API updates the agreement and header additional attributes along with POBG and order line schedules.

This API has the following technical name and prerequisite:

Submit Order Performance API

Use this API to submit all performances (deferred, delivery and advance) at the order, order line, order lines schedule levels.

This API has the following technical name and prerequisite:

Order Modification Uptake API for IGT Agreement

Use this API to uptake order modifications.

This API has the following technical name, prerequisite, and outcome:

Update POBG Lines API for IGT Projects (TAS/Task/Line)

Use this API to update performance obligation lines and line schedules.

This API has the following technical name and prerequisite:

Update Additional Attributes API for IGT Projects (Order header/OLS)

Use this API to update additional attributes maintained in the UDA framework. This API updates the agreement and header attributes along with POBG and order line schedules.

This API has the following prerequisite:

Submit IGT Agreement API

Use this API to submit the IGT Agreement for Approval.

This API has the following technical name, prerequisite, assumptions, and outcome:

Public Views for IGT Staging Tables and UDAs

Use this API to view the following tables:

This API supports the following views:

Associate Agreement with IGT Orders

Use this API to associate agreement with IGT orders. The OKE created orders requires agreements to be approval-enabled and the funding is generated after the order approval. To support approval-enabled agreement types, the Create IGT Agreement, Update IGT Agreement, and Add Funding APIs have been enhanced.

You can also indicate an agreement as advance-enabled using this API.

Reject IGT Orders

Use this API to reject an IGT order and order modification. Pull the order for reject flow to API created OKE orders. OKE creates contract agreement and updates data in the staging tables. Submit the Reject IGT Order API to reject the agreement and push it back to the Federal G-Invoicing application with the Rejected status.

Outright Order Rejection API without Agreement and Project association

Use this API to reject the order agreement and push the IGT order back to federal G-Invoicing with the rejected status. You can submit the rejection with or without an agreement.

The API has following technical name, prerequisites, outcome, and validation:

Client Extension for Seller Order Number in SFO

Oracle EBS G-Invoicing provides the following client extension to create the seller-facilitated order number. The system first looks for the seller order number, the system uses it if one is specified. If it is not specified, then the system looks for any client extension specified. If it exists, then the system uses the client extension.

You can edit and modify the seller order number field on the Create Seller Facilitated Orders page. After the order is saved you cannot modify the value. The seller order number cannot exceed 20 characters.

The following client extension is added:

Modification to Mass Submission of Performance

Oracle EBS G-Invoicing provides the ability to override preparer attributes, performance date and comments during mass performance submission using a client extension. The following client extension is added:

Based on the performance role selected in the G-Invoicing Setup page, default preparer information is retrieved.

Modification to the Refund Process

Oracle EBS G-Invoicing provides the ability to customize the refund process using a client extension. Using this client extension, you can skip the standard refund process and perform the refund activities manually. The following client extension is added:

Reusing Additional Attributes (User Defined Attributes UDA) Pages

To uptake UDA self-service pages, for both at the header and schedule-level UDA attribute access, perform the following steps:

Prerequisites

Verify the agreement is linked with the IGT Order.

  1. To access the header UDA page, pass the following mandatory parameters:

    • “orderNum" indicates the order number for which the UDA attributes are updated.

    • "fromPageURL" indicates the URL being retrieved.

    Specify the path in the following format:

    OA.jsp?page= indicates the page name with the fully qualified path.

    For example, a sample code is shown below:

    OA.jsp?page=/oracle/apps/pa/pobg/webui/ExtAttrPageRegionWrpPG&retainAM=Y)

    Specify the complete path as shown below:

    OA.jsp?page=/oracle/apps/pa/pobg/webui/ExtAttrPageRegionWrpPG&orderNum=1234&fromPageURL=OA.jsp?page=/oracle/apps/pa/pobg/webui/ExtAttrPageRegionWrpPG

  2. To access the schedule-level UDA page,pass the following mandatory parameters:

    • "orderNum" indicates the order number.

    • “lineNum” indicates the line number of the order.

    • “schdNum” indicates the schedule number for which you want to update the schedule-level UDA attributes.

    • "fromPageURL" indicates the URL being retrieved.

    Specify the path as shown below:

    OA.jsp?page= indicates the page name with the fully qualified path.

    For example, a sample code is shown below

    OA.jsp?page=/oracle/apps/pa/pobg/webui/ExtAttrPageRegionWrpPG&retainAM=Y)

    Specify the complete path as shown below:

    OA.jsp?page=/oracle/apps/pa/pobg/webui/ExtAttrPageRegionWrpPG&orderNum=1234&lineNum =1& schdNum =1&fromPageURL=OA.jsp?page=/oracle/apps/pa/pobg/webui/ExtAttrPageRegionWrpPG

Using Performance in G-Invoicing

When an order between the servicing agency and requesting agency is fulfilled, the progress of an order is tracked against the order line schedule and communicated to the requesting agency as performance. When the reported performance is accepted by the requesting agency, that performance is tracked by the servicing agency as approved.

Use the following features to manage performances and drive settlement by deriving and reporting accurate progress and delivery.

Prerequisites

Verify that you have setup preparer details to default before using performance. Refer to the "G-Invoicing Setup Options" topic in the Oracle Projects Implementation Guide for details.

Performance Management

Oracle Projects supports performance management by enabling the following actions:

This feature helps you manage Performance between the buyer and seller with the Federal agencies.

Working with Performance Obligations

The Performance Obligation page displays all performance obligations details.

To see performance obligation lines, select a single performance obligation in the Performance Obligations region.

To submit performance obligation lines, select lines in the Performance Obligation Lines region and then choose to submit advance, deferred, or delivery performance. For more information, see:

To generate funding against performance obligation lines based on applied receipts, select Generate Funding from the Actions menu. This option is available only for advance-enabled orders. For more information about generating funding, see

To edit or update performance obligations, select Update from the Actions menu. For more information about updating performance obligations, see "Defining Performance Obligation Additional Attributes".

To view the version history of a performance obligation, select View History from the Actions menu.

To view the performance history, select View Performance History from the Actions menu.

Note: To submit multiple (mass submission) performances for advance and non-advance orders, use the PRC: Mass submission performances for G-Invoicing concurrent program. Refer to the Submitting Performance for Multiple Orders section in the Running Interface Programs topic in this chapter.

Using Deferred Performance

For each performance obligation line, revenue generated is mapped to a deferred performance. Oracle Projects lets you send progress generated at the performance obligation line (order line schedule) as deferred performance to G-Invoicing. The requesting agency pulls the updated order information from G-Invoicing, but this has no impact on the financial transaction with respect to G-Invoicing. You can edit attributes and select attachments.

Impact on Accounting

A the project-level contract asset (CA) and contract liability (CL) and UBR - unbilled receivable and UER - unearned revenue balances are maintained. For revenue generation, the UBR and UER accounting is run instead of CA and CL accounting. The performance obligation ID and number are passed to revenue and invoice programs as auto-accounting parameters for all accounting events.

High Level Flow for Deferred Performance

Before you can submit deferred performance for a project, you must complete the following high-level steps:

  1. Search for projects.

  2. Incur actual transactions, such as expenditure or events.

  3. Generate revenue and revenue accounting events.

  4. Generate progress at the performance obligation lines using the revenue distribution line. See Generating Deferred Performance.

  5. Update additional attributes on the Submit Deferred Performance page.

  6. Submit deferred performance.

  7. Performances are pushed to the federal G-Invoicing application.

Generating Deferred Performance

Perform the following tasks before submitting a deferred performance:

To submit deferred performance:

  1. Navigate to the G-Invoicing Dashboard selecting the Projects Super User, US Federal responsibility.

  2. Click the Projects Command Center, and then G-Invoicing.

  3. Search for the order.

  4. Scroll down to the Header component and click Orders in the GT&C Order region.

  5. Click the Create Project icon.

  6. Search a template to create a project using that template.

    The Create Project: Select Source page appears.

  7. Search for and select a template to base the new project on.

  8. Click Continue.

    The Create Project: Details page appears.

  9. Enter the required fields. These depend on how the Quick Entry fields are configured, but may include Project Number, Project Name, Project Start Date and Project End Date.

  10. Click Finish.

    The Processing: Creating Project page appears. Wait for the request to be processed.

  11. Navigate to the Performance Obligation page.

  12. Select the performance obligation.

  13. Scroll down to the performance obligation lines.

  14. Select or enter the top task number.

  15. Select or enter the TAS value.

  16. Click Save and then Continue.

  17. Repeat Steps 12 through 15 for all the other performance obligation and PoBG lines.

  18. Click the G-Invoicing Dashboard icon on the top of the page to navigate back to the G-Invoicing home page.

  19. Click the Update Agreement icon in the Order region.

    The Update Agreement page appears.

  20. Enter the billing frequency value. This a mandatory field. If you select Others, then you must provide an explanation.

  21. Select Additional Agreement Attributes from the Actions menu and click Go.

  22. Enter servicing agency details in the Funding Approval, Program Approval, and Preparer information in the corresponding regions.

  23. Click Apply to submit the agreement for approval.

  24. Log in as the approver and approve the agreement.

  25. Navigate to the Federal G-Invoicing application.

  26. Query the order and check the Order Status.

  27. Run the ECC Incremental Data Load.

  28. Navigate to the Projects G-Invoicing dashboard by clicking the Projects Super User, US Federal responsibility, and then click Projects Command Center, and then G-Invoicing.

  29. Navigate to Expenditure and create actual expenditure task of specified quantity for few tasks.

  30. Conditional: For work-based revenue, submit and release the expenditure batches.

  31. Run the applicable cost distribution programs, such as the PRC: Distribute Labor Cost distribution .

  32. Conditional: If you are using event-based revenue, then you must create an event for a task. If you are not using event-based revenue, then this step is optional.

  33. To submit deferred performance, you must first generate revenue and approve it.

    • Run the PRC: Generate Draft Revenue for a Single Project .

    • Review the revenue by using the Review Revenue option.

    • Click Release on the Review Summary window to release the revenue.

    • Click Save.

  34. Run the PRC: Generate Revenue Accounting Event , which generates the deferred performance lines.

  35. Navigate to the Projects G-Invoicing dashboard by clicking the Projects Super User, US Federal responsibility, and then click the Projects Command Center, and then G-Invoicing.

  36. Query the order.

  37. Select View Performance Obligation by scrolling down and selecting the Orders tab.

  38. Select the performance obligation lines.

  39. Select Submit Deferred Performance from the list and click Go.

    The Submit Deferred Performance page appears.

Submitting Deferred Performance

The Submit Deferred Performance page appears where you submit the performance. The deferred performance transaction lines are generated. Each performance line maps to one order line schedule.

Submit Deferred Performance Page

the picture is described in the document text

  1. In the Header region, the preparer details are defaulted from the previously specified values. If the default value is not set up, then enter the preparer's name, phone number, and email address.

  2. In the Date field, enter a performance date between the order start and end dates.

  3. Select the accounting period that is open. The list of values lists all the periods that are open in that accounting period.

  4. The Transaction table displays the following columns:

    Column Description
    Order Number Indicates the unique number assigned to the selected order.
    Order Line Number Indicates the line number of the order used.
    Order Line Schedule Number Indicates the line number of the order used.
    Unit of Measure Displays the selected UOM.
    Performance Quantity Displays the quantity the performance can be submitted for.
    Performance Indicator Indicates whether the performance is Partial Performance or Final Performance. You can choose one of the two options.
    Attachment Lets you add attachments.

  5. Click Submit to submit the deferred performance.

    The View Performance Obligation page reappears.

  6. Enter the order number and click Go to track the performance status.

    You can track the Performance Submission status for the deferred performance lines. After the G-Invoicing application receives and accepts the deferred performance, the status changes and the performance header number populates after acknowledgement from the G-Invoicing application.

  7. Click Submit

    When performance is submitted, it triggers the PRC: Submit Intragovermental Performance in the background. This runs the MGT: Push Performance XML Generation and then the interface program to G-Invoicing, Intragovermental Performance parent . Performances are collected, and for each performance a child is run.

    You can query the order number in the View Performance Obligation page. View the Status updated to Success and Performance Header Number and Performance Detail Number are generated dynamically after the performance is submitted successfully.

  8. You can track the performance list submitted in the G-Invoicing application by clicking the Requesting Agencytab, then Options, and then Performance List.

  9. Navigate to Projects Super User, Federal responsibility, and then click Billing, then Review Revenue, and then Open to view the Unbilled Receivables and Unearned Revenue.

  10. Click Lines to view the revenue lines details at the line-level.

Using Delivery Performance

Delivery Performance lets you send progress generated at the performance obligation line (order line schedule) as delivery performance to the federal G-Invoicing application.

Invoices generated against each of the performance obligation line is mapped to a delivery performance. This performance notifies the progress of an order and initiates financial transactions to and from the federal G-Invoicing application.

The servicing agency initiates the submission of performance and pushes it to the federal G-Invoicing application, where it is then pulled by the requesting agency. Depending on the FOB point set up, the acceptance of the performance is tracked.

High-Level Flow for Delivery Performance

Delivery performance has the following overall flows:

  1. Incur actual transactions, such as expenditure or events.

  2. Generate revenue.

  3. Generate progress at the performance obligation lines using the Revenue Distribution Line.

  4. Includes summaries of progress at the header and agreement levels.

  5. Generate draft invoices.

  6. Interface invoices to Oracle Receivables.

  7. Apply advance receipts. This step is optional and applicable only for projects that service advance-enabled orders. For projects that service non-advance-enabled orders, you can submit the deferred and delivery performances.

  8. Run the PRC: Tieback Invoices from Receivables concurrent program.

  9. Create acceptance in Oracle Receivables.

  10. View performance.

  11. Update additional attributes on the Submit Delivery Performance page.

  12. Submit delivery performance.

  13. Receive acceptance from the federal G-Invoicing application.

  14. Adjust invoices, if needed.

Generating Delivery Performance

To generate delivery performance, complete the following steps:

  1. To generate a draft invoice, submit the PRC: Generate Draft Invoice for a Single Project concurrent program.

  2. Select Invoice Review. Query the project number.

    1. Approve and save.

    2. Release the invoice and save.

  3. Run the PRC: Interface Invoice to Receivables concurrent program.

  4. Run the Autoinvoice Import Program.

  5. Run the PRC: Tieback Invoices from Receivables concurrent program, which creates the delivery performance.

  6. Navigate back to the Performance Obligation window.

  7. Select the performance lines.

  8. Select Submit Delivery Performance and click Go.

    The Submit Delivery Performance page appears.

Submitting Delivery Performance

The Submit Delivery Performance page appears where you submit the performance. Oracle Projects generates delivery performance transaction lines.

Submit Delivery Performance Page

the picture is described in the document text

  1. In the Header region, the preparer details are defaulted from the previously specified values. If the default value is not set up, then enter the preparer's name, phone number, and email address.

  2. In the Date field, enter a performance date between the order start and end dates.

  3. Select the accounting period that is open. The list of values lists all the periods that are open in that accounting period.

  4. The Transaction region includes the following fields:

    Column Description
    Draft Invoice Number Displays the invoice number assigned.
    Draft Invoice Line Indicates the invoice line number.
    Transaction Source Displays the source of the transaction, such as an expenditure or an event.
    Order Number Indicates the unique number assigned to the selected order.
    Order Line Schedule Number Indicates the line number of the order line schedule that is being used.
    Unit of Measure Displays the selected UOM.
    Performance Quantity Indicates the quantity the delivery performance is to be submitted for.
    Performance Indicator Indicates whether the performance is Partial Performance or Final Performance. You can choose one of the two options.
    Attachment Lets you add attachments.

  5. Submit the Performance.

    You are taken back to the View Performance History page.

  6. Query the order number and click Go.

    Transaction displays the deferred performance and delivery performances submitted. If there are multiple delivery lines for a single schedule line, then it is reported in a separate XML file.

    Adds details on how they are added as single line and separate line in XML.

    When the performance is submitted, it triggers the PRC: Submit Intragovermental Performance concurrent program in the background. This program runs the MGT: Push Performance XML Generation and the interface program to G-Invoicing, Intragovermental Performance parent . Performances are collected and Oracle Projects runs a child for each performance.

    You can query the order number in the View Performance Obligation page. You can see the status updated to Success, and the Performance Header Number and Performance Detail Number are generated dynamically after the performance is submitted successfully.

Once delivery performance is submitted, the delivery performance lines are deleted.

Performance Lines Submission Failure: The Status field on the View Performance History page includes fail value and displays Failure for the failed performances. An appropriate rejection reason is displayed in the Reason field. You can resubmit the failed performance in the subsequent performance interface program runs.

Reverse Deferred Performance During Delivery Performance

Oracle Projects calculates the latest deferred performance when generating the delivery performance. When a delivery performance is submitted, Oracle Projects submits both the latest deferred performance and delivery performance consecutively. The deferred performance is also recalculated.

Oracle Projects verifies if the performance date is in the current accounting period and recalculates deferred performance.

Order Modification and Incremental Performance Load

To modify an order after you have submitted performance, complete the following steps:

  1. Modify the order and submit it for approval.

    • Navigate to the Federal G-Invoicing page.

    • Query the order for which you submitted performance.

    • Click Modify option to change the order.

      Note: After performance is submitted you cannot modify the unit cost of the item.

    • Modify the quantity.

    • Click the Update Draft option.

    • Click Submit for Requesting Approval.

      The draft order modification is submitted for requesting agency approval.

  2. Obtain approval from the requesting agency.

    • Enter required parameters and click Requesting Agency Approve option.

  3. Run the Intragovermental Orders Interface Program concurrent program to pull the orders into Oracle Projects.

  4. Run the Projects G-Invoicing ECC Data Load concurrent program.

  5. Navigate to the G-Invoicing dashboard click the Projects Super User, US Federal responsibility, and then Projects Command Center, then click G-Invoicing.

  6. Scroll to the GT&C and Orders region.

  7. Click the Orders tab and select the Order option.

  8. Click the Actions (Three Ellipses) menu and select the Order Modification Uptake.

    Order Modification uptake is completed.

    Order Modification Uptake

    the picture is described in the document text

  9. Select the View Performance Obligation icon in the Orders tab.

    The Performance Obligation page appears.

  10. Click the Update on the top right to uptake the modification.

  11. Associate the top task and TAS with the new order line schedule.

  12. Click the G-Invoicing Dashboard icon to return to the Home page.

  13. Select Update Agreement from the Orders tab to create and approve the agreement.

  14. Select Additional Agreement Attributes from the Actions menu and click Go.

  15. Modify any Servicing Agency parameters that you want to change.

  16. Click Apply and then Submit.

  17. Log in and approve the agreement.

  18. Check the Order Status in the Federal G-Invoicing application.

  19. Run the Projects ECC G-Invoicing incremental data load.

  20. Query the order in the Federal G-Invoicing application and check the status to ensure that it is Open.

  21. Incur events or expenditures.

  22. To submit deferred performance, you must first generate revenue and approve it.

    1. Run the PRC: Generate Draft Revenue for a Single Project .

    2. Review the revenue by clicking Review Revenue option.

    3. Click Release button on the Review Summary window to release the revenue.

    4. Click Save.

  23. Run the PRC Generate Revenue Accounting Event concurrent program, which generates the deferred performance lines.

  24. Navigate to the Projects G-Invoicing dashboard by clicking the Projects Super User, US Federal responsibility, and then click Projects Command Center, and then G-Invoicing.

  25. Query the order.

  26. Select View Performance Obligation by scrolling down and selecting the Orders tab.

  27. Select the performance obligation lines.

  28. Select Submit Deferred Performance from the list and click Go.

    The Submit Deferred Performance page reflects the modified quantity.

  29. Enter the header details.

  30. Select Partial Performance.

  31. Click Submit.

  32. Query the order and click Go.

    The status changes to Submitted.

  33. Generate the invoice by submitting the PRC: Generate Draft Invoice for a Single Project concurrent program.

  34. Select Invoice Review. Query the project number.

    1. Approve and save.

    2. Release the invoice and save.

  35. Run the PRC: Interface Invoice to Receivables concurrent program.

  36. Run the Autoinvoice Import Program.

  37. Run the PRC: Tieback Invoices from Receivables concurrent program, which creates the delivery performance.

  38. Navigate back to the Performance Obligation page.

  39. Select the performance lines. .

  40. Select the Submit Deferred Performance and click Go

    The Submit Delivery Performance window displays the delivered performance.

  41. Transaction displays the delivery performance and delivery performances submitted. If there are multiple delivery lines for single schedule line, then it is reported in a separate XML file.

  42. Query the order number and click Go.

  43. Select the performance lines

  44. Select Submit Deferred Performance and click Go.

  45. The Submit Delivery Performance Page appears.

    The Performance Quantity is displayed as the Unit Price / Quantity.

  46. Enter the required parameters in the header.

  47. Select Partial Performance as the Performance Indicator.

    You are taken back to the View Performance History page.

  48. Click Submit.

  49. Query the order number and click Go.

    The Delivery Performance line shows as submitted.

  50. To view unbilled and unearned revenue, navigate to the Projects Super User, US Federal responsibility, and then click Billing, then Review Revenue, and click Open to view the Unbilled and Unearned Revenue.

  51. Click Lines to view revenue details at the line-level.

  52. Query the order number and click Go.

    The status changes to Success after the delivery performance is successfully transferred to the federal G-Invoicing application.

Using Advance Performance

You can submit advance performances only for advance-enabled orders. For advance-enabled orders, all order line schedules are also advance enabled. The delivery progress is reported through to funding, and funding is calculated based on applied receipts. The cost budgets cannot exceed the funding value. To submit advance performances, you capture advance payments from accounts receivable receipts against each performance obligation line, generate the advance performances, and acknowledge the performance by sending them back to the requesting agency through the federal G-Invoicing application.

Anytime an advance receipt is available for a project or order, it is successfully accepted in Accounts Receivable. You can submit partial or full advance performances. When you request a full advance, Oracle Projects submits the performance automatically and you can view the transaction details on the Performance History page. You can also submit adjustments against the advance performance.

High-Level Flow for Advance Performance

The following diagram illustrates the overall advance performance flow.

The Advance Performance Flow

the picture is described in the document text

The Advance Performance submission process involves both automatic and manual steps.

To begin, perform the following steps:

  1. Make sure that the order is approved.

  2. On the Performance Obligation page, select the order line schedule for which you want to submit advance performance.

  3. Select the type of advance performance that you want to submit:

    • Full Advance

      For a full advance, click Submit.

      Oracle Projects automatically creates and submits performance lines, displays the submission details on the Performance History page, and pushes the performance to the federal G-Invoicing application.

    • Partial Advance

      For a partial advance, perform the following steps:

      • Manually select the POBG order line schedules.

      • Enter the quantity for the advance performance.

      • Click Submit.

    Oracle Projects initiates the Intragovernmental Performance Interface concurrent program, which pushes the performance to G-Invoicing.

  4. Request Partial Advance (Select Performance Obligation Lines):

    • When you select Request Partial Advance, select the POBG order line schedules. You must perform this manually.

    • Submit Advance Performance: Enter the quantity for advance performance and click Submit. This is a manual step.

    • Oracle Projects initiates the Intragovermental Performance Interface concurrent program and pushes performances to G-Invoicing.

For both full and partial advance performances, the remaining steps in the process are automatic

  1. IPAC Settlement captures settlements done by intragovernmental payments and collections (IPAC) for all performance types.

  2. The pull performance program creates accounts receivable receipts, applies them against the order line schedule as prepayment, and generates funding for the project.

To request a partial or full advance, select the order line schedule and choose Submit Partial Advance or Full Advance. If a partial quantity is already submitted for advance, then Oracle Projects calculates the balance advance and submits the advance performance.

On the performance obligation page, you identify order line schedules against which advances must be submitted and then request partial advance. On the Submit Advance Performance page, enter the advance quantity against the order line schedule and submit the advance. The performance quantity must not exceed the balance quantity. The balance quantity is calculated as:

 (Balance Quantity = total Order Line Schedule Quantity – Total  submitted Advance Performance Quantity)

Create Revenue Budget Manually

To manually create and manage revenue budget, set the personal profile option, PA: Manage Revenue Budget Manually, to Yes.

To set the new profile option:

  1. Navigate to the System Administrator responsibility.

  2. Select Profile, then Personal.

  3. Click View and then Find.

  4. Query for the profile options, PA: Manage Revenue Budget Manually.

  5. Set the value to Yes.

Pushing Budget to G-Invoicing after Revenue Budget is Baselined

EBS G-Invoicing includes a profile option, Confirm Funds Availability upon Revenue Budget Baseline, that lets you manually baseline the revenue budget. If you set the profile option value to Yes, then you baseline the revenue budget and the system automatically marks the agreement with available funds. After the budget is baselined, it is then automatically pushed to federal G-Invoicing. If the profile option value is set to No, then the agency must manually confirm the funds availability.

Submitting Advance Performance (Partial)

When you select Request Partial Advance and click Go, the Submit Advance Performance page appears.

Submit Advance Performance Page

the picture is described in the document text

In the Submit Advance Performance page, enter the following details:

  1. In the Header region, the preparer details are defaulted from the previously specified values. If the default value is not set up, then enter the preparer's name, phone number, and email address.

  2. In the Date field, enter a performance date between the order start and end dates.

  3. Select the accounting period that is open. The list of values lists all the periods that are open in that accounting period.

  4. The Transaction region includes the following fields:

    Column Description
    Draft Invoice Number Displays the invoice number assigned.
    Draft Invoice Line Indicates the invoice line number.
    Transaction Source Displays the source of the transaction, such as an expenditure or an event.
    Order Number Indicates the unique number assigned to the selected order.
    Order Line Schedule Number Indicates the line number of the order line schedule that is being used.
    Unit of Measure Displays the selected UOM.
    Performance Quantity Indicates the quantity the delivery performance is to be submitted for.
    Performance Indicator Indicates whether the performance is Partial Performance or Final Performance. You can choose one of the two options.
    Attachment Lets you add attachments.

  5. Click Submit.

    You are taken back to the View Performance History page where you can view the advance performance transaction details.

  6. Refresh until the Status changes to Success.

    The Status updates to Success and the Performance Header Number is assigned.

  7. Navigate to the Federal G-Invoice.

  8. Query the order and click Options, and then Performance List.

  9. Select the Servicing Agency Performance List details.

    The Performance Number displays as the Performance Header Number on the View Performance History page in the Projects G-Invoicing dashboard.

    You can verify if the attachments are interfaced to the servicing agency by clicking Options, and then Attachment. Displays the attachment details, such as File Name, Uploaded By, Date the file was uploaded, Uploading Party if it is by the Servicing or Requesting Agency.

Submitting Adjustment Performance

Oracle Projects lets you submit adjustment to advance performance for the selected performance obligation lines.

To submit adjustment against an advance performance, you must enter a negative quantity, description, and original performance reference number for the selected order lines along with the preparer details for that accounting period.

The View Performance History page displays the transaction details and status.

Once the IPAC settlement completes, the pull performance creates prepayment receipts, applies them to the order line schedules and generates funding automatically for the project. For a refund or adjustment transaction, the pull performance un-applies the receipt amount and reduces the funding amount from the originally applied receipts. The amount of negative advance performance must be lesser than or equal to the delivered advance quantity.

If the advance performance results in a failure, then you can delete these transactions or resubmit them in the next performance run from the performance history page.

In the Performance Obligation page, select the Refund Advance option and click Go, Oracle Projects takes you to the Submit Adjustment Performance page.

The Submit Adjustment Performance Page

the picture is described in the document text

In the Submit Adjustment Performance page, enter the following details:

  1. In the Header region, the preparer details are defaulted from the previously specified values. If the default value is not set up, then enter the preparer's name, phone number, and email address.

  2. In the Date field, enter a performance date between the order start and end dates.

  3. Select the accounting period that is open. The list of values lists all the periods that are open in that accounting period.

  4. The Transaction region includes the following fields:

    Column Description
    Draft Invoice Number Displays the invoice number assigned.
    Draft Invoice Line Indicates the invoice line number.
    Transaction Source Displays the source of the transaction, such as an expenditure or an event.
    Order Number Indicates the unique number assigned to the selected order.
    Order Line Schedule Number Indicates the line number of the order line schedule that is being used.
    Unit of Measure Displays the selected UOM.
    Quantity Indicates the quantity the delivery performance is to be submitted for. This should be in negative for refund performance.
    Total Advance Performance Quantity Indicates the total advance performance quantity that was already submitted.
    Transaction Price Indicates the unit price derived from Order Line Schedule.
    Adjust Quantity Enter the quantity the adjustment can be submitted for. This is a mandatory field.
    Adjust Amount Displays the total price of the adjustment quantity. Based on the user entered adjustment quantity, and unit price the adjust amount is derived.
    Reference Performance Indicates the adjustment reference number. This is a mandatory field.
    Reference Quantity Indicates the reference quantity.
    Description  
    Performance Indicator Indicates whether the performance is Partial Performance or Final Performance. You can choose one of the two options.
    Attachment Lets you add attachments.

  5. Select an attachment and click Apply. The attachment is added.

  6. Submit the adjustment.

    You are taken back to the View Performance History page where you can view the adjustment advance performance transaction details.

Using Refund Pay Group

Agencies can now check refunds created against delivery and advance payments using pay groups.

The G-Invoicing Setup page include a Refund Pay Group option. While creating the adjustment for a delivery or advance payment, the system considers the Refund Pay Group value set up either at the project or operating unit level. If the project level pay group is setup, then it takes precedence over the operating unit level pay group setup. Once the refund adjustment transaction completes, you can view pay group values at the payables invoice level.

Setting Up Refund Pay Group

The G-Invoicing Setup page (Navigation: click Projects Super User Federal, click Projects: Setup, and then G-Invoicing Setup) includes a new option Refund Pay Group. This option is available at the operating unit and project level (Navigation: click Project, then Setup, specify Refund Pay Group value) as well.

You can set this option at both operating unit and project levels. After the first refund transaction is created, you will not be able to change the selected value from the refund pay group LOV at the project level. Whereas you can modify the value at the operating unit level.

The G-Invoicing Setup page at the project-level includes the Refund Pay Group option.

The system sends the pay group values to both receipts (Receivables) and invoices (Payables). You can view the Pay Group details on receipts (Navigation: switch to the Oracle Receivables responsibility, select Receipts, and search by the receipt number). You can get the receipt number from the View Performance History page after the receipt is created. Click Apply to view the amount applied and receipts created. Then, click the Refund Attributes button to view the refund pay group details.

The refund also creates a payable invoice. Get the invoice number by clicking the Refund Status button from the Receipts: Applications page. You can view the Pay Group details on invoices (Navigation: switch to the Oracle Payables responsibility, select Invoices, and query the invoice). The pay group details appear on the Invoices window.

Intragovernmental Payment and Collection (IPAC) Settlement

Federal Agencies use Intragovernmental Payments and Collections (IPAC) to transfer funds between agencies. The Intragovermental Performance Interface pull program considers settlements performed by IPAC for all performance types.

IPAC Settlement – For Advance-Enabled Orders

The following diagram shows the IPAC settlement flow for advance-enabled orders:

IPAC Settlement in Advance Enabled Orders

the picture is described in the document text

For advance-enabled orders, the Intragovernmental Performance Interface concurrent program pulls the settlement information from the federal G-Invoicing application. This program automatically generates receipts for positive performance based on settlement amounts from IPAC. The program also applies receipts as prepayment. For advance settlement, the program automatically generates and baselines funding after applying the receipt on prepayments at the performance obligation levels.

If the performance is a negative transaction, then the pull program un-applies receipts in prepayments for the settled amount, and then creates a refund for the adjusted settled amount. An AP invoice is generated automatically, and the payment is accounted.

IPAC Settlement for Orders that are Not Advance Enabled

The following diagram shows the IPAC settlement flow for orders that are not advance-enabled:

IPAC Settlement for Orders that are Not Advance Enabled

the picture is described in the document text

For orders that are not advance-enabled, the Intragovernmental Performance Interface concurrent program pulls the settlement information from the federal G-Invoicing application. The Intragovernmental Performance Interface pull program automatically generates receipts for positive performance based on the settlement amounts from IPAC. This program also creates receipts for these amounts and applies receipts to the invoice.

If the performance is a negative transaction, then the Intragovernmental Performance Interface pull program un-applies receipts for the settled amount. It then creates refund the adjusted settled amount. The AP invoice is generated, and the payment is accounted.

IPAC Settlement - Business Scenarios

These business scenarios illustrate how Oracle Projects handles the IPAC settlements in G-Invoicing.

Consider an order with the order, line, and schedule numbers as shown in the following table. The order line schedule is created for a quantity of 100, with a unit price of $50. The Amount of $5000 is the product of the schedule quantity and the unit price.

Order Number Line Number Schedule Number Schedule Quantity Unit Price Amount
0123 1 1 100 $50 $5000

The subsequent tables illustrate how IPAC settlement is handled for each of the performances and FOB points:

Note: In the subsequent tables, the use of alphabets D, R and A refer to Delivery, Return, and Advance.

Delivery Performance with FOB Source for Orders that are Not Advance Enabled

This table shows the IPAC settlement for delivery performance with the FOB point set to Source for orders that are not advance enabled.

Steps Performance Number Reference Performance Number Performance Quantity Invoice Value Invoice Due Receipt Applied Refund Applied
Seller pushes delivery performance to federal G-Invoicing D100   10 (D) 10 10 0 0
Performance initiates settlement in IPAC D100   10 (D) 10 0 10 0
Buyer pulls the delivered performance from federal G-Invoicing D100   10 (D) 10 0 10 0
Buyer pushes acknowledgement of receipt/acceptance to federal G-Invoicing R100 D100 10 (R) 10 0 10 0
Seller pulls the acknowledgement receipt/acceptance from federal G-Invoicing R100 D100 10 (R) 10 0 10 0
Buyer pushes refund receipt/acceptance adjustment with negative performance to federal G-Invoicing R101 R100 -4 (R) 10 0 10 0
Seller pulls acknowledgement negative receipt/acceptance from federal G-Invoicing R101 R100 -4 (R) 10 0 10 0
Seller pushes negative delivered/performed adjustment to federal G-Invoicing as a credit memo D101 D100 -4 (D) 6 -4 10 0
Performance initiates settlement in IPAC D101 D100 -4 (D) 6 0 6 4

Delivery Performance with FOB Destination for Orders that are Not Advance Enabled

This table displays the IPAC settlement for delivery performance with the FOB point set to Destination for orders that are not advanced enabled:

Steps Performance Number Reference Performance Number Performance Quantity Invoice Value Invoice Due Receipt Applied Refund Applied
Seller pushes delivery performance to federal G-Invoicing D100   10 (D) 10 10 0 0
Buyer pulls the delivered performance from federal G-Invoicing R100   10 (D) 10 10 0 0
Buyer pushes acknowledgement of receipt/acceptance to federal G-Invoicing R100 D100 10 (R) 10 10 0 0
Performance initiates settlement in IPAC R100 D100 10 (R) 10 0 10 0
Seller pulls the acknowledgement receipt from federal G-Invoicing R100 D100 10 (R) 10 0 10 0
Buyer pushes refund adjustment receipt/acceptance with negative performance to federal G-Invoicing R101 R100 -4 (R) 10 0 10 0
Performance initiates settlement in IPAC R101 R100 -4 (D) 10 4 6 4
Seller pulls acknowledgement negative receipt/acceptance from federal G-Invoicing R101 R100 -4 (R) 10 4 6 4
Seller pushes negative delivered/performed adjustment to federal G-Invoicing as a credit memo D101 D100 -4 (R) 6 0 6 4

Advance Performance

The following table displays the IPAC settlement for advance performance:

Note: In the subsequent tables, the use of alphabets D, R and A refer to Delivery, Return, and Advance.

Steps Performance Number Reference Performance Number Performance Quantity Prepayment Balance Receipt Applied Refund Applied
Seller pushes advance performance to federal G-Invoicing A100   10 (A) 0 0 0
Performance initiates settlement in IPAC A100   10 (A) 10 10 0
Buyer pulls advance performance from federal G-Invoicing A100   10 (A) 10 10 0
Seller pushes refund adjustment advance with negative performance to federal G-Invoicing A101 A100 -4 (A) 10 10 0
Performance initiates settlement in IPAC A101 A100 -4(D) 6 6 4
Buyer pulls acknowledgement negative advance performance from federal G-Invoicing A101 A100 -4(R) 6 6 4

Delivery Performance for Advance Enabled Orders

This table displays the IPAC settlement for delivery performance for advance-enabled orders.

Steps Performance Number Reference Performance Number Performance Quantity Invoice Value Invoice Due Prepay-ment Balance Receipt Applied Refund Applied
Seller pushes advance performance to federal G-Invoicing and IPAC settlement A100   10 (A)     10 10 0
Seller pushes delivery performance to federal G-Invoicing D100   5 (D) 5 0 5 10 0
Buyer pulls the delivered performance from federal G-Invoicing D100   5 (D) 5 0 5 10 0
Buyer pushes acknowledgement of receipt/acceptance to federal G-Invoicing R100   5 (R) 5 0 5 10 0
Seller pulls the acknowledgement receipt/acceptance from federal G-Invoicing R100   5 (R) 5 0 5 10 0
Buyer pushes refund adjustment receipt/acceptance with negative performance to federal G-Invoicing R101 R100 -2 (R) 5 0 5 10 0
Seller pulls acknowledgement negative receipt/acceptance from federal G-Invoicing R101 R100 -2 (R) 5 0 5 10 0
Seller pushes negative delivered/performed adjustment to federal G-Invoicing as a credit memo D101 D100 -2 (D) 3 0 7 10 0

Viewing Receipts

When you submit an Advance Performance and run the intragovernmental performance interface program, the system generates receipts automatically for the selected order line schedule.

After the program completes, you can view the generated receipts from the view performance history page.

Prerequisites

To view receipts, perform the following step:

To view the receipts generated by the advance performance submission, perform the following steps:

  1. Click the G-Invoicing Dashboard icon.

  2. In the Header region, select Orders tab, and then select the advance-enabled orders.

  3. Select the View Performance Obligation icon.

    The Performance Obligation page displays.

  4. Select View Performance History page from the Actions drop down list and click Go.

    The View Performance History page appears:

    the picture is described in the document text

    The Receipt Number field is populated for each order line schedule.

  5. Click the Performance Obligations tab on top of the page.

    The Performance Obligation page appears.

    the picture is described in the document text

    This page includes Receipt field that displays the generated receipt details.

  6. Click the Receipt icon.

    The View Receipts page appears that shows receipts applied against each order line schedule.

    the picture is described in the document text

Refund Performance and Order Modification

On an approved order, a buyer can change the rate, quantity, add order lines, or cancel existing order lines, and modify delivery dates. The modified order is shared with the servicing agency, and Oracle Projects can pull these orders into EBS.

Before an order approval is initiated, a set of validations are run based on various performances recorded.

Attachments are used by the servicing agency to communicate key milestones that need to be captured between trading partners. You can push attachments with performances to the G-Invoicing application.

Order Modification Flow

  1. Query an existing order.

  2. Pull order modification with the shared with service (SSA) status.

  3. Update eligible order attributes.

  4. Initiate order approval.

  5. If a performance exists, then the system validates quantity and cancellation status.

    1. If the validation check fails, then the order approval fails as well.

      1. The status displays rejected in the G-Invoicing application.

      2. You can adjust revenue and invoice.

    2. If the validation check passes, then the order is submitted for approval.

      1. The funding is baselined and performance obligation is published.

      2. The status in the federal G-Invoicing application changes to Open.

When accepting and approving order modification, Oracle Projects validates changes. If the cost and quantity changes, then they are validated against the original rate and quantity. If the modified value is greater, then the order is rejected.

Admin Modifications

You can modify an order in an Administrative (Admin) mode when the order is in an open status. To modify orders in the Admin mode, perform the following:

  1. Navigate to the Federal G-Invoicing application.

  2. Query the order.

  3. Click Admin.

    You can modify fields as needed.

  4. In the Partner Information tab, change values for order Tracking Number, unique entity ID and add comments.

  5. In the Billing tab, change values for priority order indicator and capital planning and investment control.

  6. In the Point of Contact tab, change values for requesting agency name, email address, phone and fax.

  7. In the Schedule Line level, update attribute values including the schedule lines.

  8. Click Save.

  9. Run the Intragovermental Order Interface Program to pull the modifications.

  10. Run the Projects G-Invoicing ECC Data Load concurrent program as an incremental load.

  11. Navigate to the G-Invoicing dashboard by clicking Projects Super User, then click Projects Command Center, and then the G-Invoicing dashboard.

  12. In the Orders tab, select View Performance Obligation.

    The Performance Obligation page appears.

  13. You can click Additional Attributes and verify changes are reflected in EBS for each of the schedule lines.

  14. Click the G-Invoicing Dashboard icon on the top of the page to navigate back to the G-Invoicing dashboard.

  15. Select Update Agreement from the Orders tab.

    The Update Agreement window appears. You can view changes you had made. The Other Attachment region appears if the attachment was uploaded by servicing or requesting agency. The Attachment and the status changes to uploaded.

In the case of an advance-enabled order, if you create a receipt for an amount that is greater than the order amount specified, then an error displays when you submit the agreement. You must either reject the order or reduce the performance amount. You can cancel the receipt and apply another receipt with a lesser amount and resubmit the agreement for approval.

Only a requesting agency can close an IGT order.

Refund Push

If any refund is issued from a seller to a buyer, then the servicing agency creates a credit memo or concession invoice against the original invoice. This results in a negative performance, and the negative performance is pushed to the federal G-Invoicing application.

Credit memo is created in one of the following ways:

Cancel Invoice

Cancelling an invoice results in credit memo creation for the entire amount of the cancelled invoice. All items on the cancelled invoice are returned to an unbilled status. These items are eligible for rebilling during the next billing cycle. Oracle Project updates the funding balance on the agreement for the original invoice.

If a receipt is applied against an order or has a credit memo, then you cannot cancel that invoice.

Write-Off an Invoice

Writing off an invoice creates a credit memo against the original invoice for the requested write-off value. When the write-off is initiated on an invoice, Oracle Projects reverses the invoice value from the receivables account and places it into a write-off expense account while interfacing it to Accounts Receivables.

To refund a performance:

  1. Create a credit memo against the invoice.

  2. Run the Generate Draft Invoice, the Interface Invoices to AR, the Autoinvoice Import, and the Tieback Invoices from Receivables concurrent programs.

  3. Navigate to the G-Invoicing dashboard using by clicking the Projects Super User, US Federal responsibility, and then click Projects Command Center, and then G-Invoicing.

  4. Select View Performance Obligation from the Orders tab.

  5. Select the performance lines and click Submit Delivery Performance and Go.

    The delivery line displays with the credit memo quantity created with the negative amount.

  6. Enter the parameters in the Header region.

  7. Select Final Performance.

  8. Click Submit.

    The delivery line is created that displays the reference performance number and the corresponding reference performance detail number for the negative performance quantity. After the Intragovermental Performance Program completes successfully, the status is updated to success.

  9. Navigate back to the Federal G-Invoicing page and query the order.

  10. Select Options, then Performance List to view the delivered performances.

    The delivered performance for the negative quantity appears with the adjusted quantity against the original quantity.

You cannot submit a refund performance for an already submitted or accepted quantity. If the quantity is not settled, then you can submit a refund performance.

Applying Invoice Concessions

An invoice concession lets you manually credit an invoice without adjusting transactions. Applying a concession to an invoice creates a credit memo against the original invoice for the value of the concession. When you apply a concession, Oracle Projects adjusts the amount either from unbilled receivables account or unearned revenue account while interfacing the concession invoice to AR.

After an order is cancelled. you cannot delete the credit memo. You can apply concession even when a credit memo is associated with the original invoice. The credit memo inherits the same invoice currency and currency attributes of the invoice. The negative refund performance has the reference to original performance header and details when transferred to the G-Invoicing application.

Closing IGT Orders

Orders can be closed when all transactions are fulfilled between both the trading partners (requesting and servicing agencies). Requesting agencies can only close an order. While closing an order, any open quantity balance on order line schedules are adjusted and approved by both the trading partners.

The order closing process sends modifications to the federal G-invoicing application and updates the order status to closed (CLZ).

The Intragovernmental Orders Pull concurrent program pulls the closed orders into EBS.

The order closing process ensures the following conditions are met:

Buyers initiates an order closure only when:

Reopening Orders

In some cases, you would need to reopen closed orders due to changes in the order or market conditions. Requesting agencies can reopen orders.

Note: When closed orders are reopened, the orders interface program retrieves these orders and are considered by the order modification flow.

Servicing Agency Support for Buyer Initiated Orders

Oracle E-Business Suite for G-Invoicing supports orders that are initiated by requesting agencies. These buyer initiated orders (BIO) are created and approved either in the federal G-Invoicing application or in the EBS system. Servicing agencies then pull these orders into EBS for performance processing.

Prerequisite

The orders must fulfill the following setup requirements:

Servicing Agencies Handling of BIOs

Buyer initiated orders created in the federal G-Invoicing application are approved by sellers in the same system. You cannot modify these orders in EBS.

The servicing agency pulls buyer initiated orders into EBS and associates project and top task for accounting purposes. These orders are pulled in approved status. Performances are initiated from EBS and pushed to the federal G-Invoicing application. All modification must be performed only in the federal G-Invoicing application. These changes are approved by both agencies and are pulled by the servicing agency for processing performances.

Seller Facilitated Orders (SFO) also fall into the federal G-Invoicing maintained orders category. Refer to "Seller Facilitated Orders" for more details.

After the buyer initiated orders are pulled into EBS, the servicing agency can follow the order approval flows to create performances against these orders as described below:

Seller Facilitated Orders

Most orders are initiated by requesting agencies. Whereas, some orders may also be initiated by servicing agencies. Orders initiated by servicing agencies are known as seller facilitated orders. Oracle Projects supports Seller Facilitated Orders (SFO). The servicing agency creates orders in the federal G-Invoicing application and submits them for requesting agency's approval. After orders are approved, the servicing agency pulls these orders and the revenue budget is created and funding is baselined automatically.

Non-Advance-Enabled Orders - New and Modified

The following flowchart illustrates the non-advance-enabled seller facilitated orders (for new and modified order):

the picture is described in the document text

Seller facilitated orders (SFO) use the following flows for non-advance-enabled new and modified orders:

  1. Servicing agency initiates the seller facilitated order (SFO – new order) from the Federal G-Invoicing application and sends it to the Requesting Agency for approval. In the case of order modification, the servicing agency modifies the seller facilitated orders (SFO) in the federal G-Invoicing application and sends it for the requesting agency's approval.

  2. The requesting agency pulls the SFO and approves it and sends it back to the Federal G-Invoicing application.

  3. You must pull the approved seller facilitated orders to EBS from G-Invoicing. After you pull the seller facilitated orders into Oracle Projects, the concurrent program creates agreements automatically.

  4. You then create and or associate project to the orders. Performance obligations and performance obligations lines are created automatically. In the case of order modification, you must uptake the modified orders.

  5. Run the Intragovernmental Orders Interface program to pull these orders into EBS. The concurrent program updates agreements automatically and updates performance obligations and performance obligations lines.

  6. You must associate task to order line schedules and confirm funding availability. If funds are available, you can submit the agreement for approval. This publishes performance obligations, generates revenue budgets, and baselines funding.

  7. The order is ready for use.

  8. You can submit deferred and delivery performances.

Advance-Enabled Orders - New and Modified

The following flowchart illustrates the advance-enabled seller facilitated orders for new and modified order:

the picture is described in the document text

Seller facilitated order uses the following flow for advance-enabled new and modified order:

  1. Servicing agency initiates the advance-enabled seller facilitated order (SFO – new order) from the Federal G-Invoicing application and sends it to the Requesting Agency for approval. In the case of order modification, the servicing agency modifies the seller facilitated orders (SFO) in the federal G-Invoicing application and sends it for the requesting agency's approval.

  2. The requesting agency pulls the order and approves it and sends it back to the federal G-Invoicing application.

  3. You must pull the approved seller facilitated order to the G-Invoicing dashboard. After you pull the seller facilitated orders into Oracle Projects, the concurrent program creates agreement automatically.

  4. You then associate or create and associate a project to the orders. In the case of order modification, you must uptake the modified orders.

  5. Performance obligations and performance obligations lines are created automatically.

  6. You must associate a task to the order line schedules and confirm funding availability.

  7. If funds are available, you can submit the agreement for approval. publishes performance obligations, generates revenue budgets, and baselines funding.

  8. The order is ready for use.

  9. You can request partial or full advance against advance-enabled orders. The advance performance submission generates and baselines revenue budget and settles funding.

  10. Then, you can submit delivery performance and pull the acceptance for orders.

Creating Seller Facilitated Orders

Perform the following steps for creating SFOs:

  1. Log in to the federal G-Invoicing application.

  2. Create a GT&C.

  3. In the Header/Details region, select Servicing Agency for the Order Originating Partner Indicator field. For Seller Facilitated Orders (SFO), you must choose Servicing Agency for order originating partner. This is the only field that is different for SFO.

  4. Click Create Order.

  5. Enter the mandatory parameters and partner information for both requesting and servicing agencies.

  6. Also, enter values for fields in the Program Authority, Statutory Authority regions.

  7. Click the Advance tab, set the Assisted Acquisition Indicator to Yes.

  8. Click the Delivery tab, define the delivery details such as FOB Point, Acceptance Point, Inspection Point.

  9. Click the Billing tab, define billing details such as Billing Frequency, Priority Order Indicator, Capital Planning, and Investment Control.

  10. Click the Point of Contact tab, enter POC values for requesting and servicing agencies.

  11. Click Lines, enter mandatory values for creating order lines.

  12. Enter schedule details for the order line. Select Yes for the Advance Pay Indicator field to create advance-enabled orders.

  13. In the Advance tab, enter details for the advance-enabled information.

  14. Enter funding details for servicing agency.

  15. In the Standard Line of Accounting region, enter values for the mandatory fields.

  16. Click Save as Draft.

  17. Click the Share with Servicing Agency.

  18. Enter funding and program official approval details and click Servicing Agency Approve.

    The order is shared with the requesting agency for approval as shown below:

    Shared with Requesting Agency

    the picture is described in the document text

Requesting Agency Approves SFO

Perform the following steps as the requesting agency to approve SFOs:

  1. Select the Requesting Agency tab and then Orders.

  2. Query for the seller facilitated order.

  3. Click the Partner Information tab, enter values in the fields such as Order Tracking Number, Unique Entity ID, Funding Office Code, and Funding Agency Code.

  4. Click the Authority tab, enter the requesting agency program authority details.

  5. In the Lines/Schedules tab, enter values in the Funding Information such as TAS, BETC, Advance Accounting Classification, Bona Fide Need.

  6. In the Standard Line of Accounting region, enter values for the mandatory fields.

  7. Click Submit for Requesting Approval.

  8. In the Approvals tab, enter the Funding and Program Official Approval details for the requesting agency.

  9. Click Requesting Agency Approve .

Pulling Seller Facilitated Orders into EBS

The servicing agency then pulls the approved SFOs into EBS:

  1. Switch to the Projects Super User, US Federal responsibility.

  2. Select Request and then Schedule.

  3. Query the Intragovernmental Orders Interface Program concurrent program.

  4. Click Parameters.

  5. Enter values in all mandatory fields including the order number.

  6. Click Continue.

  7. Click Submit.

  8. Run the ECC G-Invoicing Data Load program to import data.

    These programs pull data into EBS.

Working with Seller Facilitated Orders in Oracle Projects

Perform the following steps in the G-Invoicing dashboard for SFOs:

  1. Select Projects Command Center and the G-Invoicing dashboard.

  2. Query the seller facilitated order.

  3. Use search refinement for GT&C and Orders to sort them by Order Originating Partner Indicator as shown:

    Search Refinement with Order Originating Partner

    the picture is described in the document text

  4. 9. In the GT&C and Orders region, view the Order Originating Partner Indicator field. This field displays servicing agency for seller facilitated orders.

  5. In the Orders tab, click the Create Project icon.

    • Query for a project template.

    • Select the template and click Continue.

    • Enter values in the mandatory fields.

    • Click Finish.

      The project is created and you are taken to the Performance Obligations page. You can only edit the top task number.

  6. Click Save and Continue.

    The Servicing Agency TAS appears. All other fields are not-editable. Similarly, the Additional Attributes fields cannot be edited.

  7. Rerun the ECC G-Invoicing Data Loadconcurrent program.

  8. In the Orders tab, click the Update Agreement icon.

  9. Enter the description.

    All the IGT related fields are read-only. There is a Confirm Funding Availability option using which you can verify that funds are available before they are settled. Also, fields in the additional attributes page are not-editable. The Partner Information region in the Additional Attributes page includes news fields such as Unique Entity Identifier, Comments, Funding Agency Codes for both servicing and requesting agencies. Similarly, since the agreement is already approved the funding information displays the details.

  10. Click Submit.

  11. Login and approve the agreement.

    Once the agreement is approved, Oracle Projects runs the following concurrent programs automatically as set up in the G-Invoicing Setup options:

    the picture is described in the document text

  12. Log into the federal G-Invoicing application and query the order and see that the order line schedule has advance performance submitted.

  13. Navigate back to the Projects Super User, US Federal responsibility.

  14. Select Requests and then Schedule.

  15. Query for the Intragovernmental Performance Interface Program.

  16. Click Parameters tab.

  17. Enter values in the mandatory fields to pull the modified performances into EBS.

  18. Notice that the Internal Status changes to Approved.

  19. Click the View Performance icon.

  20. Click the Performance Obligations tab.

  21. The advance performance is submitted and the receipt is also processed.

  22. Click the Financial tab.

    You can see budget is also approved.

  23. Click the Funding tab.

    You can see the funding created.

Modifying Seller Facilitated Orders

For modifying seller facilitated orders, perform the following steps:

  1. Switch to the federal Federal G-Invoicing application.

  2. Query the order number.

  3. Click Modify. The order has a revised number (for example, .x – where x represents the revision number).

  4. Click the copy icon next to the schedule number and create another line.

  5. Change the quantity in the first order line schedule.

  6. Change the quantity in the second order line schedule.

  7. Click the Update Draft button.

  8. Click the Share with Servicing Agency button.

  9. Click the Approvals tab and enter values in the Program Official Approval fields for the servicing agency.

  10. Click Service Agency Approval.

  11. Approve the order from the requesting agency.

    • Click the Requesting Agency tab.

    • Query for the order.

    • Click the order.

    • Click schedule and enter values for the mandatory fields in the Funding Information, Standard Line of Accounting regions.

    • Click Submit for Requesting Approval.

    • Click the Approvals tab, and enter values in the Funding and Program Official Approval fields.

    • Click Requesting Agency Approve.

  12. Navigate back to the Projects Super User, US Federal responsibility.

  13. Submit the Intragovermental Orders Interface Program using the submit request window.

  14. Enter values it the mandatory fields.

  15. Click OK and then Submit.

  16. Submit the ECC G-Invoicing Data Load concurrent program to pull the order details to the G-Invoicing dashboard.

  17. In the Headers region, select the Orders tab.

  18. In the Details region, select the Order Line Schedules tab.

    You can see order lines created with the modified values.

    Modified Order Lines Created

    the picture is described in the document text

  19. Scroll right and see the Internal Status as Modified indicating it is a modified order.

    Internal Status

    the picture is described in the document text

  20. Select the order.

  21. Click the Order Modification Uptake from the Actions (three ellipses) menu.

    Order Modification Uptake Menu

    the picture is described in the document text

    The order modification uptake completes successfully.

  22. In the Headers region, click the Orders tab.

  23. Click the View Performance Obligation icon.

  24. From the Actions list, select Update and click Go.

  25. Add value for the Top Task Number for the modified line.

  26. Click Save and Continue.

  27. Click Apply.

  28. Click the G-Invoicing Dashboard icon.

  29. Click the Orders tab.

  30. Click Update Agreement.

  31. Click Submit to submit the agreement for approval.

  32. Approve the agreement.

  33. Navigate to the federal G-Invoicing application.

  34. Query the order.

  35. Click the Show Performance button.

    Show Performance in G-Invoicing

    the picture is described in the document text

Submit Deferred and Delivery Performance for Seller Facilitated Orders

Perform the following steps for submitted deferred and delivery performances for seller facilitated orders:

  1. In the Projects Command Center, select orders in the G-Invoicing dashboard.

  2. Submit deferred and delivery performance by entering values for the mandatory fields.

  3. Performances are pushed to the federal G-Invoicing application.

For details on steps to submit deferred and delivery performance, refer to "Using Deferred Performance" and "Using Delivery Performance".

Closing Orders

Once all the performances are fulfilled, you can close the order. To close an order, perform the following steps:

  1. From the federal G-Invoicing application, select the order to close.

  2. Click Close.

  3. Enter the reason to close the order.

  4. From the Projects Super User, US Federal responsibility, run the Intragovernmental Orders Interface Program concurrent program.

  5. Run the ECC G-Invoicing Data Load concurrent program.

  6. In the G-Invoicing Dashboard, in the Headers region, click the Orders tab.

  7. Scroll to right and see the Order Status as Closed.

    Closed Order Status

    the picture is described in the document text

Organization Group Model

The Organization Group model provides the security needed with a flexibility to provide access to documents across agencies.

This functionality allows agencies to transition from a flat access model to a Hierarchical organization model:

If you belong to a Group that has access to GT&C, then you can view them. The groups above and groups below within the same hierarchy can view these GT&C.

If you belong to a Group and have access to orders, then you can edit, approve, reject, close and modify them. The groups above within the same hierarchy can perform these actions. But the groups below in the hierarchy cannot view these orders. A sample group structure is shown as follows:

The Organization Group Hierarchy address the following:

Organization Group Hierarchy

the picture is described in the document text

Performance against an Order is reported by Performance Managers of the Group to whom orders are assigned. Document Inheritance Indicator (DII) - GT&C Manager (or Creator) can limit the GT&C to only the assigned group. Ensure that you adhere to the following logic when sharing GT&C with Subordinate Groups:

You can map Agency Location Code (ALC) to Operating Unit to pull all the G-Invoicing documents. You can associate the group on Order based on the GT&C security preferences (Parent/Child, DII and Subordinate Groups) setup. You can setup and control the user and group-level access on documents (Orders and GT&C).

The Organization Group has three-level security:

  1. Operating Unit

  2. Servicing Group - Based on the servicing group selected the TAS filter applies.

  3. TAS and BETC

Prerequisite

To use the Organization Group Hierarchy, you should have installed license of Project Costing, Project Billing and Oracle Financials.

Setting Up Group Security

The Get Group in Agency Account returns Organizational Groups in that Agency for the requested System ID. The Security Attributes setup at the user-level determines the group access. The TAS and BETC filters are applied based on the group association.

G-Invoicing Options - Security Certificate

the picture is described in the document text

G-Invoicing Administration Menu

the picture is described in the document text

Organization Group Hierarchy Steps

  1. Create GT&C in the G-Invoicing application.

  2. GT&C pulled into the Servicing agency ERP system.

  3. Create Orders in the G-Invoicing application.

  4. Pull Orders from the G-Invoicing application to Oracle Projects and push orders from Oracle Projects to the G-Invoicing application.

  5. Run the Projects G-Invoicing ECC Data load in incremental mode.

  6. Navigate to the G-Invoicing dashboard using by clicking the Projects Super User, Federal responsibility, and then click Projects Command Center, and then G-Invoicing.

  7. Update Agreement in the Orders tab.

  8. Servicing Organization Group contains list of values accessible to the group.

    The groups mapped to the Agency Location Code only appears.

    You can edit the operating unit and based on the selected operating unit, organization groups are displayed. Based on the organization group selection, the corresponding associated TAS and BETCs appear in the list of values.

  9. Deactivate a child group.

  10. Run the Intragovermental Groups for Agency Interface Program which pulls all the Complete Group Structure.

    1. Specify Servicing Agency as the Agency Type.

    2. Enter the Operating Unit associated with the group hierarchy.

    3. Click Ok.

      When the agency groups are pulled, it also automatically run the Intragovermental TAS-BETCs for Group Interface Program and pulls the TAS and BETC setups as well.

  11. Run the Intragovermental Groups for GT&C Interface Program which pulls only the Group associated to the pulled GT&C.

    1. Specify Servicing Agency as the Agency Type.

    2. Enter the Operating Unit associated with the group hierarchy.

    3. Enter the GT&C Number to pull groups for only a specific GT&C. If you leave it blank, then all the GT&Cs are pulled.

    4. Click Ok.

Deleting a Group or TAS

As part of the Organization Group Hierarchy changes, you can configure TAS filters at each hierarchy level for the Servicing Agency. The list of values for TAS in the Performance Obligations page reflects these changes.

You can only delete a group that is the lowest in the order of group hierarchy. You can delete the parent without deleting the child group.

If you delete a TAS that is associated to a group, and sync the group to Oracle Projects, then the TAS will no longer be available in the list of values.