AI-Generated Video Summary by NoteTube
SAP BASIS -- TMS (TRANSPORT MANAGEMENT SYSTEM) INTRODUCTION
SAP BASIS HANA ADMINISTRATION
Overview
This video introduces SAP's Transport Management System (TMS), a crucial tool for managing changes across different SAP systems. It explains the concept of SAP landscapes, typically involving Development, Quality, and Production systems, and the role of clients within these systems. The presenter details the types of data within SAP (client-dependent and client-independent) and clarifies what data is moved during the transport process – primarily customizations, modifications, enhancements, and developments, while excluding user master data and application data. The video also touches upon the three-tier architecture of SAP systems and the underlying database structure, differentiating between logical and physical data storage. Finally, it introduces the Change Transport Organizer (CTO) and its associated transaction codes (SC01, SC09, SC10) as the first step in configuring and utilizing TMS for moving changes between systems.
This summary expires in 30 days. Save it permanently with flashcards, quizzes & AI chat.
Chapters
- •A typical SAP landscape includes Development, Quality, and Production systems.
- •Within a system, clients (e.g., 100, 200, 300) are used for different purposes like development, unit testing, sandbox, quality testing, and training.
- •Development systems often have clients for customization, unit testing, and sandbox activities.
- •Quality systems are used for testing and training.
- •Production systems are for live business operations.
- •SAP data is categorized into client-dependent and client-independent.
- •Client-dependent data includes user master data, application data, and client-specific customizing data.
- •Client-independent data includes cross-client customizing and repository data.
- •Customization involves settings, which can be client-specific (local) or cross-client (global).
- •Modifications involve changing standard SAP-delivered programs.
- •Enhancements involve adding extra code to existing programs.
- •Developments involve creating entirely new programs, reports, screens, or tables.
- •These activities are performed on repository objects.
- •User master data and application data (business data) are NOT transported between systems.
- •Customizations (client-specific and cross-client), modifications, enhancements, and new developments ARE transported.
- •The goal is to move only the changes made, not the entire system's standard software.
- •Dummy data may be used in the Quality system for testing programs.
- •SAP software is stored centrally in the database repository, unlike other software where developers save files locally.
- •Moving changes between SAP systems requires a mechanism to transfer data from one logical database to another.
- •TMS is the SAP mechanism used to move these changes.
- •The process involves exporting data from the source system, copying it, and importing it into the target system.
- •CTO is the first part of TMS, activated via transaction code SE06 as a post-installation activity.
- •Activating CTO enables three functionalities: Workbench Organizer, Customizing Organizer, and Transport Organizer.
- •These functionalities record changes made in the system as transport requests.
- •Client-specific customizing changes are recorded as Customizing Requests (via SC10).
- •Cross-client customizing and repository changes (modifications, enhancements, developments) are recorded as Workbench Requests (via SC09).
- •Every change made in the development system is recorded as a transport request with a unique ID.
- •Transport requests act as tracking IDs for changes, similar to consignment numbers.
- •These requests are used to move changes from Development to Quality, and then to Production.
- •There are different types of requests: Customizing, Workbench, Transport of Copies, and Relocations.
- •TMS configuration establishes communication routes between systems (like setting up roads between cities).
- •After CTO activation, changes are recorded as requests.
- •Data is moved by exporting logical data into physical files (stored in the `usr/sap/trans` directory), copying these files to the target system, and then importing them.
- •This export/import process is the core of transporting data using TMS.
Key Takeaways
- 1SAP landscapes typically consist of Development, Quality, and Production systems, each serving distinct purposes.
- 2Within systems, clients are used to segregate activities like development, testing, and training.
- 3Only customizations, modifications, enhancements, and new developments are transported; user master data and application data are not.
- 4SAP stores changes centrally in the database repository, necessitating a transport mechanism like TMS.
- 5TMS facilitates moving changes between SAP systems by exporting, copying, and importing data.
- 6The Change Transport Organizer (CTO), activated via SE06, is the initial step to enable recording of changes as transport requests.
- 7Customizing Organizer (SC10) handles client-specific changes, while Workbench Organizer (SC09) handles cross-client and repository changes.
- 8Transport requests are unique identifiers for changes, essential for tracking and moving them through the landscape.