Release Notes - SAP obtain the latest version of documentation including the most up-to-date version...

PUBLIC

SAP Data ServicesDocument Version: 4.2 Support Package 6 (14.2.6.0) – 2016-02-17

Release Notes

Content

1 About SAP Data Services 4.2 Support Package 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31.1 SAP information resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

2 Compatibility update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

3 Restrictions update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

4 Product dependencies update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

5 Deprecated functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

6 Installation and upgrade considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

7 Known issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

8 Fixed issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .268.1 Issues fixed in support packs and previous patches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268.2 Issues fixed in this release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2P U B L I C© 2016 SAP SE or an SAP affiliate company. All rights reserved.

Release NotesContent

1 About SAP Data Services 4.2 Support Package 6

Welcome to SAP Data Services 4.2 SP6. SAP Data Services delivers a single enterprise-class solution for data integration, data quality, data profiling, and text data processing that allows you to integrate, transform, improve, and deliver trusted data to critical business processes. It provides development user interfaces (Designer and Workbench), metadata repository, data connectivity layer, run-time environment, and management console—enabling IT organizations to lower total cost of ownership and accelerate time to value. With SAP Data Services, IT organizations can maximize operational efficiency with a single solution to improve data quality and gain access to heterogeneous sources and applications.

Documentation

To obtain the latest version of documentation including the most up-to-date version of these Release Notes, visit the SAP Help Portal at (http://help.sap.com/bods42/) and follow the appropriate product guide links.

You can also access the latest information, including additional installation and configuration troubleshooting, pertaining to the Data Services 4.2 SP6 release by reading SAP Note 1530081 on the SAP Service Marketplace.

Before you install

Before installing the software, read this entire document. It contains important information about this product release including installation notes, details regarding known issues, and important information for existing customers.

For a new or update installation, follow the instructions in your Installation Guide for Windows or Installation Guide for UNIX.

Related Information

Installation and upgrade considerations [page 14]

Release NotesAbout SAP Data Services 4.2 Support Package 6

P U B L I C© 2016 SAP SE or an SAP affiliate company. All rights reserved. 3

http://help.sap.com/bods42/

http://help.sap.com/disclaimer?site=https://service.sap.com/sap/support/notes/SAP Note 1530081

1.1 SAP information resources

A list of information resource links.

A global network of SAP technology experts provides customer support, education, and consulting to ensure maximum information management benefit to your business.

Useful addresses at a glance:

Table 1:

Address Content

Customer Support, Consulting, and Education services

http://service.sap.com/

Information about SAP Business User Support programs, as well as links to technical articles, downloads, and online discussions.

Product documentation

http://help.sap.com/bods/

SAP product documentation.

SAP Data Services tutorial

http://help.sap.com/businessobject/product_guides/sbods42/en/ds_42_tutorial_en.pdf

Introduces core features, concepts and techniques to extract, transform, and load batch data from flat-file and relational database sources for use in a data warehouse.

SAP Data Services Community Network

http://scn.sap.com/community/data-services

Get online and timely information about SAP Data Services, including forums, tips and tricks, additional downloads, samples, and much more. All content is to and from the community, so feel free to join in and contact us if you have a submission.

EIM Wiki page on SCN

http://wiki.sdn.sap.com/wiki/display/EIM/EIM+Home

The means with which to contribute content, post comments, and organize information in a hierarchical manner to so that information is easy to find.

Supported Platforms (Product Availability Matrix)

https://service.sap.com/PAM

Information about supported platforms for SAP Data Services with a search function to quickly find information related to your platform.

Blueprints

http://scn.sap.com/docs/DOC-8820

Blueprints for you to download and modify to fit your needs. Each blueprint contains the necessary SAP Data Services project, jobs, data flows, file formats, sample data, template tables, and custom functions to run the data flows in your environment with only a few modifications.


Release NotesAbout SAP Data Services 4.2 Support Package 6

http://help.sap.com/disclaimer?site=http://service.sap.com/

http://help.sap.com/bods



http://help.sap.com/disclaimer?site=http://scn.sap.com/community/data-services

http://help.sap.com/disclaimer?site=http://wiki.sdn.sap.com/wiki/display/EIM/EIM+Home

http://help.sap.com/disclaimer?site=https://support.sap.com/release-upgrade-maintenance/pam.html

http://help.sap.com/disclaimer?site=http://scn.sap.com/docs/DOC-8820

2 Compatibility update

In the typical SAP Data Services landscape, you must first install one of the following products. These products provide platform services such as security, scalability, and high availability for Data Services and Information Steward.

● SAP BusinessObjects Information Platform Services (IPS) 4.1 SP6 or SP7 or its higher compatible patches if you only want to use features of Data Services or Information Steward.

● SAP BusinessObjects Business Intelligence platform (BI platform) 4.1 SP6 or SP7 or its higher compatible patches if you also want to use Business Intelligence clients such as Web Intelligence documents or Crystal Reports.

NoteIf you are currently using SAP BusinessObjects Business Intelligence platform (BI platform), we also recommended that you install SAP Business Intelligence Information platform services (IPS) with Data Services on a separate environment to provide flexibility to upgrade Data Services and Information Steward independently from BI platform.

For the latest information regarding Data Services and BI platform/IPS compatability, see SAP Note 1740516 .

For the latest updates in other product compatibility, see the Product Availability Matrix document located in the SAP Service Marketplace: https://service.sap.com/PAM .

Release NotesCompatibility update



http://help.sap.com/disclaimer?site=https://service.sap.com/PAM

3 Restrictions update

The following restrictions apply to SAP Data Services version 4.2 SP6 (14.2.6.0).

Installation restrictions

The SAP Data Services installer is available in English only.

Modify installation restriction

During a "Modify" installation, installed features are incorrectly displayed as unchecked (not installed).

Symptom

In the maintenance installation window, if you choose Repair first, then click Next, then click Back, then choose Modify, and then click Next, the feature tree selections are incorrect: No feature is shown as already installed.

If you proceed with the incorrect selections, all unselected features (if previously installed) will be uninstalled and only the current features shown as selected will be kept or installed.

Environment

Data Services 4.x

Resolution

Exit the current maintenance installation window by clicking Cancel and then clicking Exit Setup. Re-launch the maintenance installation, select Modify, and click Next. This refreshes the feature tree selections and correctly displays the installed features as checked. You can now proceed by adding or removing features as needed for a "Modify" install.

See Also

Other troubleshooting tips can be found in the knowledge base article 1530081

Other restrictions

● Google BigQuery application datastore configuration cannot be updated using the Management Console in Data Services 4.2.4 and later. When you export a job that has a Google BigQuery datastore, the export does not include the Google private key for security reasons. When you deploy the job in a production environment, you must update the private key and make other necessary changes in the BigQuery datastore options to enable the job to access your Google BigQuery project. Instead of using Management Console to update the Google BigQuery datastore configuration, you must update the private key and other necessary options in Designer using the Datastore Editor.


Release NotesRestrictions update

http://help.sap.com/disclaimer?site=https://service.sap.com/sap/support/notes/1530081

● Although Data Services currently supports both Oracle Change Data Capture (CDC) in synchronous mode (trigger-based) and asynchronous Hotlog mode, Oracle Streams (in Data Services terms, known as asynchronous CDC mode) is being deprecated. For more information about support and recommendations, see SAP Note 2021392 – Data Services CDC support for Oracle 12c.

● For Sybase IQ versions prior to 15.x, Data Services does not support named pipes if the Job Server and Sybase database are not on the same computer.

● The installation path of Data Services cannot contain multi-byte characters.● The functionality to read from and write to Data Federator data sources is not available on the Windows 64-bit

Data Services Designer and Job Server due to unavailability of 64-bit ODBC driver for Data Federator. This functionality is available for the 32-bit Data Services Designer only.

● The Text Data Processing Entity Extraction transform assumes that the format of an input document is consistent. Processing mixed-format input (for example, a binary object embedded in an HTML e-mail message) is not supported.

● The Text Data Processing Entity Extraction transform assumes that the language of an input document has been selected correctly. Processing content using the wrong Text Data Processing language (for example, processing a Simplified Chinese document using the English language) can result in incorrect results or longer processing times.

● When you use an Attunity Connector datastore, all Data Services features are available except the following:○ Bulk loading○ Imported functions (imports metadata for tables only)○ Template tables (creating tables)○ Datetime data type supports up to 2 sub-seconds only○ Loading timestamp data into a timestamp column in a table, because Attunity truncates varchar data to 8

characters, which is not enough to correctly represent a timestamp value.● Bulk loading data to DB2 databases running on z/OS or iSeries systems is not supported.● The following table describes the Data Services support for multi-byte metadata, Data Profiler, the lookup_ext

function, and View Data.

NoteData Services supports multi-byte metadata for table names, column names, file names, and file paths.

Support for multi-byte metadata depends on comparable support in the applications, databases, and technologies with which Data Services interoperates.

Table 2:

Source/Target Multi-byte metadata

Data Profiler Lookup_ext View Data

Adapter Yes No No No

Attunity connector for mainframe databases

No Yes Yes Yes

BusinessObjects Enterprise

Yes n/a n/a n/a

COBOL Copybook Yes No No Yes

DB2 Yes Yes Yes Yes

Flat File Yes Yes Yes Yes




Source/Target Multi-byte metadata

Data Profiler Lookup_ext View Data

SAP HANA Yes Yes Yes Yes

HP NeoView Yes Yes Yes Yes

Informix Yes Yes Yes Yes

JD Edwards No No Yes No

Memory Datastore Yes Yes Yes No

Microsoft Excel Yes No No Yes

Microsoft SQL Server Yes Yes Yes Yes

MySQL Yes Yes Yes Yes

Netezza No Yes Yes Yes

ODBC Yes Yes Yes Yes

Oracle Yes Yes Yes Yes

Oracle E-Business Suite No Yes Yes Yes

People Tools No Yes Yes Yes

Persistent Cache Yes No Yes Yes

Salesforce.com Yes No No No

SAP Business Suite

Extractor No No No Yes

Hierarchy No No No Yes

IDoc No No No No

Table No Yes No Yes

SAP BW Source

IDoc No No No No

OpenHub No No No No

Table No Yes No Yes

SAP BW Target No No No No

SAP Sybase SQL Anywhere

Yes Yes Yes Yes

Siebel Yes Yes Yes Yes

Sybase ASE Yes Yes Yes Yes

Sybase IQ Yes Yes Yes Yes

Teradata Yes Yes Yes Yes

XML Yes No No Yes

● When using Microsoft Excel as a data source, the following restrictions apply:○ Concurrent access to the same Excel file will not work. For example, View Data will not display if the file is

currently open in Excel.



○ Because an Excel column can contain mixed data types, some data type conversions may produce unexpected results; for example, dates might convert to integers.

○ Workbooks with AutoFilter applied are not supported. Remove the filter before importing the workbook.○ Workbooks with hidden rows and/or columns are not supported.

● To ensure security for your Data Services environment, use a firewall to prevent remote access to administrative functions. For information about the ports required for Data Services components, see the Administrator Guide.

● The SLT feature requires that you use a compatible version of SLT. See the SAP Data Services PAM for the availability of the necessary version of SLT.



http://help.sap.com/disclaimer?site=https://service.sap.com/PAM

4 Product dependencies update

● In order to use the Teradata interface on a Windows 64-bit platform, you must set the following environment variable on the Windows job server machine:LIB_32BIT_TERADATA=<Teradata 32-bit client location>This step is necessary due to the unavailability of Teradata client utilities on Windows 64-bit platforms.

● The Microsoft Excel interface has software dependencies in SAP Data Services 4.2. Special care must be taken when installing Data Services on a machine with a Microsoft Office version lower than 2010. For details, see the Installation Guide.

● The Data Services XI 4.0 (version 14.0.0 and above) Open Hub feature is supported in SAP BW 7.01 patch level 003 and above.As a pre-requisite, the following SAP Notes must be implemented before using this feature:○ SAP Note 1294774 SAP Note1270828 Resolves table import issues.○ SAP Note 1330568 version 3: Resolves table reading issues.

For the latest information about Open Hub, refer to SAP Note 1343606 in the SAP Service Marketplace.● For the latest information about Data Services SAP extractor support, see SAP Note 1558737 .● Support for the Allow Merge option for auto correct load is provided for the following targets: Oracle 9i and

above, IBM DB2 8.2 and above, and Microsoft SQL Server 2008 and above.● Due to a vendor limitation with Oracle 10G, while running Data Services on UNIX using Oracle Client on UNIX

and Oracle Server on Windows, the Oracle Client version must be 10.2.0.1 or higher.● The Data Services log-based changed-data capture (CDC) works with the following database versions:

○ Oracle version 9.2 and above compatible versions for synchronous CDC and Oracle version 10G and above compatible version for asynchronous CDC.

○ Microsoft SQL Server 2000, 2005, and 2008.○ Attunity for mainframe sources using Attunity Connect version 5.1 and above.○ Data Services 4.0 and later versions now support extracting data from the SAP Business Suite

applications through the business content extractors. In order to fully benefit from this feature, there are some minimum support package requirements for your NetWeaver environment. In addition to the support package, an additional SAP Note needs to be applied to your NetWeaver environment to release the extractors and make them visible for Data Services. These dependencies are documented in SAP Note 1522554 .For older versions of your SAP Business Suite (pre-ECC6) or when the required support package is not installed, extractors can still be used, but with limited functionality. This includes:○ No support for delta queues○ Supported extractor types: Transaction and Attribute


Release NotesProduct dependencies update


http://help.sap.com/disclaimer?site=https://service.sap.com/sap/support/notes/SAP Note1270828






5 Deprecated functionality

Data Services 4.2 SP5

The following functionality, which had been available with Data Services 4.2 SP4, is no longer available:

● 32-bit Data Services Designer


The following functionality, which had been available with Data Services 4.2, is no longer available:

● License Manager user interface. The License Manager user interface was removed, but you can still add, remove, and view license codes through the License Manager command prompt. For more information, see "Command line administration: License Manager" in the Administrator Guide.

● NCOALink DVD Verification utility user interface. The graphical user interface for the NCOALink DVD Verification (Installer) utility, which transfers and unpacks the compressed files from the NCOALink DVD onto your system, is no longer installed with Data Services. If you still have the graphical user interface installed, you can continue to use it, or you can use the new command-line utility.

● The application right "Manage resource repository" is no longer available in the Central Management Console (CMC).



● DB2 Load method for bulkloading. We recommend using either the CLI load or import utility for bulkloading.

Data Services 4.2


● Simple Network Management Protocol (SNMP)SAP Solution Manager can provide you with a solution, in place of SNMP.

Data Services 4.1

The following functionality, which had been available with Data Services XI 4.0, is no longer available:

Release NotesDeprecated functionality


● Text Data Processing:○ Support for subentities in German and English.○ The Entity Extraction transform no longer normalizes extraction output. For example, dates and

currencies appear as they were found in the source text.● SAP BusinessObjects Metadata Integrator

Data Services XI 4.0

The following functionality, which had been available with Data Services XI 3.x, is no longer available:

● HP-UX has been removed as a supported platform. Disregard mentions of HP-UX in any documentation that may contain references to this platform and refer to the PAM for information on all supported platforms.

Data Services XI 3.x

The following functionality, which had been available with Data Services XI 3.x, is no longer available:

● HP-UX has been removed as a supported platform.● Data Cleanse dictionary functionality (moved to the Cleansing Package Builder module of Information

Steward), including:○ Creating and deleting dictionaries○ Adding, editing, and deleting entries, outputs, and classifications○ Searching

● Data Cleanse tab in a target table's View Data feature○ Add Firm Standards○ Add to Dictionary

● BWA/TREX datastore database type and its related functions● Index Designer● Graph tabs that depict Gantt charts in the Performance Monitor and Operational Dashboard are not available

in the SAP Data Services XI 3.2 version 12.2.0.0 or later releases. Table views of the data are still available.● CaShowL

Data Integrator XI Release 2 Accelerated (11.7)

The following functionality, which had been available with Data Integrator XI Release 2 Accelerated (11.7), is no longer available:

● Log-based changed-data capture (CDC) with IBM DB2 UDB for Windows, z/OS, IMS/DB, and IBM VSAM.



Data Quality XI Release 2

The following functionality, which was available with Data Quality XI Release 2, is no longer available in SAP Data Services:

● Web Services: .Net Deployment● Compound transforms● Shared options● Unique ID Record Stem support in Candidate Selector● Pre/Post SQL Operations in Reader transform● Per Dataflow Mode in User-Defined transform (use workflow and scripts instead)● Enabling and disabling transforms in a dataflow● Thread and watermark settings on a per-transform basis● Observer transform● Progress Service transform● Integrated batch API● Admin methods in Message Client API● JIS_Encoding, UTF-32 for flat files● Python methods for User-Defined transform● Generic Per Collection Mode Sort in Sorter transform● DBASE3 file formats



6 Installation and upgrade considerations

SAP Data Services 4.2 can be installed in either of the following ways:

● As a new, full installation or uninstalling any previous Data Services versions.● As an upgrade on top of an existing Data Services 4.0 or 4.1 version (without uninstalling the previous

version).

Full installation

The Data Services 4.2 installer automatically detects whether a version of Data Services is already installed and then follows the appropriate workflow. If Data Services is not already installed on the system, the installer performs the full installation.

For more information about installing and configuring Data Services, see the following resources:

● For deployment and architecture information, see the Data Services and Information Steward Master Guide.● For full installation instructions, see the SAP Data Services Installation Guide.● For additional installation and configuration troubleshooting tips, see SAP Note 1530081 .

Supported installation scenarios

The following list illustrates common supported installation sequences for upgrading Business Intelligence platform (BI), and Data Services to version 4.2. Information platform services (IPS) can be used in place of BI in any of these sequences:

● Scenario 1: New installationBI 4.1 SP6/SP7 (full installation) + Data Services 4.2 SP6

● Scenario 2: Upgrade from existing Data Services 4.0 installationBI 4.0 SP2 + BI 4.0 patch 2.13 (or above) + Data Services 4.0.x + BI 4.1 SP6/SP7 (patch installation) + Data Services 4.2 SP6[1]

● Scenario 3: Upgrade from existing Data Services 4.1 installationBI 4.0 SP4 (full installation) + Data Services 4.1x + BI 4.1 SP6/SP7 (patch installation) + Data Services 4.2 SP6

● Scenario 4: Upgrade from existing Data Services 4.2 SP1/SP2/SP3/SP4/SP5 installation○ BI 4.1 SP1 (full installation) + Data Services 4.2 SP1 + BI 4.1 SP6/SP7 + Data Services 4.2 SP6[1]

○ BI 4.1 SP2 (full installation) + Data Services 4.2 SP2 + BI 4.1 SP6/SP7 + Data Services 4.2 SP6[1]



○ BI 4.1 SP4/SP5 (full installation) + Data Services 4.2 SP4 + BI 4.1 SP6/SP7 + Data Services 4.2 SP6[1]

○ BI 4.1 SP5/SP6 (full installation) + Data Services 4.2 SP5 + BI 4.1 SP6/SP7 + Data Services 4.2 SP6[1]


Release NotesInstallation and upgrade considerations

http://help.sap.com/disclaimer?site=https://websmp208.sap-ag.de/sap/support/notes/1530081

Note[1]: A Data Services repository upgrade is mandatory. For more information, see the SAP Data Services Upgrade Guide.

Upgrading to Data Services 4.2 SP6

Before you upgrade, review the Data Services Upgrade Guide for upgrade scenarios and paths.

Also, refer to the “Restrictions update” section of these Release Notes for important installation information about upgrading from previous versions of (XI 3.x, 4.0, 4.1, and Data Integrator 11.7).

Installation sequence

Before starting the update procedure, make a backup of your Data Services configuration files (for example, DSConfig.txt). During the installation of Data Services 4.2 SP6, you can choose to reuse an existing configuration and repository from a previous Data Services installation.

1. If you have an existing installation of Business Intelligence platform or Information platform services (IPS), you must upgrade to Business Intelligence platform (BIP) 4.1 SP6 or 4.1 SP7 (patch or full version) or Information platform services (IPS) 4.1 SP6 or 4.1 SP7 (patch or full version).

2. If you are upgrading from Data Services 3.2, you need to uninstall that version first.3. Install Data Services 4.2 SP6 over versions 4.0 or 4.1.

NoteWhen upgrading to SAP Data Services 4.2 SP6 or 4.2 SP6 Patch 1, there are known issues with the %DS_COMMON_DIR% system variable. Before upgrading, for more information and workarounds, see the following SAP Notes:○ For Windows customers upgrading from SAP Data Services 4.0.x to SAP Data Services 4.2 SP6 or 4.2

SP6 Patch 1, see SAP Note 2278886 .○ For other Windows customers installing or upgrading to SAP Data Services 4.2 Support Pack 6 or

Support Patch 6 Patch 1, SAP Note 2275506 .○ After upgrading, if the Repository Manager fails to perform an upgrade or create function, see SAP

Note 2279976 .

Refer to the “Backing Up and Restoring” topic in the SAP BusinessObjects Business Intelligence platform Administrator Guide before uninstalling it.

Upgrading from Data Quality XI

If you are upgrading from Data Quality XI, you must first upgrade to Data Services 4.1 before upgrading to Data Services 4.2. See the Data Services 4.1 SP1 Upgrade Guide for more information.






http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_bip_admin_en.pdf

http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_bip_admin_en.pdf

Upgrade Guide

See the Upgrade Guide, which is available at http://help.sap.com/bods.

The Upgrade Guide includes two sections:

● “Upgrading to SAP Data Services 4.2 SP6”: Helps you upgrade from previous versions (Data Integrator 11.7 and Data Services 3.x, 4.0, and 4.1) to SAP Data Services 4.2 SP6.

● “Data Services Behavior Changes”: Describes behavior changes associated with all versions of Data Services and Data Integrator 11.7.0 and later.



http://help.sap.com/bods

7 Known issues

This section lists known issues in descending order by internal issue identification tracking number. We also use these numbers in the release notes that accompany our support packages and patches. You can reference the issue ID when searching for the issue on our knowledge base or when speaking to SAP Business User Support.

When possible, workarounds are provided to help you resolve these issues.

NoteAs of version 4.2 SP4, SAP Data Services transitioned to a new system of issue tracking. Rather than using an ADAPT number, each issue is tracked in an SAP Note, and links are provided to the SAP Note for more information.

Table 3:

Issue ID Description

SAP Note 2279976 When upgrading from SAP Data Services 4.0 or greater to SAP Data Services 4.2 SP6 or 4.2 SP6 Patch 1 and the Change DS_COMMON_DIR option is selected, after installation, the Repository Manager fails to perform an upgrade or create function.

Workaround

1. Navigate to the %DS_COMMON_DIR%\log folder.

2. Create a folder named Admin.

3. Create a sub-folder under the Admin folder named repo.

4. Make sure the path %DS_COMMON_DIR%\log\Admin\repo now exists.5. Re-launch Repo Manager and do the upgrade or create.

SAP Note 2278886 For Windows customers upgrading from SAP Data Services 4.0.x to SAP Data Services 4.2 SP6 or 4.2 SP6 Patch 1:

In SAP Data Services 4.0.x, %DS_COMMON_DIR% system variable does not exist, which causes an issue when upgrading to SAP Data Services 4.2 SP6 and 4.2 SP6 Patch 1, regardless of where %DS_COMMON_DIR% is set or if it is not set during installation.

A correction will be provided in SAP Data Services 4.2 SP6 Patch 2. It is highly recommended that you perform the upgrade with SAP Data Services 4.2 SP6 Patch 2; or, you can perform a two-step upgrade from SAP Data Services 4.0 to SAP Data Services 4.2 SP5 first, and then upgrade to SAP Data Services 4.2 SP6 or 4.2 SP6 Patch 1.

If you have already performed the upgrade and encountered this issue, please report it to SAP Technical Support for further assistance.

This is not a problem for customers upgrading from Data Integrator 11.x, BusinessObjects Data Services 3.x, or SAP Data Services 4.1.

Release NotesKnown issues







SAP Note 2275506 For Windows customers installing or upgrading to SAP Data Services 4.2 Support Pack 6 or Support Patch 6 Patch 1:

Starting with SAP Data Services 4.2 SP6, there is an option to change the %DS_COMMON_DIR% system variable to a desired location during installation or upgrade, so that disk space can be managed more efficiently; however setting %DS_COMMON_DIR% to the same location as the product installation directory %LINK_DIR% is not a supported scenario, as it causes unexpected issues in the product installation and runtime.

A correction will be provided in SAP Data Services 4.2 SP6 Patch 2 to prevent this issue. If you are using SAP Data Services 4.2 SP6 or SAP Data Services 4.2 SP6 Patch 1, do not set %DS_COMMON_DIR% to the same location as %LINK_DIR% to avoid the issue in the later update/upgrade process.

This applies to new installations and upgrades of SAP Data Services 4.2 SP6 and 4.2 SP6 Patch 1. If you plan to upgrade your Data Services installation for use with SAP Information Steward, this also applies.

For example: If %LINK_DIR% or the product installation folder is D:\Program Files (x86)\SAP BusinessObjects\Data Services, then set %DS_COMMON_DIR% to a separate folder on the D drive, such as D:\DSCOMMONDIR, but avoid setting it to D:\Program Files (x86)\SAP BusinessObjects\Data Services.

SAP Note 2244477 UDC (Data Cleanse) and Global Geocoder: Performance degradation (426 vs 425) in Linux.

SAP Note 2244473 Successful Data Services install with an error statement in install log file: "ParserConfigurationException was thrown. The feature 'http://xml.org/sax/features/namespace-prefixes' is probably not supported by your XML processor."

SAP Note 2244330 When testing the Data Cleanse .pdf report files, the Status Code Summary Report is output with the name "udcststatuscodesummary.pdf". It should be "udcstatuscodesummary.pdf" (without the 'st').

SAP Note 2243880 Trying to load an MS SQL table that contains spatial data directly to SAP HANA fails. Only the first row is transferred correctly, and the rest of the rows have empty data for the spatial columns until the next fetch batch occurs. It also fails with a bad index during the load.

Workaround

Use the feature with a Query transform, which works correctly and yields the expected results.

SAP Note 2242684 On AIX, when SAP Data Services 4.2 SP6 and BOE 4.1 SP6 are installed in the same folder on the same machine, DS AL_RWJobLauncher results in a segmentation fault error when executing the job through the scheduler

Workaround

To use AL_RWJobLauncher for scheduling a job, install BOE and Data Services on two different machines or two different folders on the same machine.

SAP Note 2240900 Jobs calling SOAP 1.1 or 1.2 web services on Solaris 11 fail with error <50406>.

SAP Note 2240264 When loading to a HIVE template table from another HIVE source and the data flow is optimized for full pushdown that is insert-select, the monitor log count shows zero as rows loaded.

Workaround

Use the count(*) from the table before and after load to get the number of rows loaded




















SAP Note 2223380 HANA Calc view gives an untranslatable error when loading target table gives a primary violation error.

Workaround

When you get the error, either select delete table before loading option in target table properties, or delete the table manually and then try to load again.

SAP Note 2218292 SAP BusinessObjects Information platform services (IPS) 4.1 SP6 CMS crashes after a fresh BOE client 4.1 SP6 installation, which causes the subsequent SAP Data Services installation to fail.

Workaround

As a workaround, see the attachment in the SAP Note.

SAP Note 2162879 A Data Services job fails when reading from the same xlsx file from parallel data flows.

Workaround

A solution to this issue is to provide read and write access to the directory in which the xlsx file is located for the user 'IUSR' . After providing access, restart the Data Services Job Service.

SAP Note 2161514 When reading from MongoDB and the Where condition in a Query or XML_Map transform that contains an empty string or null, it produces an incorrect result.

Workaround

Use a Query criteria parameter in the MongoDB source instead of a Where condition.

SAP Note 2160793 A delta extraction job for a cluster table completes without error, but results in no data.

SAP Note 2160763 Bulk load with import fails to work with a DSN-less connection on DB2.

Workaround

Use a DSN connection for bulk load.

SAP Note 2160242 Cannot delete an invalid extract request subscription from an SLT system.

SAP Note 2160228 Extracting change data from an SLT source results in an integrity constraint violation.

Workaround

To avoid the problem, use auto-correct load.

SAP Note 2160228 Delta extraction from an SLT source results in an integrity constraint violation.

Workaround

To avoid the problem, please use auto-correct load.





















SAP Note 2158337 When attempting to execute a job through SAP Data Services on HDP 2.2 Hadoop cluster, get the following error: "<Failed to initialize HDFS. Check HDFS environment setup>".

Workaround

A shared library is missing from the /usr/lib64 directory. Make a copy manually to that location from /usr/lib and create a symbolic link to the file in /usr/lib64. To work around this issue, before re-running the job, enter the following on the job server machine where the master node of the Hadoop cluster is running:

1. cd /usr/lib2. cp libhdfs.so.0.0.0 /usr/lib643. cd /usr/lib644. ln -s libhdfs.so.0.0.0 libhdfs.so

SAP Note 2156354 On AIX in Per Collection mode, after a User-Defined transform (UDT) processes null input fields, the fields are sometimes populated.

Workaround

To work around this issue:

1. Place a Query transform before the User-Defined transform to change the null field to a field with any value: nvl('field_name',' ').

2. Place a Query transform after the User-Defined transform to remove the value placed in the field: ltrim_blanks('field_name').

SAP Note 2155944 If using the MySQL 5.6 Unicode driver libmyodbc5w.so to connect to MySQL 5.6 in Solaris, the job runs successfully, but the string cannot be inserted to MySQL 5.6 tables.

Workaround

Use the ansi driver libmyodbc5a.so to configure DSN or DSN-less connectivity.

SAP Note 2108243 When installing SAP Data Services 4.2 SP4 on BOE_4.1_SP4 and later versions, ‘setup.sh -w’ does not write the “installdir” property into the response file.

Workaround

Manually edit the response file to add “installdir”.

ADAPT01731711 The Salesforce.com adapter does not start due to a missing classpath.

Workaround

To work around this issue, manually modify the classpath by adding the missing classpath to the startup JVM parameters.

ADAPT01724380 Because of a vendor limitation, Oracle CDC in asynchronous HotLog mode and Oracle CDC in asynchronous AutoLog mode is not supported if the Oracle database is a pluggable database (PDB) running on a container database (CDB).

ADAPT01723769 If using a JDBC Adapter as a source, for CHAR data type of the Information source, while loading into the target, Data Services does not trim the trailing space in the data. To trim the trailing data, you must explicitly invoke the rtrim_blanks function.












ADAPT01723472 In a JSON Schema reader, the JSON file path is not reserved when used as a source.

Workaround

As a workaround, you can browse the file location without hard type. JSON does not support remote location.

ADAPT01722799 When Teradata 14.0 or 14.10 bulk loader mload with File option Generic named pipe runs on Window 2012, it does not behave correctly. Use other methods of the bulk load option until Teradata fixes the issue.

ADAPT01722042 For Data Services jobs or data flows created using the replication wizard in Data Services Workbench, the Data Services Get_BatchJob_FlowDetails web services operation fails with the error: “<ErrorMessage>while trying to invoke the method com.acta.repo.ALParentChild.getParentObj() of an object loaded from local variable 'apc'</ErrorMessage>”.

Workaround

To work around this issue, create the data flow manually.

ADAPT01722039 If running an Oracle 12c client on Windows for Oracle bulk loading, when Data Services runs the sqlldr.exe, it throws an error that oraodm12.dll is missing. This is an Oracle issue.

Workaround

As a workaround, copy the oraodm12.dll file from the Oracle 12c server installed machine.

ADAPT01721918 If you have a Sybase IQ 16 server running on Windows, a problem may occur in bulk loader mode. This is a known issue from IQ server.

Workaround

The workaround is to install Sybase IQ server on Linux or apply the latest Sybase IQ patch.

ADAPT01719428 If the application server is JBoss, the cereports.jar file causes an issue when attempting to view Data Quality reports.

Workaround

To work around this issue, perform the following steps:

1. Stop the JBoss Application server.

2. Go to the location where the DataServices.war file is deployed on your JBoss application server (for example, C:\jboss-5.0.1.GA\server\default\deploy\DataServices.war\WEB-INF\lib).

3. Rename the cereports.jar file so that it is no longer a jar file (for example, change it to cereports.zip).

4. Restart the JBoss application server and verify that you can view the reports.

ADAPT01719261 On Windows 2012 R2, when installing Data Services as a non-administrator user with administrative privileges from a UNC path, even if the user mapped the path to a local drive, the installation fails the test connection on the CMS screen. This is a known issue caused by Windows 2012 R2.

Workaround

To work around the problem, copy the installation package to the local file system. For more information see SAP Note 1530081 - Troubleshooting tips for SAP Data Services 4.x.





ADAPT01719229 Space string comparison against SAP HANA may not comply with the ANSI SQL-92 empty string rule, which may produce erroneous results.

Workaround

The workaround is to add a Merge transform or mapping transform, which follows the ANSI SQL-92 empty string rule.

ADAPT01717112 On Solaris 10, Data Services bulkload with Parallel Transporter and Named pipe access module does not work with Teradata 14.10.

ADAPT01712677 On Unix Job Servers, loading data to Netezza using bulk load fails if the Netezza datastore connection is server based instead of DSN based.

Workaround

The workaround is to use a DSN-based connection.

ADAPT01710495 A mixed case table name in SAP HANA cannot be used as a comparison table when using a Table Comparison transform.

ADAPT01710451 Data Services cannot import Sybase ASE source/target tables with primary key/foreign key columns longer than 30 characters due to the truncation of these names in Sybase.

ADAPT01709411 Data Quality report export fails when password encryption is enabled for a Sybase repository. This occurs in both the Management Console and when utilizing the Export Data Quality Reports option when executing a job.

Workaround

To work around this issue, disable the password encryption on the Sybase repository.

ADAPT01706418 When reading from a HANA table that contains clob or lob columns, the following error might occur even though no conversion in parameter is required:

“General error;-10427 Conversion of character parameter (2) failed with return code 2”

The SAP HANA team is working on a fix and we expect the fix to be available in an upcoming HANA release.




ADAPT01692106 There are several Sybase Replication CDC issues for Power Designer CDC Configuration:

● Power Designer does not generate "ra_set_autocorrection tablename, enable" for Oracle as primary database, even if the replication definition clause "replicate all columns" is added by "SAP Data Services CDC 1.0.0" extension. This prevents the Sybase Replication Agent from replicating all columns for UPDATE records. As Data Services needs all columns in UPDATE records to correctly modify target table, you may experience missing data.WorkaroundConnect to the Oracle Replication Agent as an administrator and either mark all tables for auto correction by executing “ra_set_autocorrection all enable” or mark specific table for auto correction by executing “ra_set_autocorrection tablename, enable”. This command turns on Oracle’s supplementary logging.

● If Publication Article's has more than one LOB column, the Power Designer is not generating corresponding rs_get_textptr function strings for all BLOB columns. It only generates rs_get_textptr for the last BLOB column in the schema.WorkaroundAfter exporting the RCL script from Power Designer, add other LOB columns that need to be added to the replication definition. Follow the syntax that is generated for the last LOB column function string “rs_get_textptr” in the RCL script.

● When an Oracle table has multiple timestamp columns and the replicate database is Sybase ASE, the Power Designer creates multiple Sybase ASE table timestamp columns. Sybase ASE allows only one timestamp column.WorkaroundIn Power Designer, change the data type of the timestamp column to varchar(36) in Replication Process table Properties.

ADAPT01688186 Having more than one .xlsx source in parallel in a data flow referring to same .xlsx file results in an error message: “External table is not in the expected format”. This issue can be resolved by having different names for the .xlsx file in each source.

ADAPT01687744 When doing queries of HDFS files, Pig is used to pushdown math functions. Pig does not support calling of a math functions with a null value. Because of this limitation in Pig, if the HDFS files contain records with a null field for which a math function would be applied, then the query will fail.

ADAPT01686554 When exporting or attempting to view the Match Duplicate Sample report from an SAP HANA repository, an “Unexpected database connector” error is issued under certain circumstances.

Workaround

To work around this issue, disable the automatic generation of Data Quality reports or set the Generate Reports option in the Match transform to No.

ADAPT01684839 When inserting more than one LOB column into a HANA table, you may get the following HANA ODBC error:

“[HDBODBC] General error:-10322 Could not insert LOB. Parameter/column (11) has a NULL/DEFAULT value.”

ADAPT01678532 When there are two job servers with the same name in the repository, deployment takes place with the selected job server, but execution takes place with the first job server in the list.

Workaround

The workaround is to use a unique name for each job server.




ADAPT01675552 RFC Server Status and Configuration is not displayed in the Data Services Management Console when the EIM Adaptive Processing Server hosting Data Services RFC Service is changed. The Data Services Management Console expects the name of the EIM Adaptive Processing Service hosting RFC Service to be in <SIA Node Name>.EIMAdaptiveProcessingServer format.

ADAPT01675109 An export of Data Quality Reports fails when the Report Server is SSL enabled.

Workaround

To work around this issue, on the Job Server machine, under the [AL_Engine] section of the DS_COMMON_DIR\conf\DSConfig.txt file, add a new parameter, DQ_ReportServer_HTTPS=TRUE; in the DS_COMMON_DIR\ext\webservice-c\axis2.xml file, enable the HTTPS sender and receiver transport, SERVER_CERT parameter.

ADAPT01656582 The function day_in_week behaves differently for SAP HANA than what is stated in the Data Services documentation. When the day_in_week function is pushed down to SAP HANA, the returned result is 0-6 (Monday - Sunday), with 0 being Monday and 6 being Sunday. The documentation states that the returned result is 1-7 (Monday - Sunday).

ADAPT01632475 If a job using Text Data Processing, which is pushed down to Hadoop, is killed, the Hadoop portion of the job will continue to run to completion. You can kill the Hadoop portion of the job by using the Hadoop utilities:

hadoop job –list: Lists all hadoop jobs.

hadoop job –kill <job-id>: Kills a hadoop job with given id

You can also find the Hadoop job ID by finding the Pig Script directory, which is output by the Data Services job, and search the hdfsRead.err file found within for a line similar to:

12/04/19 15:00:02 INFO mapred.JobClient: Running job: job_201204131948_0015

In this example, the job ID would be job_201204131948_0015.

ADAPT01632076 For a high volume of data returned by native extractor, a memory issue can occur. You need to use R3 data flow to take advantage of RFC streaming to overcome the memory issue.

ADAPT01629085 Data Services limits browsing to only tables and views of a database that is configured in MySQL ODBC DSN for MyODBC driver 3.51.28 and above. Please refer to Oracle bug#13914518 for detail.

If you want to import tables or views that belong to other MySQL databases, you can do so by selecting the "Import By Name" option.

ADAPT01617434 Excel currency data of values greater than 10e+11 are imported incorrectly into Data Services. This is a known vendor issue which has not yet been resolved by Microsoft.

ADAPT01604091 Inserting to Hive Tables in Append mode: Use the Append mode when loading Hive tables carefully. Although Hive 0.8 supports INSERT INTO command syntax for appending the data, it actually overwrites data in many cases. Loading from files as source to non-partitioned Hive tables is the only way the Append mode functions correctly. In other cases, such as loading files as source to partitioned Hive tables, using Hive tables as source, and using Hive tables as target (both partitioned and non-partitioned), the Append mode actually overwrites the existing data.




ADAPT01601340 Hive Table Source: While selecting from Hive table with both GROUP BY and ORDER BY, and when the reader SELECT is pushed to Hive, Hive returns the following error:

“Error in semantic analysis: Invalid table alias or column reference”.

This is an issue in Hive.

Workaround

To work around this error, it is recommended that you block ORDER BY by using a Merge transform between GROUP BY and ORDER BY so that ORDER BY is not pushed down to database.

ADAPT01541627 Complex data flows with a large number of columns may throw the error “ODBC data source <tdata_83_64> error message for operation <SQLExecute>: <[Teradata][ODBC Teradata Driver] SQL request exceeds maximum allowed length of 1 MB”. This is a limitation of the Teradata ODBC driver.

ADAPT01511272 ABAP function modules cannot be called because of an SAP type conversion error within the ABAP transform due to data type mismatch.

Workaround

The workaround is to add a Query transform to convert all the columns that are used to map to SAP function input parameters, to exactly match the data type of the SAP function input parameters. Then connect the newly added transform to the transform that makes the SAP ABAP function call.



8 Fixed issues

This section contains a list of issues that have been fixed in the SAP Data Services 4.2 SP6 (14.2.6) release. The list includes the fixes that are forwarded from the previous patches and additional fixes in this release.

8.1 Issues fixed in support packs and previous patches

The fixes in the following support packs (SPs) and patches are included in this release. These fixes are listed in the Fixed issues section of the respective release’s Knowledge Base Article (KBA) Release Notes on the SAP Service Marketplace.

Table 4:

Data Services release version KBA release notes

4.2 SP5 Patch 2 2223961

4.2 SP5 Patch 1 2195658

4.2 SP4 Patch 3 2192027

4.2 SP4 Patch 2 2173040

4.2 SP4 Patch 1 2128966

4.2 SP3 Patch 6 2209536

4.2 SP3 Patch 5 2156309

8.2 Issues fixed in this release

Issues fixed in this release are listed below in descending order by an internal issue identification tracking number. You can reference the issue ID when searching for the issue on our knowledge base or when communicating with SAP Customer Support.

Table 5:


SAP Note 2245834 On AIX, Data Services fails to execute a scheduled job because a socket is used due to a close_wait issue. This issue has been fixed in this release.

SAP Note 2245805 When loading to HANA with HANA Calc View used to load the data and a HANA table column name contains a space in it, the Data Services job fails with a syntax error in procedure creation. This issue has been fixed in this release.


Release NotesFixed issues











SAP Note 2245804 The values of integer, real, double, and float data types is set to 0 (zero) if the data from IDoc for the columns/fields is prefixed with spaces. This issue has been fixed in this release.

SAP Note 2245717 When the Parse Discrete Input option is set to No, Info_Code P104/P204 & P105/205 information codes are reported when they should not be. The output for Info_Code P104/P204 (no given name or questionable given name) is always generated even though a given name was provided in the input. The output for Info_Code P105/P205 info code (no family name or questionable family name) is always generated even though a family name was provided in the input. This issue has been fixed in this release. The output for the exported field name INFO_CODE may show differences now containing P104/P204 & P105/205 info codes after this correction.

SAP Note 2245664 When Enable Presumptive Name Parsing is set to Yes, the Info_Code P#03 and P#02 information codes (presumptive name parse, close firm parse) should not be generated if input came from TITLE_LINE# or PERSON#_TITLE, or if only title information exists in the parse. The P#03 and P#02 information codes apply to person parses but not to title parses. This issue has been fixed in this release.

SAP Note 2245662 A specific Canada address does not make a match to a Primary Name that includes a Street Type. This issue has been fixed in this release.

SAP Note 2245639 Data Services does not return a suggestion list for the postcode when an invalid postcode is entered, there are multiple postcodes that are valid, and the Locality information is matched. This issue has been fixed in this release.

SAP Note 2245635 The parsing dictionary has 'V' as a valid abbreviation for Via street type in Spain and this is not valid. This issue has been fixed in this release.

SAP Note 2245598 When using suggestion lists on a specific Canadian address, selecting one of the secondary address entries creates an infinite loop. When entering the correct building name, an info code of 4000 is returned when it should make a building name match. This issue has been fixed in this release.

SAP Note 2245572 FR language addresses return the Primary Number prior to the Primary Name and it should be returned after the Primary Name. This issue has been fixed in this release.

SAP Note 2245107 On UNIX, using a python statement to import urllib2 in the User-Defined transform (UDT) and then executing the job causes several errors. The urllib2 Python module is used to open and read (usually HTTP) URLs. The errors are all in the following form: "ERROR:root:code for hash XXX was not found. ... ValueError: unsupported hash type XXX". This issue has been fixed in this release.

SAP Note 2244513 Under certain conditions, Lot and Lot_Order output components contain different data when processing the same record two times in a row. This issue has been fixed in this release.

SAP Note 2230103 When trying to install SAP Data Services on AIX, get the following error: "Failed: Minimum patch level requirements for OS (Critical)". This issue has been fixed in this release.

SAP Note 2225427 Data Services Designer crashes when attempting to View Optimized SQL of a data flow with a Data_Transfer transform. This issue has been fixed in this release.

SAP Note 2222805 In the CMC, not able to put multiple HANA nodes names in the Data Services repository server name string. This issue has been fixed in this release.

SAP Note 2221131 The AL_ERROR_MSG column of the RESTful web service operation response does not include the error response; only the HTTP error code and error reason are included. This issue has been fixed in this release.

SAP Note 2219795 For a job that uses a Row_Generation transform and inserts one row to a Teradata target with Trace SQL Loaders on, there is one insert for Data Services. In the ODBC trace log, there are multiple insert statements. This issue has been fixed in this release.



















SAP Note 2218698 For a batch job execution with non-printable characters from the Batch Job History page, opening the trace log of fails with the error: "Unexpected end of file in CDATA section". This issue has been fixed in this release.

SAP Note 2214382 Data Services Designer crashes or hangs when importing the XML Schema from an XSD file. This issue has been fixed in this release.

SAP Note 2213492 The al_engine command -z doesn't work as expected. Rather than create the error file in the location specified (for example -z "C:\temp\error1.txt"), the file is created in the default location C:\ProgramData\SAP BusinessObjects\Data Services\log\<JOB_Server>\<Repo_Name>. This issue has been fixed in this release.

SAP Note 2210776 The cast() function returns the wrong result for decimal data. If the input data is not numeric data, the remaining data cannot be casted. This issue has been fixed in this release.

SAP Note 2210225 When four chained data flows run with a degree of parallelism set to 1, the first two complete and the third errors out with an access violation error "SYS-170101: System Exception <ACCESS VIOLATION> occurred" before getting ready to process. Left outer join, group by, and aggregation all appear in the optimized SQL. This issue has been fixed in this release..

SAP Note 2209689 The internal job of Data Services behaves differently. It cannot be deleted by log retention functionality and is not displayed in the Jobs History page of the Data Services Management Console. This issue has been fixed in this release.

SAP Note 2207159 Column Profiling task fails with error "com.sap.icc.task.DataServiceEngineException: IDS_ERROR_DS_ENGINE_HANG" after ten minutes. This issue has been fixed in this release.

SAP Note 2203977 When you execute "print('\\\[host_name()]');" in script, the result is \\\\<hostname> instead of \\<hostname> which is expected. This issue has been fixed in this release.

SAP Note 2199738 A Query transform that contains a left join may cause the error "RUN-050406 Bad system message". This issue has been fixed in this release.

SAP Note 2194462 In Sybase IQ, using the to_char function with the datetime data type throws a "data type conversion is not possible" error when pushed down to the database. The date data type pushes down correctly. This issue has been fixed in this release.

SAP Note 2162755 While installing SAP Data Services on a Suse Linux SLES11 SP3 with Sybase ASE as the database, there is an issue creating repositories. When starting the repoman executable, it runs the following SQL script: /usr/sap/MDS/EIM/dataservices/admin/repo/sybase/sybase_content.sql. The following error appears: "BODI-320004: Error or warning in executing the SQL statement". This issue has been fixed in this release.

SAP Note 2160141 On UNIX, using a python statement to import urllib2 in the User-Defined transform (UDT) and then executing the job causes several errors. The urllib2 Python module is used to open and read (usually HTTP) URLs. The errors are all in the following form: "ERROR:root:code for hash XXX was not found. ... ValueError: unsupported hash type XXX". This issue has been fixed in this release.

SAP Note 2156863 OData adapter connection failure reports a generic error message "Please double check the URL and account information" instead of reporting actual reason for failure. This issue has been fixed in this release.
















Important Disclaimers and Legal Information

Coding SamplesAny software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

AccessibilityThe information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral LanguageAs far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet HyperlinksThe SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer).

Release NotesImportant Disclaimers and Legal Information


http://help.sap.com/disclaimer/

go.sap.com/registration/contact.html

© 2016 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

https://go.sap.com/registration/contact.html

https://go.sap.com/registration/contact.html

http://www.sap.com/corporate-en/legal/copyright/index.epx

http://www.sap.com/corporate-en/legal/copyright/index.epx

Release Notes - SAP obtain the latest version of documentation including the most up-to-date version...

Documents

Transcript of Release Notes - SAP obtain the latest version of documentation including the most up-to-date version...