Lot sizing calculation problem
Here's how i set-up my master data:
minimum lot size:500
lot size procedure : ex
rounding profile:
threshold value :1
rounding value: 100
desired output ( SO qty is 400 )=
planned order qty should be 500
yet, the system is always proposing the 400 qty in the planned order. what am i doing wrong?
Hi Raf,
test1
SO: 1 pcs
minimum lot size: 10 pcs
strategy group: 40
PldOrd: 10 pcs
test2
SO: 1 pcs (new SO, after having changed mmr)
minimum lot size: 10 pcs
strategy group: 20
PldOrd: 1 pcs
BR
Csaba
Similar Messages
-
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 -
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). -
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 -
New lot-sizing procedure (similar FX fixed order quantity)
Dear All,
I have to create a new lot sizing procedure for MRP run. This new procedure should be similar to FX - the material should be included in MRP run when the stock falls below reorder point - but the quantity ordered (proposed to be ordered in PReq) should be the fixed lot size no matter which is the difference between the reorder point and the stock.
To clarify the request: the reorder point is 70, the stock level is 15 and the fixed lot size is 25. The MRP run should create 1 PReq for 25. (The standard functionality of FX lot sizing creates 3 PReq for 25 pieces each one - because the needed quantity is 55.)
If there is no standard customization to be done, I think I should do some changes in the needed quantity (set the quantity 25 instead of 55) - but I need yours advice also about the best way to do this. Maybe you may indicate an exit/BADI or a place where I can do an enhancement to achieve this.
I now it is not the best request - but I have to do it, unfortunately .
Regards,
Florina R.Hi Tomasz,
1) The reorder point is 70 (greater than the needed quantity for a week) because the vendor has some delivery problems and also because this quantity covers the delivery lead time.
2) The lot size is fixed because they do not want to order more than the needed quantity for a week even if the difference between the reorder point and the stock level is greater than 25.
I'm able to fix the lot size but not to limit the quantity at this value (25).
I have to do this because they will provide the needed quantity (if the stock falls to 0) from another vendor (but the tricky thing and wrong also is the fact that for the second vendor I have a second material....).
It is hard for me to convince you that the request is correct because I know in this way SAP will work incorrectly - but the client knows the consequences and even so wants this kind of lot sizing procedure...
Regards,
Florina R. -
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
cheersThanks 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 -
Can somebody explain me for which business process the DY and WI lot size is recommended in MRP>
Also what is significance of eact one if it is used.
Thanks
VaibhavHi Sumeet,
Using 2 lot sizing procedures in a single material master will not be possible.
Also, creating 2 Valuation classes with different lot sizing for each valuated material data wont be acceptable by business.
Here, you can create a customized lot size by copying a standard, and in to the config of the lot size, please define Short Term and Long Term Planning details.
IMG-> MM->Consumption Based Planning->Planning->Lot Size Calculation-> Define Lot Size Procedure->MRP Lot Size.
Maintain Static for Short term and Dynamic lot size option for longer term and define the short term, long term intervals.
Hope this would work.
Thanks
Raghavan -
Helllo,
We would like to use the Wilsons formula for calculating the optimal lot sizes. This is not possible with the lot sizing procedures SAP provides.
Is there a way that I can create my own formula for calculating the optimum lot sizes?
Kind regards,
RudyHi,
You can develop a period lot sizing procedure which has a larger period length than the planning horizon. For example, if the planning horizon is 999 days, develop a procedure for 36 months. You can copy the standart lot sizing procedure TB and change the period type and number of the periods. This way all planned orders that would be generated in that period will be combined into one.
Regards. -
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,
MaheshHello 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 -
No. of POs per year
Purchase Cost
Storage Cost (20 %)
Total Cost
Purchase Value
Purchase Quantity
1
800,000
2,400,000,000
2,400,800,000
120,000,000
1200
2
160,000
13,200,000
14,800,000
60,000,000
600
3
240,000
8,800,000
11,200,000
40,000,000
400
4
3,200,000
6,600,000
9,800,000
30,000,000
300
5
4,000,000
5,280,000
9,280,000
24,000,000
240
6
4,800,000
4,400,000
9,200,000
20,000,000
200
7
5,600,000
3,771,429
9,371,429
17,142,857
171
8
6,400,000
3,300,000
9,700,000
15,000,000
150
Hi All,
I need total requirements of 1200 EA around the year from a specific material, if i issue one PO per year for total quantity of 1200 the total cost will be as shown above, if i issue two POs (one PO every 6 months with total quantity of 600) the total cost will be as shown above, the optimum quantity is 200 and 6 POs (one PO every 2 months with total quantity of 200) as the cost will be at its minimum.
Line no. 6: the optimum quantity that should be suggested by MRP run is 200 EA as the total cost is 9,200,000 (the lowest cost).
I want to use dynamic reorder point (MRP type V2) and dynamic lot size(DY) in MRP1 view i choose MRP type V2, Lot size DY,Reorder Point 300, Safety Stock 100, Ordering Cost 800,000 and Storage Cost ind. 1 ( represent 20%) but when i save the material the system issue the below message:
MRP type V2 requires forecasting data to be maintained so please help me to understand which data i have to maintain to use optimum lot sizing procedure to meet the above requirements.
If you could help me with an example and screenshot i'd be grateful. Thanks in advance.Hi,
Do refer the below wiki Link it will help you understand more about Lot sizing procedure..
Lot sizing procedure calculation - Adobe Interactive Forms (Japanese) - SCN Wiki -
Hi all,
Can some one through light on Dynamic lot size (DY) with quota split? How to maintain this quota split in dynamic lot sizing?
Thanks and Regards,
RaghuDear,
The Quota Split indicator is checked in the lot sizing\procedure SPRO --> Production --> Material Requirement Planning --> Planning --> Lot size Calculation --> Check Lot sizing procedure --> MRP Lot Size
Select your required lot size & select icon 'Details'. Then mark tick at 'Splitting Quota'. Save the changes. Then run the MRP. System will now split the quantity based on your quota arrangement.
In MEQ1 we define the quota.
Regards,
R.Brahmankar -
Dear pradeep kumar hi,
I'm refering to the thread posted by anand srinivasan for "Production Order in lot", in this you have mentioned to "Set the MTO lot size = 1 (lot-for-lot with rounding) for EX lotsize at OMI4", iam NOT finiding any setting parameter like this in OMI4 as you have mentioned, please reply
Thanks in advanceHi shaiz,
The field is "MTO lot size - Lot-size calculation in make-to-order production" avilable in bottom area of Detail screen at OMI4. Please check with page down Key.
Please check and coemback
regarsd
Pradeep -
Is Mavericks good to go, or are there lots of teething problems to be sorted yet?
Is Mavericks good to go, or are there lots of teething problems to be sorted yet?
Donald Morgan wrote:
There are normally very small bugs but at this point will not affect the operation of Mavericks. I might add is the most stable and smoothest Operating System since OS9-2
Good to know! OS 9.1 is my favorite OS to date. Tiger & SL running in close 2nd.
Me personally, I will not upgrade until OS 10.9.02 is released. -
Multiple PR's being created even though the Lot Sizing procedure is WB.
The issue is system is creating more than one PR every week even though the lot sizing procedure is WB. The MRP type of the material is P3 and planning time fence is 21 days. The PR's created have the date of every week's Monday. There's also a quota arrangement for the material having two vendors, so two PR's both having different vendors are ok but system is creating multiple PR's for same vendor on same date.
Do let me know if anything else you want to know to understand this issue.
We want system to create only one PR per week for a vendor.
Thanks,
Rakesh.Hi,
First thing theres a lot size WB
What is the qty of the PR have u maintianined any min lot sice or max lot size.
Coming to quota arrangement how did u maintained it
For eg
You might have maintained for a vendor 1 maximum qty as 100 and u have raised a request for 200 so it is raising two prs
Check u r quota arrangement once
Reagrds
sravanthi -
Alternate Lot Sizing for KMAT (configurable) materials
Hi friends,
We are using KMAT(configurable) materials.
During MPS/MRP run, SAP plans KMAT production with Lot-to-Lot production(EX) by default!
We have some capacity planning situations, due to which, we need the lot sizing options like u2018Fixed lot (FX) sizeu2019 or u2018Fixed lot size with splitting(FS)u2019 or even use of u2018Min-Max lot sizeu2019... so that the large requirements are transferred in smaller lots to the plant.
But, when we use any of these lot- sizing procedures in MRP1 screen of the material master, we do not find any difference in MRP resultsu2026 system just triggers the planned order exactly matching the Sales order quantity (as if we still use EX)!
SAP notes 437098 and 724235 hint that the alternate lot sizing procedures are possible to set up for configurable materials... but we are struggling to crack this.
If any of you have had an opportunity to work on alternate or custom lot sizing procedures with KMAT (configurable) materials, it would be wonderful to hear the suggestions and results.
Thanks in advance.
Best Regards,
SenthilHi Dario,
Thanks for the response.
We use ECC6.0; I could not find the inidicator you've referred (customer requirement)... in transaction OMI4 : Check Lot Sizing Procedure --> MRP Lot Size...
Kindly advise if you were referring to any other version or any other transaction...
Best Regards,
Senthil
Maybe you are looking for
-
I am running a HP-DV6 6090ee laptop with windows 7 Home Premium 64bit OS. This problem started from last evening. I am getting a "Smart Hard disc error" error message before boot and ater booting windows saying that my HDD is having problems and i ne
-
I need help withButtonHandler, getActionCommand
I trying to write a GUI app. I have to convert Celsius to Fahrenheit and vice versa. This is what I got so far, but when I press any of the two buttons I got an error message import java.awt.FlowLayout; import java.awt.event.ActionListener; import ja
-
Picture quality relative to bitrate vs resolution
Hello. I want to better understand the tradeoffs between bitrate and resolution. We know that a 1280x720 frame is 921,600 pixels & a 1920x1080 frame is 2,073,600 pixels - a difference of 2.25x So when considering what bitrate to encode at, is it true
-
ALV filter- In activate case Sensitive nature
Dear experts, I have z report with standard ALV filter and when I try to filter text column and itu2019s did not work. I know this happens because of case sensitive nature of filter. Could u pls help me how to inactivate case sensitive nature of the
-
HELP!!! I can't uninstall windows 7!
How can I log into Mac software when logging in directly to Windows 7? Indeed, I would like to uninstall Windows 7!