Last updated on FEBRUARY 22, 2017
Applies to:JD Edwards World EDI - Version A9.2 cume 1 to A9.3 cume 1 [Release A9.2 to A9.3]
JD Edwards World Sales Order Management - Version A9.2 cume 1 to A9.3 cume 1 [Release A9.2 to A9.3]
Information in this document applies to any platform.
When adding User Defined Data (UDD) to a kit parent line via Sales Order Entry (P4211) and in Batch Order Edit and Creation (P40211Z) via the EDI UDD detail file (F4731), records are not written to the Sales Order Detail-User Defined Data (F42116) file.
In addition, for release A9.2.1, the EDI User Defined Data (UDD) sales detail file F4731 is not creating the F42116 EDI sales detail UDD file when the P40211Z Inbound 850 Batch Sales Order (EDI) creation is executed. This also occurs when adding UDD for the kit parent on the P4211 Sales Order Entry detail UDD.
Note: The F4731 EDI User Defined Data (UDD) sales detail file updates as the P40211Z EDI Batch Sales Order Creation XJDE0004 is executed. The file updates with the newly created sales order number DOCO , order type DCTO and line number but the Send Receive flag EDSP is not updated and the F42116 Sales Order UDD file is not created.
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 hundreds of Community platforms