error handling in an ODS

[charla_robertson]

Our data load into our Billing conditions ODS failed last night in our bw production system. It failed because a bad date was entered in our R3 system and that data tried to load into our ODS. The bad date was entered for 0CALDAY and had a value of '00060828'. There are several records with this incorrect date. Our error handling options in the infopackage are limited because we are loading into an ODS. Any suggestions?

Thanks!

[Former Member · Accepted solution]

Hi Charla,

best solution is to correct data in R/3 and upload again.

If you can not in R/3 you can try to correct in PSA all affected records and upload from PSA (you have to delete request from ODS before correct in PSA).

For the futere you can follow this solution: create a copy of your ODS1 (ODS2). In start routine of ODS let enter only records that start with 200 or a similar rule. In Start Routine of the second ODS let enter all the other records, you can then check all records in ODS2 and then decide if import the same in ODS1 or delete.

Ciao.

Riccardo.

[stevenm_wilson]

We have had this same problem before. What we did to solve this issue is to check the date in the update rules. If the date is invalid or outside of the fiscal variant, then change it to a valid date (let's say sy-datum). In your R/3 system, you will eventually get the correct date. Some processes in R/3 allow the user to enter an invalid date then, later, the correct date can be updated.

As part of our checking, when we make this change programatically, we send an email to our support group notifying them of the billing document number in which the date was "changed" by our update rules. This way, someone can go in later, correct the date and it will flow back to us with no problems!

This way really works nicely as it allows your processes to continue as designed, but notifies support of possible inconsistancies in the data before users identify them..

Let me know if you need any sample code.

/smw

[Former Member]

Hi,

You can also set the update option to load till PSA and then update subsequently. That way you can go back to the PSA, correct the incorrect records and then push the data to ODS.

But best practice is to have the records corrected in source system and the reloaded to BW. This way you avoid data integrity issues and your source and target data match from a reconciliation stand point.

Cheers,

Kedar