Question:
Hello.
I have a problem with my process chain, I hope you can give me a hint how to resolve it.
I have the main process chain containing local process chain. Local process chain contains InfoPackages to load attributes and texts of masterdata objects. When I try to check or activate this local process chain, I get the message that it is necessary to add the attribute change run at the end of the chain. Here is the problem: We want to add one common attribute change run at the end of main process (meta-chain), because we need to have only one activation (attribute change run).
Do you have any idea how to get rid off this problem?
Thank you in advance.
Arelis.
Answer:
As far as i know, this is ony a (standard) warning and you just have to confirm it to get past it. So don't worry about it and add the common process at the end of the main chain...
Answer:
Good morning
Funny you just raised this ? on attrib. change run and meta/process chains. I was just going to post a ? on that topic.
Currently when using attrib chg run through process chain, I am having to add each object one by one in the attrib chg run. This is not good for me since I am loading a lot of attributes.
My question is how to create one global attrib chg run (like in rsa1)? rather than objects one by one?
Thanks,
Kathy
Answer:
Hello Kathy,
You can do the attribute change run for all attributes by leaving object type and object type and object name blank in the variant of your change run process.
Regards
Orchard
Answer:
Good morning Orchard
Thanks for writing and for the tip. That is very helpful. I will test it and check the last date of attrib change run after the process chain has run...
Leaving object type and object name blank in the variant of your change run process? That was kind of misleading to me and sounds almsot too good to be true... It must work like variable entries e.g. blank = ALL
My only question is the logic SAP has behind having the ability to enter one object and object type at a time. Why would somebody bother taking the time to enter these objects one by one and running an attribute change run for only some objects? When they could just do it once and be done. Attrib change run are not that time consuming and doin run for all attributes shoudl not be a performance issue.
Am I missing something?
Thanks,
C
Answer:
My only question is the logic SAP has behind having the ability to enter one object and object type at a time. Why would somebody bother taking the time to enter these objects one by one and running an attribute change run for only some objects? When they could just do it once and be done. Attrib change run are not that time consuming and doin run for all attributes shoudl not be a performance issue.
A possibility I can think of is when your system includes substantial numbers of aggregates. One of the features of the attribute change run is that it causes the adjustment of aggregates that contain changed master data.
So for example if you had a number of aggregates which aggregated cubes by various navigational attribute of 0MATERIAL then it is possible that when the change run is applied to 0MATERIAL the adjustment of these aggregates would take a long time. This long time may not be acceptable in your normal overnight loading schedule as it would delay transactional loads that did not use 0MATERIAL. By separating your master data change run into sections you could possibly delay the 0MATERIAL change run to after these loads.
I hope I make myself clear.
Regards
Orchard