SAP BODS 4.2

SAP Data Services
Document Version: 4.2 Support Package 1 (14.2.1.0) - 2014-02-06

What's New

Table of Contents
1

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1

Introduction to SAP Data Services 4.2 Support Package 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.2

SAP information resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

2

SAP Data Services 4.2 SP1 features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.1

Installation, administration, and monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.2

Data Services Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.3

Connectivity: Big data and CDC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.4

Usability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.5

Functions and transforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.6

Text Data Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

2.7

Adapter SDK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.8

Data Quality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
2.8.1
2.8.2

Geocoder transform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.8.3

2

Data Cleanse transform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Global Address Cleanse transform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

© 2014 SAP AG or an SAP affiliate company. All rights reserved.

What's New
Table of Contents

1

Introduction

1.1

Introduction to SAP Data Services 4.2 Support Package 1

Welcome to SAP Data Services 4.2 Support Package 1 (version 14.2.1.0). This What's New document highlights
the new features available with this release.
For important information about this product release including installation notes, known issues, and fixed issues,
see the SAP Data Services Release Notes.
SAP offers other products that complement SAP Data Services and provide additional SAP enterprise information
management solutions. These include:
●

SAP Data Federator

●

SAP Data Quality Management for Enterprise Applications

●

SAP Data Quality Management SDK

●

SAP Event Insight

●

SAP Information Steward

●

SAP Master Data Governance for Embedded MDM

●

SAP NetWeaver Business Warehouse (BW)

●

SAP NetWeaver Master Data Management for Enterprise MDM

●

SAP Rapid Marts

●

SAP Text Analysis

For more information, see the SAP website or contact an SAP sales representative.

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

1.2

SAP information resources

A global network of SAP technology experts provides customer support, education, and consulting to ensure
maximum information management benefit to your business.
Useful addresses at a glance:

What's New
Introduction


3

Address

Content

Customer Support, Consulting, and Education services

Information about SAP support programs, as well as links to
technical articles, downloads, and online forums. Consulting
services can provide you with information about how SAP
can help maximize your information management
investment. Education services can provide information
about training options and modules. From traditional
classroom learning to targeted e-learning seminars, SAP can
offer a training package to suit your learning needs and
preferred learning style.

http://service.sap.com/

Product documentation

SAP product documentation.

http://help.sap.com/bods/
Supported Platforms (Product Availability Matrix)
https://service.sap.com/PAM

Get information about supported platforms for SAP Data
Services.
Use the search function to search for Data Services. Click the
link for the version of Data Services you are searching for.

SAP Data Services Community Network
http://scn.sap.com/community/data-services

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

SAPTerm

Get online and timely information about SAP Data Services,
including forums, tips and tricks, additional downloads,
samples, and much more. All content is to and from the
community, so feel free to join in and contact us if you have a
submission.
Blueprints for you to download and modify to fit your needs.
Each blueprint contains the necessary SAP Data Services
project, jobs, data flows, file formats, sample data, template
tables, and custom functions to run the data flows in your
environment with only a few modifications.
SAP’s terminology database, the central repository for
defining and standardizing the use of specialist terms.

https://portal.wdf.sap.corp/go/sapterm

4


What's New
Introduction

2

SAP Data Services 4.2 SP1 features

2.1

Installation, administration, and monitoring

Separate Information platform services environment
This release recommends installing Data Services (and Information Steward) on a separate Information platform
services system (instead of Business Intelligence platform) to provide flexibility to upgrade Data Services (and
Information Steward) independently from Business Intelligence platform.

Updated Windows installation
The Data Services installation now includes two installation options.
Option

Description

Install with default configuration

This option installs and configures mandatory components using default
values. The installation will configure a Data Services repository on the
user-selected database via a server-based connection. This repository will
be associated with the default job server that is configured during the in
stallation.

Install without configuration

This option allows advanced users to install specific Data Services fea
tures and configure them post-installation.The user must configure the
Data Services repository (repository creation and registration on the
CMS) and Job Server.

REST web services
Representational State Transfer (REST or RESTful) web service is a design pattern for the World Wide Web. Data
Services now allows you to call the REST server and then browse through and use the data the server returns.
For more information, see “REST web services” in the Integrator Guide.

Operational statistics enhancements
Additional web service operations were added to this release of Data Services. These operations give you the
ability to generate dashboards to further analyze and review operational statistics.
The new operations include the following:

What's New


5

Operation

Description

Get_Repository_List

Retrieves a list of repositories at log in.

Get_BatchJob_ExeDetail

Retrieves a list of all job executions for the selected repository and job.
You can also filter the list by time range.

Get_BatchJob_FlowDetails

Retrieves details about the tasks included in a job.

Get_DF_Auditdata

Shows audit information for a data flow.

Get_DF_Monitor_Log

Shows the runtime statistics for single data flow execution.

Get_DF_Monitor_Log_Pivot

Shows the runtime statistics as pivoted for a single data flow execution.

Object promotion management
This release of Data Services provides a new tool, Data Services Object Promotion Management, which is
launched from the Administrator in the Data Services Management Console. The Object Promotion Management
tool enables you to securely copy one or more Data Services objects from a development environment to a
production environment. To ensure security, these environments typically do not have direct access to one
another. Object promotion in Data Services is accomplished over secure FTP or over a shared directory that only
an Administrator or a user with an account assigned to the Administrator group can configure for this purpose,
maintaining security in both the source and target environments.
Users with View access to a repository can export its objects from a development environment to a shared
directory created by authorized users. Users who have Full Control access to the repository can import objects
after an Administrator or a user with an account assigned to the Data Services Administrator group has granted
them the new Manage Object Promotion Import user application right.

Note
The user who starts the Server Intelligence Agent (SIA) on the server that has access to the shared directories
that are used for exporting and importing promoted objects must have full read and write access to those
shared directories. If the server is started by a user who does not have full access to the shared directory, all
configurations for export and import operations for that shared directory will fail validation and the
configurations cannot be completed until the issue is resolved. If another user without full read write privileges
to the shared directory starts SIA after configurations have been successfully validated, all export and import
operations will fail until SIA is restarted by a user with the required credentials.
Objects with the same name and type are imported sequentially, based on the date when the export was initiated.
When you view the list of exported objects in the Import Configuration page in the Administrator, the exported
objects are grouped together with objects of the same type and object name, listed in order by the date they were
exported. You can import the same object more than once as long as that version of the object has not yet been
imported by itself or as part of an earlier import operation.

6


What's New

User application rights
This release of Data Services introduces new or modified user application rights to support best practices for
security in message logs, create or modify object promotion export and import configurations, use an object
import promotion configuration to import objects, or to edit substitution parameters.
User Right

Description

View internal information in log

Messages displayed to a user from warning and error logs
often contain internal system information which can provide
details that might pose a potential security risk (for example,
domain names or stack traces). A new user right included in
this release, View internal information in log, provides the
Administrator or a member of the Data Services
Administrator group a way to limit who gets to see internal
system information.
If a user is not explicitly granted the View internal information
in log user right through the Central Management Server
(CMS), any internal system information displayed in warning
or error messages is masked (replaced by a series of
asterisks). A user whose account has been granted the View
internal information in log user right will see the internal
system information associated with warning or error
messages in its unmasked form. The unmasked internal
system information portion of each warning and error
message is still retained in the server's log files.
The View internal information in log user right is automatically
granted to the following users when you install or upgrade to
this release of Data Services:
●

Data Services Administrator

●

Data Services Operator Users

●

Data Services Profiler Administrator Users

Note
SAP Information Steward, SAP Data Services On Demand,
or SAP Data Services Workbench users who run the
Metadata Browsing or View Data services and who do not
have the View internal information in log right will see
masked error and warning messages. If these users run
any other services are used, they will see both the masked
and unmasked versions of warning and error messages,
even if their account has not been assigned the View
internal information in log right.
Manage datastore and substitution param configurations

What's New

An existing Data Services user right, Manage datastores, has
been expanded to also grant permission for users to edit
substitution parameters. When you upgrade to this release,
all existing user accounts who were granted the Manage
datastores right will automatically be updated to receive the
Manage datastores and substitution parameters user right.
The Administrator or a member of the Data Services


7

User Right

Description
Administrator group can grant this right to another user or
group to allow them to modify substitution parameters.
Members of the Data Services Administrator group are
automatically granted this right.

Manage Object Promotion Configurations

By default, only a user whose account is a member of the
Data Services Administrator group can create and manage
object promotion import and export configurations.
Members of the Administrator group or an Administrator can
assign the Manage Object Promotion Configurations right to
another user or group account to grant permission to edit
configurations in the Administrator to use for exporting and
importing objects.

Manage Object Promotion Import

By default, only a user whose account is a member of the
Data Services Administrator group can run an object
promotion import configuration. Members of the
Administrator group or an Administrator can assign the
Manage Object Promotion Import right to another user or
group account to grant permission to use the object import
configurations in Data Services Management Console to
import objects from a shared directory into the production
environment. The user must also have Full Access rights to
the repository from which the objects were exported.

2.2

Data Services Workbench

This version of Data Services includes several enhancements that improve the user's experience.

Data Services Workbench
The Data Services Workbench is an application that simplifies the migration of data and schema information
between different database systems.
In previous versions, migrating data and schema information required you to create many data flows in the
Designer, with each data flow reading from a single source table and writing to a template target table. This
process could take days. In addition, incompatibilities between the source and target database types could
require manual schema and data corrections.
The Data Services Workbench automates this migration process. Instead of creating many data flows manually,
you now provide connection information for the source and target databases and select the tables that you want
to migrate. The Workbench automatically creates Data Services jobs, workflows, and data flows and imports them
into a Data Services repository. You can execute and monitor these jobs from within the Workbench. In addition,
the Workbench supports more advanced options such as bulk loading and delta loading.
Jobs created in the Workbench can be scheduled with the Data Services Management Console, and the generated
objects can also be used as a starting point for further editing within the Data Services Designer. For example, you
might want to add more advanced transformations that are not available directly in the Workbench.

8


What's New

For a complete list of supported sources and targets, as well as more information about using the Workbench to
migrate data and schema information, see the Workbench Guide.

Create data flows
This version of Workbench enables you to create data flows and include them in the replication job. The
transforms supported in this release are, Query transform, Case transform, Merge transform, Row Generation
transform, Map Operation transform, Date Generation transform, and SQL transform. You can reference existing
data flows from the Replication Job by dragging and dropping the data flows in from the Explorer. You can verify
all data flows and specify whether the data flow is for initial load, delta load, or both.
You also have the ability to convert replication tables to data flows. Highlight multiple replication tables, right click
the selection, and select convert data. You have the option to generate a single data flow or one data flow per
replicated table.

Data Flow editor
The Workbench Data Flow editor includes the Data Flow diagram (top), list of input schemas for the selected
transform (bottom left), and a tabbed area containing the properties of the object currently selected in the Data
Flow diagram (bottom right).
Data Flow diagram

The Data Flow diagram is composed a graphical area (left side) and a palette of ele
ments you can drop on the graphical area. The diagram toolbar includes options,
such as Zoom slider, Snap to Grid, Highlight Related Element, and so on.

Input Schemas panel

This panel displays all the available input schemas / fields that the user can drag n
drop to the properties area. Every field that is being used in the current property tab
is marked with a little black triangle. Some fields are marked with a key icon indicat
ing they are part of the primary key.

The options for Table Reader properties, File Reader properties, Table Loader properties, Merge properties, Case
properties, SQL properties, Row Generation properties, Map Operation properties, Date Generation properties,
and the Effective Date properties are the same as the Data Services Designer.
The Template Table Loader uses the same database specific loader options as Data Services Designer as well as
some extra options:
●

Use NVARCHAR for VARCHAR

●

Drop and re-create table

●

Double quote names

●

Table Type (for HANA only)

What's New


9

Validation in the Data Flow editor
In this version, objects containing errors will be underlined in red and a tooltip will show the list of errors/warnings
for an element.

File as target
In this version you can choose to use file as target rather than datastore. This option enables you to replicate to
multiple systems, replicate multiple times, and perform replication of source and target data that is located on
different networks. The following changes are available to support the file as target functionality:
Window

New options

Replication Job editor

Replication Target Type – Choose Datastore or Files.
Target File Properties – When selecting a target type of Files, enter the file
properties.
Generate File formats - Generates the file formats containing the schema
for each file that is loaded. These file formats contain the exact schema
(column names, data types and so on.) as defined in the target options

Data Flow Editor

Template File Loader - Includes the complete information needed to use
the file loader which includes all the file format properties applicable for
the loader and the loader specific properties as well (Such as Validate dec
imal Data and Delete File). The schema of the file is generated based on
the output schema of the data flow element connected to the template file
loader in the dataflow diagram.

Quick Replication Wizard

The Configure target settings window now includes the options, Target
type (Files or Datastore) and Target file properties, and Target datastore
properties.

Query transform editor: Manage expression macros
In this version you can define expression macros that you can re-use to apply the same function to a selection of
fields with a single mouse click.

Create multiple file formats
In this version, you are able to create multiple file formats using the new wizard. You can select multiple delimited
text files from either the job server or the local file system. The wizard then scans the files and automatically
detects multiple file format parameters such as the row and column delimiters, the text qualifier and so on. The
File Format editor is similar to the one in Data Services and currently supports only text-delimited files.

10


What's New

Changes to the Replication job editor
In this version, the Replication job editor includes the following changes:
●

Files are supported as a source for replication.

●

A replication job now allows using tables from different sources for replication.

●

The source panel has been removed. Now you can use the Project Explorer as the source when selecting
tables.

Using data cleansing solutions from Data Cleansing Advisor
Data Services Workbench now includes the ability to consume and model data cleansing solutions. This feature
allows a technical ETL developer with no data quality expertise to create a data flow containing a data cleansing
solution and validate the results in a production environment.
A data steward uses the Data Cleansing Advisor feature of SAP Information Steward to create and publish a data
cleansing solution. The data cleansing solution is stored in the SAP BusinessObjects Business Intelligence
platform's Central Management Server (CMS). In the Workbench, the ETL developer then models the data
cleansing solution as a Data Cleansing Solution transform within the context of a data flow, maps the transform’s
input and output schema to production sources and targets, and validates the results in the product environment.
Finally, the ETL developer generates and deploys the data flow as ATL to the Data Services repository for
execution in the Data Services engine.
For more information about using data quality solutions in Workbench, see the SAP Data Services Workbench
Guide. For more information about Data Cleansing Advisor, see the SAP Information Steward User Guide.

2.3

Connectivity: Big data and CDC

Big data loading
Data Services 4.2 provides the big data file loading feature with the recovery option. Big data file loading is an
extension to the Recovery Mechanism. When reading the big source flat file into the database tables, you can turn
on the job recovery mode. The job recovery mode checks for the recoverability, divides the source file into smaller
batches, and then processes each batch at a time. Therefore, when a job fails, it can be resumed from the last
checked point and run forward instead of restarting.
For more information and limitations, see “Loading Big Data file with recovery option” in the Designer Guide.

Native Microsoft SQL Server support on UNIX
Data Services 4.2 provides native Microsoft SQL Server support on UNIX as a source or a target (similar to what is
available on Windows).

What's New


11

When using the UNIX job server or engine to access the MS SQL Server datastore, the following functionality is
available:
●

CDC support, which includes the Replication method for SQL Server 2008 and later and the CDC and Change
Tracking methods for SQL Server 2008 and later.

●

Bulk loading support.
For more information, see “To use the SQL Server ODBC bulk copy API” in the Performance Optimization
Guide.

●

Allow merge or upsert option support for SQL Server 2008 and later.

●

Linked datastores support, which provide a one-way communication path from one database server to
another.

The following limitations apply:
●

You cannot use SQL Server as a repository on UNIX.

●

Windows authentication for the MS SQL Server datastore is not supported on the UNIX platform.

Support for long database identifiers
The maximum length of most importable database metadata names and Data Services internal identifiers has
increased from 64 to 256, depending on the Data Service repository type. For most repository types the
maximum length is 256, for MySQL the length is 64, and for MS SQL server the length is 128.

SAP LT Replication Server integration
Data Services has been enhanced to integrate with SAP LT Replication Server (SLT) by leveraging the new version
of ODP API. The exisiting extractor interface in Data Services has been enhanced and replaced with ODP in the
Object Library and Metadata browsing. ODP allows uniform access to all contexts provided by ODP API.
In case the new interface is not available on the SAP system, the old extractor interface (ODP or native) will be
used.
A new option has been added to the SAP datastore: “Context ”. SAP datastore in Data Services has been
enhanced to support the SLT objects. Working with these objects is similar to the way Data Services users work
with SAP extractor today. The ODP context allows you to connect to both the extractors and the SLT.
For more information about ODP in SAP Data Services, see the Supplement for SAP.
SLT enhances the CDC (Change Data Capturing) scenario in DataServices, because with the trigger-based
technology SLT adds delta-capabilities to every SAP or non-SAP source table which then allows for using CDC and
transferring the delta data of the source table. For more information on the SLT for ODP scenario refer to the
Installation Guide in
Replication Server

12

www.service.sap.com/instguides

SAP Components

SAP Landscape Transformation

Operational Data Provisioning with SAP LT Replication Server .


What's New

Spatial data support in Data Services
In this release, Data Services supports spatial data (for example, point, line, polygon, collection, or a
heterogeneous collection) for the following databases:
●

Oracle—reading

●

SAP HANA—reading and loading

When you import a table with spatial data columns into Data Services, the spatial type columns are imported as
character-based large objects (clob). The column has an attribute, Native Type, which has the value of the actual
data type in the database; for example, SDO_GEOMETRY for Oracle or ST_GEOMETRY for SAP HANA.
Limitations
●

Because spatial columns are imported into Data Services as clob, creating template tables with spatial types
is not supported.

●

Spatial data cannot be manipulated inside a data flow because the spatial utility functions are not supported.

For more information about loading data from Oracle into SAP HANA, see the SAP Data Services Supplement for
SAP. For more information about SAP HANA spatial data support, see the SAP HANA documentation.

2.4

Usability

This version of Data Services includes the following enhancements that improve the user's experience.

Enhancements to variables and parameters
In the Data Services Designer, the Variables and Parameters window has been enhanced with the following items
in the right-click menu:
●

Replicate: Lets you copy an existing variable or parameter and then modify it as necessary.

●

Insert Before and Insert After: Let you insert a variable or parameter before or after an existing variable or
parameter.

●

Move Up and Move Down: Let you specify the order of variable or parameters.

Enhancements to global variables
In the Data Services Designer, the Global Variables tab of a job's properties has been enhanced in the following
ways:
●

Improved column resizing.

●

Filter: Lets you filter the displayed global variables by name.

●

Multi-select: Lets you select multiple global variables at one time.

●

Bulk value update: Lets you modify the values of multiple global variables.

What's New


13

For more information about variables and parameters, see “Variables and Parameters” in the Designer Guide.

2.5

Functions and transforms

This version of Data Services includes enhancements to transforms and function support.

Mapping expression functionality added to the Map_Operation transform
You can now use the Map_Operation transform to modify data based on current operation codes and mapping
expressions. The operation codes can then be converted between data manipulation operations.
Writing map expressions per column and per row-type (INSERT/UPDATE/DELETE) allows you to:
●

change the value of data for a column.

●

execute different expressions on a column, based on its row type.

●

use the new before_image function to access the before image value of an UPDATE row.

Note
Mapping expressions are optional. If there are no mapping expressions, Data Services performs operation
codes only.
For more information, see the “Map_Operation” topic in the Reference Guide.

Batch Mode functionality added to the XML_Map transform
You can now use the XML_Map transform in Batch mode to accumulate data as a block of rows instead of a single
row. This block of rows is sent as a unit to the next transform.

Note
Only one input is allowed in Batch mode.
For more information, see the “XML_Map” topic in the Reference Guide .

2.6

Text Data Processing

Text Data Processing analyzes content and automatically identifies and extracts entities and facts in multiple
languages. It includes a set of transforms that work together to improve the quality of your data. It has been
enhanced with the following features:

14


What's New

Multithreaded TDP Entity Extraction transform
The TDP Entity Extraction transform now permits multithreading. Previously, scaling was accomplished only by
using multiple processes. Using mutlithreading, less memory is required when scaling, and better scaling can be
achieved when processing custom extraction rules.

2.7

Adapter SDK

See the Data Services Adapter SDK Guide for more information.

Adapter SDK binary communication
This version of the SDK Adapter allows you to use binary communication when creating a source table
implementation through the Java Project wizard.

Adapter SDK simplification
This version of the SDK Adapter simplifies the process for creating an adapter in the following ways:
●

The definition of externalized properties is simplified

●

The need to generate and package the configuration XML files has been removed

●

Many command line options now have defaults to simplify debugging setup

●

The getRowType property is now externalized

2.8

Data Quality

The set of transforms that work together to improve the quality of your data has been enhanced with the following
features.

Directory Update Assistant
The new Directory Update Assistant utility helps you identify the data quality address and geocoding directories
that can be updated, and automatically adds them to your Download Basket on the SAP Service Marketplace. The
utility is installed with SAP Data Services.

What's New


15

For more information, see the SAP Data Services Installation Guide or the directory update that is included with
each directory.

2.8.1

Data Cleanse transform

The Data Cleanse solution has been significantly enhanced to include the following functionality.

Remove diacritical characters
Use the new Remove Diacritical Characters option to replace diacritical characters with the ASCII equivalent
version. The addition of this option eliminates the need to use a Query transform to replace the characters.
The option is defaulted to No for all configurations except for the US North American configuration where the
option is defaulted to Yes to replace the diacritical characters. All other configurations retain the diacritical
characters. These settings make the option compatible with previous versions of Data Services.
To view the conversion chart, see the Data Services Reference Guide.

Information and status codes
The Data Cleanse transform now includes information and status codes to help you understand how the data is
processed. Status codes provide information about corrections and standards applied to the data. Information
codes provide information about data that is suspect and might require a manual review.
To view the Data Cleanse information and status codes, see the Data Services Reference Guide.

Phone parser
The new Phone parser parses both North American phone numbers and international phone numbers. You can
still use the individual North American and International phone parsers. However, when using Multiline1-12, the
new Phone parser is used. If both North_American_Phone and International_Phone parsers are selected, the first
parser selected is changed to Phone, and the second parser is removed.
Prior to upgrade

Post upgrade

SSN | DATE | NORTH_AMERICAN_PHONE | INTERNA
TIONAL_PHONE | PERSON_OR_FIRM

SSN | DATE | PHONE | PERSON_OR_FIRM

INTERNATIONAL_PHONE | NORTH_AMERI
CAN_PHONE

PHONE

INTERNATIONAL_PHONE | EMAIL | NORTH_AMERI
CAN_PHONE

PHONE | EMAIL

16


What's New

You can use the existing North_American_Phone and International_Phone output fields or you can use the new
phone output fields.
Generated field name

Description

International_Phone

The entire international phone number, including extra items such as the
country code.

International_Phone_Coun
try_Code

The country code of an international phone number.

International_Phone_ Coun
try_Name

The name of the country of origin of an international phone number.

International_Phone_ Line

The portion of the international phone number that is not the country code
or the city code.

International_Phone_ Local
ity_Code

The locality code of an international phone number

North_American _Phone

An entire North American Numbering Plan (NANP) phone number.

North_American
_Phone_Area_Code

The area code parsed from the phone number.

North_American _Phone_Exten
sion

An extension parsed from the phone number.

North_American _Phone_Line

The last four numbers (excluding an extension) parsed from a phone num
ber. In (123) 456-7890, 7890 is returned.

North_American _Phone_Prefix

The middle three numbers parsed from a phone number. In (123)
456-7890, 456 is returned.

North_American _Phone_Type

The type of phone number that was parsed, if it is included with the input.
For example, Home or Work.

Phone

Shows the phone number that was identified as either North American or
International.

See the Data Services Reference Guide and Data Services Designer Guide.

Parse discrete input
When parsing discrete person input fields, you might get better discrete output if you set the Parse Discrete Input
option to Yes in the Data Cleanse transform. With this option on, the transform concatenates the discrete person
input fields into a single name-line field, and then parses and standardizes the data into discrete output fields.
In the following example, you can see how the input data is output differently based on how this option is set.
Table 1: Input data
Column

Field

Person1_Given_Name1

Mr John T

What's New


17

Column

Field

Person1_Family_Name1

Smith Iii

Table 2: Output data
Column

Option=No

Option=Yes

Person1.Prename

<blank>

Mr

Person1.Given_Name1

Mr John T

John

Person1.Given_Name2

<blank>

T

Person1.Family_Name1

Smith Iii

Smith

Person1.Maturity_Postname

<blank

III

New Data Cleanse output fields
Previously, you had to perform additional processing to prepare the data for other tasks that you want to
accomplish. When you want to use the standardized data for downstream processes such as creating break keys
in the Match transform, use the following output fields.

Content type

Description

Match_Family_Name

Family_Name1

The combined standardized form of FamilyName1 and Family
Name2 with a space between used in the Match transform during
the comparison process. Data is output in uppercase, apostro
phes are removed, and other punctuation is replaced with a sin
gle space. PreFamilyName data is removed.

Match_Firm

Firm

A form of Firm that may be used in the Match transform during
the comparison process. Data is output in uppercase, apostro
phes are removed, and other punctuation is replaced with a sin
gle space, and data that is extraneous for matching purposes is
removed. This extraneous data includes business types such as
Ltd. and GambH, and noise words such as The, And, and Of.

Note
Some words are classified to be removed from all domains,
while others are language-specific and are classified to be re
moved in specific cultural domains.
Match_Given_Name1

Given_Name1

The standardized form of GivenName1 used in the Match trans
form during the comparison process. Data is output in upper
case, apostrophes are removed, and other punctuation is re
placed with a single space. PreGivenName data is removed.

Match_Given_Name2

Given_Name2

The standardized form of GivenName2 used in the Match trans
form during the comparison process. Data is output in upper

18


What's New


Content type

Description
case, apostrophes are removed, and other punctuation is re
placed with a single space. PreGivenName data is removed.

Match_Maturity_Postname

Postname

The standardized form of MaturityPostname used in the Match
transform during the comparison process. Data is output in up
percase, apostrophes are removed, and other punctuation is re
placed with a single space.

Match_Phone

Phone

The standardized form of Phone used in the Match transform
during the comparison process. Data is output as a string of dig
its. Spaces, punctuation, alphabetical characters and leading ze
ros are removed.

Match_Prename

Prename

The standardized form of Prename used in the Match transform
during the comparison process. Data is output in uppercase,
apostrophes are removed, and other punctuation is replaced
with a single space.

To see the Data Cleanse output fields, see the Data Services Reference Guide.

New Data Cleanse input fields
Several input fields have been added to automatically assign the content domain sequence and output format.
Input fields

Description

Option_Country

The content domain sequence and output format usually can be automatically
generated based on the Option_Country data. However, there are a few countries
where Option_Language and Option_Region data is helpful to make the assign
ment, for example, Switzerland, Belgium, and Canada. Using Option_Language
and Option_Region is optional, and is only used to determine the most appropriate
content domain and output format.

Option_Language
Option_Region

These input fields should be mapped from the following Global Address Cleanse
output fields in this order:
●

ISO_Country_Code_2Char

●

Language

●

Region1

These input fields override the Data Cleanse Content Domain Sequence and Output Format transform options.
However, the Option_Output_Format and Option_Content_Domain_Sequence dynamic input fields override the
input fields list above as well as the Data Cleanse transform options.
To see the Data Cleanse input fields, see the Data Services Reference Guide. For more information about assigning
the content domain sequence and output format options, see the Data Services Designer Guide.

What's New


19

Memory cache
To improve performance, you can set the cache in kilobytes (KB) to allocate a certain amount of memory for use
in the Data Cleanse transform. For example, if you have a 39 MB cleansing package, you can set the cache size to
40000 KB and use the rest of available memory for processing other transforms. Likewise, if your cleansing
package is larger, you can increase the value.

Reports
To complement the many existing Data Quality reports, Data Services has added two reports. Use the Data
Cleanse Information Code Summary report to view how the Data Cleanse transform modified the data. Use the
Data Cleanse Status Code Summary report to view record counts generated for each status code.
See the Data Services Reference Guide and Data Services Designer Guide.

2.8.2

Geocoder transform

The Geocoder transform has been enhanced with the following features.

New country directory data
For this release, directory data is available for 15 additional countries:
●

Austria

●

Belgium

●

Czech Republic

●

Denmark

●

Finland

●

Greece

●

Italy

●

Liechtenstein

●

Netherlands

●

Norway

●

Poland

●

Portugal

●

Spain (parcel)

●

Sweden

●

US TomTom (parcel)

The Geocoder transform is flexible enough to accept new country directory data immediately after the directory
data is released. There is no need to wait for the next Data Services release to begin using new country directory
data.

20


What's New

Check with your sales representative for a list of the most current country directories available.

2.8.3

Global Address Cleanse transform

The Global Address Cleanse transform has been enhanced with the following features.

Language and script conversion
Output option for US ASCII
The Global Address Cleanse transform has an extended ability to cleanse address data in both local and
international formats. If input address data contains local special characters, you can choose whether the output
address data contains the special characters or their international equivalent. For example, if the street name
“Østerbrogade” is input, you can preserve the local character “Ø” or convert it to the international data format
“Osterbrogade” in the cleansed output.
For Latin script records, the new Convert_Latin_Output_To_US_ASCII option converts any extended ASCII
characters in the Best component to US ASCII characters, if a character conversion is available. Any extended
ASCII characters for which there is no conversion (for example, the degree symbol or inverted exclamation and
question marks), are left as is. By default, the option does not convert extended ASCII characters.
Romanization for Chinese and Kanji characters
Previously, when given a Chinese or Russian address, the Global Address Cleanse transform would identify the
input script. If the input script was in native Chinese, the transform cleansed and validated it to the address-line
level; however, if the input script was Latin, the address was validated only to the locality level. After processing,
the address was output in the same script as it was input. The transform did not transliterate the address to the
desired script.
With the transliteration support added in this release, With transliteration support, the Global Address Cleanse
now helps you cleanse and validate your Chinese and Russian address data more effectively, either in the native or
Latin script. Data Services adds two features:
●

Cleansing and validating Chinese and Russian addresses in Latin script to the address-line level.

●

Transliterating native Chinese and Cyrillic addresses to Latin script.

A new engine option, Output_Address_Script, has been added for transliterating native Chinese and Russian
addresses into Latin script in your output data.
Given a Chinese or Russian address, the transform first determines the input character script (CJKK, CYRL, or
LATN). If the script is in CJKK or CYRL, the output data can be formatted and output as Latin (by setting the
Output_Address_Script option to Latin) or the native script (by setting the option to Preserve). If the script is
Latin, the address is output as Latin.

What's New


21

Address-line validation for Russia
The Global Address Cleanse transform can now cleanse Russian address-line data, so that you can parse,
validate, and correct Russian address information. To support this feature, Data Services provides the following:
●

New Russia address directory to enable validation to the address-line component level.

●

Enhanced parsing dictionary and rule file to improve parsing accuracy.

●

Transliteration support to support Latin or Cyrillic scripts for address assignment.

Improved Austrian address assignment
Austrian address assignment has been improved with the following enhancements:
●

The reference data and parsing rules have been enhanced to parse building and block data.

●

Assignment for addresses that have no house number but have a suffix (stair, group, block, and so on) and
are valid addresses.

Building and block data
In the following examples both inputs are assigned to the same output, which illustrates how suffixes can be either
written in full or separated with a forward slash (/).
Example 1:
Input 1
Artillerieplatz 1 Haus 6 Tür 1
1110 Wien

Input 2
Artillerieplatz 1/6/1
1110 Wien

Postcode1

Locality1_Name

Primary_Name_
Full1

Primary_Numbe Building_Name1 Secondary_Add
r
ress

1110

WIEN

ARTILLERIEPLATZ 1

HAUS 6

1

Example 2:
Input 1
Klg Feuchterweg 10 Gruppe 5
1110 Wien

22


What's New

Input 2
Klg Feuchterweg 10/5
1110 Wien

Postcode1

Locality1_Name

Primary_Name_Full
1

Primary_Number

Building_Name1

1110

WIEN

KLG FEUCHTERWEG

10

GRUPPE 5

Addresses with a suffix and no house number
In the following examples, the suffixes have been assigned and validated for addresses that have no house
number.
Example 1:
Input 1
Klg Gaswerk Gruppe 5 Parzelle 308
1110 Wien

Input 2
Klg Gaswerk Gruppe 5/308
1110 Wien

Postcode1

Locality1_Name

Primary_Name_Full
1

1110

WIEN

Primary_Number

KLG GASWERK

Building_Name1

GRUPPE 5 PARZELLE
308

Example 2:
Input 1
Karlsplatz Objekt 26
1040 Wien

Postcode1

Locality1_Name

Primary_Name_Full
1

1110

WIEN

KARLSPLATZ

What's New

Primary_Number

Building_Name1

OBJEKT 26


23

Improved Turkish address assignment
In this version, the Turkish address cleansing solution is enhanced in the following ways:
●

A new address directory content that provides more comprehensive and accurate Turkish address data.

●

The existing parsing dictionary and rule files have been enhanced to improve parsing accuracy.

Enhanced support for SAP software
Several enhancements have been made to the Global Address Cleanse transform to allow it to work seamlessly
with other SAP software, such as SAP Customer Relationship Management and SAP Master Data Services.
●

ISO standard region code support. You can now input and output ISO standard region codes (ISO 3166-2)
from the Global Address Cleanse transform.

●

ISO standard region2 code support. The Global Address Cleanse transform now supports region2 output so
that both Region1 and Region2 components are available on output.

●

Discrete input field support for address components. The Global Address Cleanse transform includes several
new input fields, NetWeaver_<fieldname>, that map to the data model of SAP software.

Caution
Use the NetWeaver input fields properly to avoid unexpected results in your data. You cannot map multiline
or Address_Line input fields when you use the NetWeaver input fields. Although the NetWeaver input fields
appear discrete, they behave and are processed as multiline fields. They are mapped internally to
Multiline1-12 before normal Global Address Cleanse processing is performed. If a NetWeaver input field is
not mapped, the multiline that would have been mapped to it is mapped to the next available NetWeaver
input field.
●

New output field to contain unused data. A new output field, Remainder_Full, has been added that
concatenates all extra and reminder data, including Address_Line_Remainder1-4 and Lastline_Remainder1-4,
into a single output field.

●

New output field to combine primary name and secondary data. A new output field, PName_Secondary_Addr,
has been added that contains the full primary name (with no associated primary number) and the full
secondary address.

●

New output field for private mailbox data.A new output field, PMB_Full, contains private mailbox information
for U.S. addresses.

●

Standard postal code format check. The new NetWeaver_Formatted_Postcode output field lets you output a
postal code in a format required by SAP software. The Postcode_In_NetWeaver output field indicates whether
the NetWeaver_Formatted_Postcode output field is populated and is therefore a valid postal code.

●

Improved Country ID performance.

Combining overlapping ranges
A new Combine Overlapping Ranges option has been added to the Global Address Suggestion List Options group
that lets you specify whether individual suggestions with overlapping ranges are combined. You might set this

24


What's New

option to Yes if you want to limit the number of total suggestions presented to your user. However, you might not
see gaps of invalid ranges that would be apparent if this option was set to No.
For example, a suggestion list might show the following suggestions if this option is set to No:
1000-1099 Maple Ave
1100-1199 Maple Ave
But would only show this suggestion if set to Yes:
1000-1199 Maple Ave

What's New


25

www.sap.com/contactsap


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. National product specifications may vary.
These materials are provided by SAP AG and its affiliated
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 be construed as
constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks
of SAP AG in Germany and other countries.
Please see http://www.sap.com/corporate-en/legal/copyright/
index.epx for additional trademark information and notices.

SAP BODS 4.2

More Related Content

What's hot (20)

Viewers also liked (13)

Similar to SAP BODS 4.2 (20)

Recently uploaded (20)

SAP BODS 4.2