E1: 40R: Forecast Dates and Quantity not Matching Dates/Quantities in EDI or Demand Detail
(Doc ID 2573011.1)
Last updated on OCTOBER 09, 2024
Applies to:
JD Edwards EnterpriseOne Demand Scheduling Execution - Version 9.0 to 9.2 [Release 9.0 to 9.2]Information in this document applies to any platform.
Purpose
Planned demand (forecasts) are sent in by the customer via the EDI 830 (DELFOR) to notify the supplier of the expected quantities that will be required in the future. This allows suppliers in the Automotive Industry to plan in the future for the number of firm orders that will be required by the customer. A common issue reported by Demand Scheduling customers is that the dates and quantities sent by their customers do not match the values sent by their customer. This is because demand spreading is used to "spread" the demand across multiple periods (weeks), so what is seen in the EDI Schedule (F47173) and the Demand Detail (F40R11), may not be the same date and quantity sent by the customer. There is a solution for this issue. This document will provide the setup necessary to setup the EnterpriseOne Demand Scheduling Execution to have all the forecast dates and quantities match what was sent from the customer from when the EDI was sent through the creation of the forecast (F3460).
Scope
The setup below describes a scenario where the customer is sending in weekly, planned requirements on a Wednesday date. The steps would vary for customers that use another day of the week for their forecasts and the setup would need to be adjusted accordingly.
Details
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
Purpose |
Scope |
Details |