E1: 40R: Demand Maintenance (P40R10) Application Does Not Send the Shipment Number in Outbound Label Data Using XAPI Event XAPIDDOUT
(Doc ID 2905599.1)
Last updated on NOVEMBER 03, 2022
Applies to:
JD Edwards EnterpriseOne Demand Scheduling Execution - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
The customer is using P40R10|W40R10F application to send Outbound label data to 3rd party using XAPI event <XAPIDDOUT>. When checking the generated XML file in JMS queue, the Shipment Number is not populated. Per the customer's analysis, the B40R0730 business function (Internal function - IB40R0730_GetSHPN) has mismatched column structure between APIs JDB_OpenTable (structure refers to a single column) and JDB_FetchKeyed (structure refers to the whole table). As a result, the shipment number is not populating the shipment number in the BLOB files.
Steps to replicate:
- Open P40R10 and search by Branch-Plant. Take Row exit and select Demand Detail option.
- Take Row exit, select Submit Label Data and press OK. The message "Your request has been processed" is displayed.
- XAPIDDOUT event will get processed. Check the message (XML format) that occured in JMS queue in Weblogic server console.
- Notice that the Shipment Number is blank in the current output/messages and Shipment Number is 0 in the xml file.
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 |