User exits in HR-ABAP

Hi all,
Please can you give me the any small example on USER EXITS in HRmodule...
thanks
pooja

Dear,
Tell me your requirements then i will tell you the User-Exits for thatt reuirement. Or you can the user exits in the SPRO itself under the functional Module for which you r looking for user exits.
Well some of ur requirments can be fulfilled with PM01.
RG
VM

Similar Messages

User Exit in HR-ABAP.

Hi to all,
Can any body help me in User-Exit in Hr-Abap. send me ur mail id i wil send u functional specs.
Thanks
hiddu.

The most common enhancements for HR can be found in PBAS0001.
Here you will find the user exits for infotypes PBO & PAI.
http://sap.ittoolbox.com/groups/technical-functional/sap-hr/implementing-user-exit-for-it0041-452836
This link should help

Is User Exit's support ABAP Objects?

Hi Experts,
Is User Exits supports ABAP Objects. I am planning to implement the ABAP classes in User exits to fill Query Variables.
Is it possible?
Thanks & Regards

Hi,
Yes user Exit's support ABAP Object.
But according to me if you want to use class then use the class into some generic function module, then that function module use in Exit. Its just for Cleanness and Simplicity of user Exit.
Regards,

Populate user exit Variable with User Authorizations using ABAP?

Hi, Does anyone know of a way to populate a user exit variable (with ABAP) with the Authorization Values for a user running a report? I am turning off authorizations for our InfoProvider using RSSM and want to populate a variable instead and use the variable as a filter.

Hi Kenneth ,
You need dynamic authorization in your report .This can be done at query runtime by using exit variable and writing cmod code for the same .
This code will read authorization maintained at runtime of query in i_step = 1 and will pass input var values accordingly .
For step by step information you can access this document .
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0f9f33c-0f17-2d10-d3a2-ae52ccd00780?quicklink=index&overridelayout=true
Hope this will be helpful .
Regards,
Jaya Tiwari

Enhancement /User Exit for logic setting call date / Horizon

Due toe planning in IP10 we have a horizon set by the system for (eks.) 80%. This is working OK for small planning intervals (i.e. up to 24 mth intervals).
However when intarval exceeds this limit we will set the call date to be maximum 30 days (for instance) ahead of the sceduled start date of the order.
Thus we need a user-defined way to manipulate / set the call date by a user exit (logic in ABAP - or by IMG settings if possible) that differs from the standard SAP setting for this date.
The question is then how we - in best practice - can do so.
Please advice if you need mor information on this issue.

Hi
Find the available exits with the following program:::
*& Report ZFINDUSEREXIT
report zfinduserexit.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
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 eq enlfdir-area.
move : tadir-devclass to v_devclass.
endif.
endif.
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.
at line-selection.
get cursor field field1.
check field1(4) eq 'JTAB'.
set parameter id 'MON' field sy-lisel+1(10).
If there are no available user exits you could go for badi's.
To search for a badi, go to se 24 display class cl_exithandler. double click on method get_instance, get a break point on case statement. execute and start the required transaction in new session. look for variable exit_name. It would show the available badi's.
Please reward if useful....
regards
Dinesh

How to put bin information to table T_QMAT thru user exit for stock remove?

Hi,
I have already use stock removal strategy 'F' and checked the flag 'User exit active', but the value in table T_QMAT filled by the standard system not include all vendors. So I need to use stock removal strategy " " and set up the table T_QMAT by the user exit.
Do you know what is the user exit and the ABAP coding to put bin information to table T_QMAT for stock removal?
Best Regards,
Chris.

Hi Chris,
You can use the exit: EXIT_SAPLL03A_005 to populate t_qmat table based on your requirements. As you have already mentioned, it is important to check the flag: User exit active in SPRO, but bear in mind the stock removal strategy has to be BLANK. If you use F, then standard SAP auto-populates the T_QMAT table.
Regards,
Narendra.

User Exits in FI

Dear All,
Could you please tell me the general impacts of user exists in FICO with an example?. How can we use this concept in FICO module?
I request you all, please reply your values.
Thanks with regards,
Ran

Hi,
I will give you my actual example of this aplication.
I would like configure a payment condition with 15 days out of week, but the OBB8 transaction doesn't have any field to define days of week. Only sequencial days numbers.
I have created a substituition Rule in GGB4 with a user exit. This User Exit is a ABAP logics codes in a especific SAP program. This allowed especific changes in my data field recognizing days in week.
I hope I help you.
Please, assign points for my contribution.
Rgds

Re: User Exit for Delivery

Hi all,
I have an interface program that integrates with external program that via RFC it will create Delivery document by calling standard SAP tcode "VL01N" through function module and when Delivery number is successfully created, it will update the information from the Delivery document to a Z-table accordingly.
This Z-table also collectively update information passed from the external progam to SAP.
Which then, the Z-table is used by a customised report to retrieve information and tabulate in ALV.
Kindly advise if assuming a Delivery document is reversed or deleted via standard tcode (i.e. VL02N or VL09), is there any exit I can apply to update the deletion or reversal of this document to the customised table??
Kindly advise.
Thanks.

Dear PKW,
This is possible to achieve through a User Exit, where the ABAPer writes a code which will update the z table when ever data is edited for a delivery document. Presently i am not aware of any User Exit numbers, which an ABAPer or another Guru form this forum can suggest.
Happy SAPing
Venkat - Hyd

USER EXIT FOR MIGO_GR ISSUE:

HI
I have case which user want to limit material received of quantity.
i addon one table which structure
WERKS --plant id
MATNR ---material
ALLOW_SIZE -
allow max limit
RECEIVE_SIZE --- have received quantity
ervery time when execute MIGO_GR program, i will add this time received quanitity to table and check RECEIVE_SIZE < ALLOW_SIZE .
otherwise will give a message to user what this action be reject.
so i find a user exit:MB_CF001
and ABAP CODE as follow:
tables:ZMRP_LOT_SIZE,ZMRP_PARAMETER.
data:wa_mseg type mseg.
data:l_subrc type c.
DATA:IT_PARA TYPE ZMRP_PARAMETER OCCURS 0 WITH HEADER LINE.
DATA:IT_ZMRP_LOT_SIZE TYPE ZMRP_LOT_SIZE OCCURS 0 WITH HEADER LINE.
data:wa_zmrp_lot_size type ZMRP_LOT_SIZE.
RANGES:R_WERKS FOR ZMRP_LOT_SIZE-WERKS,
         R_MATNR FOR MARA-MATNR,
         R_MATKL FOR MARA-MATKL.
data:wa_mara type mara.
data:l_msg(30) type c,
       g_msg(100) type c.
break john.
break fms04873.
clear l_subrc .
read table XMSEG INTO wa_mseg with key bwart = '101'.
if sy-subrc <> 0.
    read table XMSEG INTO wa_mseg with key bwart = '103'.
    if sy-subrc = 0.
      l_subrc = '0'.
    endif.
else.
    l_subrc = '0'.
endif.
check l_subrc = '0'.
***lock mrp prameters table.
CALL FUNCTION 'ENQUEUE_EZ_MRP_PARAMETER'
   EXPORTING
     MODE_ZMRP_PARAMETER       = 'S'
     MANDT                     = SY-MANDT
MRP01                     =
MRP02                     =
X_MRP01                   = ' '
X_MRP02                   = ' '
_SCOPE                    = '2'
_WAIT                     = ' '
_COLLECT                  = ' '
EXCEPTIONS
FOREIGN_LOCK              = 1
SYSTEM_FAILURE            = 2
OTHERS                    = 3
IF SY-SUBRC <> 0.
    MESSAGE 'parameter table is lock' TYPE 'E'.
ENDIF.
SELECT * INTO TABLE IT_PARA FROM ZMRP_PARAMETER.
loop at IT_PARA.
    IF IT_PARA-MRP01 = '1'.
      R_WERKS-SIGN = 'I'.
      R_WERKS-OPTION = 'EQ'.
      R_WERKS-LOW = IT_PARA-MRP03.
      COLLECT R_WERKS.
    ENDIF.
    IF IT_PARA-MRP01 = '3'.
      R_MATNR-SIGN = 'I'.
      R_MATNR-OPTION = 'CP'.
      R_MATNR-LOW = IT_PARA-MRP03.
      COLLECT R_MATNR.
    ENDIF.
    IF IT_PARA-MRP01 = '4'.
      R_MATKL-SIGN = 'I'.
      R_MATKL-OPTION = 'CP'.
      R_MATKL-LOW = IT_PARA-MRP03.
      COLLECT R_MATKL.
    ENDIF.
ENDLOOP.
LOOP AT XMSEG INTO WA_MSEG.
    IF WA_MSEG-BWART = '101' OR WA_MSEG-BWART = '103'.
      IF WA_MSEG-WERKS IN R_WERKS.
        IF NOT WA_MSEG-MATNR IN R_MATNR.
          SELECT SINGLE * INTO WA_MARA FROM MARA
          WHERE MATNR = WA_MSEG-MATNR.
          IF NOT WA_MARA-MATKL IN R_MATKL.
            read table IT_ZMRP_LOT_SIZE with key werks = wa_mseg-werks
                                                 matnr = wa_mseg-matnr.
            if sy-subrc = 0.
              it_zmrp_lot_size-RECEIVE_SIZE =
                  it_zmrp_lot_size-RECEIVE_SIZE + wa_mseg-MENGE.
              if it_zmrp_lot_size-ALLOW_SIZE <
                        it_zmrp_lot_size-RECEIVE_SIZE.
               perform unlock_data.
               perform display_info.
                loop at it_zmrp_lot_size into wa_zmrp_lot_size.
                  CALL FUNCTION 'DEQUEUE_EZ_ZMRP_LOT_SIZE'
                    EXPORTING
                      MODE_ZMRP_LOT_SIZE = 'E'
                      MANDT              = SY-MANDT
                      WERKS              = wa_zmrp_lot_size-werks
                      MATNR              = wa_zmrp_lot_size-matnr.
                endloop.
                CALL FUNCTION 'DEQUEUE_EZ_MRP_PARAMETER'
                  EXPORTING
                    MODE_ZMRP_PARAMETER = 'S'
                    MANDT               = SY-MANDT.
                l_msg = wa_mseg-ebeln.
                condense l_msg.
                concatenate 'num:' l_msg into g_msg.
                l_msg = wa_mseg-ebelp.
                condense l_msg.
                concatenate g_msg 'item' l_msg into g_msg.
                concatenate g_msg 'exceed max number'
                    into g_msg.
                MESSAGE g_msg type 'E'.
              else.
                modify it_zmrp_lot_size.
              endif.
            else.
              select single * into IT_ZMRP_LOT_SIZE from ZMRP_LOT_SIZE
              where werks = wa_mseg-werks
              and    matnr = wa_mseg-matnr.
              if sy-subrc <> 0.
               perform unlock_data.
               perform display_info.
                loop at it_zmrp_lot_size into wa_zmrp_lot_size.
                  CALL FUNCTION 'DEQUEUE_EZ_ZMRP_LOT_SIZE'
                    EXPORTING
                      MODE_ZMRP_LOT_SIZE = 'E'
                      MANDT              = SY-MANDT
                      WERKS              = wa_zmrp_lot_size-werks
                      MATNR              = wa_zmrp_lot_size-matnr.
                endloop.
                CALL FUNCTION 'DEQUEUE_EZ_MRP_PARAMETER'
                  EXPORTING
                    MODE_ZMRP_PARAMETER = 'S'
                    MANDT               = SY-MANDT.
                l_msg = wa_mseg-ebeln.
                condense l_msg.
                concatenate 'num:' l_msg into g_msg.
                l_msg = wa_mseg-ebelp.
                condense l_msg.
                concatenate g_msg 'item' l_msg into g_msg.
                concatenate g_msg 'exceed max number'
                        into g_msg.
                MESSAGE g_msg type 'E'.
              else.
                if it_zmrp_lot_size-ALLOW_SIZE <
                          it_zmrp_lot_size-RECEIVE_SIZE.
                 perform unlock_data.
                 perform display_info.
                  loop at it_zmrp_lot_size into wa_zmrp_lot_size.
                    CALL FUNCTION 'DEQUEUE_EZ_ZMRP_LOT_SIZE'
                      EXPORTING
                        MODE_ZMRP_LOT_SIZE = 'E'
                        MANDT              = SY-MANDT
                        WERKS              = wa_zmrp_lot_size-werks
                        MATNR              = wa_zmrp_lot_size-matnr
                  endloop.
                  CALL FUNCTION 'DEQUEUE_EZ_MRP_PARAMETER'
                    EXPORTING
                      MODE_ZMRP_PARAMETER = 'S'
                      MANDT               = SY-MANDT.
                  l_msg = wa_mseg-ebeln.
                  condense l_msg.
                  concatenate 'num:' l_msg into g_msg.
                  l_msg = wa_mseg-ebelp.
                  condense l_msg.
                  concatenate g_msg 'item' l_msg into g_msg.
                  concatenate g_msg 'exceed max number'
                       into g_msg.
                  MESSAGE g_msg type 'E'.
                else.
                 perform lock_data.
                  CALL FUNCTION 'ENQUEUE_EZ_ZMRP_LOT_SIZE'
                    EXPORTING
                      MODE_ZMRP_LOT_SIZE = 'E'
                      MANDT              = SY-MANDT
                      WERKS              = it_zmrp_lot_size-werks
                      MATNR              = it_zmrp_lot_size-matnr.
                  IF SY-SUBRC <> 0.
                   perform unlock_data.
                    loop at it_zmrp_lot_size into wa_zmrp_lot_size.
                      CALL FUNCTION 'DEQUEUE_EZ_ZMRP_LOT_SIZE'
                        EXPORTING
                          MODE_ZMRP_LOT_SIZE = 'E'
                          MANDT              = SY-MANDT
                          WERKS              = wa_zmrp_lot_size-werks
                          MATNR              = wa_zmrp_lot_size-matnr
                    endloop.
                    CALL FUNCTION 'DEQUEUE_EZ_MRP_PARAMETER'
                      EXPORTING
                        MODE_ZMRP_PARAMETER = 'S'
                        MANDT               = SY-MANDT.
                    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
                  ENDIF.
                  append it_zmrp_lot_size.
                endif.
              endif.
            endif.
          ENDIF.
        ENDIF.
      ENDIF.
    ENDIF.
ENDLOOP.
*****modify
IF it_zmrp_lot_size[] is not initial.
    modify zmrp_lot_size from table it_zmrp_lot_size.
endif.
perform unlock_data.
loop at it_zmrp_lot_size into wa_zmrp_lot_size.
    CALL FUNCTION 'DEQUEUE_EZ_ZMRP_LOT_SIZE'
      EXPORTING
        MODE_ZMRP_LOT_SIZE = 'E'
        MANDT              = SY-MANDT
        WERKS              = wa_zmrp_lot_size-werks
        MATNR              = wa_zmrp_lot_size-matnr.
endloop.
CALL FUNCTION 'DEQUEUE_EZ_MRP_PARAMETER'
    EXPORTING
      MODE_ZMRP_PARAMETER = 'S'
      MANDT               = SY-MANDT.
***************end
first question:
this segment code can't be debug even have set break point.
how to debug this segment.
second question:
use the same condition to execute MIGO_GR,but one usING BDC method with CALL TRANSCTION 'MIGO_GR' will go to this segment code and display message which set in USER EXIT code.
but other use TCODE MIGO_GR to receive goods and will create document successfully.
three question:
   have other method will be resolve my issue.
thank you advance!

close!

Badi under User Exit

Hi ,
In Badi there can be 'n' number of implementations but in User Exit it is only one implementation,can we do the user exit as 'n' number of implementation ?
For E.g: can we write Badi under User Exit? if so how is it possible can any one plz explain detaily?
Regards,
Chalapathi

Hi Chalapathi,
There are two types of BADIs
1. single used BADI : we can have one implementation for single requirement. If we want to use the same implemetation for another requirement also, we can write our code in already existing implemetation, BUt we can't create seperate implementation for that requirement.
2. multiple used BADI: we can have N number of implemetations. We can implement the BADI per requirement seperately.I found it usefull when we are creating subscreen (Custom tabs) in standard screens.
USER EXITS: User exits are like ABAP Perform in standard SAP programs. We can write code directly in between FORM & ENFORM and activate it. We can use the same exit for N number of requirements by adding our code to already existing one!
If we create a new BADI (single or multiple) we can use the USER exit to write code to call our new BADI. BUT it rarely happens.
Note: As suggested by Keshav, please dont post Interview Qs in FORUM.
Reddy

User-exit/BADI during outbound ABAP proxy call

Hello,
I want to introduce certain check during outbound ABAP proxy calls to PI. This is a generic check, failure of which would stop the proxy call to proceed and raise an exception.
I would like to place this at the generic place which is called for all the outbound ABAP proxy calls, rather than coding this in each and every outbound proxy class as the check is generic.
Is there some user-exit/BADI where i can introduce this? Maybe within class CL_PROXY_OUTBOUND or somewhere else where i can introduce this check.
Any help in this regard would be appreciated.
Best Regards,
Gajendra.

Dear Gajendra ,
i agree with sabrish, you must be having a z report on the application system that must be calling that outbound proxy...may be if the check is generic it may not be related to a proxy so you can code a FM and then call it before you call that proxy in the z report
Giving points is another way to say thanks

ABAP Objects available in a USER-EXIT

Dear Sir,
I am very new to ABAP / User-Exit . To learn about User-Exit , I was refereing one tutorial related to USER-EXIT implementation in VL01 (form userexit_save_document_prepare) .
Sir , in this sample User-Exit , author is referring ABAP Objects like : xlips-lgort / xlips-matnr etc .
Sir , my query is that how can we know that which objects are available which can be used in a User-EXIT . How a new user like me will come to know that object xlips-lgort can be used in this User-Exit .
Pl help me .
Regards
B Mittal

Hi,
A user exit is similar to an function module. The difference is you can write your own piece of code in a user exit to fulfill your requirements. If you look into the IMPORT parameters of the User Exit all these variable in the IMPORT are inputs to your exit. All the variables in the EXPORT parameters are the ones that can be sent out of the exit. You can change all the variables that are present in bothe IMPORT and EXPORT parameters. Ex: If i have V_data in IMPORT as well as EXPORT then i can change the value of V_DATA from 1 to 2 and pass it to next step in the standard program.
Also you have TABLES in user exit. These can be inputs and output parameters. For example i can enter a few records in the tables parameter IT_TAB in one of the exits and change these records inside the USer Exit include and export the same to the next step in the standard transaction.
Hope this is helpful.... reward if useful.
Thanks,
Anil
Edited by: Anil Japa on Mar 20, 2008 9:27 AM

ABAP-Programming for SAP BW u0096 User-Exits und BAdIs

Hi experts,
i am a novice und looking for informations about Badi and User-exits for BW .
i want to learn how to programm extractors.
Can you you help me by giving me some informations or documents or sap links where i can find informations?
Cheers

Dear Mr Herzog,
Congratulations for the book: Abap Developement for SAP Netweaver BI: User exits and BadIs.
We're trying to implement the suggestions on the chapter 5.1.1 Interface of function module EXIT_SAPLRSR0_001 (page 136), however, we're having problens with the abap sintax CALL_FUNCTION l_d_name IF FOUND.
The command IF FOUND is not accepted.
It'll be very helpful to avoid issues on tranporting include zxrsru01.
I appreciate any additional help on how to implement it.
Best Rgs
Eliseo Bouzan

ABAP program to search for FM/User-Exit lookups

Hi everyone,
I have a need to find any and all Function Modules and User Exits that may have been written in BW that are used to do a lookup of data from one InfoProvider to another.   I have found the following program from Lijo John which works for Update Rules and Transfer Rules but I need the same type program that digs into Function Modules, DTP's and any other User-Exit type code where a lookup could be performed.   These are noted as the limitations in the program Lijo John created and I was hoping maybe someone has a solution for these as well.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/bi/abapprogramtofindBIlookupsandcodePatterns
If someone has a program that they could share that would do this it would be greatly appreciated.
Thank you,
Dave

Thank you Ashish. This was somewhat helpful.   I guess if there isn't an ABAP program available like I need then the next best thing would be for me to know the BW table names that holds the actual Function Module and DTP source code so that I can then create my own ABAP program that would query them for the existence of the InfoProvider name anywhere in the code.
The goal with all of this is to find ANY lookup from ANYWHERE in BW for a specific InfoProvider so that we will know what will have to be "disconnected" if we decide to get ride of that specific InfoProvider.
So, if anyone can tell me the tables that contain the BW Function Module and DTP ABAP source code I would appreciate it.
Thank you,
Dave

Regarding Enhancements/User-Exits in ABAP

Hi,
Can anybody tell me What is meant BY Enhancements & User-Exits.
Also what are diffrent types of Enhancements/User-Exits avialable.
Can anybody explain me about diffrent types of Enhancements/User-Exits.
Can anybody provide me documentation with the examples
for diffrent types of Enhancements/User-Exits.
If anybody is having good material on the same please post it.
Thanks in advanace.
Thanks & Regards,
Rayeez.

Customizing exits allow you to add your own functionality to SAPs standard business applications without having to modify the original applications. SAP creates customer 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.
If you want to enhance the functionality of your R/3 System, you should take advantage of the exits available in standard R/3 applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
     They do not affect standard SAP source code
When you add new functionality to your SAP System using SAPs exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAPs standard software package.
     They do not affect software updates
When you add new functionality to your R/3 System using SAPs exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects names ensure that they will not be affected by any changes or new additions to the standard software package.
Customer exits are not available for all programs and screens found in R/3 standard applications. You can only use customer exits if they already exist in the R/3 System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits.
     As part of the enhancement concept, it is possible for the customer to
     add his own elements to application logic, screens and menus.
The current possibilities for enhancement are:
Text enhancements:
     Allow the customer to add supplementary documentation for data fields
     non-specific to a transaction, and to change key word texts.
Field exits:
     Every screen element with data element reference can branch to PBO or
     prior to PAI to a function module if desired. The field contents are
     available here for doing special checks and making changes (e.g. user-
     specific checks, authority checks, writing entered data and producing
     statistics...).
Function exits:
     From the main program you branch into a software level, in which you you
     can store ABAP/4 coding. The applications programmer at SAP determines
     where in the main program the function exit is placed, and which data is
     imported/exported via the interface. The accompanying documentation
     describes the functionality of the function exit.
     Menu enhancements:
     Pre-conceived menu items can be activated and named. On the function code
     set at menu item selection, there can be a reaction in a relevant
     function exit.
Screen enhancements:
     The customer can determine the layout of areas in screens provided by the
     applications developer. Here, additional information can be displayed or
     data entered.

User exits in HR-ABAP

Similar Messages

Maybe you are looking for