Question:
We have a view on the R/3 side which joins the VBUP and VBUK tables so that all document statuses for both header and item are in one view.
We do a simple extraction of this view into an ODS in BW.
Occasionally, the load fails with the message
Object requested is currently locked by user ALEREMOTE.
Is it possible that the extract might be stepping on its own toes? Or is there something I can do to prevent this?
Answer:
Hi Steve ,
Check this job in SM37 wheather its still running or not ? If not then wait till it stops or finishes . After finishing of this job only you can start it .
Cheers,
[V]
Answer:
Hi Steve ,
Check this job in SM37 wheather its still running or not ? If not then wait till it stops or finishes . After finishing of this job only you can start it .
Cheers,
[V]
Which job are you referring to?
Answer:
Hi Steve ,
The job which I was mentioning , It was nothing but the request which can be seen in R/3 & BW . Goto monitor & then you can see the request . Copy that request & check it R/3 by SM37 then you will see it might be running .
Hope that would make it more clear !
[V]
Answer:
We run this extraction overnight, and the lock occurs very infrequently (once every couple of months or so), and we cannot reproduce the situation in any test we run. We have no one who monitors the loads overnight, so we don't know that the issue has occurred until the next morning.
Since we can't reproduce the conditions that result in the error message, we are unable to debug through the extractor to see where the lock is occurring.
I was just wondering if anyone else had had any similar experiences with extracting from an R/3 view.