My Oracle Support Banner

Interface Trip Stop Errors With No Records Found For Lot ORA-22160: Element At Index [4] Does Not Exist (Doc ID 2581244.1)

Last updated on FEBRUARY 03, 2021

Applies to:

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

Symptoms

Order containing lot controlled items have been ship confirmed with the wrong lot number.

Order line progressed to closed and delivery details are in a shipped status and fully interfaced to OM but are not interfaced to Inventory.

Interface Trip Stop errored with the following:


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

ERROR: NO RECORDS FOUND FOR LOT

Unexpected error has occurred. Oracle error message is ORA-22160: element at index [4] does not exist
         Exiting WSH_TRXLOTS_HANDLER.INSERT_ROW_BULK - EXCEPTION:OTHERS (08/13/2019 02:20:00 PM,  0 seconds)
         WSH_TRXLOT_HANDLER.INSERT_ROW_BULK l_return_status ==> U
         FND_API.G_EXC_ERROR exception has occurred.
Exiting WSH_SHIP_CONFIRM_ACTIONS.INSERT_INV_RECORDS -
EXCEPTION:FND_API.G_EXC_ERROR (08/13/2019 02:20:00 PM,  .01 seconds)
       Insert_inv_records l_return_status ==> E
       l_insert_inv_calls ==> 1
       l_insert_inv_not_success ==> 1
       l_delivery_detail_tbl.count ==> 0
       FND_API.G_EXC_ERROR exception has occurred.





STEPS
-----------------------

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

1. Responsibility: Order Management Super User
2. Navigate: Shipping > Transactions
3. Entered wrong lot number on delivery detail > ship confirm
4. Interface trip stop errors.
 

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


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