2024 Mar 19 3:26 PM - edited 2024 Mar 20 9:31 AM
Hello everyone,
What is the theory behind creating a condition table (e.g., pack specification) in the development system? The IMG activity where we enter the table layout not only creates our tables locally. Our input is also saved in a customizing transport, right?
When we import this transport into the next system, the system generates the same database tables locally again. And our table layout ALSO creates a table locally in $TMP in the test system, correct?
But what if I want to delete the condition table from the test system again? What steps do I need to take? This is not possible with a transport because the system has also created it locally.
Thank you.
Request clarification before answering.
Did you try to delete the condition in development, release and transport the Customizing request to quality, that should delete the condition table during import (since Release 3.0F)
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 | |
4 | |
4 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.