PPS_PO_PRTN_D
Draft table for entity R_PPS_PURCHASEORDERPARTNERTP
PPS_PO_PRTN_D is an SAP database table in S/4HANA. Draft table for entity R_PPS_PURCHASEORDERPARTNERTP. It contains 33 fields. 1 CDS views read from this table.
CDS Views using this table (1)
| View | Type | Join | VDM | Description |
|---|---|---|---|---|
| R_PPS_PurOrdPrtnDrft | view_entity | from | BASIC | Purchase Order Partner - Draft |
Fields (33)
| Key | Field | Data Element | Description | Domain | Type | Length |
|---|---|---|---|---|---|---|
| KEY | mandt | mandt | Client | |||
| KEY | purchaseorder | ebeln | Purchasing Doc. | |||
| KEY | partnerfunction | parvw_unv | Partner Funct. | |||
| KEY | draftuuid | sdraft_uuid | Draft Document ID | |||
| parentdraftuuid | sdraft_uuid | Draft Document ID | ||||
| suppliersubrange | ltsnr | Suppl. Subrange | ||||
| plant | werks_d | Plant | ||||
| purchasingorganization | ekorg | Purchasing Org. | ||||
| partnercounter | parza | Partner counter | ||||
| createdbyuser | ernam | Created By | ||||
| creationdate | erdat | Created On | ||||
| purchasingdocumentpartnertype | nrart | Partner Type | ||||
| supplier | lifnr | Supplier | ||||
| supplierhierarchycategory | hityp_lh | Hierarchy Cat. | ||||
| suppliercontact | parnr | Contact Person | ||||
| personworkagreement | pernr_d | Personnel No. | ||||
| employmentinternalid | pernr_d | Personnel No. | ||||
| defaultpartner | defpa | Default Partner | ||||
| partnerfunctionforedit | parvw_unv | Partner Funct. | ||||
| partnerfunctionname | vtxtk | Name | ||||
| purchasingdocumentpartner | mm_pur_partner | Partner | ||||
| purchasingdocumentpartnername | mm_pur_partnername | Partner Name | ||||
| streetname | ad_street | Street | ||||
| housenumber | ad_hsnm1 | House Number | ||||
| postalcode | ad_pstcd1 | Postal Code | ||||
| cityname | ad_city1 | City | ||||
| country | land1 | Country/Reg. | ||||
| countycode | ad_cntynum | County code | ||||
| region | regio | Region | ||||
| phonenumber | ad_tlnmbr1 | Telephone | ||||
| faxnumber | ad_fxnmbr1 | Fax | ||||
| emailaddress | ad_smtpadr | E-Mail Address | ||||
| ppsfieldchangeindicatorbinary | pps_e_control_flag | Control |
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.
-- Draft table for entity R_PPS_PURCHASEORDERPARTNERTP
-- Category TRANSPARENT · Delivery class A
-- Derived schema, generated from indexed DDIC field metadata (not the verbatim SAP source).
CREATE TABLE PPS_PO_PRTN_D (
MANDT, -- Client [mandt]
PURCHASEORDER, -- Purchasing Doc. [ebeln]
PARTNERFUNCTION, -- Partner Funct. [parvw_unv]
DRAFTUUID, -- Draft Document ID [sdraft_uuid]
PARENTDRAFTUUID, -- Draft Document ID [sdraft_uuid]
SUPPLIERSUBRANGE, -- Suppl. Subrange [ltsnr]
PLANT, -- Plant [werks_d]
PURCHASINGORGANIZATION, -- Purchasing Org. [ekorg]
PARTNERCOUNTER, -- Partner counter [parza]
CREATEDBYUSER, -- Created By [ernam]
CREATIONDATE, -- Created On [erdat]
PURCHASINGDOCUMENTPARTNERTYPE, -- Partner Type [nrart]
SUPPLIER, -- Supplier [lifnr]
SUPPLIERHIERARCHYCATEGORY, -- Hierarchy Cat. [hityp_lh]
SUPPLIERCONTACT, -- Contact Person [parnr]
PERSONWORKAGREEMENT, -- Personnel No. [pernr_d]
EMPLOYMENTINTERNALID, -- Personnel No. [pernr_d]
DEFAULTPARTNER, -- Default Partner [defpa]
PARTNERFUNCTIONFOREDIT, -- Partner Funct. [parvw_unv]
PARTNERFUNCTIONNAME, -- Name [vtxtk]
PURCHASINGDOCUMENTPARTNER, -- Partner [mm_pur_partner]
PURCHASINGDOCUMENTPARTNERNAME, -- Partner Name [mm_pur_partnername]
STREETNAME, -- Street [ad_street]
HOUSENUMBER, -- House Number [ad_hsnm1]
POSTALCODE, -- Postal Code [ad_pstcd1]
CITYNAME, -- City [ad_city1]
COUNTRY, -- Country/Reg. [land1]
COUNTYCODE, -- County code [ad_cntynum]
REGION, -- Region [regio]
PHONENUMBER, -- Telephone [ad_tlnmbr1]
FAXNUMBER, -- Fax [ad_fxnmbr1]
EMAILADDRESS, -- E-Mail Address [ad_smtpadr]
PPSFIELDCHANGEINDICATORBINARY, -- Control [pps_e_control_flag]
PRIMARY KEY (MANDT, PURCHASEORDER, PARTNERFUNCTION, DRAFTUUID)
);
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