New Features

Extractor 2.0

New OPD Fetcher is available in Extractor 2.0 enabling data extraction from ERP systems using Glue.
Listcube fetcher for extraction from InfoCubes, MultiProviders, and Composite providers was introduced.
In Process chains, there is a new type for Glue extractions available to quickly differentiate Glue extractors in daily jobs and also streamline settings for the execution.

Glue Settings enables you to set up various settings in Glue. New front-end is available instead of table-based customization used previously. Two different transactions were created: /DVD/GL_SETT for standard settings and /DVD/GL_SETT_EXPERT for expert ones. Please refer to the documentation for more info.

User interface was reworked to provide more user-friendly experience during the configuration of storage.
Extended checks were implemented to enable detailed information about connection status, including IP availability, the status of RFC connections, authentication methods ...

Azure Active Directory authorizations are supported by ADLS Gen2 and Azure Blob storages
HANA Native support for long DB table names

Improvements

Extractor 2.0

Glue request monitor
- Deletion and clean-up functionality for Extractor 2.0 extractions were added to the Glue request monitor. Also, filtering was added to the monitor.
- If you display logs for a job that is still running, standard SAP SM37 logs are shown.
Filtering using custom BADI using $NAME placeholder was added Extractor 2.0.
When creating a Glue table, the Glue consumer can be generated automatically.
You can set default start/end routine code using transaction /DVD/GL_SETT (Glue Settings). It will set corresponding parameters in table /DVD/GL_EXT2_TPD.
In the Glue Extraction process, the currency normalization is not enabled by default.
Deactivation of the Extraction process doesn't delete SAP variants of the process.
In FIFO consumer, you have an option to clean-up the FIFO queue.
CDS Views extraction is available.

General

Using enhancement point, a customer can customize the content of the generated JSON metadata file.

Object Navigator displays Glue objects (and ABAP objects) in a package structure. In case there are too many packages, and you want to add additional granularity to the navigator tree, you can use Folders.

Data Dictionary was crashing after 'Enable update' has been checked and unchecked
You could activate a Glue table with duplicate fields.
RAW fields were removed from Glue tables without notifying the user

InfoCube Extractor was unable to update delta pointer
Variant Generation on Cluster Tables was allowed in GL80 but forbidden in GLUE Workbench
JSON file "Table name" parameter was changed to "TableName"

Extractor 2.0 after copy in object navigator displayed the wrong object.
Extractor 2.0 Filtering didn't work for custom (Z*/Y*) fetchers.
Extractor 2.0 could activate syntactically incorrect reports and eventually dump.
Extraction Process - mapping check for a table with .INCLUDEs returned an error.
The logic of Currency rules was improved.
BEx Query corrections:
- BEx Query extractor returned the wrong results when the structure of formulas was in rows.
- Support for compounded characteristics without master data but with texts used as an attribute was added.
ADSO fetcher was not possible to activate with delta load
Extractor 2.0 Mass Execution - RUNID Exists and Overlapping ranges (type mismatch)
Extractor 2.0 value-based delta was not working for views (M view of IOBJ)

Activation of objects imported from transport was failing without any relevant message
BPL 2.0 import phase on the target system didn't work
Transport of Glue Virtual InfoProvider was not supported
Import of already existing table with meaningful field names terminated on INSERT of duplicate records

Mapping for HANA native extended field names wasn't mapping tables with 16+ char. names
AWS
- Cleanup on S3 didn't work
- S3 Append operation (extraction into a single file) was improved
- Redshift alter table was fixed
- Creation of Glue table from a Redshift table was corrected