LAW3_UI_USMM_USER_CONS_C
LAW3.0 Information system:User Consolid
LAW3_UI_USMM_USER_CONS_C is a CDS View that provides data about "LAW3.0 Information system:User Consolid" in SAP S/4HANA. It reads from 2 data sources (LAW3_UI_USER_TYPES_I, LAW3_UI_USMM_PERS_I) and exposes 10 fields with key fields systemguid, partid, uname.
Data Sources (2)
| Source | Alias | Join Type |
|---|---|---|
| LAW3_UI_USER_TYPES_I | LAW3_UI_USER_TYPES_I | left_outer |
| LAW3_UI_USMM_PERS_I | Pers | from |
Parameters (2)
| Name | Type | Default |
|---|---|---|
| p_datasetguid | guid | |
| p_language | sylangu |
Annotations (5)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | LAW3UIQUSRCONS | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AbapCatalog.preserveKey | true | view | |
| AccessControl.authorizationCheck | #NOT_REQUIRED | view | |
| EndUserText.label | LAW3.0 Information system:User Consolid | view |
Fields (10)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | systemguid | LAW3_UI_USMM_PERS_I | systemguid | GUID |
| KEY | partid | LAW3_UI_USMM_PERS_I | partid | Part ID |
| KEY | uname | LAW3_UI_USMM_PERS_I | uname | User Name |
| firstname | LAW3_UI_USMM_PERS_I | firstname | First Name | |
| lastname | LAW3_UI_USMM_PERS_I | lastname | Last Name | |
| accountid | LAW3_UI_USMM_PERS_I | accountid | Account no. | |
| emailaddr | LAW3_UI_USMM_PERS_I | emailaddr | E-Mail Address | |
| licensetype | LAW3_UI_USMM_PERS_I | licensetype | User Type ID | |
| usertypecons | LAW3_UI_USMM_PERS_I | usertypecons | User Type ID | |
| utyptext | Type | utyptext | Contr. User Type |
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_USER_CONS_C.
-- 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: LAW3UIQUSRCONS
-- Parameters: p_datasetguid : guid, p_language : sylangu
CREATE VIEW LAW3_UI_USMM_USER_CONS_C AS
SELECT
Pers.systemguid AS systemguid,
Pers.partid AS partid,
Pers.uname AS uname,
Pers.firstname AS firstname,
Pers.lastname AS lastname,
Pers.accountid AS accountid,
Pers.emailaddr AS emailaddr,
Pers.licensetype AS licensetype,
Pers.usertypecons AS usertypecons,
Type.utyptext AS utyptext
FROM LAW3_UI_USMM_PERS_I AS Pers
LEFT OUTER JOIN LAW3_UI_USER_TYPES_I 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