Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from ScottBJ on Sep 26 at 12:57 PM Hi Neal,
I don't have any experience with your particular process, but the Workload Monitor stores dialog transactions in the STAT. As long as the change happened recently you might catch it there. I think you can also monitor a particular transaction with SM19 & SM20. You can turn on Table Logging for one of the tables KE1K populates (probably a modification). I use a user exit in the collector job to store all user activity (Tcode, User, Terminal, Date, Time, etc.) permanently in a custom table for just this kind of scenario. Let me know if you would like more detail.
Scott
| | | ---------------Original Message---------------
From: R. N. Wilhite
Sent: Wednesday, September 26, 2012 9:38 AM
Subject: Who is Changing the INDX Used by MD63
Can someone just shoot me now? It might just be easier than solving this problem.
Ever since SP18 (ECC6) SAP has introduced an error into background loading of MC94 records and transfer from MC94 to MD63. We have an external forcast system (JDA) and we flat file interface into SAP via RKEVEXT3. This inputs basic data into MC94. Then we use RKEGESPL to transfer from MC94 to MD63. RKEGESPL assumes that you have assigned the correct index from INDX that were created via KE1K.
So, there you have it. Someone is creating new indexes and I don't know how to find out who that is...
Any suggestions would be helpful...
Neal |
| Reply to this email to post your response. __.____._ |   _.____.__ |
