Hierarchy
ECC-DIMP (Software Component) DIMP⤷
IS-A-EMM (Application Component) Enhancements to scheduling agreements MM (Outbound)⤷
ISAUTO_ME (Package) ISAUTO: Purchasing
Basic Data
| Data Element | ISAUTO_XDELIV |
| Short Description | Return via Outbound Delivery |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | MB_DELIV | |
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Via OutDel |
| Medium | 17 | Via Outb. Deliv. |
| Long | 30 | Return via Outbound Delivery |
| Heading | 29 | Return via Outbound Delivery |
Documentation
Definition
Indicates that the system generates a delivery in the background via the application component Shipping (LE-SHP) when posting the return delivery.
Note
When you create a delivery via Shipping, the system creates an outbound delivery instead of the material document. This outbound delivery is displayed in the PO history together with the associated inbound delivery.
The material document is not generated until the goods issue is posted.
Use
If you select this indicator, an outbound delivery will be created in the background when quantity differences are posted in the Automotive goods receipt process. This enables you to use all the functions of Shipping (LE-SHP), such as picking and packing.
In the PO history or in the confirmation overview for the scheduling agreement, you see the return delivery as an own delivery (or line).
Prerequisites
To create a return delivery with an outbound delivery, you must use a confirmation control key with GR assignment.
Dependencies
In the confirmation overview of the scheduling agreement, the inbound delivery is shown with the associated outbound delivery.
The external document of the outbound delivery in the confirmation overview indicates the associated inbound delivery.
The MRP reduced quantity attributable to the outbound delivery changes by the returned quantity only when the goods issue for the outbound delivery is effected. Then the inbound and outbound deliveries are offset against each other in terms of MRP.
The still-open quantity re-suggested when an inbound delivery is created (with reference to a scheduling agreement).
Example
You have posted a goods receipt of 10 pc with reference to an inbound delivery.
You return 2 pc due to poor quality.
In the confirmation overview, you get two lines: one for the inbound delivery and one for the outbound delivery/return delivery. In the view of the MRP reduced quantites, the two quantites are consolidated (netted off) so that the MRP reduced quantity amounts to 8 pc.
Goods movement Quantity MRP reduced quantity
Inbound delivery 10 0
Goods receipt 10 10
Return delivery -2 0
Goods issue -2 -2
Total MRP reduced quantity = 8
If you create a return delivery without outbound delivery, you can specify in the quantity difference profile whether or not the shipping notification/inbound delivery is to be closed. The material document for the return delivery is generated immediately.
In the PO history, you see one material document for the goods receipt and one for the return delivery.
History
| Last changed by/on | SAP | 20050301 |
| SAP Release Created in | 470 |
