• Save
Post installation steps for ecc 5.0
Upcoming SlideShare
Loading in...5
×
 

Post installation steps for ecc 5.0

on

  • 485 views

 

Statistics

Views

Total Views
485
Views on SlideShare
485
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft Word

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Post installation steps for ecc 5.0 Post installation steps for ecc 5.0 Document Transcript

  • What are the post installation steps after I have installed the Central Instance andDatabase instance?Initial Consistency CheckSM281. Logon to the newly refreshed SAP system and run transaction SM282. Ensure that no errors are reported. Otherwise, take the necessary steps to correct theproblems.Edit Batch Jobs1. Set the fields as followsJob name: RDDIMPDP*User name: *Job Status: Released and Ready checked off, all others uncheckedFr: 01/01/0001To: 12/31/9999Or after event: *2. Press <F8> to execute the query3. 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 <F3> to exitb. If the box is not empty, then clear out the contents so the field is blank and press<CTRL>+<S> to save5. Repeat Steps 3 and 4 *for* each additonal job listed.Workbench Organizer Reconfiguration1. Logon on to client 000 of the newly refreshed system with DDIC.SE061. Select the Database Copy or migration option2. Press the Post-installation Processing button.3. When prompted Do you want to re-install the CTS?, press the Yes button4. When prompted *for* the Source System of Database Copy?, make sure that the <SID> ofthe production system is selected. Press the checkmark button to continue.5. When prompted Change originals from PRD to QUA?, press the Yes button6. When prompted Delete TMS Configuration?, press the Yes button7. When prompted Delete old TMS configuration?, press the Yes button8. When prompted Delete Old Versions of transport routes?, press the No buttonTMS Configuration1. Logon on to client 000 of the newly refreshed system.STMS1. Upon starting STMS, a windows with the title TMS: Include System in Transport Domainshould be displayed2. The information on *this* screen is automatically filled out from information provided duringthe SAP installation and should be correct. If it correct, then enter a description *for* the systemand press <CTRL>+S to save. Otherwise, press the Other configuration button and manuallyconfigure.3. From the Overview menu, select Transport Routes4. From the Configuration menu, select Adjust with Controller5. Press the Yes button when prompted *if* you want copy the transport routes from thecontroller.Import Printers1. Logon on to the production client of the newly refreshed system.
  • STMS2. Press <F5> to go to the *import* Overview.3. Double click on the <SID> of the newly refresh system4. From the Extras menu select Other Requests, then Add.5. In the Transp. Request box, enter the transport number containing the printer definitions thatwas exported. Press <Enter> to save.6. Select the transport that was just added to the queue and press <CTRL>+<F11> to start theimport.7. In the Target client box, enter the productive client of the newly created system. Press<Enter> to save.8. Press the <Yes> button to start the transport.Client ConfigurationSCC41. From the Table view menu, select Display -> Change2. 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: TestChanges and transports *for* client-specific object: Changes without automatic recordingClient-independent object changes: Changes to repository and cross-client customizing allowedProtection: Client copier and comparison tool: Protection level 0Restrictions when starting CATT and eCATT: eCATT and CATT allowed5. Press <CTRL>+S to save.6. Repeat steps 4 through 6 *for* any additional clientsSet System Change OptionSE061. Press the System Change Option button.2. Set the global setting to Modifiable3. From the Edit menu, select Software Components Modifiable4. From the Edit menu, select Namespaces Modifiable5. Press <CTRL>+S to save.Import UsersSTMS1. Press <F5> to go to the Import overview2. Double click on the <SID> of the newly refreshed system.3. Press <F5> to refresh the list of transports4. Locate the transport in the list containing the user exports done before the start of therefresh.If the transport is NOT in the list, then from the Extras menu, select Other requests then Add.Enter the transport number and press <Enter>. 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 button7. Press <Enter> to confirm that the *import* will proceedSCC71. Run the Post Client Import Processing2. The transport number should be the same as that of the transport started in STMS3. Schedule the job to run in the background. Do NOT schedule it to run immediately. We needto modify the job before it can be released.4. Press <CTRL>+S to save.SM371. Set the fields as followsJob name: CLIENTIMPORT*User name: *Job Status: All options checkedFr: 01/01/0001
  • To: 12/31/9999Or after event: *2. Highlight the job that was created by SCC7 and press <CTRL>+<F11> to modify the job.3. Press the Step button.4. Select the RSCLXCOP line and press <CTRL>+<SHIFT>+<F7> to modify that step.5. In the User box, enter the background user *for* that particular system (i.e BGDUSER,SAPBATCH, BATCHSAP).6. Press <CTRL>+S to save the changes7. Press <F3> to go back to the main job screen.8. Press the Start condition button.9. Press the Immediate button.10. Press <CTRL>+S to save the changes11. Press <CTRL>+S again to save all the changes to the job.12. Job will start immediately once saved. Press <F8> to refresh the list of jobs13. Continue to press <F8> every once in a *while* to update the status of the job. Do not*continue* until the job is completed sucessfully.SCC41. From the Table view menu, select Display -> Change2. 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 15. Press <CTRL>+S to save.6. Repeat steps 3 through 5 *for* any additional clientsDeleting Source System ProfilesRZ101. 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 <F3> to leave *this* screen.3. Select the Profile field and press <F4> 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 profile7. 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 systemReconfigure Operation ModesRZ041. From the Operation Mode menu, select Timetable2. Select Normal Operation and press the Change button.3. Highlight 00:00 in the left hand column and press the Delete Assignment button4. If all the assignments are not deleted, then highlight the start time of the outstandingassignment and press the Delete Assignment button.5. Once all the assignments are deleted, press <CTRL>+S to save.6. If warned about an empty timetable, press the checkmark button and then press Yes to savethe empty timetable.7. Press <F3> to go back to the main RZ04 screen.8. Right click on one of the listed Operation modes and select Delete9. Press the Yes button to confirm the deletion.10. Repeat steps 8 through 9 *for* any additional operation modes11. Press <F5> to create a *new* operation mode.12. Enter a name and *short* description *for* the operation mode13. Press <CTRL>+S to save.14. Press <F6> to create a *new* Instance15. From the Settings menu, select Based on current settings, then New Instances, then Set16. Press <F3> to go back to the main RZ04 screen.17. Press the Yes button to save18. From the Operation Mode menu, select Timetable19. Select Normal Operation and press the Change button.20. Highlight the 00:00 at the top and press <F2>
  • 21. Highlight the 00:00 at the bottom and press <F2>22. Press the Assign button.23. Press <F4> to select the operation mode created above.24. Press <CTRL>+S to save.Delete Update FailuresSM131. Set the fields as followsClient: *User: *From data: 01/01/0001From time: 00:00:002. Press <Enter> to display the list of outstanding update requests3. If ALL the outstanding update requests have a status of ERR, then it is safe to delete theserequests by pressing <F5> to select all records, then selecting the Update Records menu, thenDelete.4. Press the Continue button to confirm the deletion.Delete Batch Input SessionsSM351. From the Edit menu, select Select All2. Press <Shift>+<F2> to delete all the batch input sessions.3. Press the checkmark button to confirm4. Press the Yes button to start the delete.Reorganize SpoolSPAD1. From the Administration menu select Clean-up Spool2. Check all check boxes and enter 0 *for* minimum age3. Press the Execute button4. Once complete, press <F3> twice to get back to the main SPAD screen5. From the Administration menu select Check Consistency6. Press the Delete All button.SP121. From the TemSe database menu, select Consistency check2. When the check is complete, press the Delete All button.Delete Invalid Background Control ObjectsSM611. Press <F8> to *switch* in to change mode2. Press the Cleanup List button.Restrict Outgoing Email and FaxesSCOT1. Double click on the green Fax entry2. From the Supported Address Types area, press the Set button that is beside Fax3. In the Address area, ADJUST AS NECESSARY4. Double click on the green SMTP entry5. From the Supported Address Types area, press the Set button that is beside Internet6. In the Address area, ADJUST AS NECESSARYAdjust RFC connections.SM591. Expand the TCP/IP connections section2. Double click on the first entry listed3. 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 connection5. Press Press <CTRL>+S and then <F3> to save and *return* to the list of RFCs.6. Repeat steps 1 through 5 *for* each additional RFC connectionConvert Logical SystemsUnder no circumstances perform *this* procedure on a Production systemBDLS1. When warned to read the documentation, press the checkmark button.2. In the Old logical system name box, press <F4>.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 duplicatesystem by clicking on the check mark.5. De-select the Test Run and Existence check on *new* names in tables options6. From the Program menu, select Execute in background7. Press the checkmark button when asked to select a spool device8. Press the Immediate button when asked *for* the schedule9. Press <Ctrl>+S to save10. Use SM37 to monitor the job11. When job is complete, repeat steps 2 through 10 *for* any additional logical system namesthat need to be changed.Adjust Logical Systems namesSALE1. Expand Sending and Receiving Systems, then Logical Systems2. Click on the execute icon beside Define Logical System3. Press the checkmark button to confirm that the change is cross client4. …Allow Certains Settings to be modifiable(Refer to Note 356483 *for* more Details)SM541. 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* requested5. Change the Recording routine to no, or user, recording routine.6. Press <Ctrl>+S to save7. Press <Enter> *if* warned that you are changing a function group that doesnt 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 youcreated above.V_T001B_GLV_T093B_01V_T093B_02BSI Configuration (R3 HR Systems only)SM591. Expand TCP/IP Connections2. Highlight BSI70-US-TAX and press the Change button3. Change the program field to <hostname>sapmnt<SID>SYSEXERUNTF60SERVER.EXE4. Double check the target host and gateway point to the correct server5. Press <CTRL>+S to save6. Press the Test connection button to test. If the connect is not successful, take the necessarysteps to resolve the issue.SE381. In the Program field, enter RPUBTCU0
  • 2. Press <F8> to execute3. Select option BSI version 7.04. Press <F8> to execute5. BSI should *return* tax calculations. If there are errors, take the necessary steps to resolve.Reconfigure DB13 scheduleDB131. Using the print out created before the refresh, recreate the DB13 calendar.Client ConfigurationSCC41. From the Table view menu, select Display -> Change2. 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 roleDevelopmentClient role: CustomizingChanges and transports *for* client-specific object: Automatic recording of changesClient-independent object changes: Changes to repository and cross-client customizing allowedProtection: Client copier and comparison tool: Protection level 0Restrictions when starting CATT and eCATT: eCATT and CATT allowedQuality AssuranceClient role: TestChanges and transports *for* client-specific object: No changes allowedClient-independent object changes: No Changes to repository and cross-client customizing allowedProtection: Client copier and comparison tool: Protection level 0Restrictions when starting CATT and eCATT: eCATT and CATT allowedTrainingClient role: EducationChanges and transports *for* client-specific object: No changes allowedClient-independent object changes: No Changes to repository and cross-client customizing allowedProtection: Client copier and comparison tool: Protection level 0Restrictions when starting CATT and eCATT: eCATT and CATT allowedSandboxClient role: TestChanges and transports *for* client-specific object: Changes without automatic recordingClient-independent object changes: Changes to repository and cross-client customizing allowedProtection: Client copier and comparison tool: Protection level 0Restrictions when starting CATT and eCATT: eCATT and CATT allowed5. Press <CTRL>+S to save.6. Repeat steps 4 through 6 *for* any additional clientsSet System Change OptionSkip *this* section of the system is a Development or Sandbox System.SE061. Press the System Change Option button.2. Set the global setting to Not Modifiable3. Press <CTRL>+S to save.Release Background JobsCurrently, all background jobs, except *for* system standard jobs have been placed on hold (statusscheduled).