Scribd
Upload
55 views15 pages

Bte - Fibf

BTEs (Business Transaction Events) are enhancements in SAP that allow modifications to core processes, similar to BADIs, and are strategically placed in transactional processes. They are used when standard SAP processes do not align with organizational requirements, and can be identified through specific transactions like FIBF and FIBF. The document outlines the steps to implement and test a BTE, including creating custom function modules and linking them to events.

Uploaded by

dipnar6379
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
55 views15 pages

Bte - Fibf

BTEs (Business Transaction Events) are enhancements in SAP that allow modifications to core processes, similar to BADIs, and are strategically placed in transactional processes. They are used when standard SAP processes do not align with organizational requirements, and can be identified through specific transactions like FIBF and FIBF. The document outlines the steps to implement and test a BTE, including creating custom function modules and linking them to events.

Uploaded by

dipnar6379
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 15

BTE – What are they?

BTEs are similar to BADIs (Business Add-Ins) and as such, BTE performance is
equally as good. BADIs typically provide windows into existing processes to allow
modifications to be made to enhance SAP processes to fit an organization’s
requirements. The BTEs are positioned strategically in transactional processes to
allow enhancements to core SAP processes which will be supported with future SAP
releases.
Field Bank Account for Vendor (FK02) should not be allowed to be initial.
In tcode FINF (BTE) there is an event with number 00003000 (Bank Details Check)
BTE – When do we use them?
Typically, these are used when standard SAP processes and organizational process
requirements are not consistent.
To find if there are BTEs available for use, there are 2 ways of determining them.
- Check in transaction FIBF or in the SAP menu path: SAP Reference IMG ->
Financial Accounting -> Financial Accounting Global Settings -> Business
Transaction Events
- Open the main program of the transaction you are wanted to enhance and search
for character string “OPEN_FI_PERFORM” in the source code.

In this tutorial, we would focus on triggering a BTE whenever a vendor data is


changed (Transaction FK02)

Go to transaction FIBF

IMG Menu Path: Financial Accounting ->Financial Accounting Global Settings-


>Business Transaction Events-> Environment-> Infosystem (Processes).
Click on execute. Look for the appropriate event that fulfills our requirement.
Double click on the corresponding BTE. Click on the Sample Function module.
Copy the interface into the custom function module (z*). The desired logic is coded
in the custom function module. The interface of the function module should never
be changed.

Additional logic can be coded in the function module. Save and activate the function
module.
The next step is to create a Product that links the event with the function module.
Products are created in the same transaction FIBF.
Click on the “New Entries” button.
Enter the product name description and RFC destination if applicable. The check
box A is to activate the product.

The next step is to link the function module and the event using the product
created. The path is shown below.
Click new entries and enter the event and the function module.

Testing the BTE. For our case go to transaction FK02, that changes the vendor
data.

Make a small change in the existing vendor’s data.


Upon save, the BTE associated with the event will be triggered.

Apply a break point in the function module associated with the event to check the
triggering.
>>>>>>>>>>>>>>>>>>>>>>>>>
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
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 might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy