BADI for ME51n screen exit

hi guys,
             i have to add a new tab with three fields  under header level in me51n, i have used enhancement MEREQ001 but it is adding under item level only..so, guys can you please tell is there any BADI for this..,thanks in advance.
regards,
anand.

Hi,
As i know there is no possibility to add custom tab at header level better to go with item level.If need help here check and post.
Regards,
Madhu.

Similar Messages

  • Badi for fv05 screen exit

    hi all,
    i am finding the badi for fv05 screen exit.
    please tell me the badi for fv05 screen exit.
    thanks
    Sachin
    Edited by: Sachin Gupta on Jul 1, 2009 4:00 PM

    S0006595706 wrote:>
    > hi all,
    >
    > i am finding the badi for fv05 screen exit.
    >
    > please tell me the badi for fv05 screen exit.
    >
    >
    > thanks
    > Sachin
    >
    > Edited by: Sachin Gupta on Jul 1, 2009 4:00 PM
    Hi,
      Please use the following program to find out exits and badis by entering tcode to the program
    *& Report  Z_FIND_USEREXIT
    report  z_find_userexit.
    *&  Enter the transaction code that you want to search through in order
    *&  to find which Standard SAP User Exits exists.
    *& Tables
    tables : tstc,     "SAP Transaction Codes
             tadir,    "Directory of Repository Objects
             modsapt,  "SAP Enhancements - Short Texts
             modact,   "Modifications
             trdir,    "System table TRDIR
             tfdir,    "Function Module
             enlfdir,  "Additional Attributes for Function Modules
             tstct.    "Transaction Code Texts
    *& Variables
    data : jtab like tadir occurs 0 with header line.
    data : field1(30).
    data : v_devclass like tadir-devclass.
    *& Selection Screen Parameters
    selection-screen begin of block a01 with frame title text-001.
    selection-screen skip.
    parameters : p_tcode like tstc-tcode obligatory.
    selection-screen skip.
    selection-screen end of block a01.
    *& Start of main program
    start-of-selection.
    * Validate Transaction Code
      select single * from tstc
        where tcode eq p_tcode.
    * Find Repository Objects for transaction code
      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 = enlfdir-area.
            move : tadir-devclass to v_devclass.
          endif.
        endif.
    * Find SAP Modifactions
        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.
    * Take the user to SMOD for the Exit that was selected.
    at line-selection.
      get cursor field field1.
      check field1(4) eq 'JTAB'.
      set parameter id 'MON' field sy-lisel+1(10).
      call transaction 'SMOD' and skip first screen.
    Edited by: Dande on Jul 1, 2009 2:27 PM
    Edited by: Dande on Jul 1, 2009 2:30 PM

  • Any userexit or badi for Me51n or me52n

    Any  user exist  or badis for  Me51n or me52n if
    Material Profit center ,v/s Plant profit center  or v/s WBS profit
    center not matched then PR should not saved.
    Moderator message: please do some own research before asking.
    [Asking Good Questions in the Forums to get Good Answers|/people/rob.burbank/blog/2010/05/12/asking-good-questions-in-the-forums-to-get-good-answers]
    Edited by: Thomas Zloch on Feb 21, 2011 2:01 PM

    Hi,
    Please check this thread for the procedure to find the BADI for a transaction
    http://searchsap.techtarget.com/tip/0,289483,sid21_gci1276392,00.html#
    Or
    You goto se24 and specify the class CL_EXITHANDLER and in that double click on GET_INSTANCE method in that put a break point on the line 
    CALL METHOD cl_exithandler=>get_class_name_by_interface
    and run you transaction... for almost every action you will get this method trigger and in that check the exit name... And that's the BADI for the interaction made in that transactation.
    Please go through this link for Finding BADI using class CL_EXITHANDLER in detail.
    [Finding BADI|http://abapreports.blogspot.com/2008/06/badi-finding-in-abap.html]
    Hope this would help you.
    Good luck
    Narin
    Edited by: Narin Nandivada on Aug 19, 2008 5:30 PM

  • Required BADI for Overiew screen of PA20 and PA30

    Dear All,
    I need BADI for Overiew screen of PA20 screen as i have to restrict end user not to see the data.
    As of know i am able to see the BADI for display but not able to find the BADI for overview.
    Thanks
    Rav Jordan

    Hi,
        For pa20 screen Check with this badi  HRPAD00AUTH_CHECK.
    I hope it is useful to u.

  • Someone has a tutorial for creating screen exit?

    I have a development and I do not know how to create screen exit.
    Case Someone has a tutorial for creating screen exit please help me
    Thank you
    <b><i>Wagner Duarte
    Consultant - SAP ABAP</i></b>

    hI
    Screen Exit is nothing but enhancing the screen like creating some more fields, subscreen and so on.
    1. Go to the screen>System>Status-->Program (Double
    click this program. It will take you to the program.
    2. Now, Goto-->Object Directory Entry.
    3. Make a note the package name.
    4. Now run the transactions SMOD, press F4 and enter the
    above noted package, press enter.
    5. It will display list of Exits.
    6. Now go back to the initial screen SMOD.
    7. Specify the exit name here and select the radio button
    Components.
    8. It will display four group boxes one for FM, second
    for Fcodes, thrid for Screen areas and last for
    includes.
    9. Goto transaction CMOD, create a new project, and
    click the button "Enhancement assignments" and
    specify your enhancements that you got in SMOD.
    10. Now bouble clikc the enhancement, it will take you to editor with some includes starting with Z, double clikc the include you want to edit and proceed.
    Have a look at below link It will definately help you to undestand the same.
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    check these links.
    http://help.sap.com/saphelp_46c/helpdata/en/c8/1975e643b111d1896f0000e8322d00/frameset.htm
    http://www.allsaplinks.com/screen_exit.html
    USER EXITS
    https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=312792
    https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=1320078
    https://forums.sdn.sap.com/click.jspa?searchID=672084&messageID=2669896
    How to implement screen exit for a SAP standard transaction
    Introduction
    SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
    To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
    To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
    An append structure in the database table with the new fields.
    A subscreen area into the standard screen – where the programmer can attach his subscreen of his own program with the new fields.
    A function group under which the new subscreen has to be created with the new fields.
    Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen – so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
    Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
    Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
    Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
    Pre-Requisites
    The developer to work on screen exit should have essential knowledge on the following:
    DDIC concepts, including the knowledge of append structure.
    Concept of SAP Enhancements and implementing them using Projects.
    Concept of function exits.
    Knowledge on Module Pool – including subscreens, Tabstrip controls etc.
    Steps
    Guidelines
    So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
    Find out the Required Enhancements
    Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton ‘SAP Applications’. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest – for e.g., Purchasing, Asset Accounting, etc.
    Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
    Utilize the Enhancement in a Project
    After you have found one, do as directed in the documentation. Generally, the steps are as follows:
    Create a project using CMOD including your enhancement.
    Create the append structure with new fields.
    Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
    Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
    Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
    Activate the project.
    Test to ensure that required functionality are met.
    Case Study 1
    Add three new custom fields for Asset master and maintain information for them
    Requirement
    Three fields in the legacy system have to be maintained in Asset master. These fields are:
    Original Asset number – 20 characters
    Location 2 – 15 Characters.
    Model no – 20 characters
    Location 2 should start with ‘L’.
    Pre-Analysis
    Finding out the Enhancement
    As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
    Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
    Studying the Function Exits
    The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
    EXIT_SAPLAIST_002
    Function module Level Documentation
    This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
    Import Parameters
    Understanding
    This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
    EXIT_SAPLAIST_003
    Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
    Understanding
    This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
    Studying the Documentation of the Enhancement
    The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
    Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
    Deciding the Final course of Action
    After making all the investigations, the final course of action was determined.
    SrlNo Step Justification
    A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
    Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
    A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be ‘CUST’ (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
    In the PAI of the subscreen, validation for Location to start with ‘L’ will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
    In the custom include of the function exit module ‘EXIT_SAPLAIST_002’, the following code will be written:-
    ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
    In the custom include of the function exit module ‘EXIT_SAPLAIST_003’, the following code will be written:-
    E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
    Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done – otherwise, the new custom subscreen will not be displayed in the Asset master screens.
    Development
    Creating a Project to include the enhancement
    Go to transaction CMOD and create a project.
    Enter a description for the project. Then, click on the pushbutton ‘Enhancement Assignments’ in the Application Toolbar.
    Enter the name of the enhancement and Save.
    Go to ‘Components’.
    Creating Custom Include for ANLU
    The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
    Create the include structure with three new fields, as required. Then, save and activate it.
    Develop the subscreen and the program
    Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
    Create it as subscreen.
    Then, go to the Layout of the screen and create three new fields from Database table ANLU.
    Drag the fields in the screen body and place them.
    Then, save and activate the screen and come back to screen flow editor.
    Create the PAI module to add validation for field “Location 2”, as required .
    Activate the whole function group and come out.
    Write code in the Function Exits to synchronize the programs
    Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
    Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
    Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
    Then, activate everything – the whole project and come out.
    Complete the configuration to link the subscreen
    The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
    Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
    Here, the requirement is to create these three custom fields in the tab page ‘General’ of asset master screen ( AS01/AS02/AS03/AS91).
    Determine the Layout
    To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class ‘1000’ and click on folder ‘General Assignment of Layout’.
    Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout ‘SAP’ cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
    Create new tab layout
    Go to transaction AOLA. Copy the tab layout ‘SAP’ to create another layout, say, YSUB.
    System will copy all the settings and will inform you about that.
    Select your newly created layout and double-click on the folder ‘Tab page titles’.
    You want to put your custom fields in the tab page “General”. So, select this tab page entry and double-click on the folder "Position of Groups".
    Here, all the field groups currently residing in the tab-page “General” are shown. Add an entry for your newly created fields.
    Select the group box from the list. An entry will come with “U” padded with the custom subscreen prepared by you.
    Then, save and come out.
    Assign the new Layout to Asset Class
    Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
    Save and come out.
    Test the Exit
    Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to them…save. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
    Original Source: ittoolbox.com
    Screen Exit is nothing but enhancing the screen like creating some more fields, subscreen and so on.
    1. Go to the screen>System>Status-->Program (Double
    click this program. It will take you to the program.
    2. Now, Goto-->Object Directory Entry.
    3. Make a note the package name.
    4. Now run the transactions SMOD, press F4 and enter the
    above noted package, press enter.
    5. It will display list of Exits.
    6. Now go back to the initial screen SMOD.
    7. Specify the exit name here and select the radio button
    Components.
    8. It will display four group boxes one for FM, second
    for Fcodes, thrid for Screen areas and last for
    includes.
    9. Goto transaction CMOD, create a new project, and
    click the button "Enhancement assignments" and
    specify your enhancements that you got in SMOD.
    10. Now bouble clikc the enhancement, it will take you to editor with some includes starting with Z, double clikc the include you want to edit and proceed.
    and you just go through these links also
    Screen exit
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    screen-exits
    Check the following link.
    https://www.sdn.sap.com/irj/sdn/advancedsearch?query=how%20to%20find%20screen%20exits&cat=sdn_all

  • Different scenarios for implementing screen exits

    Hi all,
    Is there different scenarios for implementing screen exits for different applications such as MM,SD....etc.

    Hi all,
    Is there different scenarios for implementing screen exits for different applications such as MM,SD....etc.

  • BADI for ME51N to add new TAB(screen)

    Hi,
    Is there any BADI or Screen Exit to add a new TAB at item level in Purchase Requsition (ME51n) ?
    Thanks

    Hi,
    Check below link
    https://www.sdn.sap.com/irj/sdn/forums
    Regards,
    Prashant

  • Exit/badi for me51n

    Hi Folks,
    My PO ordered quantity is greated than my PR quantity and that's because PR is not set to closed. Is there any way how to close the PR using exit/badi?
    Thanks!

    Dear Friend,
    U r creating PO with Reference to PR.
    if u r  doing like this u can check that at the PO Level itself.
    For this u can use the EXIT or BADI.
    Then Function group for the PO is XMO6 . in this there is one include . Include ZXM06U43
    Please Implement this Exit. this will trigger at the Check function of the PO.
    So u can restrict ur PO at the time of Creation..
    2 BADI for this is ME_PROCESS_PO_CUST.
    This BADI contains some many methods.
    For ur Requirement just implement Process_item method .
    Hope this will Help u.
    With Regards,
    Sumodh.P

  • BADI for ME51N

    Hi,
    Is there any BADI or Screen Exit to add a new TAB at item level in Purchase Requsition (ME51n) ?
    Thanks

    hi ,
    You can find the BADI In diffrent approches, finding thourgh class CL_EXITHANDLER is 1 method.
    Here are the steps.
    1. Go to Tcode SE24
    2. In object type specify object name as CL_EXITHANDLER
    3. Double click on method - GET_INSTANCE
    4. on line no 25 , i.e. is case statement, set a debug point
    5. execute any desire transaction code in a new screen for which
    you want to find a BADI
    6. it will take you in debugging mode, debugging the program
    press F5 until you are in method
    CALL METHOD cl_badi_flt_data_trans_and_db=>act_imps_per_flt_val
    7. check the value of exit_name in exporting parameter
    8. it will list all badi's available for that transaction
    2)Finding thourgh SQL TRACE ST05 is another apporach,see the blog
    /people/alwin.vandeput2/blog/2006/04/13/how-to-search-for-badis-trace-it
    Note : pls reward points if this is helpful to you.
    thanks & Regards,
    sravan.

  • Badi  for ME51N Item changes

    Hi ,
      Is there any Badi or user exit to make changes to the line item data in the purchase requisition create/change ME51N or ME52N transactions. We would want to populate few fields automatically on the item data, so would request if any of you have worked on any Badi for this transaction, please do post in immediately.
    Thanks,
    Sowmya

    Hi,
    1)BADI to be implemented: ME_PROCESS_REQ_CUST.
    Method to be used: PROCESS_ITEM.
    Place the below code in your implementation.
    data : l_item type MEREQ_ITEM.
    CALL METHOD im_item->get_data
    receiving
    re_data = l_item.
    *C-- L_ITEM-BEDNR is requirement tracking number
    2)Exit in ME51N
    MEREQ001 Customers' Own Data in Purchase Requisition
    You can implemet by this way
    You add your customer fields, which should be saved in the database, to
    the include CI_EBANDB (in table EBAN). You can also add customer fields
    that you want to use during the program run to the include CI_EBANMEM
    (in structure MEREQ_ITEM) These fields are not stored in database table
    EBAN.
    <b>Reward points</b>
    Regards

  • UserExit/ Badi for me51n ( Version Details )

    Hi Experts,
    In transaction ME51n for Purchase Requistion for line item in Version TAB , I want to capture the Status "version completed" checkbox in a User exit or BADI and want to put a validation on the checkbox. I have  list of all UserExits and Badi's
    which are available for me51n. But none of them capture the Version TAB details in me51n. Version Details are available in EREV table.  EREV table details are not available in any of the UserExits and BADI's. No structure is available for that in User exits / Badi's.
    Also I want to know about BTE's. What are BTE's? Can BTE be used for ME51n transaction? If yes . what is the procedure  for the same?
    Please suggest a solution for the same as soon as possible.
    Thanks in Advance.

    Hello Priti,
    For BTE ref following doc-
    http://help.sap.com/saphelp_erp2004/helpdata/en/ee/e87988027a11d5a7d60000e83dda02/content.htm
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/207835fb-0a01-0010-34b4-fef1240ba9b7
    Thank You,
    Nishikant.

  • BADI for ME51N  purchase requisition

    Dear All,
    i want to use user badi for transaction ME51N as i want to put a check for cost centre with plant such that if it does not belong to a particular plant it should throw an error message
    i hav found one BADI
    ME_PROCESS_REQ_CUST
    wherein in one of the methods(PROCESS_ITEM) i m getting
    Plant directly but i have searched all method and i m able to get costcentre(*KOSTL) in methods like 
    IF_ACCT_CONTAINER_MM~LOOKUP
    now if i m trying to use this method its saying either method unknown or private or protected
    can anyone plz help me with the syntax of using methods having such format as above i know the syntax to access normal methods like getdata or getitem and so on.
    Ronak

    Hi Ronak,
    Your input parameter in PROCESS_ITEM (IM_ITEM) is an object of class IF_PURCHASE_REQUISITION_ITEM. You can get all item data by using:
    DATA:
      zls_item TYPE MEREQ_ITEM.
    zls_item = IM_ITEM->GET_DATA( ).
    Regards,
    John.

  • Change log data is NOT captured for PO screen exit fields

    Hi,
      We created a new tab at item level for PO Screen(ME21N) for the purpose of STOs(Document Type UB) & created 3 New fields in that new tab through Screen Exit( SAPMM06E, SAPLXM06 0111 ).
      When we are entering data in those 3 new fields while creating new STOs, those data are captured in EKPO table.
      When we are changing the OLD STOs for those 3 new fileds, data is modifying in EKPO table. But changes are NOT inserted in CDHDR and CDPOS table for those 3 new fields.
      <b>Please help us to track the changes in those 3 new field data changes for old  STOs.</b>
      Please let me know if you need any further clarification regarding this.
    Thanks & Regards,
    Mani.

    Hai Naimesh Patel,
          Thanks for your promptly reply.
          Now My issue has been resolved successfully with your help.
          I rewarded Points for your reply.
    Thanks & Regards,
    Mani.

  • ME51N screen exit

    Hi All,
    In ME51N t-code  PR Creations,
           I have used enhancement  MEREQ001, In this I have used to Screen exit as Below:
                    Screen exit                    SAPLMEGUI                      0014 SUB0     SAPLXM02                       0111
    Now Please tell me from where and how to calll this screen sub-screen 0111 created in the exit.
    Thanks & Regards,
    Amit Y.

    Hi,
       You have to create SAPLXM02 0111  which is already getting called by the calling screen SAPLMEGUI 0014 so once you create this screen it should automatically come on the PR creation screen.
    Regards,
    Himanshu

  • Exit / BADI for ME51N / ME52N

    Hi experts,
    I have the following requirement:
    1. In transactions ME51N / ME52N, the long text field for the item (Item Text) must be made read-only if the PR is already approved / released (release strategy indicator = '2').
    2. The PR workflow approvers must recieve an e-mail if this text has been changed while the PR is still blocked / not fully approved (release strategy indicator = 'X').
    I'm guessing both can be achieved through BADI implementations (in this case, IF_EX_ME_REQ_POSTED~POSTED), but I've read a lot about various Exits in these transactions, and now I'm not sure if this is the right one. Can you help me?
    PS.: I'm not completely familiar with BADIs and Exits, so please bear with me on this.

    Thanks for the replies.
    The MM consultant is still looking for a way to grey out the text field within SPRO. It's not an easy requirement
    Regarding the text changes, I followed your advices and I'm now trying to implement my code within the exit EXIT_SAPLMEREQ_005 (it's triggered right after the user saves the document, so it makes sense). The problem now is that when this exit is called, the changes made to the item text are already committed, and I can't compare the new text with the old one.
    I also tried implementing ME_REQ_PROCESS_ITEM, but it doesn't seem to be called from ME52N.
    Isn't there a log for long text changes? It would be really easy to just read CDHDR / CDPOS and know if the text has been changed. Also, is this text the same text from material master? If it is, I guess it would be easier to log its changes, right?
    Will appreciate your input on this.
    Regards,
    Leo

Maybe you are looking for

  • ME23N - Read Last Purchase Order for Display

    Hi, We are upgrading from 4.6C to ECC6 and one of the problems the users have identified is that when displaying the purchase order with transactions ME22N or ME23N the last purchase order that was worked on is not always the one that is displayed. T

  • A solution for notes, non-icloud email, itunes

    Wondering if anyone out there can see what I have done... ok, let me explain... Up until an hour ago, I was syncing my iphone4s, ipad2 & Mac "manually" in itunes so my calendar, "notes", contacts updated on all the devices. At this point, I need to m

  • Behaviour of thread in multicore processor

    hiii i want to know how thread behave in the multicore processor. wt i know is that at a time only one thread is running in case of single processor. but wt happen if i hv multicore processor means can 2 threads run at a time in multicore proccessor.

  • How to run .cmd file from a Powershell script

    Hi, I would like to know how I run commands from a powershell script? how to use the invoke-command? This powershell script doesnt work for me Invoke-Command C:\setup.cmd -ArgumentList install-setupforced

  • Access Reports to CR

    Does or will SAP have some conversion in the future to take Access Reports ---> Crystal Reports?? I am aware of some on the market but would be nice is CR has the feature built-in. Edited by: palta_s on Jan 12, 2011 5:44 PM