Failed To Interface Order Management Because Api Interface_header_to_om Failed

(Doc ID 1406315.1)

Last updated on MARCH 27, 2018

Applies to:

Oracle Order Management - Version 12.1.3 to 12.2.2 [Release 12.1 to 12.2]
Information in this document applies to any platform.
ConcurrentProgram:WSHINTERFACES - Interface Trip Stop - SRS

Symptoms


On : 12.1.3 version, Interface Trip Stop

Order has status as 'BOOKED', flow process is blank.

Line/Header workflow is missing even on open Lines & Header. It is to be created.

It has warnings :

Warning List:
15. Order_Header status is BOOKED but "Book" activity has not been completed.
50. No WorkFlow Process associated to this line.

It has many order lines many with status as 'CLOSED' some with 'Cancelled' and some with 'Awaiting Shipping' status but flow process is blank for all lines.

INI & OMI as N.

'Interface Trip Stop SRS' errors :


ERROR
-----------------------
Interface trip stop is completed with warning
+---------------------------------------------------------------------------+
Start of log messages from FND_FILE
+---------------------------------------------------------------------------+
InterfaceTripStop: processing stop_id 821448 for INV OM DSNO
Time spent in notification framework is (sec)
Order Number :7525 Line Number :
Message :ORA-20002: 3100: Item 'OEOL/1101451' does not exist. in Package OE_ORDER_WF_UTIL Procedure Create_LineFork
Order Number :7525 Line Number :
Message :User-Defined Exception in Package OE_ORDER_WF_UTIL Procedure CreateStart_LineFork
Order Number :7525 Line Number :
Message :User-Defined Exception in Package OE_ORDER_WF_UTIL Procedure CreateStart_LineProcess
no. of OE messages :3
Error msg: ORA-20002: 3100: Item 'OEOL/1101451' does not exist. in Package OE_OR
DER_WF_UTIL Procedure Create_LineFork
Error msg: User-Defined Exception in Package OE_ORDER_WF_UTIL Procedure CreateSt
art_LineFork
Error msg: User-Defined Exception in Package OE_ORDER_WF_UTIL Procedure CreateSt
art_LineProcess
Failed to interface Batch 872597 to Order Management because API interface_hea
der_to_OM failed
InterfaceTripStop: total stops processed: 1
Stops processed for ORDER MANAGEMENT with status NORMAL: 0
Stops processed for ORDER MANAGEMENT with status WARNING: 1
Stops interfaced for ORDER MANAGEMENT: 0
+---------------------------------------------------------------------------+
End of log messages from FND_FILE


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. OM Superuser > Run Requests > Interface Trip Stop SRs

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms