Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
LVS (Package) Application development Warehouse Management (WM)
Basic Data
| Data Element | KOBER |
| Short Description | Picking Area |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | KOBER | |
| Data Type | CHAR | Character String |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table | T30A |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | PICK_AREA | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Pick. Area |
| Medium | 15 | Picking Area |
| Long | 20 | Picking Area |
| Heading | 3 | PAr |
Documentation
Definition
Groups storage bins together from the standpoint of picking strategies and is a symmetrical counterpart to the storage section, which groups bins from the standpoint of putaway strategies. The picking area is therefore parallel in nature to the storage section and is situated hierarchically between the storage type and storage bin.
Supplementary Documentation - KOBER 0001
Use
This field represents the planned picking area in contrast to the operative picking area of the bin status report.
The rough workload forecast calculates the workload on the basis of this planned picking area since the operative picking areas depend on the storage bins and these are not known in the documents that are included in the rough workload forecast.
This also has performance advantages since you do not have to access the operative picking area through further tables.
Procedure
For storage types with a fixed-bin structure (stock placement strategy fixed bin), the operative picking area of the fixed bin is determined from the bin status report and displayed in this field. This field is not ready for input in this case.
For storage types without a fixed-bin structure, the planned picking area should be entered if the rough workload forecast is to use data on the basis of the picking area.
If no analysis based on the picking area is planned for the rough workload forecast, this field can remain empty.
Examples
Dependencies
History
| Last changed by/on | SAP | 19971104 |
| SAP Release Created in |
