I_BCS_MSG_REQUEST_M
Interface view for BCS Requests
I_BCS_MSG_REQUEST_M is a CDS View that provides data about "Interface view for BCS Requests" in SAP S/4HANA. It reads from 1 data source (I_BCS_MSG_REQUEST) and exposes 11 fields with key field request_id. It has 3 associations to related views.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| I_BCS_MSG_REQUEST | I_BCS_MSG_REQUEST | from |
Associations (3)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..*] | I_BCS_MSG_STATUS_T | _status_text | $projection.msg_status = _status_text.status |
| [0..*] | I_BCS_MSG_RECIPIENT_STATUS_M | _recipient_status | $projection.request_id = _recipient_status.request_id |
| [0..*] | I_BCS_MSG_RECIPIENT_M | _recipient | |
Annotations (2)
| Name | Value | Level | Field |
|---|---|---|---|
| EndUserText.label | Interface view for BCS Requests | view | |
| AccessControl.authorizationCheck | #CHECK | view |
Fields (11)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | request_id | request_id | Request unique ID | |
| created | created | UTC Time Stamp in Short Form (YYYYMMDDhhmmss) | ||
| creator | creator | User ID | ||
| sender | sender | Sender | ||
| subject | subject | Title | ||
| protocol | protocol | Single-Character Flag | ||
| msg_status | msg_status | Status | ||
| category | category | Violation Category | ||
| sending_api | sending_api | Mail Origin | ||
| _recipient | _recipient | |||
| _status_text | _status_text |
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_BCS_MSG_REQUEST_M.
-- 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_BCS_MSG_REQUEST_M AS
SELECT
request_id,
created,
creator,
sender,
subject,
protocol,
msg_status,
category,
sending_api
FROM I_BCS_MSG_REQUEST
LEFT OUTER JOIN I_BCS_MSG_STATUS_T AS _status_text ON msg_status = _status_text.status -- association [0..*]
LEFT OUTER JOIN I_BCS_MSG_RECIPIENT_STATUS_M AS _recipient_status ON request_id = _recipient_status.request_id -- association [0..*]
LEFT OUTER JOIN I_BCS_MSG_RECIPIENT_M AS _recipient ON /* condition not available in parsed metadata */ -- association [0..*]
;
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