on 12-23-2008 3:50 AM
Hi All,
Can you advice how to set locking logic, in situations where nightly background jobs are failing, which are not recognised until next morning, this is due to system not forcing users out of system when these jobs run.??
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Visu,
How can a job running on some ID at whatever time and system fail..with concurrent access in dialog by other users. Unless the background user is same as the dialog user. I mean the results may loose currency or may be incorrect but why would the job fail because of this.
Regards,
Loknath
Hi Loknath,
Failing a job is primarily related to locking one or more of the things that the program is trying to change. Check the locks in SM12 for locks and that shows you what's locking you and causing the failure. Also the job log should tell you some thing.
"I mean the results may loose currency or may be incorrect but why would the job fail because of this."
This is not true.
If I am trying to delete an order using a program in a background job at the same time there is a planning run involving the order, then th job fails. I am not sure what you actually meant but it does not partially delete th order or only delete 50% of the qty. of the order as it is locked. It leads to problems..
Please let me know if I got your point right.
User | Count |
---|---|
11 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.