Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ MCS (Package) R/3 application development: Logistics Information Warehouse
Basic Data
Data Element | COMSTRU |
Short Description | Name of communication structure |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | TABNAME | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | EDD | |
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Com.struc. |
Medium | 15 | Comm. structure |
Long | 22 | Communication struct. |
Heading | 22 | Communication struct. |
Documentation
Definition
A communication structure is a structure or table in the Dictonary which satisfies specific requirements:
- It is active
- It contains at least one field of the type CHAR or NUMC
- It contains a date field of type DATS
- It was configured to the Logistics Information System.
You can use the LIS inbound interface for external data (LIS inbound interface) to do this.
Communication structures can have a hierarchical (multi-level) relationship. For instance, the document item is usually subordinate to the document header.
Note
At present, the LIS inbound interface does not support hierarchical relationships between communication structures.
Use
You can create field catalogs for a communication structure. These field catalogs can in turn be used as templates when you create info structures.
If you have created LIS inbound interfaces in your name range, then the communication structures of these LIS inbound interfaces are also offered as templates for creating information structures, in addition to the field catalogs.
In the updating definiton, you can allocate fields from the communication structures to your fields from the info structure. The fields in your information structure are then always updated from these fields.
Note
You also have the option of using IDocs as communication structures.
IDocs consist of segments. These segments are interpreted as communication structures when you use the LIS inbound interface.
History
Last changed by/on | SAP | 19980729 |
SAP Release Created in |