Convert standalone Transport System to Exportable Change Requests

[former_member323486]

Friends@SAP Community:

  I have a Sandbox which I set up as a standalone Transport System in which some consultants want to work. Now I want for them to be able to write their change requests to /usr/sap/trans, so I can later copy the cofiles/data to DEV/QAS and import those there.

  My problem is the standalone config does not write the Change Requests to /usr/sap/trans/cofiles and data. I read that the only way to make change requests writeable at /usr/sap/trans is to create a route in STMS but I don't want to change my transport routes to involve DEV/QAS. I thought if I created a new mandt(client) on the same Sandbox then I could create a route to point the change requests there, this just to make the Change Requests writeable since I would import those into DEV, not the new client. I still haven't found a way to do this; do I have to delete the whole TMS config and start over??

Thanks for your advice, rgds.

Claudio

[JPReyes · Accepted solution]

Whats you SCC4 settings?... you should be able to create cofiles and datafiles from a standalone system as long as TMS is configured to do so.

Regards, Juan

[former_member323486 · Accepted solution]

Hi Juan, thanks 4 reply,

SCC4 has automatic recording of changes,

Changes to repository and cross-client customizing allowed.

When I released a transport request of a program written to validate the standalone it did not write any logs. It did not fail, it has status "Released", but did not write logs, nor cofiles or data.

Thanks, rgds.

Claudio

[JPReyes · Accepted solution]

You must be releasing them as local requests... make sure you are not using package $TMP

You could also try adding a virtual system to your TMS route so you can have a consolidation route.

Regards, Juan

[former_member323486 · Accepted solution]

Thanks Juan, that did the trick.

Best regards y que estés bien amigo.

Claudio

[JPReyes · Accepted solution]

You're welcome/ Saludos!

[former_member323486]

HI Juan,

   Strange things have been happening. In order to have content exported to /usr/sap/trans/data and cofiles, I have to create copies of the change requests and add SBX as target.

However when I imported these to DV1, the change request had another program, not the one that was originally written to test the TMS mechanism.

So I still have the problem of not being able to write the CR's to /usr/sap/trans when they are first created....

Thanks for any further ideas, rgds.

Claudio

[former_member189725]

For any object to be transportable , the first thing is that it should be a local object meaning that object should not belong to the development class/package $TMP. The next thing is that an object should belong to a development class/package which is assigned a transport layer(This assignment is done using SE80). Next the transport layer should be used in a transport route (typically the consolidation route) in STMS.

Now a particular system(typically the dev system where transports originate) should have a target defined . The target can be a system or transport target group (which is basically a feature of extended transport control). The route to the target must have the transport layer assigned which is also assigned to the package/development class.  If the above conditions are fulfilled , when you create a transport request which has a transportable object , then  you will be able to transport the object using the SAP transport mechanism. Also when a transport request has a target system configured using STMS routes , only then when you release a request a data and a cofile is generated . Else it will not.

Regards

Ratnajit