Problem _Purchase order creation

Dear all,
i am getting Error message appears u201Cmaterial XXX  hasnu2019t quality assurance agreementu201D during Purchase order creation.
But QIR is available for material with the combination of plant and vendor  and release date also 2012
Kindly let me know
Why system require QIR at the time of creation of purchase order or i have made any wrong entry in the system if yes please suggest me
Rgds

hello,
1)Check Material is having correct inspection type in QM View of material master
2) Check Quality Inforecord is having correct release date
3) Check Purchase inforecord and their validity dates.
4) Check Quality Inforecord status.
Regards
Mahesh Naik.

Similar Messages

  • Problem in order creation

    While i am going to create an order on a particular equipment then a message is coming as:-
    Activity type 106050 for cost center 11035202 in the fiscal year 2012 not valid.Why is it coming?
    Any help greatly appreciated.

    Hi,
    The reason for this message is that the activity rates are not yet defined for the year 2012. Have your CO guy create entries in KP26 for the combination of activity type and rate for year 2012.
    Hope this helps.
    regards,
    Srinivas Potluri

  • 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

  • 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

  • Problem submitting batch request for sales order creation

    Hello experts,
    I have created a gateway service, implementing the CREATE_DEEP_ENTITY for order creation. I have tested my service with the Chrome Advanced Rest Client and it works fine with the following XML request:
    <?xml version="1.0" encoding="UTF-8"?>
    <atom:entry xmlns:atom="http://www.w3.org/2005/Atom" xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
      <atom:content type="application/xml">
      <m:properties>
      <d:OrderId>0</d:OrderId>
      <d:DocumentType>TA</d:DocumentType>
      <d:CustomerId>C6603</d:CustomerId>
      <d:SalesOrg>S010</d:SalesOrg>
      <d:DistChannel>01</d:DistChannel>
      <d:Division>01</d:Division>
      <d:DocumentDate m:null="true" />
      <d:OrderValue m:null="true" />
      <d:Currency m:null="true" />
      </m:properties>
      </atom:content>
      <atom:link rel="http://schemas.microsoft.com/ado/2007/08/dataservices/related/SOItems" type="application/atom+xml;type=feed" title="SALESORDERTSCH.SOHeader_SOItems">
      <m:inline>
      <atom:feed>
      <atom:entry>
      <atom:content type="application/xml">
      <m:properties>
      <d:OrderId>0</d:OrderId>
      <d:Item>000010</d:Item>
      <d:Material>C20013</d:Material>
      <d:Plant m:null="true" />
      <d:Quantity m:Type="Edm.Decimal">100.000</d:Quantity>
      <d:Description m:null="true" />
      <d:UoM m:null="true" />
      <d:Value m:null="true" />
      </m:properties>
      </atom:content>
      </atom:entry>
      <atom:entry>
      <atom:content type="application/xml">
      <m:properties>
      <d:OrderId>0</d:OrderId>
      <d:Item>000020</d:Item>
      <d:Material>C20014</d:Material>
      <d:Plant m:null="true" />
      <d:Quantity m:Type="Edm.Decimal">200.000</d:Quantity>
      <d:Description m:null="true" />
      <d:UoM m:null="true" />
      <d:Value m:null="true" />
      </m:properties>
      </atom:content>
      </atom:entry>
      </atom:feed>
      </m:inline>
      </atom:link>
    </atom:entry>
    Now that my service is working, I want to be able to call it from a SAP UI5/Javascript application. In order to process multiple items for one order header, I use the OData batch request. Here is my Javascript method that is being processed:
    executeOrderCreation : function() {
      // Retrieve model from controller
      var oModel = sap.ui.getCore().getModel();
      oModel.setHeaders(
      { "Access-Control-Allow-Origin" : "*",
      "Content-Type": "application/x-www-form-urlencoded",
      "X-CSRF-Token":"Fetch" }
      // Define data to be created
      var headerData = {
      OrderId : "0",
      DocumentType: "TA",
      CustomerId : "C6603",
      SalesOrg : "S010",
      DistChannel : "01",
      Division : "01",
      DocumentDate : null,
      OrderValue : null,
      Currency : null,
      varItemData1 = {
      OrderId : "0",
      Item : "000010",
      Material : "C20013",
      Plant : null,
      Quantity : "100.000",
      Description :null,
      UoM :null,
      Value :null,
      varItemData2 = {
      OrderId : "0",
      Item : "000020",
      Material : "C20014",
      Plant : null,
      Quantity : "100.000",
      Description :null,
      UoM :null,
      Value :null,
      var batchChanges = [];
      oModel.refreshSecurityToken(function(oData, oResponse){
      alert("Refresh token OK");
      }, function() {
      alert("Refresh token failed");
      }, false);
      oModel.read('/SOHeaders/?$Batch', null, null, false, function(oData, oResponse) {
      // Create batch data
      batchChanges.push(oModel.createBatchOperation("SOHeaders", "POST",headerData ));
      batchChanges.push(oModel.createBatchOperation("SOHeaders", "POST",varItemData1 ));
      batchChanges.push(oModel.createBatchOperation("SOHeaders", "POST",varItemData2 ));
      oModel.addBatchChangeOperations(batchChanges);
      // Submit changes and refresh the model
      oModel.submitBatch(
      function(oData) {
      oModel.refresh();
      function(oError) {
      var error = oError;
      alert("Read failed" + error);
      false);
      }, function() {
      alert("Read failed");
    The result is when I submit the batch, I have an error saying: The following problem occurred: no handler for data -
    Am I doing right in the batchChanges creation ? (Header then items)
    Why am I facing this error ?
    Any help would be greatly appreciated.
    Thanks and regards,
    Thibault

    Hi,
    you should also have '/' before collection name so that it will be /SOHeader and as below.
      batchChanges.push(oModel.createBatchOperation("/SOHeaders", "POST",headerData ));          batchChanges.push(oModel.createBatchOperation("/SOHeaders", "POST",varItemData1 )); 
      batchChanges.push(oModel.createBatchOperation("/SOHeaders", "POST",varItemData2 ))
    Regards,
    Chandra

  • Have a Problem in EAM work order creation API........

    I have used the following code to create work order but i was unable to do so
    I am getting return status SUCCESS(S)....
    but am unable to view the record in EAM_WORK_ORDERS_V..
    any sort of help would be appreciated...
    declare
    g_eam_wo_relations_tbl0 eam_process_wo_pub.eam_wo_relations_tbl_type;
    g_eam_wo_relations_rec eam_process_wo_pub.eam_wo_relations_rec_type;
    g_eam_op_rec0 eam_process_wo_pub.eam_op_rec_type;
    g_eam_op_rec1 eam_process_wo_pub.eam_op_rec_type;
    g_eam_op_network_rec0 eam_process_wo_pub.eam_op_network_rec_type;
    g_eam_op_network_rec1 eam_process_wo_pub.eam_op_network_rec_type;
    g_eam_mat_req_rec0 eam_process_wo_pub.eam_mat_req_rec_type;
    g_eam_mat_req_rec1 eam_process_wo_pub.eam_mat_req_rec_type;
    g_eam_di_rec0 eam_process_wo_pub.eam_direct_items_rec_type;
    g_eam_di_rec1 eam_process_wo_pub.eam_direct_items_rec_type;
    g_eam_res_rec0 eam_process_wo_pub.eam_res_rec_type;
    g_eam_res_rec1 eam_process_wo_pub.eam_res_rec_type;
    g_eam_res_inst_rec0 eam_process_wo_pub.eam_res_inst_rec_type;
    g_eam_res_inst_rec1 eam_process_wo_pub.eam_res_inst_rec_type;
    g_eam_op_tbl0 EAM_PROCESS_WO_PUB.eam_op_tbl_type;
    g_eam_op_tbl1 EAM_PROCESS_WO_PUB.eam_op_tbl_type;
    g_eam_op_network_tbl0 EAM_PROCESS_WO_PUB.eam_op_network_tbl_type;
    g_eam_res_tbl0 EAM_PROCESS_WO_PUB.eam_res_tbl_type;
    g_eam_res_inst_tbl0 EAM_PROCESS_WO_PUB.eam_res_inst_tbl_type;
    g_eam_sub_res_tbl0 EAM_PROCESS_WO_PUB.eam_sub_res_tbl_type;
    g_eam_res_usage_tbl0 EAM_PROCESS_WO_PUB.eam_res_usage_tbl_type;
    g_eam_mat_req_tbl0 EAM_PROCESS_WO_PUB.eam_mat_req_tbl_type;
    g_eam_di_tbl0 EAM_PROCESS_WO_PUB.eam_direct_items_tbl_type;
    g_out_eam_wo_relations_tbl eam_process_wo_pub.eam_wo_relations_tbl_type;
    g_out_eam_wo_rec eam_process_wo_pub.eam_wo_rec_type;
    g_out_eam_wo_tbl eam_process_wo_pub.eam_wo_tbl_type;
    g_out_eam_op_tbl EAM_PROCESS_WO_PUB.eam_op_tbl_type;
    g_out_eam_op_network_tbl EAM_PROCESS_WO_PUB.eam_op_network_tbl_type;
    g_out_eam_res_tbl EAM_PROCESS_WO_PUB.eam_res_tbl_type;
    g_out_eam_res_inst_tbl EAM_PROCESS_WO_PUB.eam_res_inst_tbl_type;
    g_out_eam_sub_res_tbl EAM_PROCESS_WO_PUB.eam_sub_res_tbl_type;
    g_out_eam_res_usage_tbl EAM_PROCESS_WO_PUB.eam_res_usage_tbl_type;
    g_out_eam_mat_req_tbl EAM_PROCESS_WO_PUB.eam_mat_req_tbl_type;
    g_out_eam_di_tbl EAM_PROCESS_WO_PUB.eam_direct_items_tbl_type;
    g_eam_wo_rec1 eam_process_wo_pub.eam_wo_rec_type;
    g_eam_wo_rec2 eam_process_wo_pub.eam_wo_rec_type;
    g_eam_wo_tbl0 eam_process_wo_pub.eam_wo_tbl_type;
    g_eam_wo_res_usg_tbl0 eam_process_wo_pub.eam_res_usage_tbl_type;
    l_return_status VARCHAR2(1);
    l_msg_count NUMBER;
    g_eam_wo_usg_rec1 eam_process_wo_pub.eam_res_usage_rec_type;
    g_eam_wo_usg_rec2 eam_process_wo_pub.eam_res_usage_rec_type;
    begin
    g_eam_wo_rec1 := null;
    g_eam_wo_rec1.transaction_type := EAM_PROCESS_WO_PVT.G_OPR_CREATE;
    g_eam_wo_rec1.batch_id := 1;
    G_EAM_WO_REC1.HEADER_ID := 1;
    G_EAM_WO_REC1.WIP_ENTITY_ID := NULL;
    g_eam_wo_rec1.wip_entity_name := '10040';
    g_eam_wo_rec1.organization_id := 207;
    g_eam_wo_rec1.asset_group_id := 16884;
    g_eam_wo_rec1.asset_number := '28Z1933';
    g_eam_wo_rec1.rebuild_item_id := null;
    g_eam_wo_rec1.rebuild_serial_number := null;
    G_EAM_WO_REC1.MAINTENANCE_OBJECT_SOURCE := 1;
    g_eam_wo_rec1.maintenance_object_type := 3;
    g_eam_wo_rec1.maintenance_object_id := 1768219;
    g_eam_wo_rec1.parent_wip_entity_id := null;
    g_eam_wo_rec1.manual_rebuild_flag := null;
    g_eam_wo_rec1.owning_department := 4002 ;
    g_eam_wo_rec1.description := 'Creating a Released Work Order';
    g_eam_wo_rec1.class_code := 'MAINT';
    g_eam_wo_rec1.status_type := wip_constants.released;
    g_eam_wo_rec1.date_released := sysdate-100;
    g_eam_wo_rec1.firm_planned_flag := 1;
    g_eam_wo_rec1.scheduled_start_date := sysdate;
    g_eam_wo_rec1.requested_start_date := sysdate;
    g_eam_wo_rec1.scheduled_completion_date := sysdate;
    g_eam_wo_rec1.material_issue_by_mo := 'N';
    g_eam_wo_rec1.priority := 10;
    g_eam_wo_rec1.issue_zero_cost_flag := 'Y';
    g_eam_wo_rec1.po_creation_time := 1;
    g_eam_wo_rec1.job_quantity := 1;
    g_eam_wo_rec1.notification_required := 'N';
    g_eam_wo_tbl0(1) := g_eam_wo_rec1;
    EAM_PROCESS_WO_PUB.PROCESS_WO
    ( p_bo_identifier => 'EAM'
    , p_api_version_number => 1.0
    , p_init_msg_list => TRUE
    , p_commit => 'Y'
    , p_eam_wo_rec => g_eam_wo_rec1
    , p_eam_op_tbl => g_eam_op_tbl0
    , p_eam_op_network_tbl => g_eam_op_network_tbl0
    , p_eam_res_tbl => g_eam_res_tbl0
    , p_eam_res_inst_tbl => g_eam_res_inst_tbl0
    , p_eam_sub_res_tbl => g_eam_sub_res_tbl0
    , p_eam_res_usage_tbl => g_eam_res_usage_tbl0
    , p_eam_mat_req_tbl => g_eam_mat_req_tbl0
    , p_eam_direct_items_tbl => g_eam_di_tbl0
    , x_eam_wo_rec => g_eam_wo_rec2
    , x_eam_op_tbl => g_out_eam_op_tbl
    , x_eam_op_network_tbl => g_out_eam_op_network_tbl
    , x_eam_res_tbl => g_out_eam_res_tbl
    , x_eam_res_inst_tbl => g_out_eam_res_inst_tbl
    , x_eam_sub_res_tbl => g_out_eam_sub_res_tbl
    , x_eam_res_usage_tbl => g_eam_res_usage_tbl0
    , x_eam_mat_req_tbl => g_out_eam_mat_req_tbl
    , x_eam_direct_items_tbl => g_out_eam_di_tbl
    , x_return_status => l_return_status
    , x_msg_count => l_msg_count
    , p_debug => 'Y'
    , p_output_dir => '/sqlcom/log/lv115dyp'
    , p_debug_filename => 'eambo22.log'
    , p_debug_file_mode => 'w'
    dbms_output.put_line('work order creation status:'||l_return_status);
    commit;
    END;
    thanks in advance
    DEV

    You have opened the render engine, not the full program.
    Mylenium

  • Purchase order Creation Problem

    Dear All
                  For Local purchase NB order creation SAP Asking the Account assignement category.
    for only particular plant ,It should ask only Service orders. but why its asking the NB orders.
         Even Valuation grouping code already assigned for that plant.
    Any other settings required..
    Please guide..
    Regards
    Kumnar

    Dear All
    For Local purchase NB order creation SAP Asking the Account assignement category.
    for only particular plant ,It should ask only Service orders. but why its asking the NB orders.
    Even Valuation grouping code already assigned for that plant.
    "System Throughout the error "Account assignment mandatory for the material 200011"
    The material type is verp. and accounting view already extented for this plant
    Any other settings required..
    Please guide..
    Regards
    Kumnar

  • Planned order creation problem

    Hello everybody,
    When I am creating a planned order manually in MD11, I receive the message "Planned order xxxxx will be created".
    Then I receive a popup window telling me "Express document 'Update was terminated' ".
    But, when I am having a look in MD04 to see the planned order, I can't see it.
    It was still okay yesterday morning, but since yesterday afternoon, no more planned orders can be created manually. Do you have an idea about what can be the reason of this?
    It's just like if the order creation was delayed... But for how long, and waiting for what???
    Thanks in advance for your help.
    Regards,
    Rudy

    Hi,
    There is something issue with ur data while saving..hence it is not saving and throwing the message. so that while upadting data in table  is not acccepting.
    GOTO SM14->click on ALL UPDATEREQUESTS push button->U will find the reocrds,select ur userid and double click on it,now u can see the module name,select it and double click on it,now u will get one small dialog box,there u can find the abap editor symbol ,click on it..it will take u to the program where it has taken place
    Please refer this thread,
    Update was terminated
    Regards,
    R.Brahmankar

  • Rework Order Creation Problem

    Hi,
    I have created trigger point in routing. I have also maintained the scheduling parameters for new order type for rework order. When trigger activates during confirmation it goes to the Rework order creation screen but gives the message of
    "Scheduling parameters are not defined for production orders"
    It is not picking the parameters.
    Regards
    HHS

    Plz also check the assigned rework workcente to the operation.
    Apart from order type scheduling parament .You have to consider the master too.Plz check and let us know

  • Problem with Sales Order Creation

    Hi,
    In my sales order creation program if item qty is zero, it should not include that item in the order. It is not working properly with this example it is creating same order for customer 1001 and 1004. It is checking for qty = 0 condition and executing 'continue' statememt , then it is not checking 'At end of kunnr' and creating only one order for all the remaining 4 items from 1001 and 1004 other than 0 qty's.
    kunnr   matnr   qty     order#
    1001     51038     723     102255
    1001     51054     0
    1001     51055     0
    1004     51038     207     102255
    1004     51054     236     102255
    1004     51055     219     102255
    it should create like this.
    kunnr   matnr   qty     order#
    1001     51038     723     102255
    1001     51054     0
    1001     51055     0
    1004     51038     207     102256
    1004     51054     236     102256
    1004     51055     219     102256
    Please help me fix this.
    Thanks,
    veni.

    Hi,
    Here is the code.
    WHEN 'ORDERS'.
          DESCRIBE TABLE gt_zprice LINES lv_cnt.
          DO lv_cnt TIMES.
            lv_index = sy-index + 4.
            READ LINE lv_index FIELD VALUE chbox.
            IF chbox = 'X'.
              READ TABLE gt_zprice INTO gs_zprice1 INDEX sy-index.
              IF sy-subrc EQ 0.
                gs_zprice1-index = sy-index.
                APPEND gs_zprice1 TO gt2_zprice.
                CLEAR gs_zprice1.
              ENDIF.
            ENDIF.
            CLEAR chbox.
          ENDDO.
          gt4_zprice[] = gt2_zprice[].
         SORT gt4_zprice BY kunnr vtweg.
          LOOP AT gt4_zprice INTO gs_zprice1.
            IF gs_zprice1-crmemo IS INITIAL.
              AT NEW kunnr.
                MOVE 'Y' TO lv_flg.
              ENDAT.
              IF lv_flg EQ 'Y'.
                PERFORM headerdata.
                PERFORM texts.
                CLEAR lv_flg.
              ENDIF.
              IF gs_zprice1-eohqty IS INITIAL.
                CONTINUE.
              ENDIF.
              PERFORM itemdata.
              APPEND gs_zprice1 TO gt3_zprice.
              CLEAR gs_zprice1.
              AT END OF kunnr.
                PERFORM call_function.
                PERFORM update_pricetable.
                PERFORM errorcheckandcommit.
                REFRESH gt2_zprice.
                CLEAR chbox.
                REFRESH partner.
                REFRESH item.
                REFRESH itemx.
                REFRESH lt_schedules_in.
                REFRESH lt_schedules_inx.
                REFRESH conditions1.
                REFRESH order_text.
                lv_itemno = 10.
              ENDAT.
            ELSE.
              REFRESH gt2_zprice.
              CLEAR chbox.
            ENDIF.
          ENDLOOP.
          WRITE: /01(179) sy-uline.
          PERFORM headings.
          WRITE: /01(179) sy-uline.
          PERFORM displaydata.
      ENDCASE.
    Thanks,
    Veni.

  • Work Order Creation Time

    Hi Guys
    I need a help with a problem here
    Our maintenance guys work in 3 different shifts. We would like to get a report about the workload in each shift
    I was wondering if its possible to get a list of orders with the creation time of each order.
    How can I get this info? The work order creation time?
    Thanks and Regards

    Transaction IW38 will give you a list based on the the date created you would need to create a varaint with a list of the user ID's that belong in each of the 3 shiftes this would then give a report of the orders created by Shift on any given day.
    Alternatively if you wanted to find out the orders on a weekly basis this could be done using the user ID's with a period of time over a week for instance.
    Hope this helps
    Jim

  • Want to change item category at the time of order creation

    Hi Gurus,
    Client require to implement individual PO scenario.
    I was configured the same and working fine.
    I am facing problem at the time of item category determination.
    User using same material and order type and they are not ready to accept to create new order type.
    Now My order type is OR and item category group is NORM and right now system determine item category TAN.
    User not want to change manually at the time of order creation.
    I have specific condition on which i want to apply this logic.
    Now i want to determine TAB item category through some user exits or enhancement.
    Can anyone suggest exact in which user exit or enhancement i have to change.
    Thanks & Regards,
    Chirag

    1. Use TCode 0VVW for creating a Z Item Usage, say, ZPO1
    2. Do an item Cat determination in VOV4, as
    Sales Doc type
    Item Cat Group
    Usage
    Item Category
    OR -
    NORM -
    ZPO1 -
    TAB
    3. Maintain Customer Materials Info Record by using VD51.
    In item screen for Cust-Mat combination maintain Item usage
    Regards
    JP

  • Return Order creation referanace to billing document.

    Hi , Experts,
                   I have one issue regarding return process , Pls do the needful ASAP.
    My question : I have created one direct sales order , After thet i have created PGI & billing , But after created billing document , I want to take return taht goods, So i had created return for same sales order quantity, & also created credit memo. But my problem is, that system allow me futher create return sales order with referance to billing document no. At a return order creation time system only give warning message - (There are already returns for item 000010: 2 EA)
    & allow to save return document no. But i want to erroe message after take return all billing quantity. Can any body suggest me, what is the customizing require for this,
    Thanks a lot in advance.
    Regards;
    Happy

    Hi, abdul sir,
                     Here no any error message, My problem is that , why all line item comes in delivery, B'cause i had already deliver 5 line item out of 10 item, Here system take delivered line item with 0 quantity, I don't want that delivered  line item at a time in delivery,
    Regards:
    Happy

  • How to trigger an Idoc from Sales order creation and change

    We are trying to trigger Idoc from sales order creation and change we have done following setting mentioned below:
    Follow the below steps:
    1. Go to NACE transaction
    2. Select V1 application and select OUTPUT TYPES
    3. Select the required output type and double click on Processing routines.
    4. Enter Medium as DISTRIBUTION ALE, Program as RSNASTED and Routine as ALE_PROCESSING.
    5. Save it.
    message type ORDERSP in the distribution model (BD64).
    Follow the below steps to configure the condition records:
    1. Go to NACE
    2. Select V1 application and select CONDITION RECORDS
    3. Select the requred output type and click on Condition records
    4. Selection screen will be displayed.
    5. Go for execution. In that screen enter the selection criteria. For eg Condition record is based on Sales document type. Then
    Sales doc type = OR
    Funt = SP
    Partner = blank. It means there is no restriction on partner numbers.
    Medium = A
    date/time = 4
    Lan = EN.
    Note: partner is left blank means, the sales order of type OR can be send to all partners.
    6. Save it.
    We also done ALE configuration.
    We are facing problem that from VA02 "No output has been selected for printing Message no. V1102"
    Kindly suggest the solution.
    Regards,
    Sharad Dixit

    Hi ,
    Please check the total error description and diagnosis as below :
    InVa02 enter SO  go to extras->output->Header->edit.You can find a table with all the triggered output types. Choose the output type BA00 with medium Distribution ALE and go for 'Processing log'. It will show you the error description.
    Please paste the diagnosis .
    Thanks and Regards,
    P.Bharadwaj

  • User Exit during Sales Order Creation - New Line Item needed

    I have a situation during the process of sales order creation. If a Material in a line item has say 27 EA and the Base Unit is EA. But the Sales Unit is CSE. Then whenever the user enters 27 EA and presses enter he should get two line items.
    The first line item needs to convert to maximum number of CSE posible and the rest will be the second line item with the remaining EA. The order isn't important but that is what is needed. Question is how do I approach this problem and code my user exit accordingly and where do I code it.
    I was looking at SAPMV45A and saw the program MV45AIZZ which is meant as a user exit for any PAI event handling. If anybody has encountered this kind of requirement can you please share your view on this.
    I will definitely reward points for useful answers.
    Clark

    Hello Mahendra
    The requirement is as follows :
    PART 1:
    Sales Order Enter: 
    1.     When a line item is entered on a sales order (VA01 or VA02), at enter, check the sales unit of measure (VBAP-VRKME).
    •     Do not check line items where item category (VBAP-PSTYV) = TANN, TAPS or ZTAP.  TANN are free goods that should not be considered for consolidation.  TAPS & ZTAP are lower level materials as a result of product selection.  They will be attached to a higher-level material with an item category of TAX, which is relevant for consolidation.
    •     Do not check items where VRKME <> EA
    2.     If VRKME = EA, go to MARM for MATNR.
    3.     Go to record where alternate unit of measure (MEINH) = CSE, get the value from the numerator field (UMREZ).
    4.     Divide the order quantity (VBEP-WMENG) by UMREZ.
    5.     If the result is greater than 1.0, the customer has ordered more than one case and a new line item needs to be added to the sales order for the case quantity.
    6.     Add a new line to VBAP for the same material with the case quantity.  If not a whole value, the remainder of eaches (bottles) should update the qty on the first item on VBAP.
    •     Part 1 is relevant for order types ZCA, ZOR, ZSO, RE, ZSM
    PART 2:
    Batch Job to run prior to the Delivery Due List:
    1.     Read VBUK for Delivery Status (LFSTK) = A (delivery not processed).  Get all of the document numbers (VBELN).
    2.     Go to VBEP for those document numbers to get the goods issue date for the order.  There will be many records in VBEP for the same sales order.  Look at all orders with a goods issue date (WADAT) of next day.
    3.     Go to VBAK for those document numbers to see if there are multiple sales orders for the same Sold To party (KUNNR).
    4.     For customers who have more than one order in VBAK, search all line items (for all orders).  If there are no duplicate materials across sales orders, do nothing.
    •     Do not check line items where item category (VBAP-PSTYV) = TANN, TAPS or ZTAP.  TANN are free goods that should not be considered for consolidation.  TAPS & ZTAP are lower level materials as a result of product selection.  They will be attached to a higher-level material with an item category of TAX, which is relevant for consolidation.
    •     Do not check line items where reason for rejection (VBAP-ABGRU) is not blank
    5.     If there are duplicate materials, go through the same logic as in part 1.  If the quantity across the sales orders adds up to greater than one case, add the appropriate quantity to a new line item on the first sales order.   If there is a remainder qty, update the line item on the first sales order with this qty. In this case, the quantities on the second sales order needs to be closed out with a reason for rejection code of 50, ‘Line Item Consolidation’. If there is no remainder,  update the qty on this item directly.
    •     Part 2 is relevant for order types ZOR, ZCA, ZSM
    •     This batch job will have to be run manually for Day Pick orders.  The end of this program should automatically kick off the delivery due list for Day Pick orders, shipping condition 02.
    Business Justification:
    The business requires that like order line items be consolidated to one line item prior to the order going to the warehouse for picking.  This will aid in picking at the warehouse as well as result in the customer invoice not reflecting more than one line item for the same material.  In the case where the customer has truly ordered more than a case, i.e;, 1 case, 2 bottles, the documents in SAP will still reflect 2 lines.

Maybe you are looking for