Professional Documents
Culture Documents
Most conversion exits used in screens by SAP are actually function modules. You can find them by searching for
CONVERSION_EXIT_name_INPUT and CONVERSION_EXIT_name_OUTPUT.
NOTE: ftp can accept commands from a file, and it is often useful to create a file containing the commands, and pipe the file into the
ftp command.
Sometime, you may find that the a SELECT that you have coded is very slow, even though you have put all the fields needed for an
index in your where clause. Usually, this means that the DBMS is selecting the wrong index, you can tell if this is the case by doing
an SQL trace (System - Utilities - SQL Trace). You can help the DBMS select the correct index by providing hints, include all fields
from the index, and make sure that the fields are in the same order as they appear in the index.
Help Views
(Provided by Paul Kjaer)
For instance, I set this up in a multi-language environment when you have a code and text combination you want to set up. Typically,
you have to set up two tables: One with just the valid codes i.e. Zxxx where the only field is the code field, the second is ZxxxT
which contains the code and language as the primary index with the description as the data field. In this case, then you usually define
a view H_Zxxx which is a join on these two tables. The key thing is that the Foreign Key definition for the code field in the ZxxxT
must have the must have the type "Key Fields of a Text Table". This results in the Table Maintenance generator (SM30) generating a
screen that allows you to maintain the code and description together for the system language.
In a related note, to set up a customer transaction for a Table Maintenance generated dialog, use SE80 and enter the function group
used for the table maintenance dialog. Then Create a transaction (Zxxx) of type parameter. Fill in text, specify Transaction SM30,
click on "skip initial screen" and set up default values of VIEWNAME set to Zxxx and UPDATE set to X.
Field Exits
(Provided by Paul Kjaer)
You cannot debug a field exit. You can at best create a small module pool with a screen that has the appropriate fields and in your
PAI, call a module which calls your function that is the field exit and debug the small module pool. Good idea to keep as much of one
around if you do field exits regularly.
I used CNEX0007 and CNEX0006 to add fields to the PRPS and PROJ tables respectively in the PS Module. As probably the case
with most of these exits, have fun trying to figure out how to protect the fields in display mode. We lived with the fact that the save
was disabled so it could not save the changes anyway. A test of the transaction code would not be complete. Use transaction SMOD
to do SAP enhancements/field exits. In SMOD, you can get list of SAP enhancements that exist by Utilities - SAP Enhancements.
Trying to figure out what they can be used for and how to accomplish the desired results is a major challenge.