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 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

Press the Immediate button. select Timetable 2. 6. 2. Highlight the job that was created by SCC7 and press + to modify the job. Locate the transport in the list containing the user exports done before the start of the refresh. Select the Profile field and press to bring up a list of profiles. 4. 5. press to leave *this* screen. 5. Double click on the of the newly refreshed system. press the checkmark button. From the Edit menu. 3. Press the Start condition button. 5. 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. Press +S to save the changes 7. Set the global setting to Modifiable 3. 3. enter the background user *for* that particular system (i. BATCHSAP). Continue to press every once in a *while* to update the status of the job. select Other requests then Add. At the client *import* screen. then highlight the start time of the outstanding assignment and press the Delete Assignment button. Repeat steps 3 through 7 *for* all additional profiles associated with the source system Reconfigure Operation Modes RZ04 1. Job will start immediately once saved. press the Yes button to delete all version of the profile 7. Once all the assignments are deleted. When prompted. When warned that the table is cross-client. Do NOT schedule it to run immediately. 6. Highlight the transport and press the Import request icon .e BGDUSER. (Note: All application servers of the target system must be started) 2. Press to confirm that the *import* will proceed SCC7 1. then of a profile. enter the target client and then press the Import button 7. 8. 3. Select Normal Operation and press the Change button. . We need to modify the job before it can be released. From the Utilities menu. Press the Step button. Press to go back to the main RZ04 screen. 6. select Software Components Modifiable 4. 3. SM37 1. Enter the transport number and press . select Delete. Press +S again to save all the changes to the job. Set the Protection to Protection level 1 5. Do not *continue* until the job is completed sucessfully. Press the System Change Option button. Press +S to save. From the Operation Mode menu. press the No button. 5. Press +S to save the changes 11. 3. 6. 4. Press to refresh the list of jobs 13. 12. Press to go to the Import overview 2. Schedule the job to run in the background. Import Users STMS 1. If the Display Profile Check Log screen is displayed. 6.e. Press +S to save. The transport number should be the same as that of the transport started in STMS 3. then All versions. select Display -> Change 2. Then press the Yes button to add the transport. Press +S to save. 001 or 066) 4. SAPBATCH. SCC4 1. From the Table view menu. press +S to save. 10. 7. If warned about an empty timetable. Press to go back to the main job screen. 9. select Import Profiles then Of Active Servers. If the transport is NOT in the list. Run the Post Client Import Processing 2. In the User box. From the Edit menu. If all the assignments are not deleted. not client 000. press the checkmark button and then press Yes to save the empty timetable. select Namespaces Modifiable 5. Press to refresh the list of transports 4.Set System Change Option SE06 1. then from the Extras menu. Highlight 00:00 in the left hand column and press the Delete Assignment button 4. From the list select one of the profiles associated with the source production system. When prompted to delete the file at the operating system level. Repeat steps 3 through 5 *for* any additional clients Deleting Source System Profiles RZ10 1. 4. Select the RSCLXCOP line and press ++ to modify that step. From the Profile menu. Double click on one of the non-system clients (i. 8.

press the Set button that is beside Internet 6. SM59 1. Select Normal Operation and press the Change button. Press to go back to the main RZ04 screen. ADJUST AS NECESSARY Adjust RFC connections. 24. select Select All 2. select Based on current settings. Press the Continue button to confirm the deletion. select Consistency check 2. Press the Yes button to start the delete. Delete Update Failures SM13 1. 4. Once complete. If ALL the outstanding update requests have a status of ERR. From the Supported Address Types area. Press +S to save. Right click on one of the listed Operation modes and select Delete 9. Press to display the list of outstanding update requests 3. 23. Check all check boxes and enter 0 *for* minimum age 3. 4. From the Supported Address Types area. From the Operation Mode menu. Restrict Outgoing Email and Faxes SCOT 1. then it is safe to delete these requests by pressing to select all records. 14. 10. Check the gateway host and gateway server to make sure it points to the appropriate NON-PRODUCTION system. Press + to delete all the batch input sessions. From the Administration menu select Check Consistency 6. From the Administration menu select Clean-up Spool 2. Double click on the green Fax entry 2. Press to create a *new* operation mode. select Timetable 19. 20. Press the Yes button to save 18. then Delete. Press +S to save. then New Instances. Repeat steps 1 through 5 *for* each additional RFC connection Convert Logical Systems .8. Delete Batch Input Sessions SM35 1. Delete Invalid Background Control Objects SM61 1. Press to create a *new* Instance 15. Enter a name and *short* description *for* the operation mode 13. press the Set button that is beside Fax 3. Reorganize Spool SPAD 1. Press to select the operation mode created above. In the Address area. then Set 16. press twice to get back to the main SPAD screen 5. Double click on the first entry listed 3. SP12 1. Press Press +S and then to save and *return* to the list of RFCs. Press the Yes button to confirm the deletion. Make changes as necessary. Double click on the green SMTP entry 5. 12. Highlight the 00:00 at the top and press 21. From the Edit menu. When the check is complete. In the Address area. Press the Cleanup List button. Highlight the 00:00 at the bottom and press 22. ADJUST AS NECESSARY 4. Set the fields as follows Client: * User: * From data: 01/01/0001 From time: 00:00:00 2. Press the Execute button 4. Press the Delete All button. Press the checkmark button to confirm 4. press the Delete All button. Repeat steps 8 through 9 *for* any additional operation modes 11. Expand the TCP/IP connections section 2. From the TemSe database menu. Press the Assign button. 6. Press the Test Connection button to test the connection 5. then selecting the Update Records menu. Press to *switch* in to change mode 2. 17. From the Settings menu. 3.

Reconfigure DB13 schedule DB13 1. WIIPRD400) 4. SE38 1. 3.e. 4. 8. Press *if* warned that you are changing a function group that doesn't belong to you. Select the Generated Objects option. take the necessary steps to resolve. repeat steps 2 through 10 *for* any additional logical system names that need to be changed. Enter V_T001B in the Table/View box. 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 . 5. Adjust Logical Systems names SALE 1. not client 000. In the Old logical system name box. then Logical Systems 2. … Allow Certains Settings to be modifiable (Refer to Note 356483 *for* more Details) SM54 1. select Display -> Change 2. When warned that the table is cross-client. 2. You can specify the same transport you created above. Change the Recording routine to no. 6. Double click on one of the non-system clients (i.0 4. If there are errors. Press the Test connection button to test. 3. press . recreate the DB13 calendar. Double check the target host and gateway point to the correct server 5. take the necessary steps to resolve the issue.EXE 4. Press +S to save 7. Press to execute 3. Repeat steps 1 through 8 *for* the following objects. Press the Immediate button when asked *for* the schedule 9. or user. press the checkmark button. Create a *new* local transport. Press the checkmark button to confirm that the change is cross client 4. Select option BSI version 7. 9. If the connect is not successful. recording routine. De-select the Test Run and Existence check on *new* names in tables options 6. enter RPUBTCU0 2.WIITRN400) Note: Ignore Error/Warning about duplicate system by clicking on the check mark. Press +S to save 10. Highlight BSI70-US-TAX and press the Change button 3. 3. When job is complete.e. V_T001B_GL V_T093B_01 V_T093B_02 BSI Configuration (R3 HR Systems only) SM59 1. In the New logical system name. From the Program menu.Under no circumstances perform *this* procedure on a Production system BDLS 1. Press +S to save 6. Press to execute 5. Expand Sending and Receiving Systems. Using the print out created before the refresh. Enter any access keys *if* requested 5. BSI should *return* tax calculations. When warned to read the documentation. Use SM37 to monitor the job 11. From the Table view menu.e. Change the program field to sapmntSYSEXERUNTF60SERVER. You are prompted *for* transport. In the Program field. press the checkmark button. Client Configuration SCC4 1. Select one of the production Logical System names that needs be changed (i. 2. enter what that logical system name should be called on *this* newly refreshed system (i. Press the checkmark button when asked to select a spool device 8. select Execute in background 7. Expand TCP/IP Connections 2. Press the Create/Change button. Click on the execute icon beside Define Logical System 3. 001 or 066) 4.

Set the global setting to Not Modifiable 3. properly configured. Click yes on each next screen. Select Standard Installation and click on execute Perform Post Installation Steps. SAP Post Installation Steps Post Installation Steps After Installing R/3 into a new system. 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.  Execute STMS . Post Installation steps make sure that System is ready. Press +S to save. Press the System Change Option button. Below are some standard steps which has to perform immediately after the installation is finished. Tuned and take load of user requests. 2. Press +S to save. Basis has to perform some post Installation steps before handing over to end users for operation. 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. If there is no Domain controller in organization then configure this new system as DC.  Apply SAP license through SLICENSE  Execute SE06 . 6. If anything is reported then trouble shoot those errors. except *for* system standard jobs have been placed on hold (status scheduled). all background jobs.  Login to SAP system using DDIC/000  Execute SICK/ SM28 to check for any Installation error . SE06 1. Transport Management System ( TMS ) Configuration In SAP Step By Step With Snap Shots  Login as SAP*/000  Execute RZ10 -> Utilities -> Import profiles -> Of Active Servers  check the system log in SM21  Check any dumps in ST22 Common ABAP Dumps (ST22) and troubleshooting in SAP . to configure TMS configuration system. Release Background Jobs Currently.

Profile parameters to increase/decrease the number of workprocesses  Define operation mode through RZ04 & SM63 How to setup operation modes in SAP ( RZ04 & SM63 )  Create one or two super users using SU01 with profiles SAP_ALL and SAP_NEW Creating a SAP Account / User Creation in SAP (SU01)  printer configuration (if required ) How to configure Frontend printer in SAP ( SPAD )  Schedule SAP Standard Background jobs through SM36 How to schedule standard jobs in SAP  Configure Web GUI SAP Web Gui Configuration Step By Step With Snap Shots  Create login page message login page message in SAP ( SE61 ) with icon from ( SA38 )  Display your company logo on initial screen of SAP How to Put my own / Company logo in the SAP initial screen ( SMW0 & SM30 )  Disable import all option (this depends on organizations requirement ) How to disable Import All option from STMS in SAP  Give protection to special users How To Protect Special Users In SAP  Stop and Start SAP R/3 for profile parameter to be in effect. Execute SCC4 -> Click on change button -> Confirm the warning and click on new entries to create a new client. Client Creation (SCC4) & Logical system(BD54) in SAP  login to new client to perform a client copy using SAP*/<new client number>/PASS Which are Client Copy Methods In SAP  Set your default client in SAP How to Define Default Client in SAP  Make changes to dialog process and background if you need to change than default one.  Upgrade the kernel to the latest level  Upgrade the SPAM version to latest level .

Execute SE06 . Post Installation steps make sure that System is ready. Add datafiles to corresponding tablespaces to increase the tablespace size and bring the utilization of tablespaces below 80% 9. 4. If there is no Domain controller in organization then configure this new system as DC. PART 1:- 1. 3. Select Standard Installation and click on execute Perform Post Installation Steps. Free space fragmentation of Tablespaces 7. to configure TMS configuration system. If anything is reported then trouble shoot those errors. IF sapdba then check the tablespace utilization by selecting c. List out all the tablespaces filled above 90% 8. Login as SAP*/000 . Basis has to perform some post Installation steps before handing over to end users for operation. Tablespace Adminitration – c. Login to SAP system using DDIC/000 2. Execute sapdba or brtools to check/increase tablespace size if any is >90% 6.Now system is ready to login and work for developers and administrator Post Installation Steps :- After Installing R/3 into a new system. Execute STMS . Execute SICK to check for any Installation error . Below are some standard steps which has to perform immediately after the installation is finished. 5. properly configured. Tuned and take load of user requests. Click yes on each next screen.

Add parameter login/system_client parameter to make new <client_number> as default client to login. Execute SCC4 -> Click on change button -> Confirm the warning and click on new entries to create a new client. 8. Check any dumps in ST22 14. check the system log in SM21 13. 7. login to new client to perform a client copy using SAP*/<new client number>/PASS 2. Once client copy is over . login to new client using SAP* and password of SAP* which was used in client 000 4. Save the profile and activate it. 5. Perform local client copy procedure to copy new client from 000 client. Execute RZ10 -> Select Instance Profile -> check Extended maint -> click on change. 11. Make changes to dialog process and background if you need to change than default one. Login at command prompt using ora<sid> or <SID>adm PART 2:- 1. 3. Create one or two super users using SU01 with profiles SAP_ALL and SAP_NEW . Execute RZ10 -> Utilities -> Import profiles -> Of Active Servers 12. 6.10.

So that transaction accessing becomes faster. 10. else leave it. system configuration as per requirement later. Stop and Start SAP R/3 for profile parameter to be in effect. Upgrade the kernel to the latest level 12. SAP_ABAP. Follow the kernel. SPAM and support pack application methods 15.9. 14. Run SGEN to regenerate the objects . Apply latest support pack to components SAP_BASIS. SAP_APPL and some other components if it is required. Create some developer users if you can. . In this process SAP keeps all the required objects access in SAP buffer. Upgrade the SPAM version to latest level 13. 11. Now system is ready to login and work for developers and administrator 16. 17. Keep on changing the parameters .