Skip to Content
author's profile photo Former Member
Former Member

Change Attributes Run Error

Hi BW Gurus,

I am executing master data loads using a Process chain.

On some fine days i get error of change attribute run. Its not specific to any master data source. It comes for any master data source. I get following error message when i display messages in RSPC...

<b>The action is locked by a change run

The change run has been started already by user ALEREMOTE

Lock NOT set for: Change run for hierarchies and attributes</b>

My transaction data process chain is dependent on successfull load of Master Data chain.

I need to rerun the change attribute run after it goes in red to make it green, other wise it does not execute the remaining process chains.

Has anyone faced such kind of problem.

Any Ideas or suggestions..

Thanks and Regards

Deepak

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Dec 30, 2004 at 10:21 AM

    Hello Deepak,

    Change run does the realignment of the master data at the BW side, Therefore if master data get changed at the OLTP source system side, need to execute the change run job at BW side in order to synchronize changed records.

    I would recommend to include change run task in process chain itself for hierarchies and attributes so you don't require to trigger it manually and in turn transaction load gets succeeded.

    Thanks and Regards,

    ~Ketan Patel.

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Creating Process Chains with the 'wizard' creates lots of different Attrib Change tasks. If these end up running simultaneously for the <b>Attribute and Hierarchy of the same Infoobject</b> then you will provoke the error you reported.

      It seems better to have one Att. Change task in a chain and add all the different objects to it.

      Follow the instructions on the Attr Ch. definition screen (To Select, Press F4 On The Object Type, Then F4 on the Name), it takes a bit of practice, then its easy.

      Like this you can be more certain not to get clashes.

  • author's profile photo Former Member
    Former Member
    Posted on Dec 31, 2004 at 06:28 AM

    Hello Deepak,

    Before giving A priority to process chain job, I would recommend to use work process monitor while you schedule process chain and analyze the process which gives locking error. If it doesn't work then use enqueue trace to find out...

    1.Which object causing locking

    2.When it gets occurred

    Thanks and Regards,

    ~Ketan Patel

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.