Screen Exit in Header Level in ME51N

Hi,
Are there any screen exits in header level in ME51N screen? I need to call a BSP upon the click of a button and when the user selects a line item from there, it has to fall as a line item in the PR screen.
Need your help on this.
Thanks and Regards,
Manideep Settipalli

Hello,
Please refer to this very useful document about finding user-exits, BADI's eg.
Methods to find Customer/User Exit's & BADi's for a Transaction Code!
Regards
Ali Murat

Similar Messages

  • Screen Exit for Header ME51N

    Hi experts, there is some screen-exit for HEADER of ME51N??
    I've found only MEREQ001, but it has a screen exit only for item requisition...
    Thanks.
    Alexandere

    Hi,
    check the following screen exit Information for Enhancement "MEREQ001"
    Calling screen     No.   Area       Called screen     No.
    SAPLMEGUI       0014 SUB0     SAPLXM02        0111
    also find the following user-exits
    EXIT_SAPLMEREQ_001             Export Data to Customer Subscreen for Re
    EXIT_SAPLMEREQ_002             Prepare Customer Subscreen for Requisiti
    EXIT_SAPLMEREQ_003             Import Data from Customer Subscreen for
    Regards
    Sreeni

  • Screen exits on Notification level

    Can any one let me know the screen exits at notification level....
    kindly refer my Enhancements ... points will be given for valid or
    useful reply....

    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.
    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 this Link
    http://www.sapbrain.com/TUTORIALS/TECHNICAL/user_exits_tutorial.html
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    check this http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    Regards,
    Deepu.K

  • Adding a new tab in the header level of me51n

    Hi gurus
        I want to add a new tab in the header level of purchase requisation (me51n/me52n) , where i want to add some new customer fileds and i will update those in a z table.
    how can i do it . please give the complete code if possible .
    thnks in advance.
    regards
    amarendra

    you can try the enhancement MM06E005, based on the Document category you can show the fields on the screen.

  • Additional Data in Header Level for ME51N / ME52N / ME53N

    Dear Gurus,
    I have one requirement related to apply enhancement for additional fields in purchase requisition header level.
    After searching a lot , I dint found any solution for this.
    Does anybody have any solution for this.
    Regards,
    Shibashis.

    I need to add on Tabstrip "Account assignment" for fields
    CO Area and Cost Center text field description ( right side ) for each one.
    How can I do this? Thanks in advance.

  • Me21n screen exit in item level

    Dear Experts I have a reqment to add a column of date in the table contol pf the po item.
    I have used the exit mm06e005 but it is not reflecting in the tem level.A new tab is created named customer data and the date fiels is ahowing in the header data.Can any one give me a step by step procuder of the above scenario??

    Hey Sayandeep,
      In the Flow Logic Process Before Output (PBO) create one module or in Module status_0101 write this code.
    V - Change
    A - Display
    H - Create
    if i_trtyp = 'A'.
        loop at screen.
          if screen-name = 'Screen Field Name'.
            screen-input = 0.
            modify screen.
          endif.
        endloop.
      else.
        loop at screen.
          if screen-name = 'Screen Field Name'.
            screen-input = 1.
            modify screen.
          endif.
        endloop.
      endif.
    Note: Try to avoid hot coding the transaction Code.
    Regards,
    Saravanan M

  • Screen exit for FB60 on header level

    hi , i am working on FB60 .  i want to add an extra tab  i.e extra screen on the header level . are there any screen exits for fb60 to add extra screen?

    hi praveen,
    search this forum on how to implement a badi if you haven't done one before. also, go to transation SE18 and read the documentation on badi_fdcb_subbas01 which clearly says that its used for FB60... see the example how they have used it by going to menubar Implementation->Overview then choose FI_FDCB_SUBBAS01_EX (Example for Screen Enhancement 1 on FDCB Basic Data Screen)...you should look at the method PUT_DATA_TO_SCREEN_OBJECT and tab Subscreens where the screen exits are available to use.
    In FB60, if you go to menubar System->Status and check the Program (Subscreen) and Screen Number, you'll see it'll match the program name and screen no. provided in the Subscreen tab of the BADI.
    Hope this helps.
    Cheers,
    Sougata.

  • 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.

  • Screen exit in VA01

    HI gurus,
    I need to add some custom fields in VA01 tcode in header level Additional DATA B Tab and also in item level.
    i came to know in SDN we can do it using screens 8309 & 8310. I didn't implement them before ...
    can anyone provide step by step procedure for this enhancement?
    thanks in advance
    Regards
    Giri

    Hi Giri,
    Previously in my project I also got the same requirement to use Header Level and Item Level additional B tab's for adding some extra custom fields which should be filled based on the Billing Plan data. So for this requirement I have used screen's 8309 (Header Level) and 8459 (Item Level).
    In order to use these screens you need to first of all get the access keys from the BASIS people.
    Proceed as follows.
    1. Execute SE51 and input the program name as SAPMV45A
    2. Input the Screen number as 8309 or 8310 and press change.
    3. System will ask you for the access key. Take the screen shot of the same and send it to BASIS team requesting for the access key. Similarly you'll also be needing the access keys for the following Include programs as well for Declaring Variables etc... and other processing logic.
    MV45ATZZ, MV45AOZZ, MV45AIZZ
    Similar is the procedure for Item level screen modification.
    4. Once you get the access key go ahead and change the screen to add the fields according to your requirement.
    5. After completing the layout part you need to create PBO and PAI modules starting with ZZ as prescribed by SAP and then implement them.
    Refer to the following link about User Exits prescribed by SAP.
    [http://help.sap.com/saphelp_46c/helpdata/en/1c/f62c7dd435d1118b3f0060b03ca329/content.htm]
    Hope this is helpful to you. Reward accordingly.
    Thanks and Regards,
    Maddineni Bharath.

  • Issue with Method to find Screen Exit

    Hi all,
    I am planning to add 2 custom fields to item details tab in ME51N .
    I tried to find screen exits using development class of ME51N i.e ME
    I went to smod and tried to find enhancements using ME development class and from the list of enhancements i tried to find a screen exit but i could found one.
    I found an enhancement
    MEREQ001   Customers' Own Data in Purchase Requisition
    Which had a screen exit  as well and this is what i was exactly looking for.
    But my question is that
    MEREQ001 is under development class MEREQ
    So that means the way i was trying to find the screen exits is wrong or is there a better way to find screen exits
    Let me know
    Thanks

    Hi,
    U will find that if u try this program.
    How to Find a Screen Exit in a Given SAP Standard T-code
    Program
    REPORT YSMOD2 .
    TABLES: MODSAP, MODACT, TSTC.
    PARAMETERS: INPUT1 LIKE TSTC-TCODE DEFAULT ' ',
                INPUT2 LIKE MODSAP-TYP DEFAULT ' '.
    DATA: SEARCH1(6),
          SEARCH2(3),
          SEARCH3 LIKE MODSAP-MEMBER.
    DATA : FIRST_ROW VALUE 'Y'.
    CONCATENATE: '%' INPUT1 '%' INTO SEARCH1,
    '%' INPUT2 INTO SEARCH2.
    SELECT * FROM TSTC WHERE TCODE LIKE SEARCH1.
    FIRST_ROW = 'Y'.
    CHECK TSTC-PGMNA NE SPACE.
    CONCATENATE '%' TSTC-PGMNA '%' INTO SEARCH3.
    SELECT * FROM MODSAP WHERE TYP LIKE SEARCH2
    AND MEMBER LIKE SEARCH3.
    SELECT SINGLE * FROM MODACT WHERE MEMBER = MODSAP-NAME.
    IF FIRST_ROW EQ 'Y'.
       WRITE: /0 TSTC-TCODE, 6 TSTC-PGMNA, 16 MODSAP-NAME, 32 MODSAP-TYP,
              45 MODSAP-MEMBER, 70 MODACT-NAME.
       FIRST_ROW = 'N'.
    ELSE.
       WRITE: /16 MODSAP-NAME, 32 MODSAP-TYP, 45 MODSAP-MEMBER, 70 MODACT-NAME. 
    ENDIF.
    CLEAR : MODSAP, MODACT.
    ENDSELECT.
    IF SY-SUBRC NE 0.
       WRITE : /0 TSTC-TCODE, 6 TSTC-PGMNA, 30 'No exits found'.
    ENDIF.
    CLEAR TSTC.
    ENDSELECT.
    END-OF-SELECTION.
    CLEAR: SEARCH1, SEARCH2, SEARCH3.
    End
    Regards,
    Jagadish

  • Screen exit for ME51N in header

    Hi friends,
    Is there any screen exit for ME51N(Purchase requisition) in header level.I found MEREQ001 enhancement, but this is for item level.please help.
    regards,
    Thoufique.

    Hi Thoufique,
    try the following screen exits:
    EXIT_SAPLMEREQ_001 Export Data to Customer Subscreen for Re
    EXIT_SAPLMEREQ_002 Prepare Customer Subscreen for Requisiti
    EXIT_SAPLMEREQ_003 Import Data from Customer Subscreen for
    Also, for more help on your problem, refer to the following link:
    Re: re: screen exits
    Hope this will help you...

  • Screen exit for me32k for header and for items

    hi experts,
    i need a screen exit  from me32k to add subscreen in :
    1. items
    2. header
    thanks in advanced,
    dana.

    Hi,
    Just some information on screen exits:
    Screen Exit:
    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
    User Exits:
    User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
    The naming standard of function modules for functionmodule exits is:
    EXIT_<program name><3 digit suffix>
    The call to a functionmodule exit is implemented as:
    CALL CUSTOMER.-FUNCTION <3 digit suffix>
    To find a Exit.
    Goto Transaction -- Find The Package
    SMOD >f4>Use the Package here to Find the Exits In the Package.
    Else if you Want to search by Application Area wise ,
    There is one more tab to find the Exits in the Respective Application Area.
    Implementing the Exit-- CMOD Create ProjectsAssgn your Component .
    Now Run ur Transaction to Check if it Triggers.
    Thats it..
    Suppose you need to find out all the user exits related to a tcode.
    1. Execute the Tcode.
    2. Open the SAP program.
    3. Get the Development Class.
    4. Execute Tcode SE84.
    5. Open the Node 'Envir. -> Exit Techniques -> 'Customer Exits -> Enhancements'
    6. Enter the Development class and execute.
    Check out this thread..
    The specified item was not found.
    1. Type the transaction : system->status-> <PROG. NAME>
    2 open SE37 , type EXIT<PROG NAME> and press F4 to get the list of function exits available.
    3. Open CMOD utilities->SAP enhancements
    EDIT->All selections
    4.type the function module name obtained in step 2, in fields 'component name' in 'additional selections' block. and execute.
    5. The displayed list contains the enhancements names for the transaction You were looking for.
    6. Create a project in CMOD and the code in default include->activate.
    http://www.erpgenie.com/sap/abap/code/abap26.htm
    which gives the list of exits for a tcode
    http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
    For information on Exits, check these links
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sapgenie.com/abap/code/abap26.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    http://www.easymarketplace.de/userexit.php
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sappoint.com/abap/userexit.pdfUser-Exit
    http://www.planetsap.com/userexit_main_page.htm
    User-Exits
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sap-img.com/ab038.htm
    http://www.planetsap.com/userexit_main_page.htm
    http://www.sap-basis-abap.com/sapab013.htm
    http://sap.ittoolbox.com/documents/popular-q-and-a/user-exits-for-the-transaction-code-migo-3283
    These links will help you to learn more on user exits.
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
    http://www.planetsap.com/userexit_main_page.htm
    http://www.allsaplinks.com/user_exit.html
    www.sap-img.com/abap/what-is-user-exits.htm
    Also please check these threads for more details about user exits.
    Re: Screen exit
    user exit and customer exit
    user exit
    1. Document on UserExits in FI/CO
    http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
    2. Finding User Exits...
    http://sap.ionelburlacu.ro/abap/sap2/Other_Useful_Tips.html#Finding_User_Exits
    3. List of all User Exits...
    http://www.planetsap.com/userexit_main_page.htm
    Reward if found helpfull,
    Cheers,
    Chaitanya.

  • User exit for Payment terms at header level

    Dear Alli
    In which user exit, I have to modify if I need ti change value of payment terms at Sales Order Header level .
    and  let me know in which include program is that ??
    Thank You.
    Regards
    Madhu
    Edited by: madhu tatikonda on Feb 12, 2008 8:58 PM

    You can check move_field_to_vbak or in USEREXIT_SAVE_DOCUMENT_PREPARE
    in include: MV45AFZZ

  • Screen exit (for newTabstrip) for ME21 TRANSACTION CODE AT ITEM LEVEL

    Hi All ABAPERS,
    I had a urgent requirement that I need to provide new tabstrip in ME21 tcode at ITEM level.
    note: not in Item overview.
    So, friends could you please tell me what is the screen exit for it and if you have steps for it please give me the solution as early as possible and good points will be rewarded.

    use this enhamcement MM06E005
    go to se51 give program name SAPLXM06 and create 0111 screen and mention subscreen under attributes of screen.
    and go to layout define ur fields in the layout..
    use exit_sapmm06e_013 for getting data .
    also create ci_ekpo structrure and write the req logic to update that strucutre so that values will go and sit in stadard ekpo table.
    after creating that structure dont forget to activate ekpo thr se14.
    and go to se80 and give function group of exit_sapmm06e_013(this fm) and u will find under includes some z*top where u can declare all ur screen fields .

  • User exit for making PO tolerance check at header level

    Hi,
    Is there a user exit or any other settings to make PO tolerance check at the PO header level rather than the usual check at the item level?
    Thanks in advance.
    Regards,
    Arun Mohan

    Hi,
    Is there a user exit or any other settings to make PO tolerance check at the PO header level rather than the usual check at the item level?
    Thanks in advance.
    Regards,
    Arun Mohan

Maybe you are looking for