SAP transport (otherwise it is called a request) packet data, which is used to migrate from one SAP system to another. The package can vary from driver to printer to a client. Such transfer can be regarded as “update” in the system with the difference that the requests for transfer created by the users performing various settings. Requests can be kartirovanii also from external systems.


The transport system consists of several types of files:

  • Data files – direct data that will be migrated
  • Cofiles – various technical information about the query and a list of steps that you must perform to migrate
  • Profile files – profile settings
  • Transport log – log, trace, statistics
  • Support packs – various files for the updates
  • Bin Folder – configuration files of the transport system


The majority of the time, the transport system is used to transfer settings to a production system. Productive system on the concept of SAP cannot be used for development and testing of various modifications, therefore, SAP has developed the principle of landscape systems (three of the same system with different roles):
1) Development System (DEV) – for setting up and development
2) Quality Assurance System (QAS) for mandatory testing and adjusting all of the changes for subsequent transfer in productivity
3) Productive system (PRD) – a system for user data. Changes to the production system only after mandatory testing.

One of the biggest shortcomings of the transport system is the inability to roll back changes. After the transfer request changes will take effect and if for any reason ceases to operate any function, the only way to return everything to its original state is to prepare a “correction request” and likewise transfer it to a production system.

Despite this shortcoming – the principle of the productive system updates, built on the basis of the transport system is quite effective and allows the system to operate with minimal downtime.