ARS_V_API_VERSION_APIS
API Release: API Objects + Contracts
ARS_V_API_VERSION_APIS is a CDS View that provides data about "API Release: API Objects + Contracts" in SAP S/4HANA. It reads from 7 data sources and exposes 9 fields with key fields object_type, object_name, object_name, object_name, object_name. Part of development package S_ARS_API_VERSIONS.
Data Sources (7)
| Source | Alias | Join Type |
|---|---|---|
| ars_w_api_state | api | inner |
| ars_w_api_state | api | left_outer |
| ARS_V_EXTENSION_OBJECTS | extension_object | union |
| ARS_V_CUSTOM_EXTENSION_OBJECTS | extension_object | union |
| I_Cfd_Registry_Objects | registry | from |
| I_Cfd_Registry_Objects | registry | union |
| scr_sw_comp_relations | scr_sw_comp_relations | union |
Annotations (5)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | ARS_V_APIV_APIS | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AbapCatalog.preserveKey | true | view | |
| AccessControl.authorizationCheck | #NOT_ALLOWED | view | |
| EndUserText.label | API Release: API Objects + Contracts | view |
Fields (9)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | object_type | ars_w_api_state | object_type | Type |
| KEY | object_name | ars_w_api_state | object_name | Technical Name |
| KEY | object_name | I_Cfd_Registry_Objects | tadir_obj_name | Technical Name |
| object_type | Type | |||
| KEY | object_name | ARS_V_CUSTOM_EXTENSION_OBJECTS | object_name | Technical Name |
| object_type | Type | |||
| KEY | object_name | ARS_V_CUSTOM_EXTENSION_OBJECTS | object_name | Technical Name |
| KEY | object_name | object_name | Technical Name | |
| is_extension |
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 ARS_V_API_VERSION_APIS.
-- 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: ARS_V_APIV_APIS
CREATE VIEW ARS_V_API_VERSION_APIS AS
SELECT
api.object_type AS object_type,
api.object_name AS object_name,
cast(' ' as abap_boolean) AS is_extension
FROM I_Cfd_Registry_Objects AS registry
INNER JOIN ars_w_api_state AS api ON /* join condition not captured in parsed metadata */
LEFT OUTER JOIN ars_w_api_state AS api ON /* join condition not captured in parsed metadata */
-- UNION with additional select branch(es): I_Cfd_Registry_Objects, ARS_V_EXTENSION_OBJECTS, ARS_V_CUSTOM_EXTENSION_OBJECTS, scr_sw_comp_relations
;
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