OBBH

OBBH

Substitution object: Constant, table field, or exit

There are three methods for changing (substituting) the value in a table field if the Boolean condition has been fulfilled (or is empty). The selected method is displayed next to this field.

The substitution methods and the necessary entries in each case are:

Substitution with a constant value.You enter the value that is to be transferred to the assigned recipient field. This value is also allowed to be blank.

Substitution with the value from a different table field.You enter the name of the other field in the following form:Table name-field nameThis field has to be transferred to the substitution, that is it must be a field that is allowed to be used in the prerequisite for substitution.You can also leave the input field blank. In this case the recipient field is initialized.

Substitution within a user exit.You enter the name of the exit.

User Exits

Syntax: Uzzzz (zzzz = up to 4 characters)

ExampleU01 "User exit U01"

User exits are customer-programmed FORM routines. There are two types of user exit:

1. Validation exits. These are used in requirements and checks. They have either the value "T" for true or "F" for false and are interpreted as a part of the logical expression, such as a comparison of constants or of fields. This type of user exit requires you to enter a parameter with the result of your check ("T" for true; "F" for false).

Example

FORM Uzzzz USING B_RESULT. "'T' oder 'F'

1. Substitution exits are used to change one or more fields. However, you can only change fields for which substitution is permitted in the Boolese class. When maintaining substitutes, you can display these fields by choosing the menu path "Extras -> Fields for substitution".

Example

FORM Uzzzz USING COST_CENTER.

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

Note

1. Data declaration To enable their content to be used together with the calling transaction, tables and structures must be declared external to FORM routines.

1. Parameter definitionIt is important that you tell your code generation program the number and type of parameters that you use for the user exit. You do this by making your newly defined user exit known in the FORM routine GET_EXIT_TITLES (with the exception of the parameter for the result of a validation exit). You do not need to declare this parameter because it is automatically generated by the system. For information on the types of parameter that exist and how they are used, refer to the online documentation. When you create a user exit, you can also use the example form pools supplied by SAP (RGGBNR000 for validation; RGGBS000 for substitution). You are recommended to copy the example form pools when creating your user exits. These example form pools already contain entries in the FORM routine GET_EXIT_TITLES for the examples supplied. Note that routine GET_EXIT_TITLES must always exist in your form pool.

Further information on creating user exits can be found in the online documentation under the topics "Validation" and "Substitution".

SAP Exits

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

Syntax: Szzzz (zzzz = up to four characters)

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

ExampleS01 "SAP exit S01"

Display description of T80D configurationReturn ->Application

FI-SL: User exit form pool

Definition

The user exit form pool name is entered as a 8-character name. It defines in which form pool system can find user exits. The name must be entered in every client. You can enter either the same form pool in every client, that means a form pool with user exits in the system, or you can define several form pools that you use accordingly in the various clients.

Example

If the form pool 'ZGGBR000' is used in all clients, enter this name in every client in the the table T80D.

Effects on Customizing

An example form pool is delivered with the system. You should copy this form pool, taking into account the user naming convention. Change the relevant entry in table T80D so that the new form pool is used.

You can edit this form pool and include your own exit routines in the form pool.

Example

Copy RGGBS000 to ZGGBS002 and change the relevant entry in T80D to ZGGBS002. If you also want to use user exits in client 004, you can

1. either enter the form pool ZGGBS002 also in this client

2. or your create a new form pool and enter these in the table T80D.

Goto T80D maintenanceDisplay Boolean rule descriptionDisplay substitution exit descriptionReturn ->FI-SL: User exit form pool T80D maintenance (GCX2)

Definition

Each prerequisite and check for a validation or substitution and every rule consists of several lines. Several operators and operands (e.g. rules) can be used in each of these logical expressions; the elements in round brackets are processed first.

Logical Operators

AND, OR, -->, .

Example

Rule_1 AND ( rule_2 OR rule_3 )

Operator DescriptionOperands

Field Comparison: Table field = "literal"

Set: Table field IN set name or IN set name

Constants: TRUE, FALSE

Rules: Rule

Exit: Uzzzz

Commentary: "Commentary"

Mathematical Formulae: Tab1-field1 + "literal" = Tab2-field2

General NotesExample

( cobl-budat = syst-datum AND syst-uname IN set_benutzer ) OR U100 "User exit for cost types"

Return ->Application

Definition

A rule consists of several lines. Several operators and different rules can be used in each logical rule; the elements in rounded brackets are processed first.

Logical Operators

AND, OR, NOR, NAND, -->, .

Example

&rule_1 AND ( &rule_2 OR &rule_3 )

Operator DescriptionOperators

Field Comparison: $field = 'literal'

Set: IN set name or IN set name

Constants: TRUE, T, FALSE, F

Rule: &Rule

Exit: =Uzzzz

Commentary: "Commentary"

Math. Formulae: MATHS(... )

General NotesExample

( $budat = $datum AND set_benutzer ) OR =U100 "User exit for cost types"

Return ->Application Substitution exit. Alternative to Boolean evaluation.

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'

1. 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: 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.

1. 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 configurationSee Help text 1.doc

Help text for Exit

Help text for User Exits

Help text for T80D configuration

Direct maintenance of Boolean expressions in validations and subtitutions

Direct maintenance of Boolean expressions in rules

Display substitution exit description