Skip to Content
avatar image
Former Member

STMS - Forward Transports into QAS Queue

Hey guys,

I want to configure our transport landscape.

DEV -> QAS -> PRD (virtual)

I create a transport domain with DEV and add QAS and the virtual PRD system into a 3 system landscape.

I configure the domain that all systems are in the same transport group.

But when I release a transport, it does not appear in QAS queue.

I really couldn't find any suitable guides.

When I change something in the profiles and distribute it, I can see, that the profile in QAS did not change!

But the transdir in all profiles points to the transport directory of DEV, which is right.

A transport group check shows that both systems creates the test files but cannot read it from the other system. I added on both servers the group SAP_<SID>_Global group to sharing/security of \\<host>\mnt\trans .

Can somebody help me? Provide me a good guide?

Thanks

Steffen

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Apr 10, 2017 at 06:11 AM

    Hi Steffen,

    Kindly check the TR release logs in Dev, confirm with infra team if the /usr/sap/trans dir is correctly mounted in all systems. If you login to QAS from OS level, do you see the Data/Cofiles of that TR?

    Also this you may have already done, but if missed, refresh the QAS STMS Queue screen and search for the TR again.

    Regards,

    Rupali S

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Rupali,

      I added <sid>adm to the access group on OS level. Now, I can access from QAS from OS level the folder via \\devhost\sapmnt\trans.

      The test says, the cannot access each other.

      This is TP_DOMAIN_L4D.PFL which is on QAS server in trans/bin

      #TMS:0005:DOMAIN_L4D
      #U
      #
      #---------------------------------------------------------------------------
      #Caution !
      #This file was generated by the Transport Management System.
      #Do not change this file using a text editor.
      #For further information please see the online documentation of
      #transaction STMS.
      #If this file was destroyed, it can be regenerated in the TMS.
      #To do this, log on to the domain controller (system L4D) and call
      #Transaction STMS. In the System Overview, you can distribute the TMS
      #configuration. This regenerates the file.
      #STMS -> Overview -> Systems -> Extras -> Distribute TMS Configuration
      #---------------------------------------------------------------------------
      #
      #
      wnt|TRANSDIR        = \\SAPL4D\sapmnt\trans
      #
      L4D/CTC             = 0
      L4D/NBUFFORM        = 1
      L4D/TP_VERSION      = 380
      #
      L4P/CTC             = 0
      L4P/DUMMY           = 1
      L4P/NBUFFORM        = 1
      L4P/TP_VERSION      = 380
      #
      L4Q/CTC             = 0
      L4Q/NBUFFORM        = 1
      L4Q/TP_VERSION      = 380
      

      This is DOMAIN.PFL which is on QAS server in trans/bin.

      SAPL4D
      00
      TMSADM
      DOMAIN_L4D
      Transport domain L4D
      L4Q
      System L4Q
      L4D
      System L4D
      GROUP_L4D
      Transport group L4D
      #---------------------------------------------------------------------------
      #Caution !
      #This file was generated by the Transport Management System.
      #Do not change this file using a text editor.
      #If this file was destroyed, it can be regenerated in the TMS.
      #To do this, log on to the domain controller (system L4D) and call
      #Transaction STMS. In the System Overview, you can distribute the TMS
      #configuration. This regenerates the file.
      #STMS -> Overview -> Systems -> Extras -> Distribute TMS Configuration
      #---------------------------------------------------------------------------
      

      But L4Q does not use the trans folder of L4D, so the transports don't appear in L4Q queue to import.

      Thank you.

  • Apr 10, 2017 at 11:05 AM

    Dear Steffen,

    Below SAP notes will be informative and helpful

    SAP Note 62739 - Configuring a central transport host.

    556734 - FAQ Transport: Setup and further information

    Regards

    Bharat

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 17, 2017 at 08:17 AM

    Hi Steffen.

    Transport request created local or is this target system mentioned? If it is local request it will not create the Co & Data files in the trans folder.

    Regards

    SS

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 21, 2017 at 06:31 PM

    Can you manually add the Transport to the QA buffer??

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 21, 2017 at 07:58 PM

    Hi Steffen,

    Try adding your SAP_<SID>_GlobalGroup groups to SAP_LocalAdmin on the transport host (i.e., your DEV system). This should setup the share and folder permissions required for the other systems to correctly access the \usr\sap\trans folder.

    I detailed a number of places to look for issues with moving transport hosts around in an old blog of mine; you might find some troubleshooting tips there to help: https://blogs.sap.com/2015/03/30/migration-of-transport-host/.

    Cheers,
    Matt

    Add comment
    10|10000 characters needed characters exceeded