sycm_aps_c_usage_by_procedure
Usage aggregated for project
sycm_aps_c_usage_by_procedure is a CDS View that provides data about "Usage aggregated for project" in SAP S/4HANA. It reads from 3 data sources (sycma_halstead, sycm_aps_i_procedure_type_text, sycm_aps_i_usage_by_procedure) and exposes 6 fields with key fields project_id, obj_type, obj_name, sub_type. It is exposed through 1 OData service (SYCM_APS_SCOPING). It is used in 1 Fiori application: Custom Code Migration. Part of development package SYCM_APS.
Data Sources (3)
| Source | Alias | Join Type |
|---|---|---|
| sycma_halstead | metrics | left_outer |
| sycm_aps_i_procedure_type_text | procedure_type_text | left_outer |
| sycm_aps_i_usage_by_procedure | usage | from |
Annotations (6)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | SYCMVCUSAGEPROC | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AccessControl.authorizationCheck | #NOT_REQUIRED | view | |
| Metadata.allowExtensions | true | view | |
| EndUserText.label | Usage aggregated for project | view | |
| Search.searchable | true | view |
OData Services (1)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| SYCM_APS_SCOPING | SYCM_APS_SCOPING | V2 | C1 | NOT_RELEASED |
Fiori Apps (1)
| App ID | App Name | Type | Description |
|---|---|---|---|
| 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. |
Custom Code Migration
Business Role: Quality Manager - Software Development
Fields (6)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | project_id | sycm_aps_i_usage_by_procedure | project_id | Project UUID |
| KEY | obj_type | sycm_aps_i_usage_by_procedure | obj_type | Type |
| KEY | obj_name | sycm_aps_i_usage_by_procedure | obj_name | Object Name |
| KEY | sub_type | sycm_aps_i_usage_by_procedure | sub_type | Object Type |
| counter | sycm_aps_i_usage_by_procedure | counter | Version | |
| last_used | sycm_aps_i_usage_by_procedure | last_used | Time Stamp |
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_usage_by_procedure.
-- 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: SYCMVCUSAGEPROC
CREATE VIEW sycm_aps_c_usage_by_procedure AS
SELECT
usage.project_id AS project_id,
usage.obj_type AS obj_type,
usage.obj_name AS obj_name,
usage.sub_type AS sub_type,
usage.counter AS counter,
usage.last_used AS last_used
FROM sycm_aps_i_usage_by_procedure AS usage
LEFT OUTER JOIN sycma_halstead AS metrics ON /* join condition not captured in parsed metadata */
LEFT OUTER JOIN sycm_aps_i_procedure_type_text AS procedure_type_text ON /* join condition not captured in parsed metadata */
;
Learn More
- 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?
- 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