I_PurchaseRequisitionAPI01

DDL: I_PURCHASEREQUISITIONAPI01 SQL: IPRHEADERAPI01 Type: view COMPOSITE

Purchase Requisition Header

I_PurchaseRequisitionAPI01 (Composite)

Package: Explore, extend and adapt the SAP S/4HANA Cloud Private Edition with built-in and side-by-side extension capabilities.

Sourcing & Procurement

I_PurchaseRequisitionAPI01 is a Composite CDS View that provides data about "Purchase Requisition Header" in SAP S/4HANA. It reads from 1 data source (I_Purchaserequisitionitem) and exposes 5 fields with key field PurchaseRequisition. It has 1 association to related views.

SAP Help Documentation

CategoryCDS Views for Purchase Requisitions
StatusReleased
Purpose
This CDS view helps to retrieve the fields related to a purchase requisition. This CDS view provides the prerequisites for answering the following business questions: How many purchase requisitions belong to a given document type? Which are the purchase requisitions that have been recently modified?

Prerequisites
Users who want to run reports using this CDS view must have a role based on the business role template listed in the table above.

Structure
Object types This view relates to the following SAP object type: Purchase Requisition Main CDS parameters and filters The main CDS parameters are: Purchase requisition number Purchase requisition document type Last changed date and time Measures and attributes Some important measures and attributes are: Purchase Requisition number

View on SAP Help Portal →

SAP API Hub

StateC1
Line of BusinessSourcing & Procurement
Application ComponentMM-PUR-REQ
CapabilitiesData Source in SQL Select, Data Source for Defining CDS Entities, Association Target for Defining CDS Entities
PackageSourcing & Procurement for SAP S/4HANA Cloud Private Edition
Description <p>This CDS view helps to retrieve the fields related to a purchase requisition.</p> <p>This CDS view provides the prerequisites for answering the following business questions:</p> <ul> <li><p>How many purchase requisitions belong to a given document type?</p></li> <li><p>Which are the purchase requisitions that have been recently modified?</p></li> </ul>

Documentation

Data Sources (1)

SourceAliasJoin Type
I_Purchaserequisitionitem I_Purchaserequisitionitem from

Associations (1)

CardinalityTargetAliasCondition
[1..*] I_PurchaseRequisitionItemAPI01 _PurchaseRequisitionItem $projection.PurchaseRequisition = _PurchaseRequisitionItem.PurchaseRequisition

Annotations (14)

NameValueLevelField
ObjectModel.usageType.dataClass #MIXED view
ObjectModel.usageType.serviceQuality #C view
ObjectModel.usageType.sizeCategory #L view
ObjectModel.representativeKey PurchaseRequisition view
AbapCatalog.sqlViewName IPRHEADERAPI01 view
AbapCatalog.compiler.compareFilter true view
AccessControl.authorizationCheck #CHECK view
EndUserText.label Purchase Requisition Header view
ClientHandling.algorithm #SESSION_VARIABLE view
VDM.viewType #COMPOSITE view
Metadata.ignorePropagatedAnnotations true view
AbapCatalog.preserveKey true view
AccessControl.personalData.blocking #BLOCKED_DATA_EXCLUDED view
VDM.lifecycle.contract.type #PUBLIC_LOCAL_API view

Fields (5)

KeyFieldSource TableSource FieldDescription
KEY PurchaseRequisition PurchaseRequisition Purchase Requisition Number
PurReqnDescription PurReqnDescription Purchase Requisition Description
PurchaseRequisitionType PurchaseRequisitionType Purchase Requisition Document Type
LastChangeDateTime
_PurchaseRequisitionItem _PurchaseRequisitionItem

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_PurchaseRequisitionAPI01.
-- 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: IPRHEADERAPI01

CREATE VIEW I_PurchaseRequisitionAPI01 AS
SELECT
  PurchaseRequisition,
  PurReqnDescription,
  PurchaseRequisitionType,
  max( LastChangeDateTime ) AS LastChangeDateTime
FROM I_Purchaserequisitionitem
LEFT OUTER JOIN I_PurchaseRequisitionItemAPI01 AS _PurchaseRequisitionItem ON PurchaseRequisition = _PurchaseRequisitionItem.PurchaseRequisition  -- association [1..*]
;