Show TOC

 Transports (Software Change Management)

Use

During the Software Change Management process, the decentralized systems in the system landscape have to be supplied with transports from their respective mirror systems. You can link the control of these transports to the synchronization report runs.

Prerequisites

You are familiar with the system architecture supported by the Defense Forces & Public Security component.

You are familiar with the transport system in the SAP system. For more information, see SAP Library at Start of the navigation path SAP NetWeaver Library Next navigation step SAP NetWeaver by Key Capability Next navigation step Solution Life Cycle Management by Key Capability Next navigation step Software Life Cycle Management Next navigation step Software Logistics Next navigation step Change and Transport System. End of the navigation path

In Customizing for Defense Forces & Public Security , you have configured the settings for FTP communication in the FTP Server for Transports section by choosing Start of the navigation path Distributed System Landscape Next navigation step Systems and Connection Parameters. End of the navigation path

You can use Business Add-In /ISDFPS/SYNC_HANDLE_TP to adjust the transport mechanism to suit your own requirements. See the Implementation Guide (IMG) under Start of the navigation path Defense Forces& Public Security Next navigation step Distributed System Landscape Next navigation step BAdI: Adjust Transport Mechanisms. End of the navigation path

Features

Linking transport processing with the synchronization report enables the following transport process:

  1. Once tested in the mirror system, the transport requests are stored on an FTP server.

  2. In the next synchronization run, the transport requests are transferred to the decentralized system by means of FTP.

  3. The transport requests are deleted on the FTP server.

  4. The transports are imported in the decentralized system.

Alternatively, you can link certain individual steps with the synchronization report and trigger other steps in a different manner.

Example Example

For example, you can use a different transfer method (such as remote access) instead of the FTP transfer and link only the import step with the synchronization report.

End of the example.

For the storage and transfer of transport requests, the system expects the standard directory structure of the SAP transport system in the form usr\sap\trans\data\<transport request> or usr\sap\trans\cofiles\<transport request> .

Faults during FTP communication are documented accordingly in the application log. If transports are not imported successfully, IDoc inbound processing is stopped in the decentralized system.

Activities

In the ALE Synchronization application (transaction /ISDFPS/SYSTEM_SYNC), select the required options in the Shipments screen area:

  • Handle Transports

    You define whether transports are to be considered during a synchronization run.

  • Transfer Transports by FTP

    You define whether transports are to be transferred from the FTP server to the decentralized system during a synchronization run.

  • Transfer Transports Bef. IDoc

    You define whether the transports are to be transferred before or after the IDocs during a synchronization run.

  • Import Transports

    You define whether the transports transferred to the decentralized system are to be imported.