Delta Records not coming from sm13 to rsa7

Question

Hi,
We have found that for the application 02, delta records are coming in RSA7(delta queue) even if these are coming in sm13.
It appears that some protocol responsible for bringing the delta records from sm13 to rsa7 is failed.
Fact is that for the data sources related to application 02 (purchasing: LO Cockpit), we did some enhancements through LBWE.
But before transporting the relavant requests to production, we did not delete sm13 and rsa7 entries and also at the time of transpoting the requests in production, postings were made by several users and the entries for those were appearing in sm13.
Thing to notice is that whatever fields were shifted in LBWE, those changes have successfully appeared in production after transporting ( LBWE and relavant Extract Structure in Production are containing the required changes)
Now each time to load the data in BW, we have to delete and refill the set up tables and schedule full update which is taking a lot of time and not advisable.
Each time when we are running job control in LBWE, it is throwing dump in ST22 with the heading CONNE_IMPORT_WRONG_STRUCTURE.
It appears that some internal problem has occured in the structure of rsa7/sm13 for application 02.
Also it is written in the dump that:--
When attempting to import data, the structure of the complex object
"MC02M_0ITM_TAB"
was not compatible with the target object. The error occurred with
component no. 24.
Try to find out why the structure of the object is unsuitable.
There are several possible reasons:
|
--- In the ABAP Dictionary, the structure of the imported
|   object has changed. Make sure that the structure of the imported
|   object matches that of the Dictionary structure.
|
|   If the data could not be restored from another source, this data
|   must be read with the "old" structure, then converted and exported
|   back with the new structure, so that future IMPORTs always work
|   with the new structure.
|
--- A new program version is active, and it no longer matches the
    dataset. Try to solve the error by generating the program "SAPLMCEX" again
    as follows:
    In the SAP System, choose the transaction SE38. Enter the program
    name "SAPLMCEX". Then choose the "Activate" function.
Now how to make the things back on track so that delta records come in rsa7 from sm13 so that we schedule delta update in info package.
Is there any OSS Note or Standard SAP Report which we have to run for getting the solution.
If not, please suggest the solution.
Thanks in advance,
Tarun Brijwani.

Answer 1

Hi,
1. Check whether your Extractor will support Early Delta Inti or not..
See this link for  Early Delta Initia...
http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/frameset.htm
Minimize downtime for delta intia..
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5d51aa90-0201-0010-749e-d6b993c7a0d6
Perform this activity on Weekends,
Also see 436393 - Performance improvement for filling the setup tables
Note 753654 - How can downtime be reduced for setup table update
2. Obviously Background job.
BG jobs can be monitored thru SM37 and maintain Logs thru SM21 and can be easier for administration
Thanks