SAP "logical system name" change in SCC4 when refreshing a sy stem
We are at 4.5B (HP level 35) and just refreshed our QA system from PRD. The last step for this process was to change the logical system name. To accomplish this, I used transaction BDLS.
PREPARATIONS and EXECUTION: --------------------------- 1. Ensured that no activity was occurring on the system when this was processing -(TP 'LOCKSYS QAS') 2. Addressed other prelim. activities defined in the online help. 2. Verified the new logical system didn't currently exist in the system (ours had been, then I reassigned the old logsysname and delete the new logsysname from table TBDLS (via SPRO)). 3. To further complicate matters, we had documents defined under both logsysnames. 4. I ran BDLS and continued past the warnings that some table entries already existed for the new logsysname.
RESULTS: -------- After all the extra complications, everything went smooth. The program took approximately 1:45 to complete (our QAS DB is approximately 240 GB, with MM, FI, SD, and some PP installed).
I have since had our configurers test the system to see: 1. Old documents created prior to the copy 2. New documents created after the copy 3. New documents created after the logsysname 4. Reports that showed all three (above) together
There are no problems with any of these documents. In addition, we were having problems with our backorder reporting prior to the logsysname change. After the change, all backorders are being reported correctly.
CONCLUSION: ----------- At this point, I would highly recommend continuing to use the DB copy procedures to refresh your TST/QAS environments. In addition, I would recommend changing the logical system name after the copy using BDLS (and supporting documentation).
I will update the list if any other problems are found.
Regards, Mike D. Martin SAP Basis Administrator SOLA Optical, USA 707-763-9911 x6106 mmartinZs...
-----Original Message----- From: Betsy Strebe [mailto:bstrebeZs...] Sent: Wednesday, February 07, 2001 8:12 AM To: JIM DOLL Cc: sap400Zm... Subject: Re: SAP "logical system name" change in SCC4 when refreshing a system
Logical systems are one of the main reasons I started doing remote client copies after moving to 4.6B. We didn't even define them in our 3.1H systems so we could get away with the restore approach (I assume this is what you mean by a copying PRD to TST) . In 4.6B they are required and my (little) understanding of these things is that now the logical system is scattered throughout the db particularly in FI, and shouldn't be messed with.
I know, remote client copies churn and bubble, moan and groan and take forever, but basically when they are done there is little to worry about.
Not much help with your current problem, I know, just my 2-cents - AGAIN!
good luck, Betsy
JIM DOLL <JDOLLZp...> on 02/06/2001 01:59:00 PM
Subject: SAP "logical system name" change in SCC4 when refreshing a system
We're on 3.1H. We've seen this on a 4.6C copy, but potentially it could occur on 3.1H as well:
When we copy PRD to TST, or to a 4.6C TST system, we always change the "logical system name" on SCC4 from PRD010 to TST010 or Q46010. My understanding is that the logical system name is a type of identifier of the SAP system to an external interface.
I was recently contacted by our FI config person, who said that he couldn't do a reversal of a document: he received "F5A135: Reversal of accounting document not possible" on our copy of PRD. But if he looked on the system, the document existed.
We eventually were given notes 317541 and 28958, indicating that our problem was caused by changing the logical system name. The 28958 note indicates that the solution is to run utility programs to change the logical system name in several files.
I thought that I'd poll the group: - do you change the logical file when you copy a system? - if not, have you ever had troubles with external systems? - if so, do you run such utility programs to clean up such errors?
Jim Doll, Perrigo
[Non-text portions of this message have been removed]