My Oracle Support Banner

Interface Trip Stop Fails With EGO API Return Status: E When Attempting to Split Line and Copy Split User Defined Attribute(UDA) (Doc ID 2941449.1)

Last updated on APRIL 10, 2023

Applies to:

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

Symptoms

Interface Trip Stop errors with the following:



ERROR
-----------------------

Entering Procedure Process_Request_Pvt
Request processed  N
Request type  SPLIT_UDA
Entity id     xxxxxxx
param1        xxxxxxx
param2        
param3        
cascade flag set to false
Entering OE_Delayed_Requests_Util.split_uda
TIMESTAT: 27-FEB-23 08:47:44: 10432119.44  : Entering oe_order_copy_util.Copy_User_Defined_Attr
p_entity_code - LINE
p_from_entity_id - xxxxxxx
p_to_entity_id - xxxxxxx
Classification Code: ADMIN_DEFINED

................

Calling EGO_USER_ATTRS_DATA_PUB.PROCESS_USER_ATTRS_DATA API
Entity: .  Row Identifier: 7.  
"XXOM_First_SOA_Date" does not appear in "XXOM_Comxxx_Conxxxx".

EGO API Return Status: E

 


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. OM Super User Responsibility
2. Orders, Returns
3, Enter order and add values for User Defined Attributes(UDA) on header and lines.
4. Progress order thru pick release and ship confirm.
5. Interface Trip Stop errors when launched at the time of ship confirm.

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.