Transport landscape best practise

[Former Member]

I'm wondering if SAP has a best practise document on transport landscape planning.

SAP Help has pretty clear description about a standard 3 system landscape. But not document is found describing complext transport landscape considerations --- multiple ABAP development/test systems, conflict resolution between project landscape and maintenance landscape.

Any feedback is greatly appreciated.

[Former Member]

Hello Peter

we think that i we use " The TMS Quality Assurance Approval Procedure" we can not assure that all request that was imported in QAS system will be imported in production system, all in the same order that was imported in QAS system.

In relation with the best practices, we consult with SAP about our doubs about TMS, and they advise us a support service called:

SAP SOFTWARE CHANGE

MANAGEMENT SERVICE (SWCM)

ASSESSMENT AND BENCHMARKING

the content of this service is:

Efficient management of your software change processes increases the system stability. Furthermore it provides

transparency on current and past software changes and ensures compliance with legal requirements. With SAP

Software Change Management you can expect:

􀂃 Indicators for the quality of software change management in your system are measured. These indicators

include ABAP dumps, transport errors, consistency of the transport landscape and so on. Based on this

analysis areas of improvement are pointed out.

􀂃 Evaluation of your transport landscape topology.

􀂃 Evaluation of your transport strategy: single or mass transports, parallel projects.

􀂃 Packaging of changes into customer releases.

􀂃 Setup of a proper test environment and code freeze as basis for a reliable integration test.

􀂃 Best practices on how to manage support package implementation projects.

􀂃 Proactive implementation of SAP Notes, HotNews and TopNotes.

􀂃 End-to-end workflow for your change request management process.

􀂃 Usage of SAP Solution Manager in the software change process.

thanks

regards