QM-qs21-qp01

Dear all,
I created mic(using qs21) and assigned in qp01.
I want to delete mic code.
fist i deleted form qp01.
In qp05 this material is not showing.
But qs22 it is showing.
i want to delete .
How to do delete this mic .
Please help me.
jyoti prakash

Dear Mittal,
While creating MIC i'm not using class characteristic field
only first 3 fields are entered viz.,
1.Plant
2. MIC code
3. Valid from then goes to next screen.
There complete copy model comes by default.It's greyed out.
Not able to change. Pls suggest what do u mean by Class char
Rgds,
Jyoti

Similar Messages

  • Defects Recording  in MIC

    Hello
    When we set this indicator , i am getting a warning message in QS21 / QP01. I already assigned the code 9 to the relevant plant .
    But the warning message was suppressed if i assign any one of the code from code 9 in MIC or Inspection plan .
    What was the concept behind it ?
    I want to use the code in the defects recording only
    Thanks
    JJ

    Dear JJ
    The defect recording tick in the mic is for automatic defect recording. What this means is if an inspection characteristic is rejected during results recording, the function for recording defects for a characteristic is automatically called up. Defects recording in the background is done if you define defect codes in the inspection characteristic.You can specify three defect codes for a quantitative characteristic:A defect code for a general rejection,A defect code for a rejection at an upper specification limit,A defect code for a rejection at a lower specification limit
    If you do not need this functioanlity remove the tick from MIC. You can anyway o defect recording without this tick also
    Hope this helps
    Regards
    Gajesh

  • Error while creating the Inspection plan by T.C QP01

    Hello Friends,
    In QP01, When i am trying to create a inspection plan system throwing the error message "The inspection plan identifier exists already. Enter another."
    Message no. QP054
    But in QP02, When i checked  for that material, Plant, Group Number, Group counter, Usage, Status, i didn't find the entry over there.
    Actually my requirement is to create a inspection plan for a material and plant combination with speicfic Usage as 61(customer requirement and status 4) but when i am trying to create that system throwing the error message explained above.
    Thanks and Regards,
    Jitendra Chauhan.
    Edited by: jitendra chauhan on Jun 1, 2010 4:28 PM

    Hello Friends,
    Thanks for your valuable answers.
    I checked in table MAPL, for a particular material, Plant, Group Number and Group Counter, there is no entry.
    Where as in table PLKO, for a particular Group Number and Group Counter, entry is there. Actually this Inspection Plan Group Number and Group Counter is assigned to multiple materials through Material Assignment. If i delete the entry for this in table PLKO, than for all rest of the materials also entry will be deleted.
    Hence how to resolve this?
    Actually for other material number, same plant, same group number and same group counter, entry exist. So can i simply go in the inspection plan of other material,same plant,same group number,same group counter and than inside the material assignment to assign the required  material code, plant and the group counter number?
    Looking ahead for valuable inputs from the genius.
    Thanks and Regards,
    Jitendra
    Edited by: jitendra chauhan on Jun 2, 2010 8:09 AM

  • Error in QS21 T-code

    Hi,
    I am getting an error when using QS21 T-code.
    I have created Characteristics in CT01 and assigned them to class in turn to Material Master in MM01. Now I have to create MIC's for the Char's I have created. While doing so in QS21 I am getting an error message that
    "Class Char is already linked with master insp.char XXX in Plant XXX"
    So does this mean that only once a Class Char is linked to MIC and cannot be linked twice across the plants of company code..??
    Because I am trying to link them in Plant B, but I am getting the error that it's already linked in Plant A..??
    and also I can see in QS61 that the Class Char's and MIC's are linked in Plant A..Now I am working in plant B..So if I have to link them in Plant B should I need to link them again by giving Plant B..??
    Please explain
    Regard's,
    Uday.
    Edited by: uday Kiran 1903 on Sep 27, 2011 8:00 AM
    Edited by: uday Kiran 1903 on Sep 27, 2011 8:05 AM

    Hi Hari,
    I have gone through the links you have given. But I am not understanding the discussions happened in Link 2 you have given.
    Regarding the "Linking MIC to Class Characteristics for Multiple Plants."
    Please explain me the Fictional plant thing in the below question posted in that SAP Fan club Forum
    1) With regards to linking MIC's to Class Characteristiecs do I have to use only 1 plant for the MIC's, i.e. I can't link two characteristics in two different plants to 1 Class Char? I see some people create a fictional plant and use this to create all the MIC's. Is this the best option?
    In my present project also we are following the same situation of similar plants producing the same material. Instead of using Inspection plan we are using MIC's for recording the results.
    Please explain.
    Regard's,
    Uday.

  • Urgent:  making multiple inspection characterstics in QP01 bdc

    Hi,
    I had made a BDC on QP01 in which i am able to upload 1 line for the
    inspection characterstic of a single Operation .
    Now the problem is there are around 10 to 15 lines for the inspection characterstic of a single Operation and i am not able to do it through it my bdc. now anybody can provide me some knowledge about it as how it is to be done?
    plzz help me out as it is really urgent to me and help will be definately rewarded.

    Hi,
    I had made bdc on transaction CA02. Its similiar to your requirement in which there are multiple inspection characterstics for single operation. Through BDC its possible. Please go through the below code.
    LOOP AT i_route_file INTO wa_route_file.
        AT NEW plnnr.
          PERFORM : zf_prepare_bdcdata_prg   USING 'SAPLCPDI'  '1010',
                    zf_prepare_bdcdata_value USING 'BDC_OKCODE' '/00',
                    zf_prepare_bdcdata_value USING 'RC271-PLNNR'
                                                   wa_route_file-plnnr.
    *--Conversion of date to internal format.
          PERFORM zf_conv_date.
          PERFORM zf_prepare_bdcdata_value USING 'RC271-STTAG' v_date.
        ENDAT.
        lv_arbpl = wa_route_file-arbpl.
        lv_steus = wa_route_file-steus.
        lv_ltxa1 = wa_route_file-ltxa1.
    *--Operation data
        AT NEW vornr.
          v_inscounter = 1.
          PERFORM : zf_prepare_bdcdata_prg   USING 'SAPLCPDI' '1400',
                    zf_prepare_bdcdata_value USING 'BDC_OKCODE' '/00',
                    zf_prepare_bdcdata_value USING 'RC27X-ENTRY_ACT' '1'.
    *--Conversion of vornr to internal format
          PERFORM zf_conv_vornr.
          READ TABLE i_opno INTO wa_opno WITH KEY plnnr = wa_route_file-plnnr
                                                  vornr = wa_route_file-vornr.
          IF sy-subrc <> 0.
            DESCRIBE TABLE i_opno LINES v_lines.
            v_num = v_lines + 1.
          ELSE.
            v_num = sy-tabix.
          ENDIF.
          CLEAR v_fieldnm.
          CONCATENATE 'PLPOD-ARBPL(' v_num ')' INTO v_fieldnm.
          PERFORM : zf_prepare_bdcdata_value USING v_fieldnm lv_arbpl.
          CLEAR v_fieldnm.
          CONCATENATE 'PLPOD-STEUS(' v_num ')' INTO v_fieldnm.
          PERFORM : zf_prepare_bdcdata_value USING v_fieldnm lv_steus.
          CLEAR v_fieldnm.
          CONCATENATE 'PLPOD-LTXA1(' v_num ')' INTO v_fieldnm.
          PERFORM : zf_prepare_bdcdata_value USING v_fieldnm lv_ltxa1,
                    zf_prepare_bdcdata_prg   USING 'SAPLCPDI' '1400',
                    zf_prepare_bdcdata_value USING 'BDC_OKCODE' '=QMUE',
                    zf_prepare_bdcdata_value USING 'RC27X-ENTRY_ACT' '1'.
          CLEAR v_fieldnm.
          CONCATENATE 'RC27X-FLG_SEL(' v_num ')' INTO v_fieldnm.
          PERFORM: zf_prepare_bdcdata_value USING v_fieldnm 'X'.
        ENDAT.
    *--Inspection Characteristics
        PERFORM: zf_prepare_bdcdata_prg   USING 'SAPLQPAA' '0150',
                 zf_prepare_bdcdata_value USING 'BDC_OKCODE' '/00'.
        CLEAR v_fieldnm.
        CONCATENATE 'PLMKB-VERWMERKM(' v_inscounter ')' INTO v_fieldnm.
        PERFORM: zf_prepare_bdcdata_value USING v_fieldnm
                                                wa_route_file-verwmerkm.
        CLEAR v_fieldnm.
        CONCATENATE 'PLMKB-MKVERSION(' v_inscounter ')' INTO v_fieldnm.
        PERFORM: zf_prepare_bdcdata_value USING v_fieldnm
                                                wa_route_file-mkversion.
        CLEAR v_fieldnm.
        CONCATENATE 'PLMKB-PMETHODE(' v_inscounter ')' INTO v_fieldnm.
        PERFORM: zf_prepare_bdcdata_value USING v_fieldnm
                                                wa_route_file-pmethode.
        CLEAR v_fieldnm.
        CONCATENATE 'PLMKB-PMTVERSION(' v_inscounter ')' INTO v_fieldnm.
        PERFORM: zf_prepare_bdcdata_value USING v_fieldnm
                                                wa_route_file-pmtversion.
        CLEAR v_fieldnm.
        CONCATENATE 'PLMKB-STICHPRVER(' v_inscounter ')' INTO v_fieldnm.
        PERFORM: zf_prepare_bdcdata_value USING v_fieldnm
                                                wa_route_file-stichprver.
        CLEAR v_fieldnm.
        CONCATENATE 'QFLTP-SOLLWERT(' v_inscounter ')' INTO v_fieldnm.
        PERFORM: zf_prepare_bdcdata_value USING v_fieldnm
                                                wa_route_file-sollwert.
        CLEAR v_fieldnm.
        CONCATENATE 'QFLTP-TOLERANZUN(' v_inscounter ')' INTO v_fieldnm.
        PERFORM: zf_prepare_bdcdata_value USING v_fieldnm
                                                wa_route_file-toleranzun.
        CLEAR v_fieldnm.
        CONCATENATE 'QFLTP-TOLERANZOB(' v_inscounter ')' INTO v_fieldnm.
        PERFORM: zf_prepare_bdcdata_value USING v_fieldnm
                                                wa_route_file-toleranzob.
        CLEAR v_fieldnm.
        CONCATENATE 'PLMKB-DUMMY10(' v_inscounter ')' INTO v_fieldnm.
        PERFORM: zf_prepare_bdcdata_value USING v_fieldnm
                                                wa_route_file-dummy10.
        PERFORM: zf_prepare_bdcdata_prg   USING 'SAPLQPAA' '1501',
                 zf_prepare_bdcdata_value USING 'BDC_OKCODE' '=ENT1',
                 zf_prepare_bdcdata_value USING 'PLMKB-VERWMERKM'
                                                wa_route_file-verwmerkm,
                 zf_prepare_bdcdata_value USING 'PLMKB-QPMK_WERKS'
                                                wa_route_file-qpmk_werks,
                 zf_prepare_bdcdata_value USING 'PLMKB-MKVERSION'
                                                wa_route_file-mkversion,
                 zf_prepare_bdcdata_value USING 'PLMKB-PMETHODE'
                                                wa_route_file-pmethode,
                 zf_prepare_bdcdata_value USING 'PLMKB-QMTB_WERKS'
                                                wa_route_file-qmtb_werks,
                 zf_prepare_bdcdata_value USING 'PLMKB-PMTVERSION'
                                                wa_route_file-pmtversion.
        PERFORM: zf_prepare_bdcdata_prg   USING 'SAPLQPAA' '1502',
                 zf_prepare_bdcdata_value USING 'BDC_OKCODE' '=ENT1',
                 zf_prepare_bdcdata_value USING 'BDC_CURSOR' 'PLMKB-PMETHODE',
                 zf_prepare_bdcdata_value USING 'PLMKB-PMETHODE'
                                                wa_route_file-pmethode,
                 zf_prepare_bdcdata_value USING 'PLMKB-QMTB_WERKS'
                                                wa_route_file-qmtb_werks,
                 zf_prepare_bdcdata_value USING 'PLMKB-PMTVERSION'
                                                wa_route_file-pmtversion.
        PERFORM: zf_prepare_bdcdata_prg   USING 'SAPLQPAA' '1502',
                 zf_prepare_bdcdata_value USING 'BDC_OKCODE' '=ENT1',
                 zf_prepare_bdcdata_value USING 'BDC_CURSOR' 'PLMKB-PMETHODE',
                 zf_prepare_bdcdata_value USING 'PLMKB-PMETHODE'
                                                 wa_route_file-pmethode,
                 zf_prepare_bdcdata_value USING 'PLMKB-QMTB_WERKS'
                                                 wa_route_file-qmtb_werks,
                 zf_prepare_bdcdata_value USING 'PLMKB-PMTVERSION'
                                                 wa_route_file-pmtversion.
        PERFORM: zf_prepare_bdcdata_prg   USING 'SAPLQPAA' '0150',
                 zf_prepare_bdcdata_value USING 'BDC_OKCODE' '=QMD1',
                 zf_prepare_bdcdata_value USING 'RQPAS-ENTRY_ACT' '1'.
        CLEAR v_fieldnm.
        CONCATENATE 'RQPAS-SEL_FLG(' v_inscounter ')' INTO v_fieldnm.
        PERFORM: zf_prepare_bdcdata_value USING v_fieldnm 'X'.
        PERFORM: zf_prepare_bdcdata_prg   USING 'SAPLQPAA' '0160',
                 zf_prepare_bdcdata_value USING 'BDC_OKCODE' '=QMAM',
                 zf_prepare_bdcdata_value USING 'PLMKB-STICHPRVER'
                                                wa_route_file-stichprver.
        PERFORM: zf_prepare_bdcdata_prg   USING 'SAPLQPAA' '0160',
                 zf_prepare_bdcdata_value USING 'BDC_OKCODE' '/00',
                 zf_prepare_bdcdata_value USING 'BDC_CURSOR'
                                                'PLMKB-PROBENR',
                 zf_prepare_bdcdata_value USING 'PLMKB-PROBENR'
                                               wa_route_file-probenr,
                 zf_prepare_bdcdata_value USING 'PLMKB-PMETHODE'
                                               wa_route_file-pmethode,
                 zf_prepare_bdcdata_value USING 'PLMKB-QMTB_WERKS'
                                      wa_route_file-qmtb_werks,
                 zf_prepare_bdcdata_value USING 'PLMKB-PMTVERSION'
                                       wa_route_file-pmtversion.
        PERFORM: zf_prepare_bdcdata_prg   USING 'SAPLQPAA' '1502',
                 zf_prepare_bdcdata_value USING 'BDC_OKCODE' '=ENT1',
                 zf_prepare_bdcdata_value USING 'BDC_CURSOR' 'PLMKB-PMETHODE',
                 zf_prepare_bdcdata_value USING 'PLMKB-PMETHODE'
                                                 wa_route_file-pmethode,
                 zf_prepare_bdcdata_value USING 'PLMKB-QMTB_WERKS'
                                                 wa_route_file-qmtb_werks,
                 zf_prepare_bdcdata_value USING 'PLMKB-PMTVERSION'
                                                 wa_route_file-pmtversion.
        PERFORM: zf_prepare_bdcdata_prg   USING 'SAPLQPAA' '0160',
                 zf_prepare_bdcdata_value USING 'BDC_OKCODE' '=QMBU',
                 zf_prepare_bdcdata_value USING 'PLMKB-PROBENR'
                                                wa_route_file-probenr,
                 zf_prepare_bdcdata_value USING 'PLMKB-PMETHODE'
                                                wa_route_file-pmethode,
                 zf_prepare_bdcdata_value USING 'PLMKB-QMTB_WERKS'
                                                wa_route_file-qmtb_werks,
                 zf_prepare_bdcdata_value USING 'PLMKB-PMTVERSION'
                                                wa_route_file-pmtversion.
        PERFORM: zf_prepare_bdcdata_prg   USING 'SAPLQPAA' '1502',
               zf_prepare_bdcdata_value USING 'BDC_OKCODE' '=ENT1',
               zf_prepare_bdcdata_value USING 'BDC_CURSOR' 'PLMKB-PMETHODE',
               zf_prepare_bdcdata_value USING 'PLMKB-PMETHODE'
                                               wa_route_file-pmethode,
               zf_prepare_bdcdata_value USING 'PLMKB-QMTB_WERKS'
                                               wa_route_file-qmtb_werks,
               zf_prepare_bdcdata_value USING 'PLMKB-PMTVERSION'
                                               wa_route_file-pmtversion.
        v_inscounter = v_inscounter + 1.
        AT END OF plnnr.
    *--Call transaction CA02- Change Routing
          CALL TRANSACTION 'CA02' USING i_bdcdata
                                  MESSAGES INTO i_messtab
                                  MODE 'N'
                                  UPDATE 'S'.
          COMMIT WORK AND WAIT.
        ENDAT.
      ENDLOOP.
    Please ask if any queries....

  • PROBLEM IN QP01 BDC ( 19TH LINE ITEM IS NOT TAKING)

    DEAR ALL,
    I am working on a bdc of QP01 for inspection plan, my bdc is working prperly , problem is that  in sceen there r 18 lines for line  items , but i have 30 line items. after 18 line items no data is picking. and a message is coming no input data is there for screen no 0150. i tried a lot  and unable to solve . if anybody can solve my problem . i send u the part of my code.
    LOOP AT ITAB.
    CHECK ITAB-MATNR = ITAB1-MATNR.
    if flag = 1.
      ** QUALITATIVE **
    if itab-QUALITAT = 'X' AND itab-QUANTITAT = ''.
    IF I ge 18.
    *CONCATENATE  'RQPAS-SEL_FLG(' I ')' INTO SCR.
    *perform bdc_field       using SCR
    X = '17'..
    CONCATENATE  'RQPAS-SEL_FLG(' X ')' INTO SCR.
    perform bdc_field       using SCR
    X1 = '18'..
    CONCATENATE  'RQPAS-SEL_FLG(' X ')' INTO SCR.
    perform bdc_field       using SCR
    X2 = '340'.
    CONCATENATE  'RQPAS-SEL_FLG(' X1 ')' INTO SCR.
    perform bdc_field       using SCR
        PERFORM BDC_DYNPRO      USING 'SAPLQPAA' '0150'.
        PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                      'RQPAS-QUALITAT(02)'.
       PERFORM BDC_FIELD       USING 'RQPAS-ENTRY_ACT'
                                     '1'.
                                       i.
       PERFORM BDC_FIELD       USING 'RQPAS-AB_MKNR'
                                ITAB-MERKNR         .
        PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                      '/00'.
    endif.
    perform bdc_dynpro      using 'SAPLQPAA' '0150'.
    perform bdc_field       using 'BDC_CURSOR'
                                  'PLMKB-VERWMERKM(01)'.
    perform bdc_field       using 'BDC_OKCODE'
                                  '/00'.
    perform bdc_field       using 'RQPAS-ENTRY_ACT'
                                  '1'.
    k = i - 1.
    CONCATENATE  'RQPAS-SEL_FLG(' k ')' INTO SCR.
    perform bdc_field       using SCR
    CONCATENATE  'RQPAS-SEL_FLG(' i ')' INTO SCR.
    perform bdc_field       using SCR
                                  'X'.
    ***perform bdc_field       using 'BDC_OKCODE'
                                 '/00'.
    ***'=QMLM'.
    CONCATENATE  'PLMKB-VERWMERKM(' I ')' INTO SCR.
    perform bdc_field       using   scr      "'PLMKB-VERWMERKM(01)'
                                 'DS-TH-01'.
    itab-VERWMERKM.
    CONCATENATE  'PLMKB-KURZTEXT(' I ')' INTO SCR.
    perform bdc_field       using   scr
    itab-KURZTEXT.
    regards
    banaja

    but i want to try it out by modifying the existing code.
    please provide me guidelines to solve this problem.

  • Error in LSMW in Uploading Inspection Plan in QP01

    Hi All,
    I am facing problem when executing LSMW, I am Uploading Inspection Plan in QP01 transaction using Direct Input methos. The problem is on 13th step :Error that I get is 'No profile with entry tool for task list / / / in session INSPECTION_OBJ', here INSPECTION_OBJ is the name of the session. I have given the constant value of field profile (BIPKO-PROFIDNETZ) in mapping step and also activated check box 'entry tool' under profile to remove this error. But in  that case i can pass only the header data while processing the session and control does not get into Operation and characteristic screen.
    Can anyone pls help me..
    Thanks in advance...

    You might need to redo the recording all over again, BDC has plentty of scenario for screen selection to go wrong, so can't really tell what cause your problem based on your desc.  I have been stop using BDC to uplaod material since 5 years ago, I always use Direct input in LSMW and it works much better. I recomend you try the Direct input method instead of BDC if still getting problem.

  • QM_LSMW BY RECORDING METHOD FOR QP01

    Dear QM Experts,
    1.     I am doing LSMW by recording method for QP01 transaction code
    2.     I am facing one problem while recording in inspection characteristic screen
    3.     While saving another screen opens prompting to put inspection method, plant and version for inspection method.
    4.     This is not at all needed as per the requirement.
    I removed default Plant for Inspection Method version, Version Number of the Inspection Method while recording LSMW in inspection characteristic screen. Still it is happening.
    Surprisingly when we create inspection plan though QP01 it never asks for these things.
    Any remedies?
    Best Regards,
    Thanks is advance
    Anand Rao

    Do not use Recording for QP01.
    There is a pragram named "RCPTRA01". It can be selected in step1 of lsmw>>Object Type and Import Method>> Standard Batch/Direct Imput>>Object 0240;Method 0000;Program RCPTRA01; Program Type B.
    Then Step 2, define source structure. In fact you may go to step 4 to have a look at the structure of the target structure. It would be easy to copy that. The source structure would be as below, ZBI001 would be the top level and the others the same lever under ZBI001:
    Source Structures
            ZBI001                    Transaction Header Record for Data Transfer of Routings
                ZBIMPL                   Batch Input Structure for Allocation of Mat. to Task Lists
                ZBIPKO                   Batch Input Structure for Task List Header
                ZBIPPO                   Batch input structure for task list operation
                ZBIPMK                   Inspection characteristics for batch input of task lists
    In step 3, define source fields for source structure. For easy define, you may click "Object Overview">> Table to get the possible fields of the related structure, and then copy to Excel; after that, you may copy the fields directly from Excel to fields difining window in step 3.
    Step 4, assign the source structures to target structures, the target structures are named the same as the source structures above, just without the letter "Z". For example, assign ZBIMPL to BIMPL, ZBIPKO to BIPKO, except ZBI001 is assigned to BI000 and BI001 as well.
    Then Step 5, you may find there are RECTY and default settings are "00" "99" "01" "03" "09" "18" for BI000, BI001, BIMPL, BIPKO, BIPPO and BIPMK. Let alone "99" and imput these value to field "RECTY" in corresponding source structure fields
    Then you may run auto field mapping in step 5, and make some values constant, like PLNTY=Q etc.
    Then a problem with the profile under field "PROFIDNET". Run TCODE 'SPRO' to IMG>Quality Management>Quality Planning>Inspection Planning>General>Maintain Profiles for Default Values>Profile: default values plan/general. You may find there is a box named "Entry tool", tick that box, if not it is not possible to run QP01 in lsmw. And at the same time you may find the profile is 0000001. Key the value to field "PROFIDNET" and make the rule as constant.
    For step 6 there is nothing to do
    in Step 7, unlike other objects, you can use just one .txt file for uploading the inspection plan. When specy file, select "Data for Multiple Source Structures(Seq.file); Delimiter: Tabulator; File structure: Field order Matches source structure definition(as in Seq.file) I find not possible to put field names at start of file, so "Field Order Matching" is very important
    Then how to prepare the file? We can accomplish this with 5 excel sheets
    the fields orders for my customer is like this:
    1)for RECTY 18(Inspection Charatristics):
    MATNR     RECTY     MERKNR     KURZTEXT     VERWMERKM     QPMK_ZAEH     PMETHODE     QMTB_WERKS     STICHPRVER     PROBEMGEH     STELLEN     MASSEINHSW     SOLLWERT     TOLERANZOB     TOLERANZUN
    2)for RECTY 09(Operation):
    MATNR     RECTY     VORNR     STEUS     WERKS     LTXA1     UMREZ     UMREN
    3)for RECTY 03(Header):
    MATNR     RECTY     DATUV     VERWE     WERKS     STATU     PLNME     LOSVN     LOSBS     VAGRP     KTEXT
    4)for RECTY 01(Allocation of Material)
    MATNR     RECTY     MATNR     WERKS     LIFNR     KUNR
    5)for RECTY 00(Transaction Header)
    MATNR     RECTY     TCODE     START
    Creat a new blank sheet and copy the fild contents of these 5 sheets into it, then you can sort the fields in A to Z order with Column A(MATNR), B(RECTY), and C(MERKNR), then the seq.file to be uploaded is completed.
    for example:
    10001042     00     QP01     20090119                                                            
    10001042     01     10001042     1200                                                            
    10001042     03     20090119     5     1200     4     PC     0     99999999          Screw\M16x45\GB/T5783                         
    10001042     09     0010     QM01     1200     inspection     1     1                                        
    10001042     18     10      inspection on material     C101     1200     JF035     1200     GUD5     PC                              
    10001042     18     20      Inspection on size     C102     1200     JF034     1200     GUD5     PC
    Then copy start from Column B, i.e., without the material numbers in Column A, to .txt file.
    Specy the file in Step 7 in lsmw.
    the step 8, assign this .txt file to all structures
    then step 9, 10, 11, 12, 13 Creast Session and run it in at the end.
    Actually this program is not possible for QP02. If you want to make some correction on the inspection plans in SAP, you'd better delete them and upload the revised one.
    This program is very similar to CA01 Production Routing and thus also applicable to CA01. But I recommend using  Object 0170;Method 0002;Program RCPTRA02; Program Type D for CA01, because it provides testing transfer at the end so that you can check out logical errors, and much fastee. Pity that for QP01 there is no such program
    Currenty I am acting as Data cunsultant for an Elevator Manufaturer in China, hope my experience would help for you. My MSN is zhangxiaojun at msn dot com

  • Generic Object Services (GOS) feature to be activated on QP01/02/03

    My client want to have the Object Services(GOS) capability turned ON on
    QP01, QP02 and QP03 screens which will allow them to link documents to
    the Inspection Plan. And right now that feature/icon is not there on
    QP01/QP02/QP03 screens. When I tried to activate the 'Services for
    Object' on those screens, I got the message 'No Service Available'.
    Could anyone please provide a solution to turn on that feature for the
    Inspection Plan screens?
    Thanks & Regards,
    AnjiReddy Pulagam.

    You need to implement a BADI to generate the GOS toolbar for that transactions, and put this code inside:
    DATA: LO_MANAGER  TYPE REF TO CL_GOS_MANAGER,
              LA_OBJ      TYPE BORIDENT.
    * Set object Key
        LA_OBJ-OBJTYPE = 'BUS1191'. "Bussiness object for inspection plan
        LA_OBJ-OBJKEY  = inspectionPlanIdentifier. " Inspection plan number
    * GOS toolbar
        CREATE OBJECT LO_MANAGER
          EXPORTING
            IS_OBJECT    = LA_OBJ
            IP_NO_COMMIT = SPACE
          EXCEPTIONS
            OTHERS = 1.
    Regards

  • Error occured while uploading the data for Tocde QP01 (BDC)

    Hi,
    I am facing a strange problem i.e. when i try to upload the data for the Tcode QP01 i am able to upload the data for the 18 rows but when it is more than 18 ,it gives the following error and saves the data upto 18 rows only :-
    CALL_TRANSACTION QP01 returncode:     0  RECORD:          0
    S Field RC27X-FLG_SEL . not found in loop of screen SAPLCPDI 1400
    S Cursor field PLMKB-VERWMERKM (18) does not exist in the screen
    S Field PLMKB-VERWMERKM (18) does not exist in the screen SAPLQPAA 0150
    S Field PLMKB-STICHPRVER (18) does not exist in the screen SAPLQPAA 0150
    S Inspection plan with plan group 12775 for material 200999 is saved
    Is there any way to solve this problem...

    hi,
    Ok,i agree with you but the thing is it was allowing to upload the data for more than 18 rows as there was logic written. It is specified in the code:-
    ELSEIF itab1-serial > 18 AND itab1-serial < 35.
                  IF index = 19.
                    index = 2.
                  ENDIF.
    Edited by: nav009 on Sep 9, 2009 8:25 AM

  • BDC for QP01

    Can any one help me ,BDC for QP01 transaction with multiple line items.
    Thanx in advance,I promise to reward.

    Hi Anurag,
      You can easily create a BDC for QP01 by going through this link,
    http://www.sapdevelopment.co.uk/bdc/bdchome.htm
    Regards,
    Azaz Ali.

  • Lsmw by bapi for qm to upload inspection plan qp01

    I want to upload Inspection plan by Transaction qp01
    <Edited by Moderator - Bhavesh Kantilal. Removed all Capitals post. User has been warned and request to move this thread to the appropriate forum has been raised.>
    Edited by: Bhavesh Kantilal on Dec 20, 2008 1:50 AM

    Post it here:
    ABAP Connectivity
    Also, Please do not use all CAPS.
    It is understood as shouting at people.
    Regards,
    Ravi

  • Changes in qs21, qs31, qs41, qdv1

    Hi, pls inform what t-codes should be used to see the changes in qm master data like qs21, qs31, qdv1, qs41 etc?

    HI,
         For QS21 use QS28
         For QS31 Use QS38
    and click on Dynamic selection ---Changed by orchanged  On and use *
    you will get Canges for the same.
    Cheers,

  • Lsmw for qp01 (inspection charactoristics).

    Hello ,
    I am trying to do lsmw for qp01 transaction (inspection charactoristics.)
    I am using Recording method to upload the data.
    I have started recording and filled
    first screen i.e header :
    MATNR C(018) Material
    WERKS C(004) plant
    STTAG DDMY(008) Key Date.
    then i have clicked enter next screen comes. which is inspection plan create tast list overview.
    here i have selected a first line and clicked 'operations' pushbutton.
    next screen operations overview opened.
    following 2 fields are for selecting line and clicking the pushbutton.
    ENTRY_ACT C(011) Entry
    FLG_SEL_01 C(001) FLG_SEL_01
    Then i have selected first line and clicked 'inspection charactoristics' pushbutton.
    next screen charactoristics overview screen is opened.
    Inspection charactoristic screen :
    VERWMERKM_03 C(008) VERWMERKM_03
    VERWMERKM C(008) VERWMERKM
    QPMK_WERKS C(004) QPMK_WERKS
    PMETHODE C(008) PMETHODE
    QMTB_WERKS C(004) QMTB_WERKS
    KURZTEXT C(040) Description
    SOLLWERT C(016) SOLLWERT
    TOLERANZOB C(016) TOLERANZOB
    My data is in .txt file.
    When i run the lsmw , when i process this session , then in inspection charactoristic screen it uploads values of master inspection charactoristics from datafile and takes automaticaly short text insp. charactoristics but system show a window to enter the Target value for quantitative charactoristics Upper specification limit and lower specification limit values for mic's .
    But i have already given these values in my .txt file.
    It is not taken from my .txt file. Again asking me to enter the values.
    Please tell me solution for this problem.

    Hi,
    For each Quantitative Char enter the quantitative data in QS23 .Then you do the LSMW recording.
    This is because you might selected control Indicators Lower and Upper specific limit.
    Regrds
    Praveen

  • Lsmw for qp01.

    Hello ,
        I am trying to do lsmw for qp01 transaction (inspection charactoristics.)
        I am using Recording method to upload the data.
      i am using these fields.
    1)  first screen i.e header :
       MATNR                          C(018)    Material
    WERKS                          C(004)  plant
    STTAG                          DDMY(008) Key Date.
    following  2 fields are for selecting line and clicking the pushbutton.
    ENTRY_ACT                      C(011)    Entry
    FLG_SEL_01                     C(001)    FLG_SEL_01
    2) Inspection charactoristic screen :
    VERWMERKM_03                   C(008)    VERWMERKM_03
    VERWMERKM                      C(008)    VERWMERKM
    QPMK_WERKS                     C(004)    QPMK_WERKS
    PMETHODE                       C(008)    PMETHODE
    QMTB_WERKS                     C(004)    QMTB_WERKS
    KURZTEXT                       C(040)    Description
    SOLLWERT                       C(016)    SOLLWERT
    TOLERANZOB                     C(016)    TOLERANZOB
        My data is in .txt file.
        When i run the lsmw ,  when i process this session , then in inspection charactoristic screen it uploads  values of master inspection charactoristics  from datafile and takes automaticaly short text insp. charactoristics   but system show a window to enter the Target value for quantitative charactoristics Upper specification limit and lower specification limit values for mic's .
        But i have already given these values in my .txt file.
       It is not taken from my .txt file. Again asking me to enter the values.
      Please  tell me  solution for this problem.

    Hi santosh,
    please check with mapping. As I have already faced this kind of problem and it was because of mapping.
    recheck and try take help from your senior ABAPers.
    cheers
    Suvi

Maybe you are looking for

  • How to call rest service with POST Http method in SMP2.3 HWC?

    Hi Experts,    I am doing a sample for Rest Service in smp. http://192.168.1.119:8086/Test/services/Products I am calling the above service in the smp it is pulling the data from the service with GET Http Method. Now i want to call this service for l

  • From PDF to ePub

    Hi everybody! I was  wondering if now, February 2011, there's a tool which can convert PDF  files into ePub format without all the mess caused by, e.g., Calibre. Thank you very much!

  • There is no iweb folder in application support

    there is no iweb folder in application support. Why?

  • Read Out Loud License Error

    Whenever I try to use Read Out Loud in either Adobe Reader XI or Acrobat X, I get an error message about having an expired license or not having a valid license verification file.  How can I fix this error message? Thanks.

  • How do you open Numbers files in Excel

    I just completed an invoice file in Numbers. And tried opening it in Excel, but it would not. Why is this? I thought they were compatible?