Advanced DSO - List of permitted data types for key fields?

[Sandra_Rossi]

That's probably a basic question about BW DSO which comes after a BW developer contacted me to know the corresponding CHAR length for RAW 16 (which is CHAR 32, I guess). I think it's a BW system with ABAP 7.50, but I can't tell more as I don't have access.

This DSO should store the data from a custom table from a SAP ECC system, whose primary key is a RAW 16 GUID.

I also ask it because I don't find much information in the forum, in SAP Library and in SAP notes.

If trying to define a RAW key field, there is this error:

• Element not allowed in key
• Data type RAW is not allowed for key elements.
• Adjust the key definition before changing the data type.

Is there any documentation about the key field restrictions?

Which data types are permitted?

Do you know the reason of the limitation?

Any general recommendation for storing a RAW 16 ?

Thanks for reading me.

Sandra

NB: as you can see, I don't know much of BW and I don't have access to the BW system, so I'm sorry in advance as I probably won't be able to give you more details.

[Abhishek_Hazra]

Hi sandra.rossi,

Yes there is a limitation on datatypes permitted for key definition in aDSO. Please have a look into the following SAP help page : https://help.sap.com/docs/SAP_BW4HANA/107a6e8a38b74ede94c833ca3b7b6f51/eda398dc0f6d49ff9acef7a272467....

If possible, try staging the data into a field of type varchar, or convert the RAW16 field to char in a transformation before loading to the aDSO (https://answers.sap.com/questions/4915675/function-module-to-convert-raw-type-to-char-data-t.html).
Hope this helps.

Best Regards,
Abhi

[ferdtulu]

Hi Sandra,

you should convert the characteristic from RAW to CHAR. In this way, you should use a field routine via a function module.

FB = RS_SCRP_FIELDS_RAW_TO_CHAR

Regards

[Sandra_Rossi]

Thanks for confirming, it's what I said to the BW developer ("... contacted me to know the corresponding CHAR length for RAW 16 (which is CHAR 32, I guess) ...") No need to overengineer, just do:

char32 = hex16.