What is I_BPAddressIndependentMobile in SAP S/4HANA?

I_BPAddressIndependentMobile is a basic CDS view in SAP S/4HANA. Root view for AddrIndMob It contains 20 fields.

Which tables does I_BPAddressIndependentMobile read from?

I_BPAddressIndependentMobile reads data from: I_AddressPhoneNumber_2.

What VDM layer is I_BPAddressIndependentMobile?

I_BPAddressIndependentMobile is classified as a Basic (interface) view providing a 1:1 representation of a database table.

I_BPAddressIndependentMobile

DDL: I_BPADDRESSINDEPENDENTMOBILE SQL: IBPADDRINDMOB Type: view BASIC Package: VDM_MD_BP_BASE

20 Fields 1 Data Sources 1 Associations

Root view for AddrIndMob

I_BPAddressIndependentMobile (Basic)

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

Database & Data Management

I_BPAddressIndependentMobile is a Basic CDS View that provides data about "Root view for AddrIndMob" in SAP S/4HANA. It reads from 1 data source (I_AddressPhoneNumber_2) and exposes 20 fields with key fields BusinessPartner, AddressID, Person, OrdinalNumber. It has 1 association to related views. Part of development package VDM_MD_BP_BASE.

SAP Help Documentation

Category	CDS Views for Business Partner

Purpose
This CDS view provides access to mobile phone number information for BP addresses-independent communication. It retrieves mobile phone contact details including phone numbers, country codes, extensions, validity periods, and related attributes such as SMS enablement and default phone number indicators. This CDS view provides the data to answer the following business questions: What are the mobile numbers independent of BP address maintained for communication? Which mobile number is set as the default contact number for a business partner? What is the validity period for each mobile number in the system? Which mobile numbers are enabled for SMS communication? What are the complete mobile numbers including country codes and extensions? What notes or remarks are associated with specific mobile communication records? To help you decide which CDS view to use for your purposes, SAP has introduced the annotation ObjectModel.supportedCapabilities that indicates the most appropriate use cases for each CDS view. To find out what use cases are best supported by this CDS view, access the entry of the CDS view in the View Browser app and find the values for this annotation under the Annotation tab. For more information, see Supported Capabilities for CDS Views .

Prerequisites
Authorizations Users who want to use this CDS view must have a role with the following restriction types set to read access: RESTRICTION_TYPE_ID RESTRICTION_TYPE B_BUP_DCPD Business Partner Processing BEGRU_BUPA_GRP Authorization Group for Business Partners

Structure
Important Fields Important fields in this view include the following: Field Name Description PHONENUMBEREXTENSION Extension number MOBILEPHONENUMBER Unique numerical identifier that is associated with a mobile device for calling purposes. MOBILEPHONECOUNTRY Country where the mobile phone number is located. ISDEFAULTPHONENUMBER Identifies the default mobile phone number PHONEISSMSENABLED Identifies if contacting the mobile phone number via SMS is enabled or not. VALIDITYSTARTDATETIME Time on a specific date from when the mobile phone number is valid in the system. VALIDITYENDDATETIME Time on a specific date until when the mobile phone number is valid in the system. ADDRESSCOMMUNICATIONREMARKTEXT Additional information about the mobile phone number VALIDITYSTARTDATE Date from when the mobile phone number is valid in the system. VALIDITYENDDATE Date until when the mobile phone number is valid in the system. ORDINALNUMBER The number which identifies a specific mobile phone number, if there are more than one mobile phone numbers.

Data Extraction
Data Extraction Type This CDS view is not enabled for data extraction.

View on SAP Help Portal →

SAP API Hub

Category	Basic
State	C1
Line of Business	Database & Data Management
Application Component	AP-MD-BP
Extensible (Key User)	No
Extensible (Developer)	No
Release State (Key User)	Released
Release State (Developer)	Released
Package	Database and Data Management for SAP S/4HANA Cloud Public Edition

Documentation

Analytics with CDS Views — Build Analytics for S/4HANA Cloud Public Edition ABAP CDS views replicated to SAP Cloud Platform
CDS Views on SAP Business Accelerator Hub — Explore SAP S/4HANA Cloud Public Edition CDS Views on SAP Business Accelerator Hub
Create CDS View as API — Create CDS views in SAP S/4HANA Cloud Public Edition and consume them as APIs
Custom CDS Views — Access data using a Custom Core Data Service view (Custom CDS view)
Custom Communication Scenarios — Create custom communication scenarios to configure custom communication arrangement
Key User Extensibility Tools — The Key User Extensibility Tools of S/4HANA
SAP S/4HANA Extensibility — SAP S/4HANA Extensibility Tutorial
VDM View Types — The Virtual Data Model in SAP S/4HANA Cloud Public Edition
View Browser — Search, browse and tag CDS Views

Data Sources (1)

Source	Alias	Join Type
I_AddressPhoneNumber_2	BPAddressIndependentMobile	from

Associations (1)

Cardinality	Target	Alias	Condition
[1..1]	I_BusinessPartner	_BusinessPartner	`$projection.AddressID = _BusinessPartner.IndependentAddressID`

Annotations (13)

Name	Value	Level
AbapCatalog.sqlViewName	IBPADDRINDMOB	view
AbapCatalog.compiler.compareFilter	true	view
AbapCatalog.preserveKey	true	view
AccessControl.authorizationCheck	#CHECK	view
AccessControl.personalData.blocking	#REQUIRED	view
EndUserText.label	Root view for AddrIndMob	view
VDM.viewType	#BASIC	view
ObjectModel.representativeKey	AddressID	view
ObjectModel.usageType.serviceQuality	#C	view
ObjectModel.usageType.sizeCategory	#XXL	view
ObjectModel.usageType.dataClass	#MASTER	view
ClientHandling.algorithm	#SESSION_VARIABLE	view
Metadata.allowExtensions	true	view

Fields (20)

Key	Field	Source Table	Source Field	Description
KEY	BusinessPartner	_BusinessPartner	BusinessPartner	Business Partner Number
KEY	AddressID	I_AddressPhoneNumber_2	AddressID	Ship-to address
KEY	Person	I_AddressPhoneNumber_2	AddressPersonID	Person Number
KEY	OrdinalNumber	I_AddressPhoneNumber_2	CommMediumSequenceNumber	Sequence Number
	OrdinalNumberForEdit	I_AddressPhoneNumber_2	CommMediumSequenceNumber	Sequence Number
	AddressIDForEdit	I_AddressPhoneNumber_2	AddressID	Ship-to address
	MobilePhoneCountry	I_AddressPhoneNumber_2	PhoneNumberCountry	Country/Region for Telephone/Fax Number
	CommNumberIsNotUsed			Flag: This Communication Number is Not Used
	MobilePhoneNumber	I_AddressPhoneNumber_2	PhoneAreaCodeSubscriberNumber	Telephone No.: Dialing Code and Number
	PhoneNumberExtension	I_AddressPhoneNumber_2	PhoneExtensionNumber	Telephone no.: Extension
	CompleteTelephoneNumber	I_AddressPhoneNumber_2	InternationalPhoneNumber	Complete Number: Dialing Code+Number+Extension
	PhoneIsSMSEnabled			Indicator: Telephone is SMS-Enabled
	PhoneNumberType	I_AddressPhoneNumber_2	PhoneNumberType	Phone number type
	ValidityStartDateTime			Communication Data: Valid From (YYYYMMDDHHMMSS)
	ValidityEndDateTime			Communication Data: Valid To (YYYYMMDDHHMMSS)
	ValidityStartDate	I_AddressPhoneNumber_2	ValidityStartDate	Validity Start Date
	ValidityEndDate	I_AddressPhoneNumber_2	ValidityEndDate	ValidTo
	_BusinessPartner		_BusinessPartner
	AuthorizationGroup	_BusinessPartner	AuthorizationGroup	Authorization Group
	AddressCommunicationRemarkText	_AddressCommunicationRemark	CommunicationRemarkText	Communication link notes

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_BPAddressIndependentMobile.
-- 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: IBPADDRINDMOB

CREATE VIEW I_BPAddressIndependentMobile AS
SELECT
  _BusinessPartner.BusinessPartner AS BusinessPartner,
  BPAddressIndependentMobile.AddressID AS AddressID,
  BPAddressIndependentMobile.AddressPersonID AS Person,
  BPAddressIndependentMobile.CommMediumSequenceNumber AS OrdinalNumber,
  BPAddressIndependentMobile.CommMediumSequenceNumber AS OrdinalNumberForEdit,
  BPAddressIndependentMobile.AddressID AS AddressIDForEdit,
  BPAddressIndependentMobile.PhoneNumberCountry AS MobilePhoneCountry,
  cast ( '' as ad_flnouse ) AS CommNumberIsNotUsed,
  BPAddressIndependentMobile.PhoneAreaCodeSubscriberNumber AS MobilePhoneNumber,
  BPAddressIndependentMobile.PhoneExtensionNumber AS PhoneNumberExtension,
  BPAddressIndependentMobile.InternationalPhoneNumber AS CompleteTelephoneNumber,
  cast ('' as ad_flgsms) AS PhoneIsSMSEnabled,
  BPAddressIndependentMobile.PhoneNumberType AS PhoneNumberType,
  cast ( BPAddressIndependentMobile.ValidityStartDate as ad_valfrom ) AS ValidityStartDateTime,
  cast ( BPAddressIndependentMobile.ValidityEndDate as ad_valto ) AS ValidityEndDateTime,
  BPAddressIndependentMobile.ValidityStartDate AS ValidityStartDate,
  BPAddressIndependentMobile.ValidityEndDate AS ValidityEndDate,
  _BusinessPartner.AuthorizationGroup AS AuthorizationGroup,
  _AddressCommunicationRemark.CommunicationRemarkText AS AddressCommunicationRemarkText
FROM I_AddressPhoneNumber_2 AS BPAddressIndependentMobile
LEFT OUTER JOIN I_BusinessPartner AS _BusinessPartner ON AddressID = _BusinessPartner.IndependentAddressID  -- association [1..1]
;

Depth:

I_BPAddressIndependentMobile view

I_AddressPhoneNumber_2 view_entity

A_BPAddressIndependentMobile view
I_BPAddressIndependentMobileTP view
I_BPAddrIndependentMobileTP_2 view_entity