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_URG |
| Short Description | Requirement Urgency |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | PRIO_URG | |
| Data Type | NUMC | Character string with only digits |
| Length | 2 | |
| Decimal Places | 0 | |
| Output Length | 2 | |
| 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 | ReqmtUrgcy |
| Medium | 15 | Reqmt Urgency |
| Long | 20 | Requirement Urgency |
| Heading | 19 | Requirement Urgency |
Documentation
Definition
Is used to prioritize material requisitions in detail.
In Customizing, you assign specific requirement urgency groups to requirement urgencies and therefore define how the system determines the overall priority of a material requirement by means of the requirement urgency group and organizational priority.
You can assign the requirement urgency in purchase requisitions, purchase orders, and reservations at item level. Depending on the requirement urgency you assigned, the system determines the requirement priority (overall priority) of a material requirement.
This also applies to purchase requisitions and reservations that are implemented as requirement coverage elements within requirements planning. 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 |
