BTE

[Former Member]

Hi Friends,

I have got some documents on BTE, i got an idea how do i copy the SAMPLE_INTERFACE_* to ZSAMPLE_INTERFACE_*

but could you pls explain me what are my next steps...

as the documents i have doesnt give me a good understanding abt that, i would be grateful if somebody could explain me the step-by-step procedure as well...

the help would be very well appreciated.

regards

srini

[Former Member]

Hi,

You can use 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 & 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. For more information on activating user exits, see the sample modules in the documentation on function modules.

What are Business Transaction Events

-> The enhancement technique (Open FI) that were developed for Financial Accounting component.

-> Open FI is based upon the following principles: Application developers must define their interface in a function module, an assignment table is read in the accompanying (generated) code, and the customer modules assigned are called dynamically.

-> This technique differentiates between enhancements that are only allowed to have one implementation and enhancements that can call multiple implementations in any sequence desired. Both industry-specific and country-specific enhancements may be defined.

-> This can be easily adopted / customized to the business needs wherein SAP does not provide the standard functionality through customization or enhancements. This functionality is primarily used in FI in the areas of dunning, credit management, banking etc. For Example: Standard Dunning functionality in SAP sends the notice to the Pay to partner function (based on the partner functions in SD module i.e. pay to hits the books in Accounts Receivable in FI module), whereas the requirement could be to send the same to Bill to party, based on the premise that the original invoice was sent to him as per the partner functions in SD.

Basic Steps in Configuring Business Transaction Events

-> Make sure the application is active for Business Transaction Events.

-> Identify the BTE �� Copy the sample interface function module into a "Z” or “Y” function module.

-> Write the ABAP code into the source code section of the new "Z” or “Y” function module. You may choose to create a "Z” or “Y” program to enter the code into and then insert the "Z" or “Y” program into your function module source code. -> Save and activate the function module.

-> Assign the function module to the event, country and application.

Have a look at below link.

http://help.sap.com/saphelp_nw04/helpdata/en/3b/7f3e8be57c11d1951f0000e82dec10/content.htm

Regards

[Former Member]

following are the steps which are needed for implemting the BTE :

You can use transaction FIBF (called when you selected Use business transaction events from the financial accounting hierarchy) to carry out all necessary activities prior to using a business transaction event.

First, choose an interface to which you would like to attach your function module. The Interface button displays the parameter structure for the interface you have selected. You can also use the documentation to determine what functions each interface allows you to perform.

Use the ABAP Workbench to copy the sample function module sample_interface_<n> to the customer namespace (z_*) of a customer function group. You must not change the interface. You can fill the module with any source text except COMMIT WORK. Do not use a COMMIT WORK! Don't forget to activate the function module.

Create a product in the administration screen.

Assign a number to your function module and product.

The following link will help

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/207835fb-0a01-0010-34b4-fef1240b....

Hope it helps.

Thanks and Regards,

Smriti

Smriti Singh

[Former Member]

BTE(Business transaction events) is an enhancement technique that was developed for Financial Accounting component of R/3.

Following are the principles on which the BTE is based:

Application developers must define their interface in a function module. An assignment table is read in the accompanying (generated) code, and the customer modules assigned to the events are called dynamically.

This can be easily adopted / customized to the business needs wherein SAP does not provide the standard functionality through customization or enhancements.

Comparing BTE with BADI:

Unlike BADIu2019s , BTEu2019s could only be used for Program enhancements, and not for enhancing the gui elements.

BTE uses function modules for program enhancements. With Business Add-Ins, ABAP Objects are used enhance programs.

Types of Interfaces in BTE:

There are two types of interface available

a) Publish and Subscribe Interface

b) Process Interface

in the General Ledger Accounting (FI-GL), Accounts Receivable and Accounts Payable (FI-AR/FI-AP) and Sales and Distribution (SD) components.

Publish and Subscribe Interface

Publish & Subscribe interfaces (also called "informing interfaces" in the following)

These should inform you about particular events (such as a document being entered) in the SAP standard application and make the data generated as a result available to the external software. The external software does not return any data to the standard R/3 System. Examples of such events in the R/3 System are:

Document was entered, parked, changed, or reversed

Master record was created, changed, or blocked

Process Interface

Process interfaces (also referred to as "process" in the following)

Process interfaces are used to submit business processes to a different control which cannot be realized with the standard system, that is process interfaces replace standard processes.

Here you can structure determination of individual field contents or of specific reactions to process flows individually. It is possible to connect different external developments to the standard R/3 System. The additional developments are generally carried out using the ABAP/4 Development Workbench.

Basic Steps in Configuring Business Transaction Events

􀂾Make sure the application is active for Business Transaction Events.

􀂾Identify the BTE

􀂾Copy the sample interface function module into a "Zu201D or u201CYu201D function module.

􀂾Write the ABAP code into the source code section of the new "Zu201D or u201CYu201D function module. You may choose to create a "Zu201D or u201CYu201D program to enter the code into and then insert the "Z" or u201CYu201D program into your function module source code.

􀂾Save and activate the function module.

􀂾Assign the function module to the event, country and application.