Entering content frameProcedure documentation Inactive Import of Report Source Code and Texts Locate the document in its SAP Library structure

Use

The larger Support Packages currently available lead to longer system downtime when they are being imported. The system is not restarted when Support Packages are imported; however, it should not be used productively. This restriction is often a disadvantage in production systems.

To reduce the downtime when importing Support Packages, an import procedure has been developed that lets you import the majority of the objects during production operation of the system. These objects consist of the report source code and texts. This new procedure can reduce downtime considerably if the Support Package contains a large proportion of report source code and texts. (This proportion is around 70-80% in Basis and R/3 Support Packages).

The objects are imported into the database in an inactive state, where they are largely 'invisible' to the system. The system can continue to be used productively.

Temporary free space is required in the database, since the inactive objects exist in the database alongside the active versions.

A defined process (triggered by the Support Package Manager) activates the objects later. However, since the inactive objects are not completely isolated from the system, parallel modifications might cause unwanted activation and inconsistencies in the system.

Therefore, make sure of the following during the import:

Recommendation

We recommend around 1.5 times the size of the Support Packages you are importing.

Database

Tablespaces/Dbspaces/Devspaces Affected

Oracle

DB2 Universal Database

PSAPES <REL>D

PSAPES <REL>I

Informix

psapes <REL>

SAP DB

If necessary, create a new devspace to extend the database (see also SAP Note 34690).

In contrast to the previous import procedure, the new procedure contains some new actions (activation of the inactive objects) and additional organizational steps. This lengthens the duration of the import process. The efficiency or time saved in the non-production phase over the standard procedure partly depends on the proportion of inactively imported objects in the total imported data. The duration of other actions performed in downtime (such as after-import methods or XPRAs) also contributes to the time saved.

Note

Import the Support Packages in queues that are as large as possible (ideally in a single queue). To make sure of this, call the Support Package Manager, and choose Display/Define ® Component Selection ® All Components (see also Defining a Queue).

Note that in some cases, Support Packages cannot be imported in a queue. For information, see SAP Note 447925.

Use the inactive import procedure in the following cases:

Do not use the inactive import procedure in the following cases:

The consistency of the system cannot be guaranteed during the import.

The additional pre- and post-import steps of the special BBP/CRM Support Package Manager make sure that the whole import can be performed effectively during downtime.

Prerequisites

You have defined a Support Package queue.

Procedure

  1. Go to the Support Package Manager settings and activate Inactively Import Report Sources.
  2. Choose Support Package ® Import Queue.

The Support Package Manager runs through the normal preparations and checks. It then runs through the import steps for inactive objects that can be performed during production operation of the system.

Note

It first locks the development environment, so that modifications to objects do not put the consistency of the system at risk.
  1. A dialog box tells you to interrupt production operation of the system, so that the Support Package Manager can perform the next import step.

End any background jobs that are running. Prompt all users to end their transactions and log off the SAP System.
  1. Continue importing the Support Package.

This import step activates the inactive imported objects, and imports the remaining objects from the Support Packages in the queue.

Once this transport step has been completed, the Support Package Manager informs you that you can restart production operation of your system.

Caution

This applies only if you have made no modifications or very few modifications to SAP objects. Otherwise, syntax errors may be caused by inconsistencies between modified and corrected SAP objects.
  1. If you have made modifications to SAP objects, the Support Package Manager prompts you to perform a modification adjustment.

You have the following options:

This is recommended if you only have a few objects to adjust, or if you can import a modification adjustment from your development or test system.
    1. To start the modification adjustment, choose Call SPAU.
    2. Perform the modification adjustment.
    3. To continue the import, choose Continue in the Support Package Manager.

This is recommended if you need to adjust a lot of objects.
    1. Start the modification adjustment (transaction SPAU) in a new session.
    2. To continue the import of the Support Package queue, choose Continue in the Support Package Manager.
  1. The modification adjustment makes the system consistent. You can resume production operation of the system.

The following import steps of the Support Package Manager physically delete the obsolete report source code and texts from the database. The import is completed.

 

 

 Leaving content frame