Applies to:

Oracle Order Management - Version: 11.5.10.2 and later [Release: 11.5.10 and later ]
Oracle Order Management - Version: 11.5.10.0 and later [Release: 11.5.10 and later]
Information in this document applies to any platform.

Goal

Provide a comprehensive list of things to check when receiving Awaiting Invoice Interface - Incomplete Data.

Solution

A. Order Line stuck with Awaiting Invoice Interface - Incomplete Data Status

1. Go to Order Management super user responsibility.
2. Navigate to Set up > Transaction type > definition.
3. Set the correct value for the receivables transaction type
(e.g.Invoice) under finance tab.
4. Run the workflow background process and check whether the line
gets closed and invoice is created properly.

B. Invoice_incomplete in New Operating Unit

Verify that the inventory item is assigned to the item validation organization.

C. ATO Items are stuck in the status Awaiting Invoice Interface - Incomplete Data.

Add description to the ordered item - once the description is added the system worked fine.

D. Invoice_incomplete After Setting 'Multiple Payments' Parameter

The issue is caused by the following setup: Null Payment Type at the line level. This is not a case of missing functionality or data corruption. It is because these orders were created
before parameter for 'Multiple Payments' was enabled.

Solution
To implement the solution, please execute the following steps:
1. Go into the responsibility: Order Management Super User
2. Navigate to Orders Workbench, Order Organizer > Query the orders > navigate to line level >
3. Do an Action > Payments (enter a payment i.e. 'Cash') and save the payment record.
4. Retest the issue.
5. Migrate the solution as appropriate to other environments.

E. Invoice_incomplete for Service Items

When ordering services in Order Management, the service start and end dates are not populated for some orders. The workflow gets the service order line to closed status without populating these fields.

Order Management calls a Service Contracts API to populate the Service Start Date of service
items at the time of order line fulfillment. In some cases the API may not return a date, typically this can happen if the Install Base interface fails for some reason for the product referenced by the service line; when this happens then Order Management leaves the service start date and service end date as NULL. The dates will be populated correctly in the Service Contracts application when the extended warranty is eventually created, but will remain null in Order Management. This is the expected behavior, as the service start and end dates in Order Management are only a recommendation.

Note: the above functionality was introduced by Bug 4067555 in 11.5.9 and by unpublished Bug 4110229 in 11.5.10. Prior to these fixes Order Management populated the fulfillment date as service start and calculated service end accordingly, but this could cause the dates to be incorrect.

Fixed file versions are:
11.5.9: OEXVFULB.pls 115.79.1159.18 and OEXVFULS.pls 115.16.1159.3
11.5.10: OEXVFULB.pls 115.91.11510.5 and OEXVFULS.pls 115.17.11510.1

(The fix was included in the base R12 release).

If the start/end dates are not populated in the sales order, then the service line cannot go to Closed status. This is because the line cannot be invoiced with the data missing. So the service line stays at "Awaiting Invoice Interface - Incomplete Data". The missing data should be entered in the sales order. To enter the missing data:
- go to (R) Order Management Super User (N) Orders,Returns >Process Messages
- query using the sales order number
- check the messages for what data is missing (in this case service start/end date)
- open the sales order and enter the missing data
- then with the cursor on service line go to Actions > Progress.
This will close the service line.