Change Planned order components

When we change a component in a planned order that is different from the manufacturing BOM, is there a way to distinguish what component was changed.

Hi Ramesh,
There is no transaction available to compare Production Order component list to BOM Component list. You need to create a Z report for yourself.
If it is just comparing 2 BOM's then you can use transaction CS14.
Hope this helps...
Regards,
Prasobh

Similar Messages

  • Reg. Mass update of Planned order components

    HI all,
    I have a requirement wherein I will come to know the raw material consumption from storage location only at the time of production.
    Now what I am doing is before doing confirmation I am updating the storage location for particular component in the planned order change mode - md12.I am doing this because the  production confirmation is happening at External system and transferred via IDOC to SAP.So I cant add the sloc at that time.
    I am doing the changes to planned order one by one. On an average I am doing this for say 50 Planned orders which is time consuming
    Is there any option available in SAP to do mass change to the planned order components.
    Regards,
    MBN.

    Hi MBN,
    You can use the LSMW, BDC program or FM MD_PLDORD_CHANGE_COMP_ITEMS to update the storage location in planned order components.
    Regards,
    R.Brahmankar

  • BAPI to change planned orders details

    Hi Experts,
    I need BAPI to change Planned order details,which are created through SNP PPM's.I searched for Bapi and got one 'BAPI_MOSRVAPS_SAVEMULTI3'  but this BAPI will change order details if created for PP/DS PPM's.
    Kindly suggest will this BAPI only work or someother.
    I want to keep the PPM name blank and save the order details through BAPI.
    Pls reply asap.
    Thanks
    surbhi

    Hi Surbhi,
    You may please search on google, there are lots of tutorial on BDC, you will surely get the solution... in short BDC is to record a transaction & then use same recording to generate ABAP program & you can play with screen navigations & update the fields you required...
    Regards,
    Adarsh

  • Change planned order - MD12

    Hi,
    What is the function of 'assign version' from the list of 'edit' in MD12 - change planned order.
    Is there a way to change the BOM revision level assigned by MRP run?
    Currently MRP assign the most recent revision level to a planned order, and I would like to be able to change it to a previsious revision level.
    Thanks
    Lin-Lin Li

    Hi,
    "Assign Version" is like the reading Master data in Planned Order.
    Now try this. in your Pl. Order Change Screen,  slect Master data Tab pag.
    Then try the "Assign Version", your BOM details in the lowerpart of the screen vanishes.
    You will get the message saying "Explosion data has changed, please re-explode" if you confirm this by Pressing Enter.
    Then the BOM details dat will go off and you can select another PV.
    Otherwise directly you can change the PV in the entry screen itself.
    Hope this helps..
    Regards,
    Siva

  • BADI For Changing Planned order Qty during MRP Run

    Hi,
      My requirement is i want to change Planned order qty based on some conditions during MRP run(MD02). Is there any BADI to fullfill my requirement.
    Thanks,
    Kishore

    Not sure I understand the situation correctly...You want to delete the planned orders before MRP runs again. WHy do you want to do that ? Are these firmed Planned orders ?

  • Planned Order Components Table

    I have a question. Is there a table that holds the components of a Planned Order?
    When I see the technical data of a component field in MD13 it tells me they are in MDPM, but this is a structure, not a table.
    that made me think that perhaps this is being fed directly from the BOM. But when I make a change to the BOM, the components in the planned order are not automatically updated.
    So they must be stored somewhere. Anyone knows which table it is?
    Otherwise, what FM can I use to fetch them?

    Fernando,
    You can get the components list of a planned order in RESB table for field PLNUM = Planned order number and BDART = SB.
    Regards,
    Prasobh

  • Automatic Firmed Planned Order / Mass Change Planned Order

    Hi PP Gurus,
    My requirement is I want to make all planned order created from planning run will be automatically firmed. I tried several option :
    1. MRP type : P1, automatic create firmed planned order within planning time fence but for new requirement, planned order will be created after planning time fence date. Example planning time fence date lies on 20/10/2011
    PIR
    09/2011     3 pc
    10/2011     4 pc
    end of planning time fence date
    11/2011     5 pc
    run MRP
    Planned order firmed for month 9 and 10. for 11 is not firmed. But the problem is if PIR on month 10 is change from 4 to 6. the other 2 planned order will be created at end of planning time fence date.
    Is it possible for planned order created at appropriate date as requirement date ???
    2. Mass Change of Planned Order
    I browse the help SAP there is function module : MD_SET_ACTION_PLAF for mass changes of planned orders.
    http://help.sap.com/saphelp_46c/helpdata/en/9e/e84226c1c311d3b54a0004ac160649/content.htm
    I execute it with SE37 but i don't know what should i do with this function module after the next screen.
    In my mind, there will be selection screen for choosing which planned order will be perform firmed action.
    Any other idea to solve my requirement is welcome.
    Regards,
    Arman Lie

    Dear Arman,
    Use T.Code MD19 for firming the planned orders,also check MDBA for firming the planned order.
    For your first question let me check and revert back.
    Regards
    Mangalraj.S

  • Change planned order operations

    Dear guru ,
    i must develop an abap program that must change the operations of a planned order.
    I can insert or delete the operations of the planned order.
    Which best solution (BAPI,user exit ..) can you suggest ?
    Thanks

    Hi
    there is no solution to this answer. you can't change operations in a PLANNED order. planned orders only refer to the master data (BOM, Routing, master recipe, task list, ...).
    You have to either change the operations in the routing, recipie, task list, ... (if it is a change for all new orders) or convert the planned order to a PRODUCTION/PROCESS order and manipulate the operations there (if it is a one-off change)
    Other options include the use of production versions as setup in MRP-4 of the material.
    Björn

  • Change the order components are painted (easy z-order)

    All,
    What is the best way to change the order child components are painted in my JPanel? I keep reading everywhere that you shouldn't override paintChildren() unless you really know what you are doing. I guess I don't know what I'm doing in that respect. Very weird things happen if I override paintChildren(). Any help?
    Duke Dollars up for grabs!
    Thanks,
    -Alan

    Why do you want to know the order in which your components are painted? Are you getting a null pointer exception?
    If that is the case then it is more dependent on which component is created first. The order of your code determines which objects are null or not.
    JTextArea area;
    JButton button;
    button = new JButton("Hello");
    button.setBackground(area.getBackground());  // this will throw a null pointer exception
    area = new JTextArea("Go Away", 20 , 10);
    area.setForeground( button.getForeground() ); // this works fineIf that is not the case, could you elaborate on your problem?
    ICE

  • Problem in changing Production order components.

    The problem is happening while changing components in Production order.
    Take a look at the source code.
    data :      IS_ORDER_KEY  TYPE  COXT_ORD_KEY,
    IS_ORDER_COMPONENT_KEY  TYPE  COXT_S_ORD_COMP_KEY,
    IS_REQUIREMENT_QUANTITY TYPE  COXT_S_QUANTITY,
    IS_REQUIREMENT_QUANTITYX  TYPE  COXT_S_QUANTITYX,
    IS_CONFIRMED_QUANTITY TYPE  COXT_S_QUANTITY,
    IS_CONFIRMED_QUANTITYX  TYPE  COXT_S_QUANTITYX,
    I_MATERIAL  TYPE  COXT_MATERIAL,
    I_MATERIALX TYPE  COXT_MATERIALX,
    IS_ORDER_OPERATION_KEY  TYPE  COXT_S_ORD_OPR_KEY,
    IS_ORDER_OPERATION_KEYX TYPE  COXT_S_ORD_OPR_KEYX,
    IS_REQUIREMENT_DATE TYPE  COXT_S_DATE,
    IS_REQUIREMENT_DATEX  TYPE  COXT_S_DATEX,
    IS_STORAGE_LOCATION TYPE  COXT_S_STORAGE_LOCATION,
    IS_STORAGE_LOCATIONX  TYPE  COXT_S_STORAGE_LOCATIONX,
    I_BATCH TYPE  COXT_BATCH,
    I_BATCHX  TYPE  COXT_BATCHX,
    I_MI_CONFIGURATION_OBJECT TYPE  COXT_CONFIG_OBJECT,
    I_MI_CONFIGURATION_OBJECTX  TYPE  COXT_CONFIG_OBJECTX.
    DATA  :wa_resb type resb,
           ES_BAPIRETURN TYPE  COXT_BAPIRETURN,
    E_ERROR_OCCURRED  TYPE  C.
    IS_ORDER_KEY = '000002098003'.
    select single * from resb into wa_resb where aufnr eq IS_ORDER_KEY
       and bwart eq '531'.
    move-corresponding wa_resb to IS_ORDER_COMPONENT_KEY.
    IS_REQUIREMENT_QUANTITY-quantity = '10.23'.
    IS_REQUIREMENT_QUANTITY-uom = 'KG'.
    IS_REQUIREMENT_QUANTITYX-quantity = 'X'.
    IS_REQUIREMENT_QUANTITYx-uom = 'X'.
    *IS_STORAGE_LOCATION-lgort = '1060'.
    *IS_STORAGE_LOCATIONX-lgort = 'X'.
    I_MATERIAL = wa_resb-matnr.
    IS_STORAGE_LOCATION-werks = wa_resb-werks.
    IS_STORAGE_LOCATIONx-werks = 'X'.
    IS_STORAGE_LOCATION-lgort = '1060'.
    IS_STORAGE_LOCATIONX-lgort = 'X'.
    CALL FUNCTION 'CO_XT_COMPONENT_CHANGE'
       EXPORTING
         IS_ORDER_KEY                     = IS_ORDER_KEY
         IS_ORDER_COMPONENT_KEY           = IS_ORDER_COMPONENT_KEY
         IS_REQUIREMENT_QUANTITY          = IS_REQUIREMENT_QUANTITY
         IS_REQUIREMENT_QUANTITYX         = IS_REQUIREMENT_QUANTITYX
         IS_CONFIRMED_QUANTITY            = IS_CONFIRMED_QUANTITY
         IS_CONFIRMED_QUANTITYX           = IS_CONFIRMED_QUANTITYX
         I_MATERIAL                       = I_MATERIAL
         I_MATERIALX                      = I_MATERIALX
    *   IS_ORDER_OPERATION_KEY           = IS_ORDER_OPERATION_KEY
    *   IS_ORDER_OPERATION_KEYX          = IS_ORDER_OPERATION_KEYX
    *   IS_REQUIREMENT_DATE              = IS_REQUIREMENT_DATE
    *   IS_REQUIREMENT_DATEX             = IS_REQUIREMENT_DATEX
         IS_STORAGE_LOCATION              = IS_STORAGE_LOCATION
         IS_STORAGE_LOCATIONX             = IS_STORAGE_LOCATIONX
         I_BATCH                          = I_BATCH
         I_BATCHX                         = I_BATCHX
         I_MI_CONFIGURATION_OBJECT        = I_MI_CONFIGURATION_OBJECT
         I_MI_CONFIGURATION_OBJECTX       = I_MI_CONFIGURATION_OBJECTX
    *   I_BATCH_SEL_CUOBJ                = I_BATCH_SEL_CUOBJ
    *   I_BATCH_SEL_CUOBJX               = I_BATCH_SEL_CUOBJX
    *   I_XFEHL                          = I_XFEHL
    *   I_XFEHLX                         = I_XFEHLX
    *   I_SOBKZ                          = I_SOBKZ
    *   I_SOBKZX                         = I_SOBKZX
    *   I_KDAUF                          = I_KDAUF
    *   I_KDAUFX                         = I_KDAUFX
    *   I_KDPOS                          = I_KDPOS
    *   I_KDPOSX                         = I_KDPOSX
    *   I_PSPEL                          = I_PSPEL
    *   I_PSPELX                         = I_PSPELX
    *   I_KZAUS                          = I_KZAUS
    *   I_KZAUSX                         = I_KZAUSX
    *   I_NAFKZ                          = I_NAFKZ
    *   I_NAFKZX                         = I_NAFKZX
    *   I_NOMAT                          = I_NOMAT
    *   I_NOMATX                         = I_NOMATX
    *   I_NFUML                          = I_NFUML
    *   I_NFUMLX                         = I_NFUMLX
    *   I_NFPKZ                          = I_NFPKZ
    *   I_NFPKZX                         = I_NFPKZX
    *   I_NOMNG                          = I_NOMNG
    *   I_NOMNGX                         = I_NOMNGX
      IMPORTING
        ES_BAPIRETURN                    = ES_BAPIRETURN "initial
        E_ERROR_OCCURRED                 = E_ERROR_OCCURRED"blank not showing 'X'.
    CALL FUNCTION 'CO_XT_ORDER_PREPARE_COMMIT'
      IMPORTING
        E_ORDER_KEY            = IS_ORDER_KEY
        ES_BAPIRETURN          = ES_BAPIRETURN
        E_ERROR_OCCURRED       = E_ERROR_OCCURRED
    * TABLES
    *   ET_ORD_KEY_MAP         = ET_ORD_KEY_MAP
    *   ET_BAPIRETURN          = ET_BAPIRETURN
    write : 'dfdfdf'
    Notable point is that after executing CO_XT_COMPONENT_CHANGE' parameters ES_BAPIRETURN and E_ERROR_OCCURRED are initial.
    This explains that the FM has been executed successfully.
    But still the changes are not done in production order.
    Please let me know where i am mistaken.

    nabheet,
    this is called expilicitly for commit.
    Not in any exit or something.
    Have a look at the source code which i have posted while starting this discussion.
    This below FM is called just after CALL FUNCTION 'CO_XT_COMPONENT_CHANGE'
    Look at the source code in starting of discussion. U will understand when it is executed.
    CALL FUNCTION 'CO_XT_ORDER_PREPARE_COMMIT'
      IMPORTING
        E_ORDER_KEY            = IS_ORDER_KEY
        ES_BAPIRETURN          = ES_BAPIRETURN
        E_ERROR_OCCURRED       = E_ERROR_OCCURRED
    * TABLES
    *   ET_ORD_KEY_MAP         = ET_ORD_KEY_MAP
    *   ET_BAPIRETURN          = ET_BAPIRETURN

  • Error on RESB table changing planning order using BAPI_PRODORD_CHANGE

    Hallo.
    In my custom program ZINTERFACE_ORDER, I use BAPI 'BAPI_PRODORD_CHANGE' to change multiple production order (quantity / start date/ end date).
    CALL FUNCTION 'BAPI_PRODORD_CHANGE'
         EXPORTING
    number       =  wk_ordine
    orderdata    =  wk_orderdata
    orderdatax  = wk_orderdatax
         IMPORTING
    return         = bapi_return.
    First order change works right, but the second order generate the error:
    TYPE: E
    ID      : CO
    NUMBER : 888
    MESSAGE:  Internal: Error when reading document table RESB
    The error is generated by  COXT_BAPI_ORDER_CHANGE , called internally from the above BAPI_PRODORD_CHANGE
    And I have to exit from my custom report and reprocess the second order to work.
    It seems that there is a lock on RESB table.
    Could you
    help me?
    Thanks a lot
    Giancarlo

    You need to find the lock that is being set.  After your BAPI Commit, you need to test that the lock is cleared.  If not, do a wait for 1 sec and retest.
    Unlock (and lock) are queued objects that do not occur until after the commit is complete.  Because they are queued, they can get slow.  Especially when a background process is going to try to work with multiple in a short period of time.
    Neal

  • How to change the components of the planned order? (FM or BAPI)

    I need to change the storage(LGORT) in the components.
    I found only MD_PLDORD_CHANGE_COMP_ITEMS, but could not get the correct result.
    Has anyone used this FM to change the components of the planned order?
    Can you please tell how to use it. Or advise an alternative solution.

    Hi Anton,
    There's a BAPI to change planned orders - BAPI_PLANNEDORDER_CHANGE, but it allows to change only header data.
    Therefore you'll have to go a bit longer, and use a couple of other BAPIs:
    First read the order that you want to change - BAPI_PLANNEDORDER_GET_DETAIL
    Second, create a new planned order with the changed data, based on the read planned order - BAPI_PLANNEDORDER_CREATE.
    Third, delete the old planned order - BAPI_PLANNEDORDER_DELETE.
    Regards,
    Mario

  • Changing & deleting the SNP PDS planned order in APO using BAPI

    Hi,
    There is a requirement to consolidate the SNP PDS planned order created from CTM in APO. This is to change one of the SNP PDS planned order by adding the quantities of the other planned order , which is to make it into one & delete the other SNP PDS planned order. Can this be done progrmatically using BAPI?. As we know this cant be changed in RRP3 as the SNP-PDS are uneditable.Please help me on this one. As I need the solution to this ASAP.
    Is there any BAPI/FM using which SNP PDS planned order can be changed? What is the BAPI for PPDS planned order creation / change?
    With thanks & regards,
    Naveen
    Message was edited by: Naveen Srinivasa

    Hi Mariano,
    I have gone through the description of the FM it says:
    This function module is complex and is subject to several technical restrictions. For this reason, you should not use ORDER_CHANGE for extended periods of time.
    The recommended alternatives are:
    OM_ORDER_CREATE
    for creating orders
    OM_ORDER_DELETE
    for deleting orders
    OM_ORDER_MODIFY
    for changing existing order components
    Have you used these FM any time?.Kindly share more details in case is you have used them.
    with thanks & regards,
    Naveen

  • User exit/ badi needed for planned order create/change,collective ATP check

    Dear All,
    I'm looking for a user exit/ badi which can be used for planned orders at the stage of
    mass collective availability check (COMAC tcode) update; or at some other relevant stages of mass update of planned orders.
    I need after collective availability check to perform the following:
    1) to copy date from "total comitment" field on header tab of planned order and paste it (replace old date) to order finish date on header screen
    then
    2) to start a scheduling.
    Very appreciate your help.
    Best Regards,
    Andrey
    Edited by: Andrey Kruglov on Apr 15, 2010 3:06 PM
    Edited by: Andrey Kruglov on Apr 15, 2010 3:07 PM

    Dear,
    Use the BAPI : BAPI_PLANNEDORDER_CHANGE
    Or use the function module MD_SET_ACTION_PLAF for Schedule planned order.
    and the transaction MDAC Execute action for planned order
    This function module includes the following actions:
    Explode BOM
    Explode BOM, check availability
    Check availability, only explode BOM in the case of a requirement
    Check availability, do not explode BOM
    Reset availability
    Change planned order data
    Schedule planned order
    Delete planned order
    Assign the key for the respective action control to the materials in the material master (MRP 4 view).
    Please refer this thread,
    Re: MDVP for collective orders
    Regards,
    R.Brahmankar

  • RECORDING CHANGES IN PLANNED ORDER

    HOW TO KEEP HISTORY OF CHANGES PLANNED ORDER.

    Hi,
    As per my knowledge, It is not possible to track history of changes for planned orders.
    You can track changes of Production /Process orders in OCM & Master data like BOM,Routing changes in ECM.
    Regards,
    Tejas

Maybe you are looking for