Planning with diff. Production versions

Dear all,
i am using make to order strategy and scenari is that there are three versions of a fert. when sale order is generated and i run MRP how can i have three plan orders with 60:30:10 ratio. i mean if sale order is of 100 units then i want to plan 60 units by version A ,30 units by version B and 10 units

Shoaib ,
It will not work with sales order, but it work fine with MTS.
with sales order it will take whole quantity of all the orders and divide it into the quota.
check my reply in  the below thread and the findings of the Jawad.
Re: Quota Arrangement in Make to order Environment
Hope it will help you.
regards
Ritesh

Similar Messages

  • MRP with selected production version

    Dear PP experts,
    I have two production version
    Prod. Version      From lot        To lot size        Base Qty.
       1001                      1                   100                100 Kg.
       1002                      101             9999999          400 Kg.
    The batch size mentioned in the material masters are Mimimum lot size 100 Kg. and Maximum lot size as 400 Kg.
    I have entered PIR in MD61 for the material for 350 Kg. Since I need planned orders selectively of 100 Kg. in MD61 I have maintained in schedule lines tab production version as 1001.
    After running MD41 system creates planned orders with the production version, but the batch size is not as per the production version.
    Pl. let me know what needs to be done.
    Regards,
    Prashant

    Hi Watson,
    I can see some conflicts in your Master Data settings.
    First of all you have set your Lot size ranges in Material Master Data from 100 to 400 Kg.
    And your Production Versions (1001) set lot size range is 1 to 100 Kg.Which may creates conflicts.
    Now your require qty is 350 kg.So as per your lot size restriction set in Material Master will force system to create one planning proposal of 350kg.I can guess you get one plan order of 350kg but due to selection made in (MD61) selected prod. version is 1001 instead of 1002.Which is again wrong
    Now to make the things correct you can have below options,
    1) change Lot size restriction to 1 to 100 in Material Master.So you wil get 3 Plan orders of 100 Kg and 1 of 50 kg.
    or
    2) Instead of changing Lot size in Material Master, use quota arrangement (MEQ1).For this you have to first activate Quota arrangement in MRP 2 view of Material Master.Then go to MEQ1 and create quota for the specified period.Here you can restrict lot size at production version level.
    Regards,
    Dhaval

  • MRP Scheduling with a material with multiple production versions scrap rate

    Greetings all.
    I have a problem with MRP scheduling.  How do you account for different loss rates or scrap rates on a material because of multiple versions of a material that are in production.  For example, we have an item.  There are two differen ways to make that item and both have different loss rates or scrap rates.  How do we account for this.  And whatt happens when you have these with multiple routings.  Thanks.

    Dear,
    It can be handled in 3 ways.
    1st way - Create 2 versions to represent 2 ways of production. Create a 3rd version name it as total and make it as a first version so that MRP will take this version for scheduling. In total version give the most correct scrap qty and timming in routing. Hence when you run MRP system will consider the total version, then change the varsion in planned order as per your requirement.
    Second way - Create 2 version and if you are using Demand planning, in MD61 against the qty represent the version number so that when youn run MRP, the planned order will carry the version.
    3rd way - Create 2 Production version and create a quota arrangement and assihgn these two Production version as Quota items and give the % share. Hence when youn run MRP system will share the demand qty into two different version as per Quiota arrangement(setting in MRP2 is necessary fir planning).
    Please come back which one you are looking for so that we can give furthur information

  • Quality plan as per production version

    Hi SAP gurus,
    My client has multiple Production versions and they want to use different Quality plan as per version , how  I can map this process in SAP.
    I tired using in production version by putting Qualiity plan instaed of routing,  Inpection lot is created but when it come for the production order it was asking for the routing / or operation generation.
    As few specfication of Quality plan is different , that is the reason Plan has to be specific to PV.
    Thanks in advance.

    Hi
    Even if you create a Inspection plan you might have observed in the production version you have to specify the Routing.
    Reason is syem will check the routing for cost collector in production order.
    what you can do is may be you can carry out inprocess inspection with routing & specify the char in the task list
    or
    You may have to go for userexit while selection of the task list you will select the appropriate task list with appropraite prod version
    Also if you creat two inspection plan with two gr counters & do not tick on "Auto Assign" in the QM view,
    System will create a lot of 04 with CRTD status.
    In QA02 you can go & manually attach the relevent task list.
    What you can do is create a Group with name of "prod version" itself.This will ease the attaching of the tak list to the the lot.
    I hope this will add some value.
    Regards
    Sujit

  • Creating Production Order with wrong production version

    Hello Expert,
    please provide me answer and solution to resolve our problem regarding creation of production order (CO01 and CO41), because SAP provide and propose production version which have alternative BOM which is status 02 (inactive) already it is not picking the production version which has active alternative bom for our finished material. it is allowing the production to be created even the bom was inactive.
    please help us to this it still bugging our system
    tenx

    Hi Ryan,
    Production version will be selected based on the field Selection Method field in Material Matser MRP 4 view.
    1  Selection by explosion date
    2  Selection by production version
    3  Selection only by production version
    If the selected field value is 1 , then system selects the version based on the validity dates i.e whichever production version is active on that day that will be considered in MRP.
    If the selected field value is 2 by production version. Then system will select the First Prodution version mentioned in the Material Master MRP 4 View (production version Tab).
    If the selected field value is 3 always only by production version. Then system will select the First Prodution version mentioned in the Material Master MRP 4 View (production version Tab).
    So to address you query I suggest you to delete the production version PV1 with BOM 01 and Make production version PV2 will be available and active in seen as the first production version in teh screen.
    Then for your inof purpose you want have the PV1 then re-create it as second version in the Version tab screen.
    Regards
    radhak mk

  • Building an Installer with the product version major at 0

    Hi Everyone,
    I'm currently working on a prototype and I should build an installer for the prototype validation.
    The matter is that the prototype version start at 0, and I can't find a way to set in the product version major field at 0.
    Setting the major field at 0 is possible while building an executable, but not for an installer.
    My LabVIEW version is 12.0
    Thanks...

    Marc-junior wrote:
    It seems to me that it is the wanted behaviour application builder here. From the help page, you can read the following "You must increment the version number if you want to create upgrade versions of the installer that are capable of overwriting previous installers."
    That does not explain anything. We should be able to make the first ever version 0.0.0, that can later be upgraded to e.g. 0.0.1.
    According to microsoft:
    The format of the string is as follows:
    major.minor.build
    The first field is the major version and has a maximum value of 255. The second field is the minor version and has a maximum value of 255. The third field is called the build version or the update version and has a maximum value of 65,535.
    So, the max is 255.255.65535. There is no minimum given, so 0 should probably be allowed. I suspect that the input field in the build specification has an incorrect range setting.
    LabVIEW Champion . Do more with less code and in less time .

  • Data Guard with diff Oracle Versions??

    Hi,
    I have one query on Data Guard.
    Can I config. data guard with two different Oracle versions?
    i.e Primary=> 8i
    stand by=> 10g
    OR either way. Pls post your comments
    JAI HIND
    Darshan

    Some of the parameters that you need to have with Physical standby database are :
    *.background_dump_dest='/ford/app/oracle/admin/xchbot1/bdump'
    *.compatible='9.2.0.7'
    *.control_files='/home30/oradata/xchange/xchbot1/control01.ctl','/home30/oradata/xchange/xchbot1/control02.ctl','/home30/orad
    ata/xchange/xchbot1/control03.ctl'
    *.core_dump_dest='/ford/app/oracle/admin/xchbot1/cdump'
    *.db_block_buffers=1024
    *.db_block_size=8192
    *.db_file_multiblock_read_count=8# SMALL
    *.db_files=1000# SMALL
    *.db_name='xchbot1'
    *.global_names=TRUE
    *.log_archive_dest_1='LOCATION=/home30/oradata/xchange/xchbot1/archivelog'
    *.log_archive_dest_2='SERVICE=standby'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_format='arch_%t_%s.arc'
    *.log_archive_start=true
    *.log_buffer=16384000# SMALL
    *.log_checkpoint_interval=10000
    *.max_dump_file_size='10240'# limit trace file size to 5 Meg each
    *.parallel_max_servers=5
    *.parallel_min_servers=1
    *.processes=50# SMALL
    *.rollback_segments='rbs01','rbs02','rbs03','rbs04','rbs05','rbs06','rbs07','rbs08','rbs09','rbs10'
    *.shared_pool_size=67108864
    *.sort_area_retained_size=2048
    *.sort_area_size=10240
    *.user_dump_dest='/ford/app/oracle/admin/xchbot1/udump'

  • Can any one help me  with SAP product version information,

    1) NW04. Which has two subsequent versions:
    SAP Netweaver 2004
    SAP Netweaver 2004S (Alias SAP Netweaver 7.0), for which one enhancement
    pack exists:
    - EHP1
    2) NW05. Which has one version:
    SAP Netweaver 2005 (Contains ECC 6.0 / ERP 6.0), for which four
    enhancement packs exists:
    - EHP1
    - EHP2
    - EHP3
    - EHP4 (Available from 21.11.2008). EHP4 seems to exist in two flavors,
    "Easy adaptation", and "Continues Innovation"
    3) NW06 (Alias SAP Netweaver 7.1, currently in rampup phase)
    4) SAP Netweaver 7.2 (Available in 2009)
    First question:
    The Netweaver Developer Studio (NWDS) seems to exist in two versions:
    - NWDS 7.0
    - NWDS 7.1 (As part of the Composit Environment / CE) Which SAP
    Netweaver release(s) support the above NWDS versions?
    Second question:
    Has anything changed in the graphical capabilities (such as the
    availability of GUI controls, office integration, etc) between both NWDS
    versions? If so, what are the major changes?
    Third question:
    The CE environment contains development tools for SOA development.
    Is it possible to use NWDS from the CE environment, without requirering
    end-users to install the CE environment on their system?
    Fourth question:
    Are there any differences in the graphical capabilities between NWDS
    Java and WebDynpro for Java.
    If so, which?
    Are there any differences in the integration capabitlities (i.e. ABAP
    dictionary info, help texts, search helps, messaging, etc) between
    WebDynpro for Java and WebDynpro for ABAP?
    If so, which?

    Have you got any answer for these questions
    Nikhil

  • Demand Management with Production Versions

    Dear all,
    Is it possible to link the requirements in Demand Management with a production version which I've listed in the MRP 4 view?

    Hi,
    Yes it is possible. In MD61 when you place independent demands, switch to the schedule line view & specify which Production Version you want the demand to consider.
    Hope the above clarifies.
    Regards,
    Vivek

  • How to add production Version  field in COOIS to selection options?

    Dear Experts,
    Need your suggestion for below issue raised by client.
    1) As per client, he was running COOIS with the selection option of a production version. But currently he is  not able to see this selection while executing a COOIS t-code.-----> Kindly guide me on its possibilities & necesary checks.
    2) If I want to correct it & want to add Production Version field in COOIS report what steps I should take?
    Need all your valuable guidence to resolve above issue.
    Thanks & Regards,
    Mehul

    Hello Vivek,
    Really thanks for your mail. Please see below comments-
    1) I checked the transaction COOIS & also told user to select Production Version after executing the report by giving Plant code & dates. But user asking for this field before execution.
    As per your suggestion I checked in Header level of first screen but its not showing me also.
    2)  I am using ECC6.0 version
    3) One finding from my side- This is I am checking only selecting Production Orders. But when I am selecting only Planned order then Production version can be seen in first screen under Repetitive Mfg. section.
    so kindly tell me why this not showing when Production order selected?
    Thanks in Advance for your help.
    Regards,
    Mehul

  • Is there option to assign Production Version in MD62

    Hi,
    Can any one please help.
    I have a HALB Material with 3 Production Versions (with the same Lot Size and Validity Dates)
    While creating Planned Indipenmdent requirement (PIR). how can i specify what Production version to be used here and as well for MRP run.
    Can any one please guide me.
    Thanks and Regards
    Khadeer

    Hi,
    Goto MD62
    Execute the report
    Goto Schedule line tab page
    Fallow the menu path
    Setting Production version
    Enter the Production version required
    Save
    Check the PV where it is in green colour it should be active with valide date.
    Regards,
    R.Brahmankar
    Edited by: R Brahmankar on Aug 2, 2008 4:34 PM

  • Multiple Production Versions in Subcontracting Inforecord

    Hi Gurus - I have a question on how to assign multiple production versions in Sub-contracting Inforecord?
    I heard this functionality is available in ECC 6.0 is that true? If so how can I assign multiple production versions? What happens after we CIF across to APO? Any help is highly appreciated.
    Thanks and regards,
    Murali.

    Murali - Its possible to use multiple PV in sub contracting.
    Settings in ERP :
    1. In CFC9 activate the - Transfer multiple selection of PDS indicator. When you select this indicator, the system allows you to select several productions versions in the integration model; it also creates a Production Process Model (PPM) or Production Data Structure (PDS) for each production version in SAP SCM
    2. Assign the PV's to the subcontracting info record through -  Logistics  - Central Functions  - Supply Chain Planning Interface - Core Interface - Advanced Planner and Optimizer - Environment  - Data Transfer  -Assign Multiple Production Versions
    3. When you select the integration model parameters for PDS, you have selected PP/DS Subcontracting as the PDS Type value. Similarly, for PPM, you have selected Subcontracting PPM as the Type of PPM value.
    Subcontracting with multiple production versions is supported. However, the integration with an SAP ERP system requires at least SAP ERP 2005 with Enhancement Pack 03.
    Rgds
    Valavan

  • Change the Product version from ECC to ERP 6.0

    Hello Experts
    I am planning to apply EHP4 on my Development ECC system. In line with the the suggestion from guide "How to install SAP Enhancement Package 4 for SAP ERP 6.0" system I am supposed to define my ECC system with leading product version ERP 6.0.
    My Ecc system is currently defined with Product version SAP ECC 6.0.
    As per the above guide and also suggestion from "Note 1344564 - Maintenance Optimizer: Check system landscape" which says-
    "In particular for a system of the product SAP ERP, assign the product version of SAP ERP, not SAP ECC."
    I am supposed to change the leading product version to ERP 6.0.
    Now with the current definition of system with product version SAP ECC 6.0, it is being used in a logical component. In order to change this I need to delete the associated logical component. The problem is -this logical component is being used in more than one Project definition that has huge documentation associated with them.
    My question -
    will the deletion of current logical component affect my documentation in any way?
    How can I change the product version from SAP ECC 6.0 to SAP ERP 6.0 without affecting the current setup?
    Regards
    Dhiraj

    Hello Warren,
    Thanks for the suggestion.
    I have already taken care of all the suggested notes in the master note that you suggested. I am able to generate the XML file for other solution defined in my system. In those I have my ECC system defined purely as ERP 6.0 system. I am not able to make out why its not generating the XML for this solution.
    Regards
    Dhiraj

  • Error as Production Version = or repetitive mfg indicator cannot be deleted

    Hi Guys,
    Please let me know before I delete the Production version for a material what are all the steps I need to carryout.
    Requesting to explain with detailed steps/Points.
    Cheers,
    Kumar.S

    Dear Kumar,
    1.First check whether is there any planned order assigned with this production version in MD04 or else in MD16.
    2.Either confirm these planned orders using T COde MFBF or else delete these orders in MD16 or else in MD12.
    3.Also clear the reprocessing list present in MF47.
    4.Do the variance calculation and settlement (KO88)
    4.Now here this issue can handled in 2 ways,one is set the valid to date as the system's date to the production version.
    5.If you want to delete the production version,then the cut off period has to be set by the CO part and proceed.
    Check these links,.
    Re: Delete Production version
    Re: production version
    Regards
    S Mangalraj

  • Costing - Multiple Production Versions and Recursive BoMs

    Hi All,
    We have a production and product costing scenario as follows:
    Production versions 10, 20 and 30. It takes all three versions to manufacture the finished material and there are no intermediate products in this scenario. 10 and 30 are to be costed and 30 is a recursive BoM with the input from version 10 also being the output. 10 is the main production step with components but 30 is a recursive BoM sometimes only with the output material as the input and sometimes with a more complete BoM but which includes the output material as an input component.
    The quantity input appears to be the same as quantity output for the recursive element.
    If anyone has come across this scenario and you can let me know what design principles you followed I would appreciate it.
    We are getting iteration error messages when costing production version 30 and even reducing the input quantity below 95% of the input as per the SAP documentation does not fix the error message.
    Any help you can give will be greatefully received.
    Thanks.
    Regards,
    Tim

    Murali - Its possible to use multiple PV in sub contracting.
    Settings in ERP :
    1. In CFC9 activate the - Transfer multiple selection of PDS indicator. When you select this indicator, the system allows you to select several productions versions in the integration model; it also creates a Production Process Model (PPM) or Production Data Structure (PDS) for each production version in SAP SCM
    2. Assign the PV's to the subcontracting info record through -  Logistics  - Central Functions  - Supply Chain Planning Interface - Core Interface - Advanced Planner and Optimizer - Environment  - Data Transfer  -Assign Multiple Production Versions
    3. When you select the integration model parameters for PDS, you have selected PP/DS Subcontracting as the PDS Type value. Similarly, for PPM, you have selected Subcontracting PPM as the Type of PPM value.
    Subcontracting with multiple production versions is supported. However, the integration with an SAP ERP system requires at least SAP ERP 2005 with Enhancement Pack 03.
    Rgds
    Valavan

Maybe you are looking for