what’s new with dqm for sap 4.0 sp02

What’s New with DQM for SAP 4.0 SP02 Public

© 2012 SAP AG. All rights reserved. 2Public

Topics

Overview

What’s new in DQM for SAP 4.0 SP02

Supported Platforms

Installation Scenarios / Processes

Deep Dive into the changes

Functionality Related changes

Configuration/Setup Related changes

Dataflow Changes


Topics

Overview


Supported Platforms





Dataflow Changes


Overview

What’s new in DQM for SAP 4.0 SP02?Ability to allow custom coding through Enhancement Points.Works with SAP Data Services 4.0 SP01 and higher, including Data Services 4.1.xPerformance improvements of Batch ReportsSimplified configuration steps and dataflow changes to work better with China and Japanese data.


Topics

Overview


Supported Platforms





Dataflow Changes


Overview

Tested/Supported PlatformsSAP Data Services 4.0 SP03 / SAP Data Services 4.1 SP01

NW640, NW700, NW702, NW731 and NW740 (NW 731 package can be installed).

Languages supportedDA – DanishDE – GermanEN – English (default)ES – SpanishFR – FrenchJA – JapaneseNL – DutchPT – PortugueseRU – RussianZH – Simplified Chinese


Topics

Overview


Supported Platforms





Dataflow Changes


Overview

Installation Scenarios for DQM for SAP 4.0 SP02

NOTE: All 3 components (ABAP, RFC and DS Jobs) must be of the same version for DQM for SAP

CUSTOMER SCENARIOSNew Installation/Upgrading

customers from DQM for SAP 3.xCustomers upgrading from

DQM for SAP 4.0 SP00Customers upgrading from

DQM for SAP 4.0 SP01

ABAP Components

1) Install DQM for SAP 4.0 SP002) Install DQM for SAP 4.0 SP013) Install DQM for SAP 4.0 SP02

1) Install DQM for SAP 4.0 SP012) Install DQM for SAP 4.0 SP02

1) Install DQM for SAP 4.0 SP02

RFC / DS Components Install SP02 Install SP02 Install SP02


Overview

Installer ChangesNo Changes for ABAP Packages or RFC installerData Flow Installer

a new screen to collect the Data Services Repository Information (to accommodate changes with SAP Data Services 4.1).


Topics

Overview


Supported Platforms





Dataflow Changes


Suppress Address Reviewer ScreenBased upon what is changing with the address data, end users can now control when to show the Address Reviewer screen popup with easy descriptions:

Example: If the zip code is changing from 4 digits to 9 digits, it may not be of value to show the Address Reviewer Screen.

End users are able to set when not to show Address Reviewer Screen based upon items from the drop-down lists of address change descriptions for a given country:

Drop-down Lists


Disable/Enable Buttons on Address Reviewer Screen

Use IMG to configure Address Validation screens to allow users to either accept the validated address or use the address that was entered by the user.

This can be configured on a per country basis.


Simplified options to Control the format of Address Line Data (Street Level)

Substitution Variable Setting - $$DQ_SAP_Output_Format_Address_Line = 1,2,3,4

1. Data is put into separate fields, there is no combination of fields. E.g. House No. = 332 Street = Front St S Suppl. = Ste 206

2. All address data is outputted to Street. E.g. House No. = Street = 332 Front St S Ste 206 Suppl. =

3. Primary name and secondary data are combined and stored in the street fieldE.g. House No. = 332 Street = Front St S Ste 206 Suppl. =

4. Primary range and primary name data are combined into the street field. All other data is separated out.

E.g. House No. = Street = 332 Front St S Suppl. = Ste 206

Substitution Variable Setting - $$DQ_SAP_PMB = STR_SUPPL2 or STREET• Controls where the PMB data is stored for US addresses. • All other extra information that is not validated by GAC will be outputted in STR_SUPPL2 (STREET3)


Changes in dual-address mode entry (Street and PO Box data)

Changes to how last line data is shared between Street and PO BoxLast line data is only shared if there are no differences between populated fields. This includes country, region, city, and postcode.

Street and PO Box addresses that are part of the same address can be validated separately. For example, you can take the validated address for street and if you use the original entry on the PO Box, the street field will keep what you initially selected. The Check Status will only be set to “C” if both are validated.


Improvements to RSADRINI Report (Batch Match code generation and Batch matching) – 1 of 2

Additional Initialization Options to improve the performance allows end users to create match codes in a multi-step process to improve the performance and minimize the locking of users during the commit process.


Improvements to RSADRINI Report (Batch Match code generation and Batch matching) – 2 of 2Batch Matching within an index group

BUT000 records will be compared against BUT000 and will never match a record from KNA1

Batch Report Statistics - New report to view the batch match code creation and batch match statistics /FLDQ/MONITOR_RSADRINI. The program can be used during or after the process to view runtime statistics, identify multi-threading optimization and to study the performance issues on the SAP and SAP Data Services side.


Steps to optimize batch match performance using the Batch Report Statistics

Report /fldq/rsardini gets the most performance by doing work concurrently. Most of the time is spent creating break keys, and that can be done with as many threads as the SAP Data Services box can support. In program /fldq/monitor_rsadrini keep track with how the match code index keeps up with the index pool, and increase the number of RFC/real time service instances that are needed to process the records as fast as they come out of the index pool. A starting place is 8-10. Keep in mind that the index pool does slow down on the last 10% of the records, allowing the match code creation to catch up.

Run program /fldq/rsadrini with higher concurrent task levels until you find the optimal result in the test system on a small set of data.

Look at the resource utilization on the SAP Data Services system. If the match code process does not get faster with more instances, you may be limited by memory, CPU, or other issues with the box.

Run transaction “sm59” to test packet speeds. Increasing the packet size of slower networks will increase performance if network administrators cannot increase the network bandwidth.

If the index pool process time for each record is slow, there are a number of Notes by the BAS team to improve performance of their database selects. There may be issues with the SAP database or system that a Basis Administrator will need to review.


Performance Improvements

Batch address cleansing report (/FLDQ/RSADRQU2 Report)Report has been multi-threaded to increase throughput of the address cleansing in SAP Data Services. 88% improvement in performance.

Batch Match Report (/FLDQ/RSADRINI Report)1

Optimized the index pool reading process. 33% improvement in performance.

1 - Batch Match Report includes reading index pool, generating match code and duplicate checking.


Improvements to Batch Match Result Report

New criteria to view the batch match results based on index group (BUT, KNA1 etc), country and Matching Group IDs. This allows end users to view the matches for a particular group in a given country and for a restricted match group if the result was a large set.


How to extend the DQM process beyond the out-of-the-box functionality?

Enhancement Points - places in the code that end users can write custom code without having to modify the existing code. New versions of the adapter keep the same enhancement points, so this custom code will continue to work and not require re-doing the customizations for each new version of the code.

Implicit enhancement points are points within ABAP code where an enhancement point is implied, and in which case can be created in all forms, programs, includes, function modules.

Explicit enhancement points are “hooks” that are specifically coded into the program at various points of the code where end users can enhance the ABAP program.

Tables and Structures can have structures appended to them in a similar concept that has the changes in a separate object that does not change if the structure changes in a newer version.


Topics

Overview


Supported Platforms





Dataflow Changes


Configuration/Setup changes

New IMG option to deactivate/activate ADDRESS_UPDATE Badi

Allows the end users to switch the match code creation/update ON or OFF in real-time.

Can be used with Postal Validation Badi option and the duplicate check Badi option to completely disable the data quality process during real time.


Configuration/Setup changes

Post-installation step for load-supported countries is no longer necessary.

Simplified the post-installation step by replacing the manual need for running the “Load Supported Countries” report /FLDQ/AD_REPT_LOAD_COUNTRIES with a Business Configuration Set shipped with ABAP package that automatically populates the supported country table while installing the ABAP Package. (Refer to Section 6.1.5 in Previous version of the User Guide). This also removes the back-end Data Services job Job_Realtime_DQ_SAP_Retrieve_Country_Purchased

Post-installation step of creating Enhancement Set for CRM Web Client is no longer necessary.

Business Configuration Set activation will now automatically create an enhancement set for the UI component and attach the latest enhancements to the UI component. (Refer to Section 6.1.9.2.2 in Previous version of the User Guide).


Topics

Overview


Supported Platforms





Dataflow Changes


China / Japanese Address ImprovementsData Services Jobs were re-engineered to handle the new functionality of GAC that now offers full support for the Native Chinese and Japanese addresses to take full advantage of these changes and present them in the expected formats.

Extra Data after Address CleansingAs with all countries all data that GAC cannot assign is not lost, but is formatted and output to “Street3 (str_suppl2)” field.

Unicode Data Matching option setting - $$DQ_SAP_Match_EngineThe Japanese engine does all that the OTHER_NON_LATIN1 engine does and also uses some internal reference data to match names/firms/addresses a bit more accurately for Kana. The only reason to use a different engine is if it is necessary to match against another CJK native script like Chinese. DQM for SAP supports LATIN1, CHINESE, JAPANESE, KOREAN, TAIWANESE, OTHER_NON_LATIN1.

Dataflow Changes


No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. 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.

Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA, pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli, Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the United States and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the United States and other countries.

Oracle and Java are registered trademarks of Oracle and its affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems Inc.

HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C, Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.

IOS is a registered trademark of Cisco Systems Inc.

RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App World are trademarks or registered trademarks of Research in Motion Limited.

© 2012 SAP AG. All rights reserved.

Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps, Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync, Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are trademarks or registered trademarks of Google Inc.

INTERMEC is a registered trademark of Intermec Technologies Corporation.

Wi-Fi is a registered trademark of Wi-Fi Alliance.

Bluetooth is a registered trademark of Bluetooth SIG Inc.

Motorola is a registered trademark of Motorola Trademark Holdings LLC.

Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

what’s new with dqm for sap 4.0 sp02

Documents