ChaRM- How Do We Ensure Transports Are Moved To Prod In The Correct Release

[Former Member]

If we have a project that would last 7 months and we start creating Transports during one release cycle, but don't move it to production until the following one, how do we prevent that this is not moving too early? If testing approval is recorded too early, it would automatically go with the first release. If we don't input Testing Approval until it's ready to move, the object is locked by this Transport, which is not desirable either as another Developer may need to begin making changes. What does SAP recommend and what do other companies do?

Thanks,

Karen

[TomCenens]

Hello Karen

If you have big projects that are intersecting for the same SAP system landscape and you want to keep the changes seperate what is often done is create a second line in that SAP system landscape and then retrofit functionality can be used.

Information on retrofit:

Service Market Place -> SAP Support Portal -> SAP Support Infrastructure -> SAP Solution Manager -> SAP Solution Manager Enterprise Edition -> Build & Test, and Deploy -> Retrofit

extract from thread:

You would have DEV --> ACC --> PRD and another line DEV --> ACC --> PRD for example.

Retrofit functionality in Solution Manager 7.0 does not work automatically in all cases so it does present some challenge.

I have heard however that the retrofit functionality will be seriously expanded in Solution Manager 7.1 and that there most cases can be retrofitted automatically.

Kind regards

Tom

[Former Member]

Tom, Thanks