Error when assigning SID: Action VAL_SID_CONVERT , InfoObject 0REF_KEY3

[Former Member]

Greetings Gurus,

yesterday i noticed this error:

"Error when assigning SID: Action VAL_SID_CONVERT , InfoObject 0REF_KEY3

Value 'Più doc.2013-2014 ' (hex. '0050006900F900200064006F0063002E003200300031003300') of characteri "

I understood that there are some characters not supported by BW so i did this:

1. delete the request from DSO.

2. PSA and edit error records.

3. save the data in the PSA.

4. load the data again and activate the DSO.

Unfortunatly, after reactivating the DSO, i'm  experiencing again the same error in the same request:

"Error when assigning SID: Action VAL_SID_CONVERT , InfoObject 0REF_KEY3

Value 'Più doc.2013-2014 ' (hex. '0050006900F900200064006F0063002E003200300031003300') of characteri "

I checked again the PSA but this time 0REF_KEY3 is correct, it hasn't the wrong char, so i can't understand how to solve this issue since i 've already edited the PSA.

Anyone has any idea on  how i could solve this ISSUE?

Thanks for your time

Elena

[RamanKorrapati]

Hi,

What value you edited at PSA?

Have you observed your error, it shows there is a empty sapce after 2013-2014.

Delete that empty space and save the record.

later relaod them into target.

Even there is two umlauts on iu. is those two are allowed into your bw server?

Thanks

[Former Member]

Hi,

thank you for your answer.

To avoid any inconvenience i erased the value 'Più doc.2013-2014 ' in PSA in InfoObject 0REF_KEY3.

After doing this i loaded the data again and activated the DSO, but incredibly the activation returns again the same error:

"Error when assigning SID: Action VAL_SID_CONVERT , InfoObject 0REF_KEY3

Value 'Più doc.2013-2014 ' (hex. '0050006900F900200064006F0063002E003200300031003300') of characteri "

Sincerly i can't understand why.

Thanks for your time,

Elena

[RamanKorrapati]

Hi,

at your transformations which field is mapped to 0REF_KEY3.

For example: you may mapped field XYZ to 0ref_key.

So at PSA you need to find XYZ value as 'Più doc.2013-2014 ', edit empty space and umlauts.

save and reload from psa to dso.

Thanks

[former_member182997]

Is your reporting on cube or DSO???

if reporting is on Cube, turn off SID generation on DSO.
This will prevent the error at least during activation. But then DTP from DSO to Cube will give error for the same characteristic and you will be able to correct few records in error stack and update in Cube.
That can be another way for this issue apart from what expert has suggested.

But most importantly  one should ensure that source data is okay.
Master data problem almost always takes place in the source side.
But if you need to allow the same characteristic to be displayed in report as you are receiving from source i think only choice is field routine for the characteristic as a permanent fix.