PRIO_REQ in RESB
Reqmt Priority (DE: Bedarfsprio)
PRIO_REQ is a field in SAP table RESB (Reservation/dependent requirements). It represents "Reqmt Priority". Data element: PRIO_REQ. Available in 5 CDS view(s) as prio_req.
Business Meaning
| Description (EN) | Reqmt Priority |
|---|---|
| Beschreibung (DE) | Bedarfsprio |
| Data Element | PRIO_REQ |
| Key Field | No |
CDS Views & Technical Names (5)
RESB.PRIO_REQ is exposed in CDS views under the following technical name. Views reading the table directly are listed first; "via" marks views that pass the field on through intermediate views.
prio_req
(5 views)
| View | Access | VDM | Release | Description |
|---|---|---|---|---|
| /merp/pm_Wo_Component | direct | CDS View: Maintenance Order Components | ||
| PPH_E_MRBED_1 | direct | |||
| PPH_E_RESB_FLEX | direct | |||
| PPH_DDL_RESB_FLEX_B | via 2 level | |||
| PPH_DDL_RESB_FLEX_P1 | via 3 levels |
Other Tables with Field PRIO_REQ (5)
| Table | Data Element | Key | Description |
|---|---|---|---|
| EBAN | PRIO_REQ | Purchase Requisition | |
| EKPO | PRIO_REQ | Purchasing Document Item | |
| MDTB | PRIO_REQ | MRP Table | |
| MMPUR_EXT_EKPO | PRIO_REQ | Purchasing Document Item | |
| VSRESB_CN | PRIO_REQ | Version: Reservation/Dependent requirements |
Learn More
- Understanding Data Lineage in SAP S/4HANA
- SAP Tables vs CDS Views — Key Differences
- Understanding the SAP S/4HANA Data Model
- BSEG to ACDOCA: The Universal Journal Migration
- Business Partner Migration: KNA1/LFA1 to BUT000
- Material Document Migration: MSEG/MKPF to MATDOC
- How to Find the Right CDS View for an SAP Table
- Sales Document Status Migration: VBUP/VBUK Removal in S/4HANA
- CO Tables in S/4HANA: COEP, COBK, COSS, COSP to ACDOCA