SAP ABAP Data Element CD3IMSGLST (List of expected messages)
Hierarchy
☛
HOME (Software Component)
⤷ BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD
⤷ SVED (Package) ABAP/4 Dictionary: Verification
⤷ BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD
⤷ SVED (Package) ABAP/4 Dictionary: Verification
Basic Data
Data Element | CD3IMSGLST |
Short Description | List of expected messages |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR60 | |
Data Type | CHAR | Character String |
Length | 60 | |
Decimal Places | 0 | |
Output Length | 60 | |
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 | Incl. msg. |
Medium | 15 | Incl. messages |
Long | 20 | Expected messages |
Heading | 0 |
Documentation
Definition
In this line, messages can be defined in the order in which they should appear in the log. The following definitions are permitted:
- e.g.: AD010 Message 010 from application area AD is expected.
- * Any number of any kind of message is expected,
i.e., messages which are not exactly known
may arrive until the next explicitly defined
message. - ? Exactly one message of any kind is expected.
- e.g.: 010 Message no. 010 is expected from an
unknown application area. - e.g.: EAD010 The message AD010 is expected with error
gravity E.
All specifications must be separated by a semicolon. Additional blanks are not permitted. There may not be a semicolon after the last entry.
History
Last changed by/on | SAP | 19991118 |
SAP Release Created in |