Flexible Delivery Processing
Purpose
You can use this process to automate outbound processing and inbound processing in ERP systems. The process allows you to:
· Create outbound deliveries in the ERP system
· Pack and load outbound deliveries in SAP Auto-ID Infrastructure
· Post goods issue in the ERP system
· Send advanced shipping notifications (ASN)
· Create inbound deliveries in the ERP system
· Unload inbound deliveries in SAP Auto-ID Infrastructure
· Post goods receipt in the ERP system
· Trigger in SAPAuto-ID Infrastructure during packing, unpacking, and moving of objects, the creation and updating of handling units in SAPERP
¡ Create and pack handling units that contain commissioned tags for serialized material
· Route updates to backend systems based on the reference attributes of physical objects in SAPAuto-ID Infrastructure
· Map SAPERP plant/storage locations to SAPAuto-ID Infrastructure locations to enable HU creation, packing, and movement
Flexible Delivery Processingallows you to process deliveries using standard ERP interfaces. It enables delivery processing without the SAPAuto-ID Infrastructure 2.1 add-on (see SAPNote 777246). SAPAuto-ID Infrastructure supports the process for multilevel hierarchies.
Prerequisites
● The intermediate document (IDoc) DELVRY03 or DELVRY05 is available in your ERP system.
● You have set up the system landscape and created the settings in Customizing as described in the configuration documentation for the Flexible Delivery Processing process in SAP Solution Manager.
Process Flow
...
1. Create outbound delivery (ERP system / Supplier)
The supplier’s ERP system sends an IDoc of type DELVRY03 or DELVRY05 to SAPAuto-ID Infrastructure. The ERP system and SAPAuto-ID Infrastructure communicate through an XI system.
2. Pack outbound delivery (optional) (SAPAuto-ID Infrastructure)
a. SAPAuto-ID Infrastructure assigns the outbound delivery to the assigned RFID device group.
b. The supplier packs the outbound delivery using the outbound delivery document.
SAPAuto-ID Infrastructure calls the rule PACK_AA for packing. This rule does not send observations to the ERP system.
3. Load outbound delivery (SAPAuto-ID Infrastructure)
a. For loading outbound deliveries, the system calls the rule LOAD_AA.
Based on the parameters of the activity HU_PACKMAT_DETERM, the rule LOAD_AA determines the correct packaging materials. The activity parameters specify the packaging materials for each object hierarchy level, starting with the top level. If the number of levels in the object hierarchy is less than or equal to the available parameters, SAPAuto-ID Infrastructure assigns the specified packaging materials to the objects of the object hierarchy and the objects themselves become handling units. If an object hierarchy has more levels than there are parameters available, the lower level objects do not become handling units.
SAP Auto-ID Infrastructure checks the packed quantity and packed products against the expected quantity and expected products. It also checks packed objects against expected objects and updates the document quantities according to the packing observations.
SAPAuto-ID Infrastructure checks the loaded quantity and products against expected quantity and products. The system does not check loaded objects against expected objects.
SAPAuto-ID Infrastructure also checks whether the outbound delivery document has already been processed. This check could be helpful, for example, in preventing you from using a document for packing that has already been processed for loading and sent to the ERP system.
b. SAPAuto-ID Infrastructure transfers the loading information to the supplier’s ERP system, using either the DELVRY03 or the DELVRY05 IDoc interface.
4. System updates outbound delivery and posts goods issue (ERP system/Supplier)
5. System sends ASN (ERP system / Supplier)
The supplier’s ERP system sends an advanced shipping notification (ASN) to the customer’s ERP system. The XI system updates the ASN with the observed IDs of the loaded objects which it obtains by calling the service /AIN/PUB_BTD_BY_INTIDS. Observed IDs are only available in SAPAuto-ID Infrastructure.
The service interface DespatchedDeliveryNotificationIn does not support physical object attributes. The XI system only enriches the ASNwith electronic labels of the observed IDs of the physical objects and not their attributes.
6. Create inbound delivery (ERP system / Customer)
After the customer’s ERP system receives the ASNthrough the XI system, it creates an inbound delivery. The XI system adds the inbound delivery number to the ASN and sends it to SAP Auto-ID Infrastructure.
7. Unload inbound delivery (SAPAuto-ID Infrastructure)
SAPAuto-ID Infrastructure transfers the unloading information to the customer’s ERP system, using the DELVRY03 or the DELVRY05 IDoc interface.
If you receive an unexpected overdelivery during unloading, you can only enter the details in SAP Auto-ID Infrastructure without the hierarchy information. For example, you cannot enter information about where in the HU hierarchy a particular package is nested. Instead you must enter the unloaded product quantities for the individual packages contained in the extra HU. For example, the RFID tag or barcode must contain this information.
8. System updates inbound delivery and posts the goods receipt (ERP system, customer)
To extend or change the messages that are exchanged between SAP Auto-ID Infrastructure and the ERP system, use the following Business Add-Ins (BAdIs):
■ /AIN/IF_BADI_ASN_IN
■ /AIN/IF_BADI_DLV_EL
■ /AIN/ACTV_DLV_CONF
For more information, see the SAP Auto-ID Infrastructure system documentation.
See also: