Lot Size different to master data

Dear Gurus,
In master recipe, when I am trying to save the following error message is appearing.
Lot size different to master data
Can anyone help me on this issue.
Thanks in advance,
Arul.

Dear,
Please check,
When a master recipe is scheduled, the lot size can be proposed in two different units of measure
If a base quantity is maintained in the material master (view Work scheduling), the lot size is entered in the base quantity of the material master. If no base quantity is maintained, it is entered in the unit of measure of the recipe header (header unit).
That is, the unit of measure of the lot size is predefined by the system and you cannot choose it.
If the lot size is entered in base unit of measure for scheduling, up to now, no conversion between base unit of measure and header unit occurs. The lot size (in base unit of measure) is converted into the operation quantity directly via the conversion factors of the operation. The scheduling result is incorrect. and system display the message   Lot Size different to master data.
Regards,
R.Brahmankar

Similar Messages

  • How to find the size of the master data objects in the BW system?

    Hi,
    We would like to understand the size of the master data tables overall for a specific source system (Logical name is Ex.ABCD, which supplies all master data to BW). Can you please advise the procedure to find out this?
    Is there any table that will allows to see all the master data objects related to specific sources system so that we can find out that table size? Thanks.
    For example, we have many Texts, Hier & Attributes.
    0COUNTRY_TEXT
    0REGION_TEXT
    0PERSON_ATTR
    0MATERIAL_LPRH_HIER
    Advance Thanks.
    Edited by: BW USA on Feb 2, 2010 10:52 AM

    Hi,
    You can find out all the master data tales used in the BW system by
    Tcode : SE11
    Enter as /BIC/P* for master data tables and press F4 which gives list of master data tables currently used in BW system.
    Similarly for Texts  /BIC/T*  and press F4
    Similarly for Hierarchies /BIC/H-* press F4
    and can know the size of the all tables.
    Thanks,
    Gopal

  • 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

  • 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

  • Min max lot size time based for use with SNP and PPDS

    Hi all, Is there anyway to set up time based min and max lot sizes? ie we want to have a Max lot size which is small for use with the first 3 months of our plan which starts life in SNP and then converts to PPDS and into blocks for block planning, but months 4 to 36 we want to leave as large max lot sizes as there is no need to have the small max lot sizes for the different horizon.
    As far as I can see there is only a material/plant lot size  and Max lot size and no way to have a different setting in a different time period.
    Thanks
    j

    Hi John,
    As you know, in the product master, the lot size maintenance is time-independent, so that obviously can not be used for your scenario. As per my understanding, to meet this using standard functionality, you can maintain multiple product specific t-lanes (for STRs) and PDSs (planned orders) with required lot size ranges and validity dates (for short or long term horizon). But, again since the validity of t-lanes and PDSs will not be automatically rolling forward so the updating the validities will be a challenge.
    The other option could be to enhance the heuristic functionality at lot size selection step while creating order.
    Regards,
    Umesh

  • SNP quota arrangement with fixed lot size

    Hi all,
    i have a question regarding quota arrangement for external procurement in snp heuristic. Whe have 2 sources of suppy created by info record. The quota is 25% for the first and 75% for the second one. In product master there is maintained a fixed lot sice of 500.000. Im wondering that the snp heuristic creates 2 requisitions of 500.000 for each sos at the same day. So we get an serios excess. Any ideas?
    Kind regards,
    Christian

    Hi,
    thanks for reply. Ok, normally net requirement calculation works properly. In case of a shortage the heuristic shall apply an receipt with the fixed lot size wich is maintained in material master. However, in out particular case it generates the double receipt quantity which is not needed at the receipt date.
    The heuristic should do the following:
    Day 01 Stock 100   
    Day 02 DepDmd 20 
    Day 03 DepDmd 20 
    Day 04 DepDmd 20
    Day 05 DepDmd 20
    Day 06 DepDmd 20
    Day 07 PurReq 100 !! Source 1!!
    Day 08 DepDmd 20
    Day xx PurReq 100 !! Source 2!!
    and not:
    Day 01 Stock 100   
    Day 02 DepDmd 20 
    Day 03 DepDmd 20 
    Day 04 DepDmd 20
    Day 05 DepDmd 20
    Day 06 DepDmd 20
    Day 07 PurReq 100 !! Source 1!!
    Day 07 PurReq 100 !! Source 2!!
    Day 08 DepDmd 20
    In this example 100 would be the fixed lot size from material master.
    Best regards,
    Christian

  • Performance: reading huge amount of master data in end routine

    In our 7.0 system, each day a full load runs from DSO X to DSO Y in which from six characteristics from DSO X master data is read to about 15 fields in DSO Y contains about 2mln. records, which are all transferred each day. The master data tables all contain between 2mln. and 4mln. records. Before this load starts, DSO Y is emptied. DSO Y is write optimized.
    At first, we designed this with the standard "master data reads", but this resulted in load times of 4 hours, because all master data is read with single lookups. We redesigned and fill all master data attributes in the end routine, after fillilng internal tables with the master data values corresponding to the data package:
    *   Read 0UCPREMISE into temp table
        SELECT ucpremise ucpremisty ucdele_ind
          FROM /BI0/PUCPREMISE
          INTO CORRESPONDING FIELDS OF TABLE lt_0ucpremise
          FOR ALL ENTRIES IN RESULT_PACKAGE
          WHERE ucpremise EQ RESULT_PACKAGE-ucpremise.
    And when we loop over the data package, we write someting like:
        LOOP AT RESULT_PACKAGE ASSIGNING <fs_rp>.
          READ TABLE lt_0ucpremise INTO ls_0ucpremise
            WITH KEY ucpremise = <fs_rp>-ucpremise
            BINARY SEARCH.
          IF sy-subrc EQ 0.
            <fs_rp>-ucpremisty = ls_0ucpremise-ucpremisty.
            <fs_rp>-ucdele_ind = ls_0ucpremise-ucdele_ind.
          ENDIF.
    *all other MD reads
    ENDLOOP.
    So the above statement is repeated for all master data we need to read from. Now this method is quite faster (1,5 hr). But we want to make it faster. We noticed that reading in the master data in the internal tables still takes a long time, and this has to be repeated for each data package. We want to change this. We have now tried a similar method, but now load all master data in internal tables, without filtering on the data package, and we do this only once.
    *   Read 0UCPREMISE into temp table
        SELECT ucpremise ucpremisty ucdele_ind
          FROM /BI0/PUCPREMISE
          INTO CORRESPONDING FIELDS OF TABLE lt_0ucpremise.
    So when the first data package starts, it fills all master data values, which 95% of them we would need anyway. To accomplish that the following data packages can use the same table and don't need to fill them again, we placed the definition of the internal tables in the global part of the end routine. In the global we also write:
    DATA: lv_data_loaded TYPE C LENGTH 1.
    And in the method we write:
    IF lv_data_loaded IS INITIAL.
      lv_0bpartner_loaded = 'X'.
    * load all internal tables
    lv_data_loaded = 'Y'.
    WHILE lv_0bpartner_loaded NE 'Y'.
      Call FUNCTION 'ENQUEUE_SLEEP'
      EXPORTING
         seconds = 1.
    ENDWHILE.
    LOOP AT RESULT_PACKAGE
    * assign all data
    ENDLOOP.
    This makes sure that another data package that already started, "sleeps" until the first data package is done with filling the internal tables.
    Well this all seems to work: it takes now 10 minutes to load everything to DSO Y. But I'm wondering if I'm missing anything. The system seems to work fine loading all these records in internal tables. But any improvements or critic remarks are very welcome.

    This is a great question, and you've clearly done a good job of investigating this, but there are some additional things you should look at and perhaps a few things you have missed.
    Zephania Wilder wrote:
    At first, we designed this with the standard "master data reads", but this resulted in load times of 4 hours, because all master data is read with single lookups.
    This is not accurate. After SP14, BW does a prefetch and buffers the master data values used in the lookup. Note [1092539|https://service.sap.com/sap/support/notes/1092539] discusses this in detail. The important thing, and most likely the reason you are probably seeing individual master data lookups on the DB, is that you must manually maintain the MD_LOOKUP_MAX_BUFFER_SIZE parameter to be larger than the number of lines of master data (from all characteristics used in lookups) that will be read. If you are seeing one select statement per line, then something is going wrong.
    You might want to go back and test with master data lookups using this setting and see how fast it goes. If memory serves, the BW master data lookup uses an approach very similar to your second example (1,5 hrs), though I think that it first loops through the source package and extracts the lists of required master data keys, which is probably faster than your statement "FOR ALL ENTRIES IN RESULT_PACKAGE" if RESULT_PACKAGE contains very many duplicate keys.
    I'm guessing you'll get down to at least the 1,5 hrs that you saw in your second example, but it is possible that it will get down quite a bit further.
    Zephania Wilder wrote:
    This makes sure that another data package that already started, "sleeps" until the first data package is done with filling the internal tables.
    This sleeping approach is not necessary as only one data package will be running at a time in any given process. I believe that the "global" internal table is not be shared between parallel processes, so if your DTP is running with three parallel processes, then this table will just get filled three times. Within a process, all data packages are processed serially, so all you need to do is check whether or not it has already been filled. Or are you are doing something additional to export the filled lookup table into a shared memory location?
    Actually, you have your global data defined with the statement "DATA: lv_data_loaded TYPE C LENGTH 1.". I'm not completely sure, but I don't think that this data will persist from one data package to the next. Data defined in the global section using "DATA" is global to the package start, end, and field routines, but I believe it is discarded between packages. I think you need to use "CLASS-DATA: lv_data_loaded TYPE C LENGTH 1." to get the variables to persist between packages. Have you checked in the debugger that you are really only filling the table once per request and not once per package in your current setup? << This is incorrect - see next posting for correction.
    Otherwise the third approach is fine as long as you are comfortable managing your process memory allocations and you know the maximum size that your master data tables can have. On the other hand, if your master data tables grow regularly, then you are eventually going to run out of memory and start seeing dumps.
    Hopefully that helps out a little bit. This was a great question. If I'm off-base with my assumptions above and you can provide more information, I would be really interested in looking at it further.
    Edited by: Ethan Jewett on Feb 13, 2011 1:47 PM

  • MRP run with lot size as per prod. version and capacity levelling

    Dear PP experts,
    Hi, We are working with strategy 10. For SFG and FG produced inhouse we have created BOM and recipe with production version.
    For example:
    I have a production version with batch size as 100 Kg.
    I load PIR for 500 Kg in MD61.
    I have maintained lot size as EX in the material master but I have not defined mini. and max. lot size.
    Is it possible during the MRP to consider the production version batch size if the mini. and max. lot size is not maintained in the system and create 5 Planned Order of 100 Kg each.
    I know, how it can be done by using lot size in material master or by maintaining schedule lines in MD61 or by maintaining quota. But if nothing is maintained is it possible for the system to create 5 Planned orders as per the production version batch size.
    Pl. check if this is possible and revert back.
    Regards,
    Prashant

    Hi
    No, system will not consider the size that maintained in the production version  for the creation of planned order while the mrp run .
    This lost size is used to validate the bom/ routing combiation for the particular  pv of the material

  • Manual Lot Size issue in SNP

    Hi Gurus,
    I have an issue while creating planned orders manually in the planning book as it is not splitting into the lot size which was maintained in the product master.
    Some details on the issue:
    I have a product X and I maintained '4000' as the fixed lot size in product master. When I enter 20000 it should spilt it into 5 batches and which is not happenning and it is placing the entire thing as one bulk order of '20000'.
    (If I run heuristics, it is splitting basing on the lot size maintained).
    It was working correctly for 1 product and for many of the products it is not working. All the parameters for the products are same and there is no difference.
    For the product which was working correctly for one user and for the same product if I try it is not working.
    I probed more into the issue to see if any parameters were added in his profile, there is one custom parameter which is assigned which splits the planned orders basing on the lot size maintained. I even assigned that profile, it worked once and later it is not working.
    The strange thing is for one user it works and for other users it doesn't even work for the same product.
    Note: We recently moved from SCM 4.0 to SCM 5.1.
    Did any one faced such kind of issues before? Any suggestions are highly appreciated.
    Thanks and regards,
    Murali.

    Hi Murali,
    I am surprised to read the issue.  I will never expect manual planned order to get split.  The lot size settings are applicable only for automated planning i.e. heuristic (MRP in R/3)
    If you have indeed observed that the system splits the orders by lot size, I have nothing to comment.  (probably that is why you did not get a reply for almost a day.
    If you have found some settings and find that they do not work, please raise a message to SAP for the same.
    I do not think system should split the manual planned order.
    Regards,
    Nitin Thatte

  • MRP lot size?

    HI All,
    Guys i configured M.R.P Type and M.R.P Controller, but I am unable to understand the M.R.P Lot size?
    while i am creating a material in mm01 lot size is not allowing me to chose any other option except EX-Lot for Lot Order quantity.. could any one suggest why is it so..?
    Thanks and Regards,
    Chinta
    Edited by: Csaba Szommer on Feb 17, 2012 11:46 AM

    > while i am creating a material in mm01 lot size is not allowing me to chose any other option except EX-Lot for Lot Order quantity.. could any one suggest why is it so..?
    Do you mean you can see all the lot sizes but system is not allowing to select or you can see only EX? Because only "EX" lot size doesnt require further data. But if you select any other lot sizes like "FX - fixed lot", you also need to enter the fixed lot size value in fixed value. if you are dealing with CBP, below are the important lot sized to use.
    Lot-for-Lot Order Quantity
    Fixed Lot Size
    Replenishment up to Maximum Stock Level
    Check this SAP site to know more
    [Lot size|http://help.sap.com/saphelp_40b/helpdata/en/7d/c27177454011d182b40000e829fbfe/content.htm]

  • HR Master Data Distribution through ALE

    Hi All,
    Iam new to HR module.
    I want to know what are the transactions to create HR master data like employee etc.
    I want to send this HR master data from one SAP system to another SAP/non-SAP system through Idocs.
    Can anyone guide me with an example for craeting the master data and sending the data through Idoc.
    Thanks a lot in advance

    For HR master data : PA30,PA40 .
    For HR ALE data transfer: PFAL.
    Plz SEARCH in SCN before posting, you will get lot of information.

  • I need tables for prepare the master data templates for PM

    Dear Experts,
    can we prepare the master data templates by using the tables? if its possible means how we can prepare and what we have to considered ? is it right way or wrong?
    please suggest me to prepare the masterdata templates for ever use. if any small corrections we can correct it at usage time.
    please help me
    thanks a lot in advance

    Dear Jalu,
    Master data Templates have to be prepared based on Client's requirement after understanding their Business.
    For example, in Equipment master there are ~ 60 to 70 feilds, no client requires all of them. Some are inherited.
    After client requirement freezing, record LSMW and based on that prepare the Template.
    Regards,
    MLN Prasad

  • Daily lot size not working for more than 5 days grouping

    Dear All,
    I want to create the procurement proposal for 6 days once. So I have created new lot size ZB by copying TB and maintained no of periods as 6.
    Assigned the lot size in Material master. After MRP run, the procurement proposal created for every two weeks on Monday. It is not created as expected (6 days once). Is there any other settings needs to be maintained to achieve the requirement?. The same problem happening for the no of periods 7,8,9 also with daily lot size.
    I don't want to use the planning calendar for this. Daily lot size is working only upto no of periods as 5.
    Could you please someone explain the standard functionality of daily lot size with combination of no of periods?
    Thanks in advance.
    Regards,
    Ganesh

    Ganesh,
    Check if your lot size is something similar to screenshot below. It is important that you have lot sizing procedure as 'Period lot size' and period as 'Daily lot size'
    With the above lot size (number of period as 8 days) I can see expected results.
    Regards,
    Himanshu

  • Min Lot Size and Rounding value

    Hello MM  Gurus
    need a small help!
    I m a bit confused regarding the  use of Min lot size and Rounding value in material master "MRP 1" view..
    can some body teach me a detailed functionlity for both..
    As both serve the purpose ..for e.g. my requirement is 7 and min lot is 10 system will create proc.proposal for 10
    in similar way if i use rounding value as 10 , then als system will create proc.proposal for 10 only even if requirement is 7.
    grateful if you could pl expain me the functionality of both...
    another query..if I use Min lot size in material master will the same will serve the puspose of  <b>min order qty ( maintained in PIRs)</b>
    i'lll appriciate with good reward points...thanks in advnace
    Br
    Sumit

    Helo Guys..
    Thanks for valuable inputs..
    i have assigned the appropriate rewards ..
    pl clear my this doubt also
    e.g. for a materials
    Min Lot size - 40
    Rounding value 25
    requirement is for - 35
    will it be 40 or 50 ..i understand 50..
    j
    ust anothe rquery..pl treat this separate issue..and separate rewards will be given
    <b>can I use max stock level w/o use of  lot size "HB"</b>
    e.g. if my max stock level is 80
    and min lot size is 30 and current stock is 60
    what'll be my proc proposal created by MRP , i dont want system to cross 60 stck,,
    Thanks in advance
    BR
    Sumit

  • Custom lot size

    Hi Experts,
    In a MTO scenario for the FG i have created sale order of 1000, fixed lot size in material master of FG is 100. System has created a plnned order of 1000. I want to divide the planned order into 10 orders as per the batch size (fixed lot size) of 100. Is it possible through custom lot size?
    Regards
    Sm

    you can use the Distribution key in production version of the material master
    This key Determines the split to be used for dividing the quantities of a planned order or a production order into partial quantities. In so doing, the relationship between time and quantity produced is established.
    Regards,
    Santhosh

Maybe you are looking for