Creation of breakdown order

Hi,
Message no. CT608
During creation of breakdown order for equipment the screen gives error that scheduling parameters are to be entered for maintenance order.But i am not understanding why we should enter scheduling parameters when we are not creating preventive maintenance order ?

In this T-CODE why it is asking to enter production scheduler for entering scheduling parameter.And why we have to enter scheduling parameter in case of creation of breakdown order ? Please clear me this concept .In this case also when i am entering production scheduler as * then it is not giving error .
vivek

Similar Messages

  • Creation of breakdown order only from the breakdown notification

    Hi Experts,
    While creating the order from the notification client has requirement that user should able to create the breakdown order only from the breakdown notification and not from the any type of notification.
    Please guide me what are the configuration that I am missing or do I need to use any BAPI/FM for the above functionality.
    Warm regards,
    Parag

    Hi Parag,
    you can use following customizing setting:
    Plant Maintenance and Customer Service - Maintenance and Service Processing - Maintenance and Service Notifications - Notification Creation - Notification Types - Assign Notification Types to Order Types
    Here you can define the default order type for a notification type.
    Hope that helps.
    Regards,
    Patrick

  • HOW TO CONTROL ON CREATION OF SALES ORDER WITH REFERENCE TO EARLIER SO?

    Dear All,
    I want to contol on creation of Sales order with reference to earlier SO?  While creation of sales order our enduser are creating sales order with reference to earlier month SO which I want to restrict. Recently I made changes in sales order like payment terms is grayed, system will atomatically pick pay terms from customer master.Now I am getting correct data also but enduser is using old SO no while creating new SO and old payment data is reflecting in fbl5n.
    I want to restrict enduser while creating new SO with ref. to old SO. Only for returns they should be able to use Billing refrence. Pl. suggest how to control the with reference to ealier SO.
    Nikhil

    Nikhil Deshpande,
          If you dont want allow create a sales order in referent to other one, just delete the copy control between these sales order type, so when the user tries to create a SO in reference to other one a message is displayed that is not possible.
    Thanks,
    Mariano.

  • Automaticf creation of purchase order through pr

    Dear Consultants,
    system is not creating automatic  purchase order. in me59n i am getting the following error
    Requisition could not be converted
    i have done the following setting for automatic creation of purchase order
    1. in materil master record i have checked auto po.
    2. in vendor master record i have checked automatic purchase order
    3. i have created purchase info record with the combination of material vendor purchase organization.
    4. in source list i have fixed the vendor in me01
    5. in source determination under define regular vendor i have checked the box against the required plant.
    kindly let me know what all other configurations are required for creating automatic purchase order through purchase requisition
    Regards/ Siri

    Hi
    Is this purchase requisition created during MRP run??
    If yes then have you marked the sourcelist record for this vendor as MRP relevant??
    If the purchase requisition is generated manually then whether the source of supply was assigned in the PR??
    In ME59N, the PR would be converted to PO if the PR has the assigned source of supply.
    Regards
    Prasad

  • Issue with creation of sales order in CRM system

    Hi Experts,
    Here are the details of the process we followed
    1.     We found a Function Module u201CBAPI_BUSPROCESSND_CREATEMULTIu201D which is used to create a sales order in CRM.
    2.     We have set a Break point in the FM u201CCRM_ORDER_MAINTAINu201D and tried to create a sales order using the transaction u201CCRMD_ORDERu201D. For this the parameters we have given are
    a.     sold-to-party
    b.     ship-to-party
    c.     quantity
    d.     product
    And after this we have saved the order and the order is saved and in the debug mode we have the parameters in u201CCRM_ORDER_MAINTAINu201D and we found all these     parameters in the FM.
    3.     After this we have given all the parameters mentioned above in the FM u201CBAPI_BUSPROCESSND_CREATEMULTIu201D and still the order is not created, gave an error message saying that CRM_ORDER: Incorrect values in the interface object.
    4.     We checked the CRM_ORDER badiu2019s interface and it is having only header guid to be given. We gave this header guid also in the FM u201CBAPI_BUSPROCESSND_CREATEMULTIu201D and then it gave a different error saying that : Document cannot be saved.
    5.     Finally we are not able to know the parameters to be passed to the FM to create an order.
    Any inputs will be highly appreciated.
    Thanks a lot in advance.
    Lakshman.

    Hi Easwar,
    Now i am able to create a sales order by passing the parameters to "BAPI_BUSPROCESSND_CREATEMULTI" and the parameters i am passing are Process_type in the ORDERADM_H, parner_fct (partner function), partner_no , Quantity and prod_ordered (product name) but after creation of sales order using my report program and if i see the sales order uisng transaction crmd_order (using transaction ID) or crmd_orderadm_h(using headerguid) or crm_order_index, only the PROCESS_TYPE is updated but the remaining parameters which i passed like QUANTITY,PRODUCT NAME,PARTNER NUMBER are not present in the sales order. I am providing the code which i have written for creation of the sales order. Can you please look into it and tell me where i might have went wrong??
    *& Report  ZCREATEORDER_TEST
    REPORT  ZCREATEORDER_TEST.
    DATA : LV_HEADER_GUID  TYPE  GUID_32,
    WA_HEADER            TYPE         BAPIBUS20001_HEADER_INS,
    ITAB_HEADER          TYPE STANDARD TABLE OF BAPIBUS20001_HEADER_INS,
    ITAB_CREATED_PROCESS TYPE STANDARD TABLE OF BAPIBUS20001_HEADER_INS,
    ITAB_OBJECTS_TO_SAVE TYPE STANDARD TABLE OF BAPIBUS20001_GUID_DIS,
    ITAB_PARTNER        TYPE STANDARD TABLE OF BAPIBUS20001_PARTNER_INS,
    lt_product_i TYPE STANDARD TABLE OF BAPIBUS20001_ITEM,
    wa_product_i  type BAPIBUS20001_ITEM,
    lt_schedlin_i type standard table of BAPIBUS20001_SCHEDLIN,
    wa_schedlin_i type BAPIBUS20001_SCHEDLIN,
    ITAB_INPUT_FIELDS TYPE TABLE OF bapibus20001_input_fields,
    ls_inputfields TYPE bapibus20001_input_fields,
    WA_PARTNER          TYPE BAPIBUS20001_PARTNER_INS,
    ITAB_RETURN          TYPE STANDARD TABLE OF BAPIRET2,
    WA_OBJECTS_TO_SAVE  LIKE LINE OF ITAB_OBJECTS_TO_SAVE,
               "To store the Objects to be saved.
    WA_CREATED_PROCESS  LIKE LINE OF ITAB_CREATED_PROCESS,
    ITAB_SAVED_OBJECTS   TYPE STANDARD TABLE OF BAPIBUS20001_OBJECT_ID,
    WA_SAVED_OBJECTS    LIKE LINE OF ITAB_SAVED_OBJECTS,
    GC_X type c.
    gc_x = 'x'.
    CALL FUNCTION 'GUID_CREATE'
      IMPORTING
        ev_guid_32 = lv_header_guid.
    CLEAR : WA_HEADER.
    Passing the respective values from the Header table to internal table.
    WA_HEADER-GUID          =  LV_HEADER_GUID.
    WA_HEADER-PROCESS_TYPE  =  'ZTA'.
    APPEND WA_HEADER TO ITAB_HEADER.
    *Appending the values to the ITAB_HEADER.
    ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'ORDERADM_H'.
    ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'PROCESS_TYPE'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
    *ls_inputfields-ref_handle = '0000000000'.
    ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-objectname = 'ORDERADM_H'.
      ls_inputfields-fieldname = 'MODE'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
    ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'ORDERADM_H'.
    ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'GUID'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
    CHANGES MADE
    ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'SCHEDLIN'.
    ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'LOGICAL_KEY'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
      ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'SCHEDLIN'.
    ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'MODE'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
      ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'SCHEDLIN_I'.
    ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'GUID'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
       ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'SCHEDLIN_I'.
    ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'QUANTITY'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
       ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'SCHEDLIN_I'.
    ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'MODE'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
    CHANGES MADE
    WA_PARTNER-REF_GUID = LV_HEADER_GUID.
    WA_PARTNER-REF_KIND = 'A'.
    giving the partner function and partner no 000000038 for slod to party
    WA_PARTNER-PARTNER_FCT = '00000038'.
    WA_PARTNER-PARTNER_NO = '10017'.
    APPEND WA_PARTNER TO ITAB_PARTNER.
    *"ADDING VALUES for the product
      wa_product_i-header        = lv_header_guid.
      wa_product_i-handle        = '0000000001'.
      wa_product_i-ordered_prod  = '12000014'.
      wa_product_i-mode          = 'A'.
      APPEND wa_product_i TO lt_product_i.
    *"ADDING VALUES for quantity
      wa_schedlin_i-quantity   = 30.
      wa_schedlin_i-handle = 1.
      APPEND wa_schedlin_i TO lt_schedlin_i.
    ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'PARTNER'.
    *ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'REF_GUID'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
    ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'PARTNER'.
    ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'PARTNER_FCT'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
    ls_inputfields-ref_guid =  LV_HEADER_GUID.
    ls_inputfields-REF_KIND = 'A'.
    ls_inputfields-objectname = 'PARTNER'.
    ls_inputfields-logical_key = ' '.
    ls_inputfields-fieldname = 'PARTNER_NO'.
    APPEND ls_inputfields TO ITAB_INPUT_FIELDS.
    CALL FUNCTION 'BAPI_BUSPROCESSND_CREATEMULTI'
      TABLES
        HEADER          = ITAB_HEADER
        ITEM            = lt_product_i
        RETURN          = ITAB_RETURN
        PARTNER         = ITAB_PARTNER
        INPUT_FIELDS    = ITAB_INPUT_FIELDS
        CREATED_PROCESS = itab_created_process
        SCHEDULELINE    = lt_schedlin_i.
    READ TABLE ITAB_CREATED_PROCESS INTO WA_CREATED_PROCESS WITH KEY GUID = LV_HEADER_GUID BINARY SEARCH.
    WA_OBJECTS_TO_SAVE-GUID = WA_CREATED_PROCESS-GUID.
    Appending the Guid of the contract to be saved to the internal table
    APPEND WA_OBJECTS_TO_SAVE TO ITAB_OBJECTS_TO_SAVE.
    CALL FUNCTION 'BAPI_BUSPROCESSND_SAVE'
      EXPORTING
        update_task_local = space
        save_frame_log    = GC_X
      TABLES
        objects_to_save   = itab_objects_to_save
        saved_objects     = itab_saved_objects
        return            = itab_return.
    Calling the Standard BAPI to Commit the transcation.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    I have debugged the above code, all the values are passing are passing to the FM "'BAPI_BUSPROCESSND_CREATEMULTI'" and these passed to the CRM_ORDER_MAINTAIN and then to CRM_ORDER_READ which are called inside the "'BAPI_BUSPROCESSND_CREATEMULTI'". Finally the sales order is created but not able to see all the values that i am passing except PROCESS_TYPE.
    Thanks a lot in Advance,
    Lakshman.

  • Creation of Sales Order and Service Contract from Inbound IDOC

    Hi Experts,
    My requirement is to create a Sales Order as well as a Service Contract from one Inbound IDOC. I am getting the Inbound IDOC from a third Party. The message type is ORDERS and Basic Type is ORDERS02. How ever i am using an extension type IDOC which carries all the required data for Sales Order and Service Contract. My requirement is like, to create a Sales Order first.
    I have created a Z FM which is attached to the Process Code and subsequently to the message type. Inside the FM i an calling FM 'IDOC_INPUT_ORDERS' for creation of Sales Order. After that i am changing the IDOC data for the Document Type. I am changing the document type which is responsible for Contract Creation.
    Then I am again calling the FM 'IDOC_INPUT_ORDERS' for creation of Contract with the help of IDOC data. But here the Contract is not getting created. It's getting failed during the Batch input session.
    I need to solve this problem as soon as possible. Please help me. If there are any other options also please share.
    Thanks in Advance.
    Regards,
    Priyabrata

    Actually there is problem with BDCDATA. Inside the FM it's calling transaction with help of BDCDATA. If i am creating a Sales order or contract alone its creating successfully. But when i am trying to create both, it's retuning sy-subrc '1001' after calling the transaction on the second attempt. Is there any problem with BDCDATA like we can't handle with less time gap? Please help and give your inputs.
    Regards,
    Priyabrata

  • Creation of service order with address data.

    Hello community,
    I have the following requirement: create maintenance orders with order address data, the creation of these orders will be triggered by an interface with a legacy system.
    For order creation I intend to use BAPI_ALM_ORDER_MAINTAIN but this function does not provide the possibility to enter address information.
    I would not like to have to create a partner and assign it to the order as this address will be used only once.
    Does anyone have suggestions how to do it ?.
    Thanks.
    Roberto.

    Roberto,
    Try this:
    *& Report  ZPJA_ADDR_TX
    report  zpja_addr_tx.
    data: lt_adrc  type  standard table of adrc with header line.
    data: lt_adrc1 type  standard table of addr1_data with header line.
    * get address from first object
    call function 'ADDR_SELECT_ADRC_SINGLE'
      exporting
        addrnumber        = '0000033071'
      tables
        et_adrc           = lt_adrc
      exceptions
        address_not_exist = 1
        parameter_error   = 2
        internal_error    = 3
        others            = 4.
    loop at lt_adrc.
      move-corresponding lt_adrc to lt_adrc1.
      lt_adrc1-name1 = sy-timlo.   " write current time for testing
      append lt_adrc1.
    endloop.
    * update second address
    call function 'ADDR_UPDATE'
      exporting
        address_data        = lt_adrc1
        address_number      = '0000033205'
        date_from           = '00010101'
        language            = sy-langu
        check_empty_address = ' '
        check_address       = ' '
      exceptions
        address_not_exist   = 1
        parameter_error     = 2
        version_not_exist   = 3
        internal_error      = 4
        others              = 5.
    call function 'ADDR_MEMORY_SAVE'.

  • !How to find out follow up activities created during creation of an Order??

    Hi Gurus,
    I want to find out the number of follow up activities created during creation of an Order??
    Is there any BAPI or Function Module which can detrmine the number of follow up activities after creation / saving an Order..
    Please Reply fast.
    Thanks
    Pranay

    Hi Pranav,
    I am confident this will solve your problem:
    <b>Step 1.</b>
    Enter the guid of the current order into function module
    CRM_DOC_FLOW_READ_DB.
    Code:
    DATA : t_doc_links TYPE crmt_doc_flow_db_wrkt,
               v_guid TYPE crmt_object_guid.
    v_guid = <guid of the order from table crmd_orderadm_h>
    CALL FUNCTION 'CRM_DOC_FLOW_READ_DB'
                  EXPORTING
                    iv_header_guid = v_guid
                  IMPORTING
                    et_doc_links   = t_doc_links
                  EXCEPTIONS
                    error_occurred = 1
                    OTHERS         = 2.
    <b>Step2.</b>
    Now loop through the returned table ie t_doc_links.
    Records which fulfill the following criteria are
    the follow up records.
      reltype    = 'VONA'
      objtype_b  = 'BUS2000126'
      objkey_b   =  v_temp
      roletype_b = 'NACHFOLGER'
      roletype_a = 'VORGAENGER'.
    <b>Step:3</b>
    Now Count the records which fulfill the above creteria.
    This count represent the number of followups created.
    <b>REWARD THE ANSWER WITH FULL 10 POINTS IF UR PROBLEM IS SOLVED.</b>
    thanks,
    ashish.

  • Blocking RdA creation from Sales Order Schedule Line

    Hi Gurus,
    please do you know if there is a way to block the RdA creation from Sales Order schedule line, for TAS item category? I tried with Header Delivery block without quantity confirmation but even if quantity on schedule lines are not confirmed, RdA is created anyway.
    Thank you very much
    Kind Regards
    Andrea

    thank you

  • Regularly auto creation of sales order

    Hi All,
    Is it possible to define or set auto creation of sales order ? e.g. there 2000 customers that every biweekly Monday will have sales orders created automatically by system, so the user just only see and copy to delivery or A/R invoice. TIA
    Rgd,
    Mark

    This can be performed if you use activity management and set sales quotation as a linked document. use one sales quotation but contains multiples row line of items that have different delivery dates can make it possible, but only as reminder, to create sales order,.although manually, you just use copy to and the add the SO. You could also develop addon to make SBO auto creation of sales order.
    Rgds,

  • Va01 creation of sales order

    Hi
    can i create sub screen  in creation of sales order item
    in user exit mv45afzz
    my requirement is when user click on any line item than than i need to call subscreen with some information
    pls guide me on this

    HI
    <b>
    Sales realated exits</b>
    SDTRM001 Reschedule schedule lines without a new ATP check
    V45A0001 Determine alternative materials for product selection
    V45A0002 Predefine sold-to party in sales document
    V45A0003 Collector for customer function modulpool MV45A
    V45A0004 Copy packing proposal
    V45E0001 Update the purchase order from the sales order
    V45E0002 Data transfer in procurement elements (PRreq., assembly)
    V45L0001 SD component supplier processing (customer enhancements)
    V45P0001 SD customer function for cross-company code sales
    V45S0001 Update sales document from configuration
    V45S0003 MRP-relevance for incomplete configuration
    V45S0004 Effectivity type in sales order
    V45W0001 SD Service Management: Forward Contract Data to Item
    V46H0001 SD Customer functions for resource-related billing
    V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
    V46H0001 SD Customer functions for resource-related billing
    V45W0001 SD Service Management: Forward Contract Data to Item
    V45S0004 Effectivity type in sales order
    V45S0003 MRP-relevance for incomplete configuration
    V45S0001 Update sales document from configuration
    V45P0001 SD customer function for cross-company code sales
    V45L0001 SD component supplier processing (customer enhancements)
    V45E0002 Data transfer in procurement elements (PRreq., assembly)
    V45E0001 Update the purchase order from the sales order
    V45A0004 Copy packing proposal
    V45A0003 Collector for customer function modulpool MV45A
    V45A0002 Predefine sold-to party in sales document
    V45A0001 Determine alternative materials for product selection
    SDTRM001 Reschedule schedule lines without a new ATP check
    SDAPO001 Activating Sourcing Subitem Quantity Propagation
    https://www.sdn.sap.com/irj/sdn/wiki
    Check this link
    Sail

  • Restrict creation of sales order for specific customer

    Hello All,
    I want to restrict creation of sales order (of particular sales order type) for specific customer, please let me know how can I do it.
    Your early reply will be highly appreciated.
    Thanks & Regards,
    Mahavir

    HI
    As per My knowledge it is not possible in Standard SAP , you need to go with Enhancement
    Go to SE38 : MV45AFZB, User Exit: USEREXIT_CHECK_VBAK
    Regards,
    Prasanna

  • Creation of sales order- screen exit

    Hi all,
    I have a requirement like while creation of sales order need to develop one screen field in additional data B.i developed that field. and now while creation of sales order it will save in vbak table. now the problem is that screen field will be enable in that particular sales order type only otherwise it will be disable. how to do this. screen exit.

    Hi
    See SAP Note 209278 - Display of customer-specific fields in sales doc
    Check also, SAP Note 302497 - Additional cust. fields not displayed in 'Additional data B' and SAP Note 386694 - Additional data not displayed in screen 8459 and 8309
    Regards
    Eduardo

  • Creation of sales order through Purchase order

    Hi all
    We have a special scenario in creation of Sales order with the help of purchase order,
    Could you please advice me how we can create sales order with the help of purchase order.
    Thank YOu
    Swaroop

    you can create the sales order from the purchase order.It can be achieved by Idocs.
    Please maintain the condition record for the output medium EDI and also maintain the Partner profile in WE20.

  • Creation of sales order with reference to inquiry no.

    Hi gurus!
    Im having trouble in creation of sales order with reference to inquiry no. The scenario is like this one. In va11(creation of inquiry no.), in the field of <b>SERVICE LEVEL</b>, i indicated a value. after the creation of inquiry no, i want to create a sales order with reference to inquiry no. But the problem is, the <b>SERVICE LEVEL</b> field does not have any value. What is the main problem to this scenario? is it the VARIANT CONFIG or the program itself? please help its urgent
    Regards,
    Mackoy

    Dear Machoy,
    In IMG under
    Sales and Distribution -> Sales -> Sales Documents -> Maintain Copy Control for Sales Documents -> Copying Control: Sales Document to Sales Document
    or Transaction VTAA
    http://help.sap.com/erp2005_ehp_02/helpdata/en/70/a7853478616434e10000009b38f83b/frameset.htm
    If you create a sales document with reference to a preceding document, the system copies nearly all the data from the preceding document. The data in the preceding document originally comes from the customer and material master records. Because the data is copied from the preceding documents into the sales document, any changes that have been made to the master data records since the preceding document was created are not included in the sales document. If, when you create with reference, you add another item to the document that was not in the preceding document, the system determines the data for it from the master records, such as the material master or info record.
    You have created an inquiry and a quotation with reference to this inquiry. Before you created the quotation, you changed some data in the material and customer master records.
    You have changed the material description in the material master record. This description is stored in the sales document at item level.
    You have changed the terms of payment in the customer master record from ZB01 to ZB03. These are stored in the sales document at header level.
    When you created the inquiry, the system copies the original material description to the item. If you enter another item in the quotation for the same material, the system displays the new material description for the new item.
    However, the system continues to propose the original term of payment, that is, ZB01, for all items including the new one. This is because it is copied from the header of the preceding document into the header of the quotation, and the change in the customer master record has no affect on the quotation.
    Regards,
    Naveen.

Maybe you are looking for