SAP HANA DWF NDSO editor with SP 04
SAP HANA data warehousing foundation (DWF) enables efficient data management and distribution across complex SAP HANA landscapes. Customers can optimize the memory footprint of data and streamline administration and development, thereby reducing TCO and at the same time supporting SAP HANA administrators and data warehouse designers.
With SAP HANA DWF SP 04a new Native DataStore Object (NDSO) editor has been introduced. It’s based on flowgraph and the generation-based approach for NDSO
To work with the new NDSO editor open the WebIDE. After creating a DWF Template project create an NDSO within the DWF module by selection of NDSO in the context menu (right-click on the DWF module > New > NDSO).
There are multiple advantages as listed below:
- Simplify the generated flowgraphs, as the rendering of generated graphs (especially in some cases when connecting multiple NDSOs) was causing issues.
- Easier adjustment of existing flowgraphs is now possible because a new procedure is generated automatically and user needs simply to enhance the connection between source table and procedure (for example in case of additional fields). Adjusting the old flowgraph was difficult and error-prone in this case, so the only solution was to re-create the new flowgraph.
- Easier bug fixing and enhancement – In case of a bug in flowgraph generation code you will have to re-create all flowgraphs manually, while currently, it is possible to re-generate the database artifacts on DWF project level and the existing flowgraphs will still be valid.
- Easier debugging – Debugging a flowgraph is more difficult than SQL procedures (ex. breakpoints can be used).
- CAP CDS enablement: Core Data & Services (CDS) is the backbone of the Application Programming Model. CDS is in maintenance mode. Therefore we need to switch to CAP CDS. In this case, the existing DWF NDSO files can be used to generate the new design-time artifacts.
- Generate DB artifacts: In addition, the CDS successor will not support annotations, which means that we also need to generate additional files to maintain the NDSO registry.
- Maintenance difficulties: Moreover, the behavior for certain flowgraph nodes is modified in the background without being transparent to the end user.
There are known limitations, such as:
- Several transform nodes are not supported such as RowGeneration, DateGeneration, Case, Lookup, MapOperation, Pivot, Unpivot, Table Comparison, Data Mask, Cleanse, Geocode Match
- No Partitioning: Partitioning is typically used to split loads into smaller chunks, to load several parts in parallel, or in smaller sequential loads to reduce source database issues or HANA performance issues.
- No ODP Support: This means that you cannot load from any ODP source unless the data set is very small. Larger data sets need the ODP framework for splitting up data sets in smaller chunks. If they are not split up, the ABAP source system will likely run into memory errors. Also, without ODP support, you cannot set a flowgraph to load ODP sources as delta’s
Find support information about SAP HANA Data Warehousing Foundation faster and easier on SAP’s Help Portal. It provides an overview of product information such as installation, upgrading, development, and the latest features for each version.
Check out the SAP HANA Data Warehousing Foundation Community Page containing valuable resources to fast-track your knowledge with news and technical information as well as a rich support section designed to help you get the highest quality answers quickly and easily directly from SAP experts.