SAP ABAP Data Element AGREQ (Requirements totaling)
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
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 | AGREQ |
| Short Description | Requirements totaling |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | AGREQ | |
| 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 | REQ_TOTALING | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Aggr.reqmt |
| Medium | 16 | Aggregate reqmts |
| Long | 20 | Aggregate reqmts |
| Heading | 1 | S |
Documentation
Definition
Controls whether dependent requirements for a component are grouped to total requirements on a daily basis when there are various dependent requirements for this component on one day.
Use
Dependencies
The orders, from which the dependent requirements result, must be individual customer orders.
The individual/collective indicator in the material master must be set to collective requirements for the components for which the dependent requirements exist.
Example
History
| Last changed by/on | SAP | 19981111 |
| SAP Release Created in |
