For partners that build or integrate commercially available applications and service solutions with the Oracle Cloud Platform
For partners that provide implementation or managed services around Oracle Cloud Applications
Hello Gurus!
We are all quite familiar with environment refreshes and cloning activities. When a PROD instance is copied over to a DEV/TEST instance, certain tasks must be completed to ensure that this recently cloned environment truly remains for support activities and does not behave like PROD.
Examples of such tasks are:
Therefore, I was wondering if there is a documented Oracle List of these activities for all modules that exists which can be leveraged or is it all "we learned it the hard way" and everyone has a task here and there that they are aware of.
Let me know, thanks!
Regards,
Felix
Hi Felix, there's this document:
In addition to this I schedule any maintenance processes. I'd be curious to see what checklists other people have. Thanks, Wendy
This is excellent! Thank you very much Wendy! I'm just surprised there isn't a full list that covers every module including SCM and HCM.
We'll see what other people and keep the discussion going!
Hi all, just a general question here.
I thought that, at a minimum, Oracle disables external email notifications and interfaces after a P2T is complete. That has been my experience, at least; it seems to be a part of the cloning script. I have to specifically re-enable these things in Test or Dev after P2T
Has anyone experienced something different?
Hey Leaman!
If that is the case for you then that is great but it isn't for us :(
After every clone, we have had to navigate to BPM and Disable the Notifications. Break some data models manually to make sure transactions don't get emailed, etc.
I have two SRs raised. One for a full task list and I have received a response where they don't have it consolidated and we need to open separate SRs for each stream (HCM, ERP, SCM) to obtain documentation for them.
The other is to have the entire SMTP server disabled after a cloning takes place. Apparently, they do not do this so they are asking development if it can be done ad-hoc.
"Oracle Applications Cloud Service Definition - Environment Refresh (Doc ID 2015788.1) specifically the PDF for Enterprise."
Regards,
Felix
In my experience, external email notifications are automatically disabled after P2T. I believe the external bank connections are not. Wendy
Thanks for confirming Wendy! I'll follow-up internally to determine if they are truly disabled when a cloning takes place. I agree for bank connections. All we need to do is disable the Transmission Configurations and end-date the Payment Systems. Not a difficult task once it is part of our to-do list. What concerns me is the Email Communications for AR Transactions, Remittance Advice for AP, Purchase Orders for PO. So far, we've found seeded configurations for PO but not AR and AP. I have a separate SR with Oracle to determine if there is a way to completely disable the SMTP server as a whole so we do not have tests which accidentally communicate to actual customers/suppliers.
Hey Leaman!
If that is the case for you then that is great but it isn't for us :(
After every clone, we have had to navigate to BPM and Disable the Notifications. Break some data models manually to make sure transactions don't get emailed, etc.
I have two SRs raised. One for a full task list and I have received a response where they don't have it consolidated and we need to open separate SRs for each stream (HCM, ERP, SCM) to obtain documentation for them.
The other is to have the entire SMTP server disabled after a cloning takes place. Apparently, they do not do this so they are asking development if it can be done ad-hoc.
"Oracle Applications Cloud Service Definition - Environment Refresh (Doc ID 2015788.1) specifically the PDF for Enterprise."
Regards,
Felix