SnipImage.JPG
Document Details
Uploaded by VivaciousConceptualArt
Tags
Full Transcript
## Section 3: MustGoDays and LookAheadDays | |...
## Section 3: MustGoDays and LookAheadDays | | | | :-------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **OH POST DATE** | | | **ORDERLEADTIME** | Deadline order | | **ORDERGENERATION** | Horizon order from deadline order | | **MUSTGODAYS** | Period containing all needs to be converted into trucks | | **LOOKAHEADDAYS** | Period containing available needs to supplement possibility truck with still room | | **NEEDS PLANNED BEFORE MUSTGODATE** | Manually entered by user into ERP (LRS2000 or GEAC) and automatically integrated by interface to JDA time minimu between the order date and the date from which the supplier can deliver | | **NEEDS PLANNED BETWEEN MUSTGODATE AND LOOKAHEADDATE** | Manually entered by user into JDA: Period during whom DC suppliers can anticipate the orders from the order date | **MustGoDays:** ORDERLEADTIME (transit days + PO lead time) + ORDERGENHORIZON (default is 1D for PO to be created and imported back from ERP system overnight). It is the duration on which DC needs MUST be included in the load. **LookAheadDays:** It is the duration on which DC needs can be used to complete/optimize the load.