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: 

is it require to create project in CMOD for user exits?

Former Member
0 Kudos

Hi,

Is it required to create project for USER-EXITS like CUSTOMER-EXITS, if it is required how to find out enhancement name for a particular USER-EXIT.

ex : J_1I7_USEREXIT_EXCISE_BEF_SAVE.(USER-Exit)

Thanks,

Sreedhar.

2 REPLIES 2

Former Member
0 Kudos

first see the documentation of this FM or see the SPRO docuementation in this case ?

regards

Peram

Former Member
0 Kudos

Hi Sreedhar,

<b>User exit means</b>

we have to provide the additional functionality to sap functionality by developing field exits,screen exits,menu exits.

customer-exits: some function exits provided by sap for customers to add some additional functionality to existing sap functionality

<b>locate customer Exit within program</b>

For this example I am using transaction MIRO Step 1Execute transaction MR1M and display program name by selecting 'Status...' from the 'System' menu Step 2Double click on the program (screen) name to enter source code, or access code via SE80.Step 3Search source code for the 'Customer-Function' string using the find button. Remember to select 'In main program'. Step 4A list of search results should be displayed indicating where all function exits can be found. You can now double click on each of them to go to its position in the source code. This also allows for the insertion of breakpoints so that you can test if the exits are called in the appropriate place. Get Function Module linked to Function Exit

.

FUNCTION field_exit_bstnr.*"----


""Local interface:" IMPORTING" REFERENCE(INPUT)" EXPORTING" REFERENCE(OUTPUT)*"----

-


  • create field symbol FIELD-SYMBOLS: <status>.* Assign value of variable from calling prog to field symbol ASSIGN ('(SAPMM06E)RM06E-BSART') TO <status>.* Display value retrieved in message* Note: Messages of type i and w are not allowed IF sy-subrc = 0. MESSAGE e003(zr) WITH <status> 'kkk'. ENDIF.ENDFUNCTION.

Adding fields to standard Infotype


SAP allows you to add additional fields to any standard Infotype. Step 1Using transaction PM01 chose the 'Enhance Infotype tab' and press the create 'All' button. Step 2The following screen will appear allowing you to enter the new fields you wish to add to the Infotype. i.e. ZZSPINST and ZZBACS Step 3Once saved and activated the new fields will appear in the Infotype screen and database table (See below)Infotype screen(PA20) Infotype database table
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: · For each of the function codes click on Extras and choose ‘Active functions in multiple statuses’.


Implementing Business Add-Ins (BADI)



The use of object orientated code within SAP has lead to new method of enhancing standard SAP code called Business Add-Ins or BADI's for short. Although the implementation concept is based on classes, methods and inheritance you do not really have to understand this fully to implement a BADI. Simply think of methods as a function module with the same import and export parameters and follow the simple instructions below.
Steps:1. Execute Business Add-In(BADI) transaction SE182. Enter BADI name i.e. HRPBSGB_HESA_NISR and press the display button 3. Select menu option Implementation->Create4. Give implementation a name such as Z_HRPBSGB_HESA_NISR5. You can now make any changes you require to the BADI within this implementation, for example choose the Interface tab6. Double click on the method you want to change, you can now enter any code you require.7. Please note to find out what import and export parameters a method has got return the original BADI definition (i.e. HRPBSGB_HESA_NISR) and double click on the method name for example within HRPBSGB_HESA_NISR contract is a method8. When changes have been made activate the implementation

Reward pts if found usefull 🙂

Regards

Sathish