A_BillingDocRequestPartnerS2S
Header Partners
A_BillingDocRequestPartnerS2S is a Consumption CDS View that provides data about "Header Partners" in SAP S/4HANA. It reads from 1 data source (R_BillgDocRequestPartnerTP) and exposes 8 fields with key fields BillingDocumentRequest, PartnerFunction. It is exposed through 1 OData service (API_BILLINGDOCUMENTREQUESTS2S). Part of development package ODATA_SD_BIL_BDR_API.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| R_BillgDocRequestPartnerTP | R_BillgDocRequestPartnerTP | projection |
Annotations (9)
| Name | Value | Level | Field |
|---|---|---|---|
| AccessControl.authorizationCheck | #MANDATORY | view | |
| EndUserText.label | Header Partners | view | |
| Metadata.ignorePropagatedAnnotations | true | view | |
| ObjectModel.usageType.dataClass | #TRANSACTIONAL | view | |
| ObjectModel.usageType.serviceQuality | #C | view | |
| ObjectModel.usageType.sizeCategory | #L | view | |
| OData.entityType.name | BillingDocumentRequestPartner_Type | view | |
| VDM.lifecycle.contract.type | #PUBLIC_REMOTE_API | view | |
| VDM.viewType | #CONSUMPTION | view |
OData Services (1)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| API_BILLINGDOCUMENTREQUESTS2S | API_BILLINGDOCUMENTREQUESTS2S | V4 | C2 | C1 |
Fields (8)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | BillingDocumentRequest | HeaderPartner | BillingDocumentRequest | |
| KEY | PartnerFunction | HeaderPartner | PartnerFunction | Partner Functn |
| Customer | HeaderPartner | Customer | Sold-to Party | |
| Supplier | HeaderPartner | Supplier | Supplier | |
| Personnel | HeaderPartner | Personnel | Personnel No. | |
| ContactPerson | HeaderPartner | ContactPerson | Contact Person Key | |
| ReferenceBusinessPartner | HeaderPartner | ReferenceBusinessPartner | Busn. Partner | |
| BusinessPartnerAddressUUID | HeaderPartner | BusinessPartnerAddressUUID | UUID |
Derived SQL interpretation, reconstructed from the parsed view metadata (data sources, associations, and field mappings). SAP annotations are omitted and the structure is reformulated as SQL — this is a functional approximation, not the verbatim SAP source.
-- Derived SQL interpretation of CDS view A_BillingDocRequestPartnerS2S.
-- Reconstructed from parsed metadata (data sources, associations, fields).
-- SAP annotations are omitted and the structure is reformulated as SQL;
-- this is a functional approximation, not the verbatim SAP source. Some join
-- conditions may be unavailable and a few CDS constructs are kept as-is.
CREATE VIEW A_BillingDocRequestPartnerS2S AS
SELECT
HeaderPartner.BillingDocumentRequest AS BillingDocumentRequest,
HeaderPartner.PartnerFunction AS PartnerFunction,
HeaderPartner.Customer AS Customer,
HeaderPartner.Supplier AS Supplier,
HeaderPartner.Personnel AS Personnel,
HeaderPartner.ContactPerson AS ContactPerson,
HeaderPartner.ReferenceBusinessPartner AS ReferenceBusinessPartner,
HeaderPartner.BusinessPartnerAddressUUID AS BusinessPartnerAddressUUID
FROM R_BillgDocRequestPartnerTP
;
Learn More
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- OData Services in SAP S/4HANA Explained
- Service Bindings and Service Definitions in SAP S/4HANA
- CDS View Annotations — A Complete Guide
- What Is a CDS View in SAP S/4HANA?
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- CDS View Field Mapping and Associations
- Understanding the SAP S/4HANA Data Model
- CDS View Extensions and Custom Fields in SAP S/4HANA
- Released APIs and Stability Contracts in SAP S/4HANA
- 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
- BW Extractor to CDS View Migration Guide
- S/4HANA CDS View Deprecation: What You Need to Know
- ABAP CDS View Tutorial — From Basics to Real-World Examples
- RAP and CDS Views — Building Transactional Apps in SAP S/4HANA
- Sales Document Status Migration: VBUP/VBUK Removal in S/4HANA
- CO Tables in S/4HANA: COEP, COBK, COSS, COSP to ACDOCA