Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-NO (Application Component) Messages⤷
DNO (Package) Messages
Basic Data
| Data Element | DNOT_COMM |
| Short Description | Communication Type (Key) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | AD_COMM | |
| Data Type | CHAR | Character String |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table | TSAC |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | COMM_TYPE | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Comm. Type |
| Medium | 17 | CommunicationType |
| Long | 20 | Communication Type |
| Heading | 17 | CommunicationType |
Documentation
Definition
A communication method used to exchange documents and messages with a business partner.
You can specify a standard communication method in central address management. This specified method can be used to automatically decide (at program level) which means of communication is used to transfer messages.
Example
One business partner wants all messages sent by Fax and another wants all messages sent by e-mail.
Notes
The means of communication that can be used depends on the application context. Invitations, for example, can only be sent by post because of the items that have to be enclosed. A protocol, however, can be sent by post, Fax, or e-mail.
So-called communication strategies can be defined for this purpose. These can be included in the respective application context.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 50A |
