Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-TS (Application Component) Technical Application Support⤷
BMG (Package) Material Master: Componentization Interfaces
Basic Data
| Data Element | PLSEL |
| Short Description | Issue Storage Location Selection |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | PLSEL | |
| 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 | ISSUE_STORAGE_LOCATION_SELECT | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Issue SLoc |
| Medium | 15 | Issue stor.loc. |
| Long | 20 | Issue stor.loc.sel. |
| Heading | 5 | ISLoc |
Documentation
Definition
Determines how the system finds the issue storage location (the production storage location from which the components are taken to produce an assembly) for the component if no issue storage location is defined for the component in the BOM of the assembly. You have the following options:
- Strategy 1 (or blank)
The system only checks for components whose issue storage location is defined in the material master record and copies it from there.
- Strategy 2
The system uses the default issue storage location specified in the material master record of the assembly in the production version. If no default issue storage location is specified in the production version, then the system uses the receiving storage location for the assembly as issue storage location for components.
- Strategy 3
The system proceeds according to strategy 1 first and then according to strategy 2.
- Strategy 4
The system proceeds according to strategy 2 first and then according to strategy 1.
If, in addition, a supply area is defined, it can be found using the same strategy as the one used for the issue storage location.
History
| Last changed by/on | SAP | 19990629 |
| SAP Release Created in |
