Regarding ME22n Transaction

Hi ABAPers,
                      I am working on one report program which is used for to transfer purchase orders from MM to SRM.In Selction Screen Paramenters we are taken Select options for purchase order selection.while exection if i am takeing only one purchase order its working fine but when i am selection range option it wont work.while debugging it tkes all the range values.But the problem is in the output it says MPxxx-spinf filed is not an input field while runing in No screen mode for one purchase order it is in change mode alternative purchase order it is in dispaly mode.
Can any one give me the solution for this.
Thanks in advance.
regards,
kishore.

> like x purchase order is already processing by user.
That means some lock already there on the Processing purchase order so that is the reason it is opening in display mode.
may be you can try to read the locks on the Purchase order before processing and then proceed.
Use the Function ENQUEUE_READ and find the lock on the processing PO beofore it going to proceed, if the lock is there then process the next Purchase order..

Similar Messages

  • Error message in ME22n transaction

    Hi All,
    We want to display error message at  status bar of me22n transaction for some certain conditon.I am using a user exit where actually i am writing a code.I tried to write like this  'Message  E101(ZE) ' but message is not displaying at status bar.
    Thanks
    Mohit

    Hi ,
    1 >If message is not getting shown at status bar then is it getting shown as popo up. ?
    2 > If message is not at all getting shown then that means your exit is not getting called. Please put a break point inside your exit and exeute  me22n and see if your debugger gets triggered.
    If Debugger does not get triggered then that mean , either you have not created Project for yoour Exit OR you are using incorrect Exit.
    Please revert with your observatins so that can help you further.
    Hope this is helpful.
    Regards,
    Uma Dave

  • User exit or BADI for ME22N transaction  (please read my requirement)

    In me22n transaction when i change a PO Delivery date for any line item and click on save The field latest GR date MEPO1313-LEWED in DELIVERY tab below should display date as per my requirement i.e (delivery date + 90 days)
    What uerexit is to be used else if BADI is used pleasee provide me step by step guide as i have never used vadi
    IT is urgent. plz helopp.

    Hi
    Find the available exits with the following program:::
    *& Report  ZFINDUSEREXIT
    report  zfinduserexit.
    tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
    tables : tstct.
    data : jtab like tadir occurs 0 with header line.
    data : field1(30).
    data : v_devclass like tadir-devclass.
    parameters : p_tcode like tstc-tcode obligatory.
    select single * from tstc where tcode eq p_tcode.
    if sy-subrc eq 0.
    select single * from tadir where pgmid = 'R3TR'
    and object = 'PROG'
    and obj_name = tstc-pgmna.
    move : tadir-devclass to v_devclass.
    if sy-subrc ne 0.
    select single * from trdir where name = tstc-pgmna.
    if trdir-subc eq 'F'.
    select single * from tfdir where pname = tstc-pgmna.
    select single * from enlfdir where funcname =
    tfdir-funcname.
    select single * from tadir where pgmid = 'R3TR'
    and object = 'FUGR'
    and obj_name eq enlfdir-area.
    move : tadir-devclass to v_devclass.
    endif.
    endif.
    select * from tadir into table jtab
    where pgmid = 'R3TR'
    and object = 'SMOD'
    and devclass = v_devclass.
    select single * from tstct where sprsl eq sy-langu and
    tcode eq p_tcode.
    format color col_positive intensified off.
    write:/(19) 'Transaction Code - ',
    20(20) p_tcode,
    45(50) tstct-ttext.
    skip.
    if not jtab[] is initial.
    write:/(95) sy-uline.
    format color col_heading intensified on.
    write:/1 sy-vline,
    2 'Exit Name',
    21 sy-vline ,
    22 'Description',
    95 sy-vline.
    write:/(95) sy-uline.
    loop at jtab.
    select single * from modsapt
    where sprsl = sy-langu and
    name = jtab-obj_name.
    format color col_normal intensified off.
    write:/1 sy-vline,
    2 jtab-obj_name hotspot on,
    21 sy-vline ,
    22 modsapt-modtext,
    95 sy-vline.
    endloop.
    write:/(95) sy-uline.
    describe table jtab.
    skip.
    format color col_total intensified on.
    write:/ 'No of Exits:' , sy-tfill.
    else.
    format color col_negative intensified on.
    write:/(95) 'No User Exit exists'.
    endif.
    else.
    format color col_negative intensified on.
    write:/(95) 'Transaction Code Does Not Exist'.
    endif.
    at line-selection.
    get cursor field field1.
    check field1(4) eq 'JTAB'.
    set parameter id 'MON' field sy-lisel+1(10).
    Execute the report, give the transaction you want to find user exit, and query.
    <b>BADI</b>
    To search for a badi, go to se 24 display <b>class cl_exithandler.</b>
    double click on method get_instance, get a break point on case statement.
    execute and start the required transaction in new session.
    look for variable <b>exit_name.</b> It would show the available badi's.
    Please do reward if useful
    Regards
    Dinesh

  • Field Exit for ME21N & ME22N transactions

    HI Friends,
    I need to make the SAP Standard screen field "Overdeliv. Tol." & "Unlimited" to inactive under the Item level data --> Delivery tab in ME21N & ME22N transaction.
    Can i do ths? If so give me the steps and Screen exit for the same...

    For User Exit's
    goto to tcode->status->program name->double click on that,
    then goto to-> attribute take the package name and
    Goto SMOD tcode ->Utilities->give the package name and F8
    then a list of exits will display for that tcode as well as that package.
    double click on the exit u can see the Fm exit,screen exit,feild exit,include exit. there
    u can check the table MODSAP
    For BADI's,
    1)goto to tcode SE24 give the CL_EXITHANDLER and display and then double click on the GET_INSTANCE
    keep Break point at this location 'call method cl_exithandler=>get_class_name_by_interface'
    then the tcode it will trigger there and we can debugg there we can find badi'for that tcode and then remove the break point.
    2)Goto to tcode->status->program name->double click on that program will display's
    then  press crtl+F then cl_exithandler
    Thank u,
    santhosh

  • Save PO in me22n transaction.

    Hello experts,
    Which user make changes in po on 'ME22N' transaction in some item from all item , how can i know
    where he make the changes , what is the item , what is the fields that was changes ?
    I write my code in  F.M 'EXIT_SAPMM06E_012' -  INCLUDE ZXM06U43 .
    Thanks for your help.
    Avi.

    Create this report...it will give you the PO changes history.
    *& Report  Z_PO_CHANGE_HIST                                            *
    REPORT  Z_PO_CHANGE_HIST  LINE-SIZE 132 NO STANDARD PAGE HEADING
                     LINE-COUNT 065(001)
                     MESSAGE-ID VR.
    TABLES: DD04T,
            CDHDR,
            CDPOS,
            DD03L,
            DD41V,
            T685T,
            VBPA,
            TPART,
            KONVC,
            EKKO.
    TYPE-POOLS : SLIS.
    SELECTION-SCREEN: BEGIN OF BLOCK B1 WITH FRAME  TITLE TEXT-001.
    SELECT-OPTIONS: XUDATE FOR CDHDR-UDATE OBLIGATORY,
                    XEBELN FOR EKKO-EBELN,
                    XLIFNR FOR EKKO-LIFNR,
                    XEKORG FOR EKKO-EKORG OBLIGATORY,
                    XEKGRP FOR EKKO-EKGRP OBLIGATORY.
    SELECTION-SCREEN: END OF BLOCK B1.
    SELECTION-SCREEN: BEGIN OF BLOCK B2 WITH FRAME  TITLE TEXT-002.
    PARAMETERS:P_RAD RADIOBUTTON GROUP RAD DEFAULT 'X',
               P_RAD1 RADIOBUTTON GROUP RAD.
    SELECTION-SCREEN: END OF BLOCK B2.
    DATA: WFLAG,
          WCHANGENR LIKE CDHDR-CHANGENR.
    DATA: BEGIN OF ICDHDR OCCURS 50.
            INCLUDE STRUCTURE CDHDR.
    DATA: END OF ICDHDR.
    DATA: BEGIN OF ICDSHW OCCURS 50.
            INCLUDE STRUCTURE CDSHW.
    DATA: END OF ICDSHW.
    DATA: BEGIN OF EKKEY,
            EBELN LIKE EKET-EBELN,
            EBELP LIKE EKET-EBELP,
            ETENR LIKE EKET-ETENR,
          END OF EKKEY.
    DATA: BEGIN OF ITAB OCCURS 50,
            BEGIN OF EKKEY,
              EBELN LIKE EKET-EBELN,
              EBELP LIKE EKET-EBELP,
              ETENR LIKE EKET-ETENR,
            END OF EKKEY,
            CHANGENR LIKE CDHDR-CHANGENR,
            UDATE    LIKE CDHDR-UDATE,
            UTIME    LIKE CDHDR-UTIME,
            USERNAME LIKE CDHDR-USERNAME,
            CHNGIND  LIKE CDSHW-CHNGIND,
            FTEXT    LIKE CDSHW-FTEXT,
            OUTLEN   LIKE CDSHW-OUTLEN,
            F_OLD    LIKE CDSHW-F_OLD,
            F_NEW    LIKE CDSHW-F_NEW,
            CHANGE(24) TYPE C,
          END OF ITAB.
    DATA: OLD_OBJECTID LIKE CDHDR-OBJECTID.
    DATA: W_XUDATE(50) TYPE C,
          W_XEBELN(50) TYPE C,
          W_XLIFNR(50) TYPE C,
          W_XEKORG(50) TYPE C,
          W_XEKGRP(50) TYPE C.
    DATA: BEGIN OF I_AUTH_EKGRP OCCURS 0,
             EKGRP LIKE EKKO-EKGRP,
          END OF I_AUTH_EKGRP.
    FCAT is used for the field catalog
    DATA: FCAT TYPE TABLE OF SLIS_FIELDCAT_ALV WITH NON-UNIQUE DEFAULT KEY
          WITH HEADER LINE INITIAL SIZE 0,
    FS_LAYO is used for Grid Layout
          FS_LAYO TYPE SLIS_LAYOUT_ALV,
    FEVENTS to handle the events TOP OF PAGE & USER_COMMAND
          FEVENTS TYPE TABLE OF SLIS_ALV_EVENT WITH NON-UNIQUE DEFAULT KEY
          WITH HEADER LINE INITIAL SIZE 0,
    FHEADER is used for List header
          FHEADER TYPE TABLE OF SLIS_LISTHEADER WITH NON-UNIQUE DEFAULT KEY
          WITH HEADER LINE INITIAL SIZE 0.
    AT SELECTION-SCREEN.
    Authorization check for Purchasing Group
      SELECT EKGRP
        INTO TABLE I_AUTH_EKGRP
        FROM T024
        WHERE EKGRP IN XEKGRP.
      LOOP AT I_AUTH_EKGRP.
        AUTHORITY-CHECK OBJECT 'M_BEST_EKG'
                 ID 'ACTVT' FIELD '03'
                 ID 'EKGRP' FIELD I_AUTH_EKGRP-EKGRP.
        IF SY-SUBRC NE 0 .
          MESSAGE E398(00) WITH
           'User' SY-UNAME 'not authorised for Purchasing group : ' I_AUTH_EKGRP-EKGRP.
        ENDIF.
      ENDLOOP.
    Check for date to be in same month
      IF SY-UCOMM EQ 'ONLI' OR SY-UCOMM EQ 'PRIN'.
        IF XUDATE-LOW0(6) NE XUDATE-HIGH0(6).
          MESSAGE E999(FG) WITH 'Date should belong to same month.'.
          LEAVE TO SCREEN 1000.
        ENDIF.
      ENDIF.
    START-OF-SELECTION.
      SELECT * FROM EKKO WHERE EBELN IN XEBELN
                           AND BEDAT IN XUDATE
                           AND LIFNR IN XLIFNR
                           AND EKORG IN XEKORG
                           AND EKGRP IN XEKGRP.
        IF SY-SUBRC NE 0.
          CONTINUE.
        ENDIF.
        CLEAR CDHDR.
        CLEAR CDPOS.
        CDHDR-OBJECTCLAS = 'EINKBELEG'.
        CDHDR-OBJECTID   = EKKO-EBELN.
        PERFORM GETCHGDOCS.
      ENDSELECT.
      IF P_RAD = 'X'.
        DELETE ITAB[] WHERE EKKEY-EBELP NE ''.
      ENDIF.
      IF ITAB[] IS INITIAL.
        MESSAGE E999(FG) WITH 'No Data found for Selection'.
        LEAVE LIST-PROCESSING.
      ENDIF.
      LOOP AT ITAB.
        CLEAR: EKKEY.
        CASE ITAB-CHNGIND.
          WHEN 'U'.
            ITAB-CHANGE = 'Changed'.
          WHEN 'D'.
            ITAB-CHANGE = 'Delete'.
          WHEN 'E'.
            ITAB-CHANGE = 'Delete(Single Field)'.
          WHEN 'I'.
            ITAB-CHANGE = 'Insert'.
        ENDCASE.
        MODIFY ITAB.
        CLEAR : ITAB.
      ENDLOOP.
      SORT ITAB BY UDATE EKKEY-EBELN CHANGENR EKKEY-EBELP
                   EKKEY-ETENR.
      PERFORM Z_TOP_OF_PAGE.
      PERFORM Z_LAYOUT_SETTINGS.
      PERFORM Z_ALV_EVENTS.
      PERFORM Z_CREATE_FIELD_CATALOG.
      PERFORM Z_REUSE_ALV_GRID_DISPLAY.
    *&      Form  GETCHGDOCS
    FORM GETCHGDOCS.
      CALL FUNCTION 'CHANGEDOCUMENT_READ_HEADERS'
        EXPORTING
          DATE_OF_CHANGE    = CDHDR-UDATE
          OBJECTCLASS       = CDHDR-OBJECTCLAS
          OBJECTID          = CDHDR-OBJECTID
          TIME_OF_CHANGE    = CDHDR-UTIME
          USERNAME          = CDHDR-USERNAME
        TABLES
          I_CDHDR           = ICDHDR
        EXCEPTIONS
          NO_POSITION_FOUND = 1
          OTHERS            = 2.
      CHECK SY-SUBRC EQ 0.
      DELETE ICDHDR WHERE CHANGE_IND EQ 'I'.
      CHECK NOT ICDHDR[] IS INITIAL.
      LOOP AT ICDHDR.
       CHECK ICDHDR-UDATE IN XUDATE.
        CALL FUNCTION 'CHANGEDOCUMENT_READ_POSITIONS'
          EXPORTING
            CHANGENUMBER      = ICDHDR-CHANGENR
          IMPORTING
            HEADER            = CDHDR
          TABLES
            EDITPOS           = ICDSHW
          EXCEPTIONS
            NO_POSITION_FOUND = 1
            OTHERS            = 2.
        CHECK SY-SUBRC EQ 0.
        LOOP AT ICDSHW.
          CHECK ICDSHW-TEXT_CASE EQ SPACE.
          MOVE-CORRESPONDING ICDSHW TO ITAB.
          MOVE-CORRESPONDING ICDHDR TO ITAB.
          MOVE ICDSHW-TABKEY+3 TO ITAB-EKKEY.
          APPEND ITAB.
        ENDLOOP.
      ENDLOOP.
    ENDFORM.                    "GETCHGDOCS
    END OF PROGRAM
    *&      Form  Z_TOP_OF_PAGE
    FORM Z_TOP_OF_PAGE .
      IF NOT XEBELN-LOW IS INITIAL.
        CONCATENATE  XEBELN-LOW  ' ' 'To' ' '  XEBELN-HIGH INTO W_XEBELN
        SEPARATED BY SPACE.
      ENDIF.
      CONCATENATE  XUDATE-LOW6(2) XUDATE-LOW4(2) XUDATE-LOW+0(4) INTO XUDATE-LOW.
      CONCATENATE  XUDATE-HIGH6(2) XUDATE-HIGH4(2) XUDATE-HIGH+0(4) INTO XUDATE-HIGH.
      IF NOT XUDATE-LOW IS INITIAL.
        CONCATENATE  XUDATE-LOW  ' ' 'To' ' '  XUDATE-HIGH INTO W_XUDATE
        SEPARATED BY SPACE.
      ENDIF.
      IF NOT XLIFNR-LOW IS INITIAL.
        CONCATENATE  XLIFNR-LOW  ' ' 'To' ' '  XLIFNR-HIGH INTO W_XLIFNR
        SEPARATED BY SPACE.
      ENDIF.
      IF NOT XEKORG-LOW IS INITIAL.
        CONCATENATE  XEKORG-LOW  ' ' 'To' ' '  XEKORG-HIGH INTO W_XEKORG
        SEPARATED BY SPACE.
      ENDIF.
      IF NOT XEKGRP-LOW IS INITIAL.
        CONCATENATE  XEKGRP-LOW  ' ' 'To' ' '  XEKGRP-HIGH INTO W_XEKGRP
        SEPARATED BY SPACE.
      ENDIF.
    For writing Report Header
      FHEADER-TYP  = 'H'.
      FHEADER-INFO = 'Purchase Order / Contract Change History'.
      APPEND FHEADER.
      CLEAR FHEADER.
      CLEAR FHEADER-KEY.
      FHEADER-TYP = 'S'.
      FHEADER-INFO = W_XUDATE.
      FHEADER-KEY = 'Date'.
      APPEND FHEADER.
      CLEAR FHEADER.
      CLEAR FHEADER-KEY.
      FHEADER-TYP = 'S'.
      FHEADER-INFO = W_XEBELN.
      FHEADER-KEY = 'PO Number'.
      APPEND FHEADER.
      CLEAR FHEADER.
      CLEAR FHEADER-KEY.
      FHEADER-TYP = 'S'.
      FHEADER-INFO = W_XLIFNR.
      FHEADER-KEY = 'Vendor Number'.
      APPEND FHEADER.
      CLEAR FHEADER.
      CLEAR FHEADER-KEY.
      FHEADER-TYP = 'S'.
      FHEADER-INFO = W_XEKORG.
      FHEADER-KEY = 'Purchasing Org'.
      APPEND FHEADER.
      CLEAR FHEADER.
      CLEAR FHEADER-KEY.
      FHEADER-TYP = 'S'.
      FHEADER-INFO = W_XEKGRP.
      FHEADER-KEY = 'Purchsing Group'.
      APPEND FHEADER.
      CLEAR FHEADER.
      CLEAR FHEADER-KEY.
    ENDFORM.                    " Z_TOP_OF_PAGE
    *&      Form  Z_LAYOUT_SETTINGS
          text
    -->  p1        text
    <--  p2        text
    FORM Z_LAYOUT_SETTINGS .
      FS_LAYO-ZEBRA           = 'X'.     " Output in Zebra pattern
      FS_LAYO-DETAIL_POPUP    = 'X'.     " A popup window appears to give details
      FS_LAYO-KEY_HOTSPOT     = 'X'.     " Key fields will have a Hotspot.
      FS_LAYO-DEF_STATUS      = ' '.
      FS_LAYO-COLWIDTH_OPTIMIZE = 'X'.
    ENDFORM.                    " Z_LAYOUT_SETTINGS
    *&      Form  Z_ALV_EVENTS
    FORM Z_ALV_EVENTS .
      CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
        EXPORTING
          I_LIST_TYPE = 0
        IMPORTING
          ET_EVENTS   = FEVENTS[].
      READ TABLE FEVENTS WITH KEY NAME = 'TOP_OF_PAGE'.
      IF SY-SUBRC = 0.
        FEVENTS-FORM = 'Z_TOPOFPAGE'.
        MODIFY FEVENTS INDEX SY-TABIX.
        CLEAR FEVENTS.
      ENDIF.                              " IF SY-SUBRC = 0.
    ENDFORM.                    " Z_ALV_EVENTS
    *&      Form  Z_CREATE_FIELD_CATALOG
    FORM Z_CREATE_FIELD_CATALOG .
    for PO No.
      FCAT-FIELDNAME = 'EKKEY-EBELN'.
      FCAT-SELTEXT_M = 'PO No'.
      FCAT-FIX_COLUMN = 'X'.
      APPEND FCAT.
      CLEAR FCAT.
    for Change Date.
      FCAT-FIELDNAME = 'UDATE'.
      FCAT-SELTEXT_M = 'Change Date'.
      FCAT-FIX_COLUMN = 'X'.
      APPEND FCAT.
      CLEAR FCAT.
    for Time.
      FCAT-FIELDNAME = 'UTIME'.
      FCAT-SELTEXT_M = 'Time'.
      FCAT-FIX_COLUMN = 'X'.
      APPEND FCAT.
      CLEAR FCAT.
    for User Name.
      FCAT-FIELDNAME = 'USERNAME'.
      FCAT-SELTEXT_M = 'User Name'.
      FCAT-FIX_COLUMN = 'X'.
      APPEND FCAT.
      CLEAR FCAT.
    for Item.
      FCAT-FIELDNAME = 'EKKEY-EBELP'.
      FCAT-SELTEXT_M = 'Item'.
    FCAT-FIX_COLUMN = 'X'.
      APPEND FCAT.
      CLEAR FCAT.
    for Sch No.
    FCAT-FIELDNAME = 'EKKEY-ETENR'.
    FCAT-SELTEXT_M = 'Sch No'.
    FCAT-FIX_COLUMN = 'X'.
    APPEND FCAT.
    CLEAR FCAT.
    for Sch No.
      FCAT-FIELDNAME = 'FTEXT'.
      FCAT-SELTEXT_M = 'Text'.
    FCAT-FIX_COLUMN = 'X'.
      APPEND FCAT.
      CLEAR FCAT.
    for Sch No.
      FCAT-FIELDNAME = 'F_OLD'.
      FCAT-SELTEXT_M = 'Old Value'.
    FCAT-FIX_COLUMN = 'X'.
      APPEND FCAT.
      CLEAR FCAT.
    for Sch No.
      FCAT-FIELDNAME = 'F_NEW'.
      FCAT-SELTEXT_M = 'New Value'.
    FCAT-FIX_COLUMN = 'X'.
      APPEND FCAT.
      CLEAR FCAT.
    for Sch No.
      FCAT-FIELDNAME = 'CHNGIND'.
      FCAT-SELTEXT_M = 'Type of Changes'.
    FCAT-FIX_COLUMN = 'X'.
      APPEND FCAT.
      CLEAR FCAT.
    for Sch No.
      FCAT-FIELDNAME = 'CHANGE'.
      FCAT-SELTEXT_M = 'Changes'.
    FCAT-FIX_COLUMN = 'X'.
      APPEND FCAT.
      CLEAR FCAT.
    ENDFORM.                    " Z_CREATE_FIELD_CATALOG
    *&      Form  Z_REUSE_ALV_GRID_DISPLAY
    FORM Z_REUSE_ALV_GRID_DISPLAY .
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
          I_CALLBACK_PROGRAM      = SY-REPID
         I_CALLBACK_USER_COMMAND = 'Z_USER_COMMAND'
         I_CALLBACK_PF_STATUS_SET = 'SET_PF_STATUS'
          IS_LAYOUT               = FS_LAYO
          IT_FIELDCAT             = FCAT[]
          I_DEFAULT               = 'X'
          I_SAVE                  = 'U'
          IT_EVENTS               = FEVENTS[]
        TABLES
          T_OUTTAB                = ITAB[].
    ENDFORM.                    " Z_REUSE_ALV_GRID_DISPLAY
    *&      Form  Z_TOPOFPAGE
    FORM Z_TOPOFPAGE.                                           "#EC NEEDED
      CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
        EXPORTING
          IT_LIST_COMMENTARY = FHEADER[].
    ENDFORM.                                " FORM Z_TOPOFPAGE
    Edited by: Sudhanshu Jain on May 6, 2009 8:45 AM

  • Regarding CJ02 transaction

    Hi all,
    I am facing a problem regarding CJ02 transaction.
    The problem is when I am saving the classifications of the project it is not reflected back to the corresponding fields of respective table.
    It would be very helpfull if anybody sahres his/her any idea regarding this.
    Thanks in advance.

    Hi
    Is it the field name or the field value which u have given? Did u add custom fields to this table?
    Regards,
    Vishwa.

  • Regarding CS03 transaction

    Hi friends,
    I have a simple query regarding the transaction CS03. When I give the Material Number, Plant and BOM Usage as input, I would get the list of components for this material.
    Inside the transaction, is a CHECKBOX field ASM - this Indicates that the component for this material has its own BOM or has further components).
    Could anyone tell me in which SAP table this information is stored i.e. an indicator to tell us if the component/material has further BOM or not.
    I checked MAST and STPO tables but could not figure out the right field.
    Awaiting your valuable inputs.
    Thank You.
    Regards,
    Gayathri.

    hi gayathri,
    1.
    the bom can exist for HALB or FERT .
    u can dimnish the material not having a bom on this category .
    i.e to say material type 'RAW' dosent hav  a bom .
    2.
    like check out for table "MVKE" (Sales Data for Material) and in here check the fields
    MVKE-MTPOS (Item category group from material master)MVKE-DWERK(Delivering Plant).
    now giv the material and execute for initially dont giv a plant , and execute .
    proceed with parent-matrial in bom  and execute ,
    u'll see the list of materials assigned in a particular sales area now check for MTPOS status this will have a category called LUMF ( this u will hav only for parent)
    now say that the parent have 4 child materials (say)of which one has subassemblies so as u said it will hav a ASM check box ticked in CS03, now take this material and goto mvke and repeat the procedure and check the MTPOS status this will have item category like 'NORM'
    remember for parent it was 'LUMF'
    now for child(having subass;les) we got'NORM'
    now check for same which dosent have a subassemblies from the child items it will be like 'ZATP' or 'XXXX' but not LUMF or NORM.  to tell that it dosent hav further bom.
    generalise the conclusion for all the materials(parent childorphans)if found okay apply this logic.
    second alternative is ,
    check the transaxction cs12.
    give  BOm material and observe that the first field(dglvl) ...
    it indicates the level of that material in thta BOM.
    exact indiaction is whether it has sub assemblies in that Material is the
    field (BOMFL) If it has sub assemblies then it will be' X'.
    see if u can make any hit in the tables using this relation above
    regards,
    vijay.

  • Regarding ME22n Call Transaction method

    Hi,
       i am working on BDC Object, in this object i am attaching  output type 'XXX' in messages for each purchase order(ME22n).For example if i am taking multiple range of purchase orders.It shows following message whenever i m executing in no screen mode.
    ' No batch input data for screen SAPMSSY3 0121' and Call transaction return code is 1001.
    If i am  debugging the same object in All Screen mode its working fine.
    SAP Version is 4.6c
    I Searched all the relvant threads but i am not able get the Soloution.
    Can any one please help me regarding this.
    Thanks and Regards,
    kishore.

    ME22N is an enjoy transaction, officially not compatible with BDC. (Look at OSS [Note 217437 - ME21N/ME51N: Batch input and CATT not possible|https://service.sap.com/sap/support/notes/217437] and [actually search at sdn|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=me22n+bdc&adv=false&sortby=cm_rnd_rankvalue])
    Try to use [BAPI_PO_CHANGE|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=bapi_po_change&adv=false&sortby=cm_rnd_rankvalue] (BUS2012) which exists in 46C even if not officially released.
    Regards

  • How to execute ME22N transaction in background.

    Hi experts,
    How to execute ME22N and ME23N in background, when execute the transaction in background, , it should generate a spool, with out any printpreview. How can we do this....?
    thanks

    Hi,
    Write a BDC program for updation of tables for u r user-exit.
    After that Schedule u r program in back gound job scheduling.
    Using  SM36 - Define Background job.
    Give the job name and Press job wizard button.
    It's asking about job name and job class -prioritty.
    press continue and give program name .
    Select radiobutton based on u r requirement.
    Then specify periodic job or only in holidays.
    Then u select hours and all.
    In SM37 give u r job name and and press execute.
    Reward if useful.
    Regards,
    Narasimha

  • Doubt Regarding MIGO Transaction

    Hi,
    Where exactly the source code of MIGO transaction fills these two fields : BED , SED  (Note: Under the Tab Excise Invoice).
    Thanks & Regards,
    Lakshmi.

    ok

  • Doubt regarding SHDB transaction

    Hi All,   
                I have a doubt regarding the Process Tab in the application tool bar of SHDB transaction. What is the use of the following check boxes?
    1)       Default Size
    2)       Cont.after commit
    3)      not a batch input session
    4)      END: Not a Batch Input session
    5)      Simulate Background mode

    Hi,
    Basically these are the properties for CALL TRANSACTION using. You need not worry about these unless you really need those.
    1) Default Size: it will set the Default screen size for CALL TRANSACTION USING...
    2) Cont.after commit : it will set indicator that CALL TRANSACTION USING... is not completed by COMMIT. after commit also the process will continue
    3) not a batch input session: sets indicator that present session is not batch input
    4) END: Not a Batch Input session
    5) Simulate Background mode : session will be run in foreground. but similar to back grpund
    you can see the documentation by placing the cursor on these and click f1.

  • Problem in me22n transaction

    Hi friends ,
    i am facing to find the bug in an user exit.ur  experiences can help me to  fix that easily .
    Scenario  : when we click on  save in me21n or me22n  , it prompts a dilogue box for reason codes , for each PO created in case of me21n and for each new line item that is being updated in case of me22n while we click next item on dilogue box . at the end it gives a message saying that last line item is reached  . finally we click update on dilogue box , they are  saved in database .
    Problem : it s going well in case of me21n , but in case of me22n , when click on update it is again prompting for reason code for last item for (last item no  -1) times before saving in database.  for ex : 5 new items are there to update . aftere entering reason codes for all line items while clickingon  next item ,message is prompted that last item is reached . then we choose update , it again prompting dialogue box for reason code for last item 4 times .we need to enter 5+ (5-1) times .
    My Analysis : dilogue box is prompted by a function module called in that  exit.there he is looping an itab constructed with new items and reason codes captured  while we entered .

    Hi,
    Only an User exit is enough for you to achieve this at item level.
    In the Main program of PO SAPMV50A  search for the include MV50AFZZ * or MV50AF* (i am not sure, take the right one for User exits and write the code for Item level
    such that : if the Indicator = N, then modify the field Vendor.
    regards.
    Anji

  • Add cost center in ME21N, ME22N transactions

    Hello,
    I need to add two columns  in item overview in transaction ME21N for cost center and PEP element. Please, could anyone tell me how I can do this?
    Thanks very much.
    Ana.

    >
    Ana Maria Garcia Tomas wrote:
    > Thanks for answers.
    > I have cost center for K account asigment but in detail item screen, I need to add a column for this field in item overview. How could I add it?
    > Best regards.
    > Ana.
    This requirement can only be fulfilled with help of ABAP.

  • Regarding FBL1N transaction

    Hi All,
    In transaction FK03 i am able to view full name of vendor but when i am going for transaction FBL1N for the same vwndor i am not able to see full name there, last few characters are missing there. Can you please tell me how can i increase the lenght of vendor name in FBL1N transaction?
    Thanks.

    Hello,
    The output of  the name is 'just' possible until the 35th character.                                                                               
    The reason is the following:                                                                               
    In the creation of the master data, the 'address' data is stored in        
    two different areas, first in the master data table (LFA1) and in the      
    specially created 'address information' tables.                                                                               
    Out of the technical design of the 'header setup' for the line item        
    display transactions, 'only' the LFA1 master data table is accessed.                                                                               
    As the field only contains 35 characters in this table LFA1, only these    
    will be displayed.                                                                               
    The restriction within some functions about the 'display' length of        
    the address information is also mentioned in a warning message you         
    receive, if you store a value which is 'bigger' then 35 characters:                                                                               
    The use of the last 5 characters in field NAME1 is restricted (40 of 40)   
    Message no. AM228                                                                               
    Diagnosis                                                                  
    The address data in field NAME1 exceeds the 35th position (40 of 40        
    characters occupied).                                                                               
    System Response                                                            
    In this form the data can be saved and used up to the complete length      
    of 40 characters.                                                          
    In some scenarios, the system only uses the first 35 characters of name    
    fields.                                                                               
    REgards,
    REnan

  • Regarding XK02 transaction in SAP ECC 6.0 Version

    Hi All,
    I am working with an object which calls a transaction <b>XK02</b> to modify the name and contact details fields in  Version <b>SAP ECC 6.0</b>.
    The problem is that, when the transaction is run manually and saved or when an SHDB Recording is created, the data is getting updated.
    But when the transaction is called from a program or when the SHDB Recording which is already created is run, the data is not getting updated in Version SAP ECC 6.0.
    The data is getting updated properly when it is done in Version SAP 4.6b.
    Central Address Management System is used here.
    Can anybody please help me in this regard?
    Thanks & Regards,
    Vaitheeswaran.

    Hi Prabhu,
    The call transaction statement is running smoothly. The SY-SUBRC is 0 for this.
    The thing is, there is a Check Box at the end of the screen called 'Use Central Address Management' when the SHDB is created.
    If this is checked, the contact details are stored in ADRC and LFA1 tables and only in LFA1 if not checked.
    In the new version SAP ECC 6.0, the data should also get populated in the ADRC table.
    There is a slight change in the logic in SAP ECC 6.0 version.
    Thanks & Regards,
    Vaitheeswaran.

Maybe you are looking for