ODS Activation Problem (with SIDS) BIG PROBLEM !!!

Question

Hi
Ok we have a situation in our project but first a few facts: -
1: For ODS we do not use keys but have a infobject that creates a unique ID for each entry with a bit of ABAP in the update rule (yep not very good I know but too many to change now)
2: The SID table keeps growing so we have deleted it four or five times with SE14.
Now I am not sure if these are related to our problem as we have used SE14 before and it hasnt created prolems??
THE PROBLEM
Some of th ODS that use this unique Info Object (we will call this A1) that creates unique entries will not activate with SID creation. It doesn't give much information apart from whatever process A1 is it is returned with errors.
We get the following message
Process 000034 returned with errors (process 34 is the one that tries to get a SID for A1)
Message no. RSODSO_PROCESSING006
Activation of M records from DataStore object CA_TS1 terminated
We also geta  short dump every time too and that is copied below the line where it fails
Does anyone know of how i can reset the SID gerenration or anythign that may help
52           ID 'KEY'  FIELD 'BI0'                 
53           ID 'DATA' FIELD l_field.              
54                                                 
55                                                 
56   IF i_abend EQ rs_c_false.                     
57 *... Nachricht an den Message-Handler schicken  
58                                                 
59     DATA: l_type  TYPE smesg-msgty.             
60                                                 
61 *... S-Meldung wenn kein Handler initialisiert  
62     IF g_active IS INITIAL.                     
63       l_type = 'S'.                             
64     ELSE.                                       
65       l_type = 'W'.                             
66     ENDIF.                                      
67                                                 
68     CALL FUNCTION 'RRMS_MESSAGE_HANDLING'       
69       EXPORTING                                 
70         i_class  = 'BRAIN'                      
71         i_type   = l_type                       
72         i_number = '299'                        
73         i_msgv1  = i_program                    
74         i_msgv2  = i_text.                      
75   ELSE.                                         
76     DATA: l_text  TYPE string,                  
77           l_repid TYPE syrepid.                 
78                                                 
79     l_repid = i_program.                        
80     l_text  = i_text.                           
81                                                 
>>     RAISE EXCEPTION TYPE cx_rsr_x_message       
83           EXPORTING text = l_text               
84                  program = l_repid.             
85   ENDIF.                                        
86                                                 
87 ENDFUNCTION.

Answer 1

Yep right click and delete data then set up new initial etc with very small selection.
Reloaded and exact same error message.
when I check the /BI0/SBBP_OBGUID  table it only has one entry whilst the other infoobjects are getting filled in their SID tables so is there any way to sort of kick this table up the butt and reset it or something??
Your right about the P table so we can cross that out of the picture )
I do think it is somethign to do with the fact that we have used SE14 too many times and it hascaused in consistencies but if you have any ideas how to resync it or somethign it would be great
thanks