// ]]>

Sunday 5 January 2014

Sap Transport Management System

STMS: Sap Transport Management System

A. What is the transport?
    Transport is used to moving the object from one sap system to another sap system in the landscape.
    Export the change request & import the transport request

B. The transport objects are divided into 2 types they are Export & Import
                                       DEV               QAS               PRO

                                                     Export                            Import
                                                  Central T.P Delivery at O.S level

C. What is domain controller?
     Domain control is a control all the systems in the landscape. It is used to manage all the transport
     parameters in the landscape. In the most of the environment there will be only one domain controller.

D. What is Transport domain controller?
     It is created as part of the post installation activity.

E. What is the transport domain & domain controller?
    At the sap level it is called as transport domain and at O.S level it is called as domain controller.

F. How to configure the domain controller?
    1. First decided which system you could like to define domain controller
    2.Login to the sap system with DDIC in client 000
    3.Go to SE06
    4.Click the post installation activity
    5.Go to STMS
    6.It will ask for the domain controller name
    7.Enter system ID of the domain controller
    8.Enter domain_<Sid> as domain controller name and enter the description
    9.Click save button

G. Steps to add the other system with domain controller
     10.   Logon domain controller system
      11.  Approve the added system







H. What is landscape?
     Landscape is arrangement of group of system to flow the objects
     DEV --------------------> QAS   -----------------------> PRO
     Landscape
     ECC            DEV ------> QAS -------> PRO
     EP               DEV ------> QAS -------> PRO
     BI                DEV ------> QAS -------> PRO
     Based on the customer requirements we can define the single, two, three and multi systems .in the landscape

I. In order to define landscape we need system
   1.Transport layer
   2.Transport root
   3.Transport group
   4.Transport target group
   5.Transport layer: transport layer is used to moving the object path from one system to another system within the landscape.
   Transport layers are 2 types they are Z<Sid> – customizing object move the Z<Sid> layer
   SAP – repository objects move the sap layer
   Transport routs: which shows from the transport direction to the target system?
   In three system landscape
   Dev -----> integrated system
   Qas -----> consolidated system
   Pro -----> delivery system
   Transport routs are 2 types they are
   Consolidated route: the route between development system to quality system is called consolidated route
   Delivery route: the route between quality systems to production system is called delivery route
   NOTE: In a two system landscape delivery route is not available
   Transport group: The systems which are shared a Trans directory is called transport  group
 Transport target group: more than 3 systems & multiple clients it work’s on   extended transport controller  is called transport target group
Extended transport controller: it is used to transport objects within the client & system

J. What is the backup domain controller?
    Whenever primary domain controller is failed. In that time it will care of the transportation

K.  What is work flow?
      To set off the automatic process & responsibility of quality system

L.   Transport background jobs are RDDIMPDP, RDDNEWDP

M. Transport request are stored in TRBAT & TRJOB

N. All the change requests are stored table is E070
     1.E070 – Change request headers
     2.E071 – change request object lists
     3.E071k – object key contained within transports

O. At end of the import, transport specific the return codes
     1.000: import the finished with successfully
     2.004: import finished with warnings
     3.008: some objects are not transported
     4.0012: critical transport errors

P. What is the change request?
    Whenever we can create a request that is called a change request

Q. What is the transport request?
     Whenever we will release the change request that is called transport request

R. Which system we can configure the domain controller?
     Development system

S. What is transport domain (or) integrated system?
    Development system

T. RSTPTEST: - Can be extended if there are any problems with TP (or) R/3 instance.

U. How to check the consistence of STMS?
    Using the transaction code is SA38 (or) SE38 and run the report is RSTPTEST (it will check the if any errors in STMS or not)



V. User locks the transaction code is EWZ5 at sap level and in OS level we can lock the system by using Tp
     # tp lock sys<Sid>  (or)  tp un lock sys<Sid>

W. What is the naming convention of the transport request?
      <Sid>k9<5 digits>

X. How many types of editors?
    1.Graphical editor
    2.Hierarchical editor

Y. Transports are O.S and Data Base Independent but R/3 system is dependent

Z. What is r3trans –d?
    r3 trans –d is used to check the R3 trans connecting to the DB (or) not.

A. Trans directory path is – usr\sap\trans

B.
 Transport request types are 3 they are
     1.K type – with change in integrated system to consolidated system
     2.C type – without change in integrated system to consolidated system
     3.T type – move the one system to another system

C. Tran’s directory structure is
    Trans Bin      buffer       cofiles date         eps         etc          log          sapnames          tmp
    1.Bin: it consists of domain configuration files and transport profile parameters.
    Tp_domain. <Sid>.pfl,   domain.cfg
    2.Buffer: buffer contains transport request ready to import
    Transport request are 2 types they are
    3.Cofiles: A cofiles contains control information of the transport request. cofiles start with K
    4.Data files: A data file contains data information of the transport request. Data files start with R
    5.EPS [Electronic panel service]: which is used to store the support packages?
    6.Log: it rides the log files during the change request
       A log: it contains the information about the transport request. Who is the transport request and name of
       the consultant?
       S log: S log files are stored in transport request of specific system
       U log: U log means it contains the transport command that are executed at OS level
    7.Sapnames: the owner of the change request is documented here

D. How to disable the fully loaded truck?
     Go to STMS --->overview ----> system ----> double click system (Ex: dev) ---> go to transport tool tab ----> insert row ----> N0_IMPORT ALL = 1 – this is used to disable the fully loaded truck

E. How to create the STMS?
    Login to the system with DDIC in client 000
    Go to the T_Code STMS ---->configured ---->standard configured ----> single system, development system, three system in group
    (Or)
    Go to the T_Code STMS ---->overview ----> systems ----> sap systems ----> external system ----> then we have to give the system name, <Sid>

F. How to create the transport route?
    Overview ---> transport route ---> change button ---> click the DEV, QAS & PRO ---> here click the add transport route tab ---> then we have to give the <Sid>, transport layer, system name.

G. How to create the change request?
     Using the transaction codes are SE01, SE09 and SE10

H. How to import the change request?
     Go to STMS --->overview ---> import (or) import overview – button

I. How many types of change request?
   Four they are
   1.Customizing request: customizing request containing client specific object
   2.Workbench request: workbench request containing cross client objects & repository objects
   3.Transport of copies: transport of copies is used for more the tables for user date. This is used for DB refresh & Client refresh
   4.Relocation: relocation object is used for changing the location of object from one system to another system

J. What are the steps for importing at command level?
    Login to target system at OS level using <Sid>adm
    Type #Add to buffer <transport request number><Sid> (enter)
    It should provide you return code 0
    Type #import <request number>CLNT<client number><Sid> U1
    Now look for return codes 0, 4,8,12
    If RC>8 then look for problems with data files & cofiles. Check permissions, check data creation, size.

K. Transport at OS level
     Requesting add to buffer: # tp add to buffer <transport request no> <sap Sid>
     Import request is: # tp import<transport request no><Sid>
     Tp clean the buffer is #tp clean buffer <Sid> ---> to delete the request after completed successfully
     #tp del form buffer <tp request no><Sid> ---> here we can delete the particular request
     #tp show buffer <Sid> ---> display the buffer request

L. How do you import the transport request at OS level?
    # tp import <tp request no><Sid>CLNT = <client no> pf = usr\sap\trans\bin\Tp_domain_<Sid>.pfl

M. How many types of transport request types?
     They are 2    one is released and another one is locked

N. Dev system to Qas, Qas system to Prod that is called transport request

O. Prod system to Qas system, Qas system to Dev that is called transport of copies

P. SE01 – transaction code is used for transport organization

Q. SE09 – transaction code is used for workbench request

R. SE10 – transaction code is used for customized transport request

S. Transport request naming convention?
    <Sid>k9<5 digits>
    <Sid>k9<5 digits>

No comments:

Post a Comment