P_PendingGIQty

DDL: P_PENDINGGIQTY SQL: PPENDINGGI Type: view COMPOSITE
12 Fields 2 Data Sources

P_PendingGIQty is a Composite CDS View in SAP S/4HANA. It reads from 2 data sources (P_SchedLineGIQty, I_SubcontractingComponent) and exposes 12 fields with key fields PurchasingDocument, PurchasingDocumentItem, ScheduleLine, Material, Supplier.

Data Sources (2)

SourceAliasJoin Type
P_SchedLineGIQty _SubcontrgOrdsSchedLines left_outer
I_SubcontractingComponent I_SubcontractingComponent from

Annotations (6)

NameValueLevelField
AbapCatalog.sqlViewName PPENDINGGI view
AbapCatalog.compiler.compareFilter true view
AccessControl.authorizationCheck #PRIVILEGED_ONLY view
ClientHandling.algorithm #SESSION_VARIABLE view
VDM.viewType #COMPOSITE view
VDM.private true view

Fields (12)

KeyFieldSource TableSource FieldDescription
KEY PurchasingDocument I_SubcontractingComponent PurchasingDocument Purchasing Document
KEY PurchasingDocumentItem I_SubcontractingComponent PurchasingDocumentItem Purchasing Doc. Item
KEY ScheduleLine I_SubcontractingComponent ScheduleLine Schedule Line
KEY Material I_SubcontractingComponent Material Vehicle Model
KEY Supplier I_SubcontractingComponent Supplier Supplier
KEY Plant I_SubcontractingComponent Plant Valuation Area
KEY RequirementDate I_SubcontractingComponent RequirementDate Requirement Date
KEY Reservation I_SubcontractingComponent Reservation Reservation
KEY ReservationItem I_SubcontractingComponent ReservationItem Reservation Item
RequiredQuantity RequiredQuantity Requirement qty
GIDonePerScheduleLineQty P_SchedLineGIQty GIDonePerScheduleLineQty
CummulativeSheduleQuantity P_SchedLineGIQty CummulativeSheduleQuantity

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 P_PendingGIQty.
-- 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: PPENDINGGI

CREATE VIEW P_PendingGIQty AS
SELECT
  I_SubcontractingComponent.PurchasingDocument AS PurchasingDocument,
  I_SubcontractingComponent.PurchasingDocumentItem AS PurchasingDocumentItem,
  I_SubcontractingComponent.ScheduleLine AS ScheduleLine,
  I_SubcontractingComponent.Material AS Material,
  I_SubcontractingComponent.Supplier AS Supplier,
  I_SubcontractingComponent.Plant AS Plant,
  I_SubcontractingComponent.RequirementDate AS RequirementDate,
  I_SubcontractingComponent.Reservation AS Reservation,
  I_SubcontractingComponent.ReservationItem AS ReservationItem,
  RequiredQuantity,
  _SubcontrgOrdsSchedLines.GIDonePerScheduleLineQty AS GIDonePerScheduleLineQty,
  _SubcontrgOrdsSchedLines.CummulativeSheduleQuantity AS CummulativeSheduleQuantity
FROM I_SubcontractingComponent
LEFT OUTER JOIN P_SchedLineGIQty AS _SubcontrgOrdsSchedLines ON /* join condition not captured in parsed metadata */
;

Learn More