Is 42 Release Notes En

7/27/2019 Is 42 Release Notes En

http://slidepdf.com/reader/full/is-42-release-notes-en 1/30

■ SAP Information Steward 4.2 (14.2.0.0)

2013-05-06

Release Notes



© 2013 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may bereproduced or transmitted in any form or for any purpose without the express permission of SAP AG.

Copyright

The information contained herein may be changed without prior notice. Some software products

marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP AG and itsaffiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials.The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should beconstrued as constituting an additional warranty. SAP and other SAP products and services mentionedherein as well as their respective logos are trademarks or registered trademarks of SAP AG inGermany and other countries. Please seehttp://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademarkinformation and notices.

2013-05-15



Contents

Compatibility update...............................................................................................................5Chapter 1

Restrictions update.................................................................................................................7Chapter 2

Installation and upgrade considerations.................................................................................9Chapter 3

Known issues .......................................................................................................................13Chapter 4

Fixed issues...........................................................................................................................23Chapter 5

Content enhancements.........................................................................................................25Chapter 6

Export option for source data and failed data..........................................................................256.1

SAP Information Resources .................................................................................................27Chapter 7

Index 29

2013-05-153



2013-05-154

Contents



Compatibility update

Before upgrading to Information Steward 4.2, ensure that the following prerequisite software has beeninstalled:

• SAP BusinessObjects Business Intelligence (BI) platform 4.0 SP5 or higher compatible patches

or

SAP BusinessObjects Information platform services (IPS) 4.0 SP5 or higher compatible patches

Note:

Information Steward 4.2 includes the new Data Cleansing Advisor feature. BI and IPS must beupgraded to 4.0 SP5 patch 4 before you can access Data Cleansing Advisor.

• SAP BusinessObjects Data Services 4.2 or higher compatible patches

For more information on the compatibility of Data Services with BI platform or IPS versions, seeSAP 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 SAPService Marketplace: https://service.sap.com/PAM. To go directly to Information Steward, enter "Information Steward" in the search field.

2013-05-155


https://websmp208.sap-ag.de/sap/support/notes/1740516



https://service.sap.com/PAM







2013-05-156




Restrictions update

The 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 BusinessObjectsBusiness Intelligence platform side-by-side environment (two versions of BusinessObjects Enterpriseon 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. Wheninstalling Information Steward, use Enterprise authentication. After installation is completed, youcan switch to Windows AD/LDAP/SAP authentication.

• The Data Insight module of Information Steward cannot export more than 250 columns of data to aMicrosoft Excel file.

Currently, Data Insight supports exporting data to Microsoft Excel 2007 and older and does notsupport 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.

Data Services Integrator

• The Metadata Management module of Information Steward does not support the following DataIntegrator 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.

Note:

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

2013-05-157

Restrictions update



BusinessObjects Enterprise Metadata Integrator

• The BusinessObjects Enterprise Metadata Integrator does not collect metadata for the followingobjects:

• 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 areusing the Designer before you run the BusinessObjects Enterprise Metadata Integrator on the samecomputer.

Metadata Management

• The Metadata Management module of Information Steward does not export objects collected by theMITI Metadata Integrator.

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

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

Note:Qualify 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 tablesas 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-targetrelationship between the view and the table or tables upon which the view is based and displaysthe following warning message:

Unable to parse SQL: <error message>

Note:The Metadata Integrators collect the SQL statement and Metadata Management displays it. Analyze the SQL statement in Metadata Management and establish a user-defined relationshipfor 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 SAPSybase PowerDesigner version 16.0 and older, you need to continue to use the Meta IntegrationMetadata Bridge (MIMB) metadata integrator for SAP Sybase PowerDesigner metadata collection.

2013-05-158

Restrictions update



Installation and upgrade considerations

SAP 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 theprevious version).

Full installation

The Information Steward 4.2 installer automatically detects whether a version of Information Stewardis already installed and then follows the appropriate workflow. If Information Steward is not alreadyinstalled 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 Information Steward 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:

• (Upgrade existing installation) BI 4.0 SP2 + BI 4.0 patch 2.13 (or above) + Data Services 4.0.x +Information Steward 4.0.x + BI 4.0 SP4 patch + Data Services 4.1 SP1 + Information Steward 4.1SP1 + BI 4.0 SP5 patch + Data Services 4.2 + Information Steward 4.2

• (New installation) BI 4.0 SP4 (Full installation) + BI 4.0 SP5 patch + Data Services 4.2 + InformationSteward 4.2

Upgrade installation

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

• If Information Steward is not already installed on the system, the installer goes through the fullinstallation.

For full installation instructions, see the Information Steward Installation Guide . Also, see SAP Note1570523 for additional installation and configuration troubleshooting tips.

• If an existing version of Information Steward is installed, the installer performs an upgrade installation.

2013-05-159










For information about upgrading your Data Services and Information Steward landscape, see theData Services and Information Steward Master Guide . For more information about possible upgradescenarios, see SAP Note 1723435 .

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

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 moreinformation, 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 fullfunctionality of all Information Steward modules and features, you must obtain and install a full InformationSteward or Information Steward – Multi-Source Metadata Integrators by MITI license key. For moreinformation, contact your SAP account executive.

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

Name in CMCInformation Steward moduleUpgrade from...

Meta Integra- tion BridgeMetadata Inte-grator (MITI)

Metapedia

Meta-data

Man-age-ment

Cleans-ing

Pack-ageBuilder

Data In-sight

SAP BusinessObjects In-formation Steward – Plat-form for Data Insight

√BusinessOb- jects Data In-sight

SAP BusinessObjects In-formation Steward – Plat-formfor Metadata Manage-ment

√√BusinessOb- jects MetadataManagement

SAP BusinessObjects In-formation Steward – Plat-formfor Metadata Manage-ment with Multi-SourceSource Metadata Integra-tors by MITI

√√√

BusinessOb- jects MetadataManagement /MITI

2013-05-1510








Name in CMCInformation Steward moduleUpgrade from...

Meta Integra- tion Bridge

Metadata Inte-grator (MITI)

Meta

pedia

Meta-data

Man-age-ment

Cleans-ing

Pack-ageBuilder

Data In-

sight

Data Services√√SAP Busines-sObjects DataServices

Data Quality ManagementPremium

√√SAP Busines-sObjects DQM

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 ManagementServer (CMS). You must either obtain a full version of Information Steward or deploy the upgradedversions of Data Insight and Metadata Management to separate CMS systems.

2013-05-1511




2013-05-1512




Known issues

This section lists known issues in descending order by SAP ADAPT system Problem Report trackingnumber. We also use these numbers in the release notes that accompany our fix packs and patches.You can reference the tracking number when searching for the issue on our knowledge base or whenspeaking to Customer Assurance.

DescriptionIssue ID

If you run a column profiling task using HANA tables with more than 330 columns,the job might fail.

Workaround: Disable the HANA pushdown by setting the following property beforerunning the column profiling task.

1. Open the MM.properties file in the <SAP BIP install

dir>\InformationSteward\config\ folder.

2. Change the following property:

enableNewDBOptimization=false

ADAPT01693283

When promoting a cleansing package via the Central Management Console (CMC),the promoted cleansing package might appear in a “Ready” state in the promoteddestination environment even though the cleansing package is still in the process of being promoted. If you open the cleansing package before it has been fully promoted,the cleansing package will be corrupt and the EIMAdaptiveProcessingServer willrestart.

Workaround: Check the Promotion Management within the CMC to ensure the jobhas completed successfully before opening the cleansing package in CleansingPackage Builder.

ADAPT01691526

If you connect to a remote CMS during a primary installation of Information Steward,

configuring the IS repository will fail.Workaround: After the installation completes, restart the CMS manually, and thenuse the ISRepositoryUtility to re-create the repository and finish the installation byfollowing the post-installing instructions.

ADAPT01689065

2013-05-1513

Known issues



DescriptionIssue ID

When you use Promotion management console to migrate existing InformationSteward objects during an upgrade installation, integrator source groups and integrator

run histories are not migrated properly.

Workaround: You can recreate only the integrator source groups but you cannotrecreate the integrator histories.

1. Login to the CMC as Administrator.

2. Navigate to Information Steward > Metadata Management.

3. Click Manage > New > Source Group.

4. Enter a name for your source group, select the integrator sources to add to thissource group, and click Save.

ADAPT01668672

When a rule name or rule dimension name contains Unicode characters, saving faileddata 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.

ADAPT01665689

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 translated links anddescriptions. However, when you click a link to a report, the "Parameters" windowand the generated report are not translated.

ADAPT01660813

If you initially configured an Information Steward repository using one type of databasein a previous version of Information Steward installation, and then switched therepository to use a different type database via ISRepositoryUtility tool, when upgradingto IS 4.2 the initial database information is pre-populated on the repository information

screen.

Workaround: Manually update the repository connection information using the seconddatabase connection information.

ADAPT01657755

2013-05-1514

Known issues



DescriptionIssue ID

Viewing Data Services Auto Documentation fails while analyzing the lineage of a

Data Services integrator source column after upgrading from Information Stewardversion 4.0.

Workaround: Remove and re-add the Data Services Administrator Service as follows:

1. Log on to the Central Management Console (CMC) as administrator.

2. Navigate to Servers > Enterprise Information Management Services.

3. Right-click EIMAdaptiveProcessingServer , and click Stop Server . Wait for theserver to stop.

4. Right-click EIMAdaptiveProcessingServer , and click Select Services.

5. Remove the Data Services Administrator Service.

6. Click OK.


8. Add the Data Services Administrator Service.9. Click OK.

10. Navigate to the <BOE_Install> \SAP BusinessObjects Enterprise XI

4.0\java\pjs\container\work folder.

11. Delete the <Node_Name> .EIMAdaptiveProcessingServer directory.

12. Right-click EIMAdaptiveProcessingServer , and click Start Server . Wait for theserver to start.

ADAPT01656567

2013-05-1515

Known issues



DescriptionIssue ID

The Log Level properties are not displayed correctly for Data Services MetadataBrowsing and View Data Services in the Central Management Console (CMC) after

upgrading from Information Steward 4.0 SP2 to Information Steward 4.1 or 4.1 SP1.

Workaround: Remove and re-add the Data Services Metadata Browsing Service andView Data Service as follows:

1. Log on to the CMC as administrator.

2. Navigate to Servers > Enterprise Information Management Services.

3. Right-click EIMAdaptiveProcessingServer , and click Stop Server . Wait for theserver to stop.


5. Remove the Data Services Metadata Browsing Service.

6. Remove the Data Services View Data Service.

7. Click OK.


9. Add the Data Services Metadata Browsing Service.

10. Add the Data Services View Data Service.

11. Click OK.

12. Right-click EIMAdaptiveProcessingServer , and click Start Server . Wait for theserver to start.

13. If you need to change the Log Level for either of these services:

a. Right-click EIMAdaptiveProcessingServer , and click Properties.

b. Scroll down to Data Services View Data Service and the Data Services Meta-data Browsing Service sections, and change the Log Level.

c. Click Save.

d. Restart EIMAdaptiveProcessServer.

ADAPT01654235

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

ADAPT01652309

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

ADAPT01628665

When you configure a Metadata collection on a SAP BusinessObjects Business In-telligence (BI) platform 4.0 FP3 system for a CMS that has an earlier SAP Busines-sObjects Business Intelligence (BI) platform 4.0 version installed, you may see thefollowing error message when you collect reports: "Unable to open report. The max-imum connection limit has been reached."

ADAPT01628180

2013-05-1516

Known issues

https://service.sap.com/sap/support/notes/1707707






DescriptionIssue ID

At the end of any mode of installation (including uninstallation), the UNIX installer

incorrectly states: “Click Finish to exit this installation” (or “uninstallation”). It shouldstate: “Press [Enter] to exit this installation”. ADAPT01623686

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 enteredas input, the data passes the rule. However, if "25 JUL 1996" is entered as input, thedata fails the rule.

ADAPT01623284

A profiling task fails when a column name contains an apostrophe ('). ADAPT01563343

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

• In an Excel worksheet containing duplicate column names, all column names arevisible in the list of column names in the dialog box. However only the first instanceof the duplicate column name may be selected.

Workaround: Rename duplicate column names so that each column name in theworksheet is unique.

• While an Excel file is selected during an import operation within Cleansing PackageBuilder, 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 amessage indicates that the value already exists in the cleansing package. Standardforms or variations imported before the empty field are saved.

Workaround: Before beginning the import process, ensure that all fields within thedesired record column are populated. You may duplicate data to fill empty fields.To avoid duplicate data warning messages, ensure your data is unique.

ADAPT01555974

2013-05-1517

Known issues



DescriptionIssue ID

In Cleansing Package Builder, after importing a custom (Universal Data Cleanse)

Data Services 3.2 dictionary that contains more than one category, you may be unableto enter a new standard form in the "When used as" area of the Manage Classificationsand Variations tab in Advanced mode.

The standard form field in the "When used as" area is unavailable for variationscontained in the attribute with the same name as the category name. For example,if your Data Services 3.2 dictionary had PAPER SIZE and MANUFACTURER cate-gories, by default Data Services 3.2 created attributes with the same names (PAPERSIZE, MANUFACTURER). You may have created additional attributes within either of the categories. You cannot edit standard forms of variations within the PAPERSIZE or MANUFACTURER attributes, however you can edit standard forms withinany additional attributes that you created.

ADAPT01553294

In Cleansing Package Builder Design mode, when the first action after opening acustom cleansing package is to add more sample data, Cleansing Package Builder generates rules and statistics only for the newly added records, not the entire sampledata set.

Either of the following workarounds will prevent the problem from occurring.

Workaround 1: After opening a cleansing package, always perform a drag and dropoperation or search before adding more sample data.

Workaround 2: If you have already opened a cleansing package and immediatelyadded more sample data, close the cleansing package. Then reopen it and performa drag and drop operation.

ADAPT01524632

In Cleansing Package Builder, a custom cleansing package is usually available inDesign and Advanced modes. If you manually create or modify a parsing rule in Ad-vanced mode and that rule is invalid, when you switch to Design mode an error message displays 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.

ADAPT01523082

2013-05-1518

Known issues



DescriptionIssue ID

In rare occasions, the ISJobServer or EIMAdaptiveProcessingServer are not added

to the CMS server list for that server node, even though the corresponding componentswere selected and the installation finished with success.

When this issue occurs, run the Add Node Wizard from Central Configuration Man-ager, and follow the steps below:

1. Stop the Server Intelligence Agent.

2. Using the command line, go to the scripts directory in the SAP BusinessObjectsEnterprise folder.

For example, for Windows go to <SAP BusinessObjects Installdir>\SAP

BusinessObjects Enterprise XI 4.0\win64_x64 and for Linux go to<SAP BusinessObjects

Installdir>\enterprise_xi40\linux_x64/scripts .

3. Run the following command:

addnode -name <SIA name> -cms <CMS server > -username Administrator -password <CMS Administrator

password > -authentication secEnterprise -usetempcms-update

For example:

addnode -name node01 -cms machine:6400 -username Administrator -password "" -authentication secEnterprise -usetempcms -update

ADAPT1522843

On Linux, if the Listener Port or JMXConnector Port is specified out of range (1000,

10000) during installation you cannot change any settings for the Data Services ViewData Service and Data Services Metadata Browsing Service in EIMAdaptiveProcess-ingServer from CMC.

ADAPT01521649

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

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

ADAPT01520065

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.

ADAPT01517520

2013-05-1519

Known issues



DescriptionIssue ID

When re-installing Information Steward on a machine where it was previously installed,during the post process check-up some problems are found due to missing services.

This is a known issue because of uninstallation.

Possible symptoms:

• <node>.ISJobServer is not installed

• <node>.EIMAdaptiveProcessingServer is not installed or some important services(Metadata Search Service, Metadata Relationship Service, etc.) are not part of the EIMAdaptiveProcessingServer.

• When adding the required services to either one of the servers (ISJobServer,EIMAdaptiveProcessingServer) via CMC, it shows the error “The edge betweenobjects <#id> and <#id2> does not exist.”

• Problems during runtime which lead to some missing components.

To fix this issue, perform the following steps:1. Do one of the following:

• In Windows, run the batch MMServiceInstaller from <SAP BIP

Install>\InformationSteward\MM\bin .

• In Linux, run the shell script MMServiceInstaller.sh from <SAP BIP

Install>/InformationSteward/MM/bin .

2. Pass arguments for the CMS credentials and the component installed on themachine. The component argument is optional. Leave it empty if you want to installall components. For example:

MMServiceInstaller boePassword <pass> [boeServer localhost] [boeUser Administrator ][-component (all|task|integrator|search|relationship|cpb|viewdata|metadata)]

3. Do one of the following:

• If the default server ISJobServer was not installed, and it was installed anyIntegrator or Task server on the machine, do the following:

a. Login to CMC > Servers.

b. Click Manage > New > New Server .

c. Select "Service Category "Enterprise Information Management Services.

d. If Integrator was installed, select "Service "Information Steward Integrator

Scheduling Service.

e. Add service “Information Steward Task Scheduling Service”; if Task Server was installed.

f. Finish the server creation.

• If any Integrators were installed, in CMC > Servers, add the newly createdISJobServer to the Job Server groups corresponding to the installed Integrators.

ADAPT01516162

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

ADAPT01512202

2013-05-1520

Known issues



DescriptionIssue ID

Schema Name for tables collected by SAP BusinessObjects Enterprise MetadataIntegrator is displayed as “Unknown schema name for <Universe Name>” for Univers-

es using MySQL connection. This issue is resolved in this release for the case wherethe same MySQL ODBC DSN is available where the SAP BusinessObjects EnterpriseMetadata Integrator is run.

ADAPT01393699

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

ADAPT01278734

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

ADAPT01275081

When you install Information Steward on a SAP BusinessObjects Enterprise (BOE)cluster environment (more than one CMS), you must reduce to one CMS to installthis product. After installation, you can use any other CMS in the cluster.

ADAPT01275056

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

ADAPT01263270

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

ADAPT01525554

Deski reports link to the wrong universe if there are multiple universes with the samename.

ADAPT01086061

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 tothe network.

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

ADAPT00619242

2013-05-1521

Known issues



2013-05-1522

Known issues



Fixed issues

The fixed issues in Information Steward 4.2 are listed below in descending order by the internal issueidentification tracking number. You can reference the tracking number when searching for the issue onour knowledge base or when speaking to SAP Business User Support.

DescriptionIssue ID

When profiling or viewing data on an SAP Extractor, an error is generated

about a method and type not being supported. This issue has been fixed inthis release.

ADAPT01685515

Installing Information Steward on the local server as an expanded installationafter an IS repository has already been created on that server is now allowed- but only the web component feature is allowed. A warning about this restric-tion is posted when the expanded installation choice is made on the localserver. This issue has been fixed in this release.

ADAPT01661739

The issues fixed in previous patches are included in this release. The following table lists the release

and patch versions and the associated SAP Note where you can find the Release Notes for that version.SAP NoteInformation Steward version

18492524.2

18439784.1 SP1 Patch 0.1

17951504.1 SP1

18102524.0 SP3 Patch 3

17951804.0 SP3 Patch 2

2013-05-1523

Fixed issues













2013-05-1524

Fixed issues



Content enhancements

6.1 Export option for source data and failed data

An option for exporting failed data is incorrectly documented in the “Exporting all failed data” topic inthe Information Steward User Guide . The option appears when users export failed data (data that faileda rule). When users click Export Data, an "Export Options" dialog box opens with three options. The

first option in the "Export Options" dialog box is documented as Export all data to CSV file. However,in this version of Information Steward, the option is actually labeled Export to CSV. Each export optionin the "Export Options" dialog box provides a choice of what data to export and in what format to exportas the table below explains.

DescriptionExport option

Exports all failed data to a CSV file.Export to CSV

Exports all columns and rows of the failed data based on the Show

Columns, Filter Criteria, and Sort Criteria options set in the "FailedData" dialog. The data is exported to a CSV file.

Export filtered data to CSVfile

Exports 500 rows of the failed data that is currently showing in the "FailedData" window directly to Excel.

Export data from current viewto Excel

In addition, the three export options also apply to exporting source data. However, the documentationfor exporting source data does not currently include the three options (“Exporting viewed data”).

2013-05-1525




2013-05-1526




SAP Information Resources

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

Useful addresses at a glance:

Content Address

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

Customer Support, Consulting, and Education

serviceshttp://service.sap.com/

User Guide, Administration Guide, and other documentation for SAP Information Steward.

Product documentation

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

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

Supported platforms (Product Availability Matrix)


Tutorials that have been developed to help you

find answers to the most common questions aboutusing SAP Information Steward.

Product tutorials

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

Discussions that include information and com-ments from other SAP users and the means toshare your knowledge with the community.

Forums on SCN (SAP Community Network )

http://scn.sap.com/community/businessobjects-information-steward

The means with which to contribute content, postcomments, and organize information in a hierar-chical manner to so that information is easy tofind.

EIM Wiki page on SCN

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

2013-05-1527


http://service.sap.com/

http://help.sap.com/bois













http://help.sap.com/bois

http://service.sap.com/



2013-05-1528




Index

C

compatibility 5

E

export change 25

F

failed data 25

fixed issuesversion 14.2.0 23

K

known issuesversion 14.2.0 13

R

restrictions 7

U

upgrade considerationsversion 14.2.0 9

2013-05-1529



Index

Date post:	14-Apr-2018
Category:	Documents
Upload:	odod
View:	213 times
Download:	0 times

Is 42 Release Notes En

Documents