Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-MSA (Application Component) Mobile Sales⤷
CDB (Package) new CDB tables for new BDocs for CRM 3.0
Basic Data
| Data Element | PRIO_REQ |
| Short Description | Requirement Priority |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | PRIO_REQ | |
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| 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 | ReqmtPrio. |
| Medium | 15 | Reqmt Priority |
| Long | 20 | Requirement Priority |
| Heading | 11 | Reqmt Prio. |
Documentation
Definition
Specifies the overall priority of material requisitions that the system determines from the combination of requirement urgency group and organizational priority (optional). For this reason, assign precisely one urgency group and, if required, one organizational priority to each requirement priority in the Customizing settings.
Since the system determines the requirement priority on the basis of what has been assigned in Customizing, this field is strictly not ready for input in purchasing and reservation documents.
The result determined for the requirement priority is displayed:
- In purchase requisitions, purchase orders, and reservations at item level
- In the stock/requirements list, planning result, and MRP list
The result determined for the requirement priority is considered as a selection field:
- When purchase orders are created using the assignment list and when purchase orders are generated automatically
- In the reservation list and pick list
During requirements planning, the requirement prioritization affects the external procurement process through purchase requisitions and reservations. The requirements themselves are not prioritized. Subsequent changes to the priorities do not result in requirements planning being carried out again for the relevant materials.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20070729 |
| SAP Release Created in | 520 |
