Lot Sizes Used for Fore cast planning

Dear all,
<b>For fore cast planing and Automatic reorder point planning what are the lot sizes are use full and what are the advantages and effects for each lot size procedure.</b>
I am expecting answer for this question from all of you.
Regards,
Krishna

Hi
These fore cast planing and Automatic reorder point types are consumption based planning.
Hence for these MRP types normally, lot for lot ( EX ) will be used.
You can go through the following link for further info on lot sizing procedures.
http://help.sap.com/erp2005_ehp_01/helpdata/en/f4/7d3f9344af11d182b40000e829fbfe/frameset.htm
Regards
YMREDDY

Similar Messages

Lot size use for splitting req. qty. with Two vendors

Hello PP experts,
We have two vendors and we want the each requirement to be split into the two vendor with 30 % for 'A' and 70 % for 'B'.
What are the IMG and master data setting required for the above scenario?
Please let me know whether can will use lot size 'ES' with splitting quota indicator marked in OMI4.
Waiting for your reply.
Regards,
Mona tiwari

Hi Mona,
You have to maiantain first quota arrangement (MEQ1) for the two vendors with alloting the percentage to split the Planned orders/PRs in planning run. Apart from this maintain the lot size either EX, FS or ES with split indicator marked in OMI4 for the quota.
Yes, maintain Quota allowed key in MRP (4) either in purchaing view or in MRP2 view as said by Prasobh.
If helps rewards points.
Regards
TAJUDDIN
Message was edited by:
TAJUDDIN MOHAMMED

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

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

Lot size key HB with a planning calendar

I would like to be able to continue to use lot size key HB (replenish to maximum stock level), but with a planning calendar in order to specify Friday deliveries. However, the system does not appear to be capable of doing this. Does anyone know a way around the system limitation?
Thanks in advance!

I appreciate the suggestions. I would very much like to use a "Friday" planning calendar, however, if I changed the lot size key to PK - I can no longer replenish to a maximum stock level (unless someone knows of a way to get MRP behavior like lot size key HB but with something like PK).
I also tried using the "Planning cycle" field on the MRP 1 screen, but it appears to require time-phased planning - which again seems to rule out use of Lot size key HB.
Any other ideas?
Thanks again,
Ed

Vector.size() using in for loop

hi,
i would like to know whether performance can be improved by using Vector.size() outside a loop than inside a loop
int size=VectorObj.size();
for(int i=0;i<size;i++)
is the above a better code than below
for(int i=0;i<VectorObj.size();i++)
please let me have your comment on this

It will be faster in the first case, but as others have already mentioned, you will run into problems if your vector is changing during the loop. If your vector IS changing, then case 1 could: a) miss the new additions to the vector, or b) throw an ArrayIndexOutOfBoundsException because the vector is smaller than it originally was (ie an item was removed during the loop).
Case 2 may also give you trouble: it may miss some elements at the end of the vector if some elements are removed during the loop. If you have "one" "two" and "three" in the vector, then remove "two" when you read it, the loop will never get to "three".
A solution to these is to clone the vector for the loop and use the original vector for additions and removals.
import java.util.Vector;
public class VectorLoop{
     public static void main(String[] args){
          bad1a();
          try{
               bad1b();
          }catch(Exception ex){
               System.out.println("Exception thrown");
          bad2();
          good();
     public static void bad1a(){//new element not reached
          System.out.println("\nBad 1a:");
          Vector vec = new Vector();
          vec.addElement("one");
          vec.addElement("two");
          vec.addElement("three");
          int size = vec.size();
          for(int i=0; i<size; i++){
               System.out.println(vec.elementAt(i).toString());
               if(vec.elementAt(i).equals("two")){
                    vec.addElement("four");
     public static void bad1b(){//exception is thrown
          System.out.println("\nBad 1b:");
          Vector vec = new Vector();
          vec.addElement("one");
          vec.addElement("two");
          vec.addElement("three");
          int size = vec.size();
          for(int i=0; i<size; i++){
               System.out.println(vec.elementAt(i).toString());
               if(vec.elementAt(i).equals("two")){
                    vec.removeElementAt(i);
     public static void bad2(){//"three" not reached
          System.out.println("\nBad 2:");
          Vector vec = new Vector();
          vec.addElement("one");
          vec.addElement("two");
          vec.addElement("three");
          for(int i=0; i<vec.size(); i++){
               System.out.println(vec.elementAt(i).toString());
               if(vec.elementAt(i).equals("two")){
                    vec.removeElementAt(i);
     public static void good(){
          System.out.println("\nGood:");
          Vector vec = new Vector();
          vec.addElement("one");
          vec.addElement("two");
          vec.addElement("three");
          Vector vec2 = (Vector)vec.clone();
          int size = vec2.size();
          for(int i=0; i<size; i++){
               System.out.println(vec2.elementAt(i).toString());
               if(vec2.elementAt(i).equals("two")){
                    vec.removeElementAt(i); //remove from ORIGINAL vector.
}Of course the over-head of cloning will slow you down...another solution may be to have an add vector and a delete vector wich will keep track of items to be added/removed AFTER the loop...there are other complexities that will crop up with this, however.
I believe that the clone() solution is the only thread-safe one.
Hope this helps.

PLANNING CALENDER IN LOT SIZE

Hi
What is the function of Planning Calender in Lot Sizing procedure in SNP.

Hi
You can define the planning calendar to define the periodicity of lot size.
For example in our case we want to SNP to create requirement only in alternate month based on lot size.
So we create planning calendar which consist only alternate month and attach to lot size.
Now when we execute the SNP planning, it will create supply element only in alternate month.
I hope this will give insight of it. Please let us know , if it helps you.
Thanks
Amol

Help on Planning Calender and lot size procedure settings

Hi Gurus,
We have 2 different schedule at the moment for our PO Placing to our supplier :
1. Planning Calendar D01 --> For Seafreight shipment, PO Placing on bi-weekly basis, every Monday and RDD (Request Delivery Date) is on Thursday (11 days after PO Placing)
2. Planning Calendar D02 --> For Airfreight shipment, PO Placing on weekly basis, every Friday and RDD (Request Delivery Date) is on Wednesday (5 days after PO Placing)
Now we have required to change the SEAFREIGHT process by having the PO Placing on weekly basis, every Monday and RDD (Request Delivery Date) is on Wednesday (9 days after PO Placing).
Please let me know the step by step procedure to create a new Planning Calendar and Lot Size Procedure to accomodate this requirement?
Thanks for your help.
Regards
Brijesh

Dear Brijesh:
1. I think you are planning to change the Planning calendare D01.
2. For this go to MD26- GIVE THE plant / palnning calendar id.
3. Then in the CAlc rule for spec peroid - change the day from wednesday to Monday.
4. SAve this and generate periods.
5. Now in the maeterial master- check if you have the lot size as PK and also planning calendar as d01.
6. In the planned dleiveyr times you enter 9 days.
Kindly check this and revert back.
Reg
Dsk

Lot size exclusion from planning run

Hi Gurus
My scenario is some materials are maintained with lot sizes as EX , VB, HB , when planning run executed , the system should not consider the VB and HB lot sizes ( these are not bom components) and no procurement proposal should exist , we are not following storage location MRP ,
Pl come back in full thanks in advance
Regards
Ram

Hi ramki
VB is MRP type not lot size. VB consumption based planning with manual reorder point. The planning proposal will be created based on your reorder level.
HB is lot size of " Replinishment to maximum lot size "
Normally oils and others are procured where the storage tank capacity is restricted. The max replish level will be your max tank capacity. You can define them as cosumable materials or bulk materials.
Regards
J . Saravan

Lot size Key without splitting Quota

Hi,
Can any one explain me what is the use of Lot size Key without splitting Quota.
We had created a lot size Key - XY with following seting:-
1) Lotsize Proceed = P
2) Lotsize indicator -K
3) Scheduling =2
4) No of periods = 1
5) Splitting Quota = Not checked(blank)
If we had configured this lot size key, what is the benefits of the above setting, What testing need to be done to know whether this lot size key is working perfectly after configuration?.
Thanks in advance

Hi,
If splitting quota indicator not set, then qouta arrangement is not used during planning wrt to selected lot size.
Lot size procedure you selected, it is a periodic lot sizing procedure. Here the system groups several requirements within a time interval together to form a lot.
Lot size indicator Determines how the lot size is calculated for a certain lot-sizing procedure during material requirements planning. For your selection system creates lot size by refereing to planning calender defined in the system
Scheduling -
This indicator defines the time in the period the system is to create the availability date or the start date for the lot for period
lot-sizing procedures.
The availability date is the date on which the material, including the goods receipt processing time, is available again. In the MRP list, the availability date is equal to the MRP date.
In in-house production, the start date is the order start date, in external procurement the start date is the release date.
according to your selection - Availability date at period end
No of periods - 1
Run a complete MRP cycel to check whether it is working properly or not.
Post the results what you get.
Regards,
Pavan

Lot size in MTO

Hi Experts,
I am using strategy 20, my FG batch size is 100 and i have a sale order of 120. I want the system to create 2 planned orders of 100 and 20. I tried with lot size EX and maximum lot size 20, but system made a single planned order of 120. Have i made any mistake, how can i address my requirement ? Please advise.
Best regards
Sm.

Dear ,
In MTO process , sales order qty can't not be spillited beacause , MRP system will not generate planned order detail scheduling to match the Schedule Delivery Date in Sales Order line item .
If you maintain lot size as EX and max lot size is 100 for the quantity of 120,system will create total 2 planned orders.Out of 2 numbers 1 will be with qty 100 and second one will be 20.In OMI4 open the details screen of the lot size which u are using
in the details screen there is a indicator LAST LOT EXACT now if u tick this indicator then the system will create the last lot exact
Basically , your requirement can be done through MTS which will possible .
Hope it is clear
Regards
JH

Fixed Lot Size and Assemby Scrap

Hi Gurus,
I've an issue using a Material with Fixed Lot Size (MRP View) and Assembly Scrap.
The system doesn't increase the base quantiy (creating a Process Order) with the Assembly Scrap defined in the Material Master, if you change manually the quantity in the COR2 quantiy will be recalculated correctly.
Anybody can help me?
Thanks
Marco

>
Marco Spinell wrote:
> Hi Gurus,
> I've an issue using a Material with Fixed Lot Size (MRP View) and Assembly Scrap.
>
> The system doesn't increase the base quantiy (creating a Process Order) with the Assembly Scrap defined in the Material Master, if you change manually the quantity in the COR2 quantiy will be recalculated correctly.
> Anybody can help me?
>
> Thanks
> Marco
dear marco,
One changes in my earlier post
IF fixed lot size is 1000, and assemby scrap as 10 %
if the pir is for 900
after running MRP system will create a plan order for 1000
In MD04 , you can see the receipt reqmt as 900 and scrap as 100
i.e System will allocate the scrap with in the fixed lot size
Once the plan order is converted in to process order you can see
the total qty as 1000 and scrap 100
for other lot size system will add the PIR reqmt +assembly scrap %,
Yes you can change the qty in COr2, system will update as per the scrap qty , i.e system will allocate the qty for scrap
for ex , if you are changing the total qty as 10000, system will propose 1000 as scrap,
when you save the order and see the mD04
you can see the receipt/ reqmt qty as 9000 and scrap as 1000
i.e system will allocate the 1000 qty from total qty
Hope you are clear how the fixed lot size is working for assembly scrap

Pass on lot size" function not supported in costing runs

hi when i am doing cost estimate through ck40n i am getting following error.
Pass on lot size" function not supported in costing runs
Message no. CK463
Diagnosis
You have selected costing variant PPC1 for the costing run. The Pass on lot size indicator is set in this costing variant. Costing variants in which this indicator is set cannot be used by the costing run.
System Response
The costing run is not created.
Procedure
You have the following options:
Reset the Pass on lot size indicator in costing variant PPC1 so that the lot size is not passed on.
Use a different costing variant in which the Pass on lot size indicator is not set.
if any one had found any same king of error please help me in fix it.
thanks
kareem

Probably this might be the cause
Sales order by Costing
Check out the below
Pass On Lot Size
Definition
If this indicator is selected, the system determines the costing lot size using the lot size of the highest material in the BOM and the input quantities of the components.
Use
1) Do not pass on lot size
If this indicator is not selected, the materials further down in the structure are costed in accordance with the lot size in the costing view of the material master record. When the materials in the next-highest costing level are costed, the costing results of the semifinished materials are converted to the lot size of the finished material to calculate the material costs for the finished product.
2) Pass on lot size only with individual requirement
In the MRP view of the material master record, you can specify that a material is planned as an individual requirement. If such a material is added to another material, costing uses the lot size of the highest material.
3) Always pass on lot size
Here, the costs for all the materials in a multi-level BOM are calculated using the costing lot size of the highest material. This function is used principally in sales order costing.
If you are costing sales orders using product costing for a material with a multilevel BOM that is produced in-house, choose 2) or 3) . For those individual requirements materials, from a business management point of view it is recommended that the order lot size be used when costing the material components going into the finished product. On the other hand, materials subject to collective requirements are generally costed using the costing lot size in the material master record.
Thanks

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 .

Function of lot size PB,FS.

Hello SAP Gurus,
   Can you help in understanding the function of lot size PB(period lot size=posting period) and FS (Fixing and Splitting).
     I mean i what to know how these lot sizes works.With this also share that where can i get study material on it.
                        Thanking You.

Hi,
Lot Size FS :-
When entering the lot size "FS" and in field the qty as fixed the system is splitting up the planned order qty.
For ex qty is 100 the fixed lot size is 25 the sys creates 5 planned orders of 25 each. The total qty now comes to 25
Lot Size PB :-
In period lot-sizing procedures, the system groups several requirements within a time interval together to form a lot
In PB periods of flexible length equal to posting periods.
Determines how the lot size is calculated for a certain lot-sizing procedure during material requirements planning.
Please go SAP help for details and system configuration in OMI4.
http://help.sap.com/saphelp_46c/helpdata/en/f4/7d281244af11d182b40000e829fbfe/frameset.htm
Hope it will help you.
Regards,
R.Brahmankar

Lot Sizes Used for Fore cast planning

Similar Messages

Maybe you are looking for