Attribute change run Failing in Process Chain

Hi guys,
Every day my process chains is failing due to Attribute change run and I am maually running attribute change run.
And one more thing when the attr. change run is triggered automatically,then it is generating 2 change counters in RSATTR tcode instead of 1.
One is successfully completes and one is still in schedule.After 2days days it is showing like completed change count id.
Please help me.
Regards,
Tiragati.

Hi,
As you said Attribute change run step is failing every day.
can you post the error message. is it failing because of Lock issue or some other issue.
Mostly attribute change runs fails with lock issues. if its the same problem in your case. make sure that no master data objects runs at the time attribute change run runs.
Try to put some delay in the process of the Attribute change run so that it will not get failed.
Check if its the same ACR scheduled or diff objects?
Regards
KP

Similar Messages

  • Attribute change Run Failed/Scheduled

    Hello All,
    For a process Chain Attribute Change Run has failed in BW 3.5,and I Repeated the Change Run in Chain only
    where Repeat option is ,now the problem is in RSA1 it is now that change run is scheduled
    and sm37 it is showing that Canceled.
    Now there is Other Process Chain in BI7.0  which picks data from  3.5
    Should I repeat the Master data Chain in BW 3.5 followed by in BI 7.0
    Or any other way is possible as in BI7 the chain has run successfully..
    Thanks,
    Kiran

    Hi Kiran.......
    BI 7.0 and BW 3.5............totally two seperate systems..............here BW 3.5 is just act as a source system of BI 7.0.............if change run fails in BW3.5...............it is not going to effect BI 7.0.............
    As ajeet already said............it will effect the SID s in 3.5.............because attribute change run activates the master data...........and SID get generated during the activation of master data.......
    Also it will effect the aggregates............because aggregates also get adjusted during change run.......if any of the aggregates contains the master data.........which are getting activated in the change run....
    Now u r saying........that in SM37 it is showing that the job got cancelled............So it will not locked the master data..............terminated change runs generally lock the master data............then we hav to repeat the chain run to release the lock.........and u hav already repeated the change run............so no issue........
    Hope this helps..........
    Regards,
    Debjani........

  • Change run error in Process Chain

    Hi,
    I got an error in running the change run step in the process chain.
    The error is "The action is locked by a change run".
    Could this mean that the change run was running when this step in the process chain was invoked.
    I have a process chain with multiple(4) parallel processes and I would like to know from you gurus the best way to model such a process chain. Should I keep just one attribute change run at the end of the complete process chain or should I let the change run after every PC (each of the 4).
    Any inputs will be appreciated
    Thanks & Regards
    Sid

    Siddhartha,
       Exactly, you need to keep the change run process at the end of the PC. no need to run the change run for every master data flow.
    check whether change run is running? check in RS12 for locked entries.
    All the best.
    Regards,
    Nagesh Ganisetti.

  • Attribute Change run failed due to the User Lock

    Hi Friends,
    attribute change run has failed due to the user lock.
    can any one tell me how to process and what is the main cause behind on this.
    thanks in advance

    if master data is loading at same time while the attr/hier change run is occuring,it cause the change run to fail.
    Usually u get error message like..user ALEREMOTE has locked the MD tables..
    Wait for some time and then try attr change run manually by going to rsa1->tools->apply hier/attr change..
    if it still shows locked..try to see in rsmo if a MD load has got stuck..
    else..see in sm12 to find lock is on which tables..
    last resort..delete lock forcefully from sm12..
    first option is wait for some time and give a try again..
    cheers,
    Vishvesh

  • Attribute change run fails - "Error when deleting the data record /B05/X.."

    Hello,
    I get the error message "Error when deleting the data record /B05/X.." on doing the change run.
    I have already done RSRV on this objects and found no errors, but still the activation fails.
    please give your suggestions ASAP to fix the issue as it is on production system.
    Thanks.

    Attribute change run could fails due to 2 reasons-
    (1) attribute xchange run is already runnnig for any toher object(monitor lock) (check by thi prog-RSDDS_CHANGERUN_MONITOR)
    (2) data is loading deleting from the object on which attribut changerun is running.(go in a manage tab and check)
    check this two conditions and rerun the attribute changrun again from program - RSDDS_AGGREGATES_MAINTAIN and give the master data name in the selection.
    Hope it helps you.

  • Attribute Change Run Process chain

    Hi,
    We have a attribute change run step in Process chain with "selective infoobjects".
    But when it executes it runs attribute change run for all infoobjects apart from what i have mentioned in the variant.
    Proof:
    I had a snapshot of infoobject list in RSA1->Tools->Attribute change Run before executing process chain in which i saw info objects other than what i had in the variant.
    I ran the process chain.
    Again I saw the infoobject list RSA1->Tools->Attribute change Run and it was empty!!
    Even though I mention some infoobject in process "Attribute change Run" It runs for all info objects irrespective of what I maintain in the variant.
    This causes problem and creacting lock. If anyone ever observed this problem and resolved please let me know!!
    Thanks
    VJ

    well here is the POC ,I have nw204s SP-12 .
    Steps followed -
    Monitor of change run - 3 infoobjects currently waiting for CR.
    Built PC with Process type "Attribute  Change"  only ..no other process types barring "Start" which is imperative.
    Included only 2 Infoobjects from the 3 aforementioned.
    Scheduled as immediate and it executed CR for the 2 only,so my CR monitor shows now 1 pending for CR to be run,which is as expected.
    So as per Proof of Concept sp-12 works with process type "Attribute  Change"
    You may wish to check your process chain again and in worst case raise an OSS to SAP.
    Hope it Helps
    Chetan
    @CP..

  • ERROR while running attribute change run.

    hi sap xperts,
    I got an error while running the attribute change run in a process chain.
    At first i got an error "The action is locked by a change run"
    SO I DID THE FOLLOWING STEPS.
    1.RUN ATTRIB CHANGE RUN MANUALLY  IT RUN SUCCESSFULLY,but the process chain is still red.
    Q1.Is there any way to link the manually run attrib chnage to process chain so that the process chain becomes Green?
    2.SM12 - realease the locks and right click the pc and repeat.It didn't work
    Q1.While removing the locks what should we remove,bcoz i removed all the locks?
    3.I again removed the lock and repeat the process but still i didn't work.Now its chowing "SQL ERROR OCCURED WHILE ACCESSING"
    So the Process chain got stuck,Can any body help me to run the attrib chnage run.
    If possible can anybody send the Process chain monitoring documents to my email id:
      <email ID removed>
    please.thanks in advance,i know how to say thanks in sdn.

    At any point in time only one attribute change run can run in the system. The other ACR's will fail due to locks. In your case, to set the process chain to green, try the following steps.
    Open the messages of a failed step by right clicking on it and selecting 'display messages'.
    In the opened popup click on the tab 'Chain'.
    In a parallel session goto transaction se16 for table rspcprocesslog and display the entries with the following selections:
    1. copy the variant from the popup to the variante of table rspcprocesslog
    2. copy the instance from the popup to the instance of table rspcprocesslog
    3. copy the start date from the popup to the batchdate of table rspcprocesslog
    Press F8 to display the entries of table rspcprocesslog.
    Now open another session and goto transaction se37. Enter RSPC_PROCESS_FINISH as the name of the function module and run the fm in test mode.
    Now copy the entries of table rspcprocesslog to the input parameters of the function module like described as follows:
    1. rspcprocesslog-log_id -> i_logid
    2. rspcprocesslog-type -> i_type
    3. rspcprocesslog-variante -> i_variant
    4. rspcprocesslog-instance -> i_instance
    5. enter 'G' for parameter i_state (sets the status to green).
    Now press F8 to run the fm.
    The above steps will help you continue with the rest of the process chain (thus avoiding manual runs) but the failed step might still remain red. Hope this helps.

  • Attribute Change Run and Editing BI data

    Hello Experts,
    I have two questions.(They are not related to each other).
    Can BI data(Infocube data) be edited?
      For eg GL account in R/3 is changed from 100 to 2100. I want to know how can this be handled in BI.
    Attribute Change Run in the process chain ends with error.
      "Master data characteristic ZACCTNUM activated in 6 seconds. Error while activating characteristic   ZACCTNUM ". There are no more information.
       The BWREMOTE user has the authorisation to Execute Change Run.
       What could be the possible reasons for this failure.
    Thanks in advance.
    Regards
    Meenakshi

    Hi Meenakshi,
    Regarding your questons:
    1. You can't edit the data directly in the cube. If you have incorrect data in the cube and the data is still in the PSA you can edit the incorrect data in the PSA and you can then delete the incorrect requests from the cube. You can then reload the correct data from the PSA. If its not an option to delete individual requests you could delete the incorrect data using the selective deletion option (if you can select on the incorrect data in the cube). You could then reload the correct data from PSA or source system.
    2. Please check the infoobject ZACCTNUM is active in RSD1. If it is there may be an inconsistency with the data in the infoobject ZACCTNUM, please check if the solution part of the SAP note 1033721 can help you in this case.
    Best Regards,
    Des.

  • Attribute Change Run in Process Chain failed with SQL 942 error

    Hi,
    Attribute change run in th eprocess chain failed with the message " SQL Error 942" and ran succesfully after repeating the step.Searched in Forums for similar error but the solutions were not apt.
    Any pointers would be of great help!!
    Thanks in advance,
    Bhagyarekha.

    Hi Bhagyarekha,
    The reason behind that error could be:
    An attempt is made to activate a characteristic whose compounding was replaced and whose navigation attributes were simultaneously deleted. The replacement of the compounding temporarily deletes the M view of the characteristic during internal activation. The process of deleting navigation attributes involves converting the attribute SID tables. However, the M-view of the characteristic, which has just been deleted, is needed for this conversion.
    Check this SAP Note:
    Note 684405 - Replacing the compounding and deleting navigation attr.
    Hope it helps.
    Veerendra.

  • Attribute Change run canceled

    Hi
      I have loaded master data for an Infoobject and executed Attribute change run by saving that object and execute. I got the message like Attribute change run is canceled((protocol/shortdump) now i can not able to run any attribute change runs since save button is not available in the window and also unable to load data to the same infoobject getting errored and giving messsage locked by attribute change run i have checked in sm12 no locks exist on this object
    Thanks
    Vani

    Hi,
    You can try going to the monitor for Attribute change run from RSA1 >> tools >> apply change run or from Transaction RSATTR which will schedule/display attribute change run. Here you can have an option called change run monitor (Monitor icon). this wil show the status of change run including which all info objects are affected, and if its hitting the aggregates of any cubes. There are scenarios where the attribute change run failed with message that it was hitting/affecting aggregates of some infocubes. In case we had to switch off aggregates and trigger the change run again and then swtich on the aggregates after the change run is over. this may not be the exact issue you are facing.
    Most of the times we have problem with the Attribute Change Run(ACR) running because ACR and the Roll Up's for Aggregates cannot run in parallel.
    The Problem may be that there is another change run triggered parallely to yours.In any SAP System only One attribute change run can run at one point of time. i. e If one attribute change run is running in system from any process chain or for any project and 2nd one fails, if start at same time due to locking problem. Due to this entire data load fails.
    Just check it there are any other change run active in SM37. Repeat your change run once the other change run is over.
    And sometimes ACR goes on running for a long time in such case we need to check which Aggregate the ACR is currently changing and may need to deactivate that aggregate.
    But before deactivating an aggregate you need to check the data present in that and the usage of the aggregate.
    Also you can try Tcode CHANGERUNMONI/program RSDDS_CHANGERUN_MONITOR to view this data.
    thanks,
    JituK

  • Attribute change run error in daily job (BI 7.0 SP 23)

    Hi All,
    We are facing an Attribute Change Run error in one of our daily batch job.we donnot see any locks in SM12.and a dump occurs in ST22.we also donnot have any master data load running at that time .We executed the the FM RSDDS_AGGR_MOD_CLOSE,but the Change run error occurs frequently .How to get the root cause of this issue as we donnot have any master data load running at that time.
    regards,
    maria

    If you are sure that your master data is 0MATERIAL then GOTO-RSA1>Tools in Top>Select Attribute Hiearchy Change Run>Select Info Object List>Select 0MATERIAL>Execute.Then message "Attribute/Hierarchy change run scheduled" will appear in the Tab on your User ID.Once its finished your masterdata is activated.
    For Activate Master Data we can do another method like "Right click on the particular Infoobject which need to activate and click "Activate Master Data".
    The above steps is for manual activation of master data changes..
    If you want to automaize the above steps "Need to add Attribute/Hierarchy Change Run" in the process chain.When execution of Processchain it will activate all the master data in the list one by one and also realign the Aggregates which using the master data objects.

  • Error with Attribute Change Run - Urjent

    Hi All,
    In our scenario we will  load  master  data from APO&ECC to BW.When we are doing attribute change run we are geetting short dump and jobs are cancelling every time .
    Please fidn the details below.
    Short Dump : ORA-14400 with ABAP/4 DBIF_RSQL_SQL_ERROR..
    When I have searched in the forum I got some information saying that we need to drop the index and recreate  the index.But we have around 40 cubes.Then how I am going to deside on which I need to the relavent settings.
    Please provide me the proper answer.We are facing this problem from past last two  days.
    Regards
    Ramakanth.

    Hi,
    You can try going to the monitor for Attribute change run from RSA1 >> tools >> apply change run or from Transaction RSATTR which will schedule/display attribute change run. Here you can have an option called change run monitor (Monitor icon). this wil show the status of change run including which all info objects are affected, and if its hitting the aggregates of any cubes. There are scenarios where the attribute change run failed with message that it was hitting/affecting aggregates of some infocubes. In case we had to switch off aggregates and trigger the change run again and then swtich on the aggregates after the change run is over.
    And sometimes ACR goes on running for a long time in such case we need to check which Aggregate the ACR is currently changing and need to deactivate that aggregate.
    But before deactivating an aggregate you need to check the data present in that and the usage of the aggregate.
    Please use the table RSDDCHNGPROT and find out the infocube affected by this change run and de-activate "ALL" the aggregates
    of the infocube listed under CNSID=0. Then start the change-run.
    You can rebuild/refill the aggregates once the change-run is finished.This is necessary because there are inconsistencies in the aggregates
    Most of the times we have problem with the Attribute Change Run(ACR) running because ACR and the Roll Up's for Aggregates cannot run in parallel.
    Also you can try Tcode CHANGERUNMONI/program RSDDS_CHANGERUN_MONITOR to view this data.
    176606 - Apply Hierarchy/Attribute change ... long runtime
    175309 - Hierarchy/attribute - change run improved
    oss note 322644
    Hope this helps.
    Thanks,
    JituK

  • Attribute change run taking more time

    Hi Gurus
    I am loading master data 0mat_plant everyday
    nearly 2 to 3 lakhs record .The extracrion and loading is taking 30 min but attribute change run is taking 3 hrs .Is there any way to reduce attribute change run time.

    Hi,
    You can try going to the monitor for Attribute change run from RSA1 >> tools >> apply change run or from Transaction RSATTR which will schedule/display attribute change run. Here you can have an option called change run monitor (Monitor icon). this wil show the status of change run including which all info objects are affected, and if its hitting the aggregates of any cubes.
    There are scenarios where the attribute change run failed with message that it was hitting/affecting aggregates of some infocubes. In case we had to switch off aggregates and trigger the change run again and then swtich on the aggregates after the change run is over. this may not be the exact issue you are facing.
    And sometimes ACR goes on running for a long time in such case we need to check which Aggregate the ACR is currently changing and need to deactivate that aggregate.
    But before deactivating an aggregate you need to check the data present in that and the usage of the aggregate.
    Also you can try Tcode CHANGERUNMONI/program RSDDS_CHANGERUN_MONITOR to view this data.
    Note 903886 - Hierarchy and attribute change run
    thanks,
    JituK

  • Due to attribute change run(sid's is missing)...process chain is failed

    Hi All,
    Due to attribute change run (SID's is missing) process chain is failed.kindly suggest me how we can rectify for this issue.
    Thanks
    Ragav

    if master data is loading at same time while the attr/hier change run is occuring,it cause the change run to fail.
    Usually u get error message like..user ALEREMOTE has locked the MD tables..
    Wait for some time and then try attr change run manually by going to rsa1->tools->apply hier/attr change..
    if it still shows locked..try to see in rsmo if a MD load has got stuck..
    else..see in sm12 to find lock is on which tables..
    last resort..delete lock forcefully from sm12..
    first option is wait for some time and give a try again..
    cheers,
    Vishvesh

  • Attribute change run process doesn't run in the chain

    Hello everyone,
    I have implemented a process chain with multiple parallel processes (12, like the batch processes in the application server) and I have put for each stream a loading of master data followed by the attribute change run process. When I run my chain then I find that one o two Attribute change run process doesn't run (the InfoObject chosen seem to be random!). The chain remain in yellow color. Can you help me anyone about this question?
    Regards,
    Francesco

    Couple of thing you should keep in mind while loading master data.
    if two loads are targeted to the same infoobject they will collide and as a result the later load will fail.
    it is a good practice to use only one Attribute change run in the end before you load master data. but if there are dependecies you can use several in series
    Also when you set up Attribute change run make sure that Attribute change run will pickup only the particualr infoobject not all the objects in the Attribute change run list.

Maybe you are looking for