EDI Transactions and Messages

Demand Scheduling Execution enables you to capture the raw EDI demand requirements that are sent by customers to suppliers. Typically, you send and receive information using the JD Edwards EnterpriseOne Electronic Data Interchange system (47). This demand scheduling information includes cumulative quantities and supplier release scheduling. You can determine which transactions and messages are sent to the supplier, and how to use them.

A supplier might receive the same type of information on several different transactions or messages, depending on the mix of customers with which they conduct business. The translator can interpret and process this data consistently and map the information to the database, based on the user-defined translation rules.

For example, demand information can be received by an 830, 850, 862, 866, DELJIT, DELFOR, or ORDERS document. The third-party translator then maps the data from the EDI transmission to EDI system (47) demand tables, based on the trading partner, the EDI transaction, and the data that was received.

Occasionally, customers use the 850 (purchase order) document for planning and forecasting, or for spot buys. Other customers use it as a blanket purchase order. For the customers that use the 850 for planning and forecasting, this document flows through the demand tables as a planning requirement. For spot buys, the system processes the 850 as a firm type of requirement. If the 850 document is used as a blanket purchase order, the system maps it to the PO System/47 tables and processes it as a typical 850 document.

You can also enter and revise this information manually and direct this information to customers or suppliers.