I_PaytDateGrouping
Payment Date Grouping
I_PaytDateGrouping is a Basic CDS View that provides data about "Payment Date Grouping" in SAP S/4HANA. It reads from 1 data source (dfpayg) and exposes 14 fields with key fields PaymentRunDate, PaymentRunID, PaymentRunIsProposal, PaymentOrigin, PaymentMediumFormat. Part of development package FINS_AP_PP.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| dfpayg | dfpayg | from |
Annotations (10)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | IPAYTDATEGRPG | view | |
| VDM.viewType | #BASIC | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| Metadata.ignorePropagatedAnnotations | true | view | |
| AccessControl.authorizationCheck | #NOT_REQUIRED | view | |
| EndUserText.label | Payment Date Grouping | view | |
| ObjectModel.usageType.serviceQuality | #C | view | |
| ObjectModel.usageType.sizeCategory | #M | view | |
| ObjectModel.usageType.dataClass | #TRANSACTIONAL | view |
Fields (14)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | PaymentRunDate | laufd | Run On | |
| KEY | PaymentRunID | laufi | Settlement ID | |
| KEY | PaymentRunIsProposal | xvorl | Proposal Run | |
| KEY | PaymentOrigin | grpno | Routine Number | |
| KEY | PaymentMediumFormat | formi | Payt Mdm Format | |
| PayingCompanyCode | zbukr | Paying CoCd | ||
| BankCountry | banks | Bank Ctry/Rgn. Key | ||
| BankKey | bankl | House Bank | ||
| HouseBank | hbkid | House Bank | ||
| HouseBankAccount | hktid | House Bank Account | ||
| DebitCreditCode | crdeb | Credit/Debit Memo | ||
| PaymentMethod | rzawe | Pymt Meth. | ||
| NumberOfPayments | anz_erz | No. of Payts | ||
| NumberOfCompletedPayments | anz_erl | Completed Pymts |
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_PaytDateGrouping.
-- 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: IPAYTDATEGRPG
CREATE VIEW I_PaytDateGrouping AS
SELECT
laufd AS PaymentRunDate,
laufi AS PaymentRunID,
xvorl AS PaymentRunIsProposal,
grpno AS PaymentOrigin,
formi AS PaymentMediumFormat,
zbukr AS PayingCompanyCode,
banks AS BankCountry,
bankl AS BankKey,
hbkid AS HouseBank,
hktid AS HouseBankAccount,
crdeb AS DebitCreditCode,
rzawe AS PaymentMethod,
anz_erz AS NumberOfPayments,
anz_erl AS NumberOfCompletedPayments
FROM dfpayg
;
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