A_FundHierNode
Fund Hierarchy Node
A_FundHierNode 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 13 fields with key fields FinancialManagementArea, FundHierarchy, HierarchyNode, ValidityEndDate. It has 1 association to related views. It is exposed through 1 OData service (API_FUNDHIERARCHY). Part of development package PSM_FM_API.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| I_FundHierarchyNode | I_FundHierarchyNode | from |
Associations (1)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..*] | A_FundHierNodeText | _FundHierarchyNodeText | $projection.FinancialManagementArea = _FundHierarchyNodeText.FinancialManagementArea and $projection.FundHierarchy = _FundHierarchyNodeText.FundHierarchy and $projection.ValidityEndDate = _FundHierarchyNodeText.ValidityEndDate and $projection.HierarchyNode = _FundHierarchyNodeText.HierarchyNode |
Annotations (13)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | AFUNDHN | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AbapCatalog.preserveKey | true | view | |
| AccessControl.authorizationCheck | #CHECK | 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_FundHierNode_Type | view | |
| Metadata.ignorePropagatedAnnotations | true | view | |
| EndUserText.label | Fund Hierarchy Node | view |
OData Services (1)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| API_FUNDHIERARCHY | API_FUNDHIERARCHY | V2 | C2 | C1 |
Fields (13)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | FinancialManagementArea | I_FundHierarchyNode | FinancialManagementArea | FM Area |
| KEY | FundHierarchy | I_FundHierarchyNode | FundHierarchy | |
| KEY | HierarchyNode | I_FundHierarchyNode | HierarchyNode | Node |
| KEY | ValidityEndDate | I_FundHierarchyNode | ValidityEndDate | ValidTo |
| ParentNode | I_FundHierarchyNode | ParentNode | Parent Node | |
| HierarchyVersion | I_FundHierarchyNode | HierarchyVersion | Version | |
| ValidityStartDate | I_FundHierarchyNode | ValidityStartDate | Validity Start Date | |
| Fund | I_FundHierarchyNode | Fund | Sender Fund | |
| HierarchyNodeSequence | I_FundHierarchyNode | HierarchyNodeSequence | Sequence Number | |
| HierarchyNodeLevel | I_FundHierarchyNode | HierarchyNodeLevel | Hierarchy Node Level | |
| NodeType | I_FundHierarchyNode | NodeType | Object Type | |
| _FundHierarchy | _FundHierarchy | |||
| _FundHierarchyNodeText | _FundHierarchyNodeText |
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 A_FundHierNode.
-- 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 A_FundHierNode AS
SELECT
I_FundHierarchyNode.FinancialManagementArea AS FinancialManagementArea,
I_FundHierarchyNode.FundHierarchy AS FundHierarchy,
I_FundHierarchyNode.HierarchyNode AS HierarchyNode,
I_FundHierarchyNode.ValidityEndDate AS ValidityEndDate,
I_FundHierarchyNode.ParentNode AS ParentNode,
I_FundHierarchyNode.HierarchyVersion AS HierarchyVersion,
I_FundHierarchyNode.ValidityStartDate AS ValidityStartDate,
I_FundHierarchyNode.Fund AS Fund,
I_FundHierarchyNode.HierarchyNodeSequence AS HierarchyNodeSequence,
I_FundHierarchyNode.HierarchyNodeLevel AS HierarchyNodeLevel,
I_FundHierarchyNode.NodeType AS NodeType
FROM I_FundHierarchyNode
LEFT OUTER JOIN A_FundHierNodeText AS _FundHierarchyNodeText ON FinancialManagementArea = _FundHierarchyNodeText.FinancialManagementArea AND FundHierarchy = _FundHierarchyNodeText.FundHierarchy AND ValidityEndDate = _FundHierarchyNodeText.ValidityEndDate AND HierarchyNode = _FundHierarchyNodeText.HierarchyNode -- association [0..*]
;
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
- 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