SAP has released the version 2024.4 of SAP Datasphere on Feb 13, 2024. Your SAP Datasphere tenants have been updated probably even before Feb 13, 2024.
1 The new monitoring view SPACE_USERS_V_EXT is deployed in the DWC_GLOBAL schema and tracks information about the user types. Monitoring Tasks, Logs and Schedules With Dedicated Monitoring Views
There are 3 fields in SPACE_USERS_V_EXT view in DWC_GLOBAL.
1 The Remote Queries monitor have been enhanced with additional columns, which provide additional information regarding used sources and runtimes. Monitoring Remote Queries
The Remote Queries monitor only shows the last 100 statements and provides many columns like Connection (Business Name or Technical Name), Start Time, End Time, Remote Statement Duration, Rows, Status, etc.
2 When you persist view data that is coming from different spaces, you can display the information of the data provenance by spaces clicking in the View Details in the log. From this View Details, you can navigate to the Remote Queries monitor and check the statement details.
The persisting views is a powerful feature, though it needs to be used carefully and efficiently. It’s a matter of great data modeling / design! “Data coming from different spaces” means that we are using shared objects from various spaces in the views and then we are persisting. So View Details and Remote Queries will show us how all these coming together. I’d like to try it sometime later.
3 You can change the run mode for a transformation flow and choose between performance and memory consumption. Change the Run Mode for a Transformation Flow
Performance vs Memory. It’s a never-ending dilemma! Let’s be clear! It’s a having or seeming to have no end and usually undesirable or unpleasant choice! Choosing one over other meaning pros & cons, gaining & sacrifice, benefit & cost! Technically speaking, right, memory or disk!
One more thing about Transformation Flows that are great additions like we remember our Transformation Flows in BW world! But it must be pointed out that you’ve got to use the Transformations Flows carefully and resourcefully. Don’t overuse them! Don’t move data from here and there!
4 From the Views monitor, in the details screen of a data persistence view run, you can change the run mode to choose between performance and memory consumption depending on your needs. Data Persistence and Processing Mode
It’s same about persisting views. You run the view and get the result but where you are going to save the result. Here two choices: Performance-Optimized (Recommended) and Memory-Optimized. Make sure memory comes with a cost, and you need a enough disk space if you go with the second choice. Monitor Disk Volume comes in handy.
1 In addition to Remote Table Replication, View Persistency, Intelligent Lookup, Data Flow, and Transformation Flow tasks, you can now also nest other task chains within a task chain.
“nest other task chains within a task chain” sounds very great! You can do many things with task chains. Group multiple tasks into a task chain and run them manually once, or periodically, through a schedule. Create linear task chains in which one task is run after another. Nest other task chains within a task chain. Create task chains in which individual tasks are run in parallel and successful continuation of the entire task chain run. It’s all up to your creativity and designer / architect mindset!
2 You can now preview data for ABAP CDS views and SAP Landscape Transformation Replication Server objects if your system meets the requirements, Creating a Data Flow:
You can click to preview data of the selected operator then the Data Preview section is displayed. You can’t perform data preview on the transformation operators. That’s very handy feature during the data flow developments.
3 You can define default values for each remote table parameter. Review and Edit Imported Table Properties
If your remote table consumes parameterized HANA SQL views the parameters are displayed with their properties. You can define a default value for the parameters. That’s great! You should have always default option for the parameters to avoid overwhelming of the parameters.
1 You can now create data access controls in which criteria are defined as operator and value pairs. Each user can only see the records that fulfill the operator-value pairs she is authorized for in the permissions entity, including support for complex AND and OR combinations. Create an “Operator and Values” Data Access Control
It must be a great relief to be able to use operators like AND and OR combinations and all operators like EQ, NE, GT, LT, CP, etc.
2 You can now create data access controls in which criteria are defined as hierarchy values. Each user can only see the records that match the hierarchy values she is authorized for in the permissions entity, along with any of their descendants. Create a “Hierarchy” Data Access Control
I can’t imagine the benefits of this new feature in especially Finance but also other lines of businesses.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
7 | |
5 | |
4 | |
4 | |
4 | |
4 | |
3 | |
3 | |
3 |