(Glue-2008) Release Notes 2008

New Features

Our new mass activation features enable you to perform activate, deactivate, and delete operations over the specified list of Glue objects in bulk.
Regenerate extraction processes instead of activating and deactivating manually, after upgrade of native process extraction logic.

Extractor 2.0 now supports /wiki/spaces/GLUE/pages/1517846614 allowing you to execute the process in parallel.

Data Validation - you can now compare the extracted data to the data stored on external storage right after the extraction in order to verify the data consistency. You can find this option under Glue settings.
Data Streaming – a new feature that enables data streaming from your SAP system through a watchdog background job that schedules the extraction of watched objects in separate jobs.
Automatic adjustments of ADSO structures – if you add a new object to your ADSO you no longer have to adjust the structure of your Glue table manually – this new feature adjusts it automatically.
Read Deleted Entries – You can now read deleted entries with trigger delta using the SAP Table Fetcher.

Google Cloud Storage and BigQuery – you can now connect Google Cloud Storage and BiqQuery as targets in storage management

You can now generate all types of Extractor 2.0 objects in bulk.
If you deactivate an extraction process, the variants created for the process are not deleted.
Extraction monitor displays selection information for DSO and InfoCube extractions.
You can now use customer exits for BEx Query extraction.
You can use date format and time format business functions to format date and time values from technical SAP format into the desired ‘easy to read’ format.
When extracting the data into file storage, you have now an option to customize the files generated by Glue.
In Glue Settings, you can specify CSV and JSON filename patterns. You can also decide if you want to have CSV and JSON extraction metadata generated if no data was transferred during the extraction.

When extracting data using trigger delta, you can specify multiple triggers on a cluster table with the same cluster table header.
You can manage the triggers created by Glue objects with the Trigger Management tool. We have improved the tool to provide you all the relevant information.
If you want to use timestamp delta for data extraction, you can define it either by using a timestamp field from a table or as a combination of date and time fields.

Glue Settings provide you with logging information of all the changes to settings parameters.

When importing the DDIC table with RAW fields, these fields were automatically removed from the Glue table. With the new implementation, the fields are added with empty Data Element, and it is up to you to decide whether you want to remove them or map them to another data type.
Similar to the RAW fields, also fields with DUMMY data elements were automatically removed from the Glue table. It is now possible to import such fields into the Glue table.
It was possible to edit File storage options in an active Glue table. This is no longer allowed because it was a dangerous operation due to possible data inconsistency and problems during the transfer of modified Glue tables using TMS.

Activation of a Glue table was overwriting start/end routines. This was fixed and the routines are kept even after activation and deactivation of an extractor.
The extraction of DSO delta mode was failing if DSO had the “OPERATION” field.
If you created a Glue table, changed the definition of one of the data elements used in that table, and executed the extraction, it ended with an error because of the length of source <> length of the target. This has been handled and a standard error message is displayed.

In the S4 system, it was possible to create SAP fetcher with trigger delta on a proxy object. The actual creation of a trigger would eventually fail during the activation, so this operation is no longer allowed.
It was not possible to delete a Glue fetcher in the saved state.
The authorization RUN_EXT was not checked right after the execution of an extraction. This was corrected and now it is not possible to start the execution without the authorization.
ADSO extraction was executing the deduplication logic (removing duplicate values from a single data load) even if this option was not marked.
Activation of Extraction Process with wrong mapping (wrong target field name) was dumping.
During the currency conversion, the logic was not checking if all the key fields from the reference table were in the source table. This was causing failures in the extraction process.
It was impossible to fully regenerate mapping in the extraction process when there were only direct assignment rules
If you delete a field from a Glue table, it is still present in extraction process mapping. The only way to delete it is to regenerate mapping, but this was not possible when there were only direct assignment rules. This has been remedied and you can regenerate it.

It was not possible to transfer Read Deleted Entries flag of SAP table fetcher using Glue TSM to the target system. This has been remedied and you can transfer all the parameters.
InfoCube and DSO extractor delta was reset after the import of Glue transport with updated versions of extractors. This has been corrected and the delta information is kept after the transport.
"Skip initial full load" flag was reset after reimporting the new version of the InfoCube extractor.
It was not possible to transport a DSO extractor if the FULL delta was used. This has been fixed and it is possible to transfer DSO extractor with such a configuration.

It was not possible to deactivate an active Glue Virtual Provider. This has been fixed and now you can deactivate it.