SAP Transport system explained (for dummies)

Dmitry Kaglik

March 10, 2014

SAP

1 Comment

Aligning objects in different systems is one of the most challenging aspects of having a system landscape with several systems in it. SAP Expert previously wrote about a method of aligning SAP master data objects like Cost and Profit Centres or GL accounts.

The generic tool in SAP that allows movement of configuration between the systems is Transport System. Usually changes to configuration objects are only allowed in the Development system. Each change is then recorded in the Transport Request. Initially each modifiable transport request only contains links to the objects. These links may help you to monitor the history of changes.

You can move configuration between clients in the same system using transaction SCC1. It reads the links in the transport request, which is client-independent itself, in the source (original) client and makes corresponding changes in the tables or other objects in the target client.

During the release of the transport, the system collects the entire table record associated with that transport request link and packs it into the file. That file can be moved between the systems and then imported in the target system’s client.

Let’s make an analogy between Transport Requests and a house move.

You can imagine Transport Request as a box. When the box is open, you can put notes in it: “This box contains plates”. “This box contains books by Bulgakov and Adam Smith”. “This box contains cutlery and blue bed linen”. While boxes are in the preparation stage, you can continue changing the contents of the boxes, add something, and continue using the plates and cutlery.

Then the “man with a van” comes along. He reads all the notes, takes the necessary books, cutlery, plates and linen and packs them in the boxes. Then he seals the boxes and takes them to the destination. The boxes are opened and all the contents appear in the new place – the same as in the source.

The only difference between the SAP transport system and “man with a van” is that original items remain in the source SAP system. They do not disappear from there. You cannot do this with physical plates and linen, can you?

Related Posts

What is actually new in New FEBAN?

Dmitry Kaglik

October 1, 2018

SAP

No Comment

Share the knowledgeFacebookGoogle+TwitterLinkedinDiggemailSAP Expert has a very popular article already about the Bank Statement Process in SAP. That article is based on the “old” SAP transaction for post-processing of bank statements: FEBAN. In fact, FEBAN was already the second generation of such transaction, first of which was the single-screen FEBA. The difference between FEBA and […]

Read More

SAP Best Practice, Model Company, or story of A Dog and A Tail

Dmitry Kaglik

August 6, 2018

SAP

No Comment

Share the knowledgeFacebookGoogle+TwitterLinkedinDiggemailThere is no doubt that SAP accumulated a huge amount of experience in automation of business processes throughout the years. Some of these processes are easy to implement in SAP, others are not so. Many years ago, at least 20 or maybe more, SAP came up with an idea of “SAP Best Practice”, […]

Read More

1 Comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Search this site

Subscribe!

You can subscribe to our regular updates here.

Polls

Will you be happy to pay for the 3rd edition of the book FREQUENTLY ASKED QUESTIONS ON SAP FINANCE?

View Results

Loading ... Loading ...
Disclaimer and privacy policy