ODS Activation Problem - Error getting SID

[Former Member]

Hi!

I was trying to activate an ODS but, the process keeps on cancelling. When I look at the log, it states the following:

1) Job started

2) Step 001 started (program RSODSACT1, variant &0000000000149, user ID XXXX)

3) Activation is running: Data Target <ODS name>, from 3,136 to 3,136

4) Data to be activated successfully checked against archiving objects

5) Error getting SID for ODS object <ODS name>

6) Activation of data records from ODS object <ODS name> terminated.

7) ...

I've done the following:

1) Recreated my ODS

2) Re-initialize and re-do set up in R/3

3) Re-installed business contents

4) Transaction RSRV

Nothing helped...

Any inputs?

Thank you so much!

Maan

[Former Member · Accepted solution]

Hi Maria,

It could be that you did not update the Master Data Objects prior posting data to the ODS. Just try it out. It might help.

Regards,

Jkyle

[Former Member · Accepted solution]

Hi,

It might be the chance of invalid characters has been uploaded in infoobject , when you are uploading data to ODS. Even though the data is loaded successfully, it will give error in the activation .

So have oyu seen any inforamtion in job overview regarding invalid characters.

With rgds,

Anil Kumar Sharma .P

[Former Member · Accepted solution]

Hi Anil!

Thank you.. All are standard datasources and procedures so I don't know why R/3 is giving invalid characteristics. We just took out the infoobject since it's not needed.

Maan

[Former Member · Accepted solution]

Hi,

I mean ,Invalid characterstics means characterstics which are special charcters to BW. These are not supported directly in BW. But These are valid in R/3 . You can include the special (invalid) characters in BW using Tcode RSKC.Then You can do activation .

With rgds,

Anil Kumar Sharma .P

[Former Member · Accepted solution]

Hi Anil!

Actually, the problem was the 0STAT_DATE infoobject that uses 0DATE as reference characteristics. The data in the PSA have this values, '__.__.0000' instead of '00.00.0000'.

The faulty data was mentioned in the job log. I just didn't consider that it was the problem because it was mentioned after it stated that there was an error in getting SID values.

We just removed that infoobject. Do you think RSKC would help?

Thanks so much,

Maan

We just removed that certain in

[Former Member · Accepted solution]

Hi,

RSKC does not help here. Here first of all, fix out the problem in source system for giving nothing to the field STADAT of base table.

With rgds,

Anil Kumar Sharma .P

[Former Member]

Solved my problem

Thanks