Difference Between User Exits, Screen Exits and Field Exits
What are the differences between user, screen and field exits?
Let me answer this question for you:
The basic rule in SAP as far as ABAP workbench developments are concerned is "Do not modify the source code of the program"
Since needs and requirements keep on changing from client to client and for various business scenarios, there is a need to customise the programs as per client requirement.
For this purpose, SAP has provided numerous list of user-exits also known as enhancements, which is nothing but a program which will deal with the client additional requirement, without modifying the source code of the program. These exits are already provided by SAP. You can see the list of user-exits provided by using the transaction code SMOD. If you cannot find an user exit which match with client requirements, then you can tell SAP to create a new user exit.
On the other hand, field exit is nothing but where you write a small program, to control the properties of an existing field in a particular screen. Hence creation of a field exit is controlled by Program name, screen no. and the field name.
To give you an example, if you want to prevent a particular payment method to be executed via transaction FBZ5 or F-58, such that if the user enter a particular payment method while executing the transaction FBZ5 or F-58, the system should restrict the user from proceeding further, u can write a field exit for field RZAWE (payment method).
The program which controls the creation of field exit is RSMODORF
As far as screen exit is concerned, as per the client requirement if the user wants a separate screen to appear on execution of a particular task, which deviates from the standard sap provided flow of transactions, you write a screen exit. In such case you first prepare the screen using the screen painter and define it as to after which sap screen you want this screen to appear for processing the transaction further.
What are the differences between user, screen and field exits?
Let me answer this question for you:
The basic rule in SAP as far as ABAP workbench developments are concerned is "Do not modify the source code of the program"
Since needs and requirements keep on changing from client to client and for various business scenarios, there is a need to customise the programs as per client requirement.
For this purpose, SAP has provided numerous list of user-exits also known as enhancements, which is nothing but a program which will deal with the client additional requirement, without modifying the source code of the program. These exits are already provided by SAP. You can see the list of user-exits provided by using the transaction code SMOD. If you cannot find an user exit which match with client requirements, then you can tell SAP to create a new user exit.
On the other hand, field exit is nothing but where you write a small program, to control the properties of an existing field in a particular screen. Hence creation of a field exit is controlled by Program name, screen no. and the field name.
To give you an example, if you want to prevent a particular payment method to be executed via transaction FBZ5 or F-58, such that if the user enter a particular payment method while executing the transaction FBZ5 or F-58, the system should restrict the user from proceeding further, u can write a field exit for field RZAWE (payment method).
The program which controls the creation of field exit is RSMODORF
As far as screen exit is concerned, as per the client requirement if the user wants a separate screen to appear on execution of a particular task, which deviates from the standard sap provided flow of transactions, you write a screen exit. In such case you first prepare the screen using the screen painter and define it as to after which sap screen you want this screen to appear for processing the transaction further.
번호 | 제목 | 글쓴이 | 날짜 | 조회 수 |
---|---|---|---|---|
127 | 새로운 Session을 생성하는 방법 [7] | 양키 | 2013.07.17 | 4963 |
126 | SCN에서 인기있는 Tutorial강좌들 입니다. [1] | 양키 | 2013.08.12 | 8421 |
125 | [덤프해결] CX_SY_READ_SRC_LINE_TOO_LONG | 양키 | 2013.08.16 | 7823 |
124 | Field Catalog 가져오지 못하는문제(REUSE_ALV_FIELDCATALOG_MERGE) [3] | 양키 | 2013.08.16 | 9586 |
123 | 메세지 팝업창 뛰워주는 Function [2] | 양키 | 2013.08.19 | 7937 |
122 | zebra printer 상세 사용메뉴얼입니다. | 양키 | 2013.08.26 | 3746 |
121 | 입력 필드 입력 중 이력이 지원되지 않는 문제 해결법. [1] | 장용천 | 2013.09.03 | 8601 |
120 | REM TABLE1 | 밤의화신 | 2013.09.11 | 2870 |
119 | REM TABLE2 | 밤의화신 | 2013.09.11 | 2822 |
118 | REM TABLE3 | 밤의화신 | 2013.09.11 | 2658 |
117 | REM PROCESS1 | 밤의화신 | 2013.09.11 | 5405 |
116 | REM PROCESS2 [1] | 밤의화신 | 2013.09.11 | 4500 |
115 | ABAP 교육 [13] | 밤의화신 | 2013.09.11 | 8495 |
114 | ABAP 교육 [32] | 밤의화신 | 2013.09.11 | 8497 |
113 | ABAP 교육 [12] | 밤의화신 | 2013.09.11 | 7290 |
112 | ABAP 교육 [6] | 밤의화신 | 2013.09.11 | 7275 |
111 | ABAP 교육 [6] | 밤의화신 | 2013.09.11 | 7204 |
110 | ABAP 교육 [9] | 밤의화신 | 2013.09.11 | 7391 |
109 | ABAP 교육 [13] | 밤의화신 | 2013.09.11 | 8363 |
108 | 요약파일1 [7] | 밤의화신 | 2013.09.11 | 8042 |