New Features

Extractor 2.0 mass execution allows you to execute the process in parallel. Mass execution splits data into multiple portions which are scheduled and executed as separate tasks.
Extractor Request Monitor that serves as a tool for monitoring ongoing or past extraction processes was introduced.

BPL 2.0 provides improved functionality for creating, modifying and using predefined business objects. Business objects are groups of SAP tables that represent SAP ERP objects (for example Plant, Material, Vendor). For more information, refer to Business Objects documentation.

Google
Support of Google Cloud Storage (file storage) and Google BigQuery storage.
The instructions for setup of the connections are available on this link.
Azure Data Lake Storage Gen 2
New storage from Microsoft Azure is available. See instructions for more information.
SM_SETUP2 - new version of Storage Management, used for setup and maintenance of connection to HDFS and Hive/Impala.

Improvements

Extractor 1.0
- Extractor monitor contains information about selections of a request
- Object generation utility generates trigger routines
- BW extractor
  - InfoCube Mass Extraction allows filtering based on Request ID
  - Support of BAdI selection for InfoCube and DSO extractors
  - Automatic adjustments of DSO structure/extractor objects is supported
- CSV File extractor
  - Added option to specify file encoding in CSV extractor/variant
Extractor 2.0
- When running extractor 2.0 in preview mode, it is not visible in the request monitor
- Query extract supports automatic adjustments of selection criteria
- Mass Execution supports time based splitting for fiscal periods and fiscal years

Added parameter "Enable update" for AWS Redshift
Added option to not overwrite generated jaas file in Hadoop JDBC java connection
Datavard JCO management tool can automatically create directories on Windows SAP systems
Improved logging information during storage creation/storage check

Data Dictionary doesn't suggest fields for meaningful values if there is no content available
Deactivation of a table was not possible if a job dumped
It is possible to automatically insert GLREQUEST field into Glue table
Added meaningful description of fields imported from a BEx Query
Deletion of inactive Glue table created in Binary storage didn't delete metadata

Improved error message if user doesn't have permissions to create trigger tables
Improved error message when executing job without permissions
Triggers were not working on tables with .INCLUDE in a table key
Currency performance optimization was not working with meaningful fields

Usability improvements:
- While renaming of Extractor 2.0 object, a user is warned if it will deactivate other object
- When copying an object, it is open in the sub-screen
- Extractor monitor displays a Load type of an extraction process
Extractor 2.0 mass execution initial job fills in a job-log in SM37
It was not possible to reactivate Extractor 2.0 if the report didn't exist
Currency normalization was not working with the same table as reference
After copy in object navigator, incorrect object was displayed
It was possible to delete extraction process even though other user was editing it
Selection filter did not preserve field order
Monitor is not cleared after extraction process deletion

JAR files for APACHE_HIVE execution engine were loaded in non-deterministic way
AWS Redshift storage wasn't working with the latest JDBC driver
Alter Table was not working on AWS Redshift
Azure Databricks storage didn't support creation of Glue table from existing Databricks table