Production version selection according to explosion date
Hello
In customizing for MRP (OPPQ), parameters for BOM explosion / routing selection is 3 (BOM explosion number/order start date).
In MRP4 view of material master, selection method for BOM explosion is 2 (Selection by production version).
No MRP group is assigned.
I have 3 production versions : one for 2014, one for 2015, one for 2016 :
I use a BOM explosion number with fixed key date 1st December 2015 :
When manually creating a planned order with dates in 2014 and explosion number EXP_1215 (fixed key date 1st December 2015), Production Version PV1 is selected (valid for 2014), but no routing is selected because explosion date is BOM explosion number, and in PV1 there is no valid routing in 2015 :
Is it possible to select production version according to explosion date, and not order dates ?
Hi Tristan
The following modification note can be used to influence the selection of production version on planned orders:
351773 - Selection of production versions for planned order
Alternatively, you can create your own logic using BAdI MD_MODIFY_PRODVERS.
BR
Caetano
Similar Messages
-
Production version selection based on Process order type
Hi,
I have the following requirement.
A material is having two production version one is for R&D and one is for regular production. Now two process order types one for R&D and one for regular production. Now during creation of process order if we use order type of R&D then it has to select production version of R&D and if we use order type of regular productionthen it has to select production version of regular production. This selection has to be happened automatically. How this can be configured.
Thanks
Vinamrath.Dear Kumar,
Assuming the production version selection is automatic in the order type dependent parameters,then during order creation this
can be automated only through validity date of the production version or else by locking the production version manually which
should not get picked or else only through different Lot Size.
Check and revert.
Regards
Mangalraj.S -
ISSUE:regarding production version tab of MRP4 of data transfer using BD10
Hi all,
This is regarding production version tab of MRP4 of data transfer using ALE idoc (BD10).
When i transfer the data using BD10 the production version is received at receiving end through segment
but not created in MRP4 view tab.An error is coming as-
"You wanted to maintain the master record of the material AB_06.04.09(2). However, it is already being processed by the user EBGABAP and is therefore locked."
I logged in as-EBGABAP
Please help me resolve the issue.
Thanks
Edited by: sanu debu on May 6, 2009 11:08 AM
Edited by: sanu debu on May 6, 2009 11:09 AM
Edited by: sanu debu on May 6, 2009 11:11 AM>
sanu debu wrote:
> Hi,
> I have to upload production version tab data of MRP4 view(MM01).Please suggest a function moduleor bapi for the same.
>
> Thanks.
>
> Edited by: sanu debu on May 6, 2009 3:24 PM
BAPI_MATERIAL_SAVEDATA can be used, populate the respective fields in input parameter PLANTDATA -
Hi
If we have two production version with same lot size quantity and same validity date
On what basis system determines IN THE PRODUCTION OR PROCESS ORDERS.
The selection key in Material master is Production version only
Please explain the logic
Regards
SasikanthWhat is the basis for the Selecting the production version .
How the system identify this is the first production version ?
system will check the validity date, from lot size and to lot size with requirement qty, if both the PV has valid on date having same lot size, System will take first created PV, if the first created PV is locked, then system will take second PV
If i created Version with Number 1000, 1001
and if we kept 1001 as the first , Which version system will create ?
System will take first created PV, if 1001 is created as first then system will take 1001 -
Automatic Production Version Selection
Dear All,
There are two production versions 0001 and 0002 for a finished material. When I create production order from planned order it automatically selects version 0001. If I want it to select version 0002 automatically what should I do?
Regards
HammadHi Hammad,
As per your querry, you want production version 0002 should be selected automatically when you create production order instead od PV 0001. If you want PV 0002 should be selected automatically then,
1. Maintain lot size of of PV 0002 to quantity which you usually use for the production. So when you create production order system will use PV0002 based on lot size.
2. Or change validity period of PV0001 to a date which is outside the planning period. So it will be no longer valid in the period in which you are creating production order.
3. As specified by experts, you can change PV selection to manual by going to transaction COR4. And change selection of PV to manual selection for your order type or you can change it by going to transaction MM02. Then lock production version by selecting locked for any usuage.
Hope this resolve your issue, please reward if it is usefull.
Regards,
Avinash. -
Production version selection in MRP run
Hi all
here my requirment is to select the Alternative BOM in MRP run.
i have three alternative BOMs. and two routings. to make different combinations i was created Production version. so now my requirment was while run MRP how to choose production version manually. i was mantained MRP 4 screen for selection method as 3.
my All BOM validity dates r same and same lot size.
can any one suggest me how to choose production version manually in MRP run. otherwise system by default it choosing 1st alternative.
Regards
DeviprasadHi All,
Thanks for all your suggestions. here my requirment was not matching with these.
my req was
1. want to select prod version while run MRP.
2. my demand was MTS.
3. i already marked in MRP 4 Screen as selection method as 3.
Constrains
my BOM validity dates r same.
lot sizes r same.
i am giving hints for this.
In Customization - BOM selection ID, Selection priority and BOM usage, Alternative selection of BOM in MRP.
i was tried to mantain this. still system picks the default as first production version.
can u try for this. how we can configure in SAP.
example.
i have one material as M-20. it has differnt grads of mixing as R1,R2,R3 alternative BOMs. all alternatives have same materials with differnt Compositions. i want to choose one alternative while run MRP. But system by default picking first alternative BOM.
regards
Deviprasad -
Production Version Selection - Manually
Hello Sir,
I created two Production Versions for my FERT.In the Order Type i am
defining that Versions to be selected manually.But when i am converting
my planned order , the version is selected automatically.
When i am creating production order manually the system is asking which
version is to be selected. I am unable to trace where i am doing mistake.
Kindly help me in solving this problem.
Thanks in advance.
S.Nandhakumar.Hi abhi
Could you please send the screen shots of the order type dependent parameters and the MRP4 view to my personal id [email protected] so that i ca check at my end.
Chandra
Message was edited by:
chandra nalam -
Not valid Explosion Date for Production Version
Hi Experts,
I am creating a production order for a new item and I am getting the following error.
version: xx
is not valid on explosion date
no other versions are available
should the document link be transfered anyway?
What is the right approach to correct this?
if I choose yes, the production order does great created,
but is it going to be a valid order?
let me know
Cheers
JD LoeraHi,
I believe it should be a warning message, else system would not allow you to proceed, so do a re-check on that.
Coming to resolving the issue, this would occur when the valid-from date of the production version is later than the date on which bom & routing is exploded in the order. So before proceeding to make any changes, analyze the valid from dates of the BOM & Routing, now create the production version valid from that date.
This would at the very minimum ensure that the production version will be valid. If you still get a warning message, it implies that validty dates of the BOM & Routing needs a re-visit as well.
So go to MM02, MRP-4 / work scheduling view & modify the valid from dates of the production version. Once the same is done create a new order & system should read the production version.
Regards,
Vivek -
Automatic selection production version in MFBF
Hello !
I have a material setted with Selection method = 2(Selection by production version) in Material Master, so, I have two production version: V001 & V002, the last one is locked for any usage.
I need automatic selection of production version in MFBF , but when I'm doing the confirmation the system show the screen of production version selection with two versions .
Do you know what is missing for automatic selection works ?
Thanks a lot.
VeroHi Vernoica ,
Good Day , PV will be selected based on the lot size and the creation dates.
It will copy the PV (BOM & Routing ) based on Lot size or Explosion date you defind in MRP-4 view i.e. BOM selection ,BY -explosion date,1-lot size,2- by PV and 3 by PV only.
If you would like to get rid the selection of PV,
why dont you try created a production version than only go to material master change screen MM02 in MRP4 view and Select 2 at selection method field.
In the IMG (OPLD) for Order Type Dependent Parameters, the production version selection is already set to manual selection. But the production version is always defaulted as version 1 which is the first one in the material master and is not asking to select the version at the time of converting the planned order to a production order!
You can also check settings in configue trans OPL8 to have routing selection set to automatic selection if you want to avoid placing routing versions in each individual material master. Just another way to look at it
Hope it will resolve your problem. -
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,
VimalIn 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 -
Automactic Selection of production Version
Hi.
I have created a material "A"
I maintained in material master's MRP4 view selection method "2"
I have created two production version with same validity period & same lot size "0001" & "0002"
I maintained in order type dependent parameter's masterdata tab in production version column "Automatic production version selection"
Now when i am going to create a process order system is selection production version "0001".
But I want automatic selection of production version "0002".
What setting shall I do?
Regards
VivekDear Vivek,
I maintained in order type dependent parameter's masterdata tab in production version column "Automatic production version selection"
In order type dependent parameters maintain as manual selection
Then system will raise an pop-up to select production version while creating prodiuction order
The above setting is only useful while creating manual production order
If you are converting plan order to production order then above setting will not play any role
System will default take 1st PV
All you can do is you can change manually in plan order
Or if you want system to take automatically in MRP then you need to lock 1st PV
Also refer my reply from this thread
[Alternative BOM selection|Using customer to determine what BOM to use in Production order (tx:CO41);
Regards
Madhu -
Produciton version selection in MRP
Dear all,
we have prepared alt bom scenario for MTS with two prod versions.
I am facing one problem of production version selection while MRP.
In MTS scenario, system is picking the prod version no. 1 by default while creating order.
1. How we can configure/change the selection of Prod version while MRP?
2. I need to select the prod version on my choice in MTS / MRP(depends on materail availability)?
Thanks,
JeevanHi,
Production Version in Material Master in tab page "MRP 04". If BOM or Routing changes then PV also change. In Selection method two options are available related to PV- Selection by order quant. 1 Selection by explosion date 2 Selection by production version 3 Selection only by production version 1)With Selection by order quantity, the system chooses the alternative BOM into whose lot size range the order quantity falls. The lot size range and area of validity of the BOM apply. 2)With Selection by explosion date, the system chooses the alternative BOM into whose area of validity the date falls according to the setting BOM via dates. 3)With Selection by production version, the system chooses the alternative BOM defined in the valid production version. The lot size range and area of validity of the production version apply. 4) With Selection only by production version, the system chooses the alternative BOM defined in the valid production version. The lot size range and area of validity of the production version apply.
1. How we can configure/change the selection of Prod version while MRP?
=>OPL8 ->Production Version->1 Manual selection of production version
In MD61 - You can set in User Parameter-Requirements type - LSF Make-to-stock production
2. I need to select the prod version on my choice in MTS / MRP(depends on material availability)?
=>In MD61 - You can set in User Parameter-Requirements type - LSF Make-to-stock production
After this u can change PV while converting Plan order to production order.
With Regards,
Ashish -
Best production version and master recipe?
Is there a way in SAP (ECC.5.0) to choose the best production version on its own besides the date?
Can MRP choose the best production version and master recipe on its own based on cost?
If so How? Config?
Please advise
thanks
WalterHi,
MRP selects production version based on Lotsize,Validity date and status.In R/3 ,we dont have functionality like
1. Simultaneous MRP and Capacity Planning
2. Best Optimum route of production.
This is very much available in APO only. You can use either of Quota arrangement or Capacity evolution functionality to distribute planned qty into other resources based on past experience.
Regards,
Velmurugan S -
Hi,
I have a BOM with 3 alternatives all with the same validity period.
The material master contains a production version which has been created for alternate 3.
When I create a production order shouldn't I get alternate 3 defaulting in????
I am currently getting alternate 1!!!!
My order type is set to 'Automatic Production Version' selection!!
Help!!!!
Thanks
StuartDear Stuart,
Please check what value you have given in the Selection method under BOM
Explosion/Dependent Requirements in MRP4 view of the material master.
Please check whether value 3(Selection only Production version) is maintained.
You can also use option 2 - Selection by Production version.
Check with this & revert to forums.
Regards
Mangal -
Capaity levelling and production version
Dear SAPper,
I curious about somecases in levelling.
My client got 8 machine work center and they aware of capacity
I create eight produciton version.
MRP always put new planned order to first production order.
After that my client would like to do capacity levelling.
The problem is although they assign to other machine but the production version is not change
leaving inconsistency of production version and new work center after capacity levelling
is there any way we can capacity levelling considering produciton version too?
Please kindly help.
Best regards,
Freddy HaDear Freddy,
1.The system always picks up the first production version as a default,if more than one more production
version exists for the same lot size,validity dates.
2.Either you have to lock the production versions so that the system picks up the open production
version or maintain different validity dates or Lot size.
3.I'm not sure whether the system considers the prod version also during capacity leveling.
check this link,
http://help.sap.com/saphelperp60_sp/helpdata/en/1a/f2f33419ec8d44e10000009b38f844/frameset.htm_
Regards
Mangalraj.S
Maybe you are looking for
-
I have a gif file which is animated when it's sent to me from a windows user. The gif is actually 10 images and when animated, it shows a coyote walking. I can't seem to get it to animate when I send it. Ideally, I'd like to add it to my signiture. A
-
Windows 2008 r2 guests blue screen on Windows 2012 R2 Hyper-V Cluster with e5 2670-v2 processors
Hello all, We have a new hyper-v infrastructure deployed in two brand new Dell R720 Servers with 384GB of Memory and dual Intel e5 2670-v2 processors. This infrastructure is replacing an existing hyper-v 2008 R2 and all the guests are being migrated
-
Cant right click!! help!!
Why cant i right click on my macbook? im so confused!!
-
Count(*) , group by with multiple columns from multiple tables involved
Hi all, I am relatively new to SQL. Currently I have these few requirements, to display quite a number of fields from 3 tables for display of report. In my query I need to: 1.) count(*) 2.) select quite a number of fields from table 1,2,3 However whe
-
Call DLL function with pointer to simple struct
Hello, I try to call a function using CLFN. My problem is the parameters of the function I try to access. Here is the function and his parameter: typedef struct { int major; int minor; int revision; int build; } VersionNumberType; int Comm_BTE_softVe