Hierarchy
BBPCRM (Software Component) BBPCRM⤷
PP-MP-DEM (Application Component) Demand Management⤷
MDPB (Package) Application development R/3 purchasing
Basic Data
| Data Element | BEDAE |
| Short Description | Requirements type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BEDAE | |
| Data Type | CHAR | Character String |
| Length | 4 | |
| Decimal Places | 0 | |
| Output Length | 4 | |
| Value Table | T459A |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | BDA | |
| Default Component name | REQMTS_TYPE | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 6 | RqType |
| Medium | 15 | Reqmts type |
| Long | 20 | Requirements type |
| Heading | 4 | RqTy |
Documentation
Definition
The requirements type determines the planning strategy to be used for a particular requirement.
Supplementary Documentation - BEDAE 0001
Use
The requirements type which you enter here serves as a default value for the items which are to be created.
The requirements type also controls the selection of the fields to be maintained.
Procedure
Examples
Dependencies
Supplementary Documentation - BEDAE 0002
Use
It is used as a selection criterion in the change mode.
Procedure
If you want to select a particular requirements type,
then enter this requirements type.
If you want to select all requirements types that exist for this material,
then leave this field blank.
Examples
Dependencies
Supplementary Documentation - BEDAE 0003
Use
Procedure
To select requirements, proceed as follows:
- if you want to change the requirements of a particular requirements
type then enter the desired requirements type - if you want to change all requirements types then enter
a '*'
Examples
Dependencies
Supplementary Documentation - BEDAE 0004
Use
Procedure
If the material's master record contains an entry for MRP group, and a strategy group has been assigned to this MRP group in Customizing, you do not need to enter a requirements type in this field.
Instead, the system proposes the requirements type on the basis of the main planning strategy in the strategy group.
You can overwrite this proposal with the requirements type of one of the alternative strategies in the same strategy group.
Examples
Dependencies
Supplementary Documentation - BEDAE 0005
Use
Procedure
If the materials' master records contain entries for MRP group, and a strategy group has been assigned to each of these MRP groups in Customizing, you do not need to enter a requirements type in this field.
Instead, the system proposes the requirements types on the next screen, on the basis of the main planning strategy in each strategy group.
You can overwrite these proposals with requirements types from the alternative strategies in the same strategy groups.
Examples
Dependencies
Supplementary Documentation - BEDAE 0006
Use
Procedure
If the materials' master records contain entries for MRP group, and a strategy group has been assigned to each of these MRP groups in Customizing, you do not need to enter a requirements type in this field.
Instead, the system proposes the requirements types on the next screen, on the basis of the main planning strategy in each strategy group.
You can overwrite these proposals with requirements types from the alternative strategies in the same strategy groups.
Examples
Dependencies
Examples
Dependencies
History
| Last changed by/on | SAP | 19991102 |
| SAP Release Created in |
