I_ProcmtHubPurgOrgAPI01
Purchasing Org in Connected System
I_ProcmtHubPurgOrgAPI01 (Basic)
Package: Explore, extend and adapt the SAP S/4HANA Cloud Private Edition with built-in and side-by-side extension capabilities.
Sourcing & Procurement
I_ProcmtHubPurgOrgAPI01 is a Basic CDS View (Dimension) that provides data about "Purchasing Org in Connected System" in SAP S/4HANA. It reads from 1 data source (mmpur_c_be_porgr) and exposes 6 fields with key fields ProcurementHubSourceSystem, ProcmtHubPurchasingOrg. It has 1 association to related views.
SAP Help Documentation
| Category | CDS Views for Purchasing Organization |
|---|---|
| Status | Released |
You must have a role based on the SAP_BR_CENTRAL_PURCHASER business role template.
SAP API Hub
| State | C1 |
|---|---|
| Line of Business | Sourcing & Procurement |
| Application Component | MM-PUR-HUB |
| Capabilities | Data Source in SQL Select |
| Package | Sourcing & Procurement for SAP S/4HANA Cloud Private Edition |
Documentation
- Analytics with CDS Views — Build Analytics for S/4HANA Cloud Private Edition ABAP CDS views replicated to SAP Cloud Platform
- CDS Views on SAP Business Accelerator Hub — Explore SAP S/4HANA Cloud Private Edition Private Edition CDS Views on SAP Business Accelerator Hub
- Create CDS View as API — Create CDS views in SAP S/4HANA Cloud Private Edition and consume them as APIs
- Custom CDS Views — Access data using a Custom Core Data Service view (Custom CDS view)
- Key User Extensibility Tools — The Key User Extensibility Tools of S/4HANA
- SAP Extensibility Explorer for SAP S/4HANA Cloud Private Edition — Explore SAP S/4HANA Cloud Private Edition Extensibility options by leveraging the sample scenarios from SAP
- SAP S/4HANA Extensibility — SAP S/4HANA Extensibility Tutorial
- VDM View Types — The Virtual Data Model in SAP S/4HANA Cloud Private Edition
- View Browser — Search, browse and tag CDS Views
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| mmpur_c_be_porgr | mmpur_c_be_porgr | from |
Associations (1)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [1..1] | I_ProcmtHubBackendSourceSystem | _ProcmtHubBackendSourceSystem | $projection.ProcurementHubSourceSystem = _ProcmtHubBackendSourceSystem.ProcurementHubSourceSystem |
Annotations (16)
| Name | Value | Level | Field |
|---|---|---|---|
| EndUserText.label | Purchasing Org in Connected System | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| ObjectModel.usageType.dataClass | #ORGANIZATIONAL | view | |
| ObjectModel.usageType.serviceQuality | #A | view | |
| ObjectModel.usageType.sizeCategory | #S | view | |
| AbapCatalog.sqlViewName | IPRCMTPORG | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AccessControl.authorizationCheck | #NOT_REQUIRED | view | |
| AbapCatalog.preserveKey | true | view | |
| VDM.viewType | #BASIC | view | |
| VDM.lifecycle.contract.type | #PUBLIC_LOCAL_API | view | |
| ObjectModel.supportedCapabilities | #SQL_DATA_SOURCE | view | |
| ObjectModel.representativeKey | ProcmtHubPurchasingOrg | view | |
| Metadata.ignorePropagatedAnnotations | true | view | |
| Analytics.dataCategory | #DIMENSION | view | |
| Analytics.internalName | #LOCAL | view |
Fields (6)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | ProcurementHubSourceSystem | be_source_sys | Connected System ID | |
| KEY | ProcmtHubPurchasingOrg | be_purchorg | Connected Purchasing Organization | |
| ProcmtHubPurgOrgUniqueID | be_purchorg_unique_id | Connected Purchasing Organization Unique ID | ||
| ProcmtHubPurgOrgName | be_purchorg_name | Connected Purchasing Organisation Name | ||
| ProcurementHubSourceSystemName | _ProcmtHubBackendSourceSystem | ProcurementHubSourceSystemName | Connected System Name | |
| _ProcmtHubBackendSourceSystem | _ProcmtHubBackendSourceSystem |
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_ProcmtHubPurgOrgAPI01.
-- 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: IPRCMTPORG
CREATE VIEW I_ProcmtHubPurgOrgAPI01 AS
SELECT
be_source_sys AS ProcurementHubSourceSystem,
be_purchorg AS ProcmtHubPurchasingOrg,
be_purchorg_unique_id AS ProcmtHubPurgOrgUniqueID,
be_purchorg_name AS ProcmtHubPurgOrgName,
_ProcmtHubBackendSourceSystem.ProcurementHubSourceSystemName AS ProcurementHubSourceSystemName
FROM mmpur_c_be_porgr
LEFT OUTER JOIN I_ProcmtHubBackendSourceSystem AS _ProcmtHubBackendSourceSystem ON ProcurementHubSourceSystem = _ProcmtHubBackendSourceSystem.ProcurementHubSourceSystem -- 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