2006 Aug 22 5:21 PM
After upgrade to ER2005 program RFBIKR00 stops processing when it calls this function module DDIF_NAMETAB_GET with include name SI_AND_CI_BLFB1. Then this function module returns 3 lines in table lt_x031l and program stops on error.
In old version of SAP 46C, the result was 1 entry in lt_x031l and program was executed correctly.
Did anyone experienced the same problem?
Code in RFBIKR00:
form addon_check_include using value(i_xale) type c
value(i_koart) type koart
value(i_strukturname) type strukname.
data: l_includename type strukname,
lt_x031l type x031l occurs 10,
l_count type i,
sysubrc type sysubrc.
concatenate 'SI_AND_CI_' i_strukturname into l_includename.
call function 'DDIF_NAMETAB_GET'
exporting
tabname = l_includename
all_types = 'X'
lfieldname = 'SENDE'
tables
x031l_tab = lt_x031l
exceptions
not_found = 1
others = 2.
sysubrc = sy-subrc.
if sysubrc = 0.
describe table lt_x031l lines l_count.
if l_count = 1.
Es gibt nur das Standard-Feld SENDE ==> Es ist ok, also fertig
exit.
endif.
endif.
Fehler ist aufgetreten (im Falle sysubrc = 0 ist l_count > 1, d.h.
es gibt mindestens ein ADD_ON-Feld, wodurch alte BI-Daten nicht mehr
verarbeitet werden können) ==> Meldung und Abbruch
if i_xale = space.
case sysubrc.
when 0. perform log_msg using c_msgid 'I' '643'
i_strukturname '' '' ''.
when 1. perform log_msg using c_msgid 'I' '642'
l_includename '' '' ''.
when 2. perform log_msg using c_msgid 'I' '641' '' '' '' ''.
endcase.
case i_koart.
when 'D'. perform dump_bkn00(rfbide00).
when 'K'. perform dump_blf00(rfbikr00).
endcase.
perform log_abort using c_msgid '013'.
else. " i.e. i_xale = 'X'
case sysubrc.
when 0. message i643 with i_strukturname raising internal_error.
when 1. message i642 with l_includename raising internal_error.
when 2. message i641 raising internal_error.
endcase.
endif. " i_xale = space
endform. " addon_check_include
After upgrade to ER2005 program RFBIKR00 stops processing when it calls this function module DDIF_NAMETAB_GET with include name SI_AND_CI_BLFB1. Then this function module returns 3 lines in table lt_x031l and program stops on error.
In old version of SAP 46C, the result was 1 entry in lt_x031l and program was executed correctly.
Did anyone experienced the same problem?
Code in RFBIKR00:
form addon_check_include using value(i_xale) type c
value(i_koart) type koart
value(i_strukturname) type strukname.
data: l_includename type strukname,
lt_x031l type x031l occurs 10,
l_count type i,
sysubrc type sysubrc.
concatenate 'SI_AND_CI_' i_strukturname into l_includename.
call function 'DDIF_NAMETAB_GET'
exporting
tabname = l_includename
all_types = 'X'
lfieldname = 'SENDE'
tables
x031l_tab = lt_x031l
exceptions
not_found = 1
others = 2.
sysubrc = sy-subrc.
if sysubrc = 0.
describe table lt_x031l lines l_count.
if l_count = 1.
Es gibt nur das Standard-Feld SENDE ==> Es ist ok, also fertig
exit.
endif.
endif.
Fehler ist aufgetreten (im Falle sysubrc = 0 ist l_count > 1, d.h.
es gibt mindestens ein ADD_ON-Feld, wodurch alte BI-Daten nicht mehr
verarbeitet werden können) ==> Meldung und Abbruch
if i_xale = space.
case sysubrc.
when 0. perform log_msg using c_msgid 'I' '643'
i_strukturname '' '' ''.
when 1. perform log_msg using c_msgid 'I' '642'
l_includename '' '' ''.
when 2. perform log_msg using c_msgid 'I' '641' '' '' '' ''.
endcase.
case i_koart.
when 'D'. perform dump_bkn00(rfbide00).
when 'K'. perform dump_blf00(rfbikr00).
endcase.
perform log_abort using c_msgid '013'.
else. " i.e. i_xale = 'X'
case sysubrc.
when 0. message i643 with i_strukturname raising internal_error.
when 1. message i642 with l_includename raising internal_error.
when 2. message i641 raising internal_error.
endcase.
endif. " i_xale = space
endform. " addon_check_include
2006 Aug 22 5:23 PM
2006 Aug 22 7:03 PM
2006 Aug 22 7:18 PM
Well, the point is, we can't really help with SAP code. If we find the problem, what will you do? Change the SAP standard program.
If there aren't any OSS notes, then your best bet is to raise an OSS message.
Rob
2006 Aug 22 7:23 PM
2006 Aug 22 7:25 PM
There is a point.
It might be some customizing or some SAP setting that somebody had to do to fix this problem.
2006 Aug 22 8:37 PM
If the program were changed so that customizing is necessary, I would expect that to be documented - either in the program documentation or a note.
In any event, I think you should raise an OSS message.
Rob
2006 Oct 04 12:39 PM
Hi,
did anybody find a solution?
I'm experiencing the same problem in our ECC 600 System.
Regards,
Andreas Gieres
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |