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

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

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

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

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

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

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

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

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

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

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

JOIN ON 2 different sets of table depending on the result of first set

 
I have a query where it returns results. I want to join this query to
2 different sets of table depending upon the first set has a result or not.
if first set didnt had a results or records then check for the second set.
SELECT
peo.email_address,
r.segment1 requistion_num,
to_char(l.line_num) line_num,
v.vendor_name supplier,
p.CONCATENATED_SEGMENTS category,
to_char(round((nvl(l.quantity, 0) * nvl(l.unit_price, 0))),'99,999,999,999.99'),
TO_CHAR(l.need_by_date,'MM/DD/YYYY') need_by_date,
pe.full_name requestor,
l.item_description,
pr.segment1 project_num,
t.task_number,
c.segment1,
c.segment2
FROM po_requisition_headers_all r,
 po_requisition_lines_all l,
(SELECT project_id,task_id,code_combination_id, distribution_id,requisition_line_id,creation_date FROM
(SELECT project_id,task_id,code_combination_id,distribution_id,creation_date,requisition_line_id,ROW_NUMBER ()
OVER (PARTITION BY requisition_line_id ORDER BY requisition_line_id,distribution_id ) rn
FROM po_req_distributions_all pod) WHERE rn = 1) d,
gl_code_combinations c,
POR_CATEGORY_LOV_V p,
per_people_v7 pe,
PA_PROJECTS_ALL pr,
PA_TASKS_ALL_V t,
ap_vendors_v v,
WHERE d.creation_date >= nvl(to_date(:DATE_LAST_CHECKED,
'DD-MON-YYYY HH24:MI:SS'),SYSDATE-1)
AND
l.requisition_header_id = r.requisition_header_id
AND l.requisition_line_id = d.requisition_line_id
AND d.code_combination_id = c.code_combination_id
AND r.APPS_SOURCE_CODE = 'POR'
AND l.category_id = p.category_id
AND r.authorization_status IN ('IN PROCESS','PRE-APPROVED','APPROVED')
AND l.to_person_id = pe.person_id
AND pr.project_id(+) = d.project_id
AND t.project_id(+) = d.project_id
AND t.task_id(+) = d.task_id
AND v.vendor_id(+) = l.vendor_id
and r.requisition_header_id in(
SELECT requisition_header_id FROM po_requisition_lines_all pl
GROUP BY requisition_header_id HAVING SUM(nvl(pl.quantity,0) * nvl(pl.unit_price, 0)) >=100000)
group by
peo.email_address,
r.REQUISITION_HEADER_ID,
r.segment1 ,
to_char(l.line_num) ,
v.vendor_name,
p.CONCATENATED_SEGMENTS ,
to_char(round((nvl(l.quantity, 0) * nvl(l.unit_price, 0))),'99,999,999,999.99'),
TO_CHAR(l.need_by_date,'MM/DD/YYYY') ,
pe.full_name ,
l.item_description,
c.segment1,
c.segment2,
pr.segment1 ,
t.task_number
I want to join this query with this first set 
SELECT b.NAME, c.segment1 CO, c.segment2 CC,
 a.org_information2 Commodity_mgr,
 b.organization_id, p.email_address
 FROM hr_organization_information a, hr_all_organization_units b, pay_cost_allocation_keyflex c, per_people_v7 p
 WHERE a.org_information_context = 'Financial Approver Information'
 AND a.organization_id = b.organization_id
 AND b.COST_ALLOCATION_KEYFLEX_ID = c.COST_ALLOCATION_KEYFLEX_ID
 and a.ORG_INFORMATION2 = p.person_id
 AND NVL (b.date_to, SYSDATE + 1) >= SYSDATE
 AND b.date_from <= SYSDATE;
if this doesnt return any result then i need to join the query with the 2nd set
select lookup_code, meaning, v.attribute1 company, v.attribute2 cc,
 decode(v.attribute3,null,null,p1.employee_number || '-' || p1.full_name) sbu_controller,
 decode(v.attribute4,null,null,p2.employee_number || '-' || p2.full_name) commodity_mgr
 from fnd_lookup_values_vl v,
 per_people_v7 p1, per_people_v7 p2
 where lookup_type = 'BIO_FIN_APPROVER_INFO'
 and v.attribute3 = p1.person_id(+)
 and v.attribute4 = p2.person_id(+)
 order by lookup_code
How do i do it?
[pre]

 
I have hard coded the 2 jon sets into one using UNION ALL but if one record exists in both sets how would i diferentiate between the 2 sets.
COUNT(*) will only give the total records.
if there r total 14
suppose first set gives 12 records
second set gives 4 records.
But i want only 14 records which could 12 from set 1 and 2 from set 2 since set1 and set2 can have common records.
SELECT
peo.email_address,
r.segment1 requistion_num,
to_char(l.line_num) line_num,
v.vendor_name supplier,
p.CONCATENATED_SEGMENTS category,
to_char(round((nvl(l.quantity, 0) * nvl(l.unit_price, 0))),'99,999,999,999.99'),
TO_CHAR(l.need_by_date,'MM/DD/YYYY') need_by_date,
pe.full_name requestor,
l.item_description,
pr.segment1 project_num,
t.task_number,
c.segment1,
c.segment2
FROM po_requisition_headers_all r,
 po_requisition_lines_all l,
(SELECT project_id,task_id,code_combination_id, distribution_id,requisition_line_id,creation_date FROM
(SELECT project_id,task_id,code_combination_id,distribution_id,creation_date,requisition_line_id,ROW_NUMBER ()
OVER (PARTITION BY requisition_line_id ORDER BY requisition_line_id,distribution_id ) rn
FROM po_req_distributions_all pod) WHERE rn = 1) d,
gl_code_combinations c,
POR_CATEGORY_LOV_V p,
per_people_v7 pe,
PA_PROJECTS_ALL pr,
PA_TASKS_ALL_V t,
ap_vendors_v v,
WHERE d.creation_date >= nvl(to_date(:DATE_LAST_CHECKED,
'DD-MON-YYYY HH24:MI:SS'),SYSDATE-1)
AND
l.requisition_header_id = r.requisition_header_id
AND l.requisition_line_id = d.requisition_line_id
AND d.code_combination_id = c.code_combination_id
AND r.APPS_SOURCE_CODE = 'POR'
AND l.category_id = p.category_id
AND r.authorization_status IN ('IN PROCESS','PRE-APPROVED','APPROVED')
AND l.to_person_id = pe.person_id
AND pr.project_id(+) = d.project_id
AND t.project_id(+) = d.project_id
AND t.task_id(+) = d.task_id
AND v.vendor_id(+) = l.vendor_id
and r.requisition_header_id in(
SELECT requisition_header_id FROM po_requisition_lines_all pl
GROUP BY requisition_header_id HAVING SUM(nvl(pl.quantity,0) * nvl(pl.unit_price, 0)) >=100000)
group by
peo.email_address,
r.REQUISITION_HEADER_ID,
r.segment1 ,
to_char(l.line_num) ,
v.vendor_name,
p.CONCATENATED_SEGMENTS ,
to_char(round((nvl(l.quantity, 0) * nvl(l.unit_price, 0))),'99,999,999,999.99'),
TO_CHAR(l.need_by_date,'MM/DD/YYYY') ,
pe.full_name ,
l.item_description,
c.segment1,
c.segment2,
pr.segment1 ,
t.task_number
UNION ALL
SELECT
r.segment1 requistion_num,
to_char(l.line_num) line_num,
v.vendor_name supplier,
p.CONCATENATED_SEGMENTS category,
to_char(round((nvl(l.quantity, 0) * nvl(l.unit_price, 0))),'99,999,999,999.99'),
TO_CHAR(l.need_by_date,'MM/DD/YYYY') need_by_date,
pe.full_name requestor,
l.item_description,
pr.segment1 project_num,
t.task_number,
c.segment1,
c.segment2
FROM po_requisition_headers_all r,
 po_requisition_lines_all l,
(SELECT project_id,task_id,code_combination_id, distribution_id,requisition_line_id,creation_date FROM
(SELECT project_id,task_id,code_combination_id,distribution_id,creation_date,requisition_line_id,ROW_NUMBER ()
OVER (PARTITION BY requisition_line_id ORDER BY requisition_line_id,distribution_id ) rn
FROM po_req_distributions_all pod) WHERE rn = 1) d,
gl_code_combinations c,
POR_CATEGORY_LOV_V p,
per_people_v7 pe,
PA_PROJECTS_ALL pr,
PA_TASKS_ALL_V t,
ap_vendors_v v,
fnd_lookup_values_vl flv,
per_people_v7 p1,
per_people_v7 p2
WHERE d.creation_date >= nvl(to_date('11-APR-2008',
'DD-MON-YYYY HH24:MI:SS'),SYSDATE-1)
AND
l.requisition_header_id = r.requisition_header_id
AND l.requisition_line_id = d.requisition_line_id
AND d.code_combination_id = c.code_combination_id
AND r.APPS_SOURCE_CODE = 'POR'
AND l.org_id = 141
AND l.category_id = p.category_id
AND r.authorization_status IN ('IN PROCESS','PRE-APPROVED','APPROVED')
AND l.to_person_id = pe.person_id
AND pr.project_id(+) = d.project_id
AND t.project_id(+) = d.project_id
AND t.task_id(+) = d.task_id
AND v.vendor_id(+) = l.vendor_id
AND flv.attribute1=c.segment1
AND flv.attribute2=c.segment2
AND flv.lookup_type = 'BIO_FIN_APPROVER_INFO'
and flv.attribute3 = p1.person_id(+)
and flv.attribute4 = p2.person_id(+)
and r.requisition_header_id in(
SELECT requisition_header_id FROM po_requisition_lines_all pl
GROUP BY requisition_header_id HAVING SUM(nvl(pl.quantity,0) * nvl(pl.unit_price, 0)) >=100000)
group by
r.REQUISITION_HEADER_ID,
r.segment1 ,
to_char(l.line_num) ,
v.vendor_name,
p.CONCATENATED_SEGMENTS ,
to_char(round((nvl(l.quantity, 0) * nvl(l.unit_price, 0))),'99,999,999,999.99'),
TO_CHAR(l.need_by_date,'MM/DD/YYYY') ,
pe.full_name ,
l.item_description,
c.segment1,
c.segment2,
pr.segment1 ,
t.task_number

How to select the production versions for MTO?

Hi PP Experts,
In our scenario we have two production versions and also we are in MTO strategy. While creating the sales order is there any option to select the production version (i.e.) before planning for that corresponding sales order I have to choose the production versions.
Example:
Material u2013 A -
sale order u2013 666001 u2013Prod version - 0001
Material u2013 A --- sale order u2013 666002 u2013 prod version - 0002
How to map the above scenario?
Thanks in advance.
Regards,
Vimal

In our scenario we have two production versions and also we are in MTO strategy. While creating the sales order is there any option to select the production version (i.e.) before planning for that corresponding sales order I have to choose the production versions.
If the Production version selection is based on Lot size means No problem.
If both the Production version is same lot size, system will select the first PV only in MRP
In STD SAP, we can't Give Production Version in sale order level,
If you want after MRP run , U can assign Production version in plan order or in production order Manually

ME51N subcontracting don't include the production version of info record

Dear guru ,
After assigning source of supply in a subcontracting purchase requisition the system donu2019t read the production version of info record from the combination of vendor and material.
Itu2019s right this behavior ?
Thanks

For a Purchase requisition it is not possible to determine the correct Product Version, even the Vendor is specified. It will just pick the first valid version it can find.
When creating the Purchase Order from this Requisition, you will get a pop-up which allows you to let the "correct" production version overwrite the one coming from the Requisition. This is the case, when you create a PO with a vendor that has a different production version assigned in its info record as it is included in the Requisition.

The product version and database version are not compatible

The following simple program gets an exception {The product version and database version are not compatible} its very hard to proceed from here. Does anybody know what cause this?
Best Regards
Jan Isacsson
using System.Collections.ObjectModel;
using Microsoft.MasterDataServices.Deployment;
using Microsoft.MasterDataServices.Services.DataContracts;
namespace MdsDeploy
 class Program
 static void Main(string[] args)
 try
 ModelReader reader = new ModelReader();
 Collection<Identifier> models = reader.GetModels();
 foreach (Identifier modelId in models)
 Console.WriteLine(modelId.Name);
 catch (System.Exception ex)
 Console.WriteLine("Error: " + ex.Message);
 Console.ReadKey();

Hi Jan,
For the error "The product version and database version are not compatible", as Emma said, the version number of the Service does not match the database schema version.
In your scenario, which version of database are you using? Please note that MDS update required after SQL 2012 SP1 installation, please refer to the links below to see the details.
http://byobi.com/blog/2012/11/mds-update-required-after-sql-2012-sp1-installation/
http://msdn.microsoft.com/en-IN/library/gg488708.aspx
Regards,
Charlie Liao
TechNet Community Support

Different fix lot size depending on the production version

Similar Messages

Maybe you are looking for