C_REIntegObjTypeVH
Real Estate Integration Object Type VH
C_REIntegObjTypeVH is a Consumption CDS View that provides data about "Real Estate Integration Object Type VH" in SAP S/4HANA. It reads from 1 data source (I_REIntegObjectType) and exposes 2 fields with key field REIntegrationObjectType. It is exposed through 4 OData services (ASQL_F5397, ASQL_F5592, UI_REOCCUPANCYGROUP, ...). It is used in 2 Fiori applications: Group Real Estate Object for Use, Group Real Estate Object for Occupancy. Part of development package VDM_RE_IP.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| I_REIntegObjectType | I_REIntegObjectType | from |
Annotations (14)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | CREINTOBJTYPVH | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AbapCatalog.preserveKey | true | view | |
| AccessControl.authorizationCheck | #NOT_REQUIRED | view | |
| ObjectModel.dataCategory | #VALUE_HELP | view | |
| ObjectModel.representativeKey | REIntegrationObjectType | view | |
| ObjectModel.usageType.dataClass | #CUSTOMIZING | view | |
| ObjectModel.usageType.serviceQuality | #B | view | |
| ObjectModel.usageType.sizeCategory | #M | view | |
| ObjectModel.resultSet.sizeCategory | #XS | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| AccessControl.personalData.blocking | #NOT_REQUIRED | view | |
| VDM.viewType | #CONSUMPTION | view | |
| EndUserText.label | Real Estate Integration Object Type VH | view |
OData Services (4)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| ASQL_F5397 | ASQL_F5397 | C2 | NOT_RELEASED | |
| ASQL_F5592 | ASQL_F5592 | C2 | NOT_RELEASED | |
| UI_REOCCUPANCYGROUP | UI_REOCCUPANCYGROUP | V2 | C1 | NOT_RELEASED |
| UI_REUSAGEENABLEGROUP | UI_REUSAGEENABLEGROUP | V2 | C1 | NOT_RELEASED |
Fiori Apps (2)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F5397 | Group Real Estate Object for Use | Transactional | The "Group Real Estate Object for Use" Fiori App allows Customers to group their Real Estate Objects (Buildings, Floors, Spaces, Land, Land Areas) for further steps in the Enable Use Process. |
| F5592 | Group Real Estate Object for Occupancy | Transactional | The "Group Real Estate Object for Occupancy" Fiori App allows Customers to group their Real Estate Objects (Buildings, Floors, Spaces, Land, Land Areas) for further steps in the Occupancy Process. |
Group Real Estate Object for Use
Business Role: Real Estate Specialist - Location Management
To support lease-in scenarios, location management must be enabled for use before real estate objects can be assigned to a lease-in contract. Real estate object here, refer to buildings, lands or groups of spaces created within SAP Cloud for Real Estate. When a real estate object is enabled for use, it (single or grouped objects) is synchronized with SAP S/4HANA, and is simultaneously assigned to a company code, a cost object, and usage type. You can optionally assign other attributes (such as fixed assets assigned to the location) to the enabled group. Once enabled for use, objects are available for assignment to a lease-in contract.
Group Real Estate Object for Occupancy
Business Role: Real Estate Specialist - Location Management
Areas that were entered in Location Management of Cloud for Real Estate, can be grouped according to certain aspects for occupancy management. When you group spaces, the spaces are synchronized with SAP S/4HANA and assigned to an object category (external, internal, or intercompany) and a usage type at the same time. After grouping, areas are available for assignment to a rental agreement.
Fields (2)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | REIntegrationObjectType | REIntegrationObjectType | ||
| _Text | _Text |
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_REIntegObjTypeVH.
-- 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: CREINTOBJTYPVH
CREATE VIEW C_REIntegObjTypeVH AS
SELECT
REIntegrationObjectType
FROM I_REIntegObjectType
;
Learn More
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- OData Services in SAP S/4HANA Explained
- Service Bindings and Service Definitions in SAP S/4HANA
- SAP Fiori Apps Architecture — How Fiori Apps Connect to Data
- 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