cancel
Showing results for 
Search instead for 
Did you mean: 

Attribute Change run is running Long

Former Member
0 Kudos

Hi,

Could you Please let me know the some tips and techinqes on how can we reduce the down time for attribte change run?

Thanks in Advance,

Janardhana Rao P

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

If these help -

1. Apply the change run ONCE for all newly loaded master data for a given period.

2. Do not schedule it for the load of every master data object.

3.Try to build basis aggregates (rather large aggregates directly filled out of the InfoCube) without master data references (i.e., without navigational attributes/hierarchies). Then there is no need of adjusting these aggregates when master data changes.

Last but not the least refer SAP Note - 176606.

hope it helps

regards

Vikash

Former Member
0 Kudos

Hi,

if you have aggregates that use navigational attributes or hierarchies, this could be a reason for the change run to take a long time. (or)

the amount of change records that come through everyday. If you're getting a high number of changes everyday then your attribute/change run is going to take a long time

OSS note 176606 helps

"Options to optimize the change run:"

Optimizing aggregates Which aggregates are used and which aggregates are required? See Note 176616 "BW statistics" and 166433 "Options to find aggregates".

Define what is known as base aggregate that is, in addition to the aggregates with attributes define aggregates only consisting of the respective characteristics. This has the advantage that the aggregates with attributes can be filled during the change run from the base aggregates whereas the base aggregates themselves do not need to be filled again. However, this is only useful if the base aggregate is considerably smaller than the InfoCube.

A separation of the different characteristics during the change run only makes sense if it is sufficent that the frequency in which characteristics are activated differs. Process the change run at night with different characteristics several times, this way the total runtime is longer, as now individual aggregates must be filled twice in succession. Nevertheless, consider carefully what degree of actuality the attributes/hierarchies need to have. A separation is not useful if you require different characteristics with different degrees of actuality (for example, one needs to be current on a weekly basis and the other on a monthly basis).

Also take a look at 534630: Parallel processing of Change Run

Go thru this thread...

Hope solved ur Issue

Assign Points if useful

-Shreya

Former Member
0 Kudos

Janardhana

Welcome to SDN

see if this helps

Thnaks

Sat