C_EquipFunctionalLocDataVH

DDL: C_EQUIPFUNCTIONALLOCDATAVH Type: view_entity CONSUMPTION

Equip with Functional Location Data

C_EquipFunctionalLocDataVH is a Consumption CDS View that provides data about "Equip with Functional Location Data" in SAP S/4HANA. It reads from 1 data source (I_EquipmentValidTimeSegment) and exposes 14 fields with key fields Equipment, ValidityEndDate, EquipUsagePeriodSequenceNumber.

Data Sources (1)

SourceAliasJoin Type
I_EquipmentValidTimeSegment _EquipmentTimeSeg from

Annotations (13)

NameValueLevelField
AccessControl.authorizationCheck #MANDATORY view
AccessControl.personalData.blocking #REQUIRED view
EndUserText.label Equip with Functional Location Data view
Metadata.ignorePropagatedAnnotations true view
ObjectModel.usageType.serviceQuality #C view
ObjectModel.usageType.sizeCategory #XL view
ObjectModel.usageType.dataClass #MIXED view
ObjectModel.dataCategory #VALUE_HELP view
ObjectModel.representativeKey Equipment view
Search.searchable true view
Consumption.ranked true view
VDM.viewType #CONSUMPTION view
Metadata.allowExtensions true view

Fields (14)

KeyFieldSource TableSource FieldDescription
KEY Equipment Equipment Equipment check
KEY ValidityEndDate ValidityEndDate ValidTo
KEY EquipUsagePeriodSequenceNumber EquipUsagePeriodSequenceNumber
EquipmentName
FunctionalLocation
FunctionalLocationLabelName
FunctionalLocationName
TechnicalObjectSortCode TechnicalObjectSortCode
CalendarDate ValidOnDate
MaintenancePlant
MaintenancePlanningPlant MaintenancePlanningPlant Planning Plant
MaintenancePlannerGroup MaintenancePlannerGroup Planner Group
WorkCenterInternalID WorkCenterInternalID Work Center
CatalogProfile CatalogProfile Catalog Profile

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_EquipFunctionalLocDataVH.
-- 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 C_EquipFunctionalLocDataVH AS
SELECT
  Equipment,
  ValidityEndDate,
  EquipUsagePeriodSequenceNumber,
  _Equipment._EquipmentText[1:Language=$session.system_language].EquipmentName AS EquipmentName,
  cast(_EquipmentTimeSeg._LocationAccountAssignment.FunctionalLocation as eams_ui_oid_name preserving type ) AS FunctionalLocation,
  cast(_EquipmentTimeSeg._LocationAccountAssignment._FunctionalLocation._FunctionalLocationLabel.FunctionalLocationLabelName as eams_tec_obj) AS FunctionalLocationLabelName,
  _EquipmentTimeSeg._LocationAccountAssignment._FunctionalLocation._FunctionalLocationText[1:Language=$session.system_language].FunctionalLocationName AS FunctionalLocationName,
  TechnicalObjectSortCode,
  ValidOnDate AS CalendarDate,
  cast(_EquipmentTimeSeg._LocationAccountAssignment.MaintenancePlant as swerk) AS MaintenancePlant,
  MaintenancePlanningPlant,
  MaintenancePlannerGroup,
  WorkCenterInternalID,
  CatalogProfile
FROM I_EquipmentValidTimeSegment AS _EquipmentTimeSeg
;