Skip to Content
avatar image
Former Member

CTM setting for Lateness of Receipt

We are trying to trigger the setting in Location Product under Demand --> Pegging sub tab on "Maximum Lateness of Receipts". We want to be able to define a location product setting for lateness of receipts for demand. We were expecting this to override the global CTM setting on lateness of receipt. Does anyone have experience on how to make the field work ?

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Best Answer
    Mar 12, 2008 at 06:16 PM

    That is correct. The value in the product master is used only for PP/DS and for pegging supply to demand. And Product View.

    It is NOT used by SNP and/or CTM at all.

    And CTM uses the Global value or the profile specific setting (as of v5.0) or material specific value if using rules.

    This is explained in OSS 1084343 - CTM : Setting Late Demand Frame (LDF) in CTM planning.

    We have used the rules to change the lateness setting by product and it works fine.

    Ken Snyder

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Note 1084343 - CTM : Setting Late Demand Frame (LDF) in CTM planning

      ummary

      Symptom

      This consulting Note describes the late demand handling logic used by the CTM planning engine.

      CTM planning for demands always tries to schedule the orders intime to meet the complete required demand quantity.Due to capacity or material constraints if the demand cannot be satisfied intime,CTM can schedule the orders late.

      For late demand scheduling 3 parameters are relevant that can be configured as follows:

      • Late Demand handling Method

      Late Demand handling method can be defined in CTM global customization under transaction /sapapo/ctmcust.You can either select "Airline" or "Domino" method for planning late demands.

      Please refer to online help documentation for more details about these methods.

      • Late Demand scheduling strategy

      Late demand scheduling strategy defines the scheduling method when planning for late demands.This can be defined in the CTM profile under the Special strategies tab using transaction /sapapo/ctm.

      Please refer to online help documentation for more details about these methods.

      • Late Demand Frame

      Late demand frame(LDF) is defined by the number of days a demand can be scheduled late.LDF is assigned to each demand planned in CTM.The calculation of the LDF considers only calendar days.No breaks are used to calaculate the LDF.

      Example : Demand date is Aug 15 2007 12:00:00 AM with LDF = 10 Days. The maximum allowed lateness for the demand is till Aug 25 2007 12:00:00 AM.

      LDF value can be maintained either at global level or at the detailed level for each demand. Here are the options to maintain the LDF.

      o Global LDF

      Global LDF value can be maintained in CTM customization.This value will be used for all the demands and all the products across all the CTM profiles.

      o CTM profile specific LDF (Option 1)

      CTM profile specific LDF value can be set using the variable planning parameter in the CTM profile.This is only valid from SCM 5.0 release.

      Parameter Name = CTM_MG

      Value 1 = nLateShipGlobal Value2 = <number of days>

      o CTM profile specific LDF (Option 2)

      CTM Profile specific LDF can be set using the ATP rules (TA /sapapo/rba04).Rule definition contains the CTM calculation profile where LDF value can be set.ATP rule evaluation can be set to determine the rule based on each product and location.Due to performance reason,this method is not recommended for CTM planning with large data volumes.

      o Demand specific LDF

      Demand specific LDF value can be set using the user exit APOBO020. All the demands planned with CTM contains the LDF attribute (LATESHIP).See Note 450794 for more details about using the userexit.

      Safety stock planning with CTM creates virtual demands for planning.By default for safety stock demands,LDF value is calculated automatically by the system.This value can be changed with the profile setting "Late fulfillment" under "Supplies" tab of CTM profile.

      The option to update the demand LDF value using the userexit is also available for safety stock demands.

      Other terms

      CTM, Capable to match, Late demand, Calculation profile

      Question: where to set this variable planning parameter?

  • avatar image
    Former Member
    Jan 06, 2008 at 03:49 PM

    I am new to SNP would be really thankful in case you would be able to explain the business case behind changing the global settings for the lateness of receipt in CTM

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      The reason is that we have two businesses. In one business the product lifecycles are very short and hence if the demand is not met on time, customers start looking for upgraded versions causing delays in demand materialization. On the same hand, there is a business which has a longer product life cycle and customers are willing to wait if the demand is not met on time.Hence we need seperate settings for the two businesses where Late demand fulfilment is distinctive. Apparently we can only have one Global CTM setting applicable for both the businesses. We have not been able to figure out thus how to make this business requirement map on to CTM. Even the local Location Product setting does not seem to work.

  • avatar image
    Former Member
    Mar 12, 2008 at 03:28 PM

    The value in the location product master, tab demand/pegging should reflect, what delay is acceptable for a late receipt. If initial (empty), late receipts are NOT allowed. e.g. 1080 (hours) means, that a receipt can be up to 45 days late and is still considered valid supply for a certain demand (and thus, pegged to this demand). Please also check note 1084343 - Setting Late Demand Frame (LDF) in CTM planning.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      The only catch is it does not work based on our understanding. It does not work at all in CTM. We proved it through an OSS message already.