SAP ABAP Data Element V50AGL_MSGTY_SET_FOR_VBFS (Message Type Quantity for Collecting Messages in VBFS)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ VL (Package) WS-SHP: General Processing for Shipping
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ VL (Package) WS-SHP: General Processing for Shipping
Basic Data
Data Element | V50AGL_MSGTY_SET_FOR_VBFS |
Short Description | Message Type Quantity for Collecting Messages in VBFS |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR005 | |
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 | 0 | |
Medium | 0 | |
Long | 0 | |
Heading | 0 |
Documentation
Definition
You can use this field and the message categories within it to specify which messages are not issued directly when you call routine MESSAGE_HANDLING, but are written into the internal table for structure VBFS.
This is necessary during vendor tolerance checks for batch split items, amongst others. In this case, messages with category "E" and "W" are not issued directly. Instead they are collected and are issued as an information (category I) message after processing. This avoids inconsistencies between the the batch main item and the batch split item.
To achieve this, you fill the field with "WE".
History
Last changed by/on | SAP | 20010720 |
SAP Release Created in | 470 |