Let’s suppose you have created a new Oracle level index on a SAP table using SE11.
You’ve created it in DEV and proven that it changes the EXPLAIN PLAN using SQL Trace or Oracle level tools.
Unfortunately you don’t have a significant amount of data in your DEV instance, but you do have data in your UAT or integration test system.
You could release your workbench request that you will have created to create the new index in SE11, but this means a flurry of potential additional transports to remove it again if it doesn’t work.
You just want a proof of concept that can be removed again.
Since it’s entirely possible for you to create an index at the Oracle level below SAP, you just need to ensure that you create the index the same as SAP would.
You can choose a couple of methods to ensure this, but we will discuss the SAP biased method.
Using SE11, find the table on which the new index exists in DEV.
NOTE: We’re showing R/3 Enterprise, but it should be similar for Netweaver based systems.
Click the “Indexes…” button to list the indexes:
Double click the new index you created earlier.
Now on the menu, select “Utilities -> Activation Log”:
Click the magnifying glass icon next to the “Technical log for mass activation” option on the main screen.
Expand all the possible expansion icons:
Look for the text “CREATE” to find the create statement:
Copy the text and paste into SQL*Plus in any other SAP systems Oracle database to create the index.
Just remember that this index does not exist in the SAP data dictionary, so you must remove it once you have proven the EXPLAIN PLAN is working for the larger amount of data.