SAP BASIS -- TMS (TRANSPORT MANAGEMENT SYSTEM) INTRODUCTION
Summary
TLDRThis video script delves into the intricacies of SAP's three-system landscape, detailing the roles of development, quality, and production systems. It explains the process of configuring and utilizing Transport Management System (TMS) for moving data between systems. The script covers client-specific customization, modifications, enhancements, and developments, emphasizing the importance of transport requests in tracking changes. It also clarifies the difference between client-dependent and client-independent data, and the significance of customization settings in SAP.
Takeaways
- 🌟 The speaker discusses a three-system landscape in SAP, which includes development, quality, and production systems, each serving different purposes in the software development lifecycle.
- 🔧 In the development system, typically two or three clients are configured for various purposes such as customization, testing, and sandbox environments, with client 100 being commonly used for development tasks.
- 🔄 The unit test client is used by developers to perform self-testing before moving their work to the quality system, ensuring that modifications and developments are correctly executed.
- 🧪 The sandbox client allows for research and development without affecting the live system, providing a separate environment for more extensive testing and experimentation.
- 📈 The quality system is crucial for testing the developments made in the development system before they are moved to the production environment, ensuring stability and reliability.
- 🛠️ Customizations in SAP can be client-specific or cross-client, affecting how settings and changes are applied across different clients within the system.
- 🔑 User master data is considered client-dependent and is not transferred between systems, unlike client-independent data like application data, which combines master data with transactional data.
- 🚫 Developers and end-users are restricted from accessing production and development systems, respectively, to prevent unauthorized changes and maintain system integrity.
- 🔀 The transport management system (TMS) in SAP is essential for moving changes from one system to another, such as from development to quality and then to production, using a logical export and import process.
- 🔧 The script also covers the technical aspects of the SAP system architecture, distinguishing between the presentation layer, application layer, and database layer, and how they interact with each other.
- 📚 The importance of understanding the different types of data and changes in SAP, such as modifications, enhancements, and developments, is highlighted, as well as the tools used for these tasks within the SAP environment.
Q & A
What are the three types of systems mentioned in the script?
-The three types of systems mentioned are development system, quality system, and production system, which together form a three-system landscape in SAP.
What is the typical client range in a single SAP system?
-In a single SAP system, clients can range between triple zero (000) and triple nine (999).
How many clients are generally configured in a development system?
-In a development system, it is common to configure two or three clients, such as a development client for customization, a test client, and a sandbox client for additional development and testing.
What does the term 'unit test client' refer to in the development system?
-The unit test client is a client within the development system where developers perform self-testing of their modifications, enhancements, or new developments before moving the transport request to the quality system.
What is the purpose of the sandbox client in a development system?
-The sandbox client is used for research and development (R&D) where developers can freely experiment and develop without affecting the main development and test clients.
What is the primary purpose of the quality system in the three-system landscape?
-The quality system is used for testing the developments made in the development system to ensure they function correctly before moving them to the production environment.
What is the difference between a three-system landscape and a three-tier architecture?
-A three-system landscape refers to the arrangement of development, quality, and production systems for different stages of development and business operations. In contrast, a three-tier architecture refers to the logical separation of a system into presentation, application, and database layers.
What types of data are considered client-dependent in SAP systems?
-Client-dependent data includes user master data, application data, and client-specific customizing data.
What is the role of the Transport Management System (TMS) in SAP?
-The Transport Management System (TMS) is used to move data, such as customizations, modifications, enhancements, and developments, from one system to another within the SAP landscape, for example, from development to quality and then to production.
What are the two types of customizations mentioned in the script?
-The two types of customizations mentioned are client-specific customization, which affects only one client, and cross-client customization, which affects all clients.
What is the significance of the 'CTS' setting during the post-installation activities in SAP?
-CTS, or Change Transport System, is important during post-installation activities as it activates the transport organizer, customizing organizer, and workbench organizer, enabling the recording of changes as transport requests and customizing requests.
Outlines
🛠️ SAP System Landscape and Client Configurations
This paragraph outlines the three-tiered SAP system landscape, which includes development, quality assurance, and production systems. It discusses the standard range of clients (000 to 999) and the typical configuration of two to three clients in a development system for different purposes such as customization, testing, and sandbox environments. The speaker explains the specific roles of development clients (100), unit test clients, and sandbox clients, emphasizing the importance of not moving developers or end-users between systems inappropriately. The paragraph also touches on the concept of client-specific and cross-client settings and customizations.
🏭 Understanding Three-Tier Architecture and SAP System Layers
The speaker clarifies the difference between a three-system landscape and a three-tier architecture in SAP. They explain that the architecture involves presentation, application, and database layers, which are used uniformly across development, quality, and production systems. The paragraph also distinguishes between different types of data in SAP: client-dependent and client-independent data. It delves into the concepts of customization, modification, enhancement, and development within the SAP environment, highlighting the importance of keeping developer access restricted to prevent unauthorized access to production data.
🔄 Transition of Data Between SAP Systems
This section describes the process of moving data between SAP systems, focusing on the transfer of customizations, modifications, enhancements, and developments rather than user master data or application data. The speaker explains that only changes made to the software, such as new developments or modifications to standard SAP programs, need to be transported through the landscape from development to quality and then to production systems. The paragraph emphasizes the importance of not moving business data between systems during this process.
📚 The Role of Customizing and Repository in SAP
The speaker discusses the importance of customizing and repository objects in SAP. They explain that customizing involves setting up local and global settings specific to a client or affecting all clients, respectively. The paragraph also covers the repository, which contains programs, reports, screens, menu options, and tables. It distinguishes between client-specific customization and cross-client customization, and the need to move these settings and developments between systems using the transport mechanism.
🔧 Transport Management System (TMS) in SAP
This paragraph introduces the Transport Management System (TMS) in SAP, which is used to move data between systems. The speaker explains that TMS is a crucial mechanism for transferring modifications, enhancements, and developments from the development system to the quality system and then to the production system. It emphasizes that TMS is not just about moving physical files but involves exporting and importing logical data between databases, which is a unique process in SAP compared to other software development practices.
🗂️ Database and Application Layer Details in SAP
The speaker provides an in-depth explanation of the database and application layers in SAP, detailing the types of data stored in each layer. They describe the user directory, service directories, and log directories found in the application layer, as well as the business data, SAP repository, and database repository in the database layer. The paragraph also explains the role of different SAP standard users and the importance of understanding the data flow and storage mechanisms in SAP.
🚀 Moving Customizations and Developments Through TMS
This paragraph delves into the specifics of how to move customizations, modifications, enhancements, and developments through the Transport Management System in SAP. The speaker explains that these changes are recorded as transport requests and are then moved from the development system to the quality system and eventually to the production system. The paragraph emphasizes the importance of understanding the types of data being moved and the process of exporting, copying, and importing within the TMS framework.
🔗 Configuring TMS and Understanding CTO in SAP
The speaker explains the initial configuration of the Transport Management System (TMS) and the activation of the Change Transport Organizer (CTO) in SAP. They describe the process of establishing communication routes between different systems for data transfer and the activation of workbench organizer, customizing organizer, and transport organizer functionalities after hitting transaction code SE06. The paragraph also discusses the creation of an initial transport request ID and the automatic recording of changes as transport requests for client-specific and cross-client modifications.
📝 Transport Request Types and Customizing Settings
This paragraph focuses on the different types of transport requests in SAP, such as customizing requests and workbench requests, which are generated based on the changes made to client-specific or cross-client objects. The speaker explains the settings that control the automatic recording of changes and the requirements for transport requests when making modifications to the repository or customizing data. The paragraph emphasizes the importance of understanding these settings and the transport request process to ensure proper data management in SAP.
🏢 Activation of CTO and Its Impact on SAP System
The speaker concludes the script by summarizing the activation process of the Change Transport Organizer (CTO) and its impact on the SAP system. They explain that upon activation, the CTO initiates the recording of changes as transport requests and the generation of an initial transport request ID. The paragraph highlights the significance of understanding the CTO functionalities and the process of creating, renaming, and releasing transport requests through the transport organizer.
Mindmap
Keywords
💡SAP System
💡Development System
💡Quality System
💡Production System
💡Client
💡Customizing
💡Modification
💡Enhancement
💡Transport Management System (TMS)
💡Transport Request
💡Workbench Organizer
💡Customizing Request
Highlights
Introduction to a three-system landscape in SAP: development, quality, and production systems.
Explanation of client configuration in SAP systems, typically ranging from triple zero to triple nine.
Common practice of configuring two or three clients in a development system for different purposes such as customization and testing.
The role of the unit test client in the development process for self-testing by developers before moving code to the quality system.
Description of the sandbox client for research and development purposes, distinct from development and unit test clients.
The necessity of having a separate client for quality testing to ensure the stability of developments before production.
Differentiating between development, quality, and production landscapes and the number of clients typically configured in each.
Understanding the concept of three-tier architecture in the context of SAP systems, distinct from the system landscape.
The importance of not moving user master data from development to quality or production to maintain system integrity.
Explanation of client-dependent and client-independent data, including user master data and application data.
Customization in SAP involves local settings, global settings, modifications, enhancements, and developments.
The restriction on developers and end users accessing production and development systems, respectively, for security.
Process of moving customizations, modifications, enhancements, and developments from development to quality systems.
Utilization of the Electronic Computer Array Test Tool (ECATT) for creating dummy data to test programs in the quality system.
The final move of changes from the quality system to the production system with the inclusion of original business data.
Differentiating between the roles of developers, functional consultants, and basis consultants in SAP system modifications and enhancements.
The significance of the Transport Management System (TMS) in SAP for moving data between systems.
Technical explanation of how data is exported from one database and imported into another using TMS.
The logical versus physical storage of data in SAP databases and the implications for data transport.
Configuration of TMS as a post-installation activity and its role in establishing communication routes between systems.
Activation of CTO functionalities such as customizing organizer, workbench organizer, and transport organizer after TMS configuration.
The process of generating transport requests for changes made in the development system and their subsequent movement through TMS.
Transcripts
[Music]
see uh
we'll be having
how many systems we are having here
three systems one is development system
second quality system third one is
production system
this is a three system landscape okay
generally you can have within one sap
system you can have clients from range
between triple zero to triple nine so
how many clients we configure generally
how many clients means in general we
don't configure more clients in general
in development system we used to
configure two or three clients first
decline for example I installed a
Creator mankind called 100 that is for
my development purpose you can say
customizing purpose second client unit
test client third client sandbox client
means in a development system you will
be having only three clients that
default lines are there triple zero zero
zero one zero double six will be there
but
occurred your business clients are three
what is development client so whatever
the customization whatever the
modification enhancements and new
developments you do you do in that
development Clinic
and you will be having another client
called unit test client
what is the meaning of this unit test
client means generally developers will
develop something some program
okay they have created a transport when
they modified they enhanced some
standard objects what happens obviously
it will create a transport request so
they have to move the transport request
to Quality client to Quality system
before moving that
what they do they do self testing for
that purpose they will move from this
development line to unit tester client
the developers will move their developer
efforts from one client to another
client within the same system for the
purpose of unit testing
okay they tested by themselves okay if
they are satisfied then they'll ask you
to move to Quality client they will they
will release a transport request then it
will come to Quality here the testing
will happen then to production and third
client is sandbox client sandbox client
means you can do any r d in this client
you cannot do all the rnds in
development and unit test line there
will be one separate client in some
organizations you will be having
separate system for sandbox
which entire system is different you can
do anything there in some organizations
you will be having one client
that is what a Sandbox line it is not
mandatory to have three clients okay in
general I am talking in general they
will be having development client and
unit test client and sandbox claim some
organizations will have only development
client some organizations will have
debit and you will test the client some
will have more than two also okay in
quality system they will be having one
client that is for testing quality
purpose quality testing purpose whatever
you developed in this development client
that will be here you do development
you are sending the developments to
Quality system
in a quality client in that client you
do testing for example you created some
new program you developed some new
program you modified some standard sap
program you enhance at some program so
you want to execute that program whether
and you want to check whether that
program is giving some positive response
on a proper response or not where you
check
for the purpose of testing only you have
quality system in quality system you
check that and in this quality system
only you will be having some more other
client called as training client for
example you want to give training to end
users will you give your production
system for end users no for training
purpose we use quality system only
so in general we will be having two
clients in quality one is 200 friend
second one is whatever the numbers you
can give any numbers these numbers are
not mandatory but I am saying Quality
Clean and training client I am saying
development client unit test client and
sandbox line number can be anything
range between triple zero to triple nine
triple zero zero zero zero double six
are default remaining
you can give anything between triple
zero to Triple A
and whatever you do you do all the
developments at 100 and move it to 200
and from there you move to production
system
here production client 300 client here
you do the business what landscape is
this it is a three system landscape I am
using three systems to do my development
quality and production arrangement of
your systems where you do your
development equality and production is
called as landscape for doing
development in quality and production I
am using three systems here so I am
calling it as three system landscape I
told you three system landscape is
different three-tier architecture is
different three-tier architecture is
what this development system should
follow 3D representation layer
application layer database quality also
presentation and application layer
database production also presentation
layer application layer data this is
architecture three tier architecture
this is how you are doing business
horizontal and vertical remember
okay three system landscape is different
three-tier architecture is different for
example if you have this 200 land here
itself quality client so 100 is for
development 200 is for Quality okay in
this system only you are having some
production claim that is two system
landscape if you do development in one
client quality in one client and the
production in one plane that is a single
system landscape so landscape is
different architecture is different
three tier architecture is different
three system landscape is different I
hope you got the point
in real time how many clients will be
having in one landscape in one landscape
means simple almost five to six that's
it not more than that
you don't have 50 clients no only in
development system two to three clients
quality two to three clients and
production one time mostly this is what
we have in our landscape what is this
landscape guys
system landscape this is
right what I am doing here in
development
client what I am doing
see you know this in database what type
of data we have we have two types of
data client dependent data client
independent data when it comes to client
dependent data we will be having user
Master data application data and client
specific customizing data we are having
two types of customizings one is client
specific customizing second one is grass
client customization customizing
customizing means what settings
so if I do this settings it will only
affect this particular client if I do
cross line settings it will affect all
the clients that is what the difference
so we have four technical words here
customize what you do in implementation
customization modification enhancement
and development customization means two
types of customizations are there client
specific customization cross clean
customization means settings I told you
country is built India you have to
select from that list you have to select
India currency INR okay Branch you have
to select that branch
like this settings is called as
customization in that customization we
have two things local settings global
settings
and the remaining three things are
modifications enhancements and
developments modification means what
where you do all these things means in
repository data
customization is only these two
modifications means or modifications
enhancements and developments you do for
repair
study means what your programs reports
screens menu options
tables everything if you want to do any
change in your program standard sap
delivered program then it is called as a
modification that's there is a standard
program you want to modify something
something to that program that is called
as a modification
where you do modification out of these
five things only into Repository
enhancement means what you haven't
programmed a report you want to add some
extra code to existing code means you
are adding something new to the existing
code that is called as enhancement where
you do that repository only
development means sap has delivered some
standard thousand programs you need
something new which is not present
in that software then what you need to
do you need to do the development of a
program or a report or a screen or a
table that is called as a development so
modifications enhancements developments
whatever you do where you do into the
repository objects customization where
you do
in the client specific customization
cross clean customization then what I
need to move from my development client
to Quality client
for example in development client I am
having some Developers evapors
the thumb rule of sap whatever the
software is what no developer should
have access to production no end user
should have access to development so can
I move for example this is my
development development client
for example I am having some developers
here can I move all the developers to
Quality in production
no
so this user Master data I don't move to
Quality from there to production
in development kind I'm I'll be having
different users in quality client I am
having different users in production
client also I'm having different users
so in development client what are the
users I am having developers some
functional people will be there basis
people will be there in quality link
testers functional people and basis
people no developers in production
functional people for doing the business
and the basis people to organize this
system to maintain this system and the
end users right do we have developers in
production system no so production
client no so every each and every client
will have its own users so sap is
restricting user Master data
to move from one system to another
system whatever the users you have you
have in that client only
user Master data is independent data so
what I'm trying to say here is what are
the things we move from developmental
into quality so do we move user Master
data from development to Quality
no no application data application data
means what
business data
the combination of Master data plus
day-to-day transactions so that
application data do we have any business
data in development trend why I am using
this development when I install the
software the standard software will be
there so whatever the customizations
modifications enhancements and
developments I want to do I am doing to
work to the software I am doing I am
making changes to software that's it I
don't deal with the business data here I
don't have any business data here then
there is no concept of moving
application data from development line
to Quality quality to production right
so we are not moving user Master data we
are not moving application data then
what we need to do
customization yes
our branch code
okay Branch name all these things are
local settings
and company name company calendar these
settings are global settings so we have
to move this customizations
modifications enhancements and
developments
simple customization means we have to
move client specific customization we
have to move class 9 customization
modifications enhancements developments
means what
not entire repository you move to
Quality system why
for example here also I am having same
software
whatever software here I am having here
also I am installing the same standard
software so why I need to move all
thousand programs which are delivered
from sap to Quality already they are
present there only what I move whatever
the programs for example I have done 50
modifications only that will move only
50 enhancements only that enhancement so
I have to move and 50 new developments
let's take example of 50. so that means
standard programs I have changing 50
standard programs I have changed
50 standard programs I am
enhanced
and these two are what already these 100
programs are in from repository only not
new things but this 50 year new
developments I am not having that
programs in this repository so I am
creating that so I have to move these 50
modifications this 50 enhancements this
50 new developments to Quality is the
person and I have done some 30 settings
local setting that's at 30 settings and
Global setting the 30. 30 global
settings 30 local settings and 50
modifications 50 enhancements 50
developments only these things I need to
move to Quality client
quality system yes or no
whatever your software here I am having
here are the same software I'm
installing why I need to move entire
thing only whatever the changes you have
done that changes and that modifications
and that enhancements and that in new
development only that thinks you move
from customizing also whatever the
changes you do local changes Global
changes the only that things you move to
Quality
from here we move to production client
this is what we do
in our landscape why we are having
development system is for doing
customization modification enhancement
and development we need a client in that
client we login into that client and we
do all the modifications enhancements
developments and customization finish
my development work is finished now I I
need to move all the changes to Quality
claim okay how we change how we move
I'll tell you
from quality client I need to test them
so all my local settings came global
settings came and my notifications
enhancement development everything now
these two systems are same
you have written some payroll program
new Pro payroll program here you want to
test that program whether that program
is executed successfully or not
then how you run that payroll program
without any employees data
so in quality system do we have any
business data
do we have any application data in
quality client
no no
no so what we do we have that ecat and
Cat settings in client settings
by using that scripts electronic
computer array test tool computer edit
test tool by using that script we create
some dummy application data means dummy
business data
customers data the transactions customer
names the transaction employees and
price transactions by using that dummy
data we run these programs we execute
that program okay all the programs
executed successfully everything is fine
then I'll move that local settings
global settings here also I install the
same system same software
only these changes whatever I have
performed here not present in Quality
quality production system so whatever
the local settings whatever the global
settings and modifications enhancements
and the new developments I'll move to
production now all the systems are same
entire my landscape is same
here in production client add my
original business data and by using that
business data I start running my
business this is what
is called as landscape
so only what are the things you move
from development to Quality quality to
production means only three things only
four things customizations modifications
enhancements and developments
customizations means two things are
there local customization client
specific customization customization
modifications enhancements developments
means from the reports your programs
reports screens menu options we'll see
what we have in repository exactly okay
these things we move from development to
Quality quality to production but we
don't move any business data application
data no user data remember out of this
five datas we only move client specific
customization grassland customization
and repository that's it we don't move
user Master data we don't move
application data
is it clear
yes or no yes
what we have in this repository
grassland customizing
see
the user Master data means what
every C I am having how many clients
here two clench this is one client and
this is second claim
every client has user Master data
application data and client specific
customizing data by its own this client
is having these three this point is
having this three but cross client
customizing data reposition data are
common for this client and this client
two clients what is user Master data
user names and their logins their
passwords address everything is called
as user Master data application data
means combination of Master data Plus
transactional data we have discussed all
these things
client specific customization means the
specific to this client settings these
settings are special to this client
crash claim customizing means printer
settings your sap calendar your company
codes your company name your company
rules and education these are all comes
under class client customers means if I
change company calendar it will affect
this client and this client
right
if I change branch code it will only
affect this client if I change here it
will only affect this claim so this
customization are
two tips local customizations Global
customizations and when it comes to
repository what are all the things we
are having in depository means programs
reports functional modules screens
tables and a data dictionary all these
things you know repository along with
that you will be having some tools above
editor tool objective browser functional
Builder screen print screen Builder menu
Builder Okay menu painter and all the
compilers about interpreter screen
interpreter calling all these things
these are all runtime environment I'll
discuss this later okay do you have any
doubt here
I am having in all these it presentation
layer or application layer database
layer all these things
presentation layer application layer did
we have three layers right in which
layer I will get user Master data
application data client specific
customers
data tell me
um
database in database layer only I'm
having all these things right
see
at presentation layer what you install
symbol geoi graphical user interface
file at application layer what you are
having
you are having simple user directory in
the directory you are having profile
directory kernel directory transport
directory work directory and logs all
the sap logs along with that
some sap standard users are there sidadm
sap Services ad users sap Services
schema service host agent is host exe
right all these host Services some ports
are there and MMC all these things you
are having it application layer
in the database layer what you are
having sap Repository
business data and
database reposted
in this
do you have sap Repository
yes all the programs reports screens
menu options tables everything is there
right
do how business data here
yes yes application data so we have it
so I have business data I have sap
repository along with that you will be
having database repository means
whatever the database software you use
that data also will be there this is how
your sap system presents a presentation
layer will be having GUI software at
application Level you will be having
user directory users Services ports MMC
all these things stuff
and at the database level you will be
having business data sap repository and
a database repository if you are using
Oracle Oracle related software will be
there you are using Hana related
software will be there I'll give you
that
see sap repository means your programs
reports screens menu options everything
and business data means all your
application data Master data press
transactional data and database
repository database related software
these all things we'll be having in this
database at application Level we will be
having all the directories kernels will
be there transport data will be there
all the territory profile directory and
all the logs
any doubt here
clear
clear so for the first time you are
seeing all these things right
yes sir yeah
okay so how's it sorry I have it ready
yes Harish
yeah another base is consultant uh are
we working on this repositives a
repository is last one oh no no
I'm coming there only I'm coming
okay
you don't do all these things you don't
deal with this programs report screens
menu options all these things are
related to your these tools about editor
these developers will do who will do
modifications
who will create a new programs
modifications enhancements and the
developments everything is done by your
developers only
all these things modifications
enhancements
and the development who will do all your
developers
and this customizations mostly
customizations will be done by your
functional people and they know that a
branch code company code and plant
numbers all the tax relations everything
they know right we don't do
customization only little bit few things
are there mostly majorly functional
considers we do the customizations
May and entire modifications
enhancements and developments is done by
your developers no basis Consultants
remember this
fine
thanks for asking
you should know what exactly we are
doing what is our role here before going
to TMS what exactly data we have in
database application Level and
presentation layer and what data we need
to move why we need to for example you
want somebody asked you client specific
customizing data we have to move from
development to Quality so you should
know what is exactly client specific
customization
and developments we are having few
developments please move the
developments to Quality as a base is
consultant you should know what is
exactly meaning of development
modification enhancement that is the
reason I'm explaining you all these
things I'll come to that okay
Harish is it clear
yes yes yeah
okay
now
come to the point
you know from development system we do
all the developments quality we test
their production we do the business in
production
how you move these all changes from
development system to Quality quality to
production
that is what my point
so in sap there is a mechanism called
TMS transport management system
transport management system by using
this mechanism we move the data from
development system to Quality from
quality to production by using which
mechanism TMS transport management
system
so what is exactly this transport
management system
means
for example to understand that concept
you should know
other softwares also generally for
example some software is using three
tier architecture some Java based
application
so where you install application at
which layer you install application
generally
at application layer only
perfect
the database layer what you have in
general
that the database software will be there
and your business data why you are using
database to store your business data
your software will be at application
layer and your business data will be
businessly business layer database layer
okay fine from presentation layer users
will log into application that
application will connect to the database
and fetch the data application again
gives the users the in end uses the data
this is what happens in general sap is
somewhat different we discussed that
already
today also we'll discuss that okay for
example
there is one application which is
developed on Java platform this
application is developed on Java
platform
there are four developers are there they
are logging from their respective
laptops these four are their end user
laptops
there are Developers
so they want to do they have given one
task to develop a develop a single
program
so what they need generally in their
laptop
they need some tool like Eclipse git
Docker Tomcat these are all developed
tools SDK software development Creator
J2 SDK these are all small small tools
by using that tool that tool will have
what
the tool will have program Builders
screen Builders interpreters and Library
files everything in that for example
Eclipse tool is there I have installed
that Eclipse too
I have installed Eclipse tool where it
is installed in Harish C drive design
now Harish wants to write a program
okay he will open this Eclipse tool
there will be some program
Builder will be there he will open that
developer toolkit and he will write a
program and save that program
where it will be saved
in that tool only in that C drive
Eclipse folder that program will be
saved the same way all these developers
will have some developer tools
that data whatever the data they are
generating they are creating it is
saving locally in their local desktops
did you got the point what I am trying
to convey here
yes yes
now these are our physical files right
later I'll put a pen drive here by using
any of the mediums I'll move all these
programs to mice application software
here it has two effect these are
physical files they are looking saving
locally
fine
now come to this
here it is sap
I am having sap developer for our webs
what software
we installed desktop
whatever end users disturb
GUI
GUI just a GUI
when they login into the system
using for logins purpose okay then login
into the system
now this user this Harish
wants to write a program
do Harish have any program Builders any
development tools here in this system
installed
no as sap developer no
if you want to write a sap about program
from where he is getting that screen
just he has to login into sap and hit
some SC 80r c38 anything
so here C about editor object so what
are the things we are having here about
editor object browser functional Builder
screen painter menu painter if you want
to build a new screen new menu new
program there are some tools
so you call
some T code you are getting that screen
from your
Sap's repository means from this
database you are getting that screen
okay you write some program
finish
and you want to execute that program to
execute that program when you say f8
execute there are something called
about interpreters screen interpreters
call interfaces these are runtime
environment
executors for compilation of the
programs we use these things from where
you are getting all these compilers
from the database only from this
repository only means your developers
toolkit double compilers Library files
everything you are getting from this
repository to your screen
you don't have anything here just you
are opening a screen
from where you are getting the developer
program screen program Builder screen
Builder page builder some hero from here
from Repository you're writing some
program and you're compiling from where
your compilers are getting from here
only and you say save where it is going
again it is going into your repository
only right
if you create a new program where it
will be saved in about bench
new program will comment here new report
it will be saved in your repository only
new page new screen new menu whatever
you do it will be saving in your
repository limits your developments
your new developments your modifications
enhancements everything saving there
repository means in sap whatever a
developer do anything
it is finally saving centrally in the
database unlike locally in the their own
desktop
you got the difference between these two
if other developers do something they if
they build some program it is saving
into their local desktop later I am
copying that files into my application
but when it comes to sap
it is directly
to calling from your repository only if
you write something when you say save it
is going and sitting in your repository
only it is not saving it your local
desktop nothing will be there
you got the point
in sap the data is saving centrally in
other softwares the data is saving
locally
the developers efforts will save here
this developers efforts will save here
but when it comes to sap it is centrally
saving into your
centralized database
here with this
okay our sap software is Market
application layer
only at application layer you'll be
having that.exe Financial dot dll files
users kernel only the user data only
these things you have all the programs
reports screens menu options everything
in the database only so in sap the data
is saving centrally in the database
unlike other softwares locally at the
developers desktop
no fine these all developers have
developed some programs into your
development database now I want to move
all these modifications enhancements and
new developments to Quality system from
this database to another database
yes are you clear with this
development to database to qualitative
can I draw the image otherwise
foreign
see this is my development database from
this database I need to move to Quality
this is my development system
this is my quality
I have done all the changes here in this
standard software I have done some
what I have done some modifications I
have done
modifications enhancements and new
developments I need to move all these
changes to this database
so this database through this database I
have to move now tell me what is
database
database is a logical it is not a
physical one
what happens actually when you install a
database physical where your data is
saving in database for example see this
is my hard disk boss
this is my 500 GB hard disk
500 GB hard disk
so in this hard disk I need to install
database software
database
software when I install this database
software while installing it will ask me
what is your database size I'll say 300
gig 300 GB so what it will do it will
occupy 300 GB of space from your
hard disk
and within that hard disk it will create
some logical partitionings
logical partitions
in the form of tablespace is something
whatever you see
within that hard disk it will create
some logical partitions and it will
organize your data in a structured
manner so similar data data at one place
similar data table set one place
now now this is where my data is saving
actually
this 300 GB belong so this hard disk
only
but physically it is saving a hard disk
but logically I am segregating my hard
disk into different different data units
different different tables and I'm
arranging my data into these tables so
logically I am saving my data in this
database am I clear
logical means can you touch that logical
one
it's not real it's a logical model so
how can you move these programs from
this logical database to this logical
database
you cannot touch that when it is logical
if it is a hard disk I can bring this
hard disk to this hard disk but it is a
logical one your tables are table spaces
in database are logical partitions
within your hard disk you cannot touch
that then how can you move the data this
logical data from this development
database to Quality database
so here we use mechanism called TMS
transport management system what we do
here
for example this is my development
system
this is my
Dev system this is my quality system
from development database what I do I'll
export the data
I'll export the data for example I am
having some three programs here
I'll export this program logical to
physical where I am getting will be
having one directory called trans
directory USR sap trans that is a
transport directory under that we will
be having one profile and data file
we'll discuss about these things so when
I export the data what happens
and three data files I am converting
this logical data into physical format
now I'll copy this profile data file to
Quality Systems user sap transdirector
will be within in quality system also
quality profile and data file now from
here I'll import
from Source database I'll export
from Source database I'll export from
here
from database level to OS level I'm
exporting
from application Level from
two database I am importing so exporting
and importing what is that
in transport what you do was
transferring the data transport means
what export
less importantly now
exporting and importing is called as a
transporting so like that I move the
logical data from one logical database
to another logical database how I am
doing that by exporting this logical
things so when I export what happens it
will convert this logical data will be
converted into physical files now I'll
copy that physical files to Quality
system CSR sap trans directory from
there I'll import into this database
means logical to physical physical to
logical so export plus copy plus import
export place what I am doing
export Plus copy
plus import that is what your TMS
transport management system
why do you don't have this concept
anyway in sap only we are having this
why you have to move the data from one
logical database to another logical
database if my software is here in the C
drive if I install my software here I
can copy that files to this location
this C drive but my software is not
storing at application Level anymore my
software is saving where in the database
from this database I need to move to
this database that is the reason I am
using this export and import mechanism
that is
only called as transport mechanism TMS
TMS is a tool through which we move the
data from one database to another
database one system to another system
how in a back end we are doing what
exporting copying and importing
that is what your TMS
from here I need to export from here I
need to import from where I am meeting
this these two physical files I need to
copy to this
I'll show you that
what so this system is having a Saturday
and another system also will have user
directory at application Level so from
database level to application levels
transport directory from database to
application Level I'm exporting and from
application to application I'm copying
and from here I am importing into this
database database from quality also same
to production like that I am moving my
repository whatever the enhancements
modifications customizations and
developments from development database
to Quality database from quality
database to production database
is it clear
yes sir
now come to TMS
you know the concept behind the TMS what
exactly DMS why we use TMs Concept in
sap
now to understand the TMS concept I say
this is a huge concept actually I
segregated this concept into three parts
one is change transport organizer second
one is transport TMS CTO TMS and TP
tools CTO means change transport
organization TMS means transport
management system and TP tools means we
use some tools for exporting and
importing we use two tools called the
tp.exa and r3trans.exe how they work
we'll see later so when it comes to CTO
we'll having three T quotes sc09 AC 10
SC 0 1. import
so we will see CTO today change the
transport organism what is this CTO
when you install your system
when you install your system for example
you are having some development system
quality system production system
three systems are there you have to
configure TMS
you have to configure TMS first if you
do TMS configuration between these three
systems I want to move the data from
development system to Quality quality to
production for example if you want to
move some package from Hyderabad to
Vijayawada
between you are having suitable right so
Hyderabad to suryapad surabay to
Vijayawada what you need actually if you
want to move the data move some
transport you need a Road Transport
facility so you have without any
transport facility can you move the data
from Hyderabad to Vijayawada
no closer so you should establish the
route between
Hyderabad to Vijayawada that route
establishment that configuration is
called as TMS configuration we need to
configure TMS between these three
systems means it will configure some
routes there by using that rods we move
the data from one system to another
system by using TMS concept
so when you for example now I am having
three different different systems I
don't have any relationship between
these systems three different individual
systems when I configure a TMS what
happens the communication will be
established between these three systems
how we establish that communication
we'll see the TMS configuration tomorrow
now as of now so when you install your
system before configuring TMS as a post
installation activity what we do we hit
it before configuring TMS we hit one key
code called se06
sc06 as a post installation activity we
hit sc06
before configuring TMS you have to
configure TMS to move the data before
configuring TMS what we do we hit SE 060
code what happens
so it will ask you post installation
actions for transport organizer
so you say standard installation
database for example if your system is a
fresh installation you go with standard
installation if your system is result of
database copy or migration you will come
to know what is this exactly so now my
system is a fresh installation so
selected the standard installation and
say perform post installation actions
do you want to reinstall CTS CTS means
change transport system that is what TMS
both are same yes
processing after installation completed
configure TMS now it is asking to
configure TMS what happens when I hit
this se06 and say perform postalization
actions what happens in a back end in a
back end there are some three
functionalities
will be activated what are the three
functionalities means one is workbench
organism customizing organism and third
one is transport organism
when you hit this sc06 these three
functionalities will be activated from
this point onwards
in your database if you do any changes
that changes will be recording as a
transport request
if you do any client specific
customizing changes means
if you do any client specific
customizing changes it will be recorded
by your
customizing organizer as a customizing
request se10
if you do any
cross client changes crash line changes
means what
grassland custom this and this if you do
any modification if you do any
enhancement if you do any development or
if you do any Global setting changes if
you do if you touch anything from this
and this it will be recorded by
workbench organizer as a workbench
requester
we are having transport request concept
you know what is transport request
exactly we already discussed that but
every change whatever the changes you do
in your development will be recorded as
a transport request the transport
request is having one unique number
we discussed that Sid K9 lag 2 that
unique number will be assigned for every
change whenever you want to
transport something for example if you
go to Career shop and you give some
person
what they'll do they will give you one
Consignment number tracking ID right
that for that package that ID will be
assigned so you can track that package
destinations by using That Consignment
number right the same way whatever the
developments modifications enhancements
you do in your development system they
all will be regarded as a transport
request each and every change will be
recorded as a transport request and by
using the transport request only we are
moving the data from development system
to Quality quality to production
so
if you do any client specific changes it
will be recorded by customizing
organizer as a customizing request we
are having different different types of
transport requests one is customizing
request second one is workman's request
third one is relocation fourth one is
transport of copies we'll discuss that
so as of now today we will see two
transport requests two types of
transport request one is customizing
request second is workbench request
customizing request means if you do any
changes to your client specific objects
that will be regarded by customizing
organizer as a customizing request
if you do any class client changes that
will be regarded by workbench organizer
as a workbench request when if you
activate the CTO
you have to hit c06 and say standard
installation perform post initial
activities when you say this what
happens from this point onwards these
three functionalities will be activated
what are the three functionalities
customizing organizer and transport
organization in your database
from that point onwards whatever the
changes you do in your database will be
recorded as a transport request whether
it may be a workman's request whether it
may be customizing request and at the
same time
it will generate a initial transport
request ID One Transport request ID will
be created for example Dave K9 lakh
something
my stud is what Dev okay some 9 lakh to
initial transport request ID will be
generated
from next to change it will create
another change request Dave okay 9 lakh
four
if you do any other change it will
create another transport like that each
and every change you do in the database
will be recorded as a transport request
whether it may be customizing request
otherwise it may be workbench request if
you do changes to Trend specific
customizing data it will create
customizing request if you do changes to
classline customizing or repository data
it will create workbench request is it
fine the naming convention will be same
for customizing requested different
naming convention workmanship no naming
convention will be same numbers are one
by one it will generate automatically
and in that request if you are
customizing requests fewer workability
request
is it fine
and when it will create customizing
requests to create that customizing
request in your client settings
in your client settings you should have
this setting remember this
for example 200 languages for changes in
transport client specific objects
automatic recording of changes if you
opt this setting
then only if you do any client specific
changes it will be regarded by
customizing request
if you do changes here client specific
customizing and your setting is this
automatically recording of changes means
it will create which request
customize your request of equipment
request
customizing requests
this setting changes to repository into
grassland customizing if you do this
changes grassline customizing and
repository changes
it will record as
performance
so if you allow changes to cross
repository and Crossland customizing
allow
you may allow
and when you say when you touch anything
to your repository and graspoon
customizing it should be required as a
transport request remember for client
specific objects it is asking you
automatically recording of changes are
changes without recording means if you
have this setting it won't record as a
customizing request if you do if you
change customizing client supposed to
customizing changes even though it won't
record a transport requests why you have
this setting
but if you have this setting automatic
recording of changes then it will create
customizing request
for client specific changes it is asking
for can I record don't record
but for class client changes it is not
asking you can I record or not if you do
any changes to reposition customizing it
should be required as a transport
request
for the point
if you do any changes in grassland
customizing data or repository database
if you do any modification through
standard program any enhancement or
standard program any new development it
will prompt you for workman's request if
you do any changes global settings it
will prompt you for workman's request if
you do any changes in client specific
customizing data requests
yes when you have
um
if you have this setting it won't record
as a transported Bill if you do any
changes here it won't require as a
transport request if you have this
setting automatic recording of changes
it will prompt you for a customizing
request
so when you hit sc060 code these three
functionalities will be activated what
are the three functionalities
whatever the changes you do in database
if you do client specific customizing
changes customizing organizer will
require as a customizing request if you
do grassland customizing changes and
repository changes workbench organizer
will requirements request so customizing
organizer is C10 workbench organizer is
sc09
and what is this a transport organism by
using this transfer you see Zero
actually three are same T quotes see if
I hit all the T quotes
sa01 observe the chain
sc01
sc09
same
SC10 AC 10.
same you are having four options
customer request workman's request we
are having four types of requests
customizing request workman's request
transport of copies relocation so all
these three T quotes are same but if
somebody asks you what is the difference
between ac09 AC 10 and C10 a c09
organizer so it will record grassland
customizing changes and repository
changes
okay
transport organization
so by using this you can create a
transport you can rename a transport
it's mute
you can create a transport request you
can rename a transport request you can
release a transport equation only that
change
ac014 it is transport organizer you can
create a transport request you can
redeem rename a transport request you
can release a transport request foreign
customizing changes repository changes
this will record
client specific customizing changes and
sc01 is correct
to create a transport request to release
a transport request to rename a
transport request this is what your CTO
so what is CTO change transport
organizer by hitting ac06 as a
personalization activity we activate
this scto
if the CTO compressor three things ac09
AC 10 and sc01 and from when you
activate this it will generate a initial
transport request ID for the first time
from that point onwards whatever the
changes you do in your database that
will be recorded as transport request
whether it may be customizing request
whether it may be workman's request if
you do client special customizing
changes it will regard as a customizing
request if you do report study changes
and changes it will requirements request
is it clear
you know
yourself
any doubts
foreign
関連動画をさらに表示
Video 01 - SAP S/4HANA Production Planning (PP) Module training - Introduction to SAP and PP
Communication in Client–Server Systems-Operating Systems-Unit-2-20A05402T
SAP S4HANA BASIS 2
SAP BASIS --TMS (IMPORT PROCESS)
ICT Infrastructure & Information Security 1
HttpServletRequest and HttpServletResponse Theory
5.0 / 5 (0 votes)