One Place to find all changes. IE A new material group is added. That material group should work the same in all programs. Normally all programs would be searched for similar constants. In ZMD_CONSTANT there is only one place to change it.
No programming change required.
User can not “mess it up”.
Drawbacks – Cons
It has be transported.
Multiple entries for the same thing with the program field.
ABAP Docs is from the monthly SDN. Here's the link:
To avoid modification of SAP code - use field symbols in your user exit. Then you can point to any field in the SAP program. Please note! User exits can be called from many places, if that field is not in the other programs, it will cause them to short-dump.
MM01/MM02 - when recording a BDC - go to the first view and then move to the others. This is a good trick for any screen similiar to MM01 or MM02 that does not have a BAPI.
SE11 - generate table maintenance for a table. Utilities -> table maintenance generator, you can change the table in SM30. To limit so that only that table can be maintained. Create a parameter transaction.
Name of screen - Update value X
Name of screen - viewname value - your table name.
You can use these routines to parse any input file, to see if your field definitions in the record layout match the data, or to print a subset of fields from an input file (e.g. list just the vendor number or employee number, etc). The p_any_rec values above can literally be changed to any structured record definition. I mostly use this when working on new interfaces, or when diagnosing a problem with an interface file. From Gordon Tobias