LAW3_UI_USMM_ENGINES_OLD_I
LAW3.0 Engines from LAW2.0
LAW3_UI_USMM_ENGINES_OLD_I is a CDS View that provides data about "LAW3.0 Engines from LAW2.0" in SAP S/4HANA. It reads from 2 data sources (LAW3_UI_USMM_PARTS_I, law2d_usmm_rslt) and exposes 15 fields with key fields datasetguid, systemguid, partid.
Data Sources (2)
| Source | Alias | Join Type |
|---|---|---|
| LAW3_UI_USMM_PARTS_I | Parts | from |
| law2d_usmm_rslt | Results | inner |
Annotations (5)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | LAW3UIQENGINOLD | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AbapCatalog.preserveKey | true | view | |
| AccessControl.authorizationCheck | #NOT_REQUIRED | view | |
| EndUserText.label | LAW3.0 Engines from LAW2.0 | view |
Fields (15)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | datasetguid | LAW3_UI_USMM_PARTS_I | datasetguid | Object GUID |
| KEY | systemguid | LAW3_UI_USMM_PARTS_I | systemguid | GUID |
| KEY | partid | LAW3_UI_USMM_PARTS_I | partid | Part ID |
| unit_rslt | law2d_usmm_rslt | unit | UoM | |
| applic | ||||
| unit | ||||
| startdate | law2d_usmm_rslt | perstart | Start Date | |
| enddate | law2d_usmm_rslt | perend | End Date | |
| counter | law2d_usmm_rslt | counter | Version | |
| datasetid | LAW3_UI_USMM_PARTS_I | datasetid | LAW Measurement ID | |
| sysid | LAW3_UI_USMM_PARTS_I | sysid | System ID | |
| instno | LAW3_UI_USMM_PARTS_I | instno | Inst. Number | |
| sapclient | LAW3_UI_USMM_PARTS_I | sapclient | Client ID | |
| systemno | LAW3_UI_USMM_PARTS_I | systemno | System Number | |
| status | LAW3_UI_USMM_PARTS_I | status | Workflow Status |
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 LAW3_UI_USMM_ENGINES_OLD_I.
-- 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: LAW3UIQENGINOLD
CREATE VIEW LAW3_UI_USMM_ENGINES_OLD_I AS
SELECT
Parts.datasetguid AS datasetguid,
Parts.systemguid AS systemguid,
Parts.partid AS partid,
Results.unit AS unit_rslt,
substring(Results.genericid,11,4) AS applic,
substring(Results.unit,7,4) AS unit,
Results.perstart AS startdate,
Results.perend AS enddate,
Results.counter AS counter,
Parts.datasetid AS datasetid,
Parts.sysid AS sysid,
Parts.instno AS instno,
Parts.sapclient AS sapclient,
Parts.systemno AS systemno,
Parts.status AS status
FROM LAW3_UI_USMM_PARTS_I AS Parts
INNER JOIN law2d_usmm_rslt AS Results ON /* join condition not captured in parsed metadata */
;
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