Regarding Menu exit

Hi All,
i need to find Menu Exit in VA01 transaction.
that i need to add additional functionality in menu bar
Goto->Item->MSDS Sheet.
i need to add MSDS Sheet functionality in menu Bar,
please can any body suggest me which menu exit will be available
Thanks in advance
thanks & Regards,
sudheer.

Check this...it will help u to create menu exit...
Creating Customer-Specific Menus
Menu exits allow you to add your own functions to the pulldown menus in standard R/3 transactions. To take advantage of a menu exit, you first need to create a project as described in the section Creating an add-on project. Then, you must include the SAP enhancement package that contains the menu exit you want to use in your project. From the main screen of the Project management transaction, proceed as follows:
Select Enhancement components and choose Change.
The system lists all customer exits contained in the enhancements included in your project.
Place the cursor on the menu exit you want to add your own function to.
Choose Edit component.
The system displays technical information about the menu entry. It also displays two input fields where you can specify a language and the text you want your menu item to have.
Enter the name of your menu function (such as Special order method) in the field New text.
Choose Save text.
Your special menu function will not appear in the pulldown menu of the corresponding standard transaction until you activate your enhancement project.
Specifying a menu text and activating your project are not the only steps you need to take to make your own menu item work. After you carry out these steps, your menu item will appear, but it will not call a corresponding function. To attach your menu entry to its corresponding function, you need to create a function module for the function module exit associated with your menu text. This function module exit is part of the same SAP enhancement that contains the menu exit you used. Creating Customer-Specific Function Modules tells you more about how to use function module exits.

Similar Messages

Query on using Screen exits & Menu Exits

Hi Group,
I was trying to make changes to Screen and also adding Menus to the standard transactions.
I went through some sites like SAP Help and SAP Development. But, they were giving info on how to create the things and not giving any sample example for creating things.
So please kindly provide some useful examples on creating the above Screen & Menu Exits.
thanks in advance.
Regards,
Vishnu.

So here is an example to Modifying Standard SAP System and help Menu options.
 Use Menu Painter (Transaction SE41), enter program MENUSYST, status MEN and click change.
 Modify SAP Standard by adding function codes.
add the 'NEW1' fuction code just for example. u can add any no of fuction keys and lastly.
 For each of the function codes click on Extras and choose Active functions in multiple statuses.
Thanks and regards,
Pavan
Thanks and regards,
Pavan

How to Create Menu Exit

Hi,
Please tell me steps for how to create Menu Exit. Please Help me

MENU EXITS
Menu exits allow you to add your own functionallity to menus. Menu exits are implemented by SAP, and are reserved menu entries in the GUI interface. The developer can add his/her own text and logic for the menu.
Function codes for menu exits all start with "+"
Example
We want to create a new menu item in the Office menu. The text for the menu should be "Run ZTEST", and the menu will
run report ZTEST.
Goto transaction SE43 Area Menu Maintenance
In Area Menu Paramenter type 'S000' (S triple Zero)
Select Change and ignore all the warning screens
Expand the office menu. In the buttom of the office tree you will find a menu named "Customer function"
Double click on the text. In the pop-up screen change the text to "Run ZTEST". Note that the trsnaction code is +C01
Goto transaction SE93 and create transaction +C01 that calls report ZTEST.
Now you will se the menu displayed in the office tree. If you delete transaction +C01 again, the new menu will dissapear.
There are 'only' 177 Menu exits in standard - I couldn't see the right one, too.
But you could search the implemented exits, this should be only a small number. Go to transaction CMOD, enter * and F4, information system (F5), show all selections (Shift+F7) and then you can restrict to search only menu exits.
Of course there is the possibility, that these are added in a different way...
... at least you can be sure, if it's a normal menu exit.
Check this sap help..
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
http://www.sapbrainsonline.com/TUTORIALS/default.html
You can achieve this functionality by configuring in IMG.
Please find the info regarding User-Exit's in the following links:
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/frameset.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
Re: doubt on user exits
user exits and Badis
User exits is the enhancements provided by SAP
You can use them in transactions. Each transaction will have user exits.
If you want to use your own requirements by making your coding while the transaction is run you can use user exits.
For example if you want to run the MRP in MD02 specific to MRP controller you can user exit.
Please also refer the document below.
USEREXIT
Userxits allow us to add our own functionality to SAP standard program
without modifying it . These are implemented in the form of subroutines and hence are also known as FORM EXITs. The userexits are generally collected in includes and attached to the standard program by the SAP.
All Userexits start with the word USEREXIT_...
FORM USEREXIT_..
z..
ENDFORM.
The problem lies in finding the correct userexit and how to find it if one exists for the purpose. Once the correct userexit is found the necessary customer code is inserted in the customer include starting with the z.. in the form routine.
e.g. USEREXIT_SAVE_DOCUMENT_PREPARE
Certain application like SD still provide this form of enhancement using userexit but this practice is no longer being followed for newer extensions instead they are using EXITs which come bundeled in enhancement packages . Neverthiless existing USEREXITS will be supported by SAP an all the newer versions of SAP.
HOW TO FIND USEREXITS
Userexits can be found in number of ways:
1) To find userexits in SD module , goto object navigator(SE80) and select
development class from the list and enter VMOD in it. All of the userexits in SD are contained in the development class VMOD. Press enter and you will find all the includes which contain userexits in SD for different functions like PRICING, ORDER PROCESSING etc. Select the userexit according to the requirement and read the comment inserted in it and start coding .
Some examples of userexits in SD(SALES & DISTRIBUTION ) are:
1)ADDING OF NEW FIELDS IN PRICING
In Pricing in SD the fields on the basis of which pricing is done are derived from the FIELD CATALOG which is a structure KOMG .This structure is used to transfer transaction data to the pricing procedure in SD and is also known as communication structure.This structure KOMG consists of two tables KOMK for Header related fields and KOMP for item related fields. The fields which are not in either of the two tables KOMK and KOMP cannot be used in pricing .Sometimes a need arises when the pricing is to be based on some other criteria which is not present in the form of fields in either of the two tables. This problem can be solved by using USEREXITS which are provided for pricing in SD. Pricing takes place both when the SALES ORDER ( Transaction VA01) is created as well as when INVOICING ( Transaction VF01) is done.Hence SAP provides 2 userexits ,one for sales order processing which is
USEREXIT_PRICING_PREPARE_TKOMP or
USEREXIT_PRICING_PREPARE_TKOMK
Depending upon which table (KOMK or KOMP) the new fields were inserted we use either of the above two userexits.These userexits are found in include MV45AFZZ of the standard SAP sales order creation program SAPMV45A.
In the case of userexit which will be called when invoicing is done ,these
are provided in the include RY60AFZZ which is in the standard SAP program SAPMV45A. The name of the userexits are same. i.e
USEREXIT_PRICING_PREPARE_TKOMP or
USEREXIT_PRICING_PREPARE_TKOMK
These userexits are used for passing the data from the communication structure to the pricing procedure, for this we have to fill the newely created field in the communication structure KOMG for this we fill the code in the above userexit using the MOVE statement after the data that has to be passed is taken from the database table by using the SELECT statement. The actual structure which is visible in these userexits and which is to be filled for that particular field is TKOMP or TKOMK.
Before the coding for these userexits is done ,it is necessary to create a new field in either of the two tables KOMK or KOMP .For this purpose includes are provided in each of them .
To create the field in header data(KOMK) the include provided is KOMKAZ
and to create the field in item data(KOMP) the include provided is KOMPAZ.
One possible example for the need of creating new fields can be e.g. Frieght to be based upon transportation zone ,for this no field is available in field catalog and hence it can be created in KOMK and then above userexits can be used to fill the transportation data to it.
2)The other method of finding userexit is to find the word USEREXIT in the
associated program of the transaction for which we want to determine userexit using SE38.
3)The other method of finding userexits is to find the include in case of SD/MM applications where the userexits are located ,this can be found in the SAP reference IMG generally in the subfolder under SYSTEM MODIFICATION.
Some other examples of userexits in SD are:
USEREXIT_NUMBER_RANGE
This userexit is used to assign a different internal document number to the
sales order(VA01) when it is created depending on some criteria like a different SALES ORGANIZAION(VKORG) .
USEREXIT_SAVE_DOCUMENT_PREPARE
This userexit is used to insert the ABAP code which will be called when
the document (sales order VA01) is just about to be saved.This userexit is used generally for custom checks on different fields , to display some information before the order will be saved or for making changes to certain fields before the sales order will be saved.
Exits & Enhancements
There are mainly six types of EXITs in sap which have been collected in the form of enhancement packages and attached to standard code in SAP.
These are different from USEREXIT in the way that they are implemented
in the form of FUNCTIONs while in USEREXITS we use form routines for their implementation. These are also sometimes known as function exits .
These start from the word EXIT_ followed by the program name and then followed by a three digit number.
e.g. EXIT_SAPMV45A_002
This exit is found in SD in enhancement V45A0002.
TYPES OF EXITS
1)MENU EXITS
2)FUNCTION EXITS
3)TABLE EXITS
4)SCREEN EXITS
5)KEYWORD EXITS
6)FIELD EXITS
We use SAP transactions CMOD and SMOD to manage exits. Before implementing an exit , it is required to create the project by using CMOD
selecting the enhancement e.g. V45A0002 and selecting the component
(one which fulfills our need) i.e the exit which will be implemented in SMOD and after coding has been done the project has to be activated.
An exit can be coded only once.
FUNCTION EXITS
These are used to add functionality through ABAP code . These start from the word EXIT_programname_NNN ending in a 3 digit number. No access code is required to implement any tupe of exit including function exits.
The function exits are called from the standard SAP program in the form
of ABAP statement
CALL CUSTOMER-FUNCTION 'NNN'
This is in contrast to USEREXITs where PERFORM statement is used to call
the required userexit.
To implement the FUNCTION EXITs first of all the project is created and a suitable enhancement package is selected and from its compnents the function exit to be implemented is selected and on double clicking it the exit code will appear in ABAP EDITOR(se38) where a Z include will be found and the customer code should be entered in this include.
e.g.
ADDING A DEFAULT SOLD-TO-PARTY in Sales Order Creation
To show a default sold-to-party in this field when the user creates a sales order (VA01) we can use a function exit .This function exit is located in enhancement no V45A0002 . Before we can choose the exit we have to create a project in CMOD after that enter V45A0002 in the enhancement field and click on the components . In the components you will see the exit EXIT_SAPMV45A_002 . This exit is used for our purpose.
Double clicking on this exit will takes us to function builder (SE37) . This
function exit has one exporting parameters and two importing parameters, we are interested in exporting parameter which is E_KUNNR of type KNA1-KUNNR i.e if we move the desired customer name to this structure(E_KUNNR) it will be shown in the field as the default value when we create the sales order. This function also contains a customer include ZXVVA04 . This include will be used to write our custom code .
Double clicking on this include and it will prompt us that this include does not exists do you want to create this object ,select yes and the include will be created .In this include we can write our own code that will fill the field E_KUNNR.
e.g. E_KUNNR = 301.
Activate the include and Activate the project. Now when ever the SALES ORDER will be created , sold-to-party field will come up with a predefined customer .
FIELD EXITS
The field exits are managed,created,activated through program RSMODPRF. The field exit is associated with a data element existing in ABAP dictionary and hence to the screen field using that data element.
The format of field exit is :
FIELD_EXIT_dataelement_A-Z or 0-9
If a particular screen and program name is not specified than the field exit will effect all the screens containing that data element.
The function module associated with field exit shows two parameters
INPUT and OUTPUT. Input parameter contains the data passed to the field exit when the field exit was invoked by the R/3 , We can write our own code to change the output parameter depending upon our requirements.
Before the field exit can have any effect the system profile parameter
ABAP/FIELDEXIT in all the application servers should be set to YES
ABAP/FIELDEXIT = YES.
Reward points Please ...

Screen Exits and Menu Exits

Hi all,
Can anyone help me with a step-by-step procedure or tutorial to create
a) Screen exit
b) Menu Exit...?
Thanks and regards
Shiva

Hi Shiva,
Check this...it will help u to create menu exit...
Creating Customer-Specific Menus
Menu exits allow you to add your own functions to the pulldown menus in standard R/3 transactions. To take advantage of a menu exit, you first need to create a project as described in the section Creating an add-on project. Then, you must include the SAP enhancement package that contains the menu exit you want to use in your project. From the main screen of the Project management transaction, proceed as follows:
Select Enhancement components and choose Change.
The system lists all customer exits contained in the enhancements included in your project.
Place the cursor on the menu exit you want to add your own function to.
Choose Edit component.
The system displays technical information about the menu entry. It also displays two input fields where you can specify a language and the text you want your menu item to have.
Enter the name of your menu function (such as Special order method) in the field New text.
Choose Save text.
Your special menu function will not appear in the pulldown menu of the corresponding standard transaction until you activate your enhancement project.
Specifying a menu text and activating your project are not the only steps you need to take to make your own menu item work. After you carry out these steps, your menu item will appear, but it will not call a corresponding function. To attach your menu entry to its corresponding function, you need to create a function module for the function module exit associated with your menu text. This function module exit is part of the same SAP enhancement that contains the menu exit you used. Creating Customer-Specific Function Modules tells you more about how to use function module exits.
Procedure for Creating MENU Exits:
1) To get into Area Menu Maintenance Screen Type SE43 T.Code in Command
Line.
2) In Area Menu Paramenter type 'S000' (S triple Zero)
3) Then Press Change Icon in Application Tool Bar. Then It may ask for
Access Key [or] it may display "Specify Processing mode" window. If it ask
for the Access Key Check for the availability of OSS Note and apply to open
Standard SAP Menu to include MENU Exits. Otherwise, if it display "Specify
Processing mode" window with Three Push Button. In which select "Change" and
proceed further.
4) Then it will display "Information" window with the following information
"Caution : The Original Language of the structure is German (editing lang. :
English) ". Then press "Enter Key to proceed further.
5) Then you will get into "Edit Area Menu S000".
6) for eg:- Expand Tools Menu.
7) Then Press ABAP Workbench <Icon>.
8) Then you will get into ABAP Workbench Menu Tree.
9) Then Expand Utilities Menu.
10) In the last line you will find one MENU EXIT Provision to include your
own menu. "Node Text Not Found" This text can be change by double Clicking
that. There you can find the T.Code. Here for Eg:- "+DW4".
11) for eg: - Here change the Text to "Sample Menu Exit" and then note down
the T.Code "+DW4".
12) Then Save with Change Request Number and come out of Transaction SE43.
13) Then Goto Transaction SE93.
14) Then type T.Code "+DW4" and press Create.
15) Then proceed further to create transaction called "+DW4".
I hope this could help you in Creating Menu Exit...
Regards,
Kumar

DIfference Between User Exits, Screen Exits, Menu Exits And BADI

Could any one let me know the exact/practical dIfference Between User Exits, Screen Exits, Menu Exits And BADI. ? And why BADIs are more proned to use?

Hi,
User Exits:
A user exit is a three character code that instructs the system to access a program during system processing.
SXX: S is for standard exits that are delivered by SAP. XX represents the 2-digit exit number.
UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number
Menu Exits:
Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu items text when activating the item in an add-on project.
Screen Exits:
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screens flow logic.
BADIs:
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
And why BADIs are more proned to use?
In contrast to above customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
Regards,
Ferry Lianto

Menu exit for VA01/02/03

How to find the menu exit for VA01/02/03 transactions?
Thanks
Tharani

hi do like this....use this program and execurte it give the tcode and execute it will give the exits list click on the exit and it will takes to the exit and choose test it gives whether it is a manu exit or function exit..
REPORT z_find_userexit NO STANDARD PAGE HEADING.
*& 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.
regards,
venkat.

Menu exit-VA01/02/03

Hi All,
I need to create a menu exit from VA* transactions to call a custom pricing screen. The user would invoke this from item pricing screen and it should call the Z transaction for the particular part number and display the price data. Can this be acheived?
Regards,
Hari.

Hi All,
I need to create a menu exit from VA* transactions to call a custom pricing screen. The user would invoke this from item pricing screen and it should call the Z transaction for the particular part number and display the price data. Can this be acheived?
Regards,
Hari.

Any menu exit or badi for tcode F110

Dear all,
My requirement is that whenever the user runs tcode F110, a flat file has to be generated with all the details from tcode F110. How can i do that? Should i change the std pgm or any menu exit or badi available. Plz help me in this regard.

Hi
Following are the User Exits and BADIs available:
Enhancement
RFFOX074                                Frame for user exit RFFOX074 (in program RFFOCH_U)
RFFOX075                                Frame for user exit RFFOX075 (in program RFFOCH_U)
RFFOX081                                Frame for user exit RFFOX081 (in program RFFOF__T)
RFFOX082                                Frame for user exit RFFOX082 (in program RFFOF__T)
RFFOX100                                Frame for user exit RFFOX100 (in program RFFOUS_T)
RFFOX101                                Frame for user exit RFFOX101 (in program RFFOUS_T)
RFFOX102                                Frame for user exit RFFOX102 (in program RFFOUS_T)
RFFOX103                                Frame for user exit RFFOX103 (in program RFFOUS_T)
RFFOX104                                user exit
RFFOX105                                Frame for user exit RFFOX105 (in program RFFOUS_T)
RFFOX200                                Frame for user exit RFFOX200 (in program RFFONZ_T)
RFFOX210                                Frame for user exit RFFOX210 (in program RFFOAU_T)
RFFOX211                                Frame for user exit RFFOX211 (in program RFFONZ_T)
RFFOX230                                General program for user exit RFFOX230 (in program RFFOJP_L)
RFFOX240                                Enhancement for User Exit 240 (RFFOAT_P)
RFFOX250                                Enhancement for User Exit 250 (RFFODK_E)
RFFOX901                                Framework for user exit RFFOX901 (in program RFFOM100)
RFFOX902                                Framework for user exit RFFOX902 (in program RFFOM100)
FDTAX001                                Enhancement to Transaction FDTA (event after the download)
FEDI0002                                Function exits for EDI DOCS in FI - Incoming pyt adv.notes
FEDI0003                                Function exits for EDI docs in FI - Save PEXR segments
FEDI0004                                Function exits for EDI docs in FI - particular events
FEDI0006                                Function Exits for EDI-docs in FI: Save IDCR Segments
RFFOX003                                Frame for user exit RFFOX003 (in program RFFOM100)
RFFOX041                                Framework for user exit RFFOX041 (in program RFFOBE_I)
RFFOX042                                Framework for user exit RFFOX042 (in program RFFOBE_E)
RFFOX043                                Framework for user exit RFFOX043 (in program RFFOBE_D)
RFFOX061                                Frame for user exit RFFOX061 (in program RFFOCH_P)
RFFOX062                                Frame for user exit RFFOX062 (in program RFFOCH_P)
RFFOX063                                Frame for user exit RFFOX063 (in program RFFOCH_P)
RFFOX064                                Frame for user exit RFFOX064 (in program RFFOCH_P)
RFFOX065                                Frame for user exit RFFOX065 (in program RFFOCH_P)
RFFOX066                                Frame for user exit RFFOX066 (in program RFFOCH_P)
RFFOX071                                Frame for user exit RFFOX071 (in program RFFOCH_U)
RFFOX072                                Frame for user exit RFFOX072 (in program RFFOCH_U)
RFFOX073                                Frame for user exit RFFOX073 (in program RFFOCH_U)
Business Add-in
FI_BSTM_MC_EXIT                         FI Account Statement: Exit from MultiCash Conversion
FI_F110_SCHEDULE_JOB                    F110: Check before scheduling a proposal/update run
Cheers
Shakir

Custom screen in a menu exit

Hi,
Can we call a custom screen from a menu exit? When the menu is clicked, a custom screen should pop up . There should be a option for going back to the old screen from this custome screen.
I have seen screen exits where u can develope custome screens but not sure whether meny exists or function exits will allow u to call custome screen.
regards,
shan

solved

Plz help me in finding out the BADI or menu exit for IW32

HI
in Tcode IW32, based on the user status(ASTTX), the menu items ,EXTRAS -> TASK LIST SELECTION -> all items have to be grayed out.
Please help me to find out BADI or menu exit which ever is available.
Thanks,
Pallavi.

Hi,
     Please check if the below user exit/BADI is useful.
     Enhancement
     IWO10012                                Maintenance order: Priority handling on central header
     BAdi
     IWO_UI_USEFLEX                     BAdI for Calling Up an Alternative UI
Regards,
Srini.

Error ! No field defined for function Code in MENU EXIT

Hello All,
I've created a project in CMOD for the MENU EXIT for handling one menu item in the SAP Standard Menu Bar .
i.e under the HELP MENU Item I've included one more sub menu item.
I've activated the project and I'm able to se the newly added Sub-Menu Item in the activated mode.
But when I press the newly created Sub Menu Item I'm getting a Message in the Status Bar saying :
No field defined for the function code
The Help of it says :
Message no. 00125
Diagnosis
The function code field (OK code field) has not been defined on this screen. If the user selects an application function (not a system function), the system usually provides it in the function code field (OK code field) as well as in SY-UCOMM. This is no longer possible.
System Response
The system is unable to inform the application of the current function code. The application should not use field SY_COMM. This field always contains the code of the last function chosen, which is not always identical to the application-relevant code.
Procedure
You should always define a field for the function code on every screen. The Screen Painter always proposes such a field (OK category), you only need to assign a name and include the definition in the ABAP program.
Please let me know what shud be done ?
Regards,
Deepu.K

Don't use this scanrio ! Instead got Access Key and chamged the Std. Program.

Hi abapers menu exit how to create for a z program

hi all gurus,
i want to create an user exit , how to implement menu exit and customer exit in a z program plz let me know steps by step plz let me know

Hi ,
check out this .
http://sap-abapinfo.blogspot.com/2008/06/short-tutorial-on-user-exits.html
regards
Prabhu

Need Menu Exit for T-Code ME32K in ECC

Hello,
I need Menu Exit for Transaction ME32K in ECC version, It would be helpful if any one could tell me,
Deserving answer will be rewarded points
Regards
Rajesh

hi
use this program to search for the BADIS and enhancements
& Report ZPJA_PM002 (V2) &
& Text Elements: &
& P_DEVC Show user-exits from development class &
& P_LIMIT Limit submit program selection &
& P_FUNC Show function modules &
& P_SUBM Show submit programs &
& S01 Selection data (TCode takes precedence over program name) &
report zpja_pm002
no standard page heading
line-size 158.
*tables: enlfdir. "Additional Attributes for Function Modules
data: tabix like sy-tabix,
 w_linnum type i,
 w_off type i,
 w_index like sy-tabix,
 w_include like trdir-name,
 w_prog like trdir-name,
 w_incl like trdir-name,
 w_area like rs38l-area,
 w_level,
 w_str(50) type c,
 w_funcname like tfdir-funcname.
constants: c_fmod(40) type c value 'Function modules selected: ',
 c_subm(40) type c value 'Submit programs selected: ',
 c_col1(12) type c value 'Enhanmt Type',
 c_col2(40) type c value 'Enhancement',
 c_col3(30) type c value 'Program/Include',
 c_col4(20) type c value 'Enhancement Name',
 c_col5(40) type c value 'Enhancement Description'.
Work Areas: ABAP Workbench
data: begin of wa_d010inc.
data: master type d010inc-master.
data: end of wa_d010inc.
data: begin of wa_tfdir.
data: funcname type tfdir-funcname,
 pname type tfdir-pname,
 include type tfdir-include.
data: end of wa_tfdir.
data: begin of wa_tadir.
data: devclass type tadir-devclass.
data: end of wa_tadir.
data: begin of wa_tstc.
data: pgmna type tstc-pgmna.
data: end of wa_tstc.
data: begin of wa_tstcp.
data: param type tstcp-param.
data: end of wa_tstcp.
data: begin of wa_enlfdir.
data: area type enlfdir-area.
data: end of wa_enlfdir.
Work Areas: BADIs
data: begin of wa_sxs_attr.
data: exit_name type sxs_attr-exit_name.
data: end of wa_sxs_attr.
data: begin of wa_sxs_attrt.
data: text type sxs_attrt-text.
data: end of wa_sxs_attrt.
Work Areas: Enhancements
data: begin of wa_modsap.
data: member type modsap-member.
data: end of wa_modsap.
data: begin of wa_modsapa.
data: name type modsapa-name.
data: end of wa_modsapa.
data: begin of wa_modsapt.
data: modtext type modsapt-modtext.
data: end of wa_modsapt.
Work Areas: Business Transaction Events
data: begin of wa_tbe01t.
data: text1 type tbe01t-text1.
data: end of wa_tbe01t.
data: begin of wa_tps01t.
data: text1 type tps01t-text1.
data: end of wa_tps01t.
user-exits
types: begin of t_userexit,
 type(12) type c,
 pname like trdir-name,
 txt(300),
 level type c,
 modname(30) type c,
 modtext(40) type c,
end of t_userexit.
data: i_userexit type standard table of t_userexit with header line.
Function module developmnet classes
types: begin of t_devclass,
 clas like trdir-clas,
end of t_devclass.
data: i_devclass type standard table of t_devclass with header line.
Submit programs
types: begin of t_submit,
 pname like trdir-name,
 level,
 done,
end of t_submit.
data: i_submit type standard table of t_submit with header line.
Source code
types: begin of t_sourcetab, "#EC * (SLIN lügt!)
 line(200), "#EC * (SLIN lügt!)
 end of t_sourcetab. "#EC * (SLIN lügt!)
data: sourcetab type standard table of t_sourcetab with header line.
data c_overflow(30000) type c.
Description of an ABAP/4 source analysis token
data: i_stoken type standard table of stokex with header line.
data wa_stoken like i_stoken.
Description of an ABAP/4 source analysis statement
data: i_sstmnt type standard table of sstmnt with header line."#EC
keywords for searching ABAP code
types: begin of t_keywords,
 word(30),
end of t_keywords.
data: keywords type standard table of t_keywords with header line.
function modules within program
types: begin of t_fmodule,
 name like rs38l-name,
 pname like trdir-name,
 pname2 like trdir-name,
 level,
 bapi,
 done,
end of t_fmodule.
data: i_fmodule type standard table of t_fmodule with header line.
& Selection Options &
selection-screen begin of block selscr1 with frame title text-s01.
parameter: p_pname like trdir-name memory id rid,
 p_tcode like syst-tcode,
 p_limit(4) type n default 100,
 p_devc like rihea-dy_ofn default ' ',
 p_func like rihea-dy_ofn default ' ',
 p_subm like rihea-dy_ofn default ' '.
selection-screen end of block selscr1.
& START-OF-SELECTION &
start-of-selection.
if p_pname is initial and p_tcode is initial.
 message e008(hrfpm). "Make entry on the selection screen
 stop.
endif.
ensure P_LIMIT is not zero.
if p_limit = 0.
 p_limit = 1.
endif.
perform data_select.
perform get_submit_data.
perform get_fm_data.
perform get_additional_data.
perform data_display.
& Form DATA_SELECT &
form data_select.
data selection message to sap gui
call function 'SAPGUI_PROGRESS_INDICATOR'
 destination 'SAPGUI'
 keeping logical unit of work
 exporting
 text = 'Get programs/includes' "#EC NOTEXT
 exceptions
 system_failure
 communication_failure
 . "#EC *
determine search words
keywords-word = 'CALL'.
append keywords.
keywords-word = 'FORM'.
append keywords.
keywords-word = 'PERFORM'.
append keywords.
keywords-word = 'SUBMIT'.
append keywords.
keywords-word = 'INCLUDE'.
append keywords.
if not p_tcode is initial.
get program name from TCode
 select single pgmna from tstc into wa_tstc-pgmna
 where tcode eq p_tcode.
 if not wa_tstc-pgmna is initial.
 p_pname = wa_tstc-pgmna.
TCode does not include program name, but does have refereve TCode
 else.
 select single param from tstcp into wa_tstcp-param
 where tcode eq p_tcode.
 if sy-subrc = 0.
 check wa_tstcp-param(1) = '/'.
 check wa_tstcp-param+1(1) = '*'.
 if wa_tstcp-param ca ' '.
 endif.
 w_off = sy-fdpos + 1.
 subtract 2 from sy-fdpos.
 if sy-fdpos gt 0.
 p_tcode = wa_tstcp-param+2(sy-fdpos).
 endif.
 select single pgmna from tstc into wa_tstc-pgmna
 where tcode eq p_tcode.
 p_pname = wa_tstc-pgmna.
 if sy-subrc <> 0.
 message e110(/saptrx/asc) with 'No program found for: '
p_tcode."#EC NOTEXT
 stop.
 endif.
 else.
 message e110(/saptrx/asc) with 'No program found for: ' p_tcode.
"#EC NOTEXT
 stop.
 endif.
 endif.
endif.
Call customer-function aus Program coding
read report p_pname into sourcetab.
if sy-subrc > 0.
 message e017(enhancement) with p_pname raising no_program."#EC *
endif.
scan abap-source sourcetab tokens into i_stoken
 statements into i_sstmnt
 keywords from keywords
 overflow into c_overflow
 with includes.
 WITH ANALYSIS.
if sy-subrc > 0. "keine/syntakt. falsche Ablauflog./Fehler im Skanner
 message e130(enhancement) raising syntax_error. "#EC *
endif.
check I_STOKEN for entries
clear w_linnum.
describe table i_stoken lines w_linnum.
if w_linnum gt 0.
 w_level = '0'.
 w_prog = ''.
 w_incl = ''.
 perform data_search tables i_stoken using w_level w_prog w_incl.
endif.
endform. "DATA_SELECT
& Form GET_FM_DATA &
form get_fm_data.
data selection message to sap gui
call function 'SAPGUI_PROGRESS_INDICATOR'
 destination 'SAPGUI'
 keeping logical unit of work
 exporting
 text = 'Get function module data' "#EC NOTEXT
 exceptions
 system_failure
 communication_failure
 . "#EC *
Function module data
sort i_fmodule by name.
delete adjacent duplicates from i_fmodule comparing name.
loop at i_fmodule where done ne 'X'.
 clear: i_stoken, i_sstmnt, sourcetab, wa_tfdir, w_include .
 refresh: i_stoken, i_sstmnt, sourcetab.
 clear wa_tfdir.
 select single funcname pname include from tfdir into wa_tfdir
 where funcname = i_fmodule-name.
 check sy-subrc = 0.
 call function 'FUNCTION_INCLUDE_SPLIT'
 exporting
 program = wa_tfdir-pname
 importing
 group = w_area.
 concatenate 'L' w_area 'U' wa_tfdir-include into w_include.
 i_fmodule-pname = w_include.
 i_fmodule-pname2 = wa_tfdir-pname.
 modify i_fmodule.
 read report i_fmodule-pname into sourcetab.
 if sy-subrc = 0.
 scan abap-source sourcetab tokens into i_stoken
 statements into i_sstmnt
 keywords from keywords
 with includes.
 if sy-subrc > 0.
 message e130(enhancement) raising syntax_error.
 endif.
check i_stoken for entries
 clear w_linnum.
 describe table i_stoken lines w_linnum.
 if w_linnum gt 0.
 w_level = '1'.
 w_prog = i_fmodule-pname2.
 w_incl = i_fmodule-pname.
 perform data_search tables i_stoken using w_level w_prog w_incl.
 endif.
 endif.
endloop.
if p_devc = 'X'.
 loop at i_fmodule.
 clear: wa_tadir, wa_enlfdir.
 select single area from enlfdir into wa_enlfdir-area
 where funcname = i_fmodule-name.
 check not wa_enlfdir-area is initial.
 select single devclass into wa_tadir-devclass
 from tadir where pgmid = 'R3TR'
 and object = 'FUGR'
 and obj_name = wa_enlfdir-area.
 check not wa_tadir-devclass is initial.
 move wa_tadir-devclass to i_devclass-clas.
 append i_devclass.
 i_fmodule-done = 'X'.
 modify i_fmodule.
 endloop.
 sort i_devclass.
 delete adjacent duplicates from i_devclass.
endif.
endform. "GET_FM_DATA
& Form GET_SUBMIT_DATA &
form get_submit_data.
data selection message to sap gui
call function 'SAPGUI_PROGRESS_INDICATOR'
 destination 'SAPGUI'
 keeping logical unit of work
 exporting
 text = 'Get submit data' "#EC NOTEXT
 exceptions
 system_failure
 communication_failure
 . "#EC *
sort i_submit.
delete adjacent duplicates from i_submit comparing pname.
w_level = '0'.
loop at i_submit where done ne 'X'.
 clear: i_stoken, i_sstmnt, sourcetab.
 refresh: i_stoken, i_sstmnt, sourcetab.
 read report i_submit-pname into sourcetab.
 if sy-subrc = 0.
 scan abap-source sourcetab tokens into i_stoken
 statements into i_sstmnt
 keywords from keywords
 with includes.
 if sy-subrc > 0.
 message e130(enhancement) raising syntax_error.
 continue.
 endif.
check i_stoken for entries
 clear w_linnum.
 describe table i_stoken lines w_linnum.
 if w_linnum gt 0.
 w_prog = i_submit-pname.
 w_incl = ''.
 perform data_search tables i_stoken using w_level w_prog w_incl.
 endif.
 endif.
restrict number of submit program selected for processing
 describe table i_submit lines w_linnum.
 if w_linnum ge p_limit.
 w_level = '1'.
 endif.
 i_submit-done = 'X'.
 modify i_submit.
endloop.
endform. "GET_SUBMIT_DATA
& Form DATA_SEARCH &
form data_search tables p_stoken structure stoken
 using p_level p_prog p_incl.
loop at p_stoken.
 clear i_userexit.
 tabix = sy-tabix + 1.
 i_userexit-level = p_level.
 if i_userexit-level = '0'.
 if p_incl is initial.
 i_userexit-pname = p_pname.
 else.
 concatenate p_pname '/' p_incl into i_userexit-pname.
 endif.
 else.
 if p_incl is initial.
 i_userexit-pname = p_prog.
 else.
 concatenate p_prog '/' p_incl into i_userexit-pname.
 endif.
 endif.
Include
 if p_stoken-str eq 'INCLUDE'.
 check p_level eq '0'. " do not perform for function modules
*(2nd pass)
 w_index = sy-tabix + 1.
 read table p_stoken index w_index into wa_stoken.
 check not wa_stoken-str cs 'STRUCTURE'.
 check not wa_stoken-str cs 'SYMBOL'.
 read table i_submit with key pname = wa_stoken-str.
 if sy-subrc <> 0.
 i_submit-pname = wa_stoken-str.
 i_submit-level = p_level.
 append i_submit.
 endif.
 endif.
Enhancements
 if p_stoken-str eq 'CUSTOMER-FUNCTION'.
 clear w_funcname.
 read table p_stoken index tabix.
 translate p_stoken-str using ''' '.
 condense p_stoken-str.
 if p_prog is initial.
 concatenate 'EXIT' p_pname p_stoken-str into w_funcname
 separated by '_'.
 else.
 concatenate 'EXIT' p_prog p_stoken-str into w_funcname
 separated by '_'.
 endif.
 select single member from modsap into wa_modsap-member
 where member = w_funcname.
 if sy-subrc = 0. " check for valid enhancement
 i_userexit-type = 'Enhancement'.
 i_userexit-txt = w_funcname.
 append i_userexit.
 else.
 clear wa_d010inc.
 select single master into wa_d010inc-master
 from d010inc
 where include = p_prog.
 concatenate 'EXIT' wa_d010inc-master p_stoken-str into
w_funcname
 separated by '_'.
 i_userexit-type = 'Enhancement'.
 i_userexit-txt = w_funcname.
 endif.
 endif.
BADIs
 if p_stoken-str cs 'cl_exithandler='.
 w_index = sy-tabix + 4.
 read table p_stoken index w_index into wa_stoken.
 i_userexit-txt = wa_stoken-str.
 replace all occurrences of '''' in i_userexit-txt with space.
 i_userexit-type = 'BADI'.
 append i_userexit.
 endif.
Business transaction events
 if p_stoken-str cs 'OPEN_FI_PERFORM'.
 i_userexit-type = 'BusTrEvent'.
 i_userexit-txt = p_stoken-str.
 replace all occurrences of '''' in i_userexit-txt with space.
 i_userexit-modname = i_userexit-txt+16(8).
 case i_userexit-txt+25(1).
 when 'E'.
 clear wa_tbe01t.
 select single text1 into wa_tbe01t-text1 from tbe01t
 where event = i_userexit-txt+16(8)
 and spras = sy-langu.
 if wa_tbe01t-text1 is initial.
 i_userexit-modtext = ''. "#EC NOTEXT
 else.
 i_userexit-modtext = wa_tbe01t-text1.
 endif.
 i_userexit-modname+8 = '/P&S'. "#EC NOTEXT
 when 'P'.
 clear wa_tps01t.
 select single text1 into wa_tps01t-text1 from tps01t
 where procs = i_userexit-txt+16(8)
 and spras = sy-langu.
 i_userexit-modtext = wa_tps01t-text1.
 i_userexit-modname+8 = '/Process'.
 endcase.
 append i_userexit.
 endif.
Program exits
 if p_stoken-str cs 'USEREXIT_'.
 i_userexit-type = 'Program Exit'.
 i_userexit-txt = p_stoken-str.
 replace all occurrences of '''' in i_userexit-txt with space.
 append i_userexit.
 endif.
Submit programs
 if p_stoken-str cs 'SUBMIT'.
 check p_level eq '0'. " do not perform for function modules
*(2nd pass)
 check not p_stoken-str cs '_'. " ensure not SUBMIT_XXX
 w_index = sy-tabix + 1.
 read table p_stoken index w_index into wa_stoken.
 check not wa_stoken-str cs '_'. " ensure not SUBMIT_XXX
 replace all occurrences of '''' in wa_stoken-str with space.
 read table i_submit with key pname = wa_stoken-str.
 if sy-subrc <> 0.
 i_submit-pname = wa_stoken-str.
 i_submit-level = p_level.
 append i_submit.
 endif.
 endif.
Perform routines (which reference external programs)
 if p_stoken-str cs 'PERFORM'.
 check p_level eq '0'. " do not perform for function modules
*(2nd pass)
 w_index = sy-tabix + 1.
 read table p_stoken index w_index into wa_stoken.
 if not wa_stoken-ovfl is initial.
 w_off = wa_stoken-off1 + 10.
 w_str = c_overflow+w_off(30).
 find ')' in w_str match offset w_off.
 w_off = w_off + 1.
 wa_stoken-str = w_str(w_off).
 endif.
 check wa_stoken-str cs '('.
 w_off = 0.
 while sy-subrc = 0.
 if wa_stoken-str+w_off(1) eq '('.
 replace section offset w_off length 1 of wa_stoken-str with ''
 replace all occurrences of ')' in wa_stoken-str with space.
 read table i_submit with key pname = wa_stoken-str.
 if sy-subrc <> 0.
 i_submit-pname = wa_stoken-str.
 append i_submit.
 endif.
 exit.
 else.
 replace section offset w_off length 1 of wa_stoken-str with ''
 shift wa_stoken-str left deleting leading space.
 endif.
 endwhile.
 endif.
Function modules
 if p_stoken-str cs 'FUNCTION'.
 clear i_fmodule.
 check p_level eq '0'. " do not perform for function modules
*(2nd pass)
 w_index = sy-tabix + 1.
 read table p_stoken index w_index into wa_stoken.
 if wa_stoken-str cs 'WF_'.
 if wa_stoken-str cs 'IF_'.
 break-point.
 endif.
 if wa_stoken-str cs 'BAPI'.
 i_fmodule-bapi = 'X'.
 endif.
 replace first occurrence of '''' in wa_stoken-str with space.
 replace first occurrence of '''' in wa_stoken-str with space.
 if sy-subrc = 4. " didn't find 2nd quote (ie name truncated)
 clear wa_tfdir.
 concatenate wa_stoken-str '%' into wa_stoken-str.
 select single funcname into wa_tfdir-funcname from tfdir
 where funcname like wa_stoken-str.
 if sy-subrc = 0.
 i_fmodule-name = wa_tfdir-funcname.
 else.
 continue.
 endif.
 else.
 i_fmodule-name = wa_stoken-str.
 endif.
 i_fmodule-level = p_level.
 append i_fmodule.
 endif.
endloop.
endform. "DATA_SEARCH
& Form GET_ADDITIONAL_DATA &
form get_additional_data.
data selection message to sap gui
call function 'SAPGUI_PROGRESS_INDICATOR'
 destination 'SAPGUI'
 keeping logical unit of work
 exporting
 text = 'Get additional data' "#EC NOTEXT
 exceptions
 system_failure
 communication_failure
 . "#EC *
loop at i_userexit.
Enhancement data
 if i_userexit-type cs 'Enh'.
 clear: wa_modsapa.
 select single name into wa_modsapa-name from modsap
 where member = i_userexit-txt.
 check sy-subrc = 0.
 i_userexit-modname = wa_modsapa-name.
 clear wa_modsapt.
 select single modtext into wa_modsapt-modtext from modsapt
 where name = wa_modsapa-name
 and sprsl = sy-langu.
 i_userexit-modtext = wa_modsapt-modtext.
 endif.
BADI data
 if i_userexit-type eq 'BADI'.
 clear wa_sxs_attr.
 select single exit_name into wa_sxs_attr-exit_name from sxs_attr
 where exit_name = i_userexit-txt.
 if sy-subrc = 0.
 i_userexit-modname = i_userexit-txt.
 else.
 i_userexit-modname = 'Dynamic call'. "#EC NOTEXT
 endif.
 clear wa_sxs_attrt.
 select single text into wa_sxs_attrt-text from sxs_attrt
 where exit_name =
wa_sxs_attr-exit_name
 and sprsl = sy-langu.
 i_userexit-modtext = wa_sxs_attrt-text.
 endif.
 modify i_userexit.
endloop.
get enhancements via program package
clear wa_tadir.
select single devclass into wa_tadir-devclass from tadir
 where pgmid = 'R3TR'
 and object = 'PROG'
 and obj_name = p_pname.
if sy-subrc = 0.
 clear: wa_modsapa, wa_modsapt.
 select name from modsapa into wa_modsapa-name
 where devclass = wa_tadir-devclass.
 select single modtext from modsapt into wa_modsapt-modtext
 where name = wa_modsapa-name
 and sprsl = sy-langu.
 read table i_userexit with key modname = wa_modsapa-name.
 if sy-subrc <> 0.
 i_userexit-modtext = wa_modsapt-modtext.
 i_userexit-type = 'Enhancement'. "#EC NOTEXT
 i_userexit-modname = wa_modsapa-name.
 i_userexit-txt = 'Determined from program DevClass'."#EC NOTEXT
 i_userexit-pname = 'Unknown'. "#EC NOTEXT
 append i_userexit.
 endif.
 endselect.
endif.
endform. "GET_ADDITIONAL_DATA
& Form DATA_DISPLAY &
form data_display.
data selection message to sap gui
call function 'SAPGUI_PROGRESS_INDICATOR'
 destination 'SAPGUI'
 keeping logical unit of work
 exporting
 text = 'Prepare screen for display' "#EC NOTEXT
 exceptions
 system_failure
 communication_failure
 . "#EC *
sort i_userexit by type txt modname.
delete adjacent duplicates from i_userexit comparing txt modname.
format headings
write: 'Enhancements from main program'. "#EC NOTEXT
write: /.
uline.
format color col_heading.
write: / sy-vline,
 (12) c_col1, "Enhanmt Type
 sy-vline,
 (40) c_col2, "Enhancement
 sy-vline,
 (30) c_col3, "Program/Include
 sy-vline,
 (20) c_col4, "Enhancement name
 sy-vline,
 (40) c_col5, "Enhancement description
 sy-vline.
format reset.
uline.
format lines
loop at i_userexit.
set line colour
 case i_userexit-type.
 when 'Enhancement'.
 format color 3 intensified off.
 when 'BADI'.
 format color 4 intensified off.
 when 'BusTrEvent'.
 format color 5 intensified off.
 when 'Program Exit'.
 format color 6 intensified off.
 when others.
 format reset.
 endcase.
 write: / sy-vline,
 i_userexit-type,
 sy-vline,
 i_userexit-txt(40),
 sy-vline,
 i_userexit-pname(30),
 sy-vline,
 i_userexit-modname(20),
 sy-vline,
 i_userexit-modtext(40),
 sy-vline.
endloop.
format reset.
uline.
user-exits from development class of function modules
if p_devc = 'X'.
 write: /.
 write: / 'User-exits from function module development class'."#EC
*NOTEXT
 write: 157''.
 uline (90).
 write: 157''.
 loop at i_devclass.
 clear wa_modsapa.
 select name from modsapa into wa_modsapa
 where devclass = i_devclass-clas.
 select single name modtext into corresponding fields of wa_modsapt
 from modsapt
 where name = wa_modsapa-name
 and sprsl = sy-langu.
 format color 3 intensified off.
 write: / sy-vline,
 (12) 'Enhancement',
 sy-vline,
 wa_modsapa-name,
 sy-vline,
 wa_modsapt-modtext,
 sy-vline.
 endselect.
 endloop.
 uline (90).
 format reset.
endif.
describe table i_fmodule lines w_linnum.
write: / c_fmod , at 35 w_linnum. "#EC NOTEXT
write: 157''.
if p_func = 'X'.
display fuction modules used in program
 uline (38).
 write: 157''.
 loop at i_fmodule.
 write: sy-vline,
 i_fmodule-name,
 sy-vline,
 i_fmodule-bapi,
 sy-vline.
 write: 157''.
 endloop.
 uline (38).
endif.
describe table i_submit lines w_linnum.
write: / c_subm , at 35 w_linnum. "#EC NOTEXT
write: 157''.
if p_subm = 'X'.
display submit programs used in program
 uline (44).
 write: 157''.
 loop at i_submit.
 write: sy-vline,
 i_submit-pname,
 sy-vline.
 write: 157''.
 endloop.
 uline (44).
endif.
issue message with number of user-exits displayed
describe table i_userexit lines w_linnum.
message s697(56) with w_linnum.
endform. "DATA_DISPLAY
reward points if it helps
gunjan

System CUA Menu Exit

I've added my own menu after "System Help" on all screens by adding it in MENUSYST status MEN. I want to call Function Module CALL_BROWSER to start a Browser in Windows which will provide Training information for Users. I'm doing this by using 'T' type menu entries to Call a Report Transaction to call the FM but this resets the original SAP transaction (as if you'd typed /N in the OKCODE). This is possibly becuase my calling transaction is not in a new task. I can't find a suitable Exit in SMOD as an alternative.
How can I invoke a Browser Window from any screen (that a User might use) without resetting the calling transaction?

Hi Raja!
There are 'only' 177 Menu exits in standard - I couldn't see the right one, too.
But you could search the implemented exits, this should be only a small number. Go to transaction CMOD, enter * and F4, information system (F5), show all selections (Shift+F7) and then you can restrict to search only menu exits.
Of course there is the possibility, that these are added in a different way...
... at least you can be sure, if it's a normal menu exit.
Regards,
Christian

Menu Exit & Screen Exit Implementation Step by Step Implementation Needed:

Hi Experts,
I am in need of how to implement Menu Exit and Screen Exit using a simple
example.If any step by step implementation through snapshots were it will be
helpful instead just some links that doesn't work after some steps due to version
changes or not proper steply explanations.Points will be rewarded accordingly.
Thanks for your help in Advance.

Hi Sudha,
Screen exits are exits that allow you to use a reserved part of the screen (A subscreen) to display or input data.
It is determined be SAP where the sub screen will be displayed.
The syntax is: CALL CUSTOMER-SUBSCREEN
The screen exit is not processed untill the corresponding subscreen has been created in an enhancement project, and the project has been activated.
Note:
Function codes are only processed in the main screens flow logic
You are not allowed to enter a name for the subscreens command field
You are not allowed to define GUI stauses
You are not allowed to enter a value for Next screen
The global data of the program is not available for the subscreen. Data for the subscreen is provided by function modules. These function modules belongs to the same function group as the subscreen
Subscreens are edited with transaction CMOD. When you activate a project containg subscreens, the calling screen is regenerated and the subscreen is displayed next time you display the calling screen
The developer must create the subscreen and the corresponding PBO and PAI modules
How to identify screen exits
Look after CALL CUSTOMER-SUBSCREEN in the screenprogram of the screen you want to modify.
Use transaction CMOD menu Utillities -> SAP enhancements to search for screen exits
MENU EXITS
Menu exits allow you to add your own functionallity to menus. Menu exits are implemented by SAP, and are reserved menu entries in the GUI interface. The developer can add his/her own text and logic for the menu.
Function codes for menu exits all start with "+"
Example
We want to create a new menu item in the Office menu. The text for the menu should be "Run ZTEST", and the menu will
run report ZTEST.
Goto transaction SE43 Area Menu Maintenance
In Area Menu Paramenter type 'S000' (S triple Zero)
Select Change and ignore all the warning screens
Expand the office menu. In the buttom of the office tree you will find a menu named "Customer function"
Double click on the text. In the pop-up screen change the text to "Run ZTEST". Note that the trsnaction code is +C01
Goto transaction SE93 and create transaction +C01 that calls report ZTEST.
Now you will se the menu displayed in the office tree. If you delete transaction +C01 again, the new menu will dissapear.
USER EXITS
User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a functionmodule. The code for the function module is writeen 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>
Example:
The program for transaction VA01 Create salesorder is SAPMV45A
If you search for CALL CUSTOMER-FUNCTION i program SAPMV45A you will find ( Among other user exits):
CALL CUSTOMER-FUNCTION '003'
exporting
xvbak = vbak
xvbuk = vbuk
xkomk = tkomk
importing
lvf_subrc = lvf_subrc
tables
xvbfa = xvbfa
xvbap = xvbap
xvbup = xvbup.
The exit calls function module EXIT_SAPMV45A_003
2. How to find user exits
Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT
If you know the Exit name, go to transaction CMOD. Choose menu Utillities->SAP Enhancements. Enter the exit name and press enter.
You will now come to a screen that shows the function module exits for the exit.
3. Using Project management of SAP Enhancements
We want to create a project to enahance trasnaction VA01
Go to transaction CMOD
Create a project called ZVA01
Choose the Enhancement assign radio button and press the Change button
In the first column enter V45A0002 Predefine sold-to party in sales document . Note that an enhancement can only be used i 1 project. If the enhancement is allready in use, and error message will be displayed
Press Save
Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit.
Now the function module is displayed. Double click on include ZXVVAU04 in the function module
Insert the following code into the include: E_KUNNR = '2155'.
Activate the include program. Go back to CMOD and activate the project.
Goto transaction VA01 and craete a salesorder. Note that Sold-to-party now automatically is "2155"
Please check if the thread given below would be of any help.
http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/menu-exits-72696#
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
Regards
KK

Regarding Menu exit

Similar Messages

Maybe you are looking for