• Always create a new separate include for each Gap in a SAP Enhancement exit
  Separate User Exits allow enable the independent migration of code as part or the promote-to-production path
  
• Using the EXIT statement will terminate processing for all subsequent user exits

• The use of memory pointers in order to overcome User Exit Interface limitations is not permitted

FIELD-SYMBOLS: <F>      TYPE STANDARD TABLE.

ASSIGN ('(SAPMV56A)XVTTP[]') TO <F>.

        T_XVTTP = <F>.

The variable XVTTP accessed in this example is not within the regular data scope of the current program. In order to overcome this limitation and we are using the 'Assign' statement against a specific memory location. During the execution of the VOFM we have no control of the availability of this memory location. The SAP Interpreter basically searches all available memory areas for the specified name and returns the value found in the first location - that's a solution that's very difficult to maintained going forward - Any OSS note or external transport could affect the availability of specific variables in SAP Memory – this is unacceptable

Related Items:

• A comparison between enhanceme
• Activating ABAP Field Exits
• Adding Custom Fields to VBAP
• Conversion Exits
• Difference Between BADI and Us