I_APIsWithCloudDevSuccessor
APIs with Cloud Development Successors
I_APIsWithCloudDevSuccessor is a CDS View that provides data about "APIs with Cloud Development Successors" in SAP S/4HANA. It reads from 4 data sources (ARS_RUNTIME_API_STATE, ars_w_api_state, ars_w_api_state, ARS_API_SUCCESSORS_FOR_C1_SCP) and exposes 23 fields with key fields PredecessorObjectType, PredecessorObjectName, PredecessorObjectDirectoryType, PredecessorObjectDirectoryName, SuccessorObjectType. It has 1 association to related views.
Data Sources (4)
| Source | Alias | Join Type |
|---|---|---|
| ARS_RUNTIME_API_STATE | cloud_dev_successor | inner |
| ars_w_api_state | predecessor | from |
| ars_w_api_state | predecessor | union |
| ARS_API_SUCCESSORS_FOR_C1_SCP | successor | inner |
Associations (1)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..1] | v_ars_release_state | _text | _text.state = predecessor.release_state |
Annotations (3)
| Name | Value | Level | Field |
|---|---|---|---|
| AccessControl.authorizationCheck | #NOT_ALLOWED | view | |
| Metadata.ignorePropagatedAnnotations | true | view | |
| EndUserText.label | APIs with Cloud Development Successors | view |
Fields (23)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | PredecessorObjectType | ars_w_api_state | sub_object_type | Subobject Type |
| KEY | PredecessorObjectName | ars_w_api_state | sub_object_name | Subobject Name |
| KEY | PredecessorObjectDirectoryType | ars_w_api_state | object_type | Type |
| KEY | PredecessorObjectDirectoryName | ars_w_api_state | object_name | Technical Name |
| KEY | SuccessorObjectType | ARS_API_SUCCESSORS_FOR_C1_SCP | successor_object_type | Type |
| KEY | SuccessorObjectName | ARS_API_SUCCESSORS_FOR_C1_SCP | successor_object_key | Subobject Name |
| KEY | SuccessorObjectDirectoryType | ARS_API_SUCCESSORS_FOR_C1_SCP | successor_tadir_object | Object Type |
| KEY | SuccessorObjectDirectoryName | ARS_API_SUCCESSORS_FOR_C1_SCP | successor_tadir_obj_name | Object Name |
| SuccessorConceptName | ars_w_api_state | successor_concept_name | Successor Concept | |
| SuccessorCategory | ||||
| PredecessorReleaseState | ars_w_api_state | release_state | Release Status | |
| sub_object_typeasPredecessorObjectType | ||||
| KEY | PredecessorObjectName | ars_w_api_state | sub_object_name | Subobject Name |
| KEY | PredecessorObjectDirectoryType | ars_w_api_state | object_type | Type |
| KEY | PredecessorObjectDirectoryName | ars_w_api_state | object_name | Technical Name |
| KEY | SuccessorObjectType | Type | ||
| KEY | SuccessorObjectName | Subobject Name | ||
| KEY | SuccessorObjectDirectoryType | Object Type | ||
| KEY | SuccessorObjectDirectoryName | Object Name | ||
| SuccessorConceptName | ars_w_api_state | successor_concept_name | Successor Concept | |
| SuccessorCategory | ||||
| PredecessorReleaseState | ars_w_api_state | release_state | Release Status | |
| PredecessorReleaseStateDescr | _text | description | Well Code Des. |
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_APIsWithCloudDevSuccessor.
-- 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 I_APIsWithCloudDevSuccessor AS
SELECT
predecessor.sub_object_type AS PredecessorObjectType,
predecessor.sub_object_name AS PredecessorObjectName,
predecessor.object_type AS PredecessorObjectDirectoryType,
predecessor.object_name AS PredecessorObjectDirectoryName,
successor.successor_object_type AS SuccessorObjectType,
successor.successor_object_key AS SuccessorObjectName,
successor.successor_tadir_object AS SuccessorObjectDirectoryType,
successor.successor_tadir_obj_name AS SuccessorObjectDirectoryName,
predecessor.successor_concept_name AS SuccessorConceptName,
cast('O' as ars_successor_category preserving type) AS SuccessorCategory,
predecessor.release_state AS PredecessorReleaseState,
_text.description as PredecessorReleaseStateDescr AS sub_object_typeasPredecessorObjectType,
_text.description AS PredecessorReleaseStateDescr
FROM ars_w_api_state AS predecessor
INNER JOIN ARS_API_SUCCESSORS_FOR_C1_SCP AS successor ON /* join condition not captured in parsed metadata */
INNER JOIN ARS_RUNTIME_API_STATE AS cloud_dev_successor ON /* join condition not captured in parsed metadata */
LEFT OUTER JOIN v_ars_release_state AS _text ON _text.state = predecessor.release_state -- association [0..1]
-- UNION with additional select branch(es): ars_w_api_state
;
Learn More
- CDS View Annotations — A Complete Guide
- 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 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