topic Re: Regarding BTE in Application Development and Automation Discussions

Regarding BTE

Former Member — Thu, 11 Oct 2007 07:00:19 GMT

HI all,

Any one can give me the brief description of BTE(Business Transaction Event)

how it useful? where it is useful? how can we use? how can we implment that?

Thanks

Sandeep

Re: Regarding BTE

Former Member — Thu, 11 Oct 2007 07:02:08 GMT

Business Transaction Events

It is also called as Open FI enhancement technique which is based on the following principle:

Application developers must define their interface in a function module. An assignment table is read in the corresponding (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.

Reward if usefull

Re: Regarding BTE

former_member404244 — Thu, 11 Oct 2007 07:03:03 GMT

hI,

CHECK the below link..

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

Reward if helpful.

Regards,

nagaraj

Re: Regarding BTE

Former Member — Thu, 11 Oct 2007 07:04:53 GMT

http://fuller.mit.edu/user_exits/business_transaction_event.htm

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

http://fuller.mit.edu/sb_support/media_lab/tbe01_business_transaction.htm

Reward if usefull

Re: Regarding BTE

RaymondGiuseppi — Thu, 11 Oct 2007 07:05:12 GMT

Look at thos sdn contribution <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/207835fb-0a01-0010-34b4-fef1240ba9b7">FI Enhancement Technique – How-To-Guide on the Usage of Business Transaction Events (BTE)</a>

What are Business Transaction Events

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

o 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.

o 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.

o 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.

Difference between BADI’s and BTE’s

The concepts behind the Business Add-Ins enhancement technique and Open FI are basically the same. However, the two enhancement techniques do differ from each other in the following points:

o Open FI can only be used to make program enhancements, that is, you can only enhance source code using Open FI. You cannot enhance user interface elements with Open FI like you can with Business Add-Ins.

o Open FI assumes that enhancement will only take place on three levels (SAP - partners - customers), whereas with Business Add-Ins you can create and implement enhancements in as many software layers as you like.

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

Regards

Re: Regarding BTE

Former Member — Thu, 11 Oct 2007 07:06:07 GMT

Hi Sandeep.

SAP business transaction events are one type of customer enhancements provided by SAP.

This activity describes how you can connect additional components (such as in the form of function modules developed yourself or a product from an external software provider) to the standard SAP system.

There are two types of interface available in the General Ledger Accounting (FI-GL), Accounts Receivable and Accounts Payable (FI-AR/FI-AP), and Sales and Distribution (SD) components for this:

1. 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 SAP system. Examples of such events in the SAP system are:

Master record was created, changed, or blocked

Document was entered, parked, changed, or reversed

Items were cleared or reset

Additional processing can be caused in the additional component on the basis of these events and data:

Starting a workflow

Generating or changing additional data

Requesting correspondence

2. 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 SAP system. The additional developments are generally carried out using the ABAP/4 Development Workbench.

This way you can, for example, influence the control of payment transactions. Selection of payment method, house bank and partner bank can be made using the payment data (currency, amount, and payee) according to a selection logic which you have defined.

Standard settings

Sample modules are delivered in the standard SAP system which you can copy into your name range and fill them with statements there.

Activities

1. Enter a product using "Settings -> Customer's products". There are generally a large number of function modules belonging to a product which can be called by different program events from within the standard SAP system. A product can also be an external software component.

If the product is in an external system, enter an RFC destination here. If the product is in the same system, you do not have to enter anything.

Important: Do not forget to activate the product after making the following settings.

2. Establish the interfaces with which the SAP system provides you.

To do this, choose Environment -> Info system (P/S) or Environment -> Info system (Processes).

Execute the program. You should enter "A" as the attribute type. You see the respective interfaces with which the SAP system provides you. Note the key of the interface which you require.

You can also select:

By particular SAP application components

By particular events by entering intervals

Which interfaces are used in activated products

Which interfaces are used within a particular country version or within a particular industry

Which interfaces are used within a particular customer product

3. Enter the function module which you have developed yourself. To do this, choose either Goto -> Edit modules within the info system or Settings -> P/S modules or Process modules -> Customer's in the "SAP Business Framework" menu.

Make the following entries:

Key for the interface

The product that you want to use

Function module which belongs to this product.

You can also enter several function modules for a product.

Caution: The function module must be within your name range, that is must begin with the letter Z.

You leave the Ctr and Appl. fields blank unless you want a particular country version or a particular SAP industry-specific component to be enhanced or replaced instead of the standard process flow.

4. Fill the source text of your function module and activate it.

To do this, go again via Environment -> Info system (P/S) or Environment -> Info system (Processes) into the information system and execute the program. Then proceed as follows:

Click twice on the interface you have chosen. If you want, you can look at the interface at this point by choosing Goto -> Interface. Then choose the Back function again afterwards.

Place the cursor on the relevant line and choose Goto -> Function library. You see the sample function module delivered by SAP.

Copy the sample module delivered by SAP and call it the same as the function module entered in step 3.

Fill the source text of the empty function module.

Activate the function module.

Activate the product as described in step 1.

5. Run the R/3 program affected and test whether calling your function module works.

Please go through this link.

http://fuller.mit.edu/user_exits/business_transaction_event.htm

Reward Points if you find information useful.