When transporting your configuration to a test system, you might be surprised to find that much of it is missing. Upon reviewing the documentation, you’ll discover that certain configuration tables need to be manually populated. This guide outlines the necessary steps and lists the tables that require manual addition.
Additionally, part of the configuration is stored in /ASADEV/ tables. These tables do not automatically record new or changed entries into transports because they need to remain editable in both Test and Production systems. Therefore, the content of these tables must be manually added to a workbench transport.
These steps can be executed using transaction codes SE09 or SE10. You must specify the “Program ID” as “R3TR” and the “Object Type” as “TABU.” The “Object Name” should correspond to the table you intend to add to the transport. To include all entries within the table, set the “Table Keys” parameter to “*” and utilize the “Function” button.
The following list of tables usually needs to be added manually to the workbench transport:
Find your workbench transport and double-click on it.
2. Add Tables to Transport:
3. Set Table Keys:
Here you can decide which records should be transported.
After completing these steps, you should have everything necessary to transport your ASANWEE add-on configuration. Release and import your transport as usual, and then verify the results in the target system.
For more detailed instructions, refer to the SAP documentation.Disclaimer: You can find this text also on my other blogs:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
7 | |
7 | |
7 | |
6 | |
4 | |
4 | |
4 | |
3 | |
3 | |
3 |