BTE的设计思路还是比较简单，和BADI有点类似。在标准程序中留有OPEN_FI的出口(以函数OPEN_FI_PERFORM_event id_type的形式存在)，然后提供一个可配置的TABLE，可以在里面针对某个特定的Event维护自己定义的出口函数，标准程序走到这里，如果查出用户定义了出口函数，则会调用，达到增强的目的。
All BTE configuration options are accessible from Transaction FIBF. Configuration activities for the BTE framework are located in the menu in Settings. Each BTE configuration activity is divided into three groups:
SAP internal
This area includes the entire configuration that SAP delivers with the installation.
Partner
This configuration area belongs to SAP’s software development partner that is developing its own add-on or application component.
Customer
This area belongs to each end-client/business that is developing application extensions for its own needs.
1.查看系统有哪些BTE被实现了：
TCODE : FIBF
操作如下：菜单 setting - P/S module只能使用值 (Process module 可以修改值) - customer （菜单操作类似于
TCODE: BF34 BF44）
这里看到的就是实现。
例如：
图中的product是在这里定义的，就是一个字符 + 描述 setting - product - customer (同功能的tcode: BF24)
这里可以配置是否是激活的状态。或者远程的RFC 目标（没有研究）。
2.BF03可以查看到有哪些event id;
或者通过数据库表：TBE01 (P&S) TPS01(PROCESS)
或者在需要查找BTE增强的主程序中查找字符串：OPEN_FI_PERFORM_ ,应该程序调用BTE是会有 关键字：“OPEN_FI_PERFORM_eventid_type” eventid 例如：00001250 type：‘E’ OR 'P'.
复制Sample Function Module到Z* function module，上图中是 ZUIF_EAI_MATERIAL.
所以BTE的处理逻辑将在Z*的function module中处理
3.创建Z* function module后需要配置到product 中，并在这里配置增强是否激活。BF24
4.再通过BF34 / BF44 把function module和product 关系对应。
------End-----
一些相关的TCODE:
FIBF Maintenance transaction BTE
BERE Business Event Repository
BERP Business Processes
BF31 Application modules per Event
BF32 Partner Modules per Event
BF34 Customer Modules per Event
BF41 Application Modules per Process
BF42 Partner Modules per Process
BF44 Customer Modules per Process
FIBF Maintenance transaction BTE
BERE Business Event Repository
BERP Business Processes
BF31 Application modules per Event
BF32 Partner Modules per Event
BF34 Customer Modules per Event
BF41 Application Modules per Process
BF42 Partner Modules per Process
BF44 Customer Modules per Process