Purpose Use the SAP transport system to transport table and screen layouts and filters between SAP systems |
Solution
The content of the first key column "RELID" in the two tables is as follows:
The next column "ID" then contains the class name, the table or screen name and the layout or filter name. Here are the details. We create a transport request with transaction SE01 and add the "R3TR " TABU" lines for the two tables: ![]() Next, we click on the key button in the "Function" column for table /S10/LAYOUT: ![]() Doubleclick the first empty line so that you can enter the table keys that are to be transported. If you want to transport all existing layouts and filters, enter "*" in the "RELID" column: ![]() The same procedure for table /S10/LAYOUTT; here you enter "*" in the language column "SPRAS": ![]() Save the transport request, release it. This will transport all existing layouts and filters from one SAP system to another. If you want to transport individual layouts and filters, the procedure is the same, but we need to enter the correct keys instead of “*”. The key structure is somewhat technical and the best way to enter the correct keys is to copy them from the table content display in transaction SE16. Let's assume we want to transport a table layout "/STANDARD": ![]() In addition to the layout name “/STANDARD”, we need the table name defined in the ABAP program, which in this case is “ALLORDERS”: ![]() We start transaction SE16 for the table /S10/LAYOUT and enter "TL" for "Table Layout", the table name "ALLORDERS" and the layout name "/STANDARD" ![]() SE16 now display one or several table rows. If more than one row is displayed, these can belong to different classes, as the same table name can appear in more than one class. You must select the correct class. Also, there is usually more than one row for the same table layout definition as it is split into consecutive rows for technical reasons, which increases the value in “SRTF2”. You can click on each of these lines as the key fields before the index column SRTF2 are the same. We doubleclick on the first line and display the details, showing the technical layout ID: ![]() Copy the ID of the table layout into the transport request and add a * at the end: ![]() This entry will transport the table layout "/STANDARD" of table "ALLORDERS". Now to the table filters. Let's assume that we want to transport all existing table filters for the “ALLORDERS” table. In SE16, still table "S10/LAYOUT, we enter "TF" for "Table Filter" in RELID and the table name "ALLORDERS" in TABLENAME: ![]() Two lines are displayed, one with an ID ending with “OPEN10” and the other with “OPEN5”: ![]() This corresponds to the two filter definitions for the “ALLORDERS” table in the S10 application: ![]() The ID “/OPEN10” or “OPEN5” is displayed in the filter definition dialog in the S10 application: ![]() We now copy the ID value into our transport request. As we want to transport all filters, we leave out “OPEN10” or “OPEN5” and replace them with an “*”. To transport individual filters, use the complete filter ID, as shown in SE16, and then the last “*”. ![]() Finally, the transport of a screen layout. Let's assume that we want to transport the two screen layouts “Info” and “Standard” of a particular screen: ![]() Look in the ABAP program to find the corresponding layout name, here “matinfo_layout”: ![]() Enter the first part "matinfo" in transaction SE16, and this time the RELID "SL" for "Screen Layout": ![]() This displays our two screen layouts: ![]() Copy the ID into the transport request, replacing the name of the individual layout names with “*” if you whish to transport all existing layouts of this screen: ![]() Now that we have entered the correct keys, the transport request looks like this: ![]() For the text table /S10/LAYOUTT, you do not have to go through the entire process again. Instead, use the Ctrl+Y function of the SAP GUI to copy all three lines, then F3, then click on the /S10/LAYOUTT entry and paste the lines: ![]() The table /S10/LAYOUTT has the same key structure, but additionally the language key as the first key column after the client. Insert the language key, e.g. “E” for English, in all rows, and if you need to transport other languages, copy the rows and insert the correct language keys. In our example, this would be “D” and “E”: ![]() Save the transport request. In SE01 it looks as follows: ![]() |
Components: S10 Framework |