A_FundCoreHierNode
Fund Hierarchy Node
A_FundCoreHierNode is a Composite CDS View that provides data about "Fund Hierarchy Node" in SAP S/4HANA. It reads from 1 data source (I_FundHierarchyNode) and exposes 14 fields with key fields FundHierarchy, HierarchyNode, ValidityEndDate. It has 1 association to related views.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| I_FundHierarchyNode | I_FundHierarchyNode | from |
Associations (1)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..*] | A_FundCoreHierarchyNodeText | _FundCoreHierarchyNodeText | $projection.FundHierarchy = _FundCoreHierarchyNodeText.FundHierarchy and $projection.ValidityEndDate = _FundCoreHierarchyNodeText.ValidityEndDate and $projection.HierarchyNode = _FundCoreHierarchyNodeText.HierarchyNode |
Annotations (13)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | AFUNDCOREHRYNODE | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AbapCatalog.preserveKey | true | view | |
| AccessControl.authorizationCheck | #CHECK | view | |
| EndUserText.label | Fund Hierarchy Node | view | |
| VDM.viewType | #COMPOSITE | view | |
| VDM.lifecycle.contract.type | #PUBLIC_REMOTE_API | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| ObjectModel.usageType.dataClass | #MASTER | view | |
| ObjectModel.usageType.serviceQuality | #A | view | |
| ObjectModel.usageType.sizeCategory | #XL | view | |
| OData.entityType.name | A_FundCoreHierNode_Type | view | |
| Metadata.ignorePropagatedAnnotations | true | view |
Fields (14)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | FundHierarchy | I_FundHierarchyNode | FundHierarchy | |
| KEY | HierarchyNode | I_FundHierarchyNode | HierarchyNode | |
| KEY | ValidityEndDate | I_FundHierarchyNode | ValidityEndDate | |
| ParentNode | I_FundHierarchyNode | ParentNode | ||
| HierarchyVersion | I_FundHierarchyNode | HierarchyVersion | ||
| ValidityStartDate | I_FundHierarchyNode | ValidityStartDate | ||
| FinancialManagementArea | I_FundHierarchyNode | FinancialManagementArea | ||
| Fund | I_FundHierarchyNode | Fund | ||
| HierarchyNodeSequence | I_FundHierarchyNode | HierarchyNodeSequence | ||
| HierarchyNodeLevel | I_FundHierarchyNode | HierarchyNodeLevel | ||
| NodeType | I_FundHierarchyNode | NodeType | ||
| HierarchyNodeVal | I_FundHierarchyNode | HierarchyNodeVal | ||
| _FundCoreHierarchy | _FundCoreHierarchy | |||
| _FundCoreHierarchyNodeText | _FundCoreHierarchyNodeText |
@AbapCatalog: {
sqlViewName: 'AFUNDCOREHRYNODE',
compiler.compareFilter: true,
preserveKey: true
}
@AccessControl.authorizationCheck: #CHECK
@EndUserText.label: 'Fund Hierarchy Node'
@VDM.viewType:#COMPOSITE
@VDM.lifecycle.contract.type: #PUBLIC_REMOTE_API
@ClientHandling.algorithm: #SESSION_VARIABLE
@ObjectModel:{
usageType: {
dataClass: #MASTER,
serviceQuality: #A,
sizeCategory: #XL
}
}
@OData.entityType.name: 'A_FundCoreHierNode_Type'
@Metadata.ignorePropagatedAnnotations:true
define view A_FundCoreHierNode
as select from I_FundHierarchyNode
association [0..*] to A_FundCoreHierarchyNodeText as _FundCoreHierarchyNodeText on $projection.FundHierarchy = _FundCoreHierarchyNodeText.FundHierarchy
and $projection.ValidityEndDate = _FundCoreHierarchyNodeText.ValidityEndDate
and $projection.HierarchyNode = _FundCoreHierarchyNodeText.HierarchyNode
association to parent A_FundCoreHierarchy as _FundCoreHierarchy on $projection.FundHierarchy = _FundCoreHierarchy.FundHierarchy
and $projection.ValidityEndDate = _FundCoreHierarchy.ValidityEndDate
{
key I_FundHierarchyNode.FundHierarchy,
key I_FundHierarchyNode.HierarchyNode,
key I_FundHierarchyNode.ValidityEndDate,
I_FundHierarchyNode.ParentNode,
I_FundHierarchyNode.HierarchyVersion,
I_FundHierarchyNode.ValidityStartDate,
I_FundHierarchyNode.FinancialManagementArea,
I_FundHierarchyNode.Fund,
I_FundHierarchyNode.HierarchyNodeSequence,
I_FundHierarchyNode.HierarchyNodeLevel,
I_FundHierarchyNode.NodeType,
I_FundHierarchyNode.HierarchyNodeVal,
/* Associations */
_FundCoreHierarchy,
_FundCoreHierarchyNodeText
}
/*+[internal] {
"BASEINFO":
{
"FROM":
[
"I_FUNDHIERARCHYNODE"
],
"ASSOCIATED":
[
"A_FUNDCOREHIERARCHY",
"A_FUNDCOREHIERARCHYNODETEXT"
],
"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