Hierarchy
BBPCRM (Software Component) BBPCRM⤷
LO-MDS (Application Component) Merchandise Distribution⤷
WFRM (Package) ISR: Cross-Docking and Floor-Ready Merchandise
Basic Data
| Data Element | DE_WMD_OBDLV_USE_SITUA |
| Short Description | Control of Determination of Storage Area |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BOOLE | |
| 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 | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Site Ind. |
| Medium | 15 | Site Indicator |
| Long | 20 | Determntn StorArea |
| Heading | 40 | Determination of Storage Area |
Documentation
Definition
If you set this indicator, when you create outbound deliveries, the determination of the storage location is taken into account. Otherwise, the storage location of the goods received is used.
Use
If you use different storage location determinations when goods are received or issued, in certain cases you can determine a picking location that is different from the storage location determined for the goods received.
You can prevent this by always predefining the storage location determined as the storage location for received goods; a new storage location is not determined for the goods issued.
Dependencies
If the storage location determination finds a different storage location for the outbound delivery than for the goods received, the goods should be transferred from one storage location to another via an internal transfer order . This transfer is not triggered automatically by ERP.
Example
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in | 700 |
