Application Development 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
Showing results for 
Search instead for 
Did you mean: 

Information on user exits

Former Member
0 Kudos

hi all ,

i want to learn user exits , how to use them and what are the uses of user exit ... can any one tell me the best link or documentation to learn user exits from the basics..

it will be great favour and person will be rewarded with points

Thanks and regards

nikesh kumar

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Exits are basically the hooks whcih SAP has provided to add your own code. There are two types of Exits:

1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.

2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.

BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)

Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.

Please go through the following link which will help you understand the exits in a much better way:

http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm

http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm

http://sap.niraj.tripod.com/id21.html

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

http://www.sap-img.com/ab038.htm

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

customer exits

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662...

Menu Exit.

http://www.sappoint.com/abap/spmp.pdf

http://www.sappoint.com/abap/userexit.pdf

http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm

http://www.sapdevelopment.co.uk/enhance/enhancehome.htm

USER EXIT

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.sap-img.com/ab038.htm

http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm

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

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

http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html

Field Exit

If you are in 4.7 and up follow this

1. Run report RSMODPRF

2. Run on the selection screen

3. In list Field Exit > Create

4. Give your data element

5.System will generate the FM FIELD_EXIT_XXXXX

6. Activate it.

7. Select your field exit and assign to your program and screen

8. Select again .. Field exit > Activate

If you are in version below 4.7

1. CMOD

2. Go to >Text enhancment > Field exit

then follow the same step from 3 onwards as given above.

Menu Exit

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

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

Creating menu exits

http://help.sap.com/saphelp_nw04/helpdata/en/c8/19762743b111d1896f0000e8322d00/content.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/83/7a18cbde6e11d195460000e82de14a/frameset.htm

Regards,

5 REPLIES 5

Former Member
0 Kudos

Hi,

In computer software, a user exit is a place in a software program where a customer can arrange for their own tailor-made program to be called. In the R/3 system from SAP, a user exit is contrasted with a customer exit and allows a customer's developer to access program components and data objects within the R/3 system. In R/3, some user exits use Include statements to include customer program enhancements that are called from the program. Other user exits use tables that are accessed through customization.

Overview

Extension of SAP functionality

SAP makes different possibilities available to extend SAP functionality in the R/3 without modifying the delivered R/3-Standard. Thus these extensions are further present also after a R/3-Release-Wechsel.

• User exit

• Field exit

• Text extensions

• Customer exit

• Table extensions

1. User exit

User exits are original one in the selling module (SD) developed expandability.

They consist of empty subroutines (FORM) in special Includes, which can be filled by a ABAP Use developer. In special places in the SA P-CODE such subroutine references were inserted by SAP. An extension is thus only possible, where SAP planned it.

They usually offer a rather rudimentary expandability, since purely technically objects in the SAP name area are modified.

What is User Exits?

The following document is about exits in SAP: -

The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications.

SAP creates user exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.

Types of Exits

There are several different types of user exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.

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 item’s 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 screen’s flow logic.

Function Module Exits :

Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits.

When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated.

Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs.

These calls have the following syntax:

CALL CUSTOMER-FUNCTION ‘001’. ]

Field Exits :

Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a company’s international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.

The field exit concept lets you create a special function module that contains this logic.

You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.

In 4.6c, you can use "RSMODPRF" program to create field exits.

An example of a user exits :-

MODULE user_exit_0001 INPUT

CASE okcode.

WHEN 'BACK OR EXIT'.

CASE sy-dynnr.

WHEN '100'.

SET SCREEN 0.

LEAVE SCREEN.

WHEN '200'.

*Note that you can write any code that satisfy your needs.

  • But in this case, this was wrote as a sample code for reference sake.

  • And you can test it.

SET SCREEN 100.

LEAVE SCREEN.

ENDCASE.

ENDCASE.

Hope this helps u,

Regards,

Arunsri

Former Member
0 Kudos

Exits are basically the hooks whcih SAP has provided to add your own code. There are two types of Exits:

1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.

2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.

BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)

Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.

Please go through the following link which will help you understand the exits in a much better way:

http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm

http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm

http://sap.niraj.tripod.com/id21.html

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

http://www.sap-img.com/ab038.htm

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

customer exits

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662...

Menu Exit.

http://www.sappoint.com/abap/spmp.pdf

http://www.sappoint.com/abap/userexit.pdf

http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm

http://www.sapdevelopment.co.uk/enhance/enhancehome.htm

USER EXIT

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.sap-img.com/ab038.htm

http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm

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

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

http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html

Field Exit

If you are in 4.7 and up follow this

1. Run report RSMODPRF

2. Run on the selection screen

3. In list Field Exit > Create

4. Give your data element

5.System will generate the FM FIELD_EXIT_XXXXX

6. Activate it.

7. Select your field exit and assign to your program and screen

8. Select again .. Field exit > Activate

If you are in version below 4.7

1. CMOD

2. Go to >Text enhancment > Field exit

then follow the same step from 3 onwards as given above.

Menu Exit

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

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

Creating menu exits

http://help.sap.com/saphelp_nw04/helpdata/en/c8/19762743b111d1896f0000e8322d00/content.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/83/7a18cbde6e11d195460000e82de14a/frameset.htm

Regards,

Former Member
0 Kudos

Hi,

Exits are basically the hooks whcih SAP has provided to add your own code. There are two types of Exits:

1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.

2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.

BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)

Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.

Please go through the following link which will help you understand the exits in a much better way:

http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm

http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm

http://sap.niraj.tripod.com/id21.html

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

http://www.sap-img.com/ab038.htm

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

customer exits

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f1a7e790-0201-0010-0a8d-f08a4662...

Menu Exit.

http://www.sappoint.com/abap/spmp.pdf

http://www.sappoint.com/abap/userexit.pdf

http://www.sapdevelopment.co.uk/enhance/mod_sapmenu.htm

http://www.sapdevelopment.co.uk/enhance/enhancehome.htm

USER EXIT

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.sap-img.com/ab038.htm

http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm

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

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

http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html

Field Exit

If you are in 4.7 and up follow this

1. Run report RSMODPRF

2. Run on the selection screen

3. In list Field Exit > Create

4. Give your data element

5.System will generate the FM FIELD_EXIT_XXXXX

6. Activate it.

7. Select your field exit and assign to your program and screen

8. Select again .. Field exit > Activate

If you are in version below 4.7

1. CMOD

2. Go to >Text enhancment > Field exit

then follow the same step from 3 onwards as given above.

Menu Exit

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

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

Creating menu exits

http://help.sap.com/saphelp_nw04/helpdata/en/c8/19762743b111d1896f0000e8322d00/content.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/83/7a18cbde6e11d195460000e82de14a/frameset.htm

Former Member
0 Kudos

check the foll link,

http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction

also refer

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

Creating menu exits

http://help.sap.com/saphelp_nw04/helpdata/en/c8/19762743b111d1896f0000e8322d00/content.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/83/7a18cbde6e11d195460000e82de14a/frameset.htm

For screen exits.

http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction

chech these links for user exists its usefull

http://www.allsaplinks.com/user_exit.html

http://help.sap.com/saphelp_47x200/helpdata/en/dd/561602545a11d1a7020000e829fd11/frameset.htm

http://www.sap-basis-abap.com/sapab013.htm

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

refer

just refer to the link below for step by step procedure with screen shots

http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g

Check this link:

http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975e643b111d1896f0000e8322d00/frameset.htm

http://help.sap.com/saphelp_47x200/helpdata/en/52/670ba2439b11d1896f0000e8322d00/frameset.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb2d40358411d1829f0000e829fbfe/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/10/e7dbde82ba11d295a40000e8353423/content.htm

http://fuller.mit.edu/tech/dialog_programming.html

http://sap.mis.cmich.edu/sap-abap/abap09/index.htm

http://sap.mis.cmich.edu/sap-abap/abap09/sld011.htm

Also, refer this:

Overview

R/3 provides three "customization spots" that allow you to enhance FI/CO features without modifying the standard code. Although often collectively referred to as "user exits," two of the three have different names. SAP Enhancements are used to expand the standard functionality within SAP. Enhancements use function modules and are called from the standard SAP code. Each module in the system has a set of delivered enhancements that help companies expand the standard functionality where they need it. Enhancements were new in release 3.0.

The Open FI Interfaces or Business Transaction Events are also used to expand the standard functionality within SAP. These events are defined in the IMG. Business Transaction Events were new in release 4.0. They are not available for all modules and are not called on all integrated transactions into FI as of release 4.5B. This will change with each release and should be retested.

The older User Exits in FI/CO are "Z" programs that are defined in table T80D for client-dependent user exits, and in table T80I for client-independent user exits. These are also used to expand the standard functionality within the FI/CO modules. These User Exits have been available since the early releases of SAP. All of these FI/CO User Exits are listed in this document in the Configuring User Exits (Older). The list is included because these User Exits are not a part of the Enhancements or Business Transaction Events and do not have an Info System for searching.

Benefits• Standard SAP functionality can be enhanced without modification to the standard code.

• Upgrades do not erase the functionality and it does not have to be re-transported or re-entered into the system. The enhancements should be thoroughly tested when upgrading to ensure the system will still work as implemented.

Configuring SAP Enhancements

Basic Steps in Configuring an Enhancement

• Find the appropriate Enhancement.

• Enter the ABAP code in the "Z" program within the function module.

• Create a project.

• Add the Enhancement to the project.

• Activate the project.

Example Business Scenario for Enhancements

Company A has a requirement to validate all customer master records created with a U.S. address. The U.S. entity reports on the industry field on the customer master. This is only a U.S. requirement and should not be required for the other countries, so the field status would not work. To accomplish this requirement, Company A will need to set up an Enhancement for the customer master transaction. The necessary steps are detailed below with screenprints. This example was configured in a 4.6C system.

Detailed Steps

1. Tools ABAP Workbench Utilities Enhancements Definition Utilities List Enhancements

2. Do not execute this without any parameters! There are too many Enhancements and it will probably time out. You’re searching for a customer master exit. Enter mast in the short text (see Figure 1). You’ll start there. Searching for an exit can be tricky, so make sure you try several things before giving up.

3. Execute the search.

Start Your Search for a Master Exit Here

4. Look through the list until you find the Enhancement for User exits: Customer Master Data.

5. Double-click on the enhancement SAPMF02D. This will take you to the details of the Enhancement and list the function modules included in the Enhancement.

6. To continue, double-click on the function module EXIT_SAPMF02D_001

7. This will take you to the source code for the function module. Click on the Import tab to review the tables/fields that are available for the Enhancement

The Tables That Are Available for the Enhancement

8. To view the tables/fields that can be changed in the function module, click on the Export and Changing tabs. For this function module, these tabs are empty because you can only validate data. You cannot change any fields in this enhancement.

9. Return to the Source Code tab.

10. Scroll down until you see the Include statement in the program. The "Z" program listed after the Include is where your code will be written

Your Program Will Begin After the Include Statement

11. Double-click on the Include. You will be prompted to create the include. Click on Yes to create.

12. At this point you will be prompted to enter a development class and to create a transport request. If you do not know which development class to use, please contact your technical team.

13. Enter the following ABAP code into the program

*

User exit to ensure that all US customers have a group key

entered on the customer master.

*

if i_kna1-land1 = 'US' and

i_kna1-brsch = ' '.

message e001(F2).

endif.

The ABAP Code You Need to Enter

14. Note that the table name matches the table name in the import tab tables.

15. In this example you are using the standard message class F2 with message number 001. Normally, you will create your own message within your own message class. All customer message classes must begin with a "Z" and are created in transaction SE91.

16. Save the program.

17. The next step is to create the project. Go to transaction code CMOD or follow menu path: Tools ABAP Workbench Utilities Enhancements Project Management.

18. Enter the project name; begin the name with a "Z."

19. Click on the Create button.

Click on Create After You Type in the Project Name

20. Enter in a description for the project.

21. Click on the Enhancement Assignments button.

22. You will be prompted to save the enhancement. Click on Yes.

23. At this point you will be asked for a development class and to create a transport for the project. You may use the same one created when adding the ABAP code to the function module.

24. Enter the name of the enhancement SAPMF02D (see Figure 6).

Enter the Name of the Enhancement Here

25. Save the project.

26. Back out of the enhancement assignment.

27. Activate the project by hitting the Activate button.

The SAP Enhancement is ready to be tested! Try creating a customer with U.S. as the country and a blank group key. Be sure to test one with a group key to make sure the message is not displayed in error as well.

Configuring Business Transaction Events

Basic Steps in Configuring an Event

• Make sure the application is active for Business Transaction Events.

• Copy the sample interface function module into a "Z" function module.

• Enter the ABAP code into the source code section of the new "Z" function module. You may choose to create a "Z" program to enter the code into and then insert the "Z" program into your function module source code.

• Activate the function module.

• Assign the function module to the event, country and application.

Example Business Scenario for Business Transaction Events

Company A would like to copy the group key field from the vendor master into the allocation field on all the line items within a vendor invoice and payments, including the vendor lines. This requirement assumes only one vendor is posted to in a document.

To accomplish this requirement, Company A will use the Business Transaction Event 1130, Post Document: SAP Internal Field Substitution.

1. IMG Menu Path: Financial Accounting Financial Accounting Global Settings Use Business Transaction Events Environment Infosystem (Processes).

2. Find the correct Business Event. You are updating a field, so you select the Processes Info System instead of the Publish and Subscribe Info System.

3. Execute the search with the defaults.

4. Find the correct interface for updating a document: Post Document: SAP- Internal Field Substitution

Find the Correct Interface for the Business Event

5. Put your cursor on the event and click on the Sample Function Module button.

6. You are now in transaction SE37 – Function Builder. This is the function module (sample_process_00001130) you will need to copy into a "Z" name function module for your coding

Figure 8. This Is the Function Module You Need to Copy Your "Z" Name Function Module

7. Click on the Copy button.

8. Enter the "Z" function module name in the To Function Module field

9. Enter a Function Group. If you need to create a "Z" function group, go to transaction code SE37 and follow menu path: Go to Function Groups Create Group. A function group is a logical grouping of function modules, and the ABAP code is generated for function groups. You will be prompted for a development class and transport when creating the function group.

Enter Your "Z" Function Module Name Here

10. In Function Builder (transaction SE37), enter the new "Z" function module. Click on the Change button.

11. The system will default into the source code screen where you may enter your ABAP code.

12. Notice the tables available for the code. Additional tables may be declared if necessary.

13. Enter the following source code

tables: lfa1.

data: z_groupkey like lfa1-konzs.

z_groupkey = ' '.

loop at t_bseg.

check for vendor lines. If one is found, read the vendor master and

retrieve the group key field.

if t_bseg-koart eq 'K'.

select single konzs from lfa1 into z_groupkey

where lifnr = t_bseg-lifnr.

endif.

Move the group key field into all line items allocation field.

loop at t_bsegsub.

t_bsegsub-zuonr = z_groupkey.

modify t_bsegsub index sy-tabix.

endloop. "t_bsegsub

endloop. "t_bseg

The Screen Where You Enter Your Source Code

14. Save the function module.

15. Back out to the main Function Builder screen by clicking on the green arrow button.

16. Activate the function module by clicking on the Activate button

. Activate the Function Module from This Screen

17. Assign the function module to the event in the IMG: Financial Accounting Financial Accounting Global Settings Business Transaction Events Settings Process Function Modules of an SAP Appl.

18. Hit enter past the warning messages that this is SAP data.

19. Click on the New Entries button.

20. Enter the process for your interface. In your example it is 00001130.

21. Enter the country the interface is valid for. If it is valid for all countries, leave this field blank.

22. Enter the application the interface should be called for. If it should be called for all applications, leave this field blank. Please note that not all integrated transactions are programmed to go through these interfaces! You will need to test to find out!

23. Enter the new "Z" function module

Enter Your New "Z" Function Module Here

24. Save the settings. At this point you will be prompted for a CTS number for the configuration change.

25. The Business Transaction Event is complete! You are ready for testing.

Configuring User Exits (Older)

Basic Steps in Configuring an User Exit

• Create a "Z" program for the User Exits and enter the necessary ABAP code.

• Enter the new program name into table T80D.

• Configure the application to call the User Exit.

List of User Exits

• Variable Field Movements

• Substitutions in FI, CO, PCA

• Validations in FI, CO, PCA

• Rollups in SPL

• Fixed Field Movements in SPL

• Cost Center Summarization on Detail Screen

• Sets Formula Variables

Example Business Scenario for User Exits

Company A would like to add a "Z" field in the Special Purpose Ledger to capture a Business Unit field for reporting. They have used all the standard SAP fields such as Business Area and Profit Center. The field will only be used for reporting and is only needed in the Special Purpose Ledger. You created a special ledger table (ZZSPL1) with field Z_BUNIT and need to populate this field based on a combination of G/L account, fund and functional area.

To accomplish this requirement, Company A will use the Variable Field Movement User Exit. To make maintenance easier, table ZZBUSUNIT was created with the G/L account, fund and functional area fields as key fields, and the business unit field as a non-key field. You generated the table maintenance so the table could be updated using transaction SM30. SAP users update the business unit determination rules in table ZZBUSUNIT by entering the G/L account, fund and functional area, and then the business unit that combination should be posting to. The User Exit will read table ZZBUSUNIT using the G/L account, fund and functional area from the posting transaction and determine the business unit. The steps for using the user exit are detailed below. This example was created on a 4.6C system.

1. Copy the delivered template User Exit program RGIVU000_TEMPLATE into a "Z" program. Follow menu path Tools ABAP Workbench Development ABAP Editor (transaction code SE38). In early releases, the delivered program was RGIVU000.

2. You will be prompted for a development class and a transport. Please check with the technical team for the correct development class.

3. At the initial ABAP Editor screen, enter your new "Z" program name, select the Source Code button and click on Change

To Enter Your New Code, Select Source Code and Click on the Change Button

4. Enter the following code in the User Exit (Figure 14):

FORM E01_MVC USING FROM_FIELD TO_FIELD.

to_field = 'CORP'. "Set a default business unit.

read table zzbusunit to determine the business unit field.

select single z_bunit from zzbusunit into to_field

where hkont = accit_glx-hkont and

geber = accit_glx-geber and

fkber = accit_glx-fkber.

ENDFORM.

Figure 14. Enter Your New Code at This Screen.

5. Activate the program by clicking on the Activate button.

6. Change the configuration in the User Exit table to point to your new "Z" program.

7. Follow the IMG menu path: Financial Accounting Special Purpose Ledger Basic Settings User Exits Maintain Client Specific User Exits.

8. The entry to maintain is application area GIMV: Variable Field Movement. Enter your "Z" program

Enter Your "Z" Program in the Application Area GIMV: Variable Field Movement

9. Save the changes.

10. The final configuration step is to assign the User Exit in the variable field movement for your special ledger table. In the IMG: Financial Accounting &#61664; Special Purpose Ledger &#61664; Basic Settings &#61664; Master Data &#61664; Maintain Field Movements. Field movements control how the fields in a special ledger table are populated. They can be populated straight from other fields in a posting or through User Exits.

After You Assign the Business Unit Field and the G/L Account, the Exit Field Should Contain U01.

11. Assign the business unit field as a receiver and the G/L account as the sender. The Exit field should contain U01 (see Figure 16).

12. The User Exit number U01 calls User Exit E01_MVC form in the "Z" program.

13. Save the field movement.

14. You are ready to test your User Exit!

Reward points if useful.

Former Member
0 Kudos

Hi,

User exits :

1. Introduction

2. How to find user exits

3. Using Project management of SAP Enhancements

1. Introduction:

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 ❤️ 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 in 1 project. If the enhancement is already 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"

****************************************************************

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.

Regards,

Priya.