There may come a time within SAP where you will need to create a copy of a standard transaction in order to customize it to your specifications.
Surprisingly, making a copy of a transaction is not as difficult as one may imagine.
Note: You may need to create your own Package to store these changes into. If you do not, then you may be able to choose "Local Object" when prompted.
The first thing you will need to do is determine what underlying program is called from the transaction you wish to create a copy of. This can easily be done by running transaction SE93, imputing the desired transaction (OS01 in my case), and clicking Display.
Note: It may be best to either screenshot or document the settings displayed for the transaction. Make sure you also click on the 'Values' button in order to get the Authorization Object's required values.
Now that you know what the program's name is, RSHOST14 in our case, you can go to transaction SE80 in order to access the ABAP Workbench. From the initial screen, you will need to select "Program" from within the drop-down and then type the program name within the text field. Click the Display button (glasses) in order to view the program.
Now that the object data is shown for the program, you can right-click on it and select "Copy" from the available list of options.
Ensure that the source program is correct and then enter the name you wish to use for the new transaction (starting with a "Z").
From the next screen, select all of the elements you wish to copy over to the new transaction. In this case, I have selected everything.
At this point, you may be prompted to add this object to a Package. You can either use one that you have created, or you can try to use "Local Object."
Now that we have a successful copy of the original program, we will need to assign a transaction to it. Remember that transactions merely call underlying programs. To do this, you can right-click on the new program's name, hover over the "Create" option, and select "Transaction" from the list.
Now you will be able to give your new transaction a proper name and give it a descriptive short text. You will also need to select how you want it to start. For this particular program, you will need to select "Program and selection screen."
We're almost done with this. Remember the program data I told you to screenshot or document? Now we need it.
On the final screen, you will need to fill out each and every field similarly to how the original program data was. The following image shows what was required for a copy of OS01.
All that's left now is to right-click on the program and select "Activate," activating all of the objects within it. Once you're done, click Save.
If everything went smoothly, you should now be able to run your new transaction and see an identical screen to the original.
Good luck and have fun!
Note: You may need to create your own Package to store these changes into. If you do not, then you may be able to choose "Local Object" when prompted.
The first thing you will need to do is determine what underlying program is called from the transaction you wish to create a copy of. This can easily be done by running transaction SE93, imputing the desired transaction (OS01 in my case), and clicking Display.
Note: It may be best to either screenshot or document the settings displayed for the transaction. Make sure you also click on the 'Values' button in order to get the Authorization Object's required values.
Now that you know what the program's name is, RSHOST14 in our case, you can go to transaction SE80 in order to access the ABAP Workbench. From the initial screen, you will need to select "Program" from within the drop-down and then type the program name within the text field. Click the Display button (glasses) in order to view the program.
Now that the object data is shown for the program, you can right-click on it and select "Copy" from the available list of options.
Ensure that the source program is correct and then enter the name you wish to use for the new transaction (starting with a "Z").
From the next screen, select all of the elements you wish to copy over to the new transaction. In this case, I have selected everything.
At this point, you may be prompted to add this object to a Package. You can either use one that you have created, or you can try to use "Local Object."
Now that we have a successful copy of the original program, we will need to assign a transaction to it. Remember that transactions merely call underlying programs. To do this, you can right-click on the new program's name, hover over the "Create" option, and select "Transaction" from the list.
Now you will be able to give your new transaction a proper name and give it a descriptive short text. You will also need to select how you want it to start. For this particular program, you will need to select "Program and selection screen."
We're almost done with this. Remember the program data I told you to screenshot or document? Now we need it.
On the final screen, you will need to fill out each and every field similarly to how the original program data was. The following image shows what was required for a copy of OS01.
All that's left now is to right-click on the program and select "Activate," activating all of the objects within it. Once you're done, click Save.
If everything went smoothly, you should now be able to run your new transaction and see an identical screen to the original.
Good luck and have fun!
0 comments:
Post a Comment