Hierarchy

⤷

⤷

Basic Data
Data Element | BCS_EXIND |
Short Description | BCS: Call Sequence |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | INT4 | 4-byte integer, integer number with sign |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
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 Call. |
Medium | 19 | Exit Call Sequence |
Long | 22 | Exit Call Sequence |
Heading | 22 | Exit Call Sequence |
Documentation
Definition
The specified number determines the sequence in which exits are called if several suitable exits are found for one send order. Subsequent exits are then only called if the exit executed previously did not execute the delivery (that is, it returned the return code GC_CONTINUE).
Use
Dependencies
Example
Two exits CL_EXIT_1 and CL_EXIT_2 are entered for the document class XML and the recipient order@co.uk.
If the processing logic in the exits expects different DTD (Document Type Definition), only one of the two exits is executed. In this case, the call sequence is of no significance.
If both exits expect the same DTD, only the exit called first is executed. This exit executes the delivery and completes the processing. In this case, the call sequence determines which exit is called.
History
Last changed by/on | SAP | 20010220 |
SAP Release Created in | 610 |