Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
CU (Package) Variant Configuration
Basic Data
| Data Element | DPSEU |
| Short Description | Read Special Procurement Key |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | X | |
| 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 | Phantom |
| Medium | 15 | Expl. phantom |
| Long | 20 | Special procurement |
| Heading | 0 |
Documentation
Definition
If a material master record has special procurement key 50 (phantom assembly), then dependent requirements, planned orders, and purchase orders are generated for the components of the material, not for the phantom assembly itself. Only the components of the phantom assembly are displayed when you explode the BOM in production.
Phantom assemblies let you group components together for organizational or technical reasons, even though they do not constitute an assembly from the production point of view.
If you set this indicator, the special procurement key is read when you explode the BOM in the configuration editor. This means that materials that have the phantom-assembly special procurement key are not displayed - only their components are displayed.
History
| Last changed by/on | SAP | 20000131 |
| SAP Release Created in |
