Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

USER EXIT

Former Member

‎2007 Jan 03 6:51 AM

0 Likes
768

hi all,

can any body tell me how to create menu exit, screen exits

thanks in advance.

regards,

Vinod.

6 REPLIES 6
Read only

Former Member

‎2007 Jan 03 6:53 AM

0 Likes
723

hi,

Check

Read only

Former Member

‎2007 Jan 03 6:54 AM

0 Likes
723

Check these links..

http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

http://www.sap-img.com/abap/what-is-user-exits.htm

Search through www.enips.com.

You can find lot of material there.

BADI's

http://help.sap.com/saphelp_erp2005/helpdata/en/73/7e7941601b1d09e10000000a155106/frameset.htm

http://support.sas.com/rnd/papers/sugi30/SAP.ppt

http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/abapindx.htm

http://members.aol.com/_ht_a/skarkada/sap/

http://www.ct-software.com/reportpool_frame.htm

http://www.saphelp.com/SAP_Technical.htm

http://www.kabai.com/abaps/q.htm

http://www.guidancetech.com/people/holland/sap/abap/

http://www.planetsap.com/download_abap_programs.htm

http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm

/people/thomas.weiss/blog/2006/04/03/how-to-define-a-new-badi-within-the-enhancement-framework--part-3-of-the-series

/people/thomas.weiss/blog/2006/04/18/how-to-implement-a-badi-and-how-to-use-a-filter--part-4-of-the-series-on-the-new-enhancement-framework

User Exits

http://www.erpgenie.com/sap/abap/code/abap26.htm

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

Regards,

Balaji Reddy G

***Rewards if answers are helpful

Read only

Former Member

‎2007 Jan 03 6:59 AM

0 Likes
723

For screen exits, have a look at below link. It will help you surely.

<a href="http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction">Screen Exits</a>

I hope it helps.

Best Regards,

Vibha

*Please mark all the helpful answers

Read only

Former Member

‎2007 Jan 03 6:59 AM

0 Likes
723

Menu exits allow you to attach your own functions to the menu options in

SAP menus. SAP application programmers reserve certain menu entries in

your GUI interface for this purpose. This allows you to define a text for

the reserved menu entry and add your own logic, often in the form of a

related function module exit. After you activate menu exits, they become

visible in the SAP menu. Whenever this menu option is chosen, the system

processes either a function provided by SAP application programmers or

your own function that you have implemented in a function module exit.

For you to be able to implement menu exits, SAP application programmers

must equip the GUI interface with the function codes that begin with

a plus sign, (+).

These function codes are inactive at first and do not appear in the GUI

until you activate them. They do not appear on the screen.

Menu exits are edited with the project management transaction, CMOD.

The pushbutton for editing components calls a dialog box where you can

enter short descriptions and choose a language for each additional menu

entry.

You may not make any changes to the GUI interface.

SAP application programmers determine where a program reads

additional function codes and how it reacts, either with a function module

exit orwith a predefined function.

You can implement menu exits based on reserved function codes. The SAP

application programmer defines the relevant function codes, assigns them

to menus, and often provides a function module exit.

Menu exits and function module exits are both a part of the same SAP

enhancement.

No pushbuttons may be assigned to additional function codes.

You can make changes to the various menu entries and activate their

function codes.

<i><b>Screen Exits</b></i>

Screen exits allow you to make use of reserved sections of a main screen,

subscreen areas. You can either display additional information in these

areas or input data. You define the necessary input and output fields on a

customer screen, subscreen.Subscreens are rectangular areas on your screen that are reserved for

displaying additional screens at run time. Each subscreen area can be filled

with a different screen of te type, subscreen, at runtime.SAP R/3 Enterprise determines which screen will be displayed in a

subscreen area at PBO. The general syntax is as follows:CALL SUBSCREEN <subscreen_area> INCLUDING <prg>

<screen_no>.

For each subscreen, PAI and PBO events are processed as if the subscreen

were a normal screen.

The sequence of CALL SUBSCREEN statements in your main screen flow

logic directly determines the order in which the flow logic of the individual

subscreens is processed.Function codes are processed only in the main screen flow

logic.

&#149; You are not allowed enter a name for the command field of

a subscreen.

&#149; You are not allowed to define the GUI status for subscreens.

&#149; No value for the next screen may be entered in a subscreen

flow control.

The SAP application programmer can reserve multiple subscreen areas

for a screen.

The subscreen is called during the flow control of the main screen with the

CALL CUSTOMER-SUBSCREEN statement. The name of the subscreen

area must be defined without apostrophes. The function group to whichthe subscreen belongs is defined statically in apostrophes but the screen

number can be kept variable by using fields. The screen number must

always have four digits.

Screen exit calls are inactive at first and are skipped when a screen is

processed.

Only after a corresponding subscreen has been created in an enhancement

project, and this project has been activated, will the system process the

screen exit.

You create subscreens in X function groups. Normally, these function

groups also contain function module exits.

Whenever the statement, CALL CUSTOMER-SUBSCREEN <area>

INCLUDING >x-function-pool> <screen_number> occurs at PBO

in the flow control of a screen, a subscreen is included in the subscreen

area defined by SAP application programmers. At this point, all modules

called during the PBO event of the subscreen are also processed.

The PAI event of a subscreen is processed when the calling screen

calls the subscreen during its PAI event using the statement, CALL

CUSTOMER-SUBSCREEN <area>.

The global data of the calling program is not known to the X function

group that contains your subscreen. SAP application programmers use

function module exits to explicitly provide this data to subscreens.

To enable data transport, modules are called in the flow control of the

calling program that contain function module exits for transferring data

through interface parameters.

Function modules belonging to these types of function module exits can be

found in the same function groups as their corresponding subscreens.

Data must be transported in the other direction as well because global data

from the X function group that contains your subscreen is not known to

the calling program. For this reason, SAP application programmers use

function module exits to return any data to the calling program that was

changed in the subscreen.

This is achieved by calling a module during the main screen&#146;s PAI event

that contains a function module exit for returning customer data through

interface parameters.

Subscreens are edited with the project management transaction, CMOD.

The technical names of screen exits consist of the name of the calling

program, a four-digit screen number, and the name of the subscreen area,

followed by the name of the X function group&#146;s program and the number

of the subscreen.

You must create the subscreen as well as the corresponding PBO and PAI

modules. The SAP development environment supports creation with

forward navigation.

Make sure that your subscreens are of the screen type, subscreen, the first

time you create them.

You are not allowed to change any of the interfaces in the X function group

that the subscreen and the function module exits belong to nor are you

allowed to add any of your own function modules.

Note that the same constraints apply as when calling a normal subscreen.

Screen exits allow you to determine the layout of certain portions of a

screen yourself. You can use these areas to display additional information,

or to collect and process data.

Screen exits must be predefined (planned) by an SAP application

programmer. Use the statement, CALL CUSTOMER-SUBSCREEN, to

integrate these preplanned subscreen areas into the flow control of the

calling screen at PBO and PAI events.

As soon as you activate an enhancement project that contains a subscreen

as a component, the calling screen is regenerated and the subscreen is

displayed the next time the application function is called.

Regards,

Balaji Reddy G

***Rewards if answers are helpful