New Features
BEx Query fetcher (BICS)
The BEx Query Fetcher allows you to use BEx Query as a data source using BI Consumer Services. This logic provides new features and overcomes the limitations of the previous implementation.
The fetcher allows you to change the navigational state of a query with which it will be executed. The functionality is similar to the drill-down of free characteristics in Query Monitor (transaction RSRT). If you want to change the default navigational state of a query, you can drag and drop query elements between three screens - Rows, Columns, Free Characteristics.
Glue Cleanup Watchdog
The Cleanup Watchdog is a tool for managing periodically running background jobs that cleans up old Glue metadata that is no longer needed. Using the tool you can specify the periodicity of individual scans and criteria to identify the data to cleanup.
Storage Management
Snowflake – you can now connect Snowflake as a target in storage management
Improvements
Mass Execution
For the mass extraction of BEx Query data, you can use the Combined data partitioning type which allows you to specify custom ABAP reports for the definition of data splits.
Extractors
FIFO extraction enables you to access data from the FIFO cluster table from another SAP system using an RFC connection.
You can change the parameters of the SAP table fetcher (e.g. selection fields or load type) without losing current delta information.
SAP Table Fetcher also supports trigger delta for Database Views. For this scenario, you need to specify the trigger table name which is part of the view.The Glue request monitor :
Displays the extraction jobs that were scheduled for a particular date and time with status Pending.
Enables you to restart all failed requests of mass extraction.
Data Browser
With the new version, you can also display files created during the extraction for Azure Data Lake Storage Ge2.
REST API
Glue REST API endpoints were renamed to be more meaningful.
An endpoint was created to provide the list of ADSO objects in an SAP system.
REST API can be used to generate Glue FIFO extraction objects.
Object Navigator
Object Navigator tree now displays the status of each individual Glue object.
You can create a Glue table from a table existing in target storage directly from the Object Navigator, and you can also activate or delete a selection of multiple Glue objects.
Transport Management
It is possible to modify the File storage options of a Glue table. With the new implementation, it is no longer required to deactivate the table. This means that the update of the existing Glue table settings using Transport Management is also supported.
In Transport Management, logging was added to enable tracking the execution of Cleanup and Cleanup All functions.
Fixes
Data Dictionary
When creating a Glue table with '/' in the table name on AWS S3 storage, subfolders were created.
Data Browser
In Glue Data Browser, you couldn’t specify a selection with ranges (e.g. between, exclude, GT, LT....) nor use the integer fields for filtering. This has been corrected and now you can use the full functionality of the select options.
Extractor 2.0
FIFO extraction procedure was improved to be more robust and to be able to handle various error situations.
ListCube fetcher has been improved to support filtering for field-based ADSOs.
CDC
It was possible to start the trigger watchdog even without saved settings, which lead to unexpected behavior. This has been improved and the logic is now consistent.
Trigger management cockpit was prompting the user to save the changes when switching between the tabs even if nothing was changed.
Glue Monitor
If an extraction process terminated with a dump, the status of the request was displayed as running. This has been corrected and the correct status is now displayed.
The selection screen of the Glue monitor didn’t provide F4 help. This has been implemented to improve user experience.
When deleting a request of a running extraction, data was deleted, extraction job terminated, but in the monitor, the request remained with status failed. Now we delete also the corresponding metadata and the extraction job request is removed from the monitor.
Mass operations
Even though the regeneration of Glue objects via Glue Mass Regeneration (transaction /dvd/gl_mass_regen) failed, the application logs stated that it ended successfully. This has been corrected and the correct logs are now created.
If a Glue object was created using Mass Generation functionality, JSON files were generated incorrectly.
Glue Object Generation variants were saving incomplete collection of parameters. With the correction of the logic, the complete information is stored.
It was possible to generate a Glue table without the defined Container Name. This is no longer possible because the container is a mandatory parameter.
Transport Management
Transport Management was not working for FIFO fetchers. This has been corrected and now you can transfer the fetchers without any problems.
Glue REST API
Glue REST API schedule endpoint was returning GLREQUEST = '0' when the replication job was put into a queue and not executed immediately.
In FIFO extraction process, the schedule API failed to trigger the second process of the chain.