Different Displays of char field in se37 output versus debugger on a unicode system

[former_member184385]

Hallo Apab Gurus,

calling a standard bapi (bapi_alm_order_get_detail) on an ecc 6.00 unicode system (and hdb) I'm, experiencing different display results of the field header_es-funct_loc, in the 1st place displayed in debugger, in the 2nd place displayed on the s37 result page (after the bapi returns). Below you can find the pics for illustration.

in debugger the funct_loc field is 20 chars long (incorrect)

on the s37 result output funct_loc is 10 chars long (correct, the expected value)

Could someone make sense of it?

Btw. I get the 'wrong' result for the mentioned bapi, calling it from another program. Displaying the whole structure there (using cl_demo_output, and transforming the structure into xml using id transformation beforehand) also displays funct_loc as a 20 chrs long string?

Thanks in advance for your help.

Best regards, Gregor

[Sandra_Rossi]

I see 30 characters (with 10 blanks), not 20.

[Sandra_Rossi]

internal length = 30 characters

output length = 10 characters

It's called conversion exit or conversion routine, defined at the domain level.

[former_member184385]

Hello Sandra,

thanks you very much for the hint regarding the conversion routines!

I found the conversion fm conversion_exit_tplnr_output and could verify, that its called during the processing of fm bapi_alm_order_get_detail, when called from se37

Best regards, Gregor

[manfred_reinart]

Hello Gregor,

as Sandra already depicted this is result of execution of the CONVERSION_EXIT_TPLNR_OUTPUT and the fact that you are using so-called 'alternative labelling'.

With this functional locations habe an internal representation starting with '?' and one or more external 'labels'.

Best regards

M.

[Ulrich_Schmidt]

For a description of several "peculiarities" of SE37 compared to "normal execution" of a function module (especially when it's executed remotely via RFC) see also SAP note 206068. (It also mentions conversion exists for IMPORTING as well as EXPORTING parameters.)