Delivery Interface


At present, deliveries are communicated in a variety of ways to internal and external instances, such as the following examples:

1. As an outbound shipping notification in the vendor's system and inbound in the customer's system.
2. For communicating with external warehouse by sending a picking request and reporting the picking results and packing data.

Up till now, various message types and IDocs were used to do the above. In Release 4.0, a generic IDoc (called DELVRY01) will be available to support all of these scenarios, as well as new scenarios such as the shipping order. The IDoc represents the object 'delivery' exactly and contains all relevant data.

In Release 4.0, the new procedure supports the following scenarios:

1. Outbound shipping notification using EDI (message LAVA/DESADV)
This enables you to communicate additional information such as serial numbers and configuration
2. Inbound shipping notification using EDI (message DESADV)
In Release 4.0, it is also possible to copy packaging data to the MM system when shipping notifications are received via EDI. This enables posting of the goods receipt for a package.
3. Shipping order via EDI to a service agent (message SHOR/SHPORD)
New in 4.0
4. Shipping confirmation of the service agent via EDI (message SHPCON)
New in 4.0
5. Stock order to own external system using ALE (message WSOR/WHSORD)
New in 4.0
6. Warehouse confirmation from an external system using inbound ALE (WHSCON)
Here, the two messages for picking results and packing data have been fused together. Furthermore, it is possible to report actual weights and volumes to update the delivery.
7. Notification of shipping using EDI (message CANO/CARNOT)
New in 4.0

Change system parameters in customizing

For new installations of Release 4.0, the system is automatically configured so that the new technique is used for all messages.

Upgrade installations of Release 4.0 are upwardly compatible. This means that the messages that you use will function as usual. In order to activate the new technique for a message that you have already used, you need to adjust the partner profiles accordingly. For instance, in the case of an outbound shipping notification (message LAVA) you would have to replace the process code SD04 or SD05 with DELV. You also need to specify the new type DELVRY01 instead of the IDoc basic type DESADV01 angeben.

To do this, select Partner profiles.

You also need to assign the output types LAVA, WSOR, SHOR and CANO to the output determination procedure.

To do this, select

Maintain output determination procedure .

Further notes

The existing data structures (DESADV01/DESADV, SDPIOD01/ PICKSD, SDPIID01/SDPICK and SDPAID01/SDPACK) and their processing logic will remain in 4.0 release levels, but will not be developed any further.

Due to the fact that DELVRY01 is supplied with a maximum amount of data when it is sent, in cases where a large volume of communication data is involved it may be necessary to reduce this IDoc down to the specific data required for this message. To do this, use the reduction technique for IDoc types.

Up till now, identifying the partner of a delivery at the ship-to party of the message was either only limited (per customer) or too detailed (for each sales area). In 4.0A, there is a new, more comprehensive conversion. You can maintain the necessary master data under Sales and Distribution -> Master data -> Output -> Partner conversion.