Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-MID-ALE (Application Component) ALE Integration Technology⤷
SED (Package) IDoc Interface (Processing, Administration, Definition)
Basic Data
| Data Element | EDI_SEGNA3 |
| Short Description | Name of SAP segment |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR10 | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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 | Segment |
| Medium | 16 | SAP segment name |
| Long | 21 | Name of SAP segment |
| Heading | 21 | Name of SAP segment |
Documentation
General
This field contains the ten-character SAP segment name.
The field is a required field.
Applications
Outbound IDocs:
The field must be filled with the segment type when an IDoc is created.
Inbound IDocs:
The field identifies the segment for the application data by means of its segment type.
IDoc interface
The field is used for a formal check against the EDISYN table.
Outbound IDocs:
The internal SAP segment type is converted to the external segment name.
The external segment name is converted to the internal SAP segment type.
EDI subsystem
Outbound IDocs:
The field is filled with the same value as the TABNAM field of the same data record. It identifies the segment structure of the application data that is stored in the SDATA field.
Inbound IDocs:
The field must be filled with the same value as the TABNAM field of the same data record.
History
| Last changed by/on | SAP | 19970530 |
| SAP Release Created in |
