Hierachy attribute change runs - Variant ignored; not used

[Former Member]

We currently run 2 change runs a day. North American info objects are loaded at 5:30 with a change run at the end.It has a wide open report variant of *.

Once that process is finished, we load EMEA master data and run another change run job with a wide open report variant of *.

For over 2 years this has been working correctly, then we changed the first job over to a process chain. The second job is still a manually schedule job in SM37 calling RSDDS_AGGREGATES_MAINTAIN program.

ever since we changed over to a process chain, sproadically on some days the first job does not activate/realign ALL of the objects in the list that were just loaded?? When the second job comes along, however it still picks them up.

This doesn't happen everynight and we are puzzled as to what causes the job to only pick up some of the MD objects that are ready to be realigned?

Thanks, Peggy

[Former Member]

Could you elaborate on the variant used in the process "Attribute change run" in your process chain. Please check if your variant includes all the MD infor objects that are ready to be re-aligned?

[Former Member]

The variant we use in the process chain is the Object type = Report variant = Z_ALL. This variant contains no infoobjects. This runs for ANY/ALL info object that a change is ready. At least that is the way it works some nights! In the past as a scheduled job it worked fine. Same report variant was converted over to a process chain.

Thanks.

[Former Member]

Peggy,

How do you have the process variant in the chain configured? Do you have each infoobject that is loaded assigned in the attribute change run variant? Or are you running the change run as an abap variant running RSDDS_AGGREGATES_MAINTAIN with your variant?

If you would like, send me a screen shot of your process chain and I will see what you are talking about easier...

chandjian@sylack.com

Craig