Demantra clone with ASCP and EBS
We are using EBS-ASCP-Demantra. Issue that we have is after we clone environments from production (all 3 at the same time) we are unable to publish forecast from Dematra to ASCP (in test environments).
We had Sev-1 SR open with oracle support and what they are saying unless you name all envrionment same as production we would not be able to leverage clone data from production (in demantra) to publish forecast after making forecast overrides.
I am sure lot of organization clones test environment periodically and it's had to beleive that we have to name environment (instance name) as as production. Can somebody share post clone steps for demantra to solve this issue. We have performed following