From: Wang, Jerry
Sent: Montag, 9. Juni 2014 10:48
Hi Carsten,
I am now on customer site to help them resolve an annoying issue in their CRM system. Simply speaking, customer has encountered database inconsistency between table CMSD_CI_HISTORYand CMSD_LO_STATUS. They have a background report which are running periodically calling APIs which will finally change these two tables.
Sometimes after report runs, the table CMSD_CI_HISTORY is updated as expected butCMSD_LO_STATUS remains unchanged. Since customer and partner and even SAP support team colleagues could not find a way to reproduce this issue, we could only make analysis based on the source code statically, instead of debugging in the runtime.
During reading code I find CMSD_CI_HISTORY is changed in one BAdI, while CMSD_LO_STATUS is changed in update function module CMS_LO_STATUS_UPDATE_DB.
My question: since these two table are updated in different workprocess ( normal work process and update work process ), is it possible that the update function module fails to be executed at all due to the heavy system load ( no free update work process ? ) I just would like to get your suggestion whether this would be a potential reason which causes the inconsistency.
From: Carsten
Sent: Tuesday, June 10, 2014 3:03 PM
To: Wang, Jerry
Hi Jerry,
I don’t think this is due to a problem in the update work process. Normally this runs smoothly. If updates terminates, you should be able to see failed records in transaction SM13. Is it ensured that a COMMIT WORK is posted after calling the update function module? Else no update will be performed. Is the problem occurring only sometimes? If this is customer code, you could also insert some statements temporarily that help to trace the problem by writing some log entries.
Best regards,
Carsten
要获取更多Jerry的原创文章，请关注公众号"汪子熙":