SAP NetWeaver as Source

Capture

Fivetran HVR allows you to Capture changes from SAP NetWeaver using HVR's AppConnect. This section describes the configuration requirements for capturing changes from SAP NetWeaver location. For the list of supported SAP NetWeaver versions from which HVR can capture changes, see Capture changes from location in Capabilities.

HVR supports capturing changes from SAP NetWeaver only when the underlying database is either Oracle or SAP HANA. The requirements for capturing from NetWeaver is classified based on the underlying database:

• Capture from SAP NetWeaver on HANA
• Capture from SAP NetWeaver on Oracle

SAP columns are non-nullable by default. They will be described as nullable in the hub's repository and thus as nullable in the target. This is valid for the non-key columns. Key columns will remain non-nullable.

SAP Data Types Conversion

Since v6.1.0/7

This option enables conversion/mapping of SAP specific data types (available in SAP dictionary meta-data) in source location to corresponding data type in the target location. The SAP specific data type will be localized with the source DB's data type and then mapped to HVR's Repository data type. For example, if you have an SAP system with NetWeaver driver, the DATS data type will be mapped to HVR Repository type nvarchar / date.

This feature is supported for the following SAP specific data types:

• DATS

If the SAP Data Types Conversion option is NOT selected, SAP specific data types are mapped to various other HVR Repositry data types. For more information, see Data Type Mapping for SAP NetWeaver (or SAP dictionary).

If the SAP Data Types Conversion option is selected during location creation, HVR will automatically define action TableProperties with parameters CoerceErrorPolicy and CoerceErrorType.

While creating an SAP NetWeaver location, the SAP Data Types Conversion option is selected/enabled by default. To enable SAP data type conversion for an existing location, select the SAP Data Types Conversion option by editing the location's source and target properties and then manually define action TableProperties with parameters CoerceErrorPolicy and CoerceErrorType.

Intermediate Directory

This option in the HVR UI allows you to specify a directory path for storing intermediate (temporary) files generated during Compare. These files are created during both "direct file compare" and "online compare" operations.

Using an intermediate directory can enhance performance by ensuring that temporary files are stored in a location optimized for the system's data processing needs.

This setting is particularly relevant for target file locations, as it determines where the intermediate files are placed during the Compare operation. If this option is not enabled, the intermediate files are stored by default in the integratedir/_hvr_intermediate directory, where integratedir is the replication DIRECTORY (File_Path) defined for the target file location.

This option is equivalent to the location property Intermediate_Directory.

Intermediate Directory is Local

This option in HVR UI specifies that the Intermediate Directory will be created on the local drive of the file location's server.

This setting is crucial for optimizing performance, as it reduces network latency and avoids potential permission issues associated with remote storage. By storing intermediate files locally, HVR can process data more efficiently, taking advantage of the speed and reliability of local storage.

This option is particularly beneficial when the HVR Agent has access to ample local storage, enabling it to handle large data volumes without relying on networked storage solutions.

This option is equivalent to the location property Intermediate_Directory_Is_Local.

Compare and Refresh from Oracle and HANA

HVR allows you to perform only Compare and Refresh from SAP NetWeaver (without using Capture). Any specific database (Oracle or HANA) grants are not required for performing only Compare and Refresh from NetWeaver on Oracle or HANA.