Scribd
Upload
221 views2 pages

Sap Bte

BTE, or Business Transaction Event, is an enhancement type developed for financial accounting in SAP. It allows customizing via transaction FIBF. The main steps to activate a BTE are to check documentation, copy a sample function module, make sure the application is active for BTEs, maintain tables TBE11, TBE34 and TBE01, and enter code in the BTE function module. There are two types of BTE interfaces: publish/subscribe interfaces that provide event data without returning any, and process interfaces that allow external control of business processes by interrupting standard processes.

Uploaded by

subhastt
Copyright
© Attribution Non-Commercial (BY-NC)
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
221 views2 pages

Sap Bte

BTE, or Business Transaction Event, is an enhancement type developed for financial accounting in SAP. It allows customizing via transaction FIBF. The main steps to activate a BTE are to check documentation, copy a sample function module, make sure the application is active for BTEs, maintain tables TBE11, TBE34 and TBE01, and enter code in the BTE function module. There are two types of BTE interfaces: publish/subscribe interfaces that provide event data without returning any, and process interfaces that allow external control of business processes by interrupting standard processes.

Uploaded by

subhastt
Copyright
© Attribution Non-Commercial (BY-NC)
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/ 2

BTE - Business Transaction Event

Added by Peter Inotai, last edited by Alon Mizrahi on Nov 01, 2011 (view change)

BTE - Business Transaction Event Enhancement type developed for FI (Financial Accounting). SAP Reference IMG -> Financial Accounting -> Financial Accounting Global Settings -> Business Transaction Events . Customizing can be done via transaction FIBF. Main steps for activating a BTE: 1. Check OSS note for documentation and explanation 2. Copy sample function module SAMPLE_INTERFACE_<event_number> to Customer namespace 3. Make sure the application is active for Business Transaction Events , else maintain table TBE11. 4. Maintain table TBE34 and TBE01 5. Enter code to the BTE function module How to check/debug? To check the functionality, you can put a break-point in your BTE function module. If it's not called, put a breakpoint at FM OPEN_FI_PERFORM_<BTE number>_E. Related Transaction Code : 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 BTE exits to add additional components to the SAP standard system, for example in the form of function modules. There are two types of interface: Publish and Subscribe interfaces

These give information that specific events have occurred in the SAP standard application and provide the data generated to external software. However the external software does not return any data to the SAP standard system. Process interfaces

These subject business processes to an external control function that is not part of the standard system; in other words the process interfaces interrupt the standard process and deliver data to the SAP application. A BTE exit is called up in the process, meaning that process modules check the events in Customizing for calling up the BTE exits. In the BTE method, function modules are called up in specified events, to which they have been assigned in Customizing. The event interface is predefined. To activate the process modules, choose _Settings for Process Interfaces -> Assign Customer Function Modules to Process Interfaces.

You might also like