Use of periodic lot sizing in SNP heuristics

I am using APO V5.1.
I am using the standard APO SNP heuristic, and have periodic lot sizing working OK, with a 2 week periodic type.
But I want to try and model the fact that certain products are to be produced in 'even' weeks and other products are to be produced in 'odd' weeks.
I thought that the use of different planning calendars for the different products would help here, but I do not think SNP is recognising the planning calendars.
Any other ideas on this?...

hI,
Wanted to know if you have checked the option and tryed the same in system since the helptext says the same will not be considered by optimizer but will be considerd by heuristic.
Period Lot Size
Specifies that a period lot-sizing procedure is used in Supply Network Planning (SNP) and Production Planning and Detailed Scheduling (PP/DS).
Use
Use in SNP
This indicator is only used in heuristic-based planning (and not in optimization-based planning). If you set this indicator, the system groups the demand quantities of several consecutive periods together and creates orders to fulfill the quantity of this combined demand.
The period type and number of periods can be entered in the accompanying fields Period Type and No. of Periods. You can set the start time for the grouping in the Lot Size Grp. Start field.
The settings you make in the Lot Size Strategy field govern the period in which the combined demand is placed and the demand fulfillment order is created.
When calculating lot sizes and creating orders, the system considers all the other lot size settings from the location product master, such as minimum and maximum lot size, rounding value, and rounding profile.
Now for the solution you are thinking if possible you can divide the plant in two parts if the materials are accounted differntly and keep two different  factory calendars for the same and go ahead.This may be not a good solution but I thought I can share this with you.
Hope this can help.
regards,
kaushik

Similar Messages

  • Lot-sizing procedures

    Hi Experts,
    Can anybody please explain difference between following lot-sizing procedures.
    static lot-sizing procedures
    period lot-sizing procedures
    optimum lot-sizing procedures
    It will very much helpful if explain with example. Will appreciate with deserving point.

    Dear Raja,
    Pls. find details about Lot Sizing Procedures :
    Static Lot-Sizing Procedures
    Use
    In static lot-sizing procedures, the procurement quantity is calculated exclusively by means of the quantity specifications entered in the material master.
    Features
    The following static lot-sizing procedures are available:
    Lot-for-lot order quantity
    Fixed lot size
    Fixed lot size with splitting and overlapping
    Replenishment up to maximum stock level
    Period Lot-Sizing Procedures
    Use
    In period lot-sizing procedures, the system groups several requirements within a time interval together to form a lot.
    Features
    You can define the following periods:
    days
    weeks
    months
    periods of flexible length equal to posting periods
    freely definable periods according to a planning calendar
    The system can interpret the period start of the planning calendar as the availability date or as the delivery date.
    Splitting and overlapping are also possible for all period lot-sizing procedures
    The system sets the availability date for period lot-sizing procedures to the first requirements date of the period. However, you can also define that the availability date is at the beginning or end of the period.
    Optimum Lot-Sizing Procedures
    Use
    In static and period lot-sizing procedures, the costs resulting from stockkeeping, from the setup procedures or from purchasing are not taken into consideration. The aim of optimum lot-sizing procedures, on the other hand, is to group shortages together in such a way that costs are minimized. These costs include lot size independent costs (setup or order costs) and storage costs.
    Taking Purchasing as an example, the following problem hereby arises:
    If you order often, you will have low storage costs but high order costs due to the high number of orders. If you only seldom place orders then you will find that your order costs remain very low, but your storage costs will be very high since warehouse stock must be large enough to cover requirements for a much longer period.
    Features
    The starting point for lot sizing is the first material shortage date that is determined during the net requirements calculation. The shortage quantity determined here represents the minimum order quantity. The system then adds successive shortage quantities to this lot size until, by means of the particular cost criterion, optimum costs have been established.
    The only differences between the various optimum lot-sizing procedures are the cost criteria. The following procedures are available:
    Part Period Balancing
    Least Unit Cost Procedure
    Dynamic Lot Size Creation
    Groff Reorder Procedure
    Hope this helps.
    Regards,
    Tejas

  • Lot sizing procedure

    Hello
    Why it is said that "Periodic lot sizing procedure is suitable for forecast based planning"?
    Also please tell what is use of Subsequent settlement indicator in vendor master record?
    Thanks & Regards
    P.S.P

    Hi
    Sub seq settlement Indicates that conditions providing for subsequent settlement may apply to this vendor.
    Set this indicator if subsequent (end-of-period) settlement can be agreed with this vendor.
    Vijay

  • Lot Sizing for Short/Long Term

    Hello All,
    I tried the lot sizing with the short term/Longterm pattern..
    But I'm facing the following problem..
    I have maintained periodic lot sizing according to the planning calendar(Weeks from Saturday to Friday) for the first month...( Requirement date = period end)
    And for the other 2 years I have defined periodic lot sizing with Monthly lot size ( Requirement date = period end).
    But running MRP, the system Cumulates all the monthly requirement from the 2 nd period and creating the order proposal with the order end date of the months first planning calendar week. But I'm expecting the system to create the order proposal with the month's last date as the order end date .
    Whether my expectation is incorrect or any other settings to be maintained to achieve this.
    Thanks & regards,
    Mahesh

    Hello Mahesh,
    You can get the results without maintaining the planning calendar..Just change the lot size procedure WB :weekly lot size" and take out the planing calendar and maintain the settings as per below.
    In the period lot sizing procedure WB maintain the number of periods 1 for the period of short term period with weekly lot size. then in "end of the short term period" maintain the initail value " months: and define number of periods 24.
    maintain the same values for long term period i.e period 1 with period lot sizing procedure (monthly lot size).
    By doing the above you will get the weekly lot size for the first 2 years and then monthly lot size for the rest of the requirements.
    If helpful rewards your points.
    Regards
    TAJUDDIN

  • Reorder Point Planning via SNP heuristics based on ACTUAL stock

    Hi All,
    In R/3 there is the option in reorder point planning to take into account external requirements (MRP type V1) or not to take into account external requirements (VB). When using reorder point planning in APO SNP Heuristics, the reorder point is being determined in time based on the PROJECTED stock (so taking into account external requirements) so the result is the same as in R/3 when using MRP type V1. In the future horizon, everytime the projected stock goes below the reorder point, a replenishment is triggerd via a planned order or purchase requisition.
    I would like to know if (and how) it is possible to perform reorder point planning in APO SNP via heuristics (can be location or network) only taking into account the ACTUAL stock (and no external requirements in the past or in the future). So, the same behavior as the MRP type VB in R/3. The difference is that only on the short term, 1 time replenishment is triggered (via planned order or purchase requisition) if the current stock is below the reorder point.
    Remarks: this needs to be able to be set product specific, because not all products at the location will need to use this logic.
    Any help or thoughts for a solution direction (preferably without programming or user exits) are appreciated.
    Thanks in advance,
    Dennis

    If you really just want a pure re-order point scenario based on current stock, I'd suppose that you'd want to create a new data view and modify the total demand macro so that it doesn't generate any sort of future requirements (total demand will essentially be zero).  Then the reorder point will be the only thing driving planning when compared to the initial bucket SOH, which is presumably calculated through the standard macro and according to the stock cat. group you indicate in the location/product master.
    You could set some specific filter in the material master using the MATLOC freely definable attributes to create selection profiles and govern in which data view you process the planning for certain materials.  That is to say, you'd assign all materials which are pure current stock ROP and tag them with some attribute and use that to create selections for your Heuristic variants.

  • SNP heuristics and optimiser using transport lane validity dates

    I am using APO SNP 5.1.
    In particular I am trying to use the SNP heuristics and optimiser for supply planning.
    Can anyone confirm whether transport lane validity dates are respected by (a) SNP heuristics and (b) SNP optimiser, ie no transport requisitions will be created during times when the transport lane is not 'open' in terms of validity dates.
    Thanks for any advice on this...

    Hi,
    Irrespective of the SNP planning engine you are using, a t-lane will only be considered if the t-lane is active as per the validity dates.
    Regards,
    Umesh

  • Use of SNP Heuristics & Optimizer

    Folks,
    Has anyone used both Heuristics and Optimizer together within the same supply network?
    If so then how was this used e.g. Network optimization on monthly basis and location heuristics on weekly basis. Idea is to come up with a monthly optimum sourcing plan using optimizer and then resolve any location specific capacity issues using heuristics on a weekly basis.
    Is this a feasible solution?

    Hi,
    We are using both SNP Heuristics as well as Optimizer. SNP heuristic is not considering the Constraints, thats why it is required to be run where the demand and supply can be linked without any constraint. As in our case, we are doing it between Customer and C&F. For rest of the network, we are running Optimizer as several constraints are involved in different Supply chain nodes, like transportation capacity, production capacity, storage cost etc...
    We are running Optimizer on the whole network successfully which gives the results on a daily bucket considering various constraints.
    In your case, you can run Optimizer alone as it will consider the location specific capacities.
    Regards,
    Manjit

  • Availability Date calculation in SNP Heuristics

    Dear Experts,
    I am using weekly bucket profile. In the SNP PPM, period factor is set as 0. Lets say I create a PIR on date 09.11.2010 which is Tuesday.
    If I run Location Heuristics, it should schedule the Planned Order on 08.11.2010 12:00. But system is scheduling it on 11.11.2010 23:59:59 i.e. Thrusday. No matter on which day I create the PIR, it somehow always schedules it on Thrusday. Please help to understand how it is happening.
    (Though it should not matter here but Location-Product data also has period factor as 0)
    Regards
    Rinju
    Edited by: Rinju Mukherjee on Sep 27, 2010 7:38 PM

    Hello Micky and Amol,
    Thanks for your response. It seems F1 help for field 'Period factor' is not correct. Anyway, if system is taking 0.5, I have further two questions:
    Then it should be scheduled in the middle i.e. Monday + 2.5 = Wednesday. Why is it scheduling on Thrusday.
    (ii) In SNP Heuristics, period factor only caculate the date. It sets by-default Time as 12:00, but here system is setting 23:59:59, why?
    Thanks a lot in advance.
    Regards
    Rinju

  • Replenishment upto max. stock level during SNP heuristics run.

    Hi Experts,
    As per the requirement from client, we need to configure the setting of replenishment upto max. stock level during SNP heuristics run.
    I am using below settings in R/3 for achieving the expected results.
    (R/3 ) MRP1 u2013
    Lot size                       HB               Replenish to maximum stock level
    Maximum stock level       20,000
    (APO) Targ.Stk Lvl Methd   5 u2013 in APO u2013 product master -   lot size tab.
    Still, after heuristics run, the requisitions are getting created equals to forecast value. It should get generated as max. stock level maintained.
    Could anyone share their experience regarding this? Am I missing some additional setting?
    Inputs are highly appreciated!
    rgds/Jay

    Dear Jayprakash ,
    If the requirement is that  you have to replenish upto a certain stock level then instead of maintaining the  Max Stock level you can simply maintain
    SB : Safety stock from product master
    and in the  Safety stock field maintain the quantity as desired ( in this case 20000 ) . This probably will solve the problem  in your case . You may not require  to maintain Max stock level .
    Target stock level in heuristics also works fine with the following settings
    make sure you maintain
    Target stock level method as =5
    In Maximum Stock level  = maintain the quantity desired  ( 20000 in your case say )
    do not maintain  any safety stock method keep it blank .
    then location heuristics generates PR according to the  the maximum stock level.
    If still it is not working plz let me know what other settings you are maintaining probably we will find a way out .
    Hope it helps .
    Thanks
    Debsankar

  • Periodic lot Size

    Dear Expert,
    I working with Period lot size "W" with No. Of period 1 and the Period factor 1
    I maintain this setting in Both location production Plant & Distribution Center
    I have Demand from Distribution Center 2014, when i  run SNP Heuristic and after that PP/DS
    The stock transfer coming before the End date of the  PlOrd
    Start Date & Time:  11.11.2011   07:00:00  to 15:00:00      PReqRel
    Start Date & Time: 11.11.2011   07.:00:00  to  15:00:00    PlOrd
    Your Help Very Appreciated
    Regards
    Rami

    Hi Ashok,
    Thanks for your Response ..
    Of course i cheked the use period factor to working with period lot size
    Please advise
    Rami

  • SNP Heuristics- TSL parameter

    hello Gurus,
    I am using target stock level method 1 in product master;this setting works fine in interactive planning but not in back ground planning run.
    Can you please throw some light on significance of the below attribute and where/how to set this attribute
    Indicator for Selecting the SDT Profile from /SAPAPO/SCZPRF
    Use
    The selection you make here determines how the target stock level is calculated.
    You have the following options to calculate the target stock level:
    (0) Use the safety stock and target days' supply on the Product master.
    (1) Use target days' supply and safety stock only for the time period covered by the Time buckets profile.
    (2) Use target stock level specified in the Planning parameters only for the time period covered by the time buckets profile.
    (3) Use target days' supply and safety stock specified in the Planning parameters and apply the last target stock level value found in the past to additional periods that fall beyond the period defined in the Time buckets profile.
    (4) Use the target stock level specified in the Planning parameters and apply the last target stock level value found in the past to additional periods that fall beyond the period defined in the Time buckets profile.
    SAP recommends that you choose option (0) initially. For simulation purposes, you can change this setting by choosing, from supply network interactive planning, Planning -> Set Planning Parameters. After you have you have had an opportunity to run supply network planning in interactive planning mode using the different settings for simulation purposes, you can change this setting in the product master to make it valid for all supply network planning runs.
    Dependencies
    You must define options (1) to (4) in supply network interactive planning (Planning -> Set Planning Parameters) before you select an option in the product master data.

    Ha ha, I like this. New challenge!
    What about this scenarios.
    1. Forecast 500.000 unit per month. Lot size procedure Lot-for-Lot. Run SNP heuristic with time bucket month. Result - 1 SNP Pl.Order = 500.000 unit per month
    2. Forecast not important. Lot size procedure Fixed Lot size = 500.000 (or min/max lot size). Run SNP Heuristic with time bucket month. Result - 1 SNP PL.Order = 500.000 per month.
    You can have a separate job (separate selection loc/prod) for these SKUs with time bucket months (this is in the case when you are working with time bucket weeks).
    3. At transportation lane level. Create transport capacity resource and assign it to the t.lane. In the resource you have the possibility to restrict the capacity at 500.unit per time bucket month.
    Me too I have some issue at PPDS level. Can you give me some ideas for this issue http://scn.sap.com/thread/3596884
    Regards, Marius

  • Weekly Lot-sizing yielding incorrect Planned Order dates

    Hi All,
    need a help..
    Lot-sizing key = W2 (weekly)
    "Scheduling" on the config of the lot-sizing key = 3 (Period start := start and period end := delivery date). This data has been maintained for a material that is to be planned/produced on a weekly basis.
    Requirement --- Weekly planning on my material. MRP should return Planned Orders with Start Date = Reqt Date (of the Dependent reqt) & End date = Availability date (of the dep reqt).
    Currently, the system is calculating the "only" hours on the basis of the Routing data (I'm running Lead Time Scheduling) while creating Planned Orders during the MRP run against my expectation of spanning the production/order out over multiple days (per the lot-sizing config)
    Any clue would be of a great help
    cheers

    Thanks Mario,
    Had found that out during the course of my testing. I'm doing a Lead Time Sched, so obviously my reqt can't be met..
    So, we can conclude that though a weekly lot-sizing procedure is/could be compatible with LTS, the Config within the lot-size (field Scheduling = 3) cannot be used to influence the dates on the created Planned Orders...
    Cheers

  • Use of key figure 9ADFCST in SNP

    I am using APO V5.1.
    In particular I'm using SNP heuristics, and we have forecasts in the standard key figure 9ADFCST.
    As I understand it, this key figure contains the 'unconsumed forecast', and so is the original forecast (from APO DP) minus open sales orders and minus sales order despatches.
    I want to be able to distinguish between the situation where 9ADFCST is zero because the original forecast is zero (and we have no sales orders), and where 9ADFCST is zero because it has been fully consumed by sales orders/despatches.
    Any advice on this would be appreciated...

    Hi,
    I would recommend that you do not touch the 9ADFCST Key Figure and add a new Time Series KF for storing the original forecast (let's say CORFCST).
    When you release forecast from DP to SNP, in a next step, also copy your DP forecast to CORFCST using the program /SAPAPO/RTSCOPY.
    So, use original forecast KF CORFCST to see the values of the forecast that came out of DP, while 9ADFCST will tell you how much unconsumed forecast remains. When both values are zero, it's clear that your forecasted value was zero, otherwise, you could find out the original forecast using the KF CORFCST.
    Of course, other option is to go to forecast tab in RRP3 (product view) and check the consumption situation (how much of the forecast is consumed vs how much was available initially).
    Hope this helps.
    Thanks - Pawan

  • MRP Lot-Sizing Procedures PK

    Hi experts,
    When we use lot-sizing procedures PK, I have a problem about it.
    Can you please kindly help me.
    The problem is.
    When we run MRP and get the release date as past date in purchase requisition.
    I would not like system to propose release date as past date.
    Do we need more configuration for using lot-sizing procedures PK ?
    The settings are mentioned as below.
    * material master
    - Lot size in MRP1 view : PK
    - MRP Type in MRP1 view : PD
    - Procurement type in MRP2 view : F
    * MRP parameters
    - Processing key : NETCH
    - Create purchase req. : 1 (Purchase requisitions)
    - Delivery schedules : 3 (Schedule lines)
    - Create MRP list : 1 (MRP list)
    - Planning mode : 1 (Adapt planning data (normal mode))
    - Scheduling : 2 (Lead Time Scheduling and Capacity Planning)

    please read below for the detail explanation of the  release date.
    please check the example part of below.
    wish it help.
    tks.
    Purchase Requisition Release Date
    Specifies the date on which the purchase order
    should be initiated on the basis of the purchase
    requisition.
    The release date is based on:
    The
         purchasing department processing time defined for the plant
    The
         planned delivery time from the material
         master record or purchasing
         info record
    The
         delivery date
    The
         goods receipt processing time from the material master record
    Note
    The planned delivery time from the
    purchasing info record and the GR processing time are only taken into account
    if the purchase requisition was generated via materials
    planning.
    Example
    Processing time Planned del. GR processing
    Purchasing time time
    |----------|---------------------|--------|
    Release PO Delivery Date
    date date date required
    Date required: 01.10.2007
    GR processing time: 2 days (working days)
    Planned delivery time: 10 days (calendar days)
    Purchasing dept processing time: 2 days (working days)
    For the material to be available on the
    date it is needed, the purchase requisition must be released on 13.09.2007
    (requirement date less GR processing time, planned delivery time, and
    purchasing department processing time).

  • SNP Heuristics is not picking up contracts as source of supply

    Hi Experts,
      I have a strange situation here. I have integrated a vendor contract with APO, which has created an external procurement relationship and a valid transportation lane. When I create a receipt element manually through /n/sapapo/rrp3, the source of supply is determined rightly to this vendor and receipt is created.....but when I run location SNP heuristics interactively, system generates receipt element without any reference to this source of supply. Expectation is creation of receipt element with reference to vendor and contract...
    System release is SCM 5.1 with ECC 6
    Am I missing something?....please let me have your inputs...
    Thanks and regards,
    Raghav

    Hi Aparna,
       Thank you for your response.
    I have checked the note, but it is applicable till SCM 500 SP 13. Our's is SCM 5.1 and this is inclusive I suppose. As per the SAP SCM standard documentation, external procurement relationship between vendor and receiving plant can be created through following 3 docuements:
    1. Purchase infor record
    2. Scheduling agreement
    3. Contracts
    Additionally, as per documentation, even source list between plant and vendors can be integrated by enabling the same through R/3 transaction 'CIFPUCUST01'.
       I have worked with first two and SNP considers these for source determination. When I tried to integrate the contract, though it is creating TL between 'vendor --> receiving plant' and an active external procurement relationship, SNP is not found considering this for source determination. When I tried to use the source list for creating TL and esternal procurement relationship, the same is not creating any.
    What type of contracts can be used for SNP planning and what else required to be done for integrating source list? I have enabled source list in R/3 material master. Source list is maintained as 'MRP relevant' in R/3.
    Thanks and regards,
    Raghav

Maybe you are looking for