SAP ABAP Data Element EXITSUBST (Substitution exit. Alternative to Boolean evaluation.)

Hierarchy

☛ SAP_FIN (Software Component) SAP_FIN
   ⤷ FI-SL-VSR (Application Component) Validation, Substitution and Rules
     ⤷ GVAL (Package) Validation, Substitution and Rules

Basic Data

Data Element	EXITSUBST
Short Description	Substitution exit. Alternative to Boolean evaluation.

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	EXIT_NR_G
Data Type	CHAR	Character String
Length	5
Decimal Places	0
Output Length	5
Value Table

Further Characteristics

Search Help: Name
Search Help: Parameters
Parameter ID
Default Component name
Change document	☐
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	10	Exit
Medium	15	Sub.exit
Long	20	Substitution exit
Heading	55	Substitution exit

Documentation

User exits

Syntax: =Uzzzz (zzzz = up to 4 characters)

Example

            =U01             "User exit U01"

User exits are form routines that the user programs. There are two types of user-exits:

1. Validation exits are used in the prerequisites and checks. They have either the value 'T' for true or 'F' for false. They are interpreted as a part of the logical statement, like a constant or field comparison. For this type of user exit, you must fill a parameter with the results of your check ('T' for true; 'F' for false).
   
   Example
   
   FORM Uzzzz USING B_RESULT. "'T' or 'F'
   
2. Substitution exits are used to change one or more fields. However, you can only change those fields that are permitted in the Boolean class for the substitution. You can display these fields by selecting the following menu options in substitution maintenance: <Extras -> Fields for substitutions>
   
   Example
   
   FORM Uzzzz USING COST_CENTER.
   

The name of the form pool that contains your user exit must be stored in table T80D.

Note

1. Data declaration
   Tables and field stings cannot be declared in form routines, so that the contents can be used along with the calling transaction.
2. Parameter definition
   It is important that you make declare the code generation program for your user exit; how many and what type of parameters you are using for the user exit. You do this by entering your newly defined user exits in the form routine GET_EXIT_TITLES. One exception is the parameter for the results of a validation exit. You must not declare this, it is automatically generated be the system. What types of parameters are available and how you use them is described in the online documentation. When creating your user exits, you can use the example form pools delivered by SAP (RGGBR000 for validations; RGGBS000 for substitutions) as a reference. We recommend that you copy the example form pools delivered by SAP when creating your own user exits. In these example form pools, entries already exist in the form routine GET_EXIT_TITLES for the examples delivered. The GET_EXIT_TITLES must absolutely exist in your form pool.

You can find additional information on the creation of user exits in the online documentation on validations and substitutions.

SAP exits

SAP exits are form rountines programmed by SAP. The name of the form pool is SAPFGBEB.

Syntax: =Szzzz (zzzz = up to four characters)

FORM Szzzz using B_result. "'T' or 'F'

Example

            =S01            "SAP exit S01"

Display description of T80D configuration

History

Last changed by/on	SAP	19990223
SAP Release Created in