Embed Size (px)
Citation preview
ECC 6.0 sr2 ides can be restored from vmware image within 1 hour. I have installed SAP ECC 6.0 SR2 in my
computer using vmware workstation. The .vmdk file will be created while installing creating virtual machine in
vmware software. We can copy .vmdk file to any computer or laptop to restore ecc 6.0 sr2 ides within 5 minutes.
You have to use this ECC 6.0 SR2 installation for educational purpose only. You should not use installation for any
commercial purpose. You have to buy the original software from SAP AG to use in a production environment.
Any body can install this software on their computer or laptop in one hour by following simple installation
procedure. I will provide all required tools to restore the software. You can start practice after completion of
restoring. You may need to have your mother board drivers to install some of the automatically not installed
drivers.
To install this software, you should have minimum of 500GB Hard Disk and 2GB RAM. I recommend to use 4 GB
RAM for better working experience. You should have minimum dual core processor. I will help you online while
restoring on your computer or laptop.
Please contact me for further clarification. You can also leave comments about this article here. I can send this file
through courier or post by copying on a 500GB portable hard disk.
I have installed IDES SAP ECC 6.0 SR3 successfully last night on my AMD 64 bit machine with 5 GB RAM and 500 GB
Hard Disk Drive. It took approximately 12 hours to finish the installation. I have done the following steps to
complete the successful installation.
I have installed 64 bit Windows server enterprise operating system
I have made 500 GB Hard Disk into 3 partitions. The partition sizing details are as follows…
C: 50GB – 5.76GB filled
D: 300GB – 285GB filled with data
E: Remaining – 55GB software size
I chose ‘sapdev’ as computer name (Host Name) while installation. You can choose any computer name, but
you need solman key for the selected hostname
I have installed Microsoft Loopback adapter and configured static IP address. Loopback adapter can be avoided
if your computer on network with a network IP.
I have set pagefile as 25000 MB – 30000 MB in D drive. This page file can be assigned in many drives instead of
one.
I have copied complete IDES SAP ECC 6.0 SR3 software dump to my E drive
I have installed j2sdk1.4.2_12 and configured JAVA HOME and did path setting
I have installed Oracle for 64bit machine
I ran Installation master
I have chosen proper paths for Export DVDs, Kernel, oracle client and given values like SAP SID and Oracle SID
as and when installation master insisted to enter values
I have entered solution manager key
I have seen the completion screen of Central services instance screen and closed. This step took 10 hours time.
I have Installed presentation server (GUI)
I have added New item SAP Logon pad with parameters of SAP system
I haved logged into the SAP system using client 001, user name and password
I think the installation of SAP ECC 6.0 SR3 IDES is very simple for me because i did it many times. I took all the
screen shots while doing above installation. Please write a mail to get them at nominal charges. I will also
do remote installations and give support for online servers. Please get back to me for the support prices. I can also
do this installation in a cloud environment for temporary or long term purpose. I do give freelance support on
official sap software implementations. I can help the people who wants to practice sap modules on their laptops
using vmware without loosing host operating system.
Please ask any questions or doubts here only as comments to this article. This information will be helpful for other
readers of this blog.
Step-by-step instructionsRelease 4.7 or earlier
1. Take a full DB2 backup of the source system. The backup can be online or offline. To obtain an offline backup, do the following:
a. Shut down the SAP system.b. Check that no applications are connected to the database. Do this by entering the
command:db2 list applicationsThis command must return with: No data was returned by the database system monitor.
c. Stop the DB2 instance by entering the command:db2stop
d. Run the backup:db2 backup db <SID> to <backup directory>You should include the logs in the backup. This happens by default as of DB2 Version 8.2 and 9.5. Refer to the documentation for the backup database command in the information center for your version of DB2 (see theResources section for a link).
2. If your target SAP system is 4.6x or earlier, follow these steps:a. Follow the installation instructions in the SAP R/3 Homogeneous System
Copy document provided by SAP. (Instead of CENTRDB.R3S or DATABASE.R3S, use the templates CEDBR3CP.R3S for a central and database server, or DBR3CP.R3S for a database server.)For example:./R3SETUP -f CEDBR3CP.R3SThe installation assistant will ask questions that you must answer according to your system's configuration. For guidelines on how to answer these questions, see R/3 Installation on UNIX: IBM DB2 Universal Database for UNIX and Windows.
b. When R3SETUP stops at step EXITR3COPY_IND_DB6, run the redirected restore using one of the methods specified in the following section.
c. Complete the installation as described in the SAP installation guide.3. If your target SAP system is 4.70, follow these steps:
a. Install the central instance as described in SAP R/3 Enterprise 4.70 Installation on UNIX: DB2 Universal Database for UNIX and Windows.Important: Your target system must have the same SID as the source system.
b. Before installing the database instance, follow the instructions in OSS Note 564720 to modify the control.xmlfile.
c. Run the installation for the database instance by answering the questions as described in the guide until it stops before creating the database.
d. Run the redirected restore using one of the methods specified in the following section.
e. Complete the installation as described in the SAP installation guide.4. After the installation is complete, perform the following steps:
a. Report loads in an SAP system are OS-dependent; you must delete these loads to complete the System Copy. The system will automatically re-create them at first access. To delete the report loads, enter the following commands from the operating system using the DB2 command line processor (CLP):
For 4.6x or earlier:db2 "delete from sapr3.d010l" db2 "delete from sapr3.d010q" db2 "delete from sapr3.d010y" db2 "delete from sapr3.d010linf"
For 4.70:
db2 "import from /dev/null of del replace into <schema_name>.repoload"
b. The DB2 event monitors keep information on owners and permissions, which are
kept in the database system catalog. To avoid having the event monitors connect to the owner of the source system (rendering them unusable in the target system), drop and recreate them with the instance owner of the target system (follow the instructions in OSS note 95282).
Releases based on NetWeaver 7.0(2004s) or higherOn the Source System:
1. Take a full db2 offline or online backup of the source system as explained above. You should include the logs in the backup image, which is the default behavior as of DB2 Version 8.2 and 9.5. You need the logs because a rollforward is required following the restore on the target system.
2. Optionally, you can create the export directory structure with labels, and you can archive SDM and application specific file system content. You can use SAPinst to perform this task. From the SAP Installation Master welcome screen, select:<System Release> --> Software Life-Cycle Options --> System Copy --> IBM DB2 for Linux, Unix, and Windows -->Source System Export --> <System Variant> --> <Technical Stack> --> Export PreparationBy providing an export location, all the labels and directory structures will be created in that location and these files can be used in the target system.
1. In a Java® or a double stack system (ABAP+Java), you need to run a separate export for the Java engine to archive SDM and application specific contents. For more information about this step and the previous step, please review the SAP system copy guide for your release.
On the Target System:1. Run SAPinst and from the SAP Installation Master welcome screen, select:
<System Release> --> Software Life-Cycle Options --> System Copy --> IBM DB2 for Linux, Unix, and Windows -->Target System Installation --> <System Variant> --> <Technical Stack>
2. Follow the normal installation procedure. When asked for a SID, either select the same SID as the source system, or a new SID.
3. On the database specific screen, select Homogeneous System Copy (Database copy method)
3. In a Java® or a double stack system (ABAP+Java), you need to run a separate export for the Java engine to archive SDM and application specific contents. For more information about this step and the previous step, please review the SAP system copy guide for your release.
On the Target System:1. Run SAPinst and from the SAP Installation Master welcome screen, select:
<System Release> --> Software Life-Cycle Options --> System Copy --> IBM DB2 for Linux, Unix, and Windows -->Target System Installation --> <System Variant> --> <Technical Stack>
2. Follow the normal installation procedure. When asked for a SID, either select the same SID as the source system, or a new SID.
3. On the database specific screen, select Homogeneous System Copy (Database copy method)
4. Continue with the installation procedure. Enter the database ID, the database ports, and the connect user. Remember that the connect user must be identical to the source system, even if the SID is different.
5. If you are installing a double stack system, you will be asked to enter the location of the Java export, as well as the username and password of the Java administrator. The information
you enter must match the source system, but you can change it after the system copy.
6. After you enter all the required parameters, the install continues up to the step where the restore is
required.
7. When the restore is required, you will see a Message Box pop-up as shown in the figure below. Select Cancel to abort the installation and run the database restore. Alternatively, you can leave the Message Box pop-up open, complete the restore from a separate window, and select OK when the restore is
complete.
8. If you made the selection in the previous step to abort the installation, you see another Message Box. Select Stop to confirm that you want to stop the installation and exit SAPinst.
9. Run the redirected restore using one of the methods specified in the following section.10. Restart SAPinst and continue the installation as described in the SAP installation guide for
your release.11. if you changed the SID, you need to enter the following command to update the
LOGARCHMETH1 database configuration parameter to point to the new SID:db2 update database configuration for <NEW_SID> using LOGARCHMETH1 /db2/<NEW_SID>/log_archive
Redirected Restore methodsThere are three different methods you can use to restore the database:
Generate a script using the SAP brdb6brt tool.From the source system, invoke the tool by issuing the following command:brdb6brt -s <SID> -bm RETRIEVE -user <instance_owner> -using <password>
For example:brdb6brt -s LR1 -bm RETRIEVE -user db2lr1 -using PASS123
The tool generates a script in the form SID_NODE000X.src. The tool also creates a file named SID_NODE000X.brp that includes a log of the steps performed. You can use this file to trace errors if they occur.Modify the generated script to fit the specifications of the target system. You can change the SID, storage paths, location of the log directory, etc. (note that if you are using automatic storage, there is no need to set container paths). After making your modifications, run the script from the CLP using the command:db2 -tvf <SID>_NODE0000.scr
The Download section at the end of this article contains a link to a sample redirected restore script.
You can also use the brdb6brt tool to create a backup and generate the restore script in one step. For more information on the script or on the brdb6brt tool, refer to the SAP DB6 Database Administration Guide.
Generate a script using DB2's redirected restore.You can invoke the restore utility through the DB2 command line processor (CLP) or the db2Restore application programming interface (API). To run it from the CLP, issue the following command on the target system: db2 restore db <SID> from <location> taken at <timestamp> redirect generate script <script>.clp
For example: db2 restore db LR1 from /backup/LR1 taken at 20090804090733 redirect generate script LR1restore.clp
Modify the generated script to fit the specifications of the target system. You can change the SID, storage paths, location of the log directory, etc. (note that if you are using automatic storage, there is no need to set container paths). After making your modifications, run the script from the CLP using the command: db2 -tvf LR1restore.clp
Alternatively, you can use the CLP to manually issue the redirected restore command and set the container paths (note that if you are using automatic storage, there is no need to set the container paths).For example:db2 restore database LR1 from /mnt/LR1backup taken at 20090914135805 redirectdb2 restore database LR1 continue
Perform a rollforwardUpon completion of the restore, you must perform a rollforward on the database.For example:db2 rollforward db LR1 to end of logs
If there are no logs available or if there is no need to rollforward, you can issue the command with the stop option.For example:db2 rollforward db LR1 stop
Alternatively, you can add the rollforward command to the generated redirected restore script described previously.
Convert your system to automatic storage using DB2 9.7 Redirected RestoreAutomatic storage is a feature that allows DB2 to control database growth without having to preset any specific sizes for the database or the tablespace containers. This results in less user interference and fewer interruptions due to space constraints during normal workload.With releases of DB2 prior to 9.7 you could only enable automatic storage during database creation (this is the default behavior starting with DB2 Version 9.1). With DB2 9.7 you can also convert your database and tablespaces to use automatic storage after database creation.You can use the system copy method to convert your database to automatic storage on the same system, or you can combine a system copy with a conversion to auto storage in one step by doing the following:On the Source System:
1. Issue the following command to enable automatic storage at the database level:db2 ALTER DATABASE <dbname> ADD STORAGE ON <path1> [<path2>,...,<pathn>]
For example:db2 ALTER DATABASE LR1 ADD STORAGE ON ’/db2/LR1/sapdata1’,’/db2/LR1/sapdata2’, ’/db2/LR1/sapdata3’, ’/db2/LR1/sapdata4’
2. Backup the database using the backup command as explained previously.On the Target System:
1. Enable automatic storage at the tablespace level during the restore by updating the redirected restore script or by running the restore at the command line as explained previously. Set the containers to use auto storage as follows:db2 set tablespace containers for <tablespace_id1> using automatic storage;db2 set tablespace containers for <tablespace_id2> using automatic storage;...
Note that the tablespace ID can be retrieved from the tablespace snapshot. It is also included in the generated redirected restore script.For example:db2 get snapshot for tablespaces on <db_name> |grep ”Tablespace ID”
2. After the database has been fully converted to automatic storage, you should make a backup of it.
ConclusionBy providing step-by-step instructions and recommendations, this article helps you with your task of performing Heterogeneous system copies using the redirected restore method available in DB2.
DisclaimerThis article contains sample code. IBM grants you ("Licensee") a non-exclusive, royalty free, license to use this sample code. However, the sample code is provided as-is and without any warranties, whether EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT. IBM AND ITS LICENSORS SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE THAT RESULT FROM YOUR USE OF THE SOFTWARE. IN NO EVENT WILL IBM OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF IBM HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
DownloadName Size Download method
brdb6brt.out 40 KB HTTP
Information about download methods
ResourcesLearn
DB2 Version 8.5 information center .
DB2 Version 9.1 information center .
DB2 Version 9.7 information center .
Get products and technologies Download DB2 Express-C 9.7, a no-charge version of DB2 Express database server for the
community.
Download a free trial version of DB2 9.7 for Linux, UNIX, and Windows.
Discuss Participate in the discussion forum .
Check out My developerWorks blogs and get involved in the My developerWorks community.
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 Reconfiguration1. 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: 01/01/0001 To: 12/31/9999 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 00:00 in the left hand column and press the Delete Assignment button 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 00:00 at the top and press 21. Highlight the 00:00 at the bottom and press 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: 01/01/0001 From time: 00:00:00 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).
