Making the Settings for Mapping in the EDI Subsystem

Purpose

The EDI subsystem must process the transmission so that the IDoc is created correctly in the SAP system.

Prerequisites

Each IDoc should only contain the data of one delivery. Both the GSVERF01 IDoc and the inbound processing are designed for one delivery note per IDoc .

Process Flow

The EDI subsystem must give the transmissions to the ERP interface in such a form that one delivery is referred to per IDoc.

The examples that follow are based on the German standard VDA 4908 for self-billing documents. Other standards, like the ANSI 820, work in a similar manner. You should regard the information as an example, and adapt it to your situation.

Standard VDA 4908
Record type 821	Unique data record for the transmission as a whole (external transmission number)
Record type 822	Contains the data for a self-billing document. Can occur one or n times.
Record type 823	Contains the data for a delivery note. Can occur one or n times in a record with record type 822.
Record type 824	Contains the data for a delivery note item. Can occur one or n times in a record with record type 823.

In the case of this common German standard, VDA 4908, the EDI subsystem must split up the transmissions so that one IDoc is created per record of type 823 (that is, per record that represents a delivery note.)

The basic data (e.g. transmission number, self-billing document number and date) contained in the record types 821 and 822, which are above 823 (the delivery) in the VDA 4908 hierarchy, must be written redundantly in the appropriate fields and segments in each IDoc.

For an example of the actual mapping settings to be made for the SD self-billing procedure, see Table of Settings for Mapping in EDI Subsystem .