C_BPContactEmlAddr

DDL: C_BPCONTACTEMLADDR SQL: CBPCPEMLADR Type: view CONSUMPTION Package: VDM_MD_BP
21 Fields 1 Data Sources 4 Associations

C View for BP Contact Email Address

C_BPContactEmlAddr is a Consumption CDS View that provides data about "C View for BP Contact Email Address" in SAP S/4HANA. It reads from 1 data source (I_BPContactEmlAddrTP) and exposes 21 fields with key fields BusinessPartner1, BusinessPartner2, RelationshipNumber, ValidityEndDate, AddressID. It has 4 associations to related views. Part of development package VDM_MD_BP.

Data Sources (1)

SourceAliasJoin Type
I_BPContactEmlAddrTP EmailAddress from

Associations (4)

CardinalityTargetAliasCondition
[1..1] C_BusinessPartner _BusinessPartner $projection.BusinessPartner1 = _BusinessPartner.BusinessPartner
[1..1] C_BusinessPartnerCustomer _BusinessPartnerCustomer $projection.BusinessPartner1 = _BusinessPartnerCustomer.BusinessPartner
[1..1] C_BusinessPartnerSupplier _BusinessPartnerSupplier $projection.BusinessPartner1 = _BusinessPartnerSupplier.BusinessPartner
[1..1] C_BPContactAddress _BPContactAddress $projection.BusinessPartner1 = _BPContactAddress.BusinessPartner1 and $projection.BusinessPartner2 = _BPContactAddress.BusinessPartner2 and $projection.RelationshipNumber = _BPContactAddress.RelationshipNumber and $projection.ValidityEndDate = _BPContactAddress.ValidityEndDate and $projection.AddressID = _BPContactAddress.AddressID

Annotations (13)

NameValueLevelField
AbapCatalog.sqlViewName CBPCPEMLADR view
AbapCatalog.compiler.compareFilter true view
AbapCatalog.preserveKey true view
AccessControl.authorizationCheck #CHECK view
EndUserText.label C View for BP Contact Email Address view
AccessControl.personalData.blocking #REQUIRED view
ClientHandling.algorithm #SESSION_VARIABLE view
Metadata.allowExtensions true view
ObjectModel.usageType.serviceQuality #D view
ObjectModel.usageType.sizeCategory #XXL view
ObjectModel.usageType.dataClass #MASTER view
Search.searchable true view
VDM.viewType #CONSUMPTION view

Fields (21)

KeyFieldSource TableSource FieldDescription
KEY BusinessPartner1 I_BPContactEmlAddrTP BusinessPartner1 Partner
KEY BusinessPartner2 I_BPContactEmlAddrTP BusinessPartner2 Partner
KEY RelationshipNumber I_BPContactEmlAddrTP RelationshipNumber BP Rel. Number
KEY ValidityEndDate I_BPContactEmlAddrTP ValidityEndDate ValidTo
KEY AddressID I_BPContactEmlAddrTP AddressID Ship-to address
KEY OrdinalNumber I_BPContactEmlAddrTP OrdinalNumber Sequence Number
BusinessPartner1ForEdit I_BPContactEmlAddrTP BusinessPartner1ForEdit Busn. Partner
BusinessPartner2ForEdit I_BPContactEmlAddrTP BusinessPartner2ForEdit Busn. Partner
ValidityEndDateForEdit I_BPContactEmlAddrTP ValidityEndDateForEdit Valid To
AddressIDForEdit I_BPContactEmlAddrTP AddressIDForEdit Address Number
OrdinalNumberForEdit I_BPContactEmlAddrTP OrdinalNumberForEdit Sequence Number
RelationshipNumberForEdit I_BPContactEmlAddrTP RelationshipNumberForEdit BP Rel. Number
EmailAddress I_BPContactEmlAddrTP EmailAddress E-Mail Address
IsDefaultEmailAddress I_BPContactEmlAddrTP IsDefaultEmailAddress Standard addr.
CommNumberIsNotUsed I_BPContactEmlAddrTP CommNumberIsNotUsed Do not use
IsHomeEmailAddress I_BPContactEmlAddrTP IsHomeEmailAddress Home Address
AddressCommunicationRemarkText I_BPContactEmlAddrTP AddressCommunicationRemarkText Notes
_BusinessPartner _BusinessPartner
_BusinessPartnerCustomer _BusinessPartnerCustomer
_BusinessPartnerSupplier _BusinessPartnerSupplier
_BPContactAddress _BPContactAddress

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 C_BPContactEmlAddr.
-- 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.
-- SQL view name: CBPCPEMLADR

CREATE VIEW C_BPContactEmlAddr AS
SELECT
  EmailAddress.BusinessPartner1 AS BusinessPartner1,
  EmailAddress.BusinessPartner2 AS BusinessPartner2,
  EmailAddress.RelationshipNumber AS RelationshipNumber,
  EmailAddress.ValidityEndDate AS ValidityEndDate,
  EmailAddress.AddressID AS AddressID,
  EmailAddress.OrdinalNumber AS OrdinalNumber,
  EmailAddress.BusinessPartner1ForEdit AS BusinessPartner1ForEdit,
  EmailAddress.BusinessPartner2ForEdit AS BusinessPartner2ForEdit,
  EmailAddress.ValidityEndDateForEdit AS ValidityEndDateForEdit,
  EmailAddress.AddressIDForEdit AS AddressIDForEdit,
  EmailAddress.OrdinalNumberForEdit AS OrdinalNumberForEdit,
  EmailAddress.RelationshipNumberForEdit AS RelationshipNumberForEdit,
  EmailAddress.EmailAddress AS EmailAddress,
  EmailAddress.IsDefaultEmailAddress AS IsDefaultEmailAddress,
  EmailAddress.CommNumberIsNotUsed AS CommNumberIsNotUsed,
  EmailAddress.IsHomeEmailAddress AS IsHomeEmailAddress,
  EmailAddress.AddressCommunicationRemarkText AS AddressCommunicationRemarkText
FROM I_BPContactEmlAddrTP AS EmailAddress
LEFT OUTER JOIN C_BusinessPartner AS _BusinessPartner ON BusinessPartner1 = _BusinessPartner.BusinessPartner  -- association [1..1]
LEFT OUTER JOIN C_BusinessPartnerCustomer AS _BusinessPartnerCustomer ON BusinessPartner1 = _BusinessPartnerCustomer.BusinessPartner  -- association [1..1]
LEFT OUTER JOIN C_BusinessPartnerSupplier AS _BusinessPartnerSupplier ON BusinessPartner1 = _BusinessPartnerSupplier.BusinessPartner  -- association [1..1]
LEFT OUTER JOIN C_BPContactAddress AS _BPContactAddress ON BusinessPartner1 = _BPContactAddress.BusinessPartner1 AND BusinessPartner2 = _BPContactAddress.BusinessPartner2 AND RelationshipNumber = _BPContactAddress.RelationshipNumber AND ValidityEndDate = _BPContactAddress.ValidityEndDate AND AddressID = _BPContactAddress.AddressID  -- association [1..1]
;

Learn More