Question Re: Error when assigning SID: Action VAL_SID_CONVERT , InfoObject 0REF_KEY3 in Technology Q&A

Error when assigning SID: Action VAL_SID_CONVERT , InfoObject 0REF_KEY3

Former Member — Fri, 09 Jan 2015 11:14:08 GMT

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

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

RamanKorrapati — Fri, 09 Jan 2015 11:28:23 GMT

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

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

Former Member — Fri, 09 Jan 2015 11:42:42 GMT

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

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

RamanKorrapati — Fri, 09 Jan 2015 11:48:46 GMT

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

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

Former Member — Fri, 09 Jan 2015 12:43:56 GMT

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.

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

Former Member — Fri, 09 Jan 2015 17:16:40 GMT

HI,

thanks for your answers.

we are reporting in DSO.

I modified Value 0REF_KEY3 'Più doc.2013-2014 ' as shown in the below picture, i edited the data in PSA as you said, as you can see:

After doing this i saved the data in PSA and i loaded the data again and activate the DSO.

Now i would expect a corret activation but i still have the same error:

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

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

Thanks to all

Elena

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

ccc_ccc — Fri, 09 Jan 2015 17:27:22 GMT

Hi Elena,

I guess there are more records with same value "Più doc.2013-2014" do one thing, in PSA find which field this data is coming and filter with "P" and all data and edit correct it and reload.

The ultimate goal is, take care all Più doc.2013-2014 .

Thank you,

Nanda

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

Former Member — Fri, 09 Jan 2015 17:57:24 GMT

HI Nanda,

thanks for you answer.

I used the filter *P* in key reference 3:

as you can see the value "Più doc.2013-2014 " is no more in PSA, but i still get the error:

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

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

This could be a BUG in the standard?

thanks,

Elena

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

ccc_ccc — Fri, 09 Jan 2015 18:32:35 GMT

Hi Elena,

Take PSA table name and got SE16 and filter as you did in PSA maintenance and lick on number entries,

I guess definitely there are more records with same value.

This wont be bug because its related data , not related any functionality.

Thank you,

Nanda

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

ccc_ccc — Fri, 09 Jan 2015 19:19:00 GMT

Hi Elena,

In above screenshot its showing SID generation for 0REF_KEY3 completed, may be same values other infobjects like 0REF_KEY2 , 0REF_KEY1 or any other .

so, please check all columns and find relevant and change.

Thank you,

Nanda

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

Former Member — Sat, 10 Jan 2015 12:34:41 GMT

Hi Nanda,

thanks to your advices i 've solved the problem.

thanks very much

Elena

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

former_member777600 — Wed, 17 Nov 2021 08:56:11 GMT

I had a similar problem. The main problem is that there are both lowercase and uppercase characters in the value. For successful activation, you must enable "Case-Sensitive" parameter for your InfoObject.