I_ISLM_P_PREREQ_CHK
Prerequisite check
I_ISLM_P_PREREQ_CHK is a CDS View that provides data about "Prerequisite check" in SAP S/4HANA. It reads from 1 data source (islm_prereq_chk) and exposes 19 fields with key field guid. It has 1 association to related views.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| islm_prereq_chk | islm_prereq_chk | from |
Associations (1)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [1..1] | I_ISLM_P_PREREQ_RUNS | run | $projection.check_run_guid = run.guid |
Annotations (2)
| Name | Value | Level | Field |
|---|---|---|---|
| AccessControl.authorizationCheck | #CHECK | view | |
| EndUserText.label | Prerequisite check | view |
Fields (19)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | guid | guid | UUID 22 char. | |
| name | name | Zone name | ||
| description | description | Well Code Des. | ||
| is_mandatory | is_mandatory | TRUE | ||
| check_type | check_type | Type of OTB Check | ||
| status | status | Workflow Status | ||
| type | type | Worklist Type | ||
| id | id | WorklistID | ||
| msg_number | msg_number | Message Number | ||
| message | message | User Message | ||
| message_v1 | message_v1 | Message Variable | ||
| message_v2 | message_v2 | Message Variable | ||
| message_v3 | message_v3 | Message Variable | ||
| message_v4 | message_v4 | Message Variable | ||
| actual_value | actual_value | Actual Value | ||
| addl_info | addl_info | Serialized JSON | ||
| devclass | ||||
| scn_status | ||||
| run | run |
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 I_ISLM_P_PREREQ_CHK.
-- 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 I_ISLM_P_PREREQ_CHK AS
SELECT
guid,
name,
description,
is_mandatory,
check_type,
status,
type,
id,
msg_number,
message,
message_v1,
message_v2,
message_v3,
message_v4,
actual_value,
addl_info,
run._parent.parent_guid AS devclass,
run._parent.status AS scn_status,
run
FROM islm_prereq_chk
LEFT OUTER JOIN I_ISLM_P_PREREQ_RUNS AS run ON check_run_guid = run.guid -- association [1..1]
;
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