Recently, we have received many complaints about 2 particular issues. The solutions are already documented, but it always requires more explanations before the issue is completely eliminated.
I was a little reluctant about creating posts about these issues. However, I have seen so many complaints about this, that I realized a weblog post about it may be really useful for many BW consultants, to let them quickly solve the problem by their your own.
The first issue is about transformation transports. I have worked on many messages in which transformations were not correctly converted when transported, even though the source systems mapping for the transport is properly set. Furthermore, the transport logs show the error code RSTRAN803.
This issue can be prevented by implement the following SAP Note:
1412414 - (SP24) Content is not generated/transport errors.
However, even after you apply it and re-transport the transformation, you may still have an inactive object inconsistently pointing to the wrong system. This is where you may think SAP Note #1412414 didn't solve the issue and open a message to SAP Support. Specially because it's impossible to display or manually delete this inconsistent transformation.
What you need to know is that, if in the table RSTRAN, you can see an ‘M' (Modified) version of this transformation pointing to the wrong system, you may delete it using the method CL_RSTRAN_STAT=>DELETE_VERSION_FROM_DB, as described in the SAP Note below:
1240905 - Transformation guide: Transport of deletions.
1- SE24 - Display CL_RSTRAN_STAT.
2- Click on the Test Icon.
3- Run the method DELETE_VERSION_FROM_DB.
4- Provide in the field I_TRANID the Id of the transformation to be deleted and the value ‘M' in the field I_OBJVERS.
The inconsistent version will be deleted.
In the next post I will talk about another frequent issue: Oracle DeadLocks on data loads.
1 Comment
