SAP

BASIS-Technical Preparation Activities in Business Downtime

by

Technical preparation activities are essential for ensuring that your BASIS systems are ready for business downtime. This blog post discusses some of the most important activities to complete, as well as tips for making the most of your downtime.

Lock All Relevant Users

Relevant users must be locked to avoid accidental logging on to the system and the triggering of processes directly after the import.

Procedure

  1. Access the transaction using the following navigation option:
    Transaction Code SU10
  2. On the User Maintenance: “Mass Changes” Initial Screen, select All users (for example by address data with ‘*’ in the first name).
  3. Mark all users.
  4. Deselect all technical users and all administrator users (especially DDIC).
  5. Choose Transfer in the tool bar.
  6. Lock all users.

Check for Cancelled or Pending Updates

To avoid inconsistencies, all updates should be processed correctly before starting the migration. If there are erroneous update records, check if the updates can be repaired/ processed or if they are not required and can be deleted.

Procedure

  1. Access the transaction using the following navigation option:
    Transaction Code SM13
  2. On the Update Records: Initial Screen, provide an asterisk ‘*’ in the User and Client field.
  3. In the Status section, select ALL.
  4. In the Selection section, set the From Date to 01.01.2000.
  5. Choose Execute.

Check for Erroneous / Old tRFC Queues

It is useful to reduce the data volume before the migration. Especially the tRFC queues can include much data. Mostly, the erroneous data is outdated and can be deleted.

Procedure

  1. Access the transaction using the following navigation option:
    Transaction Code SM58
  2. On the Transactional RFC screen, change the Display period to 01.01.2000 until .
  3. Provide an asterisk ‘*’ in the User Name field.
  4. All other fields are left with an asterisk (default setting).
  5. Choose Execute.

The list should be empty. If there are entries, check them.
If they are obsolete or outdated, they can be reorganized or deleted.

Proceed as follows to reorganize the erroneous or old tRFC queues:

  1. On the screen where the erroneous or old tRFC queues are listed, go to Log File → Reorganize.
  2. Change the Date to 01.01.2000 until <current date>.
  3. Provide an asterisk ‘*’ in the User Name field.
  4. Check all check boxes for which you decided to delete the entries.
  5. Choose Execute.

Check for Unfinished Table Conversion

During the export procedure, tables and data are exported from the database. To avoid the export of old temporary objects and errors due to invalid or partly active objects, perform the following checks.

Procedure

Open/ Cancelled Table Operations

  1. Access the transaction using the following navigation option:
    Transaction Code SE14
  2. On the ABAP Dictionary: Database Utility screen, from the menu, choose DB Requests → Mass Processing.
  3. In the tool bar, choose All Requests.
  4. If there are entries, check and delete them.
  5. Do the same for Terminated, Created with Import and Incremental.

Invalid Temporary Tables

  1. Access the transaction using the following navigation option:
    Transaction Code SE14
  2. On the Access transaction ABAP Dictionary: Database Utility screen, choose Extras → Invalid Temp. Table.
  3. If there are entries, check and delete them.

Empty Delta Queues

If the ERP system is the source of SAP Business Warehouse system(s), we recommend emptying the delta queues to reduce the amount of data for export or import.

Procedure

  1. Access the transaction using the following navigation option:
    Transaction Code RSA7
  2. Check the BW Delta Queue Maintenance screen in the ERP system and/ or BW system.
  3. In case there are entries in the delta queue, execute the respective InfoPackages and upload the data into the BW system until there are no entries in the delta queue.

Adapt the Operation Mode Timetable

Adapt the operation mode timetable to make sure that no switching of operation modes takes place in the target system.

Procedure

  1. Access the transaction using the following navigation option:
    Transaction Code SM63
  2. Select Normal operation (24 hours) and choose Change.
  3. Define one operation mode as an active operation mode for 24 hours.

Suspend All Scheduled Jobs

Before the conversion, all scheduled jobs are suspended to prevent them from starting automatically after the conversion. Thus, it is possible to check manually, reschedule or delete the jobs afterwards.

Procedure

  1. Access the transaction using the following navigation option:
    Transaction Code SM37
  2. On the Simple Job Selection screen, select all the periodical jobs by entering Job name ‘’, User name ‘’; in the Job status section, select Released. In the Job start condition section, select a time range from current day until at least one month ahead (From / To), in the or after event field, choose ‘*’.
  3. Choose Execute.
  4. In the Job Overview, select all jobs listed via the menu and choose Edit → Select All.
  5. Deselect all Jobs with the JobName RDDIMPDP*.
  6. From the Job menu, choose Released → Scheduled.

The SUM automatically executes the report BTCTRNS1 before the conversion will be started. This report transfers all remaining jobs with the status released to the status Suspended.

Update Table DBDIFF

The table DBDIFF contains information about all differences between the ABAP dictionary and the database, which are technically required. All differences which are not registered here are rated as errors. This table must be updated here.

Procedure

  1. Access the transaction using the following navigation option:
    Transaction Code SA38
  2. On the ABAP: Program Execution screen, provide the program name SAP_UPDATE_DBDIFF.
  3. Choose Execute.

Check/ Repair Missing Tables and Indexes

Objects that are defined in the ABAP Dictionary but missing on the database cannot be exported and are then missing after the migration.

Procedure

  1. Access the transaction using the following navigation option:
    Transaction Code DBACOCKPIT
  2. On the DBA Cockpit: System Configuration Maintenance screen, choose Diagnostics → Missing Tables and Indixes → Objects missing in the database.
  3. Access the transaction using the following navigation option: Transaction Code
    SE14
  4. In case of missing indexes:
    a. On the ABAP Dictionary: Database Utility screen, fill in the database table of the missing index.
    b. In the tool bar, choose Indexes…
    c. Choose the concerned index.
    d. Choose Create Index.
  5. In case of missing tables:
    a. On the ABAP Dictionary: Database Utility screen, fill in the missing database table.
    b. Choose Create database table.

Leave a Comment