Attribute Change Run- Serial or Parallel

If we are building a chain for Attribute Change Run for all Master data objects, should we:
1. load Masterdata A, followed by attribute change run, load masterdata B followed by attribute change run, load masterdata C followed by attribute change run....
2. Load Masterdata in Parallel followed by AND with ONE attribute change run.
The first one seems grossly redundant but then if we have only ONE attribute change run, wouldnt that lock up all the objects for a LONG time?
Also, does an attribute change run by default include ALL objects which have been loaded anew and for which the change run has not run???

Thanks!
So, having just one attribute change run for all these objects is a better option?
Wouldn't it lock up the objects for a long time?
Also, say I have loaded object A , B and C. And in my process chain I have Attribute change run only for Object C.
Will the Attribute Change Run include newly loaded A and B by default?
I ask this because we saw something like this happening
Edited by: CC on Apr 9, 2010 8:33 PM

Similar Messages

Attribute Change Run in Procee chain.

I am trying to create a process chain for loading employee master data. I have three datasources populating this data.
So in the process chain I have to add the Change Run process type only after loading data from all datasources right ?
what is the process type 'Attribute Change Run' useful for anyway ?

You are correct. If the loads to the employee Master Data Attributes are done serially, then you can end it with the 'Attribute Change Run' variant. If the loads to the employee Master Data Attributes are done in parallel, then you can have all three InfoPackages flow into an 'AND' variant and then have the 'Attribute Change Run' variant.
The 'Attribute Change Run' in effect activates the Master Data Attributes, much like the activation process of activation of a DSO. The way it does it technically behind the scenes, however, is different.

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

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

Why you cannot compress data while attribute change run is active?

why you cannot compress data while attribute change run is active?
Also, are there any prerequisites before running a compression.
Will the aggregates get inactive after running compression?
Regards,
Simmi

Hi Simmi,
I'm not sure what are u looking for ..???? now u are asking whther if activation starts at the same time for 2 ODS,.. there wont be any problem if the activation starts parallelly..
but these activation fails if the change run is running for the common master data. So make sure that when ever change run is running the corresponding master data will gets lock. thats the reason why u can see locks in rollup, compressions or any other parallel change runs....
Hope this helps....
Assign points if this helps.
thanks
Vishnu

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.

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!

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

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 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- Serial or Parallel

Similar Messages

Maybe you are looking for