BTE

Former Member — Thu, 16 Nov 2006 22:07:38 GMT

Hi all

can anybody please explain in brief abt BTE..

Thanks and regards

vijaya

Re: BTE

Former Member — Thu, 16 Nov 2006 22:25:44 GMT

Hi,

Check this link..Very good example..

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

Thanks,

Naren

Re: BTE

Former Member — Fri, 17 Nov 2006 09:44:10 GMT

Hi naren

The file got corrupted itseems...iam not able to open it.canu resend that please...

Thanka

vijaya

Re: BTE

Former Member — Fri, 17 Nov 2006 10:10:13 GMT

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 &#56256;&#56510; 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

I hope it helps.

Best Regards,

Vibha

*Please mark all the helpful answers

topic Re: BTE in Application Development and Automation Discussions

BTE

Re: BTE

Re: BTE

Re: BTE