SAP has improved his Transport Management system to work Batter SAP improves its SAP Landscape.
Basic Organizational Measures
- Definition, digitalization of the end-to-end transport process or of the whole change process
- ensuring that no transport request (technical change) is issued without change request (organizational change)
- diversification of the transport types so that for projects and releases the suitable transport can be selected
- Replacing manual execution by automatic technical implementations
- no inconsistencies due to missing and/or incorrect interactions
- release processes are validated, executed and documented
- tedious routine tasks are automated
- Also operational customizing must be subject to a controlled change management process.
- Creating development guidelines and naming conventions to support change and transport management
- changes can be checked for consistency with respect to form and – in parts – content
- Definition of a company template – particularly useful if there are more than one development client
- centrally and company-wide implemented customizing settings can be protected
Validation of Transports
- Early detection and exclusion of risky objects from transport, e.g. NRIV objects (SAP number ranges)
- Formal validation of the transport objects with regard to project/support release and organizational unit they belong to
- ensuring that a transport request contains only related changes or changes for specific areas so that parallel project activities are not compromised
- code inspection based on system engineering, validation of the transport object´s affiliation
- ensuring that the development guidelines are followed and verifying – on the basis of naming conventions – that the code is related to one single business area
- Verifying, for example by running test imports, if all referenced objects which are not yet on the target system are transported
- Object-related customizing documentation such as owner, change, changed keys, including customizing versioning
- complete documentation, complete history (comprehensive life cycle of the customizing settings), traceability and audit trail
General Consistency Measures
- Content-related division of transport requests of multiple projects or maintenance requests
- consistent, project-oriented deployment; interdependencies of objects are understood, taken into account and controlled
- autonomy of projects in terms of change transport
- Opening and closing of the systems and clients should – whenever possible – be subject to an automated change process
- system-based monitoring of the change; it can be tracked at any time, when system changes were possible.
Horizontal Consistency-Ensuring Measures
- Ensuring the correct sequence when transporting customizing changes, workbench transport objects (programs and data structures), considering dependencies between workbench and customizing objects with regard to overtaking issues.
- No inconsistencies on target systems resulting from early arrival of objects (overtaker issues)
- Rollback functionalities and automated updating of systems and clients based on transport history (system or client copy) when systems are re-initialized, added or when changes need to be reset.
- Full transparency as to which transport orders apply to which system or client level. Executed transport orders can be undone at any time when unexpected problem show up or tests are not successful.
Vertical Consistency-Ensuring Measures
- Ensuring the correct installation order of all changes (transport requests from all SAP component systems such as SAP CRM, ERP, BW for ABAP and customizing, Java packages, portal configurations) before they are further processed on the target system. This includes all changes that have to be installed together, not by themselves via different SAP Transport Systems (SAP TMS).
- all changes belonging to a group are completely installed before the next organizational step is released
- Synchronizing and locking of company template customizing
- no inconsistent company templates in target system landscapes
- vertical distribution of these settings to all SAP component systems