Select language:

SAP NetWeaver MDM 7.1 SP06

The scope of this release focuses on the following key areas to improve overall quality, efficiency, and use of the software:

  • Stability. Reduce system crashes, memory dumps, and unexplained shutdowns.
  • Performance. Improve throughput, import/export speed, and utilization of hardware.
  • Locking. User responsiveness, repository locking, database locking, and more.
  • Supportability. Improved TCO, maintenance, and root cause analysis.
Bug Fixes

For an extensive list of bug fixes available in SAP NetWeaver Master Data Management (MDM) 7.1 SP06, see SAP Note 1471203Information published on SAP site.

Improvements Available in this Release

As of SAP NetWeaver MDM 7.1 SP06, the following improvements are available:

Event Notification Filtering

Improvement

Description

MDS Event Notification Service

Previously, operations causing massive record updates (such as imports, workflows, and taxonomy modifications) would reduce Master Data Server (MDS) response time and cause users to experience frequent lock-ups or hourglass/busy states in MDM clients.

To prevent this from occurring, MDS now provides an event notification service for client applications interested in being alerted about events happening to the server and to master data.

MDM Data Manager now filters notifications for records that are not part of a current search selection

Previously, MDM Data Manager processed every notification sent from MDS related to records in a repository, regardless of whether the notifications affected the record set being worked on in the current MDM Data Manager session. This could cause noticeable performance degradations. Now, Data Manager automatically filters out notifications which do not relate to the record set resulting from the current search selections.

Event notification filtering available in Java and .NET APIs

It is now possible to filter event notifications by registering for notifications from specific groups using the following interfaces:

  • GlobalEventRegistrationSet
  • ServerEventRegistrationSet
  • RepositoryEventRegistrationSet
  • DataEventRegistrationSet 

More information: Events → Registering for Events 

Improved Matching

Improvement

Description

Required Fields for Matching

A new Required Fields pane has been added to the Strategies tab of the MDM Data Manager, enabling users to select the fields by which MDM partitions records before matching in order to improve matching performance.

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Data Manager Reference Guide → Part 8: Matching Mode → Matching Strategy Definition

Slicing of Mass Updates to Improve Performance in Multi-User Environments

Improvement

Description

New mds.ini parameters for enabling slicing of non-bulk operations

The following mds.ini parameters have been added for enabling the slicing of non-bulk operations:

  • Enable Slicing For Non-Bulk Operations, defaulting to False
  • Enable Checkin Slicing, defaulting to False
  • Enable Checkout Slicing, defaulting to False
  • Enable Assignment Slicing, defaulting to False
  • Enable Record Edit Slicing, defaulting to False

The Enable Slicing For Non-Bulk Operations parameter acts as a master "on/off" switch for non-bulk operation slicing. When it is set to False, slicing is disabled for all non-bulk operations. When it is set to True, slicing behavior is determined by the operation-specific slicing settings

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 7: MDS Administration → Optimizing Performance During Updates

New mds.ini parameters for configuring slice size and wait times for non-bulk operations

The following mds.ini parameters have been added for configuring the number of records to include in a slice for non-bulk operations:

  • Default Slice Size, defaulting to 500
  • Checkin Slice Size, defaulting to 500
  • Checkout Slice Size, defaulting to 500
  • Assignment Slice Size, defaulting to 500
  • Record Edit Slice Size, defaulting to 500

The following mds.ini parameters have been added for configuring the number of milliseconds to wait between slices for non-bulk operations:

  • Default Slice Wait Time MS, defaulting to 300
  • Checkin Slice Wait Time MS, defaulting to 300
  • Checkout Slice Wait Time MS, defaulting to 300
  • Assignment Slice Wait Time MS, defaulting to 300
  • Record Edit Slice Wait Time MS, defaulting to 300

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 7: MDS Administration → Optimizing Performance During Updates

Changed mds.ini parameters for bulk operations (import, API)

The following mds.ini parameters have been added for configuring the number of records to include in a slice and the number of milliseconds to wait between slices for bulk operations (import, API):

  • Bulk Operation Slice Size, defaulting to 500
  • Bulk Operation Slice Wait Time MS, defaulting to 300

These new parameters replace the following MDM 7.1 mds.ini parameters that existed before: Import Slice Size, Import Slice Size Min, Import Slice Size Max, and Import Sleep Time Max. If these old parameters are present in an mds.ini file, a warning is entered in the MDS log and their settings will be ignored in favor of the new default parameters.

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 7: MDS Administration → Optimizing Performance During Updates

API updates that enable implementation of slicing

  • Java and .NET APIs:

To enable optimization of lengthy record operations with slicing, new methods have been added to the following commands:

  • CheckoutRecordsCommand
  • CheckinRecordsCommand 
  • ExecuteAssignmentCommand 

More information: Optimizing Record Checkouts with Slicing

  • ABAP API:

To enable the implementation of slicing, the following new parameters were added to the CHECKIN and CHECKOUT methods:

  • IV_IS_SLICED
  • ET_FAILED_RECORDS

More information:

Interface IF_MDM_CORE_SERVICES

Counting, Archiving, and Deleting Workflow Jobs

Improvement

Description

CLIX command for counting workflow jobs

New CLIX command for counting workflow jobs:

CLIX repGetCountWorkflowJobs MDSHostSpec RepositorySpec [-A] [-C] [-L] [-#port]

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 14: CLIX Command Line Interface

CLIX command for deleting workflow jobs

New CLIX command for deleting workflow jobs:

CLIX repRemoveCompletedWorkflowJobs MDSHostSpec RepositorySpec Credentials NumberOfDays NumberOfJobs

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 14: CLIX Command Line Interface

MDM Data Manager feature for archiving completed workflow jobs

The following enhancement allows MDM Data Manager to archive completed workflow jobs:

  • A new operation, Archive, is added to the context menu in the Jobs table.
  • A new state, Archived, is added to the Workflow tab.
  • A new Archived Jobs grid is added to the Workflow tab.
  • New operations, View History and Delete, are added to the context menu in the Archived Jobs grid.

More information: http://service.sap.com/installmdm71Information published on SAP site→MDM Data Manager Reference Guide → Part 3: Record Mode → MDM Workflows

MDM Data Manager feature for displaying workflow job count

MDM Data Manager now reports the number of workflow jobs present for each workflow state.

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Data Manager Reference Guide → Part 3: Record Mode → MDM Workflows

Archive Enhancements

Improvement

Description

Parallel Archive/Unarchive

Improvements to the Archive/Unarchive feature result in faster archive/unarchive times. The older archive method is still used for archiving by masks, schema-only, and segmented archives.

An optional mds.ini parameter has been added, which allows you to revert all archiving to the old method: Use Old Archiving Method=True

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 7: MDS Administration → MDS Configuration

Smart Record Flattening for XML Imports

Improvement

Description

Import Manager/MDIS

To improve performance and reduce memory usage, XML import files are no longer flattened (converted into multiple virtual extended records) unless the file meets certain criteria.

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Import Manager Reference Guide → Part 3: Record Mode → MDM Workflows

Syndication Enhancements

Improvement

Description

XML Namespaces

For XML maps, a new Namespace field is added to the Create Map and Refresh Map dialog boxes of MDM Syndicator. The field's available values are taken from the namespaces present in the selected root of the map's XSD, and are used to populate namespaces in the syndication file. The Namespace map property is now read-only.

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Syndicator Reference Guide → Part 1:What is XML? →XML and Syndicator → XML Namespaces in Syndicator

Refresh XSD

For XML maps, a new Refresh Map operation in the Syndicator  enables users to refresh a map with any changes made to the map's XML Schema file (.xsd).

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Syndicator Reference Guide → Part 1:What is XML? →XML and Syndicator → XML Schema Enforcement in Syndicator

Increased Availability of Slave Repositories During Synchronization

Improvement

Description

Console field for configuring the wait time between master change applications during a synchronize slave operation

The Confirm Synchronize Slave dialog box now contains a Wait time between master changes field for configuring the number of milliseconds in-between each application of master changes. During the wait time MDS is available to process requests from other clients.

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 6: Repository Administration → Maintaining Master and Slave Repositories → Synchronizing a Slave Repository

New CLIX command for configuring wait time during a synchronize slave operation

New CLIX command for configuring the wait time during a synchronize slave operation:

clix repSynchronize MdsHostSpec slaveRepositorySpec Credentials [-T delay]

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 14: CLIX Command Line Interface

Java and .NET API - New method for configuring wait time during slave synchronization

To configure the wait time between each application of  master changes to a slave repository during synchronization, a new method has been added:

SynchronizeSlaveRepositoryCommand.setDelay

More information: Optimizing Repository Synchronization

Retrieval of MDM Server Versions with CLIX

Improvement

Description

New CLIX commands for retrieving versions of MDM servers

New CLIX commands for retrieving the versions of the MDM servers:

clix svrMDSVersion MDSHost [-# port]

clix svrImportVersion MDSHost [-# port]

clix svrLayoutVersion MDSHost [-# port]

clix svrSyndicationVersion MDSHost [-# port]

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 14: CLIX Command Line Interface

New Checklists for MDM Project Preparation and Business Blueprints

This is a new document that comprises two checklists:

  • Project preparation checklist
  • Business blueprint checklist

The checklists highlight the most critical tasks required by an MDM implementation owner during the project preparation and business blueprint phases to enable an optimal, effective, and successful MDM implementation.

More Information: http://service.sap.com/installmdm71Information published on SAP site → MDM 7.1 Checklists: Project Preparation and Business Blueprint

Support for Installing and Running Multiple MDM Server Components on a Single Machine

Starting from MDM 7.1 SP06, you can install and run multiple MDM server components on one physical machine.

One advantage of installing multiple MDM server components on a single machine, as opposed to loading multiple MDM repositories on a single Master Data Server (MDS), is that parallel execution of imports/syndications to/from loaded MDM repositories is possible. Another advantage is that you can have two repositories for separate projects on two different MDM versions on the same machine-resulting in reduced TCO. (In previous releases you would be required to separate the repositories on two different MDM servers, and adhere to the recommendation that the Master Data Import Server (MDIS) and Master Data Syndicator Server (MDSS) be run on a separate machine from the Master Data Server (MDS)).

Each Master Data Import Server (MDIS) and Master Data Syndicator Server (MDSS) must be configured to work with one particular MDS only.

You can distribute the MDM server components according to the following hardware configuration options:

  • Multiple Master Data Servers on one machine with remote MDM Import/Syndication Servers on a second machine, and a DBMS on a third machine.
  • Multiple Master Data Servers and MDM Import/Syndication Servers on one machine with a remote DBMS on a separate machine.
  • Multiple Master Data Servers, MDM Import/Syndication Servers, and a DBMS all on one machine.

Test results show that hardware sizing parameters are almost identical for all the aforementioned configuration options; therefore the configuring option you choose should be based solely on your preferred hardware setup.

More information:

Performance Improvements

The following table lists the performance-related pain points that were addressed in this release and the improvements that were made. Note that some issues are duplicates of improvements already listed in the tables above.

Pain Point Description of Issue Improvement in this Release

Client response time during concurrent update activities

MDS is unresponsive while waiting for an update operation (record add/modify/delete, check-in/out, and workflow) to complete.

Faster average response time for basic operations (for example, search, single-record update).

MDM Data Manager response time when switching between tabs

Switching between tabs in the MDM Data Manager detail pane (for example, Workflow tab) can take up to 2 minutes.

Faster average response time when switching between tabs in the MDM Data Manager detail pane.

Archive/Unarchive time

Archive and unarchive is slow for large repositories.

Vast improvement for Archive time and high improvement for unarchive time for large repositories.

Repository load time

Loading time for large repositories is slow.

Improvement on both Load (Immediate) and Load (with Indices) times.

Time to create or update records

Multi-record create and update operations are slow.

Large improvement in Multi-record create and update times.

Slave responsiveness during synchronization

Slave repositories are unresponsive during slave synchronization.

Faster response time for basic operations (for example, search, single-record update) on a slave repository during synchronization.

Import time for highly structured XML data

Import of XML data with embedded repeated elements (for example, multi-valued tuples) is slow.

Minor to huge improvement of Import XML data with embedded repeated elements. The improvement factor depends on the number of multivalued element in the XML input file.

Searching for both words and non-words in keyword search

Keyword search is slow when non-words are indexed along with words.

Faster response time for words and non-words in keyword search

Time to execute a matching strategy

Matching strategies are performed inefficiently, resulting in long execution times.

Improved performance using the newly added 'required fields' for matching. The usage of required fields can reduce significantly the size of the target group, and by that significantly reduce the matching time.

MDM Info Collector: New Tool for Creating Snapshots of MDM for Offline Failure Analysis

When you discover a failure with MDM and as a result open a message to SAP Customer Support, you will most likely need to send information that is related to your system so that SAP can perform an offline analysis of the problem. Collecting this information manually can be a very difficult, error prone, and time-consuming task.

The MDM Info Collector tool is a new tool that automatically collects information relating to your MDM setup and landscape, and packages it into a compressed ZIP file-in a single operation. The information can then be used by SAP Customer Support to facilitate and expedite the analysis and resolution of the reported failure. All you need to do is to run the tool and attach the resulting info package to your SAP customer message.

The tool ensures that basic information for analyzing the problem is collected and provided to SAP.

To download the tool and read the documentation, see SAP Note 1522125Information published on SAP site.

MDM Configuration Assistant: New Tool to Help Users with the Configuration of MDM

The new MDM Configuration Assistance tool helps you to configure and optimize MDM correctly from the early stages of any SAP NetWeaver MDM 7.1 implementation. Typically, you would use the tool immediately after installing MDM, but you could also use it later on to change your current MDM configuration.

The major benefits of the tool are:

  • Provides guidance and assistance with configuring MDM in a simple and easy manner and reduces the need for special technical skills or experts, such as DB and OS administrators.
  • Helps with optimizing your environment to ensure that it runs smoothly.
  • Supports for various environments, such as IBM DB2, MaxDB, MS SQL, and Oracle database servers.
  • Detects inconsistent and incorrect settings, and recommends practical solutions.

The first release of the tool helps you to configure MDM correctly so that you can connect your MDS to a DB server.

To download the tool and read the documentation, see SAP Note 1543650Information published on SAP site.

Support for SAP NetWeaver 7.02 (EHP2 for SAP NetWeaver 7.0) and SAP NetWeaver 7.30

  • Support for SAP enhancement package 2 for SAP NetWeaver 7.0 has been qualified for those MDM software components that were already supported by SAP enhancement package 1 for SAP NetWeaver 7.0.
  • Support for SAP NetWeaver 7.30 has been qualified for some MDM software components. For details about the relevant software components, see http://service.sap.com/installmdm71Information published on SAP site → MDM 7.1 Master Guide.

MDM Enrichment Controller: Support for SAP NetWeaver CE 7.11 (EHP1 for SAP NetWeaver CE 7.1) and SAP NetWeaver CE 7.2

As of MDM 7.1 SP06, a new software component for MDM Enrichment Controller is available: MDM ENRICH. CONTROLLER 7.1 7.11 (Enrichment Controller NW 7.11).

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM 7.1 Master Guide

The following topics in the MDM Enrichment Architecture Guide have also been revised accordingly:

Additional Changes in Documentation

In addition to the aforementioned enhancements, the documentation also contains the following updates:

General

  • Prior to the release of this support package, some documentation corrections were already announced in SAP Note 1429115Information published on SAP site (Central SAP Note for MDM 7.1 Documentation Corrections). Any late updates and corrections that did not make it into the MDM 7.1 SP06 documentation publication will also be announced in this SAP Note.
    Note

    We recommend that you subscribe to this SAP Note so that you can be notified automatically when it is updated.

  • Changes have been made in the navigation entries for downloading software components in the Software Download Center (SWDC) on SAP Service Marketplace ( http://service.sap.com/swdc). For example, the "Entry By Application Group" option is no longer available.

    This affects various parts of the MDM documentation where we have documented how to download software components for MDM. For example: Installation Guides, Web Dynpro Components Guide, Web Services Guide, Change Tracker, PI Adapter Guide, Enrichment Architecture, Java and .NET API Guide/.

    We have updated the download procedures in the MDM 7.1 guides as needed.

MDM Master Guide

For information about updates to the SAP NetWeaver MDM 7.1 Master Guide, refer to the Document History section in this guide. The guide is available on SAP Service Marketplace at http://service.sap.com/installmdm71Information published on SAP site.

MDM Installation Guides and Upgrade Guide

For information about updates to the SAP NetWeaver MDM 7.1 Installation Guides and Upgrade Guide, refer to the Document History section in these guides

These guides are available on SAP Service Marketplace at http://service.sap.com/installmdm71Information published on SAP site.

MDM Console

Improvement Description

Newer than Server repository state added

Previously, the same icon and state was used for repositories which were either older or newer than the Master Data Server. Now, a new icon in the Console Hierarchy tree identifies repositories that are newer than the Master Data Server.

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 3: MDM System Access → Accessing MDM Repositories

New CLIX commands for retrieving the number of changes on a master repository that are available for synchronization to a slave repository

New CLIX command for retrieving the number of changes on a master repository that are available for synchronization to a slave repository:

CLIX repGetCountOfMasterChangesAvailableForSync Host Repository Credentials

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 14: CLIX Command Line Interface

Corrupt repository state changed to Restart Required

Previously, the repository state Corrupt caused the wrong impression that user data was corrupt. Now, this state is called Restart Required. It uses the same icon as before.

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 3: MDM System Access → Accessing MDM Repositories

Changed mds.ini parameter for disabling read access to repositories which require restarting

The following mds.ini parameter has been added to disable read access to repositories in the state Restart Required:

Disable Read Access To Repositories That Require Restart (defaulting to False)

This new parameter replaces the following MDM 7.1 mds.ini parameter that existed before: Disable Read Access To Corrupt Repositories.

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 7: MDS Administration → MDS Configuration

Changed mds.ini parameter for verifying DBMS connection before executing SQL statements

The following optional mds.ini parameter has been added to verify DBMS connections before executing SQL statements:

Always Verify DBMS Connection before Executing SQL Statements (defaulting to False)

This new parameter replaces the following MDM 7.1 mds.ini parameter that existed before: Extra DBConnection Validation. If the old parameter is present in an mds.ini file, a warning is entered in the MDS log and its setting will be ignored.

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 7: MDS Administration → MDS Configuration

New mds.ini parameter for setting MaxDB statement cache size

The following optional mds.ini parameter has been added for customizing the number of prepared statements to cache for the connection to a MaxDB DBMS for reuse:

MaxDB Statement Cache Size (defaulting to 1000)

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 7: MDS Administration → MDS Configuration

Master change time logged immediately after SQL operations instead of waiting for in-memory structures to be updated

This change improves the reliability of master-slave synchronization by logging only the time required for the preparatory and SQL phases of master change operations. Previously, the time required to update in-memory structures was also included.  The master change time displayed in slave synchronization dialogs reflects this change.

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 6: Repository Administration → Maintaining Master and Slave Repositories → Synchronizing a Slave Repository

Syndication timestamps no longer synchronized to slave repositories

Syndication timestamps are no longer logged as master changes. This change reduces slave synchronization time for customers using syndication and will reduce syndication time for syndication from master repositories. Previously, syndication timestamps from a master repository were one of the changes sent to a slave repository during the synchronization process. If the slave were then normalized, it would be able to syndicate only "changed" records as if it were the master repository.

After this change, the slave will have no knowledge of what records were syndicated to what remote system and any syndications from a freshly normalized state will syndicate everything.

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 6: Repository Administration → Maintaining Master and Slave Repositories → Synchronizing a Slave Repository

MDIS handling of zero-length files enhanced

Zero-length files added to the MDIS Ready folder are now moved to the Archive folder with a warning added to the MDIS log. MDIS can then continue importing files from the port. Previously, zero-length files caused a structural exception, which blocked the port from further imports.

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 8: MDIS Administration → Troubleshooting → Import Files Are Not Being Processed By MDIS

New mds.ini parameters for defining which language layers to use for multilingual fields in expressions  for validations, calculated fields and assignments

The following optional mds.ini parameters have been added for defining which language layers to inherit from, if any, when multilingual fields are used in expressions for validations, calculated fields, or assignments. Possible values are 0 (no inheritance), 1 (inherit from primary inheritance language if values for current language are missing), or 2 (inherit from secondary inheritance language if values for current and primary languages are missing):

  • Language Inheritance Mode for Validations (defaulting to 1)
  • Language Inheritance Mode for Calculated Fields(defaulting to 1)
  • Language Inheritance Mode for Assignments (defaulting to 1)

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Console Reference Guide → Part 7: MDS Administration → MDS Configuration

MDM Data Manager

Improvement Description

Retrieve Notifications Delay in Seconds MDM Data Manager configuration option added

Previously, MDM Data Manager retrieved every notification generated by MDS as soon as it was generated. When large number of records are being updated, the constant retrieval of notifications and subsequent updating can adversely affect Data Manager performance. The Retrieve Notifications Delay in Seconds configuration option allows users to set a delay period between notification retrievals, which allows notifications to pool for greater efficiency during retrieval and greater responsiveness of Data Manager overall.

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Data Manager Reference Guide → Part 12: Configuration Options

Display Time Stamp Field in Local TimeData Manager configuration option added

Previously, MDM Data Manager displayed timestamp values in GMT only. When this option is enabled, timestamp values are adjusted to the local time zone of the machine running Data Manager.

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Data Manager Reference Guide → Part 12: Configuration Options

Partial failures for sliced operations

Some sliceable record operations can result in partial failures. Data Manager provides the ability to view the failed records and save them to a mask or copy them to the clipboard for later correction. The behavior for non-sliced operations was, and remains, that a singe failed record causes the entire operation to fail.

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Data Manager Reference Guide → Part 3: Record Mode → Limits and Slicing For Multi-Record Operations

Maximum Record Modify Limit repository property added

The repository property Maximum Record Modify Limit, set in MDM Console, limits the maximum number of records that can be modified in a single operation from within Data Manager.  The default value is 1000000000, effectively unlimited, which was the previous behavior.

The setting only applies to the Data Manager, not to the Web UI or the API.  The setting specifically applies to: record modifications, delete, check-in, check-out, roll back, recalculate, and merge operations.  If the setting is changed, it will not take effect until the next time the user starts the Data Manager.

More information: http://service.sap.com/installmdm71Information published on SAP site → MDM Data Manager Reference Guide:

  • Part 3: Record Mode → Limits and Slicing For Multi-Record Operations
  • Part 5: Repository Maintenance → Modifying Repository Properties

MDM Web Services

Improvement Description

Note added to Assignment Operations topic in documentation

If an assignment fails (in either of the assignment operations), the assignment fails for all records on which a Web service request is executed. Since each assignment is executed independently, if one assignment fails it does not necessarily mean that the others will fail.

More information: Assignment Operations

Limitation added to the Update Key Mappings Web service operation

Removing all remote keys for all remote systems for a specific record is not supported by Update Key MappingsOperation.

More information: Update Key Mappings Operation

Documentation of installation and deployment topics corrected and enhanced

The following topics of the MDM Web Services documentation were updated:

MDM Web Dynpro Components

Improvement Description

New User Exits have been added to allow  users to add their own functionality to an Item Details Web Dynpro component

The following User Exits are now exposed for Item Details Web Dynpro components:

  • Interface Method: unlimitFieldValues(String fieldCode)
  • Interface Method: validateRecord()
  • Event: ValidateRecord

More information: User Exits for Item Details Web Dynpro Components 

Description of how to display tuple member fields in an Item Details Web Dynpro component has been added

If you have selected a tuple field as one of the display fields in an Item Details component, you may want to also display the tuple member fields of the selected tuple field so that the tuple member field can be viewed and edited. A detailed procedure of how to carry out this configuration has been added.

More information: Configuring an Item Details Web Dynpro Component 

Limitations of tuple member field validations have been updated

Validations of multi valued tuple member fields are not supported by the MDM Web Dynpro Configuration Manager. However validations of single valued tuple member fields are supported but only when they are defined directly from the Main table in the MDM Data Manager.

More information: Validations

Enhanced functionality of the Multilingual Editor property of an Item Details component

Multilingual qualifiers are now supported for multilingual editing:

Extra functionality for the Multilingual Editor property of an Item Details component.

More information: Configuring an Item Details Web Dynpro Component → Multilingual Editorproperty

The documentation has been improved for the Multilingual Editor property of an Item Details component

Additional notes have been added to explain the different configuration options when choosing the display layouts for editing Text and Text Large fields at runtime.

More information: Configuring an Item Details Web Dynpro Component → Multilingual Editor property

Display of validation errors is now limited for checked out records

Previously all validation errors were visible on the user interface of the Item Details component. Now when a record is checked out, the user working on the record sees only validation errors of the validations that were selected in the Validation step of the wizard during configuration of the Item Details component (in the MDM Web Dynpro Configuration Manager).

The advantage is that a user does not need to see all the validation errors of another user and sees only the validation errors that are applicable to the records he/she is working on.

More information: Validations

Revised the configuration procedures of Web Dynpro components

The explanations of all property configurations that are related to contained and referenced components have been revised and diagrams have been included where necessary.

More information:

In the Supported Fields table, added a restriction for Lookup Taxonomy fields

When configuring an Item Details Web Dynpro component, take into account that If the Category field is enabled, changing the Category field value is denied if any of the currently linked attributes to the source category have values.

This removes the potential risk of a user unknowingly modifying the taxonomy structure by changing a category that has already a value assigned to its currently linked attributes.

This restriction applies to MDM 7.1 SP04 and higher.

More information: Item Details Web Dynpro Component → Supported Fields Table → Lookup Taxonomy

Added caution explaining to users what to do when upgrading to a new version of the MDM Web Dynpro Components

When upgrading from any version of the MDM Web Dynpro Components application, you must export all your configured projects and then re-import them once you have deployed the latest version.

Also take note of the following:

  • If you undeploy the tc/mdm/wdcomps/config/dictionary development component (DC), all the project configurations from the database of the specified Application Server Java will be deleted.
  • If you undeploy the tc/mdm/wdcomps/security DC, the MDM_WD_CONFIGURATOR and MDM_WD_TEST_APPLICATION actions will be deleted. You must reassign these actions to the role after deploying the new security DC.

More information: Installing the MDM Web Dynpro Environment

Documentation of installation and deployment topics corrected and enhanced

The following topics of the MDM Web Dynpro Components documentation were updated:

MDM Enrichment Architecture

Improvement Description

Enhancement to the documentation

Most topics in the MDM Enrichment Architecture documentation have been rewritten.

MDM PI Adapter

Improvement Description

Support for Quality of Service (QoS) model, Exactly-Once-In-Order (EOIO).

In addition to the current support of the Exactly Once (EO) Quality of Service model, there is now also support for the Exactly-Once-In-Order (EOIO) model. In this model, the messages are delivered in the same sequence that they were received in the PI.

More information: Quality of Service

For more information about configuring EOIO, see Setting Up Outbound Messaging from MDM

Documentation of installation and deployment topics corrected and enhanced

The following topics of the MDM PI Adapter documentation were updated:

MDM Portal Content Development

Improvement Description

Language inheritance for text attribute values is now supported.

Inheritance is not supported for MDM data except for text attribute values that is now supported. For example, data such as a text description for a product is not inherited but a text attribute value such as the color of a product is inherited.

More information: Language Inheritance

Caution added to the documentation

To connect to an MDM server on a host running multiple MDM servers, you must supply the port number of the server that you want to connect to.

For example: <server name>:<port number>

This option has been added for users that want to use more than one Master Data Server on the same machine. To distinguish between the different servers, a port number must be supplied.

More information: Configuring a System Object 

Properties have been added to the Text Search iView

Enables a portal administrator to control which of the search operators are enabled. When the properties are enabled (set to Yes), they are available in the dropdown list of available operators in a Text Search iView. 

More information: Editing Search iViews

New Enable Force Unlock property for an Item Details iView

Controls whether the Force Unlock button appears on the user interface of the Item Details iView. The Force Unlock button is used to remove another user's lock on a record. When a record is locked by another user, and this property is set to Yes (default), both the Force Unlock and the Refresh buttons appear on the Item Details iView. Otherwise, only a Refresh button is available.

More information: Editing an Item Details iView → Using Customization Options.

New documentation added describing the changes to the Portal user interface

To view enhancements that have been implemented in the MDM Portal user interface, the user can refer to release-specific SAP Notes. Each SAP Note includes an attachment called UI Enhancements to MDM iViews in the portal (Microsoft PowerPoint presentation). Links have been provided to all the SAP Notes.

More information: Changes to the Portal User Interface

New Item Details iView property called BLOB Label

You can choose one of the following options for displaying a link for any lookup record in a Binary Large Object table (PDFs, Images, Sounds, Videos, and so on):

  • BlobCode (default value)

    The code of the lookup record is displayed as the Binary Object link. By default, code is created by MDS from the file name - special characters and non-Latin letters are replaced with an underscore, sometimes making the link illegible.

  • TableName

    The name of the table followed by a numerator is displayed as the Binary Object link. Choosing this option ensures that the name of the Binary Object link is clear).

More information: Editing an Item Details iView

MDM Change Tracker Application

Improvement Description

Improvements were made to the runtime environment

The following improvements were made to the runtime environment:

  • A new Show Complete Event Details button has been added to the runtime user interface of the Change Tracker application. When the user chooses this button, an Event Information screen opens showing all the event details of the selected record. The advantage is that if the event on a selected record includes changes made on a tuple, then the changed tuple and the changed tuple member fields are also displayed on the Event Information screen.
  • If you are using a custom wrapper application that uses the Change Tracker application as a used component, an additional set method ( setJdbcAlias) has been added to operate the Change Tracker application. The following three set methods are now available:
    • selectLookupTable (table name - string)
    • setPermanintId (permanent id - integer)
    • setJdbcAlias (JDBC alias - string)

These methods are an additional option instead of passing the relative parameters through the URL.

Enhancement to the following topic: Change Tracker Database Table - A2i_CM_History

Entry Type tables have been expanded.

More information: Change Tracker Database Table - A2i_CM_History → Entry Types.

Updates and enhancements have been made to the sections on creating data sources for JDBC connectors.

For each database server, the user must populate fields, properties, and/or keys with specific values. We have improved this section to help the user enter the correct values for each field, property, and key to enable a successful JDBC connection.

More information:

MDM ABAP API

Improvement Description

Preventing RFC bottlenecks by defining minimum number of connections to SAP Gateway

As of MDM 7.1 SP06, the gateway configuration provides a new parameter, MIN_CONN, which specifies the minimum number of connections to the SAP Gateway. While the number of connections increases based on load, it never drops below the minimum number that is configured. This parameter can help customers with a high concurrent load on MDS, to prevent RFC bottlenecks.

More information: Configuring the MDM Server 

Additional Information

For more information about: