Problem in production order creation

Hi All,
I am using BAPI "BAPI_PRODORD_CREATE" for creation of production orders. But if i pass the value to the BAPI, i am getting the error WBS Element does not exist always...
But if i give the same value in SE37 directly the BAPI is creating Production orders........But program level it is not working.......Please help me
Even i used for converstion level FM before passing the value to BAPI structure i.e "CONVERSION_EXIT_ALPHA_INPUT"
NOTE: this BAPI not require for COMMIT......
Thanks & Regards
Santhosh

Hi,
Check [this|Re: About BAPI_PRODORD_CREATE; forum.

Similar Messages

  • Problems in production order creation!!

    Hello SAP experts, how are you , i have a question , can i configure the system to run the batch determination and then the ATP when i create a production Order with the CO01??, is there some option in spro to do it?.
    Kind Regards.

    German,
    Follow path SPRO- IMG- Production - Shop floor control- Master data--- Define production secheduling profile T code OPKP.
    Go into details of plant & prod. scheduling profile combination.
    Under batch management, for 'Automatic batch creation in order' either select 1 or 2 as per your requirement.
    Hope this helps you.
    SmanS

  • Problem in process order creation.

    Dear Sir/ Madam
                             i am facing a problem while process order creation.
    the problem is:
    Error when calculating cost for order ATFEDEC11  "see log Log is deleted when saving
    Do you still want to save?"

    Hi,
    The log for production order preliminiary costing is not saved. Therefore, once the order is saved, there is no log available anymore (this is by the way a question of PP; none of the logs is saved).
    Hope that helps...
    Regards,
    Declan

  • Batch no assigning during production order creation

    Sir,
    We are manitaining the batch management for inut raw materials. During production order creation it is mandatory to assign the batch no for raw materials then only production order releasing is possible.In our case due to batch assignement to production order while order creation,we are facing the lot of problems like batch no not assign for full req qty and also if unavailabilty of stock for particular batch no it will come to COGI.hereby i need experts help for,
    1.I want to determine the batch no during confirmation instead of order creation and also allow to release the production order even batch should be in blank.
    Kindly help
    Regards,
    PS

    Hi
    For Rawmaterials why cant'n you assign Batch nos buring GR of purchase order.
    Then you can do automatic batch determination during confirmation of order for mvrmt type ;261...
    This is  easy  to handle.
    Please check and come back
    Regards,
    srihari

  • Backflushing problem in Production order

    Hi,
      In my scenario we use valuation type for the components which we consume in the production order.There is one BATCH field in the component list for a production order.
    There i can give my valuation type of material which i want to consume for that order.But all the time i have to give it manually in the order.Is there any possiblility of picking it up automatically because i use backflush concept.
    So in my CO11N transaction the goods movement  tab appears
    where the componets get displayed.but i have to give the valuation type field manually.Other wise automatic GI does not happen.
    The problem is that i have approximately 60 components to be backflushed for an order and  all the time i have to give the valuation type maually.So it is creating problem for me.
    Please suggest.
    Regards
    madan

    Hi!,
    I think you are using spit valuation and want automatic determination of valuation type as per priority set in the configuration. For this you need to define stock determination rule/group etc. Make the necessary configuration in SPRO> Material Management> Inventory Management> Stock determination. Make the necessary assignments for various functions mentioned there such as inventory management / production order / pick list etc.
    If you want to default the valuation type for the HALB / FERT material (Split valuated) while production order creation then you need to do necessary configuration for their respective material types in SPRO>Mat Management>Valuation & Account determination>split valuation. There you can give default valuation type for the material type and also you can keep it modifiable or nonmodifiable.
    I hope this will solve your problem.
    Regards,
    Uday

  • Block the production order creation till approval of sales order

    Dear
    We are using MTO process. Client is asking to avoid the creation of production order still the sales order is approved. In sales order one user status is defined as approved. By default when sales order is created the status will be in not approved and once the accounts clears, they manually change the status to approved. Is it possible to put system check  to avoid the production order creation till sales order status is changed to approved?? Any idea??.
    Thanks in advance.

    Dear Usmani,
    I'm facing the same problem as you. Do you already have the solution for this?
    As of now, the only solution to stop the transfer of requirement to MRP is to set the delivery block at the header level and also flag on the "Fixed Date & Qty" in each schedule line item. The problem is now to deflag the "Fixed Date & Qty" in each schedule line item when the Sales Order is confirmed.
    Please share should you have any other solutions.
    Thank you.
    Regards,
    Jieyi

  • APO: RRP3 automate Production order creation from planned order ?

    Hi everyone ,
    I have got a business requirement in APO where in Open sale orders uploaded in R/3, needs to be converted to Planned order and subsequently to Production order in APO-PPDS tcode RRP3 at all stages. They want to automate this process rather than doing it
    manually.
    Can anyone tell how is this possible . Any BAPI or function module available to do this . Please help.
    Regards,
    Syed

    Hi,
    1.You need to run the heuristics Planning of standard lots SAP_PP_002  in /SAPAPO/CDPSB0 by specifying the time profile
       and  strategy profile, planning version and propagation range, product and location.
    2. Convert PPDS Planned Orders created to process orders thru /SAPAPO/RRP7 by specifying the product location start date of the order for production order creation.
    Out put of step 1- For sales order requirement, PPDS Planned orders gets created.
    Out put of step 2- PPDS Planned orders are converted to production orders.
    Thanks,
    nandha

  • IDOC/BAPI for Production order creation from Legacy system

    Hi all
    We are using an interface to create Production orders from legacy to SAP. Would you recommend an IDOC or a BAPI to create Production orders. If IDOC or BAPI then could you please mention which one?
    thanks a bunch

    Hi John,
    For your purposes, please use BAPI for production order creation from legacy system. There is no standard inbound IDoc available to use. SAP has an IDoc for outbound interface only (message type LOIPRO).
    If there is an inbound IDoc available, I would recommend to use an IDoc.
    IDoc technology has excellent error handling and will allow you to reprocess an error (if any).
    BAPI is also good approach to use and fast in term of  processing.
    For BAPI approach, you can use BAPI BAPI_PRODORD_CREATE.
    Hope this will help.
    Regards,
    Ferry Lianto

  • BAPI - Problem in Sales order creation

    Hi Friends,
    I have problem in Sales order creation using BAPI ,I am getting a messsage - Error in creating document ,I have sent the code along with this mail ,can you help it out.
    Code:
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
    PARAMETERS: p_auart TYPE auart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Sales organization
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
    PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Distribution channel
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
    PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Division.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
    PARAMETERS: p_spart TYPE spart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    Sold-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
    PARAMETERS: p_sold  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Ship-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
    PARAMETERS: p_ship  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    Material
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
    PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Quantity.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
    PARAMETERS: p_menge TYPE kwmeng  OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Plant
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
    PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Data declarations.
    DATA: v_vbeln            LIKE vbak-vbeln.
    DATA: header             LIKE bapisdhead1.
    DATA: headerx            LIKE bapisdhead1x.
    DATA: item               LIKE bapisditem  OCCURS 0 WITH HEADER LINE.
    DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
    DATA: partner            LIKE bapipartnr  OCCURS 0 WITH HEADER LINE.
    DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
    DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                             WITH HEADER LINE.
    DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                             WITH HEADER LINE.
    Initialization.
    INITIALIZATION.
    v_text   = 'Order type'.
    v_text1  = 'Sales Org'.
    v_text2  = 'Distribution channel'.
    v_text3  = 'Division'.
    v_text4  = 'Sold-to'.
    v_text5  = 'Ship-to'.
    v_text6  = 'Material'.
    v_text7  = 'Quantity'.
    v_text9  = 'Plant'.
    Start-of-selection.
    START-OF-SELECTION.
    Header data
    Sales document type
      header-doc_type = p_auart.
      headerx-doc_type = 'X'.
    Sales organization
      header-sales_org = p_vkorg.
      headerx-sales_org = 'X'.
    Distribution channel
      header-distr_chan  = p_vtweg.
      headerx-distr_chan = 'X'.
    Division
      header-division = p_spart.
      headerx-division = 'X'.
      headerx-updateflag = 'I'.
    Partner data
    Sold to
      partner-partn_role = 'AG'.
      partner-partn_numb = p_sold.
      APPEND partner.
    Ship to
      partner-partn_role = 'WE'.
      partner-partn_numb = p_ship.
      APPEND partner.
    ITEM DATA
      itemx-updateflag = 'I'.
    Line item number.
      item-itm_number = '000010'.
      itemx-itm_number = 'X'.
    Material
      item-material = p_matnr.
      itemx-material = 'X'.
    Plant
      item-plant    = p_plant.
      itemx-plant   = 'X'.
    Quantity
      item-target_qty = p_menge.
      itemx-target_qty = 'X'.
      APPEND item.
      APPEND itemx.
      Fill schedule lines
      lt_schedules_in-itm_number = '000010'.
      lt_schedules_in-sched_line = '0001'.
      lt_schedules_in-req_qty    = p_menge.
      APPEND lt_schedules_in.
      Fill schedule line flags
      lt_schedules_inx-itm_number  = '000010'.
      lt_schedules_inx-sched_line  = '0001'.
      lt_schedules_inx-updateflag  = 'X'.
      lt_schedules_inx-req_qty     = 'X'.
      APPEND lt_schedules_inx.
    Call the BAPI to create the sales order.
      CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
           EXPORTING
                sales_header_in     = header
                sales_header_inx    = headerx
           IMPORTING
                salesdocument_ex    = v_vbeln
           TABLES
                return              = return
                sales_items_in      = item
                sales_items_inx     = itemx
                sales_schedules_in  = lt_schedules_in
                sales_schedules_inx = lt_schedules_inx
                sales_partners      = partner.
    Check the return table.
      LOOP AT return WHERE type = 'E' OR type = 'A'.
        EXIT.
      ENDLOOP.
      IF sy-subrc = 0.
        WRITE: / 'Error in creating document'.
      ELSE.
    Commit the work.
        COMMIT WORK AND WAIT.
        WRITE: / 'Document ', v_vbeln, ' created'.
      ENDIF.
    Regards,
    Dinesh

    what messages u are gettting in RETURN ? Please check the RETURN tables data.
    [code]CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
    EXPORTING
    sales_header_in = header
    sales_header_inx = headerx
    IMPORTING
    salesdocument_ex = v_vbeln
    TABLES
    return = return
    sales_items_in = item
    sales_items_inx = itemx
    sales_schedules_in = lt_schedules_in
    sales_schedules_inx = lt_schedules_inx
    sales_partners = partner.
    Regards
    Prabhu

  • FM for creation of production order creation

    Hi All,
    Can anyone tell me the BAPI for the production order creation.
    BAPI for creation of production order through CO01 transaction code.
    Thanks in advance
    Ramesh.

    Hi,
    Please check this FM CO_ZF_PRODUCTIONORDER_CREATE.
    Regards,
    Ferry Lianto

  • Selection Of BOM & Routing at the time of production order creation

    Hi guys,
    Please clarify how i can go about for the following mentioned scenario
    I have one Master BOM(Finished Product Level) & alternative BOMs for that,similarly i have one Master Routing & alternate routings for the same finished product
    At the time of production order creation is it possible for me to choose one of the BOMs & One of the routings of that particular finished product without creating a production version?
    Awaiting for a quick response
    Vijai

    Hi vijai prasad shanmugam ,
                                              In the material master MRP-4 view under the BOM selection you can maintain on what fatcors you want the BOM to be selected  Viz. Selection by order quant.,Selection by explosion date.Selection by production version etc.
    As far as the master recipe is concerned ........ I guess that if there are more than one valid master recipe maintained then SAP will prompt to select the one manually.........
    But it the standard practice to maintain the production version ....... for the similar situation to the one that you have mentioned.
    Please Let me know if I can help you in any way regarding this........
    Please reward the points......... in you find the ans helpful.....
    Thanks
    Kaushik

  • IDoc Configuration for Production Order Creation and Change

    Hi All,
    Please Help me out for IDoc Configuration for Production Order Creation and Change
    I have found the IDoc for Production Order
    Messgae Type : LOIPRO and IDoc type : LOIPRO01
    Actually my requirment is to send the (LOIPRO01 )IDoc from SAP R/3 to XI system ,when ever the Production Order Created and Changed,
    I have done following Configurations:
    1. RFC Destination created for XI system
    2. PORT was created for XI
    3. Partner profile created WE20 and LOIPRO01 IDoc is added in OutBound Perameter.
    I need to know how to do the followning.
    1. How do i configure the outbound Production order idocs when Production Order is created or changed.
    2. in NACE (Output control) which is the Application for Production Order.
    3. How can I set IDoc as output Type for Production Order Creation.
    Thanks in advance
    Dhanabal T

    Hi Michal,
    I know that it is the old thread but still want to get clarified from you out of curiosity.
    Unlike other IDOC, i actiavated change pointers for LOIPRO
    1.message and idoc type is linked
    2.function module , message type , idoc type is linked
    function module used is CLOI_MASTERIDOC_CREATE_LOIPRO
    3.BD64, distribution model is created and distributed
    4. port and partner profile is in place.
    5. IDOC is not getting generated after creating the process order.
    do we need to activate the change documents for the message type in BD52,
    if yes can you please provide the object types for the same.
    or i am missing something else. please guide me in this regards.
    Thanks in advance for your time.
    S.Janagar

  • Notify of Production Order Creation service

    The SDN WIKI for Integration of Manufacturing Execution Systems states that...
    "Now, as of Enhancement Package 4, each time a production order is created in SAP ERP, that action automatically invokes the Notify of Production Order Creation service operation, which informs the MES system of all the details of the new production order. "
    I am not able to locate any further documentation and definition of the Notify of Production Order Creation service.   Please provide assistance on where to find documentation of this service.

    Look at these links , may get some help ....
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/espackages/create%252bproduction%252bplanning%252border
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/espackages/find%252bproduction%252border%252bby%252belements
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/espackages/change%252bproduction%252border
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/espackages/find%252bproduction%252bplanning%252border%252bfor%252bapproval%252bby%252belements%252b(SCM)
    Regards
    Abhishek

  • Manual production order creation in MTO

    Dear collegues,
    I am stuck in a scenario:
    I have a finished item A. strategy 20 is used.I created sales order for A in plant 1000. MRP run in plant 1000 happens. Through special procurement key 40, system generates planned order in plant 2000. Planned order is converted to production order. I can see in assignment tab of production order,  Production plant is 2000 and planning plant is also 2000. Till here it is ok. I will do GR against production order in plant 2000 and through SD route I will send it to Plant 1000.
    But when I create manually production order in CO08, always system sets in assignment tab of Production order , production plant as plant 2000 and planning plant as 1000. How to avoid this? Why manual production order is not like MRP generated planned u2013production order?
    Kindly help.
    Regards.

    Give below a try in sandbox (Not from experience, so not sure if it works):
    At the time of production order creation, maintain the production plant in Sales Order & ensure the demand flow to MRP is switched off at schedule line (If you're not sure, take help of your SD person).
    The order created in CO08 should now have production & planing plant as same. Once that is done, switch back the plant in Sales Order & release the demand to MRP. (I hope the cut over plan has addressed the sales & MRP flows, so no inputs from my end)
    If the above does not work, then revert with details.

  • Blocking of production order creation

    Hi All,
    I need a help on blocking of production order creation.
    I have few materials for which deletion has been activated in material master. But for these materials, while creating production order it is allowing to create by showing some warning message. But I want to totally block creation of production order.
    Regards,
    Vijay

    Dear,
    Youneed to define for block for productio.OMS4 --> create new one material status (08) for "Blocked for Prod Order" and set the prodution.
    If u want plant specific block then do not use this indicator in basic data 1 view ,use it in purchasing alse and MRP view.
    Please check with Message No M7-127 at OMCQ. Here u can set error message
    IMG>MATERIAL MANAGEMENT>INVEN>DEFINE ATTRIBUTES FOR SYSTEM MESSAGES. message no M7127
    Change the warning message to error. Then create the production order and check.
    Or Archieve material by SARA
    Regards,
    R.Brahmankar

Maybe you are looking for