1 Inbound Delivery Processes
If a material document is to be created when the goods receipt posting for the inbound delivery is carried out, then the goods receipt assignment must be defined in the confirmation control.
Inbound delivery creation options include:-
- You can use an inbound electronic data interchange (EDI) shipping notification from your vendor to create an inbound delivery. The message type for this is DESADV.
- You can create a delivery manually with reference to a particular order.
- You can use collective processing to deliver goods for all purchase orders that are due to be shipped. In this case, the system automatically creates multiple inbound deliveries. This can be done either online or in the background.
If you use Warehouse Management (WM) and create a transfer order to putaway the inbound delivery, you must also use Handling Unit Management. Due to this requirement, you have to pack materials in the inbound delivery before you can book the goods receipt. Packing automatically generates handling units and inspection lots for the handling units. You can use Customizing to control whether you first execute the putaway or post the goods receipt after packing. However, this decision can only be made using Handling Unit Management.
It is only possible to use WM with quality management and without Handling Unit Management along with certain specific settings. The item categories of the inbound delivery are not allowed to be relevant to putaway, which ensures that a connection is not created to WM. The inbound delivery can then only be used for goods receipt posting along with transaction MIGO, which posts goods receipt for the purchase order items. This creates an inspection lot and a quantity with stock category Q with the inspection lot number in WM.
2 Outbound Delivery Processes
2.1 Creating outbound delivery
You can create an outbound delivery manually with or without reference to a particular order. However, if you create a delivery manually, you cannot deliver purchase orders or other requests.
Delivery Due List
You can deliver goods for all types of shipping documents if you use collective processing (delivery list). In this case, the system automatically creates multiple outbound deliveries. This can take place online or in the background (overnight, for instance).
You can model the different business processes for deliveries by using delivery scenarios. Delivery scenario models business process. They are already defined in ECC.
The requirements resulting from the delivery process are modeled using user roles (also called list profiles):-
- Fine-tune processing of the delivery due list
- Control the scope of selection, the display of the delivery due list, the type of delivery, and so on
User role is assigned to delivery scenario which can be maintained in Customizing.
Delivery scenario and user role (aka list profile) can be set as parameter of user’s logon ID.
Key for list profile
2.2 Output in Shipping
The following output types are pre-configured in standard SAP:-
LAVA (Outb.shpg notif.)
LD00 (Delivery Note)
PL00 (Picking list)
WA00 (M. tag)
SA00 (Shipping order)
LQCA/LQCB (Quality cert.)
0001 (Shipping label)
LL00 (Freight list) etc.
Output can be on Header or Item level.
To be continued….