BTE

It is an ebhancement technique which is not that popular

similar to customer enhancements

we are not going to change layout using BTE.

BTE is not embeded in the standard code.

in important critical transaction SAP will provide certain places where events will be called let say 1066, that would be called via

OPEN_FI_PERFORM
OUTBOUD_CALL_EVENT_NAME

or there would be a comment mentioned as open_FI_PERForm

these are the ways by which we can identify BTE’s.

Mostly for FI.

even in APO, CRM etc..

 

FB60 – validate invoices for the vendor
FBl5n — customer line item displany
fbl3n – gl account line item display

it basically goes and check whether function has been implemented under the event

FIBF – for BTE
go to setting -> products there will be 2 options

1) of a partner – who develops a product and sells the product the application for SAP
2) of a customer – who will customize it for the business

TBE01 — Library of the Publish&Subscribe Business Transaction Events

so identify your event first and then to transaction FIBF

goto settings-> products-> of a customer

create a new product

then save and come back

Again goto FIBF go to setting-P/s module->of a customer

for each event there will be a FM preexisting by the name

SAMPLE_INTERFACE_00001650

the last part consists of the event name and there will be different FM’s for each event so that you can see import and export process and decide on your coding process.

 

BERP — BTE process interfaces.., repository for BTE

so there is a program rfposxextend – to append structure of RFPOS and RFPOSX

update structure within the standard configuration