Special Fields in the Control Segment of EDI_DC
Special functions must be taken into account for the following fields:
Field EDI_DC-DOCNUM: Document number
In the central description, the field indicates the unique number in the SAP R/3 system of the document that is transmitted. A unique number must also be entered in the subsystem so that a reference can be created to the accompanying data records. When the IDoc being transmitted from the subsystem is imported by the R/3 system, the content of DOCNUM is replaced with an internal number, determined by the R/3 system. The reference to the old DOCNUM is saved.
Field EDI_DC-RCVPRT: Partner type of receiver
The field indicates the type of partner system and is generally set to ‘LS’ (logical system) for communication with non-R/3 systems.
Field EDI_DC-RCVPRN: Partner number of receiver
Number or name of the receiving system.
Field EDI_DC-SNDPRT: Partner type of transmitter
The field indicates the type of partner system and is generally set to ‘LS’ (logical system) for communication with non-R/3 systems.
Field EDI_DC-SNDPRN: Partner number of transmitter
Number or name of the transmitting system.
The combination of fields SNDPRT and SNDPRN is extremely important for the subsystem when data in the incoming IDocs is being processed.
These two fields are used to separate documents from different R/3 systems or R/3 clients. A transportation planning system could, for example, receive two deliveries from two R/3 systems with the same delivery number. These deliveries must not get mixed up during planning. SNDPRT and SNDPRN therefore, function as an additional part of the key for all identification fields.
Field EDI_DC-ARCKEY: Document ID in the external system
In field ARCKEY, the subsystem can save additional information for unique identification of a transmitted document. If a document transmitted from the subsystem cannot be processed by the R/3 system, then an error message with the contents of ARCKEY is sent back in order to create a reference to the document-creating transaction.
Field EDI_DC-MESTYP: Logical message category
The field contains the logical name of a message. It is not bound by any EDI standard. Logical messages are assigned by SAP to the individual IDoc types.
Field EDI_DC-IDOCTYP: Name of basic IDoc category
The IDoc type is defined by the applications. They determine the sequence of the SAP segments. The IDoc types issued with the SAP standard are identified via field IDOCTYP just as IDoc types newly created by the customer are.
Field EDI_DC-SERIAL: EDI/ALE: Serialization field
The serialization field contains a unique number, that can be used in serialization, i.e. setting the correct transmission sequence of IDocs in the receiving system. Generally, this is a time stamp that explodes the sequence sufficiently or which provides a sequence of consecutive numbers based on the unique identification of the creation sequence and/or the transmission sequence in the transmission system. The serialization field should only contain numbers.