MMPRC_DISTR_PTNR
Table to hold partner data in Purchasing doc distribution
MMPRC_DISTR_PTNR is an SAP database table in S/4HANA. Table to hold partner data in Purchasing doc distribution. It contains 10 fields. 1 CDS views read from this table.
CDS Views using this table (1)
| View | Type | Join | VDM | Description |
|---|---|---|---|---|
| P_CntrlPurchaseContractPartner | view | from | BASIC | Basic View for Partners in Central Contract Distribution |
Fields (10)
| Key | Field | Data Element | Description | Domain | Type | Length |
|---|---|---|---|---|---|---|
| KEY | mandt | mandt | Client | |||
| KEY | purchasingdocument | ebeln | Purchasing Doc. | |||
| KEY | purchasingdocumentitem | ebelp | Item | |||
| KEY | distributionnumber | mm_purgdoc_distr_num | Distr. Number | |||
| KEY | partnercounter | parza | Partner counter | |||
| partnerfunction | parvw | Partner Functn | ||||
| extplantforpurg | mm_pur_hub_werks | Plant | ||||
| suppliersubrange | ltsnr | Suppl. Subrange | ||||
| supplier | lifn2 | Ref. to suplr | ||||
| purchasingorganization | ekorg | Purchasing Org. |
Derived SQL schema, reconstructed from the indexed DDIC field metadata (field names, types, lengths and key flags) — a functional representation, not the verbatim SAP source.
-- Table to hold partner data in Purchasing doc distribution
-- Category TRANSPARENT · Delivery class A
-- Derived schema, generated from indexed DDIC field metadata (not the verbatim SAP source).
CREATE TABLE MMPRC_DISTR_PTNR (
MANDT, -- Client [mandt]
PURCHASINGDOCUMENT, -- Purchasing Doc. [ebeln]
PURCHASINGDOCUMENTITEM, -- Item [ebelp]
DISTRIBUTIONNUMBER, -- Distr. Number [mm_purgdoc_distr_num]
PARTNERCOUNTER, -- Partner counter [parza]
PARTNERFUNCTION, -- Partner Functn [parvw]
EXTPLANTFORPURG, -- Plant [mm_pur_hub_werks]
SUPPLIERSUBRANGE, -- Suppl. Subrange [ltsnr]
SUPPLIER, -- Ref. to suplr [lifn2]
PURCHASINGORGANIZATION, -- Purchasing Org. [ekorg]
PRIMARY KEY (MANDT, PURCHASINGDOCUMENT, PURCHASINGDOCUMENTITEM, DISTRIBUTIONNUMBER, PARTNERCOUNTER)
);
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