C_MyEHSLocationExpanded
My EHS Location and Sublocations
C_MyEHSLocationExpanded is a Consumption CDS View that provides data about "My EHS Location and Sublocations" in SAP S/4HANA. It reads from 1 data source (I_MyEHSLocationExpanded) and exposes 15 fields with key field EHSLocationUUID. It is used in 1 Fiori application: Workplace Safety Overview. Part of development package EHFND_CNS_LOCATION.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| I_MyEHSLocationExpanded | I_MyEHSLocationExpanded | from |
Annotations (10)
| Name | Value | Level | Field |
|---|---|---|---|
| EndUserText.label | My EHS Location and Sublocations | view | |
| OData.publish | true | view | |
| VDM.viewType | #CONSUMPTION | view | |
| AccessControl.authorizationCheck | #MANDATORY | view | |
| AbapCatalog.sqlViewName | CMYLOCEXPANDED | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| ObjectModel.usageType.serviceQuality | #C | view | |
| ObjectModel.usageType.sizeCategory | #L | view | |
| ObjectModel.usageType.dataClass | #MASTER | view |
Fiori Apps (1)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F7512 | Workplace Safety Overview | Analytical | An application which provides overview for the Workplace Safety state of the organization: Safety Incidents, Related tasks and various analytical data points. |
Workplace Safety Overview
Business Role: Industrial Hygienist
New Workplace Safety Overview application which provides Cards with data insights regarding Incident Management. All Cards are based on the My Location concept and use the currently set My Location ID for the logged in user to pre-filter all data. If no location is set, then by default the Cards will show all data in the organization.Certain cards which have IBN are able to be assigned on the Fiori Launchpad Home Page.
Fields (15)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | EHSLocationUUID | _EHSLocationRevision | EHSLocationUUID | |
| MyEHSLocationUUID | MyEHSLocationUUID | |||
| RevisionStartDate | _EHSLocationRevision | RevisionStartDate | ||
| RevisionEndDate | _EHSLocationRevision | RevisionEndDate | ||
| EHSLocationHierarchyLevel | EHSLocationHierarchyLevel | |||
| EHSLocationID | ||||
| EHSLocationRevisionUUID | _EHSLocationRevision | EHSLocationRevisionUUID | ||
| EHSLocationType | _EHSLocationRevision | EHSLocationType | ||
| EHSLocationStatus | _EHSLocationRevision | EHSLocationStatus | ||
| EHSLocationAuthorizationGroup | _EHSLocationRevision | EHSLocationAuthorizationGroup | ||
| Plant | _EHSLocationRevision | Plant | ||
| CostCenter | _EHSLocationRevision | CostCenter | ||
| CompanyCode | _EHSLocationRevision | CompanyCode | ||
| BusinessArea | _EHSLocationRevision | BusinessArea | ||
| _Name | _EHSLocationRevision | _EHSLocationRevisionName |
@EndUserText.label: 'My EHS Location and Sublocations'
@OData.publish: true
@VDM.viewType: #CONSUMPTION
@AccessControl.authorizationCheck: #MANDATORY
@AbapCatalog.sqlViewName: 'CMYLOCEXPANDED'
@AbapCatalog.compiler.compareFilter: true
@ClientHandling.algorithm: #SESSION_VARIABLE
@ObjectModel.usageType: {serviceQuality: #C, sizeCategory: #L, dataClass: #MASTER}
define view C_MyEHSLocationExpanded
as select from I_MyEHSLocationExpanded
{
// To be able to resolve the association to the location name it is necessary to have the field
// _EHSLocationRevision.EHSLocationUUID in this view, even though this is the same UUID as
// the EHSLocationUUID from view I_MyEHSLocationExpanded. To avoid having two fields with the
// same value here we use _EHSLocationRevision.EHSLocationUUID as key field instead of
// I_MyEHSLocationExpanded.EHSLocationUUID
@UI.hidden: true
key _EHSLocationRevision.EHSLocationUUID as EHSLocationUUID,
MyEHSLocationUUID,
// Only needed for technical reasons
@Consumption.hidden: true
_EHSLocationRevision.RevisionStartDate,
// Only needed for technical reasons
@Consumption.hidden: true
_EHSLocationRevision.RevisionEndDate,
EHSLocationHierarchyLevel,
@ObjectModel.text.association: '_Name'
_EHSLocationRevision._EHSLocationRoot.EHSLocationID,
_EHSLocationRevision.EHSLocationRevisionUUID,
_EHSLocationRevision.EHSLocationType,
_EHSLocationRevision.EHSLocationStatus,
_EHSLocationRevision.EHSLocationAuthorizationGroup,
_EHSLocationRevision.Plant,
_EHSLocationRevision.CostCenter,
_EHSLocationRevision.CompanyCode,
_EHSLocationRevision.BusinessArea,
_EHSLocationRevision._EHSLocationRevisionName as _Name
}
Learn More
- What Is a CDS View in SAP S/4HANA?
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- CDS View Annotations — A Complete Guide
- 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