status_text_edit parameters imported incorrectly

I’m having some trouble trying to call SAP function status_text_edit from an R3 dataflow, and wondered if anybody has hit this before.

When I import the function module under my R3 datastore, it looks strange.

Looking at the function through se37 in SAP there are 6 import parameters;

CLIENT
FLG_USER_STAT
OBJNR
ONLY_ACTIVE
SPRAS
BYPASS_BUFFER

3 of the import parameters look sensible when they are imported.

However, 3 of the parameters look very strange. For example BYPASS_BUFFER is there 33 times in the format :BYPASS_BUFFER:MANDT

Looking closer at the function module, the 3 parameters that are causing the problem have a typing of ‘TYPE’, whereas the ones that are imported correctly are ‘LIKE’.

Does anybody know why this happens, and if there is any way to avoid it?


dcstevenson (BOB member since 2006-09-06)

I’m surprised nobody has hit this problem before, as it seems like a major weakness in SDS.

There are a lot of function modules in SAP that use typing of ‘TYPE’ rather than ‘LIKE’.

It would seem like a fairly major problem if SDS couldn’t import the metadata for these function modules correctly.

No workarounds for this? (other than creating a version of the function that uses ‘LIKE’)


dcstevenson (BOB member since 2006-09-06)

SAP support came back with an answer on this one.

They gave us a new version of the function module that is used to import SAP metadata into SDS.

When we import function modules now it all looks ok, regardless of the typing of the parameters.

So there is a fix out there for this if anybody is having the same problem on v3.2


dcstevenson (BOB member since 2006-09-06)