sycm_aps_c_scp_by_ep_e

DDL: SYCM_APS_C_SCP_BY_EP_E Type: view_entity
8 Fields 1 Data Sources 5 Associations 1 OData Services 2 Fiori Apps

Scope for entry points

sycm_aps_c_scp_by_ep_e is a CDS View that provides data about "Scope for entry points" in SAP S/4HANA. It reads from 1 data source (sycm_aps_i_scp_by_ep) and exposes 8 fields with key field project_id. It has 5 associations to related views. It is exposed through 1 OData service (SYCM_APS_SCOPING). It is used in 2 Fiori applications: Custom Code Migration, Custom Code Migration - Scoping - Package.

Data Sources (1)

SourceAliasJoin Type
sycm_aps_i_scp_by_ep scope from

Associations (5)

CardinalityTargetAliasCondition
[1] sycm_aps_i_scp_info_text _scope_text _scope_text.scope_information = $projection.scope_information
[0..*] sycm_aps_c_scp_by_ep_item_e _object _object.project_id = scope.project_id and _object.entry_point_type = scope.entry_point_type and _object.entry_point_name = scope.entry_point_name
[0..*] sycm_aps_c_usage_by_procedure _procedure _procedure.project_id = scope.project_id and _procedure.entry_point_type = scope.entry_point_type and _procedure.entry_point_name = scope.entry_point_name
[0..*] sycm_aps_c_atc_fnd_by_ep _finding _finding.project_id = scope.project_id and _finding.entry_point_type = scope.entry_point_type and _finding.entry_point_name = scope.entry_point_name
[0..*] sycm_aps_c_sap_objects_usage _sap_object _sap_object.project_id = scope.project_id and _sap_object.entry_point_name = scope.entry_point_name and _sap_object.entry_point_type = scope.entry_point_type

Annotations (3)

NameValueLevelField
AccessControl.authorizationCheck #CHECK view
EndUserText.label Scope for entry points view
Metadata.allowExtensions true view

OData Services (1)

ServiceBindingVersionContractRelease
SYCM_APS_SCOPING SYCM_APS_SCOPING V2 C1 NOT_RELEASED

Fiori Apps (2)

App IDApp NameTypeDescription
F3191 Custom Code Migration Transactional The Custom Code Migration app enables you to create three different kinds of projects: 1. SAP S/4HANA Migration Project: Analyze custom code that shall be migrated from an existing product like SAP Business Suite to a new product such as SAP S/4HANA 2021. To evaluate the custom objects to be adapted, it performs the SAP S/4HANA custom code checks. 2. SAP BTP Analysis Project: Analyze custom code for readiness to run in SAP BTP, ABAP environment. 3. Custom Code Analysis Project: Analyze custom code with arbitrary ATC check variants. In addition, this app supports you with identifying unused custom code based on your collected usage data. This enables you to remove unused custom code during a system conversion to SAP S/4HANA.
F4199 Custom Code Migration - Scoping - Package Transactional, Analytical One of the biggest challenges for our customers during the system conversion to S/4HANA (or Suite on HANA) on-premise is the custom code adaptation. These adaptations are necessary because of the simplifications (e.g. data model changes, removal of obsolete functionality, removal of redundant components) in S/4HANA compared to the classic ERP. To minimize the efforts for our customers to adapt their code the ABAP Platform provides tools to analyze custom code based on the so-called simplification database. This toolset is crucial for the adoption of S/4HANA on-premise.

Custom Code Migration

Business Role: Quality Manager - Software Development

Custom Code Migration - Scoping - Package

Business Role: Project Manager - IT

Fields (8)

KeyFieldSource TableSource FieldDescription
KEY project_id sycm_aps_i_scp_by_ep project_id Project UUID
last_used sycm_aps_i_scp_by_ep last_used Time Stamp
h_index sycm_aps_i_scp_by_ep h_index Complexity (H-Index)
_scope_text _scope_text
_object _object
_procedure _procedure
_finding _finding
_sap_object _sap_object

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 sycm_aps_c_scp_by_ep_e.
-- 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 sycm_aps_c_scp_by_ep_e AS
SELECT
  scope.project_id AS project_id,
  scope.last_used AS last_used,
  scope.h_index AS h_index
FROM sycm_aps_i_scp_by_ep AS scope
LEFT OUTER JOIN sycm_aps_i_scp_info_text AS _scope_text ON _scope_text.scope_information = scope_information  -- association [1]
LEFT OUTER JOIN sycm_aps_c_scp_by_ep_item_e AS _object ON _object.project_id = scope.project_id AND _object.entry_point_type = scope.entry_point_type AND _object.entry_point_name = scope.entry_point_name  -- association [0..*]
LEFT OUTER JOIN sycm_aps_c_usage_by_procedure AS _procedure ON _procedure.project_id = scope.project_id AND _procedure.entry_point_type = scope.entry_point_type AND _procedure.entry_point_name = scope.entry_point_name  -- association [0..*]
LEFT OUTER JOIN sycm_aps_c_atc_fnd_by_ep AS _finding ON _finding.project_id = scope.project_id AND _finding.entry_point_type = scope.entry_point_type AND _finding.entry_point_name = scope.entry_point_name  -- association [0..*]
LEFT OUTER JOIN sycm_aps_c_sap_objects_usage AS _sap_object ON _sap_object.project_id = scope.project_id AND _sap_object.entry_point_name = scope.entry_point_name AND _sap_object.entry_point_type = scope.entry_point_type  -- association [0..*]
;

Learn More