Document that is triggered in the warehouse directly.
Extended Warehouse Management (EWM) sends the direct outbound delivery order to SAP ERP. The direct outbound delivery order contains the SAP ERP document number. The structure and data of the direct outbound delivery order match those of an outbound delivery order that is triggered in SAP ERP.
Unlike EWM outbound delivery orders, for which SAP ERP generated a reference document previously, you or EWM can also generate direct outbound delivery orders directly and locally in EWM, which EWM then sends to SAP ERP.
You can use direct outbound delivery orders in the following scenarios:
Pickup
Direct sales
For direct sales, transportation activities do not apply, since the customer asks for the goods and picks them up on-site in the warehouse. You do not need to create a sales order for this. The direct outbound delivery order you generated manually in EWM forms the basis for the delivery in SAP ERP. The delivery in SAP ERP forms the outbound document for billing.
You can also trigger direct sales in SAP ERP without generating a sales order.
Account assignment
For account assignment, transportation activities also do not apply, since the internal or external customer asks for the goods and picks them up on-site in the warehouse. Unlike for direct sales, you post a goods issue with account assignment for the goods, for the cost center, for example.
You can also trigger goods issue with account assignment in SAP ERP without generating a sales order.
The Direct Outbound Delivery Order for Scrapping forms the last step in the scrapping process. You post the goods to be scrapped with the goods issue from the warehouse stock. Whereas you can also trigger the preparation for scrapping – such as collecting goods in a scrapping container – using a posting change request from SAP ERP, you always trigger this last step locally in the warehouse.
Kit to stock or reverse kitting
For kit to stock, you use a value-added service orderto create a kit from different components. If you want to reserve the corresponding components, you can use a direct outbound delivery order. When you have created the kit and post goods issue for the direct outbound delivery order, EWM reduces the stock of the respective components.
You can use the direct outbound delivery order to execute actions that you require for generating and processing an outbound delivery in the warehouse, such as picking. You can carry out the following for a direct outbound delivery order:
Save
Validate
Archive
Delete
For the structural description of the direct outbound delivery order, see Outbound Delivery Order .
The structure of a direct outbound delivery order also contains the following, differentiating it from the structure of an outbound delivery order:
Document categories with different document types
You can define the document types in Customizing for delivery processing.
Note
For more information about defining document types in EWM, see the Implementation Guide (IMG) for
EWM
under
:
An item category with different item types
You can define the item types in Customizing for delivery processing.
Note
For more information about defining item types in EWM, see the Implementation Guide (IMG) for
EWM
under
:
Direct outbound delivery orders have the following properties that differentiate them from outbound delivery orders that were generated in EWM based on outbound deliveries created in SAP ERP:
Necessity of the availability check, as this check is usually triggered in SAP ERP
To avoid endangering the continual ability to deliver, the planning situation must be adjusted with the availability check.
Note
In SAP SCM 5.1, planning-related reservation of the products only takes place if you are using SAP Advanced Planning and Optimization (SAP APO). No reservation takes place for checks in SAP ERP. In exceptional cases, overconfirmation may occur.
A lot of organizational and logistically relevant delivery data that is copied to outbound delivery orders from SAP ERP preceding documents must be specified for the direct outbound delivery orders locally in EWM. Either you enter the data directly, such as the product or quantity, or EWM determines the data automatically using configuration data, such as the goods issue bin for items that are not pick-relevant.
As you start the goods issue process using direct outbound delivery orders in EWM, the underlying document type must display the process correspondingly. EWM uses the process profile to do this. When generating a direct outbound delivery order, you must select the correct document type to ensure the process flow is correct. For more information, see the IMG for EWM under
As no outbound delivery request from SAP ERP exists for direct outbound delivery orders, actions such as splitting direct outbound delivery orders are not possible (see
Delivery Split for Outbound Deliveries
). Direct outbound delivery orders are also always checked, meaning they have the status type
Locked (Unchecked Item)
and status value
No
, and are immediately ready for processing.
Direct outbound delivery orders support processing of non-pick-relevant items, for example, or generation of items from handling units.
As direct outbound delivery orders are created in EWM directly, no availability check is performed in SAP ERP for the required product. Instead, EWM triggers the availability check. Depending on the configuration, the check can be performed in SAP ERP or in SAP APO. For outbound delivery orders replicated from SAP ERP, however, the availability check is triggered in SAP ERP.
For more information, see Availability Check .
EWM can send direct outbound delivery orders for scrapping to SAP ERP. For more information, see the Implementation Guide (IMG) for EWMunder
.If you are not using a corresponding Enhancement Package, only the goods movement posting takes place. There is no delivery replication.When you generate a direct outbound delivery order, EWM automatically performs a Compliance Check .
See also: