The outbound delivery document is the central document in shipping. It forms the basis for further shipping activities such as picking, packing, and goods issue posting.
After creating outbound delivery documents (normally for stock transport orders or sales orders), you can group them together in wave picks (work packages for the goods issue processes that have to be processed during a specified time interval), if necessary. This can be done for example to map the shift plan of the warehouse. The outbound deliveries have to be picked, and can also be packed. Finally, they are ready for goods issue posting.
The standard version means that the picking storage location is not connected to a warehouse management system. Therefore, the picked quantities are directly maintained in the delivery, and after (optional) packing, the goods issue can be posted. In contrast, if the merchandise is picked from a full WM storage location, then a separate picking document is generated, the transfer order. The system determines the relevant picking storage bins based on the assigned picking strategy. The picking activities have to be confirmed. However, if desired, automatic confirmation can be set in customizing. It is possible to connect radio frequency devices, for example for voice picking to support the picking processes. With confirmation of the transfer order, the picked quantities are updated in the outbound delivery, which is then ready for goods issue posting.
Using Lean Warehouse Management (WM), you execute picking using transfer orders (picking requests), even though no storage bins are managed in the system. In Lean WM, neither the putaway processes nor the picking processes that use WM strategies are executed as follow-up processes in WM. This means that stocks are not updated at storage bin level using quants. Instead, goods receipt and goods issue processes are actually carried out at storage location level. Still, you can assign a fixed storage bin to the article/DC in the article master, which is later included in the transfer order as information for the picker.
The processes in Lean WM are fundamentally the same as those in standard Warehouse Management. For the picking step in the goods issue process, transfer orders are created for the outbound delivery items. The other structures in WM (storage types, doors, staging areas, storage sections) can be mapped in Lean WM in exactly the same way as in WM.
The shipping point is the organizational unit in the SAP system that is responsible for the execution of goods issue processes (and, as receiving point, for inbound processes). Consequently, it can be found in the header of the delivery documents. It is determined for a combination of the recipient’s shipping condition (for example, express), the article’s loading group (for example, forklift) and the supplying site.
Before you can provide your customer a delivery date for a particular article, the system needs to know all the necessary lead times for the different steps in the goods issue and transportation processes.
You can define time periods for preparation and loading merchandise for the shipping point.
The shipping point is normally determined automatically for each item in the sales document. The value proposed by the system can be changed manually at a later date if you have defined alternative shipping points for your DC.
When deliveries are generated for purchase orders and/or sales orders (referred to as PO/SO in the previous figure, Shipping Point), a delivery split might apply. This occurs when (based on the shipping point determination criteria) a different shipping point is determined for the items in a preceding document. For example, this could happen when different loading groups are assigned to the articles.
Outbound delivery documents consist of a header and any number of items.
The header contains data that is valid for the entire document. For example, this includes the recipient, the shipping point, and possibly the route.
The items contain all relevant information about the articles that are going to be delivered.
The information in the outbound delivery document is displayed in different screen areas:
The overview screen contains much of the header and item data, which are organized thematically in tab pages. This allows the user to find a lot of important data on the same screen.
An additional screen each is available for displaying detailed information at header level and item level. This data is also grouped in tab pages.
For example, at header level you can access data on processing, picking, loading, transportation, global trade services/customs, texts, partners, messages, parcel tracking, and conditions.
The item detail screen displays tab pages containing item-related information, such as processing information, material, and picking details, loading and shipment data, and so on.
When an outbound delivery is created, several background activities can be performed by the system, depending on customizing settings. For example, these are (re-)scheduling, (actual) route- and route schedule determination, door/picking zone determination, a (new) ATP check, and picking location determination.