SAP ABAP Data Element CO_SNDALL (Indicator: Send message to all destinations or not at all)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ COCB (Package) R/3 Application Development: PP Orders Batch Management
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ COCB (Package) R/3 Application Development: PP Orders Batch Management
Basic Data
Data Element | CO_SNDALL |
Short Description | Indicator: Send message to all destinations or not at all |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFLAG | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
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 | To all |
Medium | 18 | Send to all dest. |
Long | 20 | Send to all dest. |
Heading | 4 | SndA |
Documentation
Definition
You use this indicator to specify how a message is treated if:
- It cannot be processed by one of its destinations (message status Destination error
- One of its destinations is temporarily locked (message status To be resubmitted)
Use
If you set this indicator, the message is not sent to any of its destinations if one of the above errors occurs.
Thus, the message can be corrected in the message monitor and then sent to all destinations.
If you do not set the indicator, the message is sent to all destinations that can process it even if an error occurs at another destination.
Once the message has been sent to one destination, it can no longer be changed even if the destination error resulted in incorrect message data.
Procedure
Use this processing type, if:
- Several destinations are allocated to one message category
- One of the destinations is a function module that cannot process messages with incorrect characteristic values
This includes all message destinations contained in the standard system except for PI01.
To improve system performance, do not use this processing type if:
- Only one destination is allocated to a message category
- Destinations of type ABAP table, SAPoffice user, or external function only are allocated to a message category
Examples
Dependencies
History
Last changed by/on | SAP | 19980325 |
SAP Release Created in |