Change Run performance

Hi all,
we've being having problems with the attr change run, it's been taking too long. We heard of a setting for the % of change of master data to run the change run process. How does it work and how can we set this ? We need to do delta master data load for this to work, or it can be used with full load too ?
Is there any other consideration to improve this process times ?
thx in advance (again)
JP

...thanks a lot for the notes Patrick.
How about the % of master data change. I found it is set on transaction SPRO, and still have a couple of questions:
1) Do i need to load master data using delta to use this ?
2) What if I set a 30% of master data change for the pocess, then a 0CUSTOMER attribute change and it doesn't represent a 30% of change, this means that the change run is not going to run and 0CUSTOMER won't be updated for the aggregates ?
thx again

Similar Messages

For one Urgent Change during performing the Approval(chnging the status to 'To be Tested') system does not recognize any changes using the CTS WBS BOM in the development system. The transaction is therefore incorrect or the status was reset by the system.

For one Urgent Change while performing the one of the Approval before changing the status to 'To Be Tested'
We are getting below error.
The system does not recognize any changes using the CTS WBS BOM in the development system. The transaction is therefore incorrect or the status was reset by the system.
COuld anyone please help us to know, How it can be resolved?
We also have this below error.
System Response
If the PPF action is a condition check, the condition is initially considered as not met, and leads to another warning, an error message, or status reset, depending on the configuration.
If the PPF action is the execution of a task in the task list, and the exception is critical, there is another error message in the document.
Procedure
The condition cannot be met until the cause is removed. Analyze all messages in the transaction application log.
Procedure for System Administration
Analyze any other messages in the task list application log, and the entries for the object /TMWFLOW/CMSCV
Additional Information:
System cancel RFC destination SM_UK4CLNT005_TRUSTED, Call TR_READ_COMM:
No authorization to log on as a trusted system (Tr usted RC=0).
/TMWFLOW/TU_GET_REQUEST_REMOTE:E:/TMWFLOW/TRACK_N:107
For above error Table /TMWFLOW/REP_DATA_FLOWwas refreshed as well but still the same error.

If you are in Test System, you can use function module AA_AFABER_DELETE to totally delete the depreciation area (tcode SE37, specify chart of depreciation and depreciation area), After that recreate your depreciation area and run AFBN. But before you do that, have you created a retirement transaction type that limits the posting on your new depreciation area? If not create one.
Hope this helps.
Thanks!
Jhero

Issue with Attrbute Change Run in BI 7.0

Hi All,
I have loaded a few master data objects as well as some custom master data objects and have found that they do not always show up in the list when you go to apply the attribute change run to something you have just loaded.
For instance I have just loaded a custom object from a DSO and if I click on manage on the attribute the load is there but I am not seeing any data in the object, then if I go to apply the attribute change run in the tools menu. The infoobject does not show up in the list???
Has anyone else run into this issue. I have done a search but could not find anything that answered my question.
Thank you!
Caroline

Hi Caroline,
If the hierarchies and attributes of characteristics that belong to an InfoCube have been changed, you have to make structural changes to the aggregates to modify the data accordingly.
In this task, you can perform the attribute change run ad hoc.
http://help.sap.com/saphelp_nw70/helpdata/en/80/1a67ece07211d2acb80000e829fbfe/content.htm
After each full load of master data, if you want to run attribute change run for an object eventhough the object does not show up in the list. Go to se38 Execute the program RSDDS_AGGREGATES_MAINTAIN. In selection, Info object list - enter the infoobject name then execute it. Will give a pop-up message Hierarchy/attribute change successfully carried out.
Edited by: Priya.D on Mar 11, 2010 6:16 AM

Aggregates in Production System and Change Run Hierarchy

Hi All,
Can anybody tell me, Why should we create Aggregates in Production System nd How?
What is Change Run Hierarchy nd How to perform this?
Reply back me to [email protected]
Regards,
Kiran

Hi Kiran,
Aggregates are nothing but a subset of your Infocube... when a query is executed, it firstl looks for the presence of the data in your aggregates and if found then it fetches the reocrds from there itself.. Else not, it'll search teh entire infocube and then fetch the records which is at a high risk of time consumption and the performance of the Query execution slows down or becomes worse significantly.. for this purpose, you build aggregates.. how do you decide whether you should go for aggregates or not is based on the following criteria...
if the %Data Base time is > 30% and if the KPI ratio (selected to transferred records) is > 10, then you go for the aggregates... you can get these details in the ST03N transaction by choosing Expert mode and selecting BI Workload... you can find all the statistics related to the Query execution starting from the front end time to db time/...
thats all about your aggregates...
Attribute or Hierarchy change run is done so that any changes to your Master data Attributes will have to get effected in terms of your reporting...
say for eg.. ur name is XYZ and loc is in India.. this is how it'll be reflected in your reporting also.. but at a later point in time, if you have changed your location from India to Europe, then for that to be reflected in your reporting, you'll have to perform an Attribute change run for that Characteristic...
Hope it solves your issue..
Regards
Manick

Process chain best practice - attribute change runs

When building attribute change runs into Process Chains I see that there are potentially two main options to consider:
1. One to One mapping. Incorporate a separate attribute change run object type after each InfoObject has been loaded.
2. Many to One mapping. Build the process chain so that one single attribute change run occurs after all the InfoObjects have been loaded.
I would be interested to see how other people have incorporated their attribute loading into Process Chains.
any info appreciated.
Mike

We run the attribute change run twice in our daily process chain, here's our order:
- Load all master data
- Attrib change run
- Load all tx data
- Run ABAP programs that generate master data
- Attrib change run
I doubt there will be much of a performance difference if you do the change run after each master data load, but it makes the process chain a lot easier to read.

Attribute Change Run in BW 3.5

Hi,
In RSA1 ->Monitoring ->Reallignment Run,
When I click on the InfoObject List button, I can see one InfoObject.
1) Does it mean the attribute Change Run is not yet perform for this InfoObject?
2) If yes, then I would just need to select this InfoObject, then click one the Execute button, correct?
3) If not, then why I have that InfoObject in the InfoObject List button?
Please advise, thank you.

Hi,
For your last quesdtion, why the infoobject is there in the list is it could be that the master data was changed/new records in to BW for this infoobject, hence requires the change run to be executed.
Regards.
Srini

Exception 'CX_RSR_X_MESSAGE' was raised when doing the Change Run

Hi ,
Change Run is not happening and it is throwing runtime error "The exception 'CX_RSR_X_MESSAGE' was raised, but it was not caught anywhere along the call hierarchy."
When ever I am trying to "Monitor and Start Terminated Change Runs" the same error is happening.
Below is the error I see in the Job Log
Job started
Step 001 started (program RSDDS_AGGREGATES_MAINTAIN, variant &0000000000054, user ID)
SQL: 06.03.2009 09:55:59
TRUNCATE TABLE "/BI0/0600001776"
SQL-END: 06.03.2009 09:55:59 00:00:00
SQL: 06.03.2009 09:56:01
TRUNCATE TABLE "/BI0/0600001470"
SQL-END: 06.03.2009 09:56:01 00:00:00
ABAP/4 processor: UNCAUGHT_EXCEPTION
Job cancelled
Any help on this would be great
Thanks
Subbu

Hi,
I guess there was nothing to change with tht, the log was simply showing tht ur change run was performing on tht table....
Chk on which object ur running this? whether any load got failed for this...?
Now restart the same run from the EXECUTE button in the window of monitor and start terminated change runs..... i guess it may finish...
rgds,

Master data change run.

dear all,
quick and easy question... after loading 0asset_attr_text, do i need to have an attribute change run? if not why? thanks.

Hi......
Whenever master data attributes or hierarchy is loaded an attribute chnage run need to be performd due to the following reasons:
1. When a master data is changed/updated it gets loaded into the master data table as version "M"(modified). It is only after a attribute chnage run that the master data becomes activated i.e. version "A".....and while activation of master data SID gets generated........SID is very essential for Extended Star Scema...........Otherwise Transaction data load will fail due to SID issue......
2. Master data attributes and hierachies are used in cube aggregates also. So to do update the latest master data attributes values in the aggregtes attribute change run need to be performed.
But it is required for attribute but not for text.......So for 0asset_attr_text attribute change run is not required.......
Hope this helps......
Regards,
Debjani.......
Edited by: Debjani Mukherjee on Oct 18, 2008 12:18 AM
Edited by: Debjani Mukherjee on Oct 18, 2008 12:20 AM
Edited by: Debjani Mukherjee on Oct 18, 2008 12:21 AM

Attr change run cannot preceed Data Load?

Hi, all
I need to make attr change run before loading data, because these active MD should be used in data loading routines. When checking this chain BW shows message " A type "Attribute Change Run" process cannot precede process "Execute InfoPackage" var. ZPAK_E5NXARYHE6BXRST2FD3YZAN7B in the ch".
Why? Is that because change run only activated and chain doesnt wait for change run end and starts next process?
Or I can suppress this warning?

2 Gopikrishna eriki 
Why? I think it isn't for no particular reason.
2AHP
normaly attribute/hierarchy change run is performed after all data loading finished, it should put after the infopackage process.

But here I need to schedule another load after this change run. And I want to use results of this change run in this load.
BTW, when running this chain I have dump on this infopackage load with OPEN_DATASET_NO_AUTHORITY on lines
OPEN DATASET L_PFILENAME FOR INPUT IN TEXT MODE
 ENCODING DEFAULT
 IGNORING CONVERSION ERRORS.
When I schedule this package manually everyting is OK.

Issues with Master Data Change Run after upgrade 7.3.1

We have upgraded to 7.3.1 on both our BW and ECC clients. When we first run out change run in BW it chose to drop and rebuild aggregates
on changes that usually don't cause a drop and rebuild. They usually do a delta.
Has anyone had this issue once upgraded?
We looked at our performance setting in SPRO for aggregates and the settings have not changed.

I loaded data for 0Material, 4 fields are not getting populated....when I checked in R/3 base table and RSA3, I am able to see data for those 4 fields. But in PSA and 0MATERIAL I am not seeing data for those fields.
THose 4 fields are Z fields mapped to Standard fields in MARA table.
As you say you can see the values of these fields in RSA3, We can rule out that the fields arent hidden. Check the mapping on the BI side, do you have all the Zinfoobjects added to the Omaterial and the corresponding mapping of source fields to target fields.
0CUSTOMER_ATTR has some data...I added new field in datasource as well as in BW also. After creating transformation I executed the DTP, it is throwing same error in every data package
"Record filtered in advance as error records with the same key exist".
Load till PSA is Init with data transfer and DTP is delta.
there are some duplicate records in the master data values that are coming in. You can manually change them in PSA and load. And if you are sure the duplicated records can be dropped, you can tick the HANDLE DUPLICATE RECORDS in DTP - update tab

Master data loads vs attr change runs

Hi experts,
I need to load master data daily and want to know the difference between attribute change runs and process chains for master data. Please explain with steps. I know how to create process chains.

Attribute change run is nothing but adjusting the master data after its been loaded from time to time so that it can change or generate or adjust the sid's so that u may not have any problem when loading the trasaction data in to data targets.
Whenever master data attributes or hierarchy is loaded an attribute chnage run need to be performd due to the following reasons:
1. When a master data is changed/updated it gets loaded into the master data table as version "M"(modified). It is only after a attribute chnage run that the master data becomes activated i.e. version "A".
2. Master data attributes and hierachies are used in cube aggregates also. So to do update the latest master data attributes values in the aggregtes attribute change run need to be performed.
Re: Attribute Change Run
Re: Attribute Change Run for Hierarchy

Attribute Change Run VS Master data activation

hello guys
I just want to know whats the difference between 'Attribute Change Run' and Master data Activation...For me,both seem to serve same purpose.......in which scenarios do we use them?
Thanks and Regards
S

Hi S,
Although they seem to be the same there are differences.
Master Data activation.: When you load master data, they are loaded as D or M versions. Check the table as /BI0/P<infoobject tech name> , you will see different versions, if you have not activated your master data yet.
Note : If you are checking for SAP standard objects, drop the 0 eg table for 0MATERIAL would be /BI0/PMATERIAL.
When you activate master data, all D and M versions of records get transferred into A or active versions. So after activation, you should not find anything other than A versions.
ACR: The use of an ACR is two fold. 1st use is that it performs the same action as a master data activation automatically.
The 2nd function, is that it realligns the aggregates for the changed attributes
let me give you an example.
You have an aggregate based on material group which is an aggregate of material.
Consider that you have a material X which initial belonged to group A.
The aggregate would look like this
Material Material Group Keyfigure
X A 100
Now you change the material group of the same material as B
The aggregate would not change automatically....ie it would still be X A 100
To realign the aggregate,you use an ACR. After running an ACR, the aggregate would look like
X B 100
Hope this helps.
Regards.

CRITICAL QUESTION ABOUT ATTRIBUTE CHANGE RUN?

In the master data load process chain there are several hidden small Attribute change run for each and individual loads and at the end there is a final Attribute change run this is causing delay for loads. i think this is been done this way because there are several delta loads going to the same infoobject, so it is doing Attribute change run after each and every load going to the target.
My question is it mandatory to do this Attribute change run after each an every load going to the same data target or can we have only one big Attribute change run after all the master data loads to avoid delay and to improve load performance?
Thanks in advance!

Hi les,
u can run manullay also attribute change run for particular infopbect whichever impacting the peroformance thruogh RS1 goto "Tools" menu and select apply attribute change run and select infoobjects whichever u want to run.
I think it will help u. In this way u can run only relevant infoobjects ultimately it wont efect for system perofmance also
assign the points if it helps.
thanks
sg

Attribut change run

HI,
I've one doubt about ACR.Since we deactivate all the aggregates and activate all the aggregates after attribute change run to speed up attribute change run whenevr we undergo system master data mass update?
Is this the correct way to handle this and another My question is if we are not loading any data in some xy cube but whenever we are doing mass update to master data we still deactivate that xy cubes aggregates and then activate the same.
Now if we are not laoding any data in the cubes then why we need to bother about aggregates of that particluar cube.I think we don't need to touch aggregates of that xy cube because we didn't loaded any new transaction data in it(Note cube already has previous years data ,I'm reffreing new data is not being loaded into cubes but this cube still being used in queries)
is this something related to historical records?
Can anybody clarifies my doubt?

Hi Rubane,
    Its like this, an ACR is used for updating master data changes. I'll try and explain with an example.
You have material in the cube and an attribute material group of material is switched on a navigational attribute.
Now since this is a navigational attribute, you can add it to an aggregate to improve your query performance.
Now a material group can be changed for a material at any given point of time.
say material X earlier had material group A but now has material group B.
In youe aggregate, you have all values corresponding to material X still assigned to material group A
eg aggregate Z
Material Group material key figure
A                      x            100
This is where an ACR comes into picture.
If you run an ACR for material, it activates the master data and then realligns the aggregate with any changes
So now your aggregate looks like this
Material Group material key figure
B                         x            100
So now to answer your question, yes we need to realign the aggregates even if the cubes are not being loaded. This is to take care of any master data changes that occur.
As for your second question, i do agree that its better to have aggregates with a '-' rather than none at all, since these help in the selection. Rather than selecting data from the cube, the query selects the data from the aggregate which is faster.
However the draw back of such aggregates if that they take a long time to fill. and nothing really changes i.e. very few records are summarized. I would suggest in your case, that you look at the aggregates and check the usage field. If you are continously activating and deactivating the aggregates, this really wont give you any idea. However you can still check this field. The more the value, the more times the aggregates is used.
Generally there are aggregates which have no usage at all. These can be deactivated which will save you some time.
Also check for the aggregates which are taking time. You can check the logs for the change run. You will see some values like /BIC/F**** where the ****** indicates the aggregate no. Go to table RSDDAGGRDIR and find the aggrcube field and enter this value. You will find the aggregate. You can then run some checks in RSRV for the cube. You can also try deactivating and then reactivating the aggregates. This will remove any inconsistency in the database for that aggregate which will save you time.
Regards.

Small confusion about aggregates and attribute change run.. plz explain

hi bw experts,
i am having a small confusion regarding the aggregates and attribute change run.
as far as in know if there is any new master data loaded, then we will activate it by context menu on the particular info object and select the option activate master data.
the second one is going to tools--?apply hierarchy/attribute change run option.
my doubt is is the attribute change run related to aggregates is yes then how,.?
appreciated if you plz help me in detail both these concepts and wherther there is any connection between them.
thanks & regards.
vijay..

Hi Vijay sagar,
ATTRIBUTE CHANGE RUN:
1)It's used after you change (add/delete/modify) attribute in the master data. You've to make it in order to have an effect after you modify it.
2)Once the master data has been loaded, the hierarchy/attribute change run is performed. Once this process chain has been ended correctly, master data and texts are available in an active format in SAP BW.
To get it :
1. tcode : RSA1.
2. Tools -> Apply Hierarchy/Attribute Change
3. tap on Info-object list button (checking what master data you've modified before).
4. tap on selection button for type of job
5. Execute.
link(s):
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a67ece07211d2acb80000e829fbfe/frameset.htm
AGGREGATES:
1)Aggregates make it possible to access InfoCube data quickly in reporting. In doing so, aggregates help improve performance. (See Aggregate.)
2)In order to be able to insert aggregates effectively, it is important to find out which aggregates are frequently used or have not been used in a long time.
3)Aggregates contains not only general data but also data that appears in an aggregate after data is filled and rolled up. Reporting in this InfoCube reveals how often data was loaded into an aggregate, how long filling and rolling up took, and whether it took longer to read or write the data.
4)Adding when Rolling Up in Aggregate counts the time required to write the data to the aggregate.
The Records, Read for Aggregate Structure key figure counts the data records that are read for constructing the aggregate.
Refer the following link:
http://help.sap.com/saphelp_nw70/helpdata/en/3d/5fb13cd0500255e10000000a114084/frameset.htm
Assign points if it helps u
Thanks & Regards,
Madhusudhan Reddy.K

Change Run performance

Similar Messages

Maybe you are looking for