Scribd
Upload
62 views21 pages

Scenario On Business Transaction Events (Btes) : Zfibf

This document discusses using Business Transaction Events (BTEs) in SAP to trigger custom code when specific transactions occur. It provides steps to create a BTE that will add custom fields to a financial report when that report is run. The steps include creating a product to link an event to a custom function module, then linking the event and function module. The function module contains code to append fields to structures used in the report transaction.

Uploaded by

knani9090
Copyright
© © All Rights Reserved
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
62 views21 pages

Scenario On Business Transaction Events (Btes) : Zfibf

This document discusses using Business Transaction Events (BTEs) in SAP to trigger custom code when specific transactions occur. It provides steps to create a BTE that will add custom fields to a financial report when that report is run. The steps include creating a product to link an event to a custom function module, then linking the event and function module. The function module contains code to append fields to structures used in the report transaction.

Uploaded by

knani9090
Copyright
© © All Rights Reserved
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/ 21

ZFIBF

Scenario on Business Transaction Events (BTEs)


By Deepak K Manjunatha, IBM India
In this tutorial, we would focus on triggering a BTE whenever a vendor data is changed (Transaction FK02) Go to transaction FIBF or

IMG Menu Path: Financial Accounting !Financial Accounting Glo"al #ettings !Business $ransaction %&ents ! %n&iron'ent ! In(osyste' )Processes*+

Click on e ecute! "ook for the a##ro#riate event that fulfills our re$uire%ent!

&ou'le click on the corres#onding BTE! Click on the (a%#le Function %odule!

Co#) the interface into the custo% function %odule (*+)! The desired logic is coded in the custo% function %odule! The interface of the function %odule should never 'e changed!

Additional logic can "e coded in the (unction 'odule+ #a&e and acti&ate the (unction 'odule+

$he ne,t step is to create a Product that links the e&ent -ith the (unction 'odule+ Products are created in the sa'e transaction FIBF+

.lick on the /0e- %ntries1 "utton+

%nter the product na'e description and 2F. destination i( applica"le+ $he check "o, A is to acti&ate the product+

$he ne,t step is to link the (unction 'odule and the e&ent using the product created+ $he path is sho-n "elo-+

.lick ne- entries and enter the e&ent and the (unction 'odule+

$esting the B$%+ For our case go to transaction FK34, that changes the &endor data+

Make a s'all change in the e,isting &endor5s data+

6pon sa&e, the B$% associated -ith the e&ent -ill "e triggered+

,##l) a 'reak #oint in the function %odule associated with the event to check the triggering!

Adding custom fields to the FI report FBL5N using BTEs

E a%#le (cenario- .hen we run FB"/0, we need to have additional colu%ns (Custo% Fields) Billing 1lant and &escri#tion!

0ow for the a'ove re$uire%ent, we need to do following in FIBF tcode (BTE)!

2ive a 1roduct na%e

(elect the a##ro#riate event which gets triggered during the e ecution of the tcode FB"/0! ,gainst the Event assign the 1roduct na%e which was created a'ove and assign a function %odule na%e (the #rocedure to create the correct function %odule can 'e found at this link htt#-33www!sa#technical!co%3Tutorials34thers3BTE31age5!ht% )

In FB"/0, we need to have two additional colu%ns, Billing #lant and &escri#tion! For this we need to a##end a structure with two fields in 6F14( structure and 6F14(7 structure!

Then we need to e ecute a 6e#ort 6F14(7E7TE0&

(elect 8E(

Code written in the Function %odule is as follows

TE(T-

You might also like