SAP Note Processing Status

The user who is processing an SAP Note specifies its processing status. This status indicates whether a user has already processed this SAP Note, and if so, to which extent.

You can set the following processing statuses in the Note Assistant:

• New

You have loaded the SAP Note into your system, but have not yet processed it.

• In processing

A user is processing the SAP Note.

• Completed

You have followed the instructions in the SAP Note and implemented any corrections in your system. The processing of the SAP Note has now been completed.

• Not relevant

You have read the SAP Note and decided that it is not relevant, for example because it refers to a function that you do not user.

SAP Note Troubleshooting

This section provides information about messages that the Note Assistant can display:

· Object cannot be locked under request

The Note Assistant makes sure that an SAP Note is implemented under one request. To do this, it enters the transport object R3TR NOTE in the request and locks the SAP Note under this request. You can then edit the SAP Note or its objects in this request only.

If the objects are already locked in other requests, you must release them. You can then edit the object again.

· Note is inconsistent

An SAP Note can include corrections to multiple objects. Transporting individual objects may cause an SAP Note to be implemented incompletely. In this case, the status of the SAP Note is displayed as inconsistent. You should then check the implementation status of the SAP Note and implement it again if necessary.

· Note not in worklist after download

The SAP Note may have already been downloaded and processed. Search in the Note Browser to find all SAP Notes that are available in the system.

Other Problems with the Note Assistant

If the system cannot implement an SAP Note automatically, and there are no modifications in your system, try to use the split-screen editor to implement the SAP Note. If automatic implementation fails, it is usually due to small differences in the source code.

If implementation still fails, create a problem message in SAPNet – R/3 Frontend and assign it to the component of the SAP Note. The component is in the note header (for example, FI-AR-CR).

If you experience any other problems with the Note Assistant, create a problem message and assign it to the component BC-UPG-NA.

Checking Support Packages

A Support Package contains a collection of error corrections. You can only import complete Support Packages and in a specified sequence. Each correction in a Support Package is documented in an SAP Note.

After you have imported a Support Package, you must perform the Modification Adjustment using transaction SPAU. The following cases exist:

• Correction implemented by an SAP Note and included in a Support Package (traffic light without colors)

When you import a Support Package, the system automatically checks whether you have already used SAP Notes to implement individual corrections from the Support Package in your system. In the modification adjustment function (transaction SPAU), these SAP Notes are flagged as obsolete by a gray light.

Reset the objects to their original SAP versions. You can do this in the following ways:

• Click the traffic light icon.
• Select the SAP Note number. Choose Reset to Original.

A dialog box appears. Confirm that you want to reset the correction to its original status.

If you have selected more than one correction, you can choose Reset All. The dialog box no longer appears.

• SAP Note implemented, but not included in Support Package (yellow traffic light icon)

The system checks whether corrections you implemented with an SAP Note have been overwritten by a Support Package that does not contain these corrections. You must implement these corrections again. In the modification adjustment function (transaction SPAU), these SAP Notes are flagged with a yellow light.

Double-click the light to implement the SAP Note again.

Your worklist also indicates that you need to implement these SAP Notes again (status inconsistent). To do this, choose Implement SAP Note.

• Correction implemented by an SAP Note and included in a Support Package, however SAP Note version is different (yellow traffic light)

The system checks whether you have already used SAP Notes to implement individual corrections from the Support Package in your system. If the version of the SAP Note included in the Support Package is a later version than that of the SAP Note that was implemented using the Note Assistant, then the modification adjustment is unable to reset the objects included in the SAP Note to their original status. The system displays this SAP Note with a yellow traffic light.

In this instance, proceed as follows:

1. Call the Note Assistant.
2. Download the current SAP Note version for all SAP Notes.
3. In the modification adjustment, calculate the adjustment modes again. Choose Goto ® Determine Adjustment Mode.

If the SAP Note was not changed by SAP, a traffic light without colors is displayed. You can reset it to its original status, as described under the section Correction implemented by an SAP Note and included in a Support Package (traffic light without colors).

If the SAP Note was changed by SAP, a yellow traffic light is displayed. Proceed as described under the section SAP Note implemented, but not included in Support Package (yellow traffic light icon).

• SAP Note implemented, although parts included in Support Package (green traffic light icon)

An SAP Note contains multiple correction instructions with different validity periods, for example. When you import the Support Package, one set of correction instructions becomes obsolete and the other remains valid. In this exception case, the SAP Note appears with a green traffic light icon.

If you click the icon, the correction instructions that are no longer relevant are reset to their original status.

• Adjustment mode for SAP Note implementation undetermined (green question mark)

After you have imported the Support Package, the adjustment modes for corrections are calculated in a background process. If this process is not started or if errors occur, a green question mark appears in front of the object in the tree display.

Double-click the question mark to restart the process. This can take a few minutes.

• Objects with your modifications and corrections from SAP Notes

If objects contain your own modifications and SAP Note corrections, you must first process the displayed SAP Note corrections with the modification adjustment function (transaction SPAU), and then adjust your own modifications.

The modification adjustment in the subtree With Modification Assistant is not supported if the object is contained in SAP Note corrections that have not yet been adjusted or reset to their original status.

The objects that are contained in the SAP Note are entered in transport requests if you adjust modifications to these objects, or if you reset them to their original status. This guarantees that they are transported into follow-on systems.

Updating an SAP Note

You use this function to compare the version of the SAP Notes that are in your system with the latest version of the SAP Notes in SAPNet - R/3 Frontend. In this way you can check at any time whether the SAP Notes in your system have the latest version. The system downloads the latest version when necessary.

You have the following options:

• Adjusting one SAP Note from the SAP Note display
• Adjusting all the SAP Notes that are in your worklist
• Adjusting all the SAP Notes that are listed in the note browser

SAP Notes can only be updated automatically if you have created an RFC connection to the SAPNet - R/3 Frontend.

Prerequisites

You have created an RFC connection to the SAPNet – R/3 Frontend.

Procedure

1. Choose Download Latest SAP Note Version.

The system checks whether the latest version of the SAP Notes that are listed on the screen are available in your system.

The SAP Notes that were changed by SAP since you last downloaded them are displayed in a dialog box.

2. To download the latest version of these SAP Notes, confirm the dialog box.

Result

If an SAP Note was changed and had to be reimplemented, the Note Assistant displays this SAP Note in your worklist under the category inconsistent. Implement this note in your system again.

Otherwise, no action is required.

Classifying SAP Notes

Use

Use this function to specify the relevance or processing status of an SAP Note.

Procedure

...

1. Read the SAP Note carefully and decide whether its contents apply to the situation in your system.

2. Follow the procedure below:

¡ If the SAP Note is relevant for your situation, set its processing status to In process.

This informs other users that you are processing this SAP Note.

Follow the precise recommendations in the SAP Note. If the SAP Note contains correction instructions, implement them in your system.

¡ If you want to assign the SAP Note to another user, specify the name of the user.

Every action that you perform is recorded in a log file for the SAP Note. You can also enter your own comments there, for example for another user.

¡ If the SAP Note is not relevant for your situation, set its processing status to Not relevant.

The system will then indicate to you and all other users that this SAP Note can be ignored.

Searching for an SAP Note

You can use the Note Browser to find any SAP Note that is available in the system. The Note Browser also displays SAP Notes that are assigned to another user, and SAP Notes that have already been implemented.

Prerequisites

You can load SAP Notes into your system from SAPNet - R/3 Frontend or the SAP Service Marketplace.

Procedure

...

1. Select one of the following criteria for the SAP Note:

- Note Number

- Application component

- Processing status

- Implementation Status

- Processor

2. Choose whether you want to

- Limit the selection to certain software components and their releases

- Sort the SAP Notes according to their number or to their corresponding application component

3. Confirm the selection.

Result

The SAP Notes are listed together with their number, short text, component, processing status, implementation status, and user. You can also implement the SAP Notes from the Note Browser.

Working with SAP Notes

You can load SAP Notes into your system from the SAP Service Marketplace or SAPNet - R/3 Frontend. You can do this using an RFC connection (SAP Note download) or with the file transfer method (SAP Note upload).

The SAP Note download has the following advantages:

· When you download an SAP Note, you can use the Note Assistant to load it directly into your system from SAPNet - R/3 Frontend.

· If other SAP Notes are entered as prerequisites in an SAP Note, the Note Assistant automatically downloads the prerequisite SAP Notes during the implementation (Implementing Correction Instructions).

· You can download updated versions of SAP Notes at the press of a button (Updating an SAP Note).

To download an SAP Note, you must create an RFC connection to the SAPNet – R/3 Frontend.

Uploading an SAP Note does not require a permanent RFC connection to the SAPNet – R/3 Frontend. To upload the note, you first download the required SAP Note from the SAP Service Marketplace and save it locally on your front-end PC. You then use the Note Assistant to upload the SAP Note.

Prerequisites

· Note download: You have created an RFC connection to the SAPNet – R/3 Frontend. (See also: Activating the Note Assistant)

· Note upload: You have installed the SAP Download Manager, which enables you to load SAP Notes from the SAP Service Marketplace. You can find the SAP Download Manager in the SAP Service Marketplace, under service.sap.com/download-basket ® Get Download Manager.

Procedure

SAP Note Download

...

1. In the Note Assistant, choose SAP Note Download.

2. Specify the numbers of the SAP Notes that you want to download.

Use the selection function to load one SAP Note or a list of SAP Notes.

3. Confirm your selection.

The system loads the SAP Notes from SAPNet – R/3 Frontend into your database.

SAP Note Upload

...

1. Select the correct SAP Note in the SAP Service Marketplace under service.sap.com/notes.

2. Choose Download.

The SAP Note is added to your download basket. You can repeat this action for as many SAP Notes as you require.

3. To save the SAP Notes locally on your PC, start the SAP Download Manager. Choose Download.

The SAP Notes are loaded as files into the directory you have specified.

4. Use the upload function in the Note Assistant (Goto -> Upload SAP Note) to load the SAP Note files into your system.

Result

After you have successfully downloaded or uploaded an SAP Note that did not previously exist in your system, the processing status of this SAP Note is set as new in the SAP Note overview.

Registering Manually Implemented SAP Notes

If you implemented corrections contained in SAP Notes in your SAP System before you installed the Note Assistant, you can make this known to the Note Assistant retroactively. This is important since the Note Assistant cannot automatically recognize whether a correction was implemented manually in your system without using the Note Assistant.

Registration offers the following benefits:

• All the SAP Notes that have been implemented in your system are displayed in the Note Browser.

• If a manually implemented SAP Note is a prerequisite for an SAP Note that you want to implement using the Note Assistant, the Note Assistant recognizes that the prerequisite SAP Note has already been implemented and does not prompt you to implement it again.

• For future Support Packages or upgrades, the manually implemented SAP Notes are displayed during the modification adjustment in the category SAP Note Corrections. The system determines whether these SAP Notes have to be implemented again or reset to their original status.

Prerequisites

You have implemented SAP Notes manually without the Note Assistant.

Procedure

1. Call the SCWN_REGISTER_NOTES program with the ABAP Editor (transaction SE38).

2. On the input screen of the program, enter the numbers of the completely implemented SAP Notes that you want to register.
3. This may lead to the following situations:

• If you have created an
RFC connection to the SAPNet - R/3 Frontend, the program automatically loads the SAP Notes that are to be registered into the database of your system.
• If you have not created an RFC connection, first you must load the SAP Notes that are to be registered from the SAP Service Marketplace. Then perform an
Upload in the Note Assistant.

The program checks whether the SAP Notes are valid for your release and Support Package level. The system also checks whether the SAP Notes have already been registered in the Note Assistant as implemented.

The system displays the results of these checks in a list.

4. To register the SAP Note, choose Execute.

To register an SAP Note as implemented, the system must enter the SAP Note together with the objects that are corrected by this SAP Note in a change request. By transporting this request you also register the SAP Notes in your follow-on systems as implemented. If you cannot enter the SAP Note and its objects in a request (because some objects are locked by other requests, for example), the system terminates registration.

Result

The system registers the valid SAP Notes that have been implemented manually as completely implemented in your system, and automatically sets the processing status to Completed. Every SAP Note has a log entry in which the time and the user who triggered the registration are recorded. Invalid SAP Notes cannot be registered as implemented. This is not necessary since these corrections have already been imported into your system in the form of a Support Package. The processing status of these SAP Notes is automatically set to not relevant.

Loading an SAP Note

Use

You can load SAP Notes into your system from the SAP Service Marketplace or SAPNet - R/3 Frontend. You can do this using an RFC connection (SAP Note download) or with the file transfer method (SAP Note upload).

The SAP Note download has the following advantages:

· When you download an SAP Note, you can use the Note Assistant to load it directly into your system from SAPNet - R/3 Frontend.

· If other SAP Notes are entered as prerequisites in an SAP Note, the Note Assistant automatically downloads the prerequisite SAP Notes during the implementation (Implementing Correction Instructions).

· You can download updated versions of SAP Notes at the press of a button (Updating an SAP Note).

To download an SAP Note, you must create an RFC connection to the SAPNet – R/3 Frontend.

Uploading an SAP Note does not require a permanent RFC connection to the SAPNet – R/3 Frontend. To upload the note, you first download the required SAP Note from the SAP Service Marketplace and save it locally on your front-end PC. You then use the Note Assistant to upload the SAP Note.

Prerequisites

· Note download: You have created an RFC connection to the SAPNet – R/3 Frontend. (See also: Activating the Note Assistant)

· Note upload: You have installed the SAP Download Manager, which enables you to load SAP Notes from the SAP Service Marketplace. You can find the SAP Download Manager in the SAP Service Marketplace, under service.sap.com/download-basket ® Get Download Manager.

Procedure

SAP Note Download

...

1. In the Note Assistant, choose SAP Note Download.

2. Specify the numbers of the SAP Notes that you want to download.

Use the selection function to load one SAP Note or a list of SAP Notes.

3. Confirm your selection.

The system loads the SAP Notes from SAPNet – R/3 Frontend into your database.

SAP Note Upload

...

1. Select the correct SAP Note in the SAP Service Marketplace under service.sap.com/notes.

2. Choose Download.

The SAP Note is added to your download basket. You can repeat this action for as many SAP Notes as you require.

3. To save the SAP Notes locally on your PC, start the SAP Download Manager. Choose Download.

The SAP Notes are loaded as files into the directory you have specified.

4. Use the upload function in the Note Assistant (Goto -> Upload SAP Note) to load the SAP Note files into your system.

Result

After you have successfully downloaded or uploaded an SAP Note that did not previously exist in your system, the processing status of this SAP Note is set as new in the SAP Note overview.

SAP Notes

SAP Notes give you instructions on how to remove known errors from SAP Systems. They include a description of the symptoms, the cause of the error, and the SAP Release and Support Package level in which the error occurs.

Depending on the type of error, an SAP Note may also include:

· Workarounds

· Descriptions of how to correct repository objects in the ABAP workbench, known as correction instructions

· Links to Support Packages that solve the problem

You can access SAP Notes both from the SAP Service Marketplace and SAPNet - R/3 Frontend.

The Note Assistant can automatically implement only SAP Notes that have correction instructions.

Read the SAP Note carefully before you use the Note Assistant to implement it. The SAP Note can contain prerequisites, interactions, and references to postprocessing activities (making changes to a table, for example) that you must take into consideration when you implement it.

Alert Viewer in Transport Organizer

The TMS Alert Viewer records and displays all the actions which you perform with the Transport Management System. You can display this information using the Alert Viewer.

To do this, call Transaction STMS and choose Monitor ® TMS Alerts ® TMS Alert Viewer.

The following information is displayed:

• Date and time

• User name
• TMS function
• TMS message

• SAP System in which the TMS function was triggered
• System name
• Client

The following functions are provided in the Alert Viewer:

	Success messages are also displayed beside TMS error messages and warnings
	Limits the display to errors and warnings or just errors
	Includes any non-displayed actions in the list
	Displays detailed information about a user if the user is known in the SAP System where the Alert Viewer was started
	Displays the TMS Alerts of another SAP System in the transport domain

If you click a message, the TMS Alert Viewer: Error Message dialog box appears with additional information on the message. You can navigate through the messages in this dialog box using . Choose to display the relevant online documentation.

The following functions are available in the dialog box TMS Alert Viewer: :

	Displays the original message
	Displays the long text, if it is available
	For tp errors, the information written by tp to StdOut is displayed

Alerts in the Transport Management System

Alerts

Various situations can lead to errors when you are working with the Change and Transport System (CTS). The system administrator must react to these errors to ensure the stability and consistency of the SAP System.

To support the administrator, the Transport Management System (TMS) records CTS errors and provides tools that can be used to display and process these situations, known as alerts.

Among others, the Transport Management System records the following alerts:

• Errors that occurred when transport requests were exported
• Errors that occurred when transport requests were imported
• Errors in communication between SAP Systems
• Errors in the CTS configuration

You can display the alerts in both the CCMS Alert Monitor and the TMS Alert Viewer. On the initial TMS screen you can specify the default alert display by choosing Extras ® Settings ® Standard Alert Display.

Tools

CCMS Alert Monitor

The CCMS Alert Monitor is activated automatically when the TMS is configured. It replaces the TMS Alert Viewer, which is now only needed in special cases (for example, for special analyses). The CCMS monitor organizes alerts by system and topic. You can use this tool to display and process alerts.

Alerts are recorded in the system where they occur and then sent to the transport domain controller. This lets the system administrator monitor all systems in the transport domain centrally from the domain controller.

You do not need to make any additional changes to the configuration of the Computing Center Management System (CCMS) (such as maintaining central system groups) to be able to monitor TMS alerts in multiple systems. The TMS communication interface is used to send alerts to the CCMS in the domain controller system.

TMS Alert Viewer

Unlike the CCMS Alert Monitor, the TMS Alert Viewer is organized chronologically, and displays all actions for the selected system, not just errors. However, the Alert Viewer does not let you process these actions.

The TMS Alert Viewer only retains a certain number of actions in the display. If you want to display older actions, choose Edit ® History +/- to include more entries.

It can take some time to include older actions in the TMS Alert Viewer.

Displaying Schedules and Logs for TMS Jobs

You have displayed a job list and want to see:

• The scheduling data for TMS jobs
• The logs for TMS jobs

Procedure

Displaying Scheduling Data

Position the cursor on a job in the list with the scheduling data you want to see and choose . The dialog box Job Information from System appears with the relevant data under the tab Schedule.

Displaying the Logs

Position the cursor on a job in the list with the log you want to see, and choose . The dialog box Job Log from TMS from System appears. You can navigate through the entire job list using the icons.

If you want to display the logs of jobs in other systems, you need the administration authorization for background processing. For more information, see Background Processing.

To display job logs in other systems, you must first log on to the relevant system. The logon screen of the system is displayed automatically.

Administrating TMS Jobs

Use

You have displayed a job list and want to:

• Reset the scheduling of TMS jobs

• Release TMS jobs
• Cancel TMS jobs
• Delete TMS jobs
• Check the status of TMS jobs

Procedure

To perform the relevant action, proceed as follows:

Resetting the Scheduling of TMS jobs

In the job list, mark the job(s) whose scheduling you want to reset, and choose .

Releasing TMS Jobs

In the job list, mark the job(s) that you want to release, and choose .

Canceling TMS Jobs

In the job list, mark the job(s) that you want to cancel, and choose .

Deleting TMS Jobs

In the job list, mark the job(s) that you want to delete, and choose .

Checking the Status of TMS Jobs

In the job list, mark the job whose status you want to check, and choose . In the status bar, you can see the result of the check.

Resetting User TMSADM

Use

If you want to reset user TMSADM to the default, or if the configuration of this user was damaged, then:

Procedure

1. Log on to the SAP System in which you want to reset user TMSADM.
2. Enter Transaction STMS.
3. Choose Overview
® Systems. The system overview appears.
4. Choose Extras ® Reset user TMSADM.

Result

The CPIC user TMSADM is regenerated with the default authorizations.

Determining Approval Steps in the Domain Configuration

Use

You want to determine approval steps for QA systems.

Note the following rules:

• At least one approval step must be active for each defined QA system.
• You cannot delete or change the 3 default approval steps. You can only set the approval steps to be active or inactive. The default approval steps are valid for all configured QA systems.
• If you define additional approval steps and have configured more than one QA system, you can determine if the additional steps are to be system-/client-specific (only one QA system) or cross-system/client (global).

Prerequisites

You have configured at least one QA system.

To determine approval steps for the QA systems in the domain, you have to log on to the domain controller.

Procedure

1. In the TMS initial screen, choose . The screen System Overview: Domain appears.
2. Choose . The screen Display TMS Configuration: appears.

Under the tab Management you see how many QA systems are configured and who made the last change and when.

Under QA Approval Procedure you see the names of the configured QA systems and which steps exist. (If the transport routes are client-specific, the column Client is also displayed. If several QA systems are configured, the column System is also displayed.)

3. Switch to the change mode. To do this, choose Configuration ® Display « Change.

If you want to add approval steps:

1. Choose Insert row. By default, the new step has the type Approved by user department.
2. You can choose another type using the input help. If you choose another type, you receive the default text for it at the same time. You can edit this text.
3. If you have more than one QA system configured, additional columns are displayed (System and Client). You must use the input help to determine if the additional step is system-/client-specific or global.

4. Mark the approval step in the column Active that you want to process for the requests of the relevant QA system.
5. Save your entries.
6. Distribute the configuration.

Result

You have defined the approval step that is valid for your QA systems.

Configuring the QA System

Use

To perform quality assurance measures in the TMS, you must first configure the QA system.

Prerequisites

The system you want to configure as the QA system must have the following attributes:

• It must be the target of at least one consolidation or delivery.
• It must deliver to at least one additional real system.

To configure the QA approval procedure, you have to be logged on to the domain controller.

Procedure

1. In the TMS initial screen, choose . The screen Display Transport Routes appears displaying the existing transport routes in the transport domain.
2. Switch to the change mode by choosing Configuration ® Display <-> Change.
3. Position the cursor on the system that you want as the QA system.
4. Choose Edit ® System ® Change. The dialog box Change System Attributes appears.
5. Choose the tab System attributes and under Quality assurance select Delivery after confirmation.

You can only set Delivery after confirmation for the whole system. If you use Extended Transport Control, then all clients with the following attributes become QA clients in the system:

1. Clients that are the target of a delivery or consolidation
2. Clients that deliver to other clients

Under Procedure you can determine the approval steps. You can also set and change the approval steps in the domain configuration. The step Approved by system administrator is the active default setting.

1. Choose Copy.
2. Choose Configuration ® Distribute and activate.

Result

You have configured the QA system. After the configuration, the QA worklist is built. All the requests that are then imported into the QA system are included in the QA worklist. You can only import completely approved requests into the delivery systems.

Configuring the QA Approval Procedure

Use

Before you can process request with respect to the TMS Quality Assurance, you must configure the QA approval procedure.

Prerequisites

Ensure that your system landscape and/or transport domain is set up so that there is at least one development, one quality assurance, and one production system.

The system you want to configure as the QA system must have the following attributes:

• It must be the target of at least one consolidation or delivery.
• It must deliver at least one additional system.

To configure the QA approval procedure, you have to be logged on to the domain controller.

Procedure

1. 
   
Configure your QA system.
2. 
   
Determine the approval steps for your QA system.

TMS Quality Assurance

Use

TMS Quality Assurance increases the quality and the availability of the production systems by letting you check requests in the QA system before they are delivered to subsequent systems.

The system for which the QA approval procedure is activated is called the QA system. When the QA approval procedure is activated, transport requests are only forwarded to the delivery systems if all the QA approval steps are processed for each request in the QA system and each request has been approved. (When you configure the QA system, you determine how many QA approval steps have to be processed for each request.) If a check for an approval step is not successful, the entire request cannot be approved.

Rejected requests are not imported into the delivery systems of the QA system.

If you reject requests, there is the risk that errors may occur when they are imported into the delivery systems. This is a result of the requests containing objects that are referenced from other requests. It is safer to correct an error using a subsequent transport (see Transport Strategy in the CTS).

Integration

In the TMS transport route configuration, you determine which system is the QA system, and which approval steps should apply to this system. You configure the QA approval procedure by performing these two steps. All the requests that are then imported into the QA system are included in the QA worklist.

You can go from the TMS Import Overview to the QA Worklist where you have to check the requests for each approval step.

You can only import all requests into the delivery systems if all the requests ready for import have been checked (which means approved or rejected).

If all the requests for a project and target clients are checked, you can import them even if requests for other projects and target clients have not been checked yet.

Prerequisites

Your system landscape contains at least one QA system from which there are configured delivery routes into other systems.

In a 3-system landscape, the requests from the development system are imported into the QA system. There, the requests are checked and the approved requests are forwarded to the production system.

Functions

• Configuring the QA approval procedure (determining the QA system and the approval steps)

You determine which system is the QA system, switch on the option Forward after confirmation for this system, and define which approval steps are valid for this system.

• Processing the QA worklist

After a system has been configured as the QA system, the QA worklist is built. You then have to check the requests in these views for the individual approval steps.

• Displaying the QA history

Using this history you can display the QA activities for a specific period.

Activities

1. When you configure the
QA approval procedure, you determine the QA system, switch on the option Forward after confirmation, and define the approval steps for that system.
2. You
approve or reject requests.
3. You display the
QA history for a selected period.

external SAP System

Change & Transport System

A special type of virtual system that uses a real SAP System to perform actions for the system in a transport directory.

External systems differ from virtual systems in that they have their own separate transport directory.

Import Overview: Information

The TMS import overview shows the current status of the import queue for each SAP System in the transport domain. To access the import overview, call Transaction STMS and choose .

The following system types exist:

	Virtual system
	External system
	Quality assurance system

An import queue can have one of the following statuses:

	Data is obsolete or does not exist
	Import queue is open All requests released for this SAP System, or forwarded to this SAP System are flagged for the next import.
	Import queue is closed The import queue has an end mark. All requests in the queue before the end mark are imported during the next import. All requests marked after the end mark are marked for the import following the next import. After the import queue has been closed, all the released or forwarded requests for this SAP System after the end mark are sorted.
	Import is scheduled
	Import is running All requests in the queue before the end mark are currently being imported into the SAP System. To display detailed information about the import running, use the Import Monitor. Preliminary imports are not displayed in the import overview.
	Errors occurred during import All requests in the queue before the end mark are currently being imported into the SAP System. However, errors occurred during the import. To find the source of the errors, use the tools described under Monitoring Transports.
	Import terminated An error occurred during the import. You can display detailed information about the source of the error by using the Import Monitor.
	Could not read import queue Error occurred when reading the import queue of an SAP System. Click the status field of the import queue to display a detailed error message.