Lot size dependent / independent

Hi, please advise when the system uses this lot size times data in mrp4 view? Where we need to specify that whether lot size dependent or independent need to select? When the system uses this data and when the system uses the planned delivery days and in-house production days which is in mrp2? Pls advise.

Dear,
Planned Delivery Time use for  external procurement Like raw materials.
In-house production time use for in house manufacture materials like HELB and FERT.
In-house production time is independent of the order quantity.
Lot size depnendent timing calculate from the routing.  It is calculated byadding the lead times of all operations, the float before production, and the float after production.
You schedule the routing for a base qty The in the scheduling results screen click the button" scheduling results"
You will get the results screen in days.
In that screen at the botton there is abutton update material master.
After this go to CA96 There update the material master.
Please refer this link,
Re: set up time dependant and independant of order qty
Regards,
R.Brahmankar

Similar Messages

  • How to make lot size dependent in Material master?

    Hello Experts,
                   I created a Material master for a Finished product in Pharma industry and in work scheduling screen, under the section "In house production time in days", I see that "lot size independent". What change(s) in my settings in the Material Master can change it to "lot size dependent"?
    Does any changes in the  "Lot size data" section in the view "MRP1" have any effect on this field?
    Also one more question:
    Where is the Usage for BOM first specified? Is it in material Master or when creating a BOM?
    Thank you.
    Message was edited by: Visu Venkat

    Hi Visu
    No,Lot size data in MRP1 view will not have any effect in inhouse production time in work scheduling view.
    You need to maintain the base qty in work scheduling in order to get the scheduling time for lot size dependant.
    BOM useage is first specified only during BOM creation.
    Suppose if u maintain the BOM useage in material master before creation of BOM, then still u can create a BOM with different useage. During these case, there will be always inconsistencies.
    Hence Useage is always specified first during BOM creation.
    Hope u r clear now.
    Regards
    Vijay

  • Different fix lot size depending on the production version

    Hi all,
    I have the next scenario:
    2 production versions. 2 different fix lot size por each. So:
    Prod Version 1 - Fix lot size 200
    Prod Version 2 - Fix lot size 300
    I created the Quota Arrangement just to make SAP to take my favourite version. And trought the quota, I can define the lot size for each version. BUT.
    If I change the version in the order or in the planned order, the quantity don't change.
    So: How can I manage 2 different fix lot size for 2 different product versions? If I change the version once the order is created, how can I do the system change de quantity to the right one?
    Thanks in advante
    << Please do not offer points >>
    Edited by: Rob Burbank on Oct 1, 2010 2:53 PM

    I have n't  tried this scenario,
    This is my Idea
    Create a two production version
    for ex: lot size 100 to 1000, set the rounding profile qty as 1000
    for lot size 1001 to 99999, set the lot rounding profile value to 5000
    BY this way u can get the two lot based on the rounding profie
    Expert; please correct if i am wrong
    Edited by: Sundaresan . E. V on Oct 1, 2010 4:12 PM

  • Schedule with dependent lot size problem

    Hi,
        I maintain the setup/process/tear down time(base qty is 10) in Work Schedule view in MM02(dependent with lot size)..But the begin date/end date in these POs are the same when I create Production Orders with different qty.
        It seems my setting doesn't take effect..Do you have any suggestion?
    PO 1:   100 qty      Start date 11/10  End DAte 11/11
    PO 2:    1 Qty      Start date 11/10  End DAte 11/11
    PO 3:1000000 Qty Start date 11/10  End DAte 11/11
    Why the start/end date doesn't change based on my PO qty?thanks..

    Hi,
    Monst Yang wrote:
    >     I maintain the setup/process/tear down time(base qty is 10) in Work Schedule view in MM02(dependent with lot size)..But the begin date/end date in these POs are the same when I create Production Orders with different qty.
    In-house production time (lot size dependent or independent) is used for calculating the basic dates of planned orders when MRP is run with basic dates parameter (instead of lead time scheduling). However when production orders are created basic dates are always determined according to the production dates and production dates are determined by lead time scheduling. In other words, the lot size dependent production time data that you have maintained could only determine basic dates of planned orders, only if MRP is run with that parameter. In the case of your production orders, standart values of the operations and formulas of the work centers are used by lead time scheduling. Dates might be equal because scheduling formulas of work centers does not consider order quantities or labour hours, which would be multiplied by order quantities, are not maintained in routings. Investgate the production dates and scheduling of the operations in production orders. Also have MRP create planned orders to see the effects of lot size dependent times in master data. Be sure to emty the lot size independent production time in material master to avoid it overwriting lot size dependent time.
    Regards.
    Edited by: Özgen Canan on Nov 10, 2011 3:58 PM

  • Sequence dependent lot-size planning as a basis for PP/DS blocks?

    Hi ,
    I consider the following system setup for a Mill Products planning implementation .
    1) In SNP one performs SOP planning with common goals to adjust sales plan, establish equipment maintenance plan, transportation plan, etc. The first month of the SNP plan is supposed to be in daily buckets. Using the SNP optimizer is a good option since the business goal is to use equipment more efficiently, let's say to minimize setup costs, and there are warehouse limitations for semifinished products as well.
    2) In PP/DS we are going to use CDP and block planning since it is the best practice.
    3) SNP planned orders can be used as a basis for PP/DS blocks on the resource, upon the condition that the configuration of SNP product - kmat variant and block requirements match.
    In SNP i  see that the SNP PDS has a duration of 1 day (that's fine), but the sequence dependent lot-size planning requires a bucket of at least 1 week long (1 month in my case) since the SNP orders are sequence-optimized only inside of one bucket. The result of such an optimization are additional counters assigned to SNP orders according to their sequence  minimizing setup costs. However, orders are not scheduled according to the sequence.
    So far it looks like such a combination is not useful as
    - Orders in monthly buckets are not scheduled on days and cannot serve as a basis for block dates proposal for PP/DS block planning.
    - If a product production volume is less than 1 day, SNP cannot create any more detailed block in principle since the minimal time bucket is daily bucket.
    I searched over forums on these or similar topics, however no definitive answer so far for the question in the subj.
    Could anyone bring more  light on this ? Maybe I am missing something in the setup or sequence dependent lot size planning was designed for other purposes/industries?
    Best regards
    Vladimir

    Hello Asim,
    Issue one
    in product selection for propagation range you can set your selection criteria which selects the products dynamically. You just have to change your report variants for planning run. Do I misunderstand your concerns?
    Issue two
    Changing to planning procedure 1 will not delete the PFE but will prevent APO to create a new entry after any MRP-relevant changes happen or heuristic SAP_PP_020 (which creates the initial entry and does the low level code determination) is run.
    In some cases procedure 1 will still create a PFE. Please check customizing for details. Thats why I would recommend to create a new planning procedure with "no reactions".
    As soon as you prevent APO from creating new PFEs you can just once delete the PFEs in /SAPAPO/NETCH by just setting the first column for these materials blank (select your materials, mark column, delete indicator).
    Corresponding table to MDVM is /SAPAPO/PEGKEY. Indicator for PP/DS is NETCH_RRP.
    If material is not planned in APO you do not need a PFE in APO.
    Issue 3
    Maybe utilize table /SAPAP/PEGKEY
    As I said if you prevent creating the entry you just have to delete (set indicator blank) once.
    Hope that helps.
    Regards,
    Uli

  • Relation between PO Qty and Minimum Lot size of material master

    I have maintained "100" in minimum lot size ( MRP1 View, table MARC and field BSTM) for the material.
    I am also succssed to create the Purchase order for 2.5 Qty for the same material. '
    I wanted to know, how system is allowig to create the PO with lesser qty or is this view is maintained only for sales?
    Please give your expert comments on the same.
    Thanks,
    Vikas
    99301 03991

    Used for claculate the procurement qty during MRP and depends on the lot size procedure you select. quota arrangement also uses this lot size.
    [http://help.sap.com/saphelp_erp60_sp/helpdata/en/f4/7d26ad44af11d182b40000e829fbfe/content.htm]
    Edited by: Karthik on Jul 8, 2011 9:47 PM

  • How to perform Data Collection on single SFC with QTY = 1 with material lot size 1?

    Dear experts,
    We are working with SFC qty>1 on a relaxed routing. At a given operation we want to collect the data on single quantity; i.e. SFC qty on that operation, where the collection will happen, will be 1.The corresponding material lot size is for ex 10. The operator must be able to collect data on SFC with qty=1 multiple times until the quantities will be consumed. He must be also able to collect other values on the remaining quantities on the same operation with the same DC group or other DC groups. How many times the data must be collected is dependent on the shop order build quantity. The data may be collected several time but not more than the build qty. In other words some specific data will be collected on a qty of a product while others will be collected against remaining quantity. The data collection must be also done in a serialized manner.
    Here's what we have set up so far:
    1) 3 DC groups, each DC group has 3 data fields.
    2) Each data field has the following restrictions:  Required Data Entries = 0 and Optional Data Entries = 1
    3) All DC groups are attached on the same combination of operation\material\routing
    4) we are using relaxed routing
    Process description:
    The operator must be able to collect any data field on single product. For that he will enter the operation where the data collect are attached, he will enter the SFC with qty=1 then he will run the data collection after selecting the appropriate DC Group and entering the needed information. The operator will complete the SFC with qty=1.
    The operator will pick the next product, select the same SFC and enter qty 1 and collect other value against this product.
    Problem is:
    Once the first collection is done on a given SFC with entered qty=1, the system is not allowing the operator to do further collects on the same SFC with qty=1 or any other quantity. He cannot select any DC group from the DC group list. We tried also with the table selection menu on the DC Group list but nothing can be selected.
    So we tried to play around with the DC group definitions as follows:
    A) we set Required Data Entries = 0 and Optional Data Entries = 10. Still the operator was not able to select any DC group after collecting data the first time. We tried to reopen the pod and list again. But we get the same blocking behavior.
    B) we set Required Data Entries = 10 and Optional Data Entries = 1. The operator was able to select the DC group after collecting data the first time. BUT operator must enter the data fields 10 times on one SFC quantity, which is not what we want. Besides again he cannot collect other information on remaining quantities on the same operation.
    C) There's an option to serialize the SFC before reaching the operation where the collection is happening, then merging ofter complete. Automation is needed here; hence customization. We are highly avoiding customization now, since we expect the data collect to work well on single quantities even when the main SFC has qty>1
    Questions:
    1) Are we missing any kind of further configuration\setup?
    2) Or the current system design does not allow collecting data on single quantities of an SFC which main quantity is greater than 1?
    3) Looking at this link Approaches to Collection of Data - SAP Manufacturing Execution (SAP ME) - SAP Library, there's nothing mentioned about same SFC number with multiple quantities!!!
    We are using SAP ME 15.0.3.0.
    Thanks in advance for your help
    Ali

    Ali
    to collect data for the same SFC multiple times, your system rule "Allow Multiple Data Collection" needs to be set to true for the site.
    Stuart

  • Material Cost Estimate with different lot size.

    What happens if the material cost estimate is run twice using different lot sizes each time  (all other parameters unchanged) for the same period?
    Will the cost estimate run later overwrites the results from cost estimate run earlier (though the lot size is different)? What is the role of lot size in a material cost estimate?

    The costing lot size impacts your cost estimate if you have lot size independent costs (i.e. setup cost).  Those fixed costs are spread over the costing lot sizee to give you a cost per unit..  Larger costing lot sizes can also help you minimize rounding issues.
    You can only have one marked cost estimate in a given period.  However, you can create and save a cost estimate as many times as you want as long as you have not marked it for release.  When you save the estimate it will overwrite an existing estimate.  You also have the option of creating multiple estimates under different versions or with different costing variants.

  • Lot size

    The parents material lot size is fixed lot size , child component lot size is 2 week lot size.  ( ie. 2 week = 10 Days ).
    question:
    If the demand for parent material in month,after MRP run the dependent requirement for child component also getting generate only one planned order.
    What are the possibilities if the parent demand in month, child requirement is needed in weekly basis .Any chance to get the child requirement in weekly by changing lot size or any other possibilities.

    Hi,
    Thanks for your answer. if we change the lot size for dependent material to weekly , biweekly or fixed etc....
    The dependent req. will generate according to the lot size that is absolutely correct. but planned order or purchase req. will create according to the parent demand (ie .Adding of dependant req. what ever falling with in the lot size period and for that quantity planned order or purchase req. is getting created )
    Actually my requirement is for the each dependent requirement one planned order should get generate .

  • Minimum Lot Size Ignored

    Hello All,
    To replicate scenario, I have created new material with minimum lot size 10 pcs and created independent requirement (LSF) and then created scheduling agreement.
    Independent requirements as 8 pc for every day.
    Now when I run the MRP and check in MD04, for the last requirement, planned order was raised for just 9 pcs, ignoring minimum order qty/minimum lot size functionality.
    Just for information, Lot size -EX, MRP type PD, Strategy group 10 (though these factor doesnot influence).
    Any more settings/customizing required?
    BR,
    Krishna

    Dear Krishna,
    I guess you must have activated the check box for Last Lot Exact for the Lot size - EX in T.code OMI4.
    If so means remove this and then check with new requirements and MRP run with planning mode - 3.
    Regards
    Mangalraj.S

  • Lot Size Planning for Procurement

    Hi  guys
    In our company we work with minimum lot sizes for procurement, and we need to configure minimum lot sizes for procurement in the SNP optimization run. It´s posible to do it in SNP, pls can someone tell me how to configure this in SNP?
    David

    Hi David,
    I am glad to hear that.
    Regarding your performance issue: it is very usual to have long runtime when using discrete model.
    The complexity of this model is much higher than a linear problem; so the optimiser takes time to find THE optimal solution.
    However there is a lot you can do to make it better:
    1. Split your model: instead of running 1 big optimiser, run serveral smaller one in parallel.Ensure your model are all independant (e.g. no common product or resource)
    2. Use decomposition: (product/ time/resource; based on your scenari) to simplify the porblem, hence speeding the solution.
    3. Set a maximum time
    You do not have to wait for THE optimal solution. The optimiser can sometime very quickly find a very good solution; the last hours are spent "fine tuning" it. Potentially, you might not be able to see the difference between a 4h job and the 15H one).
    Hence SAP advises to set a maximum runtime when working with discrete model.
    The question is how to define this maximum time to optimise the ratio solution quality / runtime.
    Answer: test it, check the result. Be aware that perfomrance testing for the optimiser can take a while.
    4. fine tune you optimiser setting
    There is a couple a finetuning that can be done to improve performance, especially for discrete model.
    I will not be able to help you woth that.
    As far as I am aware only the SAP optimiser team has the expertise to help here.
    I strongly recommand to contact them; their help is often invaluable. They will also help you to define the 3 first points.
    I hope this will help you.
    Thanks and Regards
    Julien

  • Fixed lot size key has no effect on planned orders generated for VC PIRu2019s

    Hello gurus,
    does anyone have an idea why the fixed lot size key is not having an effect on the planned orders that are generated for the Planned Independent Requirements (PIR) for MTO configurable materials. My client is using planning strategy 56.
    I have copied & customized the Fixed lot size key FX to suit the MTO production (u201CLot size as in short-term periodu201D activated) that works nicely even with configurable materials when a planned order is generated for a sales order. But the planned orders in the preplanning segment, i.e. that were generated for PIR's, are still created equally to the PIR quantity.
    Is this behavior an error or an SAP feature? Though, I have reviewed the OSS Note 437098 that might be related to this. Can anyone tell me if it is related to this issue?
    Regards,
    Mikko

    Got the answer fro SAP:
    Please consider the following note, which provides the explanation about this behavior of the lot-size, when VSE requirements are used:
    125498 - MRP/Docu: Planning segment and lot-for-lot order quantity
    The following section of the note describes your scenario in detail:
    "The planned independent requirements for a material are in a separate
    planning segment (planning strategy planning without final assembly,
    requirements type VSE, VSEV).
    You enter a rounding value or a rounding profile or an lot size that is
    not exact in the material master.
    Material Requirements Planning:
    In Material Requirements Planning, planned orders are generated for the
    planned independent requirements. The lot size settings (such as fixed
    lot size or minimum lot size) are also not taken into account."

  • Material set to lot size TB not summing up orders when covering

    Hello all. I'd appreciate any input on this problem we're seeing.
    We have a material that has lot size set to "TB" (Daily lot size). This leads us to expect that demands on this material will be covered by purchase orders summing up all  the demands for this day.
    For instance we currently have 10 orders for 11. sep in different quantities from 1 to 3. Since the material is set to lot size TB we would expect to see a purchase order for 19 pieces which is the total.
    But instead we get a bunch of small purchase orders, the system doesn't appear to sum up as expected.
    Has anyone any ideas about why this may be so?
    Regards
    Simon Pedersen

    Thanks for the answers so far, It's not letting us make much progress though.
    The material is a trading good (HAWA). It has no BOM. The Collective indicator on MRP4 is not maintained (as far as i know it should not be since there are no dependent requirements involved). The demand is triggered by Sales Orders.
    The purchase requisitions get generated by the MRP run based on these sales orders. That is what we don't understand, since the material is set to TB the MRP should make a single bigger order instead of many small ones.

  • /SAPAPO/RRP_PLANNING   calculation requirements lot size period

    Hi all,
    In badi:  /SAPAPO/RRP_PLANNING  Method: AFTER_NETTING I want to recalculate the requirement (QUANTITY in CT_REQ_IO) depending on the period type of the lot size ( SAPAPO/MATLOTSZ-PERVR ).
    So feg, requirements for 1 product for 1 day, the period type of the lot size = W week -> so I have to summerize all quantities for that product for 1 week.
    Is there a function module to do this? Because you can have week but also month, quater, ...
    thanks a lot,
    Caroline,

    Hi,
        Please see the BAdi documentation available also one example class is given from which you can use the code whichever is applicable to your requirement.
    Class Name: /SAPAPO/CL_EXM_IM_RRP_PLANNING
    Regards,
    Saurabh

  • Mixed-price variance &  Lot size variance

    Dears Gurus,
    Can anyone give a detail explanation & examples of Mixed-price variance & Lot size variance?
    (After reading sap library, I still didn't get clear idea)
    Thanks
    Ellie

    Mixed Price Variance :- This is the variance between a standard price that was calculated in a mixed calculation for more than one procurement alternative and the costing of a procurement alternative.
    For Example : Standard Cost was made for a Raw Material A purchased from 2 sources ( X and Y ) with 50/50 ratio..
    Actuals it was made of a Raw Material A purchased from X and Y ( in 25:75 ratio ).
    The same can happen for production versions also . Standard May have version 1 and 2 (in 50:50 ratio).. actual have version 1 and 2 ( 40: 60) ratio .
    Lot Size Variance :  Variance due to effect of lot-size-independent costs when the lot size is changed .
    For Example : we may have consumables cost per 10000 lot size . Original Lot size during creation of standard is 10000 .
    Actually lot size was 150000 .. hence due to change the lot size.. the cost has increased and its lot size variance..
    Hope it clarifies..
    Regards
    Sarada

Maybe you are looking for