SYCM_APS_I_USAGE_BY_PROCEDURE
Usage aggregated for project
SYCM_APS_I_USAGE_BY_PROCEDURE is a CDS View in S/4HANA. Usage aggregated for project. It contains 9 fields. 1 CDS views read from this table.
CDS Views using this table (1)
| View | Type | Join | VDM | Description |
|---|---|---|---|---|
| sycm_aps_c_usage_by_procedure | view | from | Usage aggregated for project |
Fields (9)
| Key | Field | CDS Fields | Used in Views |
|---|---|---|---|
| KEY | entry_point_name | entry_point_name | 1 |
| KEY | entry_point_type | entry_point_type | 1 |
| KEY | obj_name | obj_name | 1 |
| KEY | obj_type | obj_type | 1 |
| KEY | project_id | project_id | 1 |
| KEY | sub_name | procedure_name | 1 |
| KEY | sub_type | sub_type | 1 |
| counter | counter | 1 | |
| last_used | last_used | 1 |
Derived SQL schema, reconstructed from the indexed DDIC field metadata (field names, types, lengths and key flags) — a functional representation, not the verbatim SAP source.
-- Usage aggregated for project
-- Derived schema, generated from indexed DDIC field metadata (not the verbatim SAP source).
CREATE TABLE SYCM_APS_I_USAGE_BY_PROCEDURE (
ENTRY_POINT_NAME,
ENTRY_POINT_TYPE,
OBJ_NAME,
OBJ_TYPE,
PROJECT_ID,
SUB_NAME,
SUB_TYPE,
COUNTER,
LAST_USED,
PRIMARY KEY (ENTRY_POINT_NAME, ENTRY_POINT_TYPE, OBJ_NAME, OBJ_TYPE, PROJECT_ID, SUB_NAME, SUB_TYPE)
);
Learn More
- Understanding Data Lineage in SAP S/4HANA
- SAP Tables vs CDS Views — Key Differences
- Understanding the SAP S/4HANA Data Model
- 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
- Sales Document Status Migration: VBUP/VBUK Removal in S/4HANA
- CO Tables in S/4HANA: COEP, COBK, COSS, COSP to ACDOCA