Invalid SID value for date field

[Former Member]

I am doing a "Delta Init" load data of data from R/3 into BI. When the R/3 data comes into the ODS I am getting Invalid Sid Values "20000000" error for one of the date fields. The error message gives a record number. I go into the PSA and bring up the record and the date fields looks OK.

I deleted all of the requests and changed the load to a full load with error handling for 1,000 errors. The full load runs but I get the same Invalid SID error on the date field.

1. I would have thought the full load with error handling would have bypassed the errors and loaded only the good data. Was I wrong?

2. Is there any way to find the invalid record in the PSA and fix it and then process the data into the ODS?

Any suggestions would be appreciated.

Recards,

Mike...

[Former Member]

Thanks to everyone who responded.

After a lot of looking at data we found that the one of the date fields coming from our R/3 system contained an invalid date (value was 20709171). The invalid date was making its way all the way to the PSA and into the ODS. When it tried activate the ODS and create a SID for that invalid date is when I got the error.

Thanks again for all your help.

Mike...

[Former Member]

Edit PSA Data ,Try to delete the incorrect entry in PSA and if those entries are correct again manually make entries of all those records which was previously mark as error.

Some time this might works.

[Former Member]

RaJ,

Thanks for the reply.

I forgot to mention that this is a transaction data load and not a master data load. I think the error is caused by a bad date in a date field coming from R/3. I would like to find the record in error so I can delete it in R/3.

The BW error is:

"Error when assigning SID (details in long text)"

Value '20000000 ' of characteristic 0DATE is not plausible.

Regards,

Mike...

[Former Member]

Edit/Correct the date in PSA.

[Former Member]

Hi,

what is your datasource in R/3? You'll have to analyze the data flow back to the R/3 table-field.

Another option as mentionned is to change this PSA record, however it will not fix it permanently in the case you'll extract this record again.... so you are right in wanting to correct this record in your source system....

Let's us know your DSource details, LO, generic, etc....

hope this helps....

Olviier.

[former_member187400]

Hi Michael,

You need to check that date in your PSA.. If you find it then you need to correct in the PSA & R/3 itself.

But if you don't find it ..

You can try this as my experience i was facing before:

1. Change the setting in the ODS for SIDs Generation upon activation => Make it with uncheck ..

• Activation&SIDs checking will be done in query's running.

2. You re-load this request, you can make it from PSA/source system.

3. Your data will get in to the info-provider, then you get the code from that info-provider.

4. Fix that data using the code in the R/3.

5. Re-load manually based on the code representing the incorrect/invalid data.

Hopefully it can solve your problem.

Regards,

Niel

• thanks for the points you choose to assign.

[Former Member]

Hi,

a) Kindly check in the CalDay SID table (/BI0/SDATE) for the entry you have in your load. If the entry is not existing, kindly take your necessary actions (adding the entry or correcting your PSA)

b) You can alternatively try checking the option of 'loading master data even if there is no master data'.

Best Regards,

Raj