Posted by Vinod Vemuru in SAP ERP Financials on May 13, 2014
http://scn.sap.com/community/erp/financials/blog/2014/05/13/how-to-search-bte
Are you facing difficulties in finding out correct BTE to implement for your custom requirements? Doing extensive search over net/SCN? Not required now!!!
Yes, SAP has already given awesome “BTE search tool” which many people are unaware. I came across this interesting tool during my R&D and found it very helpful.
Hence, sharing this with the community.
Before we go on how to use this tool, let us go through little basics of BTE.
Business transaction event is delivered by SAP to code customer specific requirements during predefined standard processes. Call points are already defined by SAP. All we need to do is just plug in our code in the BTE based on our requirements and SAP would play it during standard process
Business transaction events are of two types.
Process BTE:
Process BTEs are called at a fixed, predefined points during the standard SAP program flow at which the system can process user defined/custom function modules instead of the standard function module. The pre-conditions/rules for calling up alternative processes are defined in the customization of BTEs in t-code FIBF. There would be standard function module OPEN_FI function module assigned by default by SAP. If there are no custom function modules assigned in FIBF, standard function module is processed. Data and process flow of standard SAP can be changed in BTE.
OPEN_FI function module select the FM to be processed for P/S BTE.
Function module PC_FUNCTION_FIND determines the function module to process from the following tables (equal priority):
a) TPS34 Customer-Specific Function Modules
b) TPS32 Partner Function Modules
c) TPS31 SAP Function Modules
d) TPS01 Standard Function Module
Publish & Subscribe (P/S) BTE:
P/S BTEs are called at a fixed, predefined points during the standard SAP program flow. Data can only be published to another application through P/S BTE i.e. we can only export the data to P/S BTE. Changes to program flow or data can’t be performed here. The pre-conditions/rules for calling up alternative processes are defined in the customization of BTEs in FIBF.
OPEN_FI function module select the FM to be processed for P/S BTE.
Function module BF_FUNCTIONS_FIND which is called inside OPEN_FI function module determines the function modules to process from the following tables:
a) TBE34 Customer-Specific Function Modules
b) TBE32 Partner Function Modules
c) TBE31 SAP Function Modules
(Source: Partly from F1 help)
How to search BTE:
Assume you have business requirement to implement a custom functionality to send an SMS alert to customers when dunning run is done. Since standard SAP does not have such functionality,
You can look for BTE for this.
Go to below t-codes
BERP: To search for process BTE
BERE: To search for P/S BTE
Both t-codes have same selection fields.
Select the attribute type A (Application component) and click F4 on selection attributes field.
In the next popup, drill down to the process area you are looking for. The paths displayed here are similar to SPRO path.
Select appropriate node. In this case it is DUNNING.
Path would come as shown below.
You can further restrict the search by entering other selection parameters which are self-explanatory. Now execute the program.
Output would show the list of available BTEs for the given node. Most of the times, description of the BTE says functionality.
Select appropriate BTE and use below tool bar options to explore further. We can see the sample FM delivered by SAP, interface of the BTE, Documentation etc.
Custom FMs can be created with the same interface as of sample FM. One common error seen while implementing the BTE is, custom FM interface may differ than standard FM interface.
In this case, the process would go for dump. This is because, SAP determines the FM name during run time (Dynamic call).
Similarly, search can be done based on other parameters like based on Business object name, IMG nodes etc.
You are welcome to post your comments and feedback on this blog
Regards,
V V
