2LIS_13_VDITM Extractor

[Former Member]

A transport from R/3 development has been moved to production. However, it was not noticed that the transport included a deletion of a field from R/3 (a mistake) which is still a requirement for B/W. When the transport is replicated to B/W you get an error since R/3 and B/W are out of synch.

Has anyone come across this problem and how did they solve. The concern here is that we have a delta queue, so this needs to also be dealt with

Thanks for your help

[Former Member]

Hi Harry,

If the field is needed, it needs to be mapped in the VDITM extract structure and hence moved to production. If the field is no longer needed, then on BW end the field should be de-mapped. As history of the cube / ods contains this value, they shouldn't be disturbed. But in case if this characteristic is a KEY FIELD in ODS, you need to ensure that, you are getting what is needed in the reports.

if there is a INTEGRITY CHECK on this, then it has to be removed.

You shouldn't have an issue with DELTA, reason being you are not deleting the delta queue in RSA7. So as long as you don't drop this, you should be safe.

Hope this answers your question.

Regards,

GPK.

[Former Member]

Praveen,

Thanks for that are you on an email so that I can take this up with you further?

Thanks

Harry

[Former Member]

What my concern is that there are circa 20,000 records in the Delta queue. If I demap the field in B/W and load the data I will have that many records without the value which has been demapped.

I can possibly right a routine to add the value but would prefer not to. So was looking at any alternatives.

Once the 20,000 records have been corrected, I can enhance the extractor and remap but its the bit in between.

Thanks