Attribute change run cancelled - Reg

Hi,
Can we run master data Job if attribute change run has cancelled for the same Master data Object?
Thanks,
Ajay

Hi,
if the attribute changerun is cancelled then you cannt run thw masterdata.. because it wil agian fail with the message :
locked by terminated changerun .. so first run the chaingerun succssfully to release the masterdata..
check the link to release the lock ..
Attribute ChangeRun issue
hope this helps you .
Reagrds,
Shikha.
Edited by: Shikha Goel on Oct 14, 2008 10:09 PM

Similar Messages

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

Hi i have 50 infoobjects as part of my aggregates and in that 10 infoobjects have received changes in masterdata.so in my process chain the Attribute change run in running for a long time.can i kill the job and repeat the same.

Hi i have 50 infoobjects as part of my aggregates and in that 10 infoobjects have received changes in masterdata.so in my process chain the Attribute change run in running for a long time.can i kill the job and repeat the same.

Hi,
I believe this would be your Prod system, so don't just cancel it but look at the job log. If it is still processing then don't kill it and wait for the change run to complete but if you can see that nothing is happening and it is stuck for a long time then you can go ahead and cancel it.
But please be sure, as these kind of jobs can create problems if you cancel them in the middle of a job.
Regards,
Arminder Singh

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........

Attribute change Run and Infocube Problem

Hi SAP BW Experts ,
I am getting the following problem
2 days back our production system was down when Attribute change run is running in a process chain . After the system is up I triggered the Attribute change run manually for that specific master data Object. But the jobs was cancled automatically. When I checked the Job log I found the following messages
InfoCube XXX is locked by a terminated change Run
System error: RSDU_TABLE_COPY_INI/DDIF_TABL_ACTIVATE /BIC/E200073 /BIC/E100073 0
Message no. DBMAN100
When I verified manage screen in the Infocube XXX , one request is not rolled up . when I tried to rollup that particular request manually again I am getting the same message InfoCube XXX is locked by a terminated change Run
When I tried to create Indexes on that Infocunbe XXX , Again I am getting the same message InfoCube XXX is locked by a terminated change Run
When I tried to load data in to that Infocube I am getting the same message InfoCube XXX is locked by a terminated change Run
The Steps Taken By Me:
1. In SM12 , there are no lock entries for the Infocube XXX
2. According to A.H.P reply I verified the Support package . We are having Import Support package 18 for 3.10( BW 3.10 patch 18 or SAPKW31018 )
so I think there is no problem from patch side.
So please let me know by doing which task , I can eliminate the error message InfoCube XXX is locked by a terminated change Run

I got this reference from one of other site. Hope this solves issues of most of our ques on this topic.
We faced this problem and reported to OSS. They solved our problem.Here is
the answer from OSS
I connected to your BWQ system. I checked the table RSDDAGGRMODSTATEand
found an entrie for a change run "not yet" finished.
CNSID CLOSEDFL TIMESTMP_START TIMESTMP_END TSTPNM
207,851,300 20,030,910,141,500 0 SIDTLHG
As you can see, the field CLOSEDFL is blank (should be 'X' for an ended
change run) and the field TIMESTMP_END is also zero.
You can also check with the function module RSDDS_CHANGERUN_MONITOR as
in note 388069 that both objects you reported are the ones involved
with thi change run error (Infocube ZINV and Infoobject ZELEM_PEP):
E_CR_STATE C
E_T_CHANM 1 Entry (IOBJNM = ZELEM_PEP)
E_T_HIEID 0 Entries
E_T_AGGRSTATE 1 Entry (AGGRID = 3QR79ZYB6VGSDS3C42HPXMA8S
ICUBE = ZINV)
E_T_MSG 1 Entry (IOBJNM = ZELEM_PEP)
You have two choices to solve this problem. You cn either:
1.- Restart the change run and let it finish with ok.
The change run usually fails due to database errors, tablespace
problems, and when some user manually cancel it (NEVER should be
done!!)
2.- Change manually the entry from table RSDDAGGRMODSTATE that isdescribed
above. Set the field CLOSEDFL with a 'X' and also fill the field
TIMESTMP_END with a value with the following format
yy,yym,mdd,hhm,mss. Use, for example, '20,030,910,181,500'
IMPORTANT!!!
After this change on table RSDDAGGRMODSTATE, you have todeactivate
all aggregates, activate again and refill them!!
Hope this solves your error. If the issue is solved, please close this
message with the [confirm] button.
Best regards,
David =C1lvarez
SAP Active Global Support
The answer refers to our problem.We chosed option 2. Here is the AbAPcode:
REPORT ZLOCKED .
tables: RSDDAGGRMODSTATE.
select * from RSDDAGGRMODSTATE where CLOSEDFL = ' '.
RSDDAGGRMODSTATE-CLOSEDFL = 'X'.
RSDDAGGRMODSTATE-TIMESTMP_END = 20020912195015.
MODIFY RSDDAGGRMODSTATE.
ENDSELECT.

Attribute change run---imp--urgent

hi experts,
when i am trying to run attribute change run for master data infoobject, always it gets cancelled, the reason system shows for cancelled attribute change run is "Hierarchy/Attribute change cancelled (protocol/Shortdump)"
what is the reason for this and secondly when i try to do the manual activation of that particular infoobject, it gives a pop-up window saying " The infoobject XXXX is already active" which means that though we are doing the manual activation, it is not doing the activation. Why i am strong in saying this is beacuse there were new records entered into that infoobject and after the data loading when i activate it manually because attribute change run is not running successully, it shows that infoobject data is already active.
why is it so ? what could be the reason?
would appreciate your quick responce

Hi,
Are you able to schedule the Attribute change run from Tools-> attribute Hierarchy change run? I hope you still able to see your Info object in the list.
Check the shortdump. May be you can find a clue as sometimes some aggrgetaes cause problem while adjusting. If you find such aggrgeate, deactivate it and run teh change run.
You can also check in the Attribute change run monitor. There also youw ill find clues as which aggrgeate is causing the problem.
Regards
Srini

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 terminating - repeated several times - not locked

I had a failure in my master data chain tonight. The attribute change run that ran yesterday ran for 11k seconds and was cancelled (it says manually). When the chain ran tonight, the process failed again. I checked the log and it says "UNCAUGHT_EXCEPTION" and it created a short dump. I tried repeating to see if it did anything and it gave me the same message.
I went into the change run monitor and reset the status and manually tried to run the change run again. Same result "UNCAUGHT_EXCEPTION".
I then checked table RSDDAGGRMODSTATE and there was no blank CNSID entries, but there was a blank "completed flag" entry. I don't have change access to the table in prod so I cannot manually change it to X (meaning closed). I reset the status again in the chagne run monitor and the record with the blank "completed flag" disappeared. I repeated the change run and it failed again and a new record with the "completed flag" being blank appeared in the RSDDAGGRMODSTATE table.
I checked SM12 and there are no locks there. I'm on 7.0 so I can't manually right click on 0CUSTOMER and activate the master data either.
As a last resort I did run the function module RSDDS_AGGR_MOD_CLOSE but that short dumped too.
Any ideas? Please? This will fail my other chains that have 0CUSTOMER in the aggregates. Thanks.

HI,
Firstly try this FM RSDDS_AGGREGATES_MAINTAIN
if not possible
Try doing it manually
Uncaught exception may come due to many reasons
IN RSA1 go to tools and select attribute change run
Check the blog it shows you how to manually do attribute change run step by Step (for BI7.0 also)
/people/debjani.das/blog/2009/03/30/attribute-change-run-acr
Regards,
MADhu.
Edited by: MadhuMarupudi on Aug 21, 2009 5:49 AM

Attribute Change run taking too long time to complete.

Hi all,
Attribute change run has been taking too long time to complete.It has to realign 50 odd aggreagates, some by delta , some by reconstruction. But inspite of all the aggregates it used to finish in quick time earlier. But since last 4-5 days it is taking indefinite time to finish.
Can anyone please suggest what all reasons may be causing this? and what possibly can be the solution to the problem? It is becoming a big issue. So kindly help with ur advises.
Promise to reward your answer liberally.
Regards,
Pradyut.

Hi,
Check with your functional owners in R/3 if there are mass changes/realignments or classification changes are going on regarding master data. e.g. reasigning materials to other material groups. This causes a major realignment in BW for all the aggregates. Otherwise check for parameterchanges / patches or missing db stats with your sap basis team.
Kind regards, Patrick Rieken.

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 problem - infoobject is not listed in the list

Hi folks,
When I load master data for 0customer, the infoobject 0customer doesnt come in the infoobject list for attribute change run. Also, when I try to activate master data manually it says 'Master Data already active'. and the reality is M version of Data is not active.
Can you guide me.

Try running the program RSDMD_CHECKPRG_ALL for this infoobject. You can select all the options when running this program.
Try running this program multiple times, coz my experience showed that initial run may not always fix this issue.
Good luck!

ABAP program to add in the process chain before the attribute change run

Hi
I need a ABAP program to add in the process chain before the attribute change run(process) to avoid the locks, can any one send me the program
Regards,
Satish

I am not sure of any standard program .... but you can write your own... should be a small one..
you can check if the table RSDMDENQ has entry for your InfoObject... if yes, then its locked.. if not.. its not locked

Issue: attributes change run triggers the rebuilt of 0IC_C03 aggregates

Hello Guru,
I am facing to a problem that I don't understand.
Here is below the detail of the messages of a '3-infoobjects attributes change run' step of a Master Data process chain.
22:06:14     Job started
22:06:14     Step 001 started (program RSPROCESS, variant &0000000231235, user ID RFC_BW)
22:06:16     Starting process type ATTRIBCHAN with 3 objects...
22:06:16     Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BICHNG_D8FC4Q04UD7NGLDMZ0QUBLX4K with ID 22061600
22:06:16     Editing of aggregate 100139; background job BICHNG_D8FC4Q04UD7NGLDMZ0QUBLX4K; start time 22:06:16/07.07.2010
22:06:18     Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BICHNG_D8FC4Q04UD7NGLDMZ0QUBLX4K with ID 22061601
22:06:18     Editing of aggregate 100143; background job BICHNG_D8FC4Q04UD7NGLDMZ0QUBLX4K; start time 22:06:18/07.07.2010
23:02:29     Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BICHNG_D8FC4Q04UD7NGLDMZ0QUBLX4K with ID 23022900
23:02:29     Editing of aggregate 100140; background job BICHNG_D8FC4Q04UD7NGLDMZ0QUBLX4K; start time 23:02:29/07.07.2010
23:52:38     Starting process type MDHIERACT with 2 objects...
23:52:39     Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BIACTI_D8FCR9Y1NWOP2T4F76FYE0HDG with ID 23523900
23:52:39     Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BIACTI_D8FCR9Y1NWOP2T4F76FYE0HDG with ID 23523901
23:53:10     Aggregate 100139: Repair indexes
23:57:14     Aggregate 100140: Repair indexes
00:17:23     Aggregate 100143: Repair indexes
00:50:09     3 aggregates are condensed
00:50:09     Starting process type CONDAGGR with 3 objects...
00:50:10     Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BICOND_D8FD3GTNF0KF92R34346SW6PG with ID 00501000
00:50:10     Editing of aggregate 100143; background job BICOND_D8FD3GTNF0KF92R34346SW6PG; start time 00:50:10/08.07.2010
00:50:10     Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BICOND_D8FD3GTNF0KF92R34346SW6PG with ID 00501001
00:50:10     Editing of aggregate 100140; background job BICOND_D8FD3GTNF0KF92R34346SW6PG; start time 00:50:10/08.07.2010
00:50:16     Program RSBATCH_EXECUTE_PROZESS successfully scheduled as job BICOND_D8FD3GTNF0KF92R34346SW6PG with ID 00501600
00:50:16     Editing of aggregate 100139; background job BICOND_D8FD3GTNF0KF92R34346SW6PG; start time 00:50:16/08.07.2010
00:50:22     Hierarchy/attribute change successfully carried out
00:50:23     Event RSPROCESS with parameter D59BE8XWZMHY0IFP2VLEFP671 successfully triggered
00:50:23     Job finished
As you can observe, the step takes almost 3 hours !!!!!!! After anlyses BICHNG_* concerns
22:06:16 Job started
22:06:16 Step 001 started (program RSBATCH_EXECUTE_PROZESS, variant &0000000891873, user ID RFC_BW)
22:06:18 Aggregate 100139( 0IC_C03) is being adapted / rebuilt
22:06:18 Statistic UID of the aggregate process: 'D8FC4Q9KSAMRDWQ1RDPPKMF3O' (RSDDSTATAGGR)
22:06:27 Aggregate 100139: Read (1) from table /BI0/E0ICC03_ (max 500000 records)22:06:27 SQL: 07.07.2010 22:06:27 RFC_BW
I don't understand what is the link between the '3-infoobjects attributes change run' (BBATCH, 0MAT_SALES, 0MAT_PLANT) and the rebuilt of 3 0IC_C03 (Material Stocks/Movements) aggregates (why does the 'attribute chan run' trigger the rebuit of aggregates???).
The rebuilt of the 3 aggregates takes 1 416, 3 366, 3 009 secondes...
Does anyone understand my problematic? If not I can give you more details.
Thanks in advance for your help.
Samuel

1/ Exactly Fred
Here is the definitions of the aggregate:
100139:
0PLANT
0STOR_LOC
0MAT_PLANT__0VAL_CLASS
0STOCKCAT
0STOCKTYPE
BMODIFIC
BMVTSTOCK
0MATL_TYPE
0CALxxx
2/ For my information in the aggregate 100140 , does the presence of BBATCH (one of the 3 IO) trigger the rebuilt or is it only 0MAT_PLANT__0VAL_CLASS ?
100140:
0PLANT
0STOR_LOC
0MATERIAL
0MAT_PLANT__0VAL_CLASS
BBATCH
0STOCKCAT
0STOCKTYPE
BMODIFIC
BMVTSTOCK
0MATL_TYPE
0CALxxx
3/ In the same process chain, I have another Attributes Change Run: 0MATERIAL. Several active aggregates using 0MATERIAL__0MATL_TYPE are built on a CO-PA cube.
Why did the '0MATERIAL Attributes Change Run' rebuild no aggregate? (see below)
22:06:04     Job started
22:06:04     Step 001 started (program RSPROCESS, variant &0000000231238, user ID RFC_BW)
22:06:06     Activation of master data for 0MATERIAL
22:06:07     154 Data records deleted
22:06:11     154 Data records deleted
22:06:12     154 Data records updated
22:06:13     154 Data records updated
22:06:13     0 aggregates are condensed
22:06:14     Hierarchy/attribute change successfully carried out
22:06:14     Event RSPROCESS with parameter D59BEEE069HKRCRU0ZPYFUPB1 successfully triggered
22:06:14     Job finished
Samuel

Regarding attribute change runs in process chains

Hi All,
While creating process chain for master data objects. I am trying to incorporate attribute change run process type for an info object. But the system asks for the DTP of the attribute and when i choose the DTP then both DTP and then Attribute are being incorporated. This is not exactly a problem but i need to understand why it is happening as i am already using that DTP to load data. Will this affect the data in master data object?. Thanks in advance.
regards
satish

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 taking very Long time.

Hi Experts:
We are daily loading Master data from one common process chain. There are 33 Infoobjects which are getting activated in Attribute Change Run Process. This process is taking almost 3 hours to run daily; due to this it is impacting our other data load process chains.
Many times it happens that there is lock on cubes due to attribute change as attributes are getting aligned to same cube on which the roll up is running.
There are local chains below the attribute change run, which are also important to run.
Please help and suggest the workaround for the same.
Cheers,
Omkar

33 info objects in one ACR(attribute change run) is not a good idea.
Better to split the info objects and use multiple ACR.
During your ACR if transaction data load was on then lock issues always occurs.
Thats why we need to run master data loads first and later transaction data loads.
Which info object change run was troubling, better to note the info objects which are causing and try to put them in separate ACR and trigger it before start of your transaction data loads. so that it won't raise the same issue again.

Attribute change run cancelled - Reg

Similar Messages

Maybe you are looking for