I_MKT_StatusForBusObj
Status for Business Object
I_MKT_StatusForBusObj is a Basic CDS View (Dimension) that provides data about "Status for Business Object" in SAP S/4HANA. It reads from 1 data source (hpai_status) and exposes 4 fields with key fields SAPObjectType, ObjectStatus. It has 2 associations to related views. Part of development package CUAN_CDS_COMMON.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| hpai_status | hpai_status | from |
Associations (2)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..*] | I_MKT_StatusForBusObjText | _Text | $projection.SAPObjectType = _Text.SAPObjectType and $projection.ObjectStatus = _Text.ObjectStatus |
| [1..1] | I_MKT_ObjectType | _MKT_ObjectType | $projection.SAPObjectType = _MKT_ObjectType.MarketingObjectType |
Annotations (14)
| Name | Value | Level | Field |
|---|---|---|---|
| EndUserText.label | Status for Business Object | view | |
| Analytics.dataCategory | #DIMENSION | view | |
| VDM.viewType | #BASIC | view | |
| AccessControl.authorizationCheck | #NOT_REQUIRED | view | |
| AbapCatalog.sqlViewName | IMKT_STATUS | view | |
| ObjectModel.representativeKey | ObjectStatus | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AbapCatalog.preserveKey | true | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| ObjectModel.usageType.serviceQuality | #A | view | |
| ObjectModel.usageType.sizeCategory | #S | view | |
| ObjectModel.usageType.dataClass | #CUSTOMIZING | view | |
| ObjectModel.modelingPattern | #ANALYTICAL_DIMENSION | view | |
| Metadata.ignorePropagatedAnnotations | true | view |
Fields (4)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | SAPObjectType | object_type | Type | |
| KEY | ObjectStatus | status_id | Trans Doc Status | |
| _MKT_ObjectType | _MKT_ObjectType | |||
| _Text | _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_MKT_StatusForBusObj.
-- 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: IMKT_STATUS
CREATE VIEW I_MKT_StatusForBusObj AS
SELECT
object_type AS SAPObjectType,
status_id AS ObjectStatus
FROM hpai_status
LEFT OUTER JOIN I_MKT_StatusForBusObjText AS _Text ON SAPObjectType = _Text.SAPObjectType AND ObjectStatus = _Text.ObjectStatus -- association [0..*]
LEFT OUTER JOIN I_MKT_ObjectType AS _MKT_ObjectType ON SAPObjectType = _MKT_ObjectType.MarketingObjectType -- association [1..1]
;
Learn More
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- CDS View Annotations — A Complete Guide
- What Is a CDS View in SAP S/4HANA?
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- 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