R_FinTransCashFlowActivity
Financial Transaction Cash Flow Activity
R_FinTransCashFlowActivity is a Basic CDS View that provides data about "Financial Transaction Cash Flow Activity" in SAP S/4HANA. It reads from 4 data sources (vtbfha, at06, vtbfhazu, vtbfhazu) and exposes 6 fields with key fields CompanyCode, FinancialTransaction, FinancialInstrumentActivity.
Data Sources (4)
Annotations (14)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | RFINTRANSCASHACT | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AbapCatalog.preserveKey | true | view | |
| AbapCatalog.buffering.status | #NOT_ALLOWED | view | |
| AccessControl.authorizationCheck | #PRIVILEGED_ONLY | view | |
| AccessControl.personalData.blocking | #NOT_REQUIRED | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| EndUserText.label | Financial Transaction Cash Flow Activity | view | |
| ObjectModel.usageType.dataClass | #MIXED | view | |
| ObjectModel.usageType.serviceQuality | #D | view | |
| ObjectModel.usageType.sizeCategory | #L | view | |
| Metadata.allowExtensions | false | view | |
| VDM.lifecycle.contract.type | #SAP_INTERNAL_API | view | |
| VDM.viewType | #BASIC | view |
Fields (6)
@AbapCatalog.sqlViewName: 'RFINTRANSCASHACT'
@AbapCatalog.compiler.compareFilter: true
@AbapCatalog.preserveKey: true
@AbapCatalog.buffering.status: #NOT_ALLOWED
@AccessControl.authorizationCheck: #PRIVILEGED_ONLY
@AccessControl.personalData.blocking: #NOT_REQUIRED
@ClientHandling.algorithm: #SESSION_VARIABLE
@EndUserText.label: 'Financial Transaction Cash Flow Activity'
@ObjectModel.usageType.dataClass: #MIXED
@ObjectModel.usageType.serviceQuality: #D
@ObjectModel.usageType.sizeCategory: #L
@Metadata.allowExtensions:false
@VDM.lifecycle.contract.type: #SAP_INTERNAL_API
@VDM.viewType: #BASIC
define view R_FinTransCashFlowActivity
as select distinct from vtbfhazu as Activity
left outer join vtbfhazu as SuccActivity on Activity.bukrs = SuccActivity.bukrs
and Activity.rfha = SuccActivity.rfha
and Activity.rfhazu = SuccActivity.rofhazu
left outer join vtbfhazu as SuccSuccActivity on SuccActivity.bukrs = SuccSuccActivity.bukrs
and SuccActivity.rfha = SuccSuccActivity.rfha
and SuccActivity.rfhazu = SuccSuccActivity.rofhazu
inner join vtbfha as Deal on Activity.bukrs = Deal.bukrs
and Activity.rfha = Deal.rfha
left outer join at06 as ProcessingCategory on Deal.sanlf = ProcessingCategory.sanlf
and Deal.abwtyp = ProcessingCategory.abwtyp
and Deal.sfgtyp = ProcessingCategory.sfgtyp
and Activity.sfgzustt = ProcessingCategory.sfgzustt
{
key Activity.bukrs as CompanyCode,
key Activity.rfha as FinancialTransaction,
key Activity.rfhazu as FinancialInstrumentActivity,
Activity.sgsart as FinancialInstrumentProductType,
Deal.sanlf as FinancialInstrProductCategory,
Deal.rfhazul as FinInstrLastActiveActivity
}
where
// for money market and some derivatives
// cashflow activities can be determined with field RFHAZUX
( ( Deal.sanlf = '020'
or Deal.sanlf = '510'
or Deal.sanlf = '520'
or Deal.sanlf = '530'
or Deal.sanlf = '540'
or Deal.sanlf = '550'
or Deal.sanlf = '560'
or Deal.sanlf = '570'
or Deal.sanlf = '580'
or Deal.sanlf = '740'
or Deal.sanlf = '770'
or Deal.sanlf = '790'
or Deal.sanlf = '850'
or Deal.sanlf = '860' )
// last active activity
and ( Activity.rfhazu = Deal.rfhazul
// cashflow activity for successor
or ( Activity.rfhazu = SuccActivity.rfhazux
and Activity.saktiv <> '3' )
// cashflow activity for successor-successor
or ( Activity.rfhazu = SuccSuccActivity.rfhazux
and Activity.saktiv <> '3' ) ) )
// for some derivatives
// cashflow activities can be determined with database table AT06 (defining which activity categories are posting relevant)
or ( ( Deal.sanlf = '610'
or Deal.sanlf = '620'
or Deal.sanlf = '630'
or Deal.sanlf = '640'
or Deal.sanlf = '760' )
and ( Activity.rfhazu = Deal.rfhazul
or ( ProcessingCategory.sebene = '1'
and Activity.saktiv <> '3' ) ) )
// for other instruments (securities, fx, some derivatives)
// always only current activity is relevant
or ( ( ( Deal.rantyp = '2' and Deal.sanlf <> '020')
or Deal.sanlf = '600'
or Deal.sanlf = '700'
or Deal.sanlf = '730'
or Deal.sanlf = '750'
or Deal.sanlf = '780' )
and Activity.rfhazu = Deal.rfhazul )
/*+[internal] {
"BASEINFO":
{
"FROM":
[
"AT06",
"VTBFHA",
"VTBFHAZU"
],
"ASSOCIATED":
[],
"BASE":
[],
"ANNO_REF":
[],
"SCALAR_FUNCTION":
[],
"VERSION":0,
"ANNOREF_EVALUATION_ERROR":""
}
}*/
Learn More
- What Is a CDS View in SAP S/4HANA?
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- CDS View Annotations — A Complete Guide
- 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