Page tree
Skip to end of metadata
Go to start of metadata

Purpose

Learn how "Lead-time offset" & "Oper. LT offset" determines component requirement date.

Overview

Test how the setting of "Lead-time offset" & "Oper. LT offset" in BOM affects component requirement date.

TEST 1 -  Lead-time offset and Operation LT offset are all negtive value

<Master Data>

In t-code CS01/CS02, set the component as below.

 Lead-time offsetOper. LT offset
Item 0010    -1 Day    -2 Days
Item 0020    -3 Days    -4 Days

 

<Step>

  • Create a planned order in T-code MD11.  It is forward scheduling with Basic Start Date 09.11.2015. Since detailed scheduling is not executed yet, component requirement date is calculated with "Lead-time offset".
 Calculation LogicRequirement Date
Item 0010

Order start date - 1 working days

09.11.2015 - 1 = 06.11.2015
Item 0020

Order start date - 3 working days

09.11.2015 - 3 = 04.11.2015

 

  • Convert this planned order to production order in t-code CO40.  Detailed scheduling is executed since production order must execute detailed scheduling.

Operation 0010 starts on 11.11.2015.

Component 0010 and 0020 are assigned to operation 0010.

 Calculation LogicRequirement Date
Item 0010Operation start date - 2 working days11.11.2015 - 2 = 09.11.2015
Item 0020Operation start date - 4 working days

11.11.2015 - 4 = 05.11.2015

TEST 2 - Only Lead-time offset is set with negative value

<Master Data>

In t-code CS01/CS02, set the component as below.

 Lead-time offsetOper. LT offset
Item 0010    -1 Day    0
Item 0020    -3 Days    0

<Steps>

  • Create a planned order in T-code MD11.  It is forward scheduling with Basic Start Date 09.11.2015. Since detailed scheduling is not executed yet, component requirement date is calculated with "Lead-time offset".
 Calculation LogicRequirement Date
Item 0010

Order start date - 1 working days

09.11.2015 - 1 = 06.11.2015
Item 0020

Order start date - 3 working days

09.11.2015 - 3 = 04.11.2015

 

  • Convert this planned order to production order in t-code CO40.  Detailed scheduling is executed since production order must execute detailed scheduling.
 Calculation LogicRequirement Date
Item 0010

Operation start date - 1 working days
(Reason:Operation LT offset = 0 and LT offset is negtive)

11.11.2015 - 1 = 10.11.2015
Item 0020

Operation start date - 3 working days
(Reason:Operation LT offset = 0 and LT offset is negtive)

11.11.2015 - 3 = 06.11.2015

TEST 3 - Only Lead-time offset is set with positive value

<Master Data>

In t-code CS01/CS02, set the component as below.

 Lead-time offsetOper. LT offset
Item 0010      1 Days         0
Item 0020      3 Days         0

 

<Steps>

  • Create a planned order in T-code MD11.  It is forward scheduling with Basic Start Date 09.11.2015. Since detailed scheduling is not executed yet, component requirement date is calculated with "Lead-time offset".

 Calculation LogicRequirement Date
Item 0010

Order start date + 1 working days

31.08.2017 + 1 = 01.09.2017
Item 0020

Order start date + 3 working days

31.08.2017 + 3 = 04.09.2017

NOTICE: The requirement date will not be later than order finish date. Sample is exact same. But when Basic End Date = 31.08.2017,  the requirement dates are 31.08.2017, like positive lead-time offset is not considered. Actually, in such case, system will choose the smaller date.

  • Convert this planned order to production order in t-code CO40.  Detailed scheduling is executed since production order must execute detailed scheduling.

 Calculation LogicRequirement Date
Item 0010 = Operation start date
(Reason:Operation LT offset = 0 and LT offset is positive)
31.08.2017
Item 0020 = Operation start date
(Reason:Operation LT offset = 0 and LT offset is positive)
31.08.2017

 

 

 

 

 

  • No labels