I_PrelimBillingDocPartner
Preliminary Billing Document Partner
I_PrelimBillingDocPartner is a Composite CDS View that provides data about "Preliminary Billing Document Partner" in SAP S/4HANA. It reads from 1 data source (I_BillingDocumentPartnerBasic) and exposes 17 fields with key fields PrelimBillingDocument, PartnerFunction. It has 1 association to related views.
SAP Help Documentation
| Category | Preliminary Billing Documents |
|---|---|
| Status | Released |
Purpose
This CDS view provides the prerequisites for answering questions about preliminary billing document partners at header level. For more information about preliminary billing documents, see Preliminary Billing Documents . Example business questions could include: What are the partner functions specified in a given preliminary billing document? Who is the customer, supplier, personnel, or contact person entered in a given preliminary billing documents? What is the address or phone number of a partner in a given preliminary billing document?
Prerequisites
Authorizations Users who want to use this CDS view must have the following authorization objects assigned: V_VBRK_FKA (Billing: Authorization for Billing Types) V_VBRK_VKO (Billing: Authorization for Sales Organizations)
Structure
Object types This view relates to the following SAP object types: PreliminaryBillingDocument You can use the field PrelimBillingDocument (document number) as a key field. Measures and attributes Some important measures and attributes are: Partner function ( PartnerFunction ) Customer number ( Customer ) Supplier account number ( Supplier ) Personnel number ( Personnel ) Number of contact person ( ContactPerson ) Partner address ( AdressID )
This CDS view provides the prerequisites for answering questions about preliminary billing document partners at header level. For more information about preliminary billing documents, see Preliminary Billing Documents . Example business questions could include: What are the partner functions specified in a given preliminary billing document? Who is the customer, supplier, personnel, or contact person entered in a given preliminary billing documents? What is the address or phone number of a partner in a given preliminary billing document?
Prerequisites
Authorizations Users who want to use this CDS view must have the following authorization objects assigned: V_VBRK_FKA (Billing: Authorization for Billing Types) V_VBRK_VKO (Billing: Authorization for Sales Organizations)
Structure
Object types This view relates to the following SAP object types: PreliminaryBillingDocument You can use the field PrelimBillingDocument (document number) as a key field. Measures and attributes Some important measures and attributes are: Partner function ( PartnerFunction ) Customer number ( Customer ) Supplier account number ( Supplier ) Personnel number ( Personnel ) Number of contact person ( ContactPerson ) Partner address ( AdressID )
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| I_BillingDocumentPartnerBasic | Partner | from |
Associations (1)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [1..1] | I_PrelimBillingDocument | _PrelimBillingDocument | $projection.PrelimBillingDocument = _PrelimBillingDocument.PrelimBillingDocument |
Annotations (12)
| Name | Value | Level | Field |
|---|---|---|---|
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| EndUserText.label | Preliminary Billing Document Partner | view | |
| AccessControl.authorizationCheck | #CHECK | view | |
| AbapCatalog.sqlViewName | ISDPREBILDOCPT | 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)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | PrelimBillingDocument | |||
| KEY | PartnerFunction | |||
| Customer | I_BillingDocumentPartnerBasic | Customer | Sold-to Party | |
| Supplier | I_BillingDocumentPartnerBasic | Supplier | Supplier | |
| Personnel | I_BillingDocumentPartnerBasic | Personnel | Personnel No. | |
| ContactPerson | I_BillingDocumentPartnerBasic | ContactPerson | Contact Person Key | |
| ReferenceBusinessPartner | I_BillingDocumentPartnerBasic | ReferenceBusinessPartner | Busn. Partner | |
| AddressID | I_BillingDocumentPartnerBasic | AddressID | Ship-to address | |
| AddressPersonID | I_BillingDocumentPartnerBasic | AddressPersonID | Person Number | |
| AddressObjectType | I_BillingDocumentPartnerBasic | AddressObjectType | Address Type | |
| SDDocPartnerAddressRefType | I_BillingDocumentPartnerBasic | SDDocPartnerAddressRefType | Adress ind. | |
| VATRegistration | I_BillingDocumentPartnerBasic | VATRegistration | VAT Registration No. | |
| UnloadingPointName | I_BillingDocumentPartnerBasic | UnloadingPointName | Unloading Point Name | |
| _PrelimBillingDocument | _PrelimBillingDocument | |||
| _PartnerFunction | I_BillingDocumentPartnerBasic | _PartnerFunction | ||
| _Address | I_BillingDocumentPartnerBasic | _Address | ||
| _DfltAddrRprstn | I_BillingDocumentPartnerBasic | _DfltAddrRprstn |
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_PrelimBillingDocPartner.
-- 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_PrelimBillingDocPartner AS
SELECT
cast( Partner.BillingDocument as prelim_billing_document preserving type ) AS PrelimBillingDocument,
cast(Partner.PartnerFunction as parvw_unv preserving type ) AS PartnerFunction,
Partner.Customer AS Customer,
Partner.Supplier AS Supplier,
Partner.Personnel AS Personnel,
Partner.ContactPerson AS ContactPerson,
Partner.ReferenceBusinessPartner AS ReferenceBusinessPartner,
Partner.AddressID AS AddressID,
Partner.AddressPersonID AS AddressPersonID,
Partner.AddressObjectType AS AddressObjectType,
Partner.SDDocPartnerAddressRefType AS SDDocPartnerAddressRefType,
Partner.VATRegistration AS VATRegistration,
Partner.UnloadingPointName AS UnloadingPointName,
Partner._PartnerFunction AS _PartnerFunction,
Partner._Address AS _Address,
Partner._DfltAddrRprstn AS _DfltAddrRprstn
FROM I_BillingDocumentPartnerBasic AS Partner
LEFT OUTER JOIN I_PrelimBillingDocument AS _PrelimBillingDocument ON PrelimBillingDocument = _PrelimBillingDocument.PrelimBillingDocument -- association [1..1]
;
Learn More
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- 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