Hi
Assumption; since you have two different regions so I am assuming that you have different set of master/transaction data for these regions example locations, customer etc. plus I am not complete aware of dependencies between two regions (which you can check).
This is what you can try (though I have not but on a high level):
- Create two different CIF (integration models) models for all transaction data example EU & NZ (in our example SOs IM). They should not have dependency on regions.
- Now before planning run I am sure you are carrying out CCR activity so that both systems are in sync, as part of your planning run or different steps (but before run).
- Once above is done above means systems are in sync.
- Now we trigger PC of NZ but with below adjustment.
- In this process chain put a job for program RIMODAC2 with "deactivate all versions" before CTM run for NZ integration models (for SO). This will basically lock your transaction data for NZ region (so no more transfer of SO to APO for NZ region) as IM is no more active but both systems were in sync for CTM. Where as EU integration model is active for SOs (GATP) which doesn't have a dependency.
- Now CTM is getting executed and simultaneously you can do GATP for EU as IM is available.
- When CTM is finished trigger another job for RIMODAC2 with "Activate with newest version" (could be you have to put for RIMODGEN also for newest version)
- Thereafter do the CCR to bring back both systems into sync.
- If above works, same way you can do vice-verse for EU region.
Of course above approach is not per best practice etc. but if it works then why not to try and use it. Share your results so that we also get an understanding whether it worked or there is/are some drawback(s).
Regards
Rahul