|
Post Installation Steps For ECC 5.0 |
Views: 1504
|
Thread Tools | Rate Thread |
#1
|
|||
|
|||
Post Installation Steps For ECC 5.0
Post Installation Steps For ECC 5.0
What are the post installation steps after I have installed the Central Instance and Database instance? 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: 01/01/0001 To: 12/31/9999 Or after event: * 2. Press 3. Highlight the first job in the list and press the 4. Examine the Exec Target field. a. If the box is empty, press b. If the box is not empty, then clear out the contents so the field is blank and press 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 ****on. 3. When prompted Do you want to re-install the CTS?, press the Yes ****on 4. When prompted *for* the Source System of Database Copy?, make sure that the 5. When prompted Change originals from PRD to QUA?, press the Yes ****on 6. When prompted Delete TMS Configuration?, press the Yes ****on 7. When prompted Delete old TMS configuration?, press the Yes ****on 8. When prompted Delete Old Versions of transport routes?, press the No ****on 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 3. From the Overview menu, select Transport Routes 4. From the Configuration menu, select Adjust with Controller 5. Press the Yes ****on 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 3. Double click on the 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 6. Select the transport that was just added to the queue and press 7. In the Target client box, enter the productive client of the newly created system. Press 8. Press the Client Configuration SCC4 1. From the Table view menu, select Display -> Change 2. When warned that the table is cross-client, press the checkmark ****on. 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 6. Repeat steps 4 through 6 *for* any additional clients Set System Change Option SE06 1. Press the System Change Option ****on. 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 Import Users STMS 1. Press 2. Double click on the 3. Press 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 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 ****on 7. Press 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 SM37 1. Set the fields as follows Job name: CLIENTIMPORT* User name: * Job Status: All options checked Fr: 01/01/0001 To: 12/31/9999 Or after event: * 2. Highlight the job that was created by SCC7 and press 3. Press the Step ****on. 4. Select the RSCLXCOP line and press 5. In the User box, enter the background user *for* that particular system (i.e BGDUSER, SAPBATCH, BATCHSAP). 6. Press 7. Press 8. Press the Start condition ****on. 9. Press the Immediate ****on. 10. Press 11. Press 12. Job will start immediately once saved. Press 13. Continue to press SCC4 1. From the Table view menu, select Display -> Change 2. When warned that the table is cross-client, press the checkmark ****on. 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 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 3. Select the Profile field and press 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 ****on to delete all version of the profile 7. When prompted to delete the file at the operating system level, press the No ****on. 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 ****on. 3. Highlight 00:00 in the left hand column and press the Delete Assignment ****on 4. If all the assignments are not deleted, then highlight the start time of the outstanding assignment and press the Delete Assignment ****on. 5. Once all the assignments are deleted, press 6. If warned about an empty timetable, press the checkmark ****on and then press Yes to save the empty timetable. 7. Press 8. Right click on one of the listed Operation modes and select Delete 9. Press the Yes ****on to confirm the deletion. 10. Repeat steps 8 through 9 *for* any additional operation modes 11. Press 12. Enter a name and *short* description *for* the operation mode 13. Press 14. Press 15. From the Settings menu, select Based on current settings, then New Instances, then Set 16. Press 17. Press the Yes ****on to save 18. From the Operation Mode menu, select Timetable 19. Select Normal Operation and press the Change ****on. 20. Highlight the 00:00 at the top and press 21. Highlight the 00:00 at the bottom and press 22. Press the Assign ****on. 23. Press 24. Press Delete Update Failures SM13 1. Set the fields as follows Client: * User: * From data: 01/01/0001 From time: 00:00:00 2. Press 3. If ALL the outstanding update requests have a status of ERR, then it is safe to delete these requests by pressing 4. Press the Continue ****on to confirm the deletion. Delete Batch Input Sessions SM35 1. From the Edit menu, select Select All 2. Press 3. Press the checkmark ****on to confirm 4. Press the Yes ****on 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 ****on 4. Once complete, press 5. From the Administration menu select Check Consistency 6. Press the Delete All ****on. SP12 1. From the TemSe database menu, select Consistency check 2. When the check is complete, press the Delete All ****on. Delete Invalid Background Control Objects SM61 1. Press 2. Press the Cleanup List ****on. Restrict Outgoing Email and Faxes SCOT 1. Double click on the green Fax entry 2. From the Supported Address Types area, press the Set ****on 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 ****on 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 ****on to test the connection 5. Press Press 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 ****on. 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 ****on when asked to select a spool device 8. Press the Immediate ****on when asked *for* the schedule 9. Press 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 ****on 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 ****on. 4. Enter any access keys *if* requested 5. Change the Recording routine to no, or user, recording routine. 6. Press 7. Press 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 ****on 3. Change the program field to \\ 4. Double check the target host and gateway point to the correct server 5. Press 6. Press the Test connection ****on 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 3. Select option BSI version 7.0 4. Press 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 ****on. 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 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 ****on. 2. Set the global setting to Not Modifiable 3. Press Release Background Jobs Currently, all background jobs, except *for* system standard jobs have been placed on hold (status scheduled). |