My Oracle Support Banner

Interface Trip Stop Errors With Failed To Interface Batch XXXXX To Order Management and Process Order Warning512 (Doc ID 2020268.1)

Last updated on AUGUST 10, 2018

Applies to:

Oracle Shipping Execution - Version 12.0.6 and later
Information in this document applies to any platform.


Interface trip stop is failing with the following error:

After OE_Shipping_Integration_PUB.Ship_Confirm_New TIME: ==> 12/29/XXXX 12:11:25 AM        
l_return_status  ==> W
         NO. OF OE MESSAGES :
           No. Warning Rec. Update ==> 1
           No DCP Error
           Inside Loop WSH_DCP_PVT.G_INIT_MSG_COUNT ==> 0
           before deleting tables ==> 2
           current index ==> 1
           next index ==> is NULL
           l_loop_count ==> 1
           l_error_count ==> 0
         l_warn_count ==> 1
         Process Order Warning512
Failed to interface Batch  1482643  to Order Management because API interface_header_to_OM failed

The issue can be reproduced at will with the following steps:
1. OM Super User Responsibility
2. Shipping> Interfaces> Interface Trip Stop.
3. Using the delivery or trip stop id, run the process.
4. Process fails with the errors.
    The Log file should match all the error messages, not only the last one (last one is a generic message).





To view full details, 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 a vibrant support community of peers and Oracle experts.