Sales and purchase orders along with their respective line items always seem to have associated customer, supplier, and item data that needs to travel along with them. The trouble is finding enough real estate and benign fields that are usable on program videos to enter and store this data. Wouldn’t it be great if there were user-defined fields that could be used solely for this purpose?


You‘re in luck! Starting with JD Edwards World Release A9.2, we introduced User-Defined Data  (or UDD for short). Even better, the data travels along with its related item, sales and purchase order.  Here is an example of one of the many places you can define user defined data. Except for Customer and Customer Group below, all fields are available for user-defined data:

UDD example.png


The UDD files and fields design incorporates:

  • Nine files with 100+ fields each
  • Alpha-numeric data entry
  • Associated, definable UDC tables 
  • Errors returned if data is required or incorrect 
  • UDD data defaults in based on customer, supplier,  item, and group setup at time of order entry


How does it work?

  • Access UDD from Sales Order Entry, Purchase Order Entry, and a variety of Electronic Commerce (EDI) programs accessible via processing option and function keys.
  • Once the UDD video pops up, enter data or review the default data from related setup.
  • The data is written to a transaction file once the order is accepted.
  • Order is printed via invoice or PO Print  - The UDD information maintains its relationship to the order.
  • If you are using EDI, an EDI UDD file is written relating the files to the orders. This data may be mapped and sent to trading partners via XML or translation software.


On top of all this, custom reports can also be created using the UDD fields to report information tied to orders and items.


To find out more about UDD, check out Doc ID 858973.1 User-Defined Data for Distribution.   Make sure to post any questions to My Oracle Support Community for JDE World or feel free to add a comment to this blog.