Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from Andy Murzyn on Mar 31 at 8:17 PM Hi Eric,
Thank you for the quick response. The issue is that the GL migration is a per system conversion expense done by a consulting company. Since we were required to perform the conversion a number of times in a test environment in order to validate the transports and configuration changes the decision was made to only convert the Production system, then do the system restores over the QA and DEV systems.
Dev system storage is more than adequate to hold the Prod db and multiple clients. Test systems that were upgraded were copies of Production, so data is the same. No value in using them as a source.
I use third party software to export "scrambled" HR data to any system copies I make from Prod.
So while this may not sound like the ideal solution, it appears that there is no issue with deleting the SOFFCONT1 table from the copied client 500, then using that as the source for the two (200 and 230) Dev clients. Once the copies are complete do I need to create the SOFFCONT1 table or will SAP create that when needed? Not having a Content Server, if users try to attach documents while testing the portal, or within any financial transactions, won't they need to be stored somewhere?
Thanks again for the response, I appreciate it,
Andy
| | | ---------------Original Message---------------
From: Eric Griscom
Sent: Monday, March 31, 2014 1:30 PM
Subject: Client Copy excluding SOFFCONT1 Table
Are you OK having PROD DATA in DEV? This is usually not a good
idea. Any severely frowned upon by mgmt and audit.
Is your DEV environment large to hold PROD database?
Why can't you just perform the upgrade in DEV?
Does your QAS system have the SOFFCONT1 also? If not use QAS to refresh
DEV.
Do you have a TRAINING system where the upgrade was performed?
Since you will be copying prod to DEV, all your CTS (transports) history
will need to be preserved. Many OSS notes for this.
1. Perform System Copy of Prod to DEV.
2. Perform all post-copy steps in DEV, i.e CTMS, etc.
a. delete SOFFCONT1/500 table via se12
3. Perform Client Copy in DEV of 500 to 230.
4. Delete Client 500 after successful copy to 230.
5. Perform Client Copy of 230 to 200 (Excluding SOFFCONT1 table.)
(The main reason for the exclusion is the amount of time the copy
takes. Also, I am assuming that any documents contained in SOFFCONT1
would be unnecessary in the Development client.) I would prefer to exclude
the SOFFCONT1 table to the 230 client as well if possible.
.
Regards,
Eric Griscom
IBM Global Business Services |
| Reply to this email to post your response. __.____._ | In the Spotlight Become a blogger at Toolbox.com and share your expertise with the community. Start today.   _.____.__ |
