0% found this document useful (0 votes)
45 views4 pagesConfiguring BTE 1650 in SAP FI Module
The document describes the steps to modify the fields in the FAGLL03 transaction to display the information of the counterpart account. These steps include 1) creating and implementing a BAdI extension for FAGL_ITEMS_CH_DATA, 2) adding ABAP code to retrieve the data of the counterpart account and account type, and 3) activating the BAdI implementation.
Translated by
ScribdTranslationsCopyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
45 views4 pagesConfiguring BTE 1650 in SAP FI Module
The document describes the steps to modify the fields in the FAGLL03 transaction to display the information of the counterpart account. These steps include 1) creating and implementing a BAdI extension for FAGL_ITEMS_CH_DATA, 2) adding ABAP code to retrieve the data of the counterpart account and account type, and 3) activating the BAdI implementation.
Translated by
ScribdTranslationsCopyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
BTE
1) Extend the RPFOS and RFPOSX structures SE11
2) Run the programs RFPOSXEXTEND and BALVBUFDEL
3) Write the code to complete the extra fields in the BTE 1650
There is more data in the sdn:
Unable to access the content from the provided URL.
General Information BTE
BTE's - Business Transaction Events
The BTE's (Business Transactions Events, or business transaction events)
they are a type of extension for the FI module of SAP. Just like for SD, there are User-
Exits from the CMOD transaction, SAP created BTE's to adapt the FI module of
SAP system for all clients who require it
The BTEs are based on the following principles: application designers must
define the interface in a function module; an assignment table is read in
generated code and user modules are called dynamically.
The concepts of BADIs and BTEs are similar in some aspects, but they
they differentiate at different points:
BTEs can only be used to extend the standard SAP code; it is not
It is possible to extend interfaces like with the BADI's.
It is assumed that in the BTEs there are only 3 levels: SAP, Partners, and Clients, at
opposite of BADI's that support multiple layers.
In BTEs, functions are used to extend the SAP code; in BADIs, they are used.
ABAP Objects.
There are 2 types of interfaces:
Publication and Subscription Interfaces
Process Interfaces
Publication and Subscription Interfaces
These interfaces report on particular events (for example, a document
entered) in the standard SAP application and make the created data accessible for the
external software. The external software does not return any results to the standard of
SAP. Examples of these interfaces are:
Creation, modification, or blocking of a Master Record
A document was created, modified, or annulled
Items were deleted or reset
Additional processing can be generated in the additional component based on the foundations.
from the following data and events:
Start a Workflow
Generation or modification of additional data
Request for correspondence
Process Interfaces
They are used to send business processes to a different control that cannot be
performed from the standard processing; that is, the process interfaces
replace the standard SAP interfaces.
At this point, the determination of individual fields or can be structured.
specific reactions to flow processes individually. It is possible to connect different
different developments external to the standard SAP system. Generally the
External developments are carried out using the ABAP Workbench.
Basic steps to configure BTE's
First, you must ensure that the application is active for BTE's
Identify the BTE
Copy the example code into a Z module
Write the new ABAP code in module Z
Record and activate the function module
Assign the functions module to the event, country, and application
Optimal Way to Identify BTE.
A very practical way is by putting a break-point in the following modules of
functions and then execute the business process, with the break-point it will stop at
each BTE that jumps in the process.
PC_FUNCTION_FIND
BF_FUNCTIONS_FIND
Greetings.
You know.
FICO Moderator
Steps:
1. Enter transaction FIBF.
2. You go to the Environment / System Info (P/S) option. This option will show you a
selection screen, press F8 on it.
3. All events are shown to you, select the one you want to use and press the button
Module Type Functions.
4. An example of the function module for the selected event is shown to you, within
from it you will find the data, tables, and structures that you can use when the event
It will be shot. The only thing you need to do is copy the sample module by creating the
yours and within it place your program logic.
5. You return to the tcode FIBF and go to the menu Options / Products / ..a customer... Here
you create the product that you will associate with the event, for this you create an entry
Zeta
Most importantly, check the active checkbox.
6. Finally, you return to transaction code FIBF and go to the Modules P/S menu / ..a client and in
you create a new entry pointing out the event you want to use, the created product and
your function module.
Modification of fields FGALL03
Note 1034354 - FAGLL03: Display of offsetting account
information
Header
Version / Date 1 / 2007-03-12
Header
Priority Recommendations/additional info
Category Consulting
Primary Component FI-GL-GL-D Reporting/Analysis/Display
Secondary Components
Summary
Symptom
You want to display the offsetting account information in the line item display for the new general ledger.
(FAGLL03).
Other terms
FAGLL03
Reason and Prerequisites
This is for a customer inquiry.
Solution
To ensure the offsetting account information is available, you must create and activate an implementation.
for the 'FAGL_ITEMS_CH_DATA' BAdI. To do so, proceed as follows:
Call transaction SE19.
Enter for example, the name 'Z_FAGL_ITEMS_CH_DATA' and choose 'Create'.
As the Definition name select 'FAGL_ITEMS_CH_DATA'.
Create the BAdI implementation.
On the 'Interface' tab select the 'CHANGE_ITEMS' method.
The following source code should be defined in the method:
DATA: wa_items TYPE faglposx.
Loop through ct_items into wa_items.
CALL FUNCTION 'GET_GKONT'
EXPORTING
belnr = wa_items-belnr
company code
= wa_items-bukrs
buzei wa_items-buzei
year wa_items-fiscal_year
gknkz 3
IMPORTING
gkont wa_items-gkont
art = wa_items-gkart
EXCEPTIONS
belnr_not_found = 1
buzei_not_found = 2
gknkz_not_found = 3
OTHERS = 4.
IF sy-subrc = 0.
MODIFY ct_items FROM wa_items.
ENDIF.
ENDLOOP.
Summary
Activate the method and the BAdI implementation.
After you carry out these steps, the 'Offsetting account' (GKONT) and the 'Offsetting account type' (GKART)
fields are available in the field catalog of FAGLL03 and you can use them for display.
Affected Releases
Software Component Release From Release To Release And subsequent
SAP_APPLICATION 500 500 500
SAP_APPL 600 600 600
SAP_APPLICATION 602 602 602
SAP_APPL 603 603 603
SAP Application 604 604 604
SAP_APPLICATION 605 605 605
SAP_APPLICATION 606 606 606 X
Related Notes