Initial Consistency Check
SM28
1. Logon to the newly refreshed SAP system and run transaction SM28
2. Ensure that no errors are reported. Otherwise, take the necessary steps to correct the problems.
Edit Batch Jobs
1. Set the fields as follows
Job name: RDDIMPDP*
User name: *
Job Status: Released and Ready checked off, all others unchecked
Fr:
To:
Or after event: *
2. Press to execute the query
3. Highlight the first job in the list and press the ctrl + f11 to change the job.
4. Examine the Exec Target field.
a. If the box is empty, press to exit
b. If the box is not empty, then clear out the contents so the field is blank and press ctrl + s to save
5. Repeat Steps 3 and 4 for each additonal job listed.
Workbench Organizer Reconfiguration
1. Logon on to client 000 of the newly refreshed system with DDIC.
SE06
1. Select the Database Copy or migration option
2. Press the Post-installation Processing button.
3. When prompted Do you want to re-install the CTS?, press the Yes button
4. When prompted *for* the Source System of Database Copy?, make sure that the of the production system is selected. Press the checkmark button to continue.
5. When prompted Change originals from PRD to QUA?, press the Yes button
6. When prompted Delete TMS Configuration?, press the Yes button
7. When prompted Delete old TMS configuration?, press the Yes button
8. When prompted Delete Old Versions of transport routes?, press the No button
TMS Configuration
1. Logon on to client 000 of the newly refreshed system.
STMS
1. Upon starting STMS, a windows with the title TMS: Include System in Transport Domain should be displayed
2. The information on *this* screen is automatically filled out from information provided during the SAP installation and should be correct. If it correct, then enter a description *for* the system and press +S to save. Otherwise, press the Other configuration button and manually configure.
3. From the Overview menu, select Transport Routes
4. From the Configuration menu, select Adjust with Controller
5. Press the Yes button when prompted *if* you want copy the transport routes from the controller.
Import Printers
1. Logon on to the production client of the newly refreshed system.
STMS
2. Press to go to the *import* Overview.
3. Double click on the of the newly refresh system
4. From the Extras menu select Other Requests, then Add.
5. In the Transp. Request box, enter the transport number containing the printer definitions that was exported. Press to save.
6. Select the transport that was just added to the queue and press + to start the import.
7. In the Target client box, enter the productive client of the newly created system. Press to save.
8. Press the button to start the transport.
Client Configuration
SCC4
1. From the Table view menu, select Display -> Change
2. When warned that the table is cross-client, press the checkmark button.
3. Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
4. Define client as follows:
Client role: Test
Changes and transports *for* client-specific object: Changes without automatic recording
Client-independent object changes: Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
5. Press +S to save.
6. Repeat steps 4 through 6 *for* any additional clients
Set System Change Option
SE06
1. Press the System Change Option button.
2. Set the global setting to Modifiable
3. From the Edit menu, select Software Components Modifiable
4. From the Edit menu, select Namespaces Modifiable
5. Press +S to save.
Import Users
STMS
1. Press to go to the Import overview
2. Double click on the of the newly refreshed system.
3. Press to refresh the list of transports
4. Locate the transport in the list containing the user exports done before the start of the refresh.
If the transport is NOT in the list, then from the Extras menu, select Other requests then Add. Enter the transport number and press . Then press the Yes button to add the transport.
5. Highlight the transport and press the Import request icon .
6. At the client *import* screen, enter the target client and then press the Import button
7. Press to confirm that the *import* will proceed
SCC7
1. Run the Post Client Import Processing
2. The transport number should be the same as that of the transport started in STMS
3. Schedule the job to run in the background. Do NOT schedule it to run immediately. We need to modify the job before it can be released.
4. Press +S to save.
SM37
1. Set the fields as follows
Job name: CLIENTIMPORT*
User name: *
Job Status: All options checked
Fr:
To:
Or after event: *
2. Highlight the job that was created by SCC7 and press + to modify the job.
3. Press the Step button.
4. Select the RSCLXCOP line and press ++ to modify that step.
5. In the User box, enter the background user *for* that particular system (i.e BGDUSER, SAPBATCH, BATCHSAP).
6. Press +S to save the changes
7. Press to go back to the main job screen.
8. Press the Start condition button.
9. Press the Immediate button.
10. Press +S to save the changes
11. Press +S again to save all the changes to the job.
12. Job will start immediately once saved. Press to refresh the list of jobs
13. Continue to press every once in a *while* to update the status of the job. Do not *continue* until the job is completed sucessfully.
SCC4
1. From the Table view menu, select Display -> Change
2. When warned that the table is cross-client, press the checkmark button.
3. Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
4. Set the Protection to Protection level 1
5. Press +S to save.
6. Repeat steps 3 through 5 *for* any additional clients
Deleting Source System Profiles
RZ10
1. From the Utilities menu, select Import Profiles then Of Active Servers.
(Note: All application servers of the target system must be started)
2. If the Display Profile Check Log screen is displayed, press to leave *this* screen.
3. Select the Profile field and press to bring up a list of profiles.
4. From the list select one of the profiles associated with the source production system.
5. From the Profile menu, select Delete, then All versions, then of a profile.
6. When prompted, press the Yes button to delete all version of the profile
7. When prompted to delete the file at the operating system level, press the No button.
8. Repeat steps 3 through 7 *for* all additional profiles associated with the source system
Reconfigure Operation Modes
RZ04
1. From the Operation Mode menu, select Timetable
2. Select Normal Operation and press the Change button.
3. Highlight
4. If all the assignments are not deleted, then highlight the start time of the outstanding assignment and press the Delete Assignment button.
5. Once all the assignments are deleted, press +S to save.
6. If warned about an empty timetable, press the checkmark button and then press Yes to save the empty timetable.
7. Press to go back to the main RZ04 screen.
8. Right click on one of the listed Operation modes and select Delete
9. Press the Yes button to confirm the deletion.
10. Repeat steps 8 through 9 *for* any additional operation modes
11. Press to create a *new* operation mode.
12. Enter a name and *short* description *for* the operation mode
13. Press +S to save.
14. Press to create a *new* Instance
15. From the Settings menu, select Based on current settings, then New Instances, then Set
16. Press to go back to the main RZ04 screen.
17. Press the Yes button to save
18. From the Operation Mode menu, select Timetable
19. Select Normal Operation and press the Change button.
20. Highlight the
21. Highlight the
22. Press the Assign button.
23. Press to select the operation mode created above.
24. Press +S to save.
Delete Update Failures
SM13
1. Set the fields as follows
Client: *
User: *
From data:
From time:
2. Press to display the list of outstanding update requests
3. If ALL the outstanding update requests have a status of ERR, then it is safe to delete these requests by pressing to select all records, then selecting the Update Records menu, then Delete.
4. Press the Continue button to confirm the deletion.
Delete Batch Input Sessions
SM35
1. From the Edit menu, select Select All
2. Press + to delete all the batch input sessions.
3. Press the checkmark button to confirm
4. Press the Yes button to start the delete.
Reorganize Spool
SPAD
1. From the Administration menu select Clean-up Spool
2. Check all check boxes and enter 0 *for* minimum age
3. Press the Execute button
4. Once complete, press twice to get back to the main SPAD screen
5. From the Administration menu select Check Consistency
6. Press the Delete All button.
SP12
1. From the TemSe database menu, select Consistency check
2. When the check is complete, press the Delete All button.
Delete Invalid Background Control Objects
SM61
1. Press to *switch* in to change mode
2. Press the Cleanup List button.
Restrict Outgoing Email and Faxes
SCOT
1. Double click on the green Fax entry
2. From the Supported Address Types area, press the Set button that is beside Fax
3. In the Address area, ADJUST AS NECESSARY
4. Double click on the green SMTP entry
5. From the Supported Address Types area, press the Set button that is beside Internet
6. In the Address area, ADJUST AS NECESSARY
Adjust RFC connections.
SM59
1. Expand the TCP/IP connections section
2. Double click on the first entry listed
3. Check the gateway host and gateway server to make sure it points to the appropriate NON-PRODUCTION system.
Make changes as necessary.
4. Press the Test Connection button to test the connection
5. Press Press +S and then to save and *return* to the list of RFCs.
6. Repeat steps 1 through 5 *for* each additional RFC connection
Convert Logical Systems
Under no circumstances perform *this* procedure on a Production system
BDLS
1. When warned to read the documentation, press the checkmark button.
2. In the Old logical system name box, press .
3. Select one of the production Logical System names that needs be changed (i.e. WIIPRD400)
4. In the New logical system name, enter what that logical system name should be called on *this* newly refreshed system (i.e.WIITRN400) Note: Ignore Error/Warning about duplicate system by clicking on the check mark.
5. De-select the Test Run and Existence check on *new* names in tables options
6. From the Program menu, select Execute in background
7. Press the checkmark button when asked to select a spool device
8. Press the Immediate button when asked *for* the schedule
9. Press +S to save
10. Use SM37 to monitor the job
11. When job is complete, repeat steps 2 through 10 *for* any additional logical system names that need to be changed.
Adjust Logical Systems names
SALE
1. Expand Sending and Receiving Systems, then Logical Systems
2. Click on the execute icon beside Define Logical System
3. Press the checkmark button to confirm that the change is cross client
4. …
Allow Certains Settings to be modifiable
(Refer to Note 356483 *for* more Details)
SM54
1. Enter V_T001B in the Table/View box.
2. Select the Generated Objects option.
3. Press the Create/Change button.
4. Enter any access keys *if* requested
5. Change the Recording routine to no, or user, recording routine.
6. Press +S to save
7. Press *if* warned that you are changing a function group that doesn't belong to you.
8. You are prompted *for* transport. Create a *new* local transport.
9. Repeat steps 1 through 8 *for* the following objects. You can specify the same transport you created above.
V_T001B_GL
V_T093B_01
V_T093B_02
BSI Configuration (R3 HR Systems only)
SM59
1. Expand TCP/IP Connections
2. Highlight BSI70-US-TAX and press the Change button
3. Change the program field to \\\sapmnt\\SYS\EXE\RUN\TF60SERVER.EXE
4. Double check the target host and gateway point to the correct server
5. Press +S to save
6. Press the Test connection button to test. If the connect is not successful, take the necessary steps to resolve the issue.
SE38
1. In the Program field, enter RPUBTCU0
2. Press to execute
3. Select option BSI version 7.0
4. Press to execute
5. BSI should *return* tax calculations. If there are errors, take the necessary steps to resolve.
Reconfigure DB13 schedule
DB13
1. Using the print out created before the refresh, recreate the DB13 calendar.
Client Configuration
SCC4
1. From the Table view menu, select Display -> Change
2. When warned that the table is cross-client, press the checkmark button.
3. Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
4. Define clients as follows depending on client role
Development
Client role: Customizing
Changes and transports *for* client-specific object: Automatic recording of changes
Client-independent object changes: Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
Quality Assurance
Client role: Test
Changes and transports *for* client-specific object: No changes allowed
Client-independent object changes: No Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
Training
Client role: Education
Changes and transports *for* client-specific object: No changes allowed
Client-independent object changes: No Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
Sandbox
Client role: Test
Changes and transports *for* client-specific object: Changes without automatic recording
Client-independent object changes: Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
5. Press +S to save.
6. Repeat steps 4 through 6 *for* any additional clients
Set System Change Option
Skip *this* section of the system is a Development or Sandbox System.
SE06
1. Press the System Change Option button.
2. Set the global setting to Not Modifiable
3. Press +S to save.
Release Background Jobs
Currently, all background jobs, except *for* system standard jobs have been placed on hold (status scheduled).
