Showing posts with label STMS. Show all posts
Showing posts with label STMS. Show all posts

Single Transports In STMS

Purpose

You may want to use single transports for the following reasons:

  • You only make transports infrequently.
  • Your organization does not include fixed import times.
  • You want to maintain production systems directly with corrections.

A strategy of single transports has the following risks:

  • Increased administration

Caution

If you import single requests from the import queue into the target system, you must make sure that the objects in the requests are complete and consistent. Unlike the Structure link import of individual projects, the system does not provide automatic support for dealing with relationships between requests.

  • Relationships between transport requests can create inconsistencies in the target system:
    • Import sequence

It is important that you import requests in the correct order, so that development work is up-to-date in the target system.

    • Incompleteness

Example

A request is not imported, but it contains an important data element. You use another request to transport a table that references this data element. Since the referenced data element does not exist in the target system, activation errors will occur when you import the second request.

Process Flow

The single transport strategy is defined as follows:

  • Use of transport routes

Change requests are transported using predefined consolidation and delivery routes (see: Structure link Configuring Transport Routes).

  • Import individual change requests from the
  • import queue:

Select the change requests that you want to transport and then import them into the target system. The requests are imported in the order in which they are placed in the import queue.

  • Import all change requests of a
  • project:

If you want to organize your developments in different projects, use the IMG project functions. If you do this, it is important that you keep your development projects distinct from each other. You can then import your requests in projects.

Activating Inactive Requests

Use

Normally, you cannot import requests with the import status Request must still be approved . In exceptional cases, you can manually activate non-approved (inactive) requests in the import queue without a quality check.

Prerequisites

To activate inactive requests, you need the authorization S_CTS_ADMIN. This authorization is in the profile S_A.SYSTEM.

Procedure

To activate inactive requests:

  1. Enter transaction STMS.
  2. Choose This graphic is explained in the accompanying text. The Import Overview appears.
  3. Position the cursor on the SAP System whose import queue you want to edit.
  4. Choose This graphic is explained in the accompanying text. The import queue of the selected SAP System appears.
  5. Mark the inactive requests you want to activate and choose Extras ® Activate inactive requests.

Result

TMS activates these requests locally in the import queue of the selected system:

  • The import status changes to Request waiting to be imported.
  • In the expanded view of the import queue, the processed requests are displayed in the column Ac as being active. (To expand the import queue display, choose This graphic is explained in the accompanying text.)
  • You can now import the activated requests.
  • Processing these requests in the QA work list is no longer relevant for this system.

Closing/Opening the Import Queue

Prerequisites

So that an SAP System being supplied with change requests always remains consistent, you must specify deadlines by which developers must release their change requests. You can close the import queue to prevent requests released after the deadline from being imported.

Change requests which are then released are placed after the current import in the queue, and marked for import next time around. During the next import, which can also take place at a later point in time, only the requests before the end mark are imported.

Note

Make sure that all concerned are aware of when you want to close the import queue. This lets your developers decide when to release their work for import into other systems.

Procedure

To close the import queue:

  1. Enter transaction STMS.
  2. Choose This graphic is explained in the accompanying text. The import overview appears.
  3. Position the cursor on the SAP System whose import queue you want to close.
  4. Choose This graphic is explained in the accompanying text. The import queue of the selected SAP System appears.
  5. In the Status column choose This graphic is explained in the accompanying text.

The end mark of is set and the display updated. The requests that will be imported are displayed.

Note

In the import overview, a closed queue is shown by the This graphic is explained in the accompanying text icon in the Status column.

To open the import queue, go to the import queue of the closed SAP System and choose This graphic is explained in the accompanying text.

How to disable Import All option from STMS in SAP

Any changes made in the development server needs to be transported to the Quality server for checking and then finally in Production server.

So Importing the Transport Requests is the critical. Sometimes by mistake if one click on the button Import All in the production environment all the Transport Request which is in released status or already Imported to Production can be directly Imported to the production environment (Which may not be required in the Production). This will create great impact in the production Server.

To avoid such situation, IMPORT ALL Icon should be disabled in STMS.

Procedure to Disable IMPROT_ALL Icon in STMS:-

1) Go to STMS Tcode



2) Go to Menu Option Overview



3) Select System

4) Choose SAP SYSTEM



5) Go to Transport Tool Tab



6) Create Parameter "NO_IMPORT_ALL" with value 1 (True)

7) Save it.

Once it is done the Import_ALL icon will be Disabled from STMS.

SAP Transport Management System

Logon to the R/3 system, which is to be designated as Transport domain controller using SAP* or any user having similar authorization in to 000 client.Use TCODE STMS, it will propose the system as Transport domain controller,provide the description and click on Save

From the Transport management screen Select Overview menu and select Systems
From the System overview screen, place the cursor on SID and Select SAP System menu
and select Display

Logon 000 client on the R/3 system to be included into domain and use T-code STMS.
It will propose the system as Transport domain controller.
Select the Button Other Configuration

Logon to 000 client of domain controller and use TCODE STMS,
Select Overview menu and select Systems

Place the cursor on R/3 system waiting for inclusion and Select SAP System menu
and Select Approve and Click on Yes.

Distribute the TMS configuration by Selecting Extras à Distribute TMS Configuration.
Select Yes to distribute Configuration.
Select SAP System Menu and select Update Configuration.

Use TCODE STMS, Select Overview menu and select Systems (System Overview Screen)
Select SAP System -> Create -> Virtual System.
Provide Virtual System SID , Description and Click Save .
Click yes to distribute the configuration change across domain .

This Systems have their own transport directory. They are used to provide an
intermediate directory to enable us to send change requests to other transport
domain or to exchangeable data media.
From the System Overview ScreenSelect SAP System ->Create ->External System.
Provide the SID and Description and Path to the transport directory of the External System. Click Save.
Select Yes to distribute the change Immediately

Goto Stms->Overview-> Transport routes and from the screen displayed goto Configuration->Display and Change Configuration->Standard Configuration-> Three Systems in Group

Choose Continue






Standard Transport Layer: Describes the transport route that the data
from the development system follows.
SAP Transport Layer: It is a predefined Transport layer for the development SAP Transport Layer: It is a predefined Transport layer for the development
classes of SAP Standard objects.

From the Change transport route Screen, select Edit-> Transport Layer-> Create

Standard Transport Layer: Describes the transport route that the data
from the development system follows.
SAP Transport Layer: It is a predefined Transport layer for the development SAP Transport Layer: It is a predefined Transport layer for the development
classes of SAP Standard objects.



Click on the Client assignment button,
Select Target sytem , Target Client and all needed clients.
Choose transfer.

A Target Group is a group of target clients.
Access one of the Transport route editors
Edit->Transport Target Group -> Create
Enter Target group name should be in between “/” (Slash) and Description


STMS Material free downloads


STMS
TMS Overview
TMS Overview By SAP-AG
TMS With MYSAP Landscape
TMS With MYSAP Landscape - 1
Types Of Transports
Managing Transports