Show TOC
Communication
Structures
Communication structures form the basis of the LIS inbound
interface for external data (LIS inbound interface).
The communication structure must contain a date
field of type DATS.
It is recommended that you use the following
field types for indicators that can be totalled: CURR (currency field), QUAN
(quantity field), DEC and NUMC (for other field values that can be totalled),
CHAR, DATS (date field), TIMS (time field). If you use currency and quantity
fields, you must also include the corresponding unit (type UNIT) and currency
key (CUKY) in the communication structure. If possible, you should use the SAP
standard data elements.
Note
- If you wish to use IDocs, the sender system
(your system) must serve the IDoc interface, or be able to perform Remote
Function Call (RFC).
- Long names are not supported in LIS. You
cannot include fields in the fields catalog if their table name/structure
name/field name has more than ten characters. This also applies to
communication structures used in the LIS inbound interface.
- Before you use IDocs as communication
structures, you need to gain an overview of the following basic concepts: ,
the different types of IDoc, and
segments).
You can find
detailed information about these concepts in the SAP library under
Basis Components -> Basis Services/Communication Interfaces -> The IDoc
Interface -> BC IDoc Interface: EDI Application
Scenarios<->.
- Before you use dictionary structures as
communication structures, you need to gain an overview of how to use and
maintain structures.
You can find
detailed information on this subject in the R/3 library under Basis
Components -> ABAP Workbench -> ABAP Dictionary.