I_BillingDocumentPartner

DDL: I_BILLINGDOCUMENTPARTNER Type: view COMPOSITE

Billing Document Partner

I_BillingDocumentPartner (Composite)

Package: Explore, extend and adapt the SAP S/4HANA Cloud Private Edition with built-in and side-by-side extension capabilities.

Sales

I_BillingDocumentPartner is a Composite CDS View that provides data about "Billing Document Partner" in SAP S/4HANA. It reads from 1 data source (I_BillingDocumentPartnerBasic) and exposes 17 fields with key fields BillingDocument, PartnerFunction. It has 1 association to related views.

SAP API Hub

StateC1
Line of BusinessSales
Application ComponentSD-BIL
CapabilitiesData Source in SQL Select, Data Source for Defining CDS Entities, Association Target for Defining CDS Entities
PackageSales for SAP S/4HANA Cloud Private Edition
Description <p>This CDS view provides the prerequisites for answering questions about billing document partners at header level. Example business questions could include:</p> <ul> <li><p>What are the partner functions specified in a given billing document?</p></li> <li><p>Who is the customer, supplier, personnel, or contact person of a given billing document?</p></li> <li><p>What is the address of a partner in a given billing document?</p></li> </ul>

Documentation

Data Sources (1)

SourceAliasJoin Type
I_BillingDocumentPartnerBasic Partner from

Associations (1)

CardinalityTargetAliasCondition
[1..1] I_BillingDocument _BillingDocument $projection.BillingDocument = _BillingDocument.BillingDocument

Annotations (13)

NameValueLevelField
ClientHandling.algorithm #SESSION_VARIABLE view
EndUserText.label Billing Document Partner view
AccessControl.authorizationCheck #CHECK view
AccessControl.personalData.blocking #REQUIRED view
AbapCatalog.sqlViewName ISDBILDOCPT view
AbapCatalog.compiler.compareFilter true view
AbapCatalog.preserveKey true view
ObjectModel.representativeKey PartnerFunction view
ObjectModel.usageType.dataClass #TRANSACTIONAL view
ObjectModel.usageType.serviceQuality #B view
ObjectModel.usageType.sizeCategory #XL view
VDM.viewType #COMPOSITE view
Metadata.ignorePropagatedAnnotations true view

Fields (17)

KeyFieldSource TableSource FieldDescription
KEY BillingDocument I_BillingDocumentPartnerBasic BillingDocument Billing Document
KEY PartnerFunction I_BillingDocumentPartnerBasic PartnerFunction Partner Function
Customer I_BillingDocumentPartnerBasic Customer Customer Number
Supplier I_BillingDocumentPartnerBasic Supplier Account Number of Supplier
Personnel I_BillingDocumentPartnerBasic Personnel Personnel Number
AddressID I_BillingDocumentPartnerBasic AddressID Ship-to address
ContactPerson I_BillingDocumentPartnerBasic ContactPerson Number of Contact Person
AddressPersonID I_BillingDocumentPartnerBasic AddressPersonID Person Number
ReferenceBusinessPartner I_BillingDocumentPartnerBasic ReferenceBusinessPartner Business Partner Number
SDDocPartnerAddressRefType I_BillingDocumentPartnerBasic SDDocPartnerAddressRefType Address indicator
BPRefAddressIDForDocSpcfcAddr I_BillingDocumentPartnerBasic BPRefAddressIDForDocSpcfcAddr BP Reference Address Number
_BillingDocument _BillingDocument
_PartnerFunction I_BillingDocumentPartnerBasic _PartnerFunction
_Address I_BillingDocumentPartnerBasic _Address
_BusinessPartnerAddress I_BillingDocumentPartnerBasic _BusinessPartnerAddress
_DfltAddrRprstn I_BillingDocumentPartnerBasic _DfltAddrRprstn
_BPRefAddressForDocSpcfcAddr I_BillingDocumentPartnerBasic _BPRefAddressForDocSpcfcAddr

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 I_BillingDocumentPartner.
-- 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 I_BillingDocumentPartner AS
SELECT
  Partner.BillingDocument AS BillingDocument,
  Partner.PartnerFunction AS PartnerFunction,
  Partner.Customer AS Customer,
  Partner.Supplier AS Supplier,
  Partner.Personnel AS Personnel,
  Partner.AddressID AS AddressID,
  Partner.ContactPerson AS ContactPerson,
  Partner.AddressPersonID AS AddressPersonID,
  Partner.ReferenceBusinessPartner AS ReferenceBusinessPartner,
  Partner.SDDocPartnerAddressRefType AS SDDocPartnerAddressRefType,
  Partner.BPRefAddressIDForDocSpcfcAddr AS BPRefAddressIDForDocSpcfcAddr,
  Partner._PartnerFunction AS _PartnerFunction,
  Partner._Address AS _Address,
  Partner._BusinessPartnerAddress AS _BusinessPartnerAddress,
  Partner._DfltAddrRprstn AS _DfltAddrRprstn,
  Partner._BPRefAddressForDocSpcfcAddr AS _BPRefAddressForDocSpcfcAddr
FROM I_BillingDocumentPartnerBasic AS Partner
LEFT OUTER JOIN I_BillingDocument AS _BillingDocument ON BillingDocument = _BillingDocument.BillingDocument  -- association [1..1]
;