ARS_API_STATE

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_API_STATE.
-- 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 ARS_API_STATE AS
SELECT
  api.object_type AS tadir_object,
  api.sub_object_type AS object_type,
  api.sub_object_name AS object_key,
  api.release_state AS state
FROM ARS_RUNTIME_API_STATE AS api
LEFT OUTER JOIN v_ars_release_state AS _state_text ON _state_text.state = state  -- association [0..1]
LEFT OUTER JOIN ARS_API_SUCCESSOR AS _successor ON _successor.tadir_object = tadir_object AND _successor.tadir_obj_name = tadir_obj_name AND _successor.object_type = object_type AND _successor.object_key = object_key AND _successor.compatibility_contract = compatibility_contract  -- association [0..*]
LEFT OUTER JOIN ARS_API_CATALOG_ASSIGNMENT AS _api_catalog_assignment ON _api_catalog_assignment.tadir_object = tadir_object AND _api_catalog_assignment.tadir_obj_name = tadir_obj_name AND _api_catalog_assignment.object_type = object_type AND _api_catalog_assignment.object_key = object_key  -- association [0..*]
;