I_PaytReqChgAndPostingData

DDL: I_PAYTREQCHGANDPOSTINGDATA Type: view_entity BASIC

Change And Posting Data of Payt Request

I_PaytReqChgAndPostingData is a Basic CDS View that provides data about "Change And Posting Data of Payt Request" in SAP S/4HANA. It reads from 1 data source (payrqc) and exposes 12 fields with key field PaymentRequest. It has 4 associations to related views.

Data Sources (1)

SourceAliasJoin Type
payrqc payrqc from

Associations (4)

CardinalityTargetAliasCondition
[0..1] I_FinancialAccountType _FinancialAccountType $projection.FinancialAccountType = _FinancialAccountType.FinancialAccountType
[1..1] I_Customer _Customer $projection.CustomerSupplierAccount = _Customer.Customer
[1..1] I_Supplier _Supplier $projection.CustomerSupplierAccount = _Supplier.Supplier
[1..1] E_PaymentRequest _Extension $projection.PaymentRequest = _Extension.PaymentRequest

Annotations (7)

NameValueLevelField
AccessControl.authorizationCheck #MANDATORY view
AccessControl.personalData.blocking #BLOCKED_DATA_EXCLUDED view
ObjectModel.usageType.dataClass #TRANSACTIONAL view
ObjectModel.usageType.serviceQuality #B view
ObjectModel.usageType.sizeCategory #L view
VDM.viewType #BASIC view
EndUserText.label Change And Posting Data of Payt Request view

Fields (12)

KeyFieldSource TableSource FieldDescription
KEY PaymentRequest
LastChangedByUser
LastChangeTime payrqc chtime Time Changed
LastChangeDate
FinancialAccountType
CustomerSupplierAccount
DocumentItemText payrqc sgtxt Text
PaymentRequestType
BankChain payrqc chainid Chain ID
_FinancialAccountType _FinancialAccountType
_Customer _Customer
_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 I_PaytReqChgAndPostingData.
-- 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 I_PaytReqChgAndPostingData AS
SELECT
  cast(payrqc.keyno as farp_prq_keyno preserving type) AS PaymentRequest,
  cast(payrqc.chusr as farp_changed_by preserving type) AS LastChangedByUser,
  payrqc.chtime AS LastChangeTime,
  cast(payrqc.chdate as ttet_dt_chg_date preserving type) AS LastChangeDate,
  cast(payrqc.koart as farp_koart preserving type) AS FinancialAccountType,
  cast(payrqc.konto as farp_account_apar) AS CustomerSupplierAccount,
  payrqc.sgtxt AS DocumentItemText,
  cast(payrqc.payrq_type as farp_payrq_type preserving type) AS PaymentRequestType,
  payrqc.chainid AS BankChain
FROM payrqc
LEFT OUTER JOIN I_FinancialAccountType AS _FinancialAccountType ON FinancialAccountType = _FinancialAccountType.FinancialAccountType  -- association [0..1]
LEFT OUTER JOIN I_Customer AS _Customer ON CustomerSupplierAccount = _Customer.Customer  -- association [1..1]
LEFT OUTER JOIN I_Supplier AS _Supplier ON CustomerSupplierAccount = _Supplier.Supplier  -- association [1..1]
LEFT OUTER JOIN E_PaymentRequest AS _Extension ON PaymentRequest = _Extension.PaymentRequest  -- association [1..1]
;