cancel
Showing results for 
Search instead for 
Did you mean: 

Error when assigning SID: Action VAL_SID_CONVERT InfoObject 0BP_ACTIVIT

nikhil527
Discoverer
0 Kudos

Hello Team,

WE are facing the error"Error when assigning SID: Action VAL_SID_CONVERT InfoObject 0BP_ACTIVIT" .Please see he below screen shot.

Every day the failure is for a different value and this is fixed with the manual activation of he DSO, with out any change .

Below are the steps we have tried:

1. The RSRV tests for the info objects were consistant. We have done he below rsrv tests:

a. Compare characterstic of P/Q table with X/Y tables.

b.SID values in X and Y tables.

2. We have changed the DSO setting  from Parallel to Serialized Activation.

Also the format of the values are as per the designated type.

One more thing which i noticed is , the values for which the failure occurs , are new entries to the DSO, and they do no exists in the Change log table.

Please let us know , what else can be done to fix this issue.

Thanks in Advance,

Nikhil

Accepted Solutions (0)

Answers (3)

Answers (3)

colm_boyle
Employee
Employee
0 Kudos

Hi Nikhil,

please do an 'xSearch' for all notes using the search criteria VAL_SID_CONVERT, you will find endless documentation on this issue and will undoubtedly find the solution. Focus your analysis on the notes in the component areas BW-BEW-OT* and BW-WHM-DBA-ODS.

I believe these notes will reveal the solution,

Thanks,


Colm

Former Member
0 Kudos

HI Nikhil,

please go through the documents.

http://scn.sap.com/thread/1820047

http://scn.sap.com/message/14266151

http://scn.sap.com/thread/1520825

Regards,

Abdul rAwoof Syed.

shalaka_golde
Participant
0 Kudos

Hi,

0BP_ACTIVIT refers to characteristic 0BPARTNER that is it uses its master data tables.So pls check whether there are any invalid characteristic values coming for 0BPARTNER.

Regards,

Shalaka

nikhil527
Discoverer
0 Kudos

Hi Shalaka,

Thanks for reply.

Characteristic values are correct. There is no problem with Hex values.

I am resolving it by manual activation on daily basis.

If it is Invalid characteristic value, then manual activation shouldn't work.

I have also checked consistency of 0BPARTNER for all tables and it works fine.

I found 2 infoobjects 0CRM_PROSPE and 0BP_ACTIVIT in DSO,which refers to 0BPARTNER.

Are they conflicting each other while SID determination?

Because DSO activation always failed for only one of them.

Regards,

Nikhil