Skip to Content
0
Aug 03, 2023 at 08:51 AM

BAPI_USER_GET_DETAIL and BAPI_USER_CHANGE truncate issue of the user PARAMETERS values

139 Views

Hello,

We have identified issue while using SAP BAPI_USER_GET_DETAIL and BAPI_USER_CHANGE

We use standard app TCODE FKKBIXBIT_MON. User can create in the FKKBIXBIT_MON custom variant via personalization. Then the FKKBIXBIT_MON stores selection variant id as parameter into USR05 table as follows, process supplied by SAP .

Once Parameter is stored into DB USR05 the Parameter value is follows CREDIT_CARD_NUMBER0910 NOTE THE VALUE IS 18 Spaces long !!!

ISSUE is we use standard SAP BAPI_USER_GET_DETAIL to get user parameters . Once we read the user parameters these are then updated via BAPI_USER_CHANGE.

Both BAPIs do have the TABLES “parameter” values assigned into type BAPIPARAM . BAPIPARAM type is using for parameter values PARVA column and this is currently limited only into XUVALUE18 !!

Once we read user parameters via BAPI_USER_GET_DETAIL and then we send these parameters into BAPI_USER_CHANGE without any change . These parameters are been truncated !!!

User is then not able to use FKKBIXBIT_MON transaction. Because the variant ID due the transamination is corrupted

BAPI TABLE param PARAMETERS TYPING:

Once we look at the type referenced into „PARAMATER“

It contains column PARVA with length 18.


------------------------------------------------------------------------------------------------------------------------------------------------
Learn more about the SAP Support user and program here.