SAP Information StewardDocument Version: 4.2 Support Package 3 (14.2.3.0) - 2014-09-09

Release Notes

Table of Contents1 Compatibility update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

2 Restrictions update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

3 Installation and upgrade considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

4 Documentation updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

5 Known issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

6 Fixed issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156.1 Issues fixed in support packs and previous patches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156.2 Issues fixed in this release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

7 SAP information resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2 © 2014 SAP SE or an SAP affiliate company. All rights reserved.Release Notes

Table of Contents

1 Compatibility updateBefore upgrading to Information Steward 4.2 SP3, ensure that the following prerequisite software has been installed:

● SAP BusinessObjects Business Intelligence (BI) platform 4.1 SP3 or SP4 or its higher compatible patchesorSAP BusinessObjects Information platform services (IPS) 4.1 SP3 or SP4 or its higher compatible patches

● SAP BusinessObjects Data Services 4.2 SP3 or higher compatible patchesFor more information on the compatibility of Data Services with BI platform or IPS versions, see SAP Note

1740516 .

For the availability of any higher compatible patches, see the “Support Packages and Patches” area of the SAP Service Marketplace.

For compatibility with SAP HANA, see SAP Note 1600140 .

For JDBC driver compatibility when connecting to Oracle, refer to SAP Note 1741042 .

For the latest updates in compatibility, see the Product Availability Matrix document located in the SAP Service

Marketplace: https://service.sap.com/PAM . To go directly to Information Steward, enter "Information Steward" in the search field.

Release NotesCompatibility update © 2014 SAP SE or an SAP affiliate company. All rights reserved. 3

2 Restrictions updateThe following restrictions apply to SAP Information Steward 4.2.

Common and new restrictions

● Information Steward does not support the capability to deploy and run on an SAP BusinessObjects Business Intelligence platform side-by-side environment (two versions of BusinessObjects Enterprise on the same machine).

● If Information Steward is running in an SSL environment, it can only connect to a BusinessObjects Enterprise integrator source that is SSL. If Information Steward is not running in an SSL environment, it can only connect to a BusinessObjects Enterprise integrator source that is also not SSL.

● Installing Information Steward using Windows AD/LDAP/SAP authentication does not work. When installing Information Steward, use Enterprise authentication. After installation is completed, you can switch to Windows AD/LDAP/SAP authentication.

● The Data Insight module of Information Steward cannot export more than 250 columns of data to a Microsoft Excel file.Currently, Data Insight supports exporting data to Microsoft Excel 2007 and older and does not support more than 250 columns. As a workaround, you can selectively choose the columns to export, so that it will not exceed 250 columns.

● The Data Cleansing Advisor feature, which is available in the Data Insight module, currently generates data cleansing solutions for party data only. Party data is data about individuals or organizations, such as name, address, and phone data.

● The Match Review feature does not support Sybase tables.

Data Services Integrator

● The Metadata Management module of Information Steward does not support the following Data Integrator or Data Services objects:

○ COBOL copybooks○ DTDs○ EXCEL workbooks○ XML schemas○ IDOCs○ PeopleSoft domains

● The Data Services Metadata Integrator does not collect metadata from memory datastores. It also doesn't collect metadata if the Data Services repository is an Oracle RAC database.

NoteTo configure a connection to an Oracle RAC database as the Data Services repository, you can specify a single node for the service name in the repository connection input parameters.

4 © 2014 SAP SE or an SAP affiliate company. All rights reserved.Release Notes

Restrictions update

BusinessObjects Enterprise Metadata Integrator

● The BusinessObjects Enterprise Metadata Integrator does not collect metadata for the following objects:

○ Business Views○ Crystal Reports that connect to XML files or Web Services○ Desktop Intelligence documents based on 8-bit universe names○ multi-dimensional .unx universes

● The Metadata Management module of Information Steward still uses the term Universe classes for Universe folders in .unx universes in SAP BusinessObjects Business Intelligence platform.

● The BusinessObjects Enterprise Metadata Integrator will terminate any open Universe Designer and Desktop Intelligence Designer sessions before it starts the collection. Ensure that no users are using the Designer before you run the BusinessObjects Enterprise Metadata Integrator on the same computer.

Metadata Management

● The Metadata Management module of Information Steward does not export objects collected by the MITI Metadata Integrator.

● The SQL parser in Metadata Management has limited parsing capabilities to collect column names and table names to build the relationships. This limitation might occur in situations such as the following:

○ If you do not qualify column names in a derived table with the table name, the Metadata Integrator cannot associate the column with the correct table and displays the following warning message:

Parsing failure for derived Table <table_name>.

NoteQualify the column name with the table name: <table_name.column_name> or add the tables used by the derived tables to the universe. The Metadata Integrator treats the universe tables as a system catalog to find the table and column references.

○ If a Metadata Integrator fails to parse the SQL parser for a view, it cannot build the source-target relationship between the view and the table or tables upon which the view is based and displays the following warning message:

Unable to parse SQL: <error message>

NoteThe Metadata Integrators collect the SQL statement and Metadata Management displays it. Analyze the SQL statement in Metadata Management and establish a user-defined relationship for these tables and columns.

● Metadata Management does not export the SQL statement for a view to the CWM XML file.● The SAP Sybase PowerDesigner metadata integrator in Information Steward version 4.2 (14.2.0) works with

the SAP Sybase PowerDesigner application version 16.1 and newer. If you use SAP Sybase PowerDesigner

Release NotesRestrictions update © 2014 SAP SE or an SAP affiliate company. All rights reserved. 5

version 16.0 and older, you need to continue to use the Meta Integration Metadata Bridge (MIMB) metadata integrator for SAP Sybase PowerDesigner metadata collection.

6 © 2014 SAP SE or an SAP affiliate company. All rights reserved.Release Notes

Restrictions update

3 Installation and upgrade considerationsSAP Information Steward 4.2 can be installed in either of the following ways:

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

version).

Full installation

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

For more information about installing and configuring Information Steward, see the following resources:

● For deployment and architecture information, see the Data Services and Information Steward Master Guide.● For full installation instructions, see the Installation Guide.

● For additional installation and configuration troubleshooting tips, see SAP Note 1570523 .

Supported installation scenarios

The following list illustrates common supported installation sequences for upgrading Business Intelligence platform (BI), Data Services, and Information Steward 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 SP3/SP4 (full installation) + Data Services 4.2 SP3 + Information Steward 4.2 SP3

● Scenario 2: Upgrade from existing DS/IS 4.0 installationBI 4.0 SP2 + BI 4.0 patch 2.13 (or above) + Data Services 4.0.x + Information Steward 4.0.x + Data Services 4.2 SP3 + Information Steward 4.2 SP3

● Scenario 3: Upgrade from existing DS/IS 4.1 installationBI 4.0 SP4 (full installation) + Data Services 4.1 SP1 + Information Steward 4.1 SP1 + BI 4.1 SP2 (patch installation) + Data Services 4.2 SP3 + Information Steward 4.2 SP3

● Scenario 4: Upgrade from existing DS/IS 4.2 SP1/SP2/SP3 installation [1]

○ BI 4.1 SP2 (full installation) + Data Services 4.2 SP1 + Information Steward 4.2 SP1 + BI 4.1 SP3/SP4 + Data Services 4.2 SP3 + Information Steward 4.2 SP3

○ BI 4.1 SP2 (full installation) + Data Services 4.2 SP2 + Information Steward 4.2 SP2 + BI 4.1 SP3/SP4 + Data Services 4.2 SP3 + Information Steward 4.2 SP3

○ BI 4.1 SP3 (full installation) + Data Services 4.2 SP2 + Information Steward 4.2 SP2 + BI 4.1 SP4 + Data Services 4.2 SP3 + Information Steward 4.2 SP3

Note[1]: Upgrading to BI 4.1 SP4 is optional because the existing installation is already at the minimum supported BI 4.1 SP3 version.

Release NotesInstallation and upgrade considerations © 2014 SAP SE or an SAP affiliate company. All rights reserved. 7

Upgrade installation

The Information Steward 4.2 installer automatically detects whether a version of Information Steward is already installed and then follows the appropriate workflow:

● If Information Steward is not already installed on the system, the installer goes through the full installation.

For full installation instructions, see the Installation Guide. Also, see SAP Note 1570523 for additional installation and configuration troubleshooting tips.

● If an existing version of Information Steward is installed, the installer performs an upgrade installation.For information about upgrading your Data Services and Information Steward landscape, see the Data Services and Information Steward Master Guide. For more information about possible upgrade scenarios, see

SAP Note 1723435 .You need to enter only the administrator-level password in the Central Management Server (CMS) connection screen of the installer.

NoteThe upgrade installation from Information Steward 4.2 SP2 to 4.2 SP3 does not perform a repository upgrade.

To work around this issue, run the following command after installation to manually upgrade the repository:

1. UNIX: <InstallRootDir>\InformationSteward\MM\bin\ISRepositoryUtility.sh upgrade password <repository_password> boeUser <boe_user_name> boePassword <boe_password>Windows: <InstallRootDir>\InformationSteward\MM\bin\ISRepositoryUtility.bat upgrade password <repository_password> boeUser <boe_user_name> boePassword <boe_password>

2. After the command finishes, restart Server Intelligence Agent (SIA) and Tomcat.

A fix for this issue is planned for an upcoming patch.

Upgrading after Information Steward 4.0 SP2 Patch 4 or Patch 5 was applied

If you applied Information Steward 4.0 SP2 Patch 4 or Patch 5, and upgrade to a higher patch level or service pack level, you must run a repair install of Information Steward after installing it. On Windows, use the Repair Program

utility. On Linux, use the modifyOrRemoveProducts.sh utility. For more information, see SAP Note 1738878 .

Upgrading from Data Insight, Metadata Management, Data Services, or Data Quality Management

When upgrading from BusinessObjects Data Insight 3.0, BusinessObjects Metadata Management 3.1, SAP BusinessObjects Data Services 3.2, or SAP BusinessObjects Data Quality Management 3.2, license keys enable access to comparable functionality in Information Steward modules. To enable full functionality of all Information Steward modules and features, you must obtain and install a full Information Steward or Information Steward – Multi-Source Metadata Integrators by MITI license key. For more information, contact your SAP account executive.

8 © 2014 SAP SE or an SAP affiliate company. All rights reserved.Release Notes

Installation and upgrade considerations

The Information Steward modules enabled by each upgrade license and license name displayed in the CMC are shown in the following table:

Upgrade from... Information Steward module Name in CMC

Data In­sight

Cleans­ing Package Builder

Meta­data Man­age-ment

Meta­pedia

Meta Integration Bridge Metadata Integrator (MITI)

BusinessObjects Data Insight

√ SAP BusinessObjects Information Steward – Platform for Data Insight

BusinessObjects Metadata Management

√ √ SAP BusinessObjects Information Steward – Platform for Metadata Management

BusinessObjects Metadata Management / MITI

√ √ √ SAP BusinessObjects Information Steward – Platform for Metadata Management with Multi-Source Metadata Integrators by MITI

SAP BusinessObjects Data Services

√ √ Data Services

SAP BusinessObjects DQM

√ √ Data Quality Management Premium

After you install Information Steward, the license key information is available in the License Keys management area of the CMC.

Data Insight and Metadata Management coexistence

Data Insight and Metadata Management products cannot be deployed to the same Central Management Server (CMS). You must either obtain a full version of Information Steward or deploy the upgraded versions of Data Insight and Metadata Management to separate CMS systems.

Release NotesInstallation and upgrade considerations © 2014 SAP SE or an SAP affiliate company. All rights reserved. 9

4 Documentation updatesThe following updates apply to the SAP Information Steward 4.2 documentation.

Documentation corrections

Support for Sybase ASE as a repository is not yet available although it was documented in the Information Steward 4.2 SP2 Installation Guide.

10 © 2014 SAP SE or an SAP affiliate company. All rights reserved.Release Notes

Documentation updates

5 Known issuesThis 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.

Issue ID Description

ADAPT01733119 The upgrade installation from Information Steward 4.2 SP2 to 4.2 SP3 does not per­form a repository upgrade.

To work around this issue, run the following command after installation to manually upgrade the repository:

1. UNIX: <InstallRootDir>\InformationSteward\MM\bin\ISRepositoryUtility.sh upgrade password <repository_password> boeUser <boe_user_name> boePassword <boe_password>Windows: <InstallRootDir>\InformationSteward\MM\bin\ISRepositoryUtility.bat upgrade password <repository_password> boeUser <boe_user_name> boePassword <boe_password>

2. After the command finishes, restart Server Intelligence Agent (SIA) and Tomcat.

ADAPT01727174 DCA - RH6.5-SQL Anywhere ODBC is not configured during installation. When DCA processes, an error is issued: “The ODBC Driver Manager library for data source is not set. Set the <DQL_ANYWHERE_12_X_DRIVERMANAGER> environment variable by running DSConnectionManager.sh.”

ADAPT01725639 The report functionality does not work properly in Internet Explorer 11.

Workaround: To make the Crystal reports viewer work, configure the Information Steward website in compatible view in Internet Explorer.

ADAPT01713377 When you select Disk Cost in the Select features step of the installation, the installer calculates cost using all drives, including mapped drives. This may result in additional installation time if, for example, the network is slow.

Workaround: Unmap your network drives before you install the software.

ADAPT01709665 When planning to use Cleansing Package Builder on Websphere, the initial deployment does not work.

Workaround:

1. Navigate to the Websphere installation directory and find the CPBWebservice.ear\CPBWebservice.war\WEB-INF\conf folder. For exam­ple, the Websphere directory could be similar to this: C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\Win2k8R2Tomcat7Node01Cell\CPBWebservice.ear\CPBWebservice.war\WEB-INF\conf.

2. Delete axis2.xml.

Release NotesKnown issues © 2014 SAP SE or an SAP affiliate company. All rights reserved. 11

Issue ID Description

ADAPT01709514 In Data Insight, when running a column profiling task with the Median & Distribution and the Word Distributed option selected, the following warning message is shown.

The auto refresh of the task <task_name> in project <project_name> has exceeded. Use the Refresh button to check the status.

However, the task never completes.

Workaround: Have your Unix administrator change the value of ulimit-n to a value of 4096.

ADAPT01706509 Associating a custom content type with a column that contains Unicode data is not supported in Data Insight. Therefore, if you have data in a column that, for example, contains both English and Chinese, the results for content type profiling are based on the English data only for custom content types. The Chinese is not recognized nor in­cluded in the results.

h

ADAPT01702019 In Excel workbooks, if a column contains more than one data type, or multiple text alignments, one of the data types will be set to null.

Workaround: Refer to the following Microsoft support link for workarounds for this de­

sign limitation: http://support.microsoft.com/kb/194124

ADAPT01691524 When promoting a cleansing package via the Central Management Console (CMC), the promoted cleansing package might appear in a Ready state in the promoted destina­tion environment even though the cleansing package is still in the process of being pro­moted. If you open the cleansing package before it has been fully promoted, the cleansing package will be corrupt and the EIMAdaptiveProcessingServer will restart.

Workaround: Check the Promotion Management within the CMC to ensure the job has completed successfully before opening the cleansing package in Cleansing Package Builder.

ADAPT01665689 When a rule name or rule dimension name contains Unicode characters, saving failed data to one of the following failed data databases stores the name as question marks (???) in the IS_FD_RULES_INFO table: SAP HANA, Informix IDS, MySQL, Netezza, Sybase ASE, Sybase IQ, and Teradata.

ADAPT01660813 Information Steward reports are only available in English, regardless of the set local­ized language. If you are using Information Steward in a language other than English and click View Reports in the top right corner, the Reports window shows trans­lated links and descriptions. However, when you click a link to a report, the Parameters window and the generated report are not translated.

ADAPT01652309 Starting JBoss Application Server 5.0.1 when Information Steward is deployed with the SAP BusinessObjects Business Intelligence (BI) platform dswsbobje component shows an error on startup. This error can be ignored as it has no effect on Information Steward.

12 © 2014 SAP SE or an SAP affiliate company. All rights reserved.Release NotesKnown issues

Issue ID Description

ADAPT01628665 You might encounter an invalid keycode error during installation. This is likely due to some client tools installed on desktop deployments. For information, see SAP Note

1707707 .

ADAPT01623284 When testing a rule for which invalid input values require conversion to a number, the results are inconsistent. For example, if "26 JUL 1997" or a blank value is entered as input, the data passes the rule. However, if "25 JUL 1996" is entered as input, the data fails the rule.

ADAPT01555974 In Cleansing Package Builder Design mode, or in the Create Custom Cleansing Package wizard, while importing a list of standard forms or variations using a Microsoft Excel file or a comma separated value (CSV) file, the following behaviors may occur:

● In an Excel worksheet containing duplicate column names, all column names are visible in the list of column names in the dialog box. However only the first instance of the duplicate column name may be selected.Workaround: Rename duplicate column names so that each column name in the worksheet is unique.

● While an Excel file is selected during an import operation within Cleansing Package Builder, you cannot use Excel to modify and save the file.

● In an Excel worksheet, if the columns do not contain an equal number of records, data from a column other than the selected column may be imported in error.Workaround: Ensure that each column in the worksheet contains an equal number of rows so that there are no empty cells. To avoid duplicate data warning mes­sages, ensure your data is unique.

● When importing standard forms or variations in Design mode using a CSV file, an empty field within a record column causes the import process to stop and a mes­sage indicates that the value already exists in the cleansing package. Standard forms or variations imported before the empty field are saved.Workaround: Before beginning the import process, ensure that all fields within the desired record column are populated. You may duplicate data to fill empty fields. To avoid duplicate data warning messages, ensure your data is unique.

ADAPT01525554 In Information Steward, the type of connection established when SSL is enabled is not supported by Metadata Management 3.x. As a result, during a test connection, all at­tempts to log on to Metadata Management 3.x will fail with a communication error. This does not prevent the integrator from running.

ADAPT01523082 In Cleansing Package Builder, a custom cleansing package is usually available in De­sign and Advanced modes. If you manually create or modify a parsing rule in Advanced mode and that rule is invalid, when you switch to Design mode an error message dis­plays and Cleansing Package Builder closes the cleansing package.

Workaround: Reopen the cleansing package and edit the parsing rule so it is valid. Close and then reopen the cleansing package to continue working.

Release NotesKnown issues © 2014 SAP SE or an SAP affiliate company. All rights reserved. 13

Issue ID Description

ADAPT01520065 A profiling task fails when the same Data Services job server is associated with both the Information Steward and Data Services repositories.

Workaround: Create separate Data Services job servers for Information Steward and Data Services.

ADAPT01517520 Redundancy profiling tasks fail in the following cases:

● Two SAP extractors, one SAP extractor, and one virtual view based on another SAP extractor.

● Two virtual views based on two SAP extractors.

ADAPT01512202 Information Steward installer fails when there are two File Repository Servers (FRS) installed, but they point to different physical locations. This issue is due to a limitation on the SAP BusinessObjects Business Intelligence platform.

ADAPT01393699 Schema Name for tables collected by SAP BusinessObjects Enterprise Metadata Integrator is displayed as “Unknown schema name for <Universe Name>” for Uni­verses using MySQL connection. This issue is resolved in this release for the case where the same MySQL ODBC DSN is available where the SAP BusinessObjects Enterprise Metadata Integrator is run.

ADAPT01278734 The display of search results and lineage information is not limited to that information for which the user has access permission.

ADAPT01275081 When installing this product on a CMS cluster, you must use the physical machine name of the CMS server.

ADAPT01263270 If a Data Services job uses the Table_Comparison transform, Metadata Management will not show the impact and lineage on the same table.

ADAPT00619242 Information Steward loses connection to the Information Steward repository when the following situations occur:

● Restarting the Information Steward repository database server.● Disconnecting from and reconnecting to the Information Steward web server to

the network.

To recover from this error, restart the web server on which the Information Steward web application is running.

14 © 2014 SAP SE or an SAP affiliate company. All rights reserved.Release NotesKnown issues

6 Fixed issuesThis section contains a list of issues that have been fixed in the SAP Information Steward 4.2 SP3 (14.2.3) release. The list includes the fixes that are forwarded from the previous patches and additional fixes in this release.

6.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.

Information Steward release version KBA release notes

4.2 Patch 2.1 2047601

4.2 Patch 1.4 2026765

4.1 Patch 3.2 2026821

6.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 speaking to SAP Customer Support.

Issue ID Description

ADAPT01732346 Publish Lineage Utility fails with the error "ORA-00933: SQL command not properly ended" when the highest level to determine whether two related objects are same is set to database. This issue has been resolved in this release.

ADAPT01732345 A user who has 'View objects' rights for the project and a failed rule connection cannot ex­port the failed data. This issue has been fixed in this release.

ADAPT01731926 When exporting a project from Information Steward 4.1 SP2 and importing it to Informa­tion Steward 4.2 SP1, the Low Threshold and High Threshold of KDD is changed, and its description is not imported. This issue has been fixed in this release.

ADAPT01731820 Business Objects Enterprise Integrator does not collect all reports from a folder, when re­port collection is restricted to a folder. This issue has been resolved in this release.

ADAPT01731592 When running the ISRepositoryUtility with the recover option, some rule tasks are deleted. This issue has been fixed in this release.

ADAPT01730556 When testing rules which use match_regex functionality in Information Steward, it gives different results. This issue has been fixed in this release.

Release NotesFixed issues © 2014 SAP SE or an SAP affiliate company. All rights reserved. 15

Issue ID Description

ADAPT01729022 After migrating from Information Steward 4.1 SP1 to 4.2 SP1, some scores do not display and a red icon appears next to all levels of the scorecard. This issue has been fixed in this release.

ADAPT01728069 After a Metapedia term is approved, the following issues occur:

● The user cannot see the end of the term name when there is a long item name.● The user cannot select the text to copy and paste.● The user cannot move the pointer along to view the end of the term that has been

truncated on the screen.

These issues have been fixed in this release.

16 © 2014 SAP SE or an SAP affiliate company. All rights reserved.Release Notes

Fixed issues

7 SAP information resourcesA 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:

Address Content

Customer Support, Consulting, and Education serv­ices

http://service.sap.com/

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

Product documentation

http://help.sap.com/bois/

User Guide, Administration Guide, and other documen­tation for SAP Information Steward.

Supported platforms (Product Availability Matrix)

https://service.sap.com/PAM

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

Product tutorials

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

Tutorials that have been developed to help you find an­swers to the most common questions about using SAP Information Steward.

Forums on SCN (SAP Community Network )

http://scn.sap.com/community/businessobjects-in­

formation-steward

Discussions that include information and comments from other SAP users and the means to share your knowledge with the community.

EIM Wiki page on SCN

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

+Home

The means with which to contribute content, post com­ments, and organize information in a hierarchical man­ner to so that information is easy to find.

Release NotesSAP information resources © 2014 SAP SE or an SAP affiliate company. All rights reserved. 17

Important Disclaimers on Legal AspectsThis document is for informational purposes only. Its content is subject to change without notice, and SAP does not warrant that it is error-free. SAP MAKES NO WARRANTIES, EXPRESS OR IMPLIED, OR OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

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 specifically disclaims any liability with respect to this document and no contractual obligations or commitments are formed either directly or indirectly by this document.

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. Regarding link classification, see: http://help.sap.com/disclaimer.

18 © 2014 SAP SE or an SAP affiliate company. All rights reserved.Release Notes

Important Disclaimers on Legal Aspects

Release NotesImportant Disclaimers on Legal Aspects © 2014 SAP SE or an SAP affiliate company. All rights reserved. 19

www.sap.com/contactsap

© 2014 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.