on 04-15-2008 2:13 PM
Hi Guys,
Everyday in the process chain i experience an error in 0MAT_UNIT_ATTR as follows: "Lock not set for loading data attributes". Has anyone previously experienced this, and can you please tell me how to resolve this?
Thanks in advance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
This is a temperorary issue.
This is because the MD table may be locked due to another change run or load.
Try to find out if there is any other load running to the same target or any change run locking for this object.
Check RSATTR or CHANGERUNMONI for the objects that are being part of change run.
If its there wait for that to get over.
Once done you can force the request to red, delete the bad request from target and retrigger the IP.
Also check in SM12 for any lock entries for the MD table.
Thanks,
JituK
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
First thing to check is whether an "attribute change run" job is running at the same time.
If you have multiple process chains loading master data and they all have change run processes in them, you will have these kinds of conflicts. You have to organize them so change run doesn't conflict with some other master data load.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.