Scribd
Upload
92 views5 pages

Business Transaction Events

Business Transaction Events (BTEs) allow implementing program exits using function modules and have been available since Release 4.0. BTEs are generally found in financial accounting, accounts receivable/payable, and sales and distribution. A BTE has a predefined interface and allows attaching additional functionality as a function module. There are two types of BTEs - publish/subscribe interfaces that cannot update data and process interfaces that can update data but only allow one active implementation. BTEs can be found by searching for code containing "OPEN_FI_PERFORM" or "OUTBOUND_CALL_" or using transaction FIBF.

Uploaded by

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

Business Transaction Events

Business Transaction Events (BTEs) allow implementing program exits using function modules and have been available since Release 4.0. BTEs are generally found in financial accounting, accounts receivable/payable, and sales and distribution. A BTE has a predefined interface and allows attaching additional functionality as a function module. There are two types of BTEs - publish/subscribe interfaces that cannot update data and process interfaces that can update data but only allow one active implementation. BTEs can be found by searching for code containing "OPEN_FI_PERFORM" or "OUTBOUND_CALL_" or using transaction FIBF.

Uploaded by

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

Business Transaction Events (BTEs) have been available as of Release 4.

0 and are another


technique for implementing program exits, and only program exits.

BTEs are generally found in the general ledger accounting (FI-GL), account receivable and
payable (FI-AR and FI-AP) and sales and distribution components.

A BTE has a predefined interface and allows you to attach additional functionality in the form of
a service funtion module.You must create funtion module with the parameters you have
previously dictated. The BTE is called by the SAP standard program by a call to function
OPEN_FI_PERFORM_ or OUTBOUND_CALL_. This function checks if there are any active
BTEs according to customizing.

According to its Interface there are 2 types of BTEs:

Publish & Subscribe interfaces. Can not update data. Possible to have multiple
implementations

Process interfaces. Can update date. Only one active implementation

How to find a BTE (2 ways)

 Search the source code for for "OPEN_FI_PERFORM" og " OUTBOUND_CALL_"


 Use transaction FIBF menu Environment->Info System (P/S ). Use the Documentation
button to see the documentation for the BTE.
Implementing the BTE

 Goto transaction FIBF menu Environment->Info System (P/S )

 Select the BTE you want to implement. (as below)


 Double click on Sample function module

 Then we copy the sample function module to a Z-function module (First create a new
function group for the function module) .

Note: The name of the Z-function module is not important

 Edit the code in the new function module:


 Go back to transaction FIBF - Menu Settings->Products -> Of a customer and create a
new product which identifies the new product .

Remember to mark the Active field.

 We 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. Go
back to FIBF menu Settings->P/S function modules->of a customer - Create an entry that
links the BTE and Product with the new function module (as below)

 And that´s all, we only need to save and activate.

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