Posted: Fri Oct 09, 2009 4:23 pm Post subject: Note 530655 - Performance improvements in BTE (OpenFI_1025)
Если коротко и по-русски, возвращает обмен данными в OpenFI_1025 через ABAP память, как это было до версии 4.7.
--------------------------------------------------------------------------------
Message Number : 0120050409 0000094659 2005 Installation : 6020047401
Short Text: FIBF - BTE - Business Transaction Events
Contact Person: Mr. Suporte Financeiro Country : BR
Phone Number: 005555(21)2534-5964 R/3 Release: 620
Customer Name: Infoglobo Comunicaзхes Ltda Database : ORACLE 9.2
Customer Number: 318441 Oper. System :
Product: SAP R/3 ENTERPRISE Product Vers.: 47X200
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Description
Transaction : FIBF Program : Screen :
Error Message .. ...
We are in process of upgrade (4.0b will be 4.7). There are some
functions configured in the FIBF (BTE - Business Transaction Events) had
been developed for us.
However after upgrade some are not change the BSEG.
Our development is referring the alterations in field BSEG-SGTXT for the
Historical description XX-CSC-BR to appear in the respective legal
reports.
We know of the existence of the SAP NOTES 108559.
Also we know of the existence of note 530655 (accesses to the memory of
the BTEs are ineffective).
We would not like to remake our development, we would like alternatives
command EXPORT/IMPORT that had been inhibited in BTE 00001025
(OPEN_FI_PERFORM_00001025_E).
Best regards.
Reinaldo Catharino
--------------------------------------------------------------------------------
Reply
15.02.2005 15:28:19 Paulo Evaristo
Reinaldo,
I have to see the problem in your system, please, provide the logon
data ( system, server, user, client and password) and data to simulate
the problem in your system.
Best regards,
Paulo Evaristo
Active Global Support - Financials
@E1@ [email protected]
--------------------------------------------------------------------------------
Info for SAP
16.02.2005 01:03:07 Suporte Financeiro
Prezado Paulo.
Conforme descrito no chamado, possuнamos algumas funзхes atreladas a
eventos (BTE - FIBF), estas funзхes tinham como objetivo a ediзгo de
histуricos padrхes. Com a implementaзгo da versгo 4.7, os eventos se
tornaram ineficientes para a atualizaзгo da BSEG, conforme nota SAP
530655.
Sabemos da orientaзгo da SAP quanto a histуricos padrхes (108559),
contudo, estamos em uma instalaзгo que possui IS-M, e possuнmos algumas
particularidades, por este motivo que se optou-se pela soluзгo de
eventos (BTE).
Meu telefone й (21) 2534-9706, cso queira posso estar ligando para vocк.
Desde jб, meus agradecimentos.
Reinaldo Catharino
--------------------------------------------------------------------------------
Reply
16.02.2005 23:56:33 Paulo Evaristo
Reinaldo,
Por favor, entre em contato comigo para que possamos discutir
o problema reportado, pois acredito que o problema estб na configuraзгo.
Hoje e amanhг eu estou no escritуrio do Rio de Janeiro e a partir de
sexta em Sгo Paulo.
Atenciosamente,
Paulo Evaristo
@F2@ Suporte Global - Finanзas
--------------------------------------------------------------------------------
Info for SAP
17.02.2005 02:46:41 Suporte Financeiro
Paulo,
Me informe os telefones.
Obrigado.
Reinaldo
--------------------------------------------------------------------------------
Internal Memo
18.02.2005 00:12:19 Paulo Evaristo
Hello Colleagues,
Could you please take care of this problem?
We dont't have localization for the component IS-M.
Thanks and regards
Paulo Evaristo
--------------------------------------------------------------------------------
Internal Memo
18.02.2005 01:18:25 Martin Schindel
Hallo Frank,
da hab ich jetzt nicht verstanden, was eigentlich das Problem ist.
Kennst Du Dich mit diesen BTE aus? Das klingt fьr mich nach FI.
GruЯ, Martin
--------------------------------------------------------------------------------
Reply
18.02.2005 12:52:34 Frank Werner
Dear Reinaldo,
how do you create the FI-Documents? Which transaction do you use, which
example data do you use?
Please provide logon data.
Is the problem related to IS-Media or FI?
Sincerely yours
@KR@ Frank Werner (SAP for Media Development Support)
--------------------------------------------------------------------------------
Info for SAP
18.02.2005 23:13:08 Suporte Financeiro
Hi Frank.
You don’t forget the note SAP 530655
therefore this note modified the events 00001025.
Transaction FIBF, event 00001025 and function Z_FI_INTERFACE_00001025.
For you simulate it will be able to use a simple transaction of FI. Use
the transaction FB60
you it will inform:
Vendor - 7000035
Invoice date - 18022005
Amount - 800,00
G/L acc - 11110101
Amount in doc - 800,00
This transaction is not IS/M but it will call the event.
ENDFUNCTION.
--------------------------------------------------------------------------------
Internal Memo
21.02.2005 13:22:20 Frank Werner
Hi Colleagues,
this is more or less a consulting request. What should customer do
instead of following coding line after implementation of note 530655:
EXPORT T_BSEG TO MEMORY ID 'OPENFI00001025E'.
Regards
Frank
--------------------------------------------------------------------------------
Info for SAP
23.02.2005 02:00:55 Suporte Financeiro
Hi Frank.
This problem is of FI.
The INFOGLOBO had in 4.0b a development based on the events (BTE - FIBF)
It isn't possible to change this development for user-exit with
substitution rule (GGB4) as guided in the note 108559.
This development also atends of all the integrations with FI including
IS-M.
best regards.
Reinaldo Catharino.
--------------------------------------------------------------------------------
Internal Memo
25.02.2005 23:48:55 Dieter Gietl
message 181289/2004
Dear Reinaldo Catharino,
the changes of note 530655 in function module
OPEN_FI_PERFORM_00001025_E are a performance improvement and thus
should not be removed from the standard.
Please note that Publish&Subscribe-BTE 00001025 is not intended
to change any field contents, but only to check data (-> validation).
I can offer you the following coding modification with which
the old behavior of function module OPEN_FI_PERFORM_00001025_E
is restored. Please note that this coding modification is not
contained in the standard so that it might have to be reimplemented
after the implementation of support packages or upgrades.
-> transaction SE37 -> function module OPEN_FI_PERFORM_00001025_E
<<<<<<<<<<<<<<<<<<<<<< begin of context block >>>>>>>>>>>>>>>>>>>>>>>>>
*" IMPORTING
*" VALUE(I_BKDF) LIKE BKDF STRUCTURE BKDF OPTIONAL
*" TABLES
*" T_AUSZ1 STRUCTURE AUSZ1 OPTIONAL
*" T_AUSZ2 STRUCTURE AUSZ2 OPTIONAL
*" T_AUSZ3 STRUCTURE AUSZ_CLR OPTIONAL
*" T_BKP1 STRUCTURE BKP1
*" T_BKPF STRUCTURE BKPF
*" T_BSEC STRUCTURE BSEC
*" T_BSED STRUCTURE BSED
*" T_BSEG STRUCTURE BSEG
*" T_BSET STRUCTURE BSET
*" T_BSEU STRUCTURE BSEU OPTIONAL
*"----------------------------------------------------------------------
<<<<<<<<<<<<<<<<<<<<<<< end of context block >>>>>>>>>>>>>>>>>>>>>>>>>>
<<<<<<<<<<<<<<<<<<<<<<<< start of deletion >>>>>>>>>>>>>>>>>>>>>>>>>>>>
DATA: L_AUSZ1 TYPE TABLE OF AUSZ1, "start:note530655
L_AUSZ2 TYPE TABLE OF AUSZ2,
L_AUSZ3 TYPE TABLE OF AUSZ_CLR,
L_BKPF TYPE TABLE OF BKPF,
L_BKP1 TYPE TABLE OF BKP1,
L_BSEC TYPE TABLE OF BSEC,
L_BSED TYPE TABLE OF BSED,
L_BSEG TYPE TABLE OF BSEG,
L_BSET TYPE TABLE OF BSET,
L_BSEU TYPE TABLE OF BSEU. "end:note530655
<<<<<<<<<<<<<<<<<<<<<<<<< end of deletion >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<<<<<<<<<<<<<<<<<<<<<<< start of insertion >>>>>>>>>>>>>>>>>>>>>>>>>>>>
* DATA: L_AUSZ1 TYPE TABLE OF AUSZ1, "start:note530655
* L_AUSZ2 TYPE TABLE OF AUSZ2,
* L_AUSZ3 TYPE TABLE OF AUSZ_CLR,
* L_BKPF TYPE TABLE OF BKPF,
* L_BKP1 TYPE TABLE OF BKP1,
* L_BSEC TYPE TABLE OF BSEC,
* L_BSED TYPE TABLE OF BSED,
* L_BSEG TYPE TABLE OF BSEG,
* L_BSET TYPE TABLE OF BSET,
* L_BSEU TYPE TABLE OF BSEU. "end:note530655
<<<<<<<<<<<<<<<<<<<<<<<< end of insertion >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<<<<<<<<<<<<<<<<<<<<<< begin of context block >>>>>>>>>>>>>>>>>>>>>>>>>
CALL FUNCTION 'BF_FUNCTIONS_FIND'
EXPORTING
I_EVENT = '00001025'
TABLES
T_FMRFC = FMTAB
EXCEPTIONS
NOTHING_FOUND = 4
OTHERS = 8.
CHECK SY-SUBRC = 0.
Dieter Gietl
Development Financials
SAP AG
--------------------------------------------------------------------------------
Internal Memo
02.03.2005 13:51:41 Gisela Siefert
mail fwd to processor.
--------------------------------------------------------------------------------
Reply
02.03.2005 14:44:26 Dieter Gietl
Dear Reinaldo Catharino,
the changes of note 530655 in function module
OPEN_FI_PERFORM_00001025_E are a performance improvement and thus
should not be removed from the standard.
Please note that Publish&Subscribe-BTE 00001025 is not intended
to change any field contents, but only to check data (-> validation).
I can offer you the following coding modification with which
the old behavior of function module OPEN_FI_PERFORM_00001025_E
is restored. Please note that this coding modification is not
contained in the standard so that it might have to be reimplemented
after the implementation of support packages or upgrades.
-> transaction SE37 -> function module OPEN_FI_PERFORM_00001025_E
<<<<<<<<<<<<<<<<<<<<<< begin of context block >>>>>>>>>>>>>>>>>>>>>>>>>
*" IMPORTING
*" VALUE(I_BKDF) LIKE BKDF STRUCTURE BKDF OPTIONAL
*" TABLES
*" T_AUSZ1 STRUCTURE AUSZ1 OPTIONAL
*" T_AUSZ2 STRUCTURE AUSZ2 OPTIONAL
*" T_AUSZ3 STRUCTURE AUSZ_CLR OPTIONAL
*" T_BKP1 STRUCTURE BKP1
*" T_BKPF STRUCTURE BKPF
*" T_BSEC STRUCTURE BSEC
*" T_BSED STRUCTURE BSED
*" T_BSEG STRUCTURE BSEG
*" T_BSET STRUCTURE BSET
*" T_BSEU STRUCTURE BSEU OPTIONAL
*"---------------------------------------------------------------------
<<<<<<<<<<<<<<<<<<<<<<< end of context block >>>>>>>>>>>>>>>>>>>>>>>>>>
<<<<<<<<<<<<<<<<<<<<<<<< start of deletion >>>>>>>>>>>>>>>>>>>>>>>>>>>>
DATA: L_AUSZ1 TYPE TABLE OF AUSZ1, "start:note530655
L_AUSZ2 TYPE TABLE OF AUSZ2,
L_AUSZ3 TYPE TABLE OF AUSZ_CLR,
L_BKPF TYPE TABLE OF BKPF,
L_BKP1 TYPE TABLE OF BKP1,
L_BSEC TYPE TABLE OF BSEC,
L_BSED TYPE TABLE OF BSED,
L_BSEG TYPE TABLE OF BSEG,
L_BSET TYPE TABLE OF BSET,
L_BSEU TYPE TABLE OF BSEU. "end:note530655
<<<<<<<<<<<<<<<<<<<<<<<<< end of deletion >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<<<<<<<<<<<<<<<<<<<<<<< start of insertion >>>>>>>>>>>>>>>>>>>>>>>>>>>>
* DATA: L_AUSZ1 TYPE TABLE OF AUSZ1, "start:note530655
* L_AUSZ2 TYPE TABLE OF AUSZ2,
* L_AUSZ3 TYPE TABLE OF AUSZ_CLR,
* L_BKPF TYPE TABLE OF BKPF,
* L_BKP1 TYPE TABLE OF BKP1,
* L_BSEC TYPE TABLE OF BSEC,
* L_BSED TYPE TABLE OF BSED,
* L_BSEG TYPE TABLE OF BSEG,
* L_BSET TYPE TABLE OF BSET,
* L_BSEU TYPE TABLE OF BSEU. "end:note530655
<<<<<<<<<<<<<<<<<<<<<<<< end of insertion >>>>>>>>>>>>>>>>>>>>>>>>>>>>>
<<<<<<<<<<<<<<<<<<<<<< begin of context block >>>>>>>>>>>>>>>>>>>>>>>>>
CALL FUNCTION 'BF_FUNCTIONS_FIND'
EXPORTING
I_EVENT = '00001025'
TABLES
T_FMRFC = FMTAB
EXCEPTIONS
NOTHING_FOUND = 4
OTHERS = 8.
CHECK SY-SUBRC = 0.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
All product names are trademarks of their respective companies. SAPNET.RU websites are in no way affiliated with SAP AG. SAP, SAP R/3, R/3 software, mySAP, ABAP, BAPI, xApps, SAP NetWeaver and any other are registered trademarks of SAP AG. Every effort is made to ensure content integrity. Use information on this site at your own risk.