Explain about What is User Exits and Customer Exits?

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.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Difference between user exits & customer exits:

User exit - A user exit is a three character code that instructs the system to access a program during system processing.

SXX: S is for standard exits that are delivered by SAP.   XX represents the 2-digit exit number.

UXX: U is for user exits that are defined by the user.  XX represents the 2-digit exit number

Customer exit - 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 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.     *-- Mani

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.

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.

时间: 2024-08-24 09:05:35

Explain about What is User Exits and Customer Exits?的相关文章

SAP USER-EXITS && Customer EXITS

Enhancements using Customer Exits / User Exits (Find a program exit that is implemented using a customer exits, and use them to enhance functions ) There are several types of Customer Exits :Menu Exits, Screen Exits, Function Module Exits, Field Exit

MYSQL EXPLAIN执行计划命令详解(支持更新中)

本文来自我的github pages博客http://galengao.github.io/ 即www.gaohuirong.cn 摘要: 本篇是根据官网中的每个一点来翻译.举例.验证的:英语不好,所以有些话语未必准确,请自行查看官网,若有些点下面没有例子的是因为当时一下子没有想出那么多来,如果大家有遇上好的例子,欢迎在下面留言我持续更新 查看执行计划的关键EXPLAIN 版本MYSQL5.6,用到的库是官网例子sakila,自行下载导入 由于要把每个点都翻译出来,还需要举例,所以需要一定的时间

mysql explain type

explain执行计划中type字段分为以下几种: ALL        INDEX        RANGE        REF        EQ_REF        CONST,SYSTEM        NULL 从左至右,性能从最差到最好 type = ALL,全表扫描,MYSQL扫描全表来找到匹配的行 (因为film表中rating不是索引) mysql> explain extended select * from film where rating > 9\G ******

SAP问题【转载】

1.A:在公司代码分配折旧表时报错? 在公司代码分配折旧表时报错,提示是"3000 的公司代码分录不完全-参见长文本" 希望各位大侠帮我看看. 3000 的公司代码分录不完全-参见长文本 R: a.你把零进项税的代码分配给这个公司代码就可以了 .没有指定非税代码,OBCL b.据此可能company code 设置有问题,检查一下OBY6 2.a,维护客户科目组:财政供应链管理->现金和流转情况管理->现金管理->主数据->子分类帐科目->客户控制->

SAP错误问题汇总

1.A:在公司代码分配折旧表时报错? 在公司代码分配折旧表时报错,提示是"3000 的公司代码分录不完全-参见长文本" 希望各位大侠帮我看看. 3000 的公司代码分录不完全-参见长文本 R: a.你把零进项税的代码分配给这个公司代码就可以了 .没有指定非税代码,OBCL b.据此可能company code 设置有问题,检查一下OBY6 2.a,维护客户科目组:财政供应链管理->现金和流转情况管理->现金管理->主数据->子分类帐科目->客户控制->

MongoDB数据库索引

前面的话 索引通常能够极大的提高查询的效率,如果没有索引,MongoDB在读取数据时必须扫描集合中的每个文件并选取那些符合查询条件的记录.这种扫描全集合的查询效率是非常低的,特别在处理大量的数据时,查询可以要花费几十秒甚至几分钟,这对网站的性能是非常致命的.本文将详细介绍MongoDB数据库索引 引入 索引能够提高查询效率,如何体现呢?接下来使用性能分析函数explain()来进行分析说明 首先,插入10万条数据 接着,不创建索引,来寻找time范围在100和200之间的文档 由图中所知,tot

[ZT]Enhancement-01

Enhancement(1)--BTEs 最近一个同事碰到一个FI的增强,要用BTEs实现,我也是第一次接触到这种增强,所以跟着他一起做了一下.写一个这方面的小节. BTEs(Business Transaction Events),是SAP的一种增强方式,技术上讲是介于Customer Exits和BAdIs的产物. 它主要有两种类型的接口: Publish and Subscribe Interface Process Interface 其比较核心的理念是,使一个接口重复利用,多种实现并且

【ZT】Enhancement Framework – Introduction

Enhancement Framework – Introduction By Naimesh Patel | March 26, 2014 | Enhancement Implementation ABAP Enhancement Implementations concept which allows you to easily enhance the standard SAP delivered functionality with your desired one. With this

SAP 中如何寻找增强

方法一.利用TCODE寻找增强(第二代的增强) 执行一个程序(源代码后附),在选择屏幕处输入你所需要增强的程序TCODE,执行後,就会出现一个列表,那里就有关于如何增强这个的绝大部分SMOD增强. 点击进去,自己手动寻找需要的增强. 这是第二代增强 方法二.利用系统函数寻找         MODX_FUNCTION_ACTIVE_CHECK 在这个FUNCTION的代码最后添加一个断点.执行需要增强的TCODE,如果有增强,就会自动跳入DEBUG界面.在DEBUG界面,查看f_tab字段,这里