Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE

SAP Application (DB) Source Endpoint changed how the Metadata is processed with Replicate

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Bill_Steinagle
Support
Support

SAP Application (DB) Source Endpoint changed how the Metadata is processed with Replicate

Last Update:

Jul 6, 2022 3:03:06 PM

Updated By:

Bill_Steinagle

Created date:

Jul 6, 2022 3:03:06 PM

In Qlik Replicate 2021.5 (SP04), 2021.11 and 2022.5 the Source Endpoint SAP Application (DB) changed how the Metadata for character based columns is processed during Load and CDC processing of SAP Tables. 

Environment

  • Replicate 2021.5 SP04
  • Replicate 2021.11
  • Replicate 2022.5

Cause

Prior to the versions listed above Replicate used data length semantics to process character based columns. Upgrading to any of the listed versions automatically changes this processing of these columns to character length semantics. This can be seen on the Target for Tables that have been reloaded. For example the column MANDT is defined as a VARCHAR(9) on Targets with data length semantics. The same column would appear as a VARCHAR(3) with character length semantics. 

Resolution 

With Replicate 2021.11 SP06 and 2022.5 SP01 data length semantics has been restored as the default for character based columns when using the SAP Application (DB) Endpoint. If your Tables are reloaded with either of these versions they will automatically be defined with data length semantics. In addition there is a new Internal Parameter you can set on the SAP Application (DB) Source Endpoint to continue with character length semantics.

Internal Parameter: useLengthUnitsInSAPDB

 Bill_Steinagle_0-1657019750815.png

 

 

Contributors
Version history
Last update:
‎2022-07-06 03:03 PM
Updated by: