100% found this document useful (2 votes)
4K views12 pages

Delivery Interface - DESADV

The document describes the delivery interface in SAP which groups ALE and EDI outputs related to deliveries. It defines common output types like shipping notifications, orders, and confirmations. It provides details on integrating delivery data with external systems and the roles of various delivery participants. Sections cover the structure and fields used for different outbound and inbound output types, qualifying options, and scenarios like using DESADV for shipping notifications between vendor and customer systems.

Uploaded by

Ram KL
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
100% found this document useful (2 votes)
4K views12 pages

Delivery Interface - DESADV

The document describes the delivery interface in SAP which groups ALE and EDI outputs related to deliveries. It defines common output types like shipping notifications, orders, and confirmations. It provides details on integrating delivery data with external systems and the roles of various delivery participants. Sections cover the structure and fields used for different outbound and inbound output types, qualifying options, and scenarios like using DESADV for shipping notifications between vendor and customer systems.

Uploaded by

Ram KL
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 12

Delivery Interface

Use
The delivery interface groups all ALE and EDI outputs with reference to the delivery. Here, the EDI output is used mostly for external communication, and ALE output for internal communication. In the standard system, the following outputs are defined: Sending a shipping notification (DESADV, outbound EDI) Informing the forwarding agent (CARNOT, outbound EDI) Shipping order to warehousing contractor (SHPORD, outbound EDI) Shipping confirmation from service agent (SHPCON, inbound EDI) Warehouse order to internal warehouse (WHSORD, outbound ALE) Warehouse verification from internal warehouse (WHSCON, inbound ALE) Proof of delivery (STPPOD, outbound, EDI) Proof of delivery (STPPOD, inbound, EDI)

Integration
The shipping notification is the advance announcement of the delivery at the customer. When the forwarding agent makes this announcement (shipping order), the delivery data is transmitted so that the agent can organize the pickup and delivery of the goods on behalf of the customer. The shipping order and the shipping confirmation serve to communicate with a warehousing contractor / service agent. The latter supervises the warehouse and is responsible for the delivery. The contractor also either takes care of the delivery himself/herself or commissions a service agent. The warehouse order and the warehouse verification both serve to connect a company's own external system (external software) with Warehouse Management. The following overview shows the output flow:

All outputs are based on the basis IDoc type DELVRY03.

Range of Functions

Output that is outbound contains the complete structure, that is, all the fields in the individual segments are supplied with data. In the case of inbound output, only certain fields in the segments for delivery header, delivery item, and handling units are used. Here you have control segments at your disposal in order to initiate the required behavior when you are processing the output. The more significant segments and fields are listed below:

E1EDL20 Delivery header

Segment field

Table field

VBELN BTGEW NTGEW GEWEI VOLUM VOLEH

Sales document number Total weight Net weight Weight unit Total volume of delivery Volume unit

LIKP-VBELN LIKP-BTGEW LIKP-NTGEW LIKP-GEWEI LIKP-VOLUM LIKP-VOLEH

E1EDL18 Delivery header control

Segment field

Table field

QUALF

Qualifier control Post goods issue Delete delivery Picking with flow records Adopt gross weight Adopt net weight Adopt volume PGI DEL PIC GWT NWT VOL

PARAM

Control parameters

E1EDT13 Deadlines delivery header

Segment field

Table field

QUALF

Qualifier deadline Goods issue 6 VBDDL-ISDD 10 VBDDL-NTANF VBDDL-NTANZ

ISDD

Actual start date Picking

NTANF NTANZ E1EDL24 Segment field POSNR MATNR CHARG LFIMG NTGEW BRGEW GEWEI VOLUM VOLEH E1EDL19 Segment field QUALF

Planned start date Planned start time Delivery item

Table field Item number of sales document Material number Batch number Quantity actually delivered Net weight Total weight Weight unit Total volume of the handling unit Volume unit Control of delivery item Table field Qualifier control Adjust quantity Adopt gross weight Adopt net weight Adopt volume Batch split item QUA GWT NWT VOL BAS LIPS-POSNR LIPS-MATNR LIPS-CHARG LIPS-LFIMG LIPS-NTGEW LIPS-BRGEW LIPS-GEWEI LIPS-VOLUM LIPS-VOLEH

PARAM E1EDL37 Segment field EXIDV TARAG GWEIT BRGEW NTGEW MAGEW GWEIM BTVOL NTVOL MAVOL VOLEM TAVOL VOLET VEGR1 VEGR2 VEGR3 VEGR4 VEGR5 VHILM LAENG BREIT HOEHE MEABM INHALT EXIDV2 E1EDL44

Control parameters Handling unit header Table field External handling-unit identifier Tare weight of the handling unit Weight unit Tara Total weight Net weight Allowed weight for the handling unit Weight unit Total volume of the handling unit Load volume of the handling unit Allowed load volume Volume unit Tare volume of the handling unit Volume unit Tara Handling unit group 1 Handling unit group 2 Handling unit group 3 Handling unit group 4 Handling unit group 5 Packaging material Length Width Height Unit for length/width/height Description of the handling unit 2. 2nd external identification Handling unit item VEKP-EXIDV/-VENUM VEKP-TARAG VEKP-GEWEI VEKP-BRGEW VEKP-NTGEW VEKP-MAGEW VEKP-GEWEI_MAX VEKP-BTVOL VEKP-NTVOL VEKP-MAVOL VEKP-VOLEH_MAX VEKP-TAVOL VEKP-VOLEH VEKP-VEGR1 VEKP-VEGR2 VEKP-VEGR3 VEKP-VEGR4 VEKP-VEGR5 VEKP-VHILM VEKP-LAENG VEKP-BREIT VEKP-HOEHE VEKP-MEABM VEKP-INHALT VEKP-EXIDV2

Segment field

Table field

VBELN POSNR EXIDV VEMNG

Sales document number Item number of sales document External identification Delivery item quantity

VEPO-VBELN VEPO-POSNR

VEPO-VEMNG

E1EDL53

Proof of delivery

GRUND PODMG LFIMG_DIFF VRKME LGMNG_DIFF MEINS

Reason for deviation for the POD Quantity (in sales units) actually received for each delivery item

TVPOD-GRUND TVPOD-PODMG

Deviation from the quantity actually delivered (in TVPOD-LFIMG_DIFF sales units) Sales unit Deviation from actual delivery quantity (in stockkeeping units) Base unit of measure TVPOD-VRKME TVPOD-LGMNG_DIFF TVPOD-MEINS

E1EDL54

Repacking handling units

SOURCEHU DESTHU PACKHU PACK_QTY BASE_UOM DELIV_NUMB DELIV_ITEM

External HU identification of the source HU Handling unit is to be packed Base quantity that is packed in the HU item Base unit of measure Delivery Delivery item

HUM_REPACK-SOURCEHU HUM_REPACK-PACKHU HUM_REPACK-PACK_QTY HUM_REPACK-BASE_UOM HUM_REPACK-DELIV_NUMB HUM_REPACK-DELIV_ITEM

External HU identification of the destination HU HUM_REPACK-DESTHU

Below you find a description of the options for inbound output with the required fields: 1. Picking verification without flow records. This type of verification is used if the delivery items in the central system are set in Customizing as non-picking-relevant. The picked quantities are reported by the subsystem to the central system. There, the delivery quantity is adjusted, if allowed. In the IDoc, the following fields must have data: E1EDL20-VBELN E1EDL24-POSNR

E1EDL24-MATNR E1EDL24-LFIMG E1EDL19-QUALF = 'QUA' 2. Picking verification with flow records If, in the central system, the items are set as relevant for picking, the picked quantities can be reported to the central system. However, only the complete, picked quantity of an item can be taken. Multiple reporting with an accumulated figure for the reported quantities is not allowed. So that the picking flow records can be updated, the following IDoc field must also be transmitted, in addition to the fields described under step 1. E1EDL18-QUALF = 'PIC' 3. Verification of batch split items from the subsystem If batch split items occur in the central system, the original item must not be reported. Instead, the new items are transferred as follows: E1EDL24-POSNR = Item number of batch split item E1EDL24-MATNR E1EDL24-CHARG E1EDL24-LFIMG E1EDL24-HIPOS = Item number of main item E1EDL19-QUALF = 'BAS'

If there is no batch splitting, the batch for the main item can be verified. E1EDL24-POSNR = Item number of batch split item E1EDL24-MATNR E1EDL24-CHARG E1EDL24-LFIMG 4. Weight and volume verification It is possible to report back (verify) the gross weight, net weight, and the volume for the entire delivery or for individual items. Using the qualifier in the segments E1EDL18 and E1EDL19, you can control which fields are to be updated in the delivery.

E1EDL20-VBELN E1EDL20-BTGEW E1EDL20-NTGEW E1EDL20-GEWEI E1EDL20-VOLUM E1EDL20-VOLEH E1EDL18-QUALF = 'GWT' E1EDL18-QUALF = 'NWT' E1EDL18-QUALF = 'VOL' E1EDL24-POSNR E1EDL24-MATNR E1EDL24-NTGEW E1EDL24-BRGEW E1EDL24-GEWEI E1EDL24-VOLUM E1EDL24-VOLEH E1EDL19-QUALF = 'GWT' E1EDL19-QUALF = 'NWT' E1EDL19-QUALF = 'VOL' 5. Post delivery goods issue For the goods issue posting, the following additional field must exist. E1EDL18-QUALF = 'PGI' 6. Delete delivery You can delete a delivery in the subsystem if the following fields are transmitted: E1EDL20-VBELN

E1EDL18-QUALF = 'DEL' 7. Packing verification (only for creating handling units) When you report back (verify) handling units, the (external) identification and the packaging material must always be transmitted. E1EDL37-EXIDV E1EDL37-VHILM If a non-assigned handling unit is to be created, no contents data (items) must be transmitted. If a delivery is packed, the item number and the packed quantity must be transmitted (use the quantity unit of the delivery item). If you have a batch split, use the actual (external) item number. E1EDL44-POSNR E1EDL44-VEMNG If a handling unit in another handling unit is to be verified (multi-step packing), you must specify the (external) identification of the lower-level handling unit. E1EDL44-EXIDV 8. Repacking handling units Enter data in all the segment fields in segment E1EDL54.

DESADV Scenario

Outbound(Vendorsystem): From an outbound delivery, an EDI shipping notification can be sent to the customer using output type LAVA, IDoc message DESADV. Inbound(Customersystem): In the receiving system, an inbound delivery is created like in VL31N with reference to a purchase order.

DESADV Outbound (Basic Type DELVRY0*)


DESADV IDoc is sent via output type LAVA.

Customizingof PartnerProfile withWE20

DESADV Inbound
Characteristics:

No batch splits are created. See SAP note 209240 . Batches are only transferred as vendor batches, i.e. the batch field (LIPS-CHARG) is not filled in standard but could be filled by customer function in IDOC_INPUT_DESADV1. If batch items should also be packed, then the delivery item category should allow packing without batches (TVLP-CHHPV pack accumulated batches). In case of packed batch items then: E1EDL44-CHARG (Handling Unit Item) transferred to VERPO-CHARG but E1EDL24-CHARG (Delivery Item) transferred to LIPS-LICHN EXIDV segment at HU level In case the customer and the vendor system are both using the EAN128 / SSCC (unique HU number see the SAP Help page ), it makes sens to transfer the EXIDV number with the Idoc. HU packing item are created via DESADV if all the customizing is set correctly. See SAP note 831204 . Several inbound deliveries could be created automatically due to an automatic delivery split. IDoc Status: 51: only if inbound delivery could not be created 52: if at least one inbound delivery could be created but errors or warnings occurred 53: if no error/ warning occured

o o

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy