SAP ABAP Data Element AHDIS (MRP relevancy for dependent requirements)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷
MD03 (Package) Appl. development R/3 MPS/determin. requirements planning
⤷
⤷
⤷
Basic Data
| Data Element | AHDIS |
| Short Description | MRP relevancy for dependent requirements |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | AHDIS | |
| 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 | MRP_RELEVANCY_DEP_REQUIREMENTS | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | MRP DepReq |
| Medium | 15 | MRP dep. reqmts |
| Long | 20 | MRP dep.requirements |
| Heading | 10 | MRP DepReq |
Documentation
Definition
This indicator controls whether dependent requirements are relevant to MRP or not. Dependent requirements include dependent reservations and stock transfer requirements.
Use
You only use this indicator in connection with planning strategies for make-to-stock production, assembly planning. Note that the indicator Dependent requirements not relevant to MRP should only be used when, for example, planned independent requirements exist for an assembly. In this case, no receipt elements for the dependent requirements in MRP should be created as receipts have already been created for the planned independent requirements.
History
| Last changed by/on | SAP | 19991108 |
| SAP Release Created in |