C_GRIRProcessHistoryNote
Notes history for purchase orders
C_GRIRProcessHistoryNote is a Consumption CDS View that provides data about "Notes history for purchase orders" in SAP S/4HANA. It reads from 1 data source (I_GRIRProcessHistory) and exposes 18 fields with key fields CompanyCode, PurchasingDocument, PurchasingDocumentItem, LastChangeDateTime. It has 2 associations to related views. It is exposed through 3 OData services (ASQL_F3302, ASQL_F5796, UI_GRIR_BPI). It is used in 1 Fiori application: GR/IR Process Insights. Part of development package FINS_FIS_FICO_APPS.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| I_GRIRProcessHistory | I_GRIRProcessHistory | from |
Associations (2)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..1] | I_Supplier | _Supplier | $projection.Supplier = _Supplier.Supplier |
| [0..1] | I_UserContactCard | _LastChangedByUser | $projection.LastChangedByUser = _LastChangedByUser.ContactCardID |
Annotations (6)
| Name | Value | Level | Field |
|---|---|---|---|
| AccessControl.authorizationCheck | #CHECK | view | |
| VDM.viewType | #CONSUMPTION | view | |
| EndUserText.label | Notes history for purchase orders | view | |
| ObjectModel.usageType.sizeCategory | #L | view | |
| ObjectModel.usageType.dataClass | #TRANSACTIONAL | view | |
| ObjectModel.usageType.serviceQuality | #B | view |
OData Services (3)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| ASQL_F3302 | ASQL_F3302 | C2 | NOT_RELEASED | |
| ASQL_F5796 | ASQL_F5796 | C2 | NOT_RELEASED | |
| UI_GRIR_BPI | UI_GRIR_BPI | V2 | C1 | NOT_RELEASED |
Fiori Apps (1)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F5796 | GR/IR Process Insights | Analytical | With this app, you can gain insights into the GR/IR (goods receipt/invoice receipt) account reconciliation process which is performed using the Reconcile GR/IR Accounts app. |
GR/IR Process Insights
Business Role: General Ledger Accountant
With this app, you can gain insights into the GR/IR (goods receipt/invoice receipt) account reconciliation process which is performed using the app. You can visualize the activities of the reconciliation process and thereby identify opportunities for process improvements, such as, by discovering bottlenecks, duplicate work or root causes for delays. You can also retrospectively review all activities on the level of a purchasing document item together with all relevant documents from the purchasing document history. Thus, this app enables you, as a process owner, to analyze the process efficiency of the GR/IR account reconciliation process and to define improvement activities.
Fields (18)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | CompanyCode | I_GRIRProcessHistory | CompanyCode | Receiver Company Code |
| KEY | PurchasingDocument | I_GRIRProcessHistory | PurchasingDocument | Purchasing Document |
| KEY | PurchasingDocumentItem | I_GRIRProcessHistory | PurchasingDocumentItem | Purchasing Doc. Item |
| KEY | LastChangeDateTime | I_GRIRProcessHistory | LastChangeDateTime | Timestamp |
| LastChangedByUser | I_GRIRProcessHistory | LastChangedByUser | User Name | |
| Note | I_GRIRProcessHistory | Note | TradeRequest Comment | |
| HasNote | I_GRIRProcessHistory | HasNote | TRUE | |
| _CompanyCode | I_GRIRProcessHistory | _CompanyCode | ||
| _PurchasingDocument | I_GRIRProcessHistory | _PurchasingDocument | ||
| _PurchasingDocumentItem | I_GRIRProcessHistory | _PurchasingDocumentItem | ||
| PurchasingOrganization | I_GRIRProcessHistory | PurchasingOrganization | Purchasing Organization | |
| PurchasingGroup | I_GRIRProcessHistory | PurchasingGroup | Purchasing Group | |
| Plant | I_GRIRProcessHistory | Plant | Valuation Area | |
| Supplier | I_GRIRProcessHistory | Supplier | Supplier | |
| GRIRClearingProcessStatus | I_GRIRProcessHistory | GRIRClearingProcessStatus | Status | |
| ResponsiblePerson | I_GRIRProcessHistory | ResponsiblePerson | Processor | |
| _LastChangedByUser | _LastChangedByUser | |||
| _Supplier | _Supplier |
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 C_GRIRProcessHistoryNote.
-- 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 C_GRIRProcessHistoryNote AS
SELECT
I_GRIRProcessHistory.CompanyCode AS CompanyCode,
I_GRIRProcessHistory.PurchasingDocument AS PurchasingDocument,
I_GRIRProcessHistory.PurchasingDocumentItem AS PurchasingDocumentItem,
I_GRIRProcessHistory.LastChangeDateTime AS LastChangeDateTime,
I_GRIRProcessHistory.LastChangedByUser AS LastChangedByUser,
I_GRIRProcessHistory.Note AS Note,
I_GRIRProcessHistory.HasNote AS HasNote,
I_GRIRProcessHistory._CompanyCode AS _CompanyCode,
I_GRIRProcessHistory._PurchasingDocument AS _PurchasingDocument,
I_GRIRProcessHistory._PurchasingDocumentItem AS _PurchasingDocumentItem,
I_GRIRProcessHistory.PurchasingOrganization AS PurchasingOrganization,
I_GRIRProcessHistory.PurchasingGroup AS PurchasingGroup,
I_GRIRProcessHistory.Plant AS Plant,
I_GRIRProcessHistory.Supplier AS Supplier,
I_GRIRProcessHistory.GRIRClearingProcessStatus AS GRIRClearingProcessStatus,
I_GRIRProcessHistory.ResponsiblePerson AS ResponsiblePerson
FROM I_GRIRProcessHistory
LEFT OUTER JOIN I_Supplier AS _Supplier ON Supplier = _Supplier.Supplier -- association [0..1]
LEFT OUTER JOIN I_UserContactCard AS _LastChangedByUser ON LastChangedByUser = _LastChangedByUser.ContactCardID -- association [0..1]
;
Learn More
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- OData Services in SAP S/4HANA Explained
- Service Bindings and Service Definitions in SAP S/4HANA
- SAP Fiori Apps Architecture — How Fiori Apps Connect to Data
- 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