Understanding EDI Information for Demand Scheduling Execution

Demand Scheduling Execution focuses on capturing the demand requirements that are sent by customers to suppliers, including cumulative quantities. You can determine which transactions and messages are sent to the supplier, and how to use them.

The EDI (47) tables store the relevant data items as interpreted by the third-party translator. You can manually revise this information using EDI Demand Header Maintenance (P47171) and then process the demand requirements using the EDI Inbound Demand Edit/Update (R47171), which stores the demand requirements in the Demand Scheduling (40R) database. After the EDI data has been imported into the Demand Scheduling tables, the system does not reflect any changes to the EDI tables in the Demand Scheduling tables unless you change the Successfully Process flag in the EDI Demand Header and EDI Demand Detail to a blank or N. Periodically, you can purge the processed EDI records using the EDI Demand Purge (R47190) program to reduce the size of the EDI tables.

When you run the EDI Inbound Demand Edit/Update program, the system cross-references the Requirement Type value and Requirement Frequency values with the Demand Type and Demand Period values through Demand Cross Reference (P40R21).

Note: When you delete EDI demand information from the programs, the system deletes all of the dependent data. For example, when you delete an EDI demand address, the system also deletes the dependent EDI demand contact name and demand contact number.

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. Demand information can be received either 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, EDI transaction, and the data received. The translator can interpret and processes this data consistently and map the information to the database, based on the defined translation rules.

Note: 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, the information 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.

The system uses information from inbound transactions to populate these EDI demand tables with information translated by the third-party translator:

Table	Description
F47171 EDI Demand Header	Stores a set of EDI demand header records, such as Branch/Plant, Sold To, Ship To and Release Number values.
F47172 EDI Demand Detail	Stores line items from an EDI message.
F47173 EDI Demand Scheduling	Stores shipping and delivery dates, times, and quantities.
F471721 EDI Supplemental	Stores user-defined information specific to the implementation and customer.
F471731 EDI Packaging	Stores packaging information, such as weight and number of packages.
F471722 EDI Address	Stores address information.
F471723 EDI Contact Names	Stores contact information.
F471724 EDI Contact Numbers	Stores contact phone numbers.