Showing posts with label STMS. Show all posts
Just a small configuration in STMS, hope it helps.
QA Approval step configuration.
Go to STMS in Transport Domain Controller.


Switch to change mode
Click on <SID> – the QA system, choose Edit – System – Change


Select Deliver After Confirmation in tab System Attributes.



Click on Procedure.


Click OK.

Save and distribute configuration.


Perform a test for approval.

From DEV system create a new single role ZS_CTS_ADMIN, add the authorization object S_CTS_ADMI.

And put * for Administration Tasks CTS_ADMFCT.


Save and generate profile for the role.


Create a transport request from the role.


Release it from SE01.


Now transport the request into QUALITY system.


To be able to import into Production, you will be ask for approval.

From production system, go to transaction STMS_QA
Double click the icon to see the status of approval step
We have set 2 approval step need : Request owner and System Administrator
*To be able to do the approval, make sure 2 users have the profile from role with the authorization object S_CTS_ADMI


Select To be the approved by request owner.
Then make sure the request is still selected, click Approve.


Enter text for the approval.
You will be asked to logon to QCR once.
Now Double click the icon under St to see the status.


Do the same step for “To be Approved by system Administrator”
When you finished all the approval steps, it will be available to import into PCR now.
  • TMS is the transport tool that assists the CTO for central management of all transport functions. TMS is used for performing:
    • Defining Transport Domain Controller.
    • Configuring the SAP system Landscape
    • Defining the Transport Routes among systems within the system Landscape
    • Distributing the configuration
  • Transport Domain Controller – one of the systems from the landscape that contains complete configuration information and controls the system landscape whose transports are being maintained jointly. For availability and security reasons, this system is normally the Productive system.

Within transport domain all systems must have a unique System Ids and only one of these systems is identified as the domain controller, the transport domain controller is the system where all TMS configuration settings are maintained. Any changes in to the configuration settings are distributed to all systems in the landscape. A transport group is one or more systems that share a common transport directory. Transport Domain – comprises all the systems and the transport routes in the landscape. Landscape, Group and Domain are the terms that are used synchronously by system administrators.
Step 1:Setting up the Domain Controller
  • Log on to the SAP system, which is decided to be the Domain Controller, in client 000 and enter the transaction code STMS.
  • If there is no Domain Controller already, system will prompt you to create one. When the Transport Domain is created for the first time, following activities happen in the background:
    • Initiation of the Transport Domain / Landscape / Group
    • Creating the user TMSADM
    • Generating the RFC Destinations required for R/3 Configurations, TMSADM is used as the target login user.
    • Creating DOMAIN.CFG file in usr/sap/trans/bin directory – This file contains the TMS configuration and is used by systems and domains for checking existing configurations.
Step 2:Transaction STMS
 


Step 3: Adding SAP systems to the Transport Domain
  • Log on to SAP systems (to be added in the domain) in client 000 and start transaction STMS.
  • TMS will check the configuration file DOMAIN.CFG and will automatically propose to join the domain (if the domain controller already created). 'Select' the proposal and save your entries.
  • For security purpose, system status will still be in 'waiting' status, to be included in the transport domain.
  • For complete acceptance, login to Domain Controller System (Client 000) -> STMS -> Overview -> Systems. New system will be visible there. From the menu choose 'SAP System' -> Approve.

Step 4:Configuring Transport Routes
  • Transport Routes – are the different routes created by system administrators and are used to transmit changes between the systems in a system group/landscape. There are two types of transport routes:
    • Consolidation (From DEV to QAS) – Transport Layers are used
    • Delivery (From QAS to PRD) – Transport Layers not required
  • Transport Layer – is used to group the changes of similar kinds, for example, changes are done in development objects of same class/category/package, logically should be sent through same transport route. Therefore transport layers are assigned to all objects coming from DEV system. Layers are used in Consolidation routes, however after testing happens in QAS, layers are not used and the changes are moved using single routes towards PRD system.
Package – (formerly known as Development Class) is a way to classify the objects logically belonging to the same category or project. A package can also be seen as an object itself and is assigned with a specific transport layer (in consolidation route), therefore, changes made in any of the development object belonging to a particular Package, will be transmitted towards target system through a designated Transport Layer only, or else the change will be saved as a Local (non-transportable) modification.
Make sure the transport request is released from the source system. Log onto the target system as <SID>adm.
To add the transport request to the buffer (Single command line).
tp addtobuffer <TRANSPORT-REQUEST> <SID> Client=<CLIENT-NUMBER>
pf=/usr/sap/trans/bin/TP_DOMAIN_<DOMAIN_SID>.PFL
Example:
tp addtobuffer DEV12345 QAS Client=000
pf=/usr/sap/trans/bin/TP_DOMAIN_DEV.PFL
To import the transport request (Single command line).
tp pf=/usr/sap/trans/bin/TP_DOMAIN_<DOMAIN_SID>.PFL
import <TRANSPORT-REQUEST> <SID> U128 client=<CLIENT-NUMBER>
Example:
tp pf=/usr/sap/trans/bin/TP_DOMAIN_DEV.PFL
import DEV12345 QAS U128 client=000
Subscribe to: Posts (Atom)
Copyright © 2013 VENKAT SAP BASIS