I_BillingDocTypeHierNode

DDL: I_BILLINGDOCTYPEHIERNODE Type: view_entity BASIC Package: FINS_FIS_FICO

Billing Document Type Hierarchy Node

I_BillingDocTypeHierNode (Basic)

Package: Explore, extend and adapt the SAP S/4HANA Public Edition with built-in and side-by-side extension capabilities.

BillingDocTypeHierarchyNode · Accounting and Financial Close

I_BillingDocTypeHierNode is a Basic CDS View that provides data about "Billing Document Type Hierarchy Node" in SAP S/4HANA. It reads from 1 data source (hrrp_node_n) and exposes 13 fields with key fields BillingDocumentTypeHierarchy, HierarchyNode, ValidityEndDate. It has 3 associations to related views. Part of development package FINS_FIS_FICO.

SAP Help Documentation

CategoryCDS Views for Master Data
Purpose
This CDS view is designed to represent a hierarchical structure of billing document types. It organizes billing document types into a parent-child hierarchy, allowing users to understand the relationships and structure of different billing document types within the system. The view also supports data extraction and provides associations to related text and document type entities for additional context and information. This CDS view provides the data to answer the following business questions: What is the hierarchical structure of billing document types in the system? How are different billing document types related to each other in terms of parent-child relationships? What are the validity periods for each node in the billing document type hierarchy? What are the sequence and level of each node within the hierarchy? What additional information or text is associated with each billing document type hierarchy node? How can I filter and view specific billing document types based on their hierarchy and validity dates? To help you decide which CDS view to use for your purposes, SAP has introduced the annotation ObjectModel.supportedCapabilities that indicates the most appropriate use cases for each CDS view. To find out what use cases are best supported by this CDS view, access the entry of the CDS view in the View Browser app and find the values for this annotation under the Annotation tab. For more information, see Supported Capabilities for CDS Views .

Prerequisites
Authorizations Users who want to use this CDS view must have a role with the following restriction types set to read access: Restriction Type ID Restriction Type HRYTYPE_HRYID_OH Hierarchy Type/ID for Overhead Accounting HRYTYPE_HRYID_LI Hierarchy Type/ID for Liquidity Item HRYTYPE_HRYID_BS Hierarchy Type/ID for Budget Specialist HRYTYPE_HRYID_SA Hierarchy Type/ID for Sales Accounting HRYTYPE_HRYID Hierarchy Type/ID HRYTYPE_HRYID_BAM Hierarchy Type/ID for Bank Account Management HRYTYPE_HRYID_CS Hierarchy Type/ID for Consolidation HRYTYPE_HRYID_DV Hierarchy Type/ID for Profit Center Accounting HRYTYPE_HRYID_GL Hierarchy Type/ID for General Ledger Accounting HRYTYPE_HRYID_GM Hierarchy Type/ID for Grants Management HRYTYPE_HRYID_FA Hierarchy Type/ID for Fund Accounting HRYTYPE_HRYID_FFS Hierarchy Type/ID for Financial Services Enhancements HRYTYPE_HRYID_PM Hierarchy Type/ID for Master Data - Product Master HRYTYPE_HRYID_CIT Hierarchy Type/ID for Corporate Income Tax HRYTYPE_HRYID_CS_AND_REF Hierarchy Type/ID for Consolidation including references These restriction types are edited in the Maintain Business Roles app.

Structure
Fields used for Filtering Field Name Label BillingDocumentTypeHierarchy Billing Document Type Hierarchy ID ValidityEndDate Validity End Date Important Fields Important fields in this view include the following: Field Name Description HIERARCHYNODE Node PARENTNODE Par. Node HIERARCHYNODEVAL Value BILLINGDOCUMENTTYPE Billing Type BILLINGDOCUMENTTYPEHIERARCHY Billing Document Type Hierarchy ID NODETYPE Node Type VALIDITYENDDATE Validity End Date VALIDITYSTARTDATE Validity Start Date HIERARCHYNODELEVEL Hierarchy Level HIERARCHYNODESEQUENCE Sequence Number

Data Extraction
This CDS view is enabled for data extraction in full mode.

View on SAP Help Portal →

SAP API Hub

CategoryBasic
StateC1
Line of BusinessAccounting and Financial Close
Application ComponentFI-GL-IS-2CL
CapabilitiesData Source for Data Extraction,Data Source for Defining CDS Entities,Association Target for Defining CDS Entities,Data Source for Hierarchies in Analytics
Extensible (Key User)No
Extensible (Developer)No
Release State (Key User)Released
Release State (Developer)Released
PackageAccounting and Financial Close for SAP S/4HANA Cloud Public Edition
Description <p>This CDS view is designed to represent a hierarchical structure of billing document types. It organizes billing document types into a parent-child hierarchy, allowing users to understand the relationships and structure of different billing document types within the system. The view also supports data extraction and provides associations to related text and document type entities for additional context and information.</p> <p>This CDS view provides the data to answer the following business questions:</p> <ul> <li><p>What is the hierarchical structure of billing document types in the system?</p></li> <li><p>How are different billing document types related to each other in terms of parent-child relationships?</p></li> <li><p>What are the validity periods for each node in the billing document type hierarchy?</p></li> <li><p>What are the sequence and level of each node within the hierarchy?</p></li> <li><p>What additional information or text is associated with each billing document type hierarchy node?</p></li> <li><p>How can I filter and view specific billing document types based on their hierarchy and validity dates?</p></li> </ul> <p>To help you decide which CDS view to use for your purposes, SAP has introduced the annotation ObjectModel.supportedCapabilities that indicates the most appropriate use cases for each CDS view. To find out what use cases are best supported by this CDS view, access the entry of the CDS view in the View Browser app and find the values for this annotation under the Annotation tab. For more information, see Supported Capabilities for CDS Views.</p>

Documentation

Data Sources (1)

SourceAliasJoin Type
hrrp_node_n hrrp_node_n from

Associations (3)

CardinalityTargetAliasCondition
[0..*] I_BillingDocTypeHierNodeTxt _Text $projection.BillingDocumentTypeHierarchy = _Text.BillingDocumentTypeHierarchy and $projection.HierarchyNode = _Text.HierarchyNode and $projection.BillingDocumentType = ''
[0..1] I_BillingDocumentType _BillingDocumentType $projection.BillingDocumentType = _BillingDocumentType.BillingDocumentType
[1..1] I_BillingDocumentTypeHier _Hierarchy $projection.BillingDocumentTypeHierarchy = _Hierarchy.BillingDocumentTypeHierarchy and $projection.ValidityEndDate = _Hierarchy.ValidityEndDate

Annotations (12)

NameValueLevelField
AccessControl.authorizationCheck #MANDATORY view
EndUserText.label Billing Document Type Hierarchy Node view
Metadata.ignorePropagatedAnnotations true view
ObjectModel.usageType.dataClass #MASTER view
ObjectModel.usageType.serviceQuality #A view
ObjectModel.usageType.sizeCategory #L view
ObjectModel.dataCategory #HIERARCHY view
VDM.viewType #BASIC view
Analytics.dataExtraction.enabled true view
ObjectModel.representativeKey HierarchyNode view
ObjectModel.sapObjectNodeType.name BillingDocTypeHierarchyNode view
ObjectModel.modelingPattern #ANALYTICAL_PARENT_CHILD_HIERARCHY_NODE view

Fields (13)

KeyFieldSource TableSource FieldDescription
KEY BillingDocumentTypeHierarchy Billing Document Type Hierarchy ID
KEY HierarchyNode hrrp_node_n hrynode Hierarchy node
KEY ValidityEndDate Validity End Date
ValidityStartDate Validity Start Date
ParentNode hrrp_node_n parnode Hierarchy parent node
BillingDocumentType hrrp_node_n fkart Ship. cost type
HierarchyNodeSequence hrrp_node_n hryseqnbr Hierarchy Sequence Number
HierarchyNodeLevel hrrp_node_n hrylevel Hierarchy Level
NodeType hrrp_node_n nodetype Hierarchy node type
HierarchyNodeVal hrrp_node_n nodevalue Node value
_Text _Text
_BillingDocumentType _BillingDocumentType
_Hierarchy _Hierarchy

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_BillingDocTypeHierNode.
-- 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_BillingDocTypeHierNode AS
SELECT
  cast(hrrp_node_n.hryid as fis_hryid_billingdoctype preserving type ) AS BillingDocumentTypeHierarchy,
  hrrp_node_n.hrynode AS HierarchyNode,
  cast(hrrp_node_n.hryvalto as fis_datbi preserving type ) AS ValidityEndDate,
  cast(hrrp_node_n.hryvalfrom as fis_datab preserving type ) AS ValidityStartDate,
  hrrp_node_n.parnode AS ParentNode,
  hrrp_node_n.fkart AS BillingDocumentType,
  hrrp_node_n.hryseqnbr AS HierarchyNodeSequence,
  hrrp_node_n.hrylevel AS HierarchyNodeLevel,
  hrrp_node_n.nodetype AS NodeType,
  hrrp_node_n.nodevalue AS HierarchyNodeVal
FROM hrrp_node_n
LEFT OUTER JOIN I_BillingDocTypeHierNodeTxt AS _Text ON BillingDocumentTypeHierarchy = _Text.BillingDocumentTypeHierarchy AND HierarchyNode = _Text.HierarchyNode AND BillingDocumentType = ''  -- association [0..*]
LEFT OUTER JOIN I_BillingDocumentType AS _BillingDocumentType ON BillingDocumentType = _BillingDocumentType.BillingDocumentType  -- association [0..1]
LEFT OUTER JOIN I_BillingDocumentTypeHier AS _Hierarchy ON BillingDocumentTypeHierarchy = _Hierarchy.BillingDocumentTypeHierarchy AND ValidityEndDate = _Hierarchy.ValidityEndDate  -- association [1..1]
;