OTM EBS API: WSH_OTM_INBOUND_GRP.INITIATE_PLANNED_SHIPMENT Lacks Waybill Field
(Doc ID 2246569.1)
Last updated on MARCH 22, 2017
Applies to:Oracle Shipping Execution - Version 12.1.3 and later
Information in this document applies to any platform.
OTM EBS API: WSH_OTM_INBOUND_GRP.INITIATE_PLANNED_SHIPMENT lacks waybill field
How we can get the waybill #passed to EBS from OTM?
The waybill # is passed from OTM to SOA but there is no input field on the OTM Shipment API that consumes that field.
OTM EBS API: WSH_OTM_INBOUND_GRP.INITIATE_PLANNED_SHIPMENT
Inside the code, we see that it first inserts into a couple of interface tables then runs a concurrent program.
The interface table WSH_NEW_DEL_INTERFACE has the waybill field, but nothing is mapped or inserted to it.
screen shot shows WSH_NEW_DEL_INTERFACE interface table definition with waybill field.
What is the recommended approach to populate ship number?
WSH_NEW_DEL_INTERFACE has the waybill field but the API does not.
We expect to be able to send the shipping number to EBS, but find no place to hold that value in the API.
OTM can generate or accept shipping numbers from freight partners.
The issue can be reproduced at will with the following steps:
1. Responsibility: Order Management Super user & OTM user
2. Navigate: Make use of the API > try to map waybill >
3. Find interface table WSH_NEW_DEL_INTERFACE has the waybill field, but nothing is mapped or inserted to it.
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