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."

Similar Messages

Fixed lot size and Minimum lot size

Dear senior,
My client has the following scenario. His supplier provides the item in a fixed lot size of 100. The minimum lot size to be ordered is 300.
The supplier is a fixed vendor.
I tried to maintain this information in the Material Master MRP views. Lot size - FX, Fixed lot size - 100, Minimum lot size - 300.
However, everytime, the minimum lot size will get reset.
Is there any way , I can maintain this scenario via configuration or any other method?
Thank you.

Hi,
Fixed lot size - 100 means for every 100 quantity system will create one purchase document.
If you selected Lot size - FX - Fixed order quantity , then no need to maintain Minimum lot size & Maximum lot size fields.
Then you have to maintain Fixed lot size filed only.
Ex:
Lot size = FX
Fixed lot size = 100
There is a requirement of 300. Then system will create 3 PO's with quantity of 100 each.
If Lot size is Ex - Lot-for-lot order quantity, then only need to maintain Minimum lot size & Maximum lot size fields in the MRP 1 view.
Ex: Lot size = EX
Minimum lot size = 60
Maximum lot size = 100
There is a requirement of 250. Then system will create 3 purchase documents, two documents with the quantity of 100 and third one with the quantity of 60.
That's why, in your case system is reseting Minimum lot size every time.
If you want to maintain Minimum lot size, then maintain
Lot size as EX
Minimum lot size = 100
Max lot size = 300
It will solve your problem.
Regards
KRK

Report for Reorder point, safety stock, current stock and fixed lot size

Hi,
Purchasing Dept. is looking for a report which can give list of materials falling below the reorder point, so that they can go ahead and create procurement proposals for those materials.
They also want to see the Reorder Point, Safety Stock, current stock and fixed lot size in the same report.
Let me know if there ia any standard report availbale which displays the same or any approach to get the same.
Thanks in Advance.
Regards,
Shankar Goud.

Hi,
There is no standard report because this is meant to be managed by the MRP run.
The MRP lists show all materials that have a problem (such as stock below reorderpoint) but MRP generates requirements for these anyway and so all you need to do is to look for the MRP generated requirements (requisitions?) and you have your list?
Are you using MRP?
If so then please use the standard functions in MRP to get this.
If not, then WHY NOT?
Steve B

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

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

Fixed Lot Size

Dear Gurus,
I am simulating the functionality of Fixed Lot Size so I enter Lot Size = FX and indicated Fixed order Quantity = 40,000 in Material Master. We are using Ind./Coll = 1 and I want to generate fixed quantity of planned order equal to 40,000. But when I run MD42, the system still generated planned order equal to the shortage/required quantity. Our requirement is to generate fixed quantity of 40,000 per planned order regardless of demand requirement.
Please help. Thanks in advance.
Regards,
SD

Hi,
Please find my reply below,
Use MRP Type VB:Manual reorder point planning:Here you need to define reorder point in material master in MRP view.When the stock level reaches the re order point then system will create a procurement proposals.
Regards,
Kumar.S

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

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

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

MRP planning Purchase REQ per fixed lot size

Folks,
I have materials which have MRP type PD with fixed lot size of 20 pieces. Safety stock = 200 pieces. MRP run results in 10 preqs of 20 pieces each. I would like to have 1 Preq of 200 pieces. How can this be achieved?
Regards,
MdZ

Hi,
This is because of Lot size "FX" you maintained as 20.
For FX lot size system will divide the total qty as per the fixed lot qty & throw that much of PR for that stock.
So Safety stock = 200, FX =20 so PR will be 200/20 = 10 PRs
If you want 1 PR for your safety stock, then change the Lot size to "EX" then system will throw 1 PR for 200 qty as per your Safety stock
rgds
gsc

Lot size key

Hi ,
In one scenario , it is required that planned prders will be created where the req for 5- 8 days is clubed together and order date is not created on some specific day .
Will lot ize key help in this regard .
Regards
ShankarR

Hi,
Connect the planning calendar to your lot size key
First, you will need to set up the planning calendar.
Menu path: Production -> MRP -> Master Data -> Planning Calendar (MD25)
You will then need to use this planning calendar (the one you created) in the material master when planning your raw materials (MRP2 View in 4.6C - Field name : Planning Calendar).
1. When you maintain the planning calendar you will need to enter a valid from date and valid to date.
2. Your periods will also need to be set up and they will be weekly, for example:
    From Date : 11/23/2001    To Date : 11/29/2001   (11/23 is a Friday, this is your from date).
    Do this for as may weeks as you wish (say weekly for 2 years).
3. When you have set up the planning calendar, you will then need to make some changes to the weekly lot size configuration
    (WB), or you may need to create a new lot size key if you do not want to change 'WB'. Essentially, you will need to use the
    following in the lot size configuration (OMI4) :
    No. of Periods : 1
    LotSizeProced.: P
    LotSize ind : K
    Scheduling : 1

Combination of Fixed Lot size and Period lot size

Dear all
I have scenario as follows:
1. My supplier's standard packing size of a raw material is 1000 EA.
2. I want to follow period based lot size to optimise my order and inventory cost. But I don't want to use dynamic lot size which will propose dynamic quantity.
So my requirement is like I want to fix lot size as 1000 at material master and Period is Week. My proposal quantity must be 5000 EA for the following demand pattern:
Week 1:1200
Week 2: 1000
Week 3: 1100
Week 4: 1000
System must consider period as well as fixed quantity.
Kindly throw some light on this.
Advance thanks.

Hi
1.As you are looking for Weekly demand demand quanityt , you have to assign Weekly Lot Size : WB.
2. Goto OWD1 and Create a Rounding Profile which will rounds into Weekly Demand quantity for that plant and simulate .
3.Assign this rounding profile in MMR in MRP1
3.DO NOT assing rounding valu as 1000 .Rather keep it blank
Hope this will solve the problem
Regards
JH

Intel GMA - turning off rotation access keys has no effect

I want to use ctrl+alt+down and ctrl+alt+up in some application, so I want to turn these access keys off. I did it in Intel Graphics Media Accelerator Driver for Mobile settings but it has no effect - these key combinations still rotate my screen. The settings are correctly remembered.
I tried it on administrator and on normal user account. Anyone knows how to solve this problem?

Yes. I have already done it, but it's a workaround, not a solution to this problem. I got used to this key combinations in Eclipse (programming environment). There are a lot of key shortcuts, which I use, so it's hard to choose another one, which is good and free.
When I comes to rotating a screen - I don't need it. I can not even imagine use case when 180 degree screen rotation in laptop would be useful :)

FiX lot size & minimum sale order qty .

hi all
We maintained minimum order quantity for material ; can we put massage sale oraganization wise
ie for SO IN01 Massage type is 'E"
& for IN02 massage type is 'W"
If my minimum order qty. is 10 then SAP will accept the sale order qty. with multiple of 10 .
Eg. If customer placed order qty. 15 Nos. Dose SAP convert it into 20 automatically ?
PL. suggest me how to configure this scnerio

Hello,
Min sales order qty is controlled through MMR Sales Org 1 - if you want it to round up or down to the correct order quantity then you will need to create a rounding profile (see below).
Otherwise to change your message from a info or warning to an error goto transaction OVAH message V4 082 and change to E = error.
Rounding Profile
Key that the system uses to adjust the order proposal quantity to deliverable units.
Procedure
In Customizing, enter a threshold value from which the system should round up to the next value per deliverable unit:
If the requirements value exceeds the first threshold value, the system always rounds up to the next multiple of the level found
If the requirements value falls below the first threshold value, the system copies the original requirements value.
Two other types of rounding exist:
Dynamic rounding profile:
These profiles are used to round up quantities to logistical units of measure (for example, layers). The contents of a logistical unit of measure does not have to be know when creating the rounding profile. It is determined by the master data from the material master.
Rounding profile with quantity to be added/subtracted
With these profiles, the given quantity is changed either by adding a percentage or subtracting a percentage.
Only static rounding profiles are taken into account in requirements planning. Neither dynamic rounding profiles not quantity addition/ subtraction are taken into account.
Examples
A material's base unit of measure is 1 unit; the purchase order is to be delivered in layers (1 layer corresponds to 5 units) or in pallets (1 pallet corresponds to 8 layers which contains 40 units).
You maintain the profile as follows:
From a requirements of 2 units, the system is to round up to 5; from a requirement of 32 units, the system is to round up to 40.
This results in the following order proposal quantities:
Requirement from 1 -> 1 requirement from 31 -> 30
Requirement from 2 -> 5 requirement from 32 -> 40
Requirement from 6 -> 10 requirement from 74 -> 80
Requirement from 7 -> 10
Dependencies
If no rounding profile has been entered, the system uses the rounding value entered in the material master record for the planning run
Kind regards
Sue

Priority of message has not effect on delivery order

Hi,
I'm sending messages into a JMS queue with two different priorities and a property for use with a JMS selector.
Then via a JMS message recievers that have a selector I recieve the messages.
But the order is always the same First in, First Out.
Example Code
Random Object Choice:
String[] myObject = new String[]{"Low Priority","RECIEVER_ONE"};
String[] myObject = new String[]{"High Priority","RECIEVER_ONE"};
String[] myObject = new String[]{"Low Priority","RECIEVER_TWO"};
String[] myObject = new String[]{"High Priority","RECIEVER_TWO"};Sender snippet of code:
ObjectMessage objectMessage = queueSession.createObjectMessage(myObject);
objectMessage.setStringProperty("SELECTOR", myObject[1]);
if (myObject[0].equals("Low Priority")) {
priority = 0;
} else {
priority = 5;
queueSender.send(objectMessage,DeliveryMode.PERSISTENT,priority,0);RECIEVER_ONE snippet of code:
queueSession.createReceiver(queue,"SELECTOR == 'RECIEVER_ONE'");
Message message = queueReceiver.receive(100);RECIEVER_TWO snippet of code:
queueSession.createReceiver(queue,"SELECTOR == 'RECIEVER_TWO'");
Message message = queueReceiver.receive(100);problem is that the order in which the random messages are add to the queue is the order the the recievers recieve the messages.
I get the correct results from other JMS vendors.
Is this a bug in Sun Message Queue or is it a configuration option?

MQ does look at priority when delivering messages
However, Prior to our 3.5 release, priority was only
taken into account on the 3.5 broker (the client just
delivered messages in the order they were received).
This meant that as long as your consumers were keeping
up with producrs, you dont see the affect of priority
(for example, the priority 0 message was already on the
wire to the MQ client BEFORE the priority 5 message was
received and processed)
To verify that a 3.0* version of MQ is processing priority,
you can try stopping your consumer connection until
after the messages are produced .... you will see messages arriving in priority order.
If you upgrade to 3.5, you should see the behavior that you
have seen on other platforms (since both the client and
the broker are handling priority)

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

Similar Messages

Maybe you are looking for