Question:
Within a Process Chain I have loaded a Master Data InfoObject. I have an Attribute Change Run at the end of the PC for that InfoObject. That PC works.
I now have a second PC with a different Master Data InfoObject. I have an Attribute Change Run at the end of that PC for that InfoObject. That PC works.
Will I have issues if at night, when both of these Process Chains are running and the step within each PC that executes the Attribute Change Run begin at the same time?
Will I get a LOCK?
Will I get an Error?
Will both Attribute Change Runs execute at the same time and active the Master Data?
I say it will work. Other ETL members at the company say you can only run one Attribute Change Run at a time.
Thx
Answer:
I am not sure 100% that two change run can run simultaneously, but I have a tip to solve your argument anyway
instead of having two attributes change run,
make it only one for both master data at the same time by creating a variant mentionning both infoobjects. This is definitely running fine without any problem.
Answer:
I would go with the solution proposed by CHC.
but running two attribute change run at the same time will not give problems as long as they don't activate the same infoobject...
Gr,
M.
Answer:
This question was running in my mind's background...
I think you might face a problem if the two infoobjects have navigational attributes that are contained in the same aggregate.
In this (rather specific) case, I think the second change run would face a problem : it would at least be delayed until the first is finished, or produce a dump.
Never experienced.
Maybe you should ask why the other members are saying it is not possible ?
Because they may base their assumptions on the sole fact that when you do it manually, you have to wait until the first is finished to be able to launch the second
Ch
Answer:
CHC,
My teammates differ in opinion because of the 2 reasons you state:
#1 - when ACR is done manually you have to wait for the first one to finish for the second one to begin.
#2 - we've had some Process Chain "crash" in the Attribute Change Run.
My issue is whether this is a SAP issue or something we just can't do.
I'll look further into your concept of how Aggregates play a role in this - I think that has something to do with the ACR crashing.
My concern (and personality) is I don't like the "blanket" statement that you can't run ACRs simultaenously when in fact you can UNLESS this ?? specific situation occurs.
Later
Answer:
Check these OSS notes 730980 and subsequently 785840
It allows you to specify a wait time when teo attribut change runs gets scheduled at the same time.
regards
phemrajani