You are on page 1of 91

Don Loden

SAPInformation
Steward: Monitoring
Data in Real Time

~ Rheinwerk
Publishing

Bonn Boston
What You'll Learn

Implement real-time information governance with SAP Information


Steward with this E-Bite! Learn how to use three key SAP Information
Steward modules: Data Insight, Metadata Management, and Metapedia.
Build views and create scorecards with Data Insight. Discover data trans-
parency, and collect and manage metadata with Metadata Management.
Implement an enterprise data dictionary to apply business terminology to
data with Metapedia.
Complimented with a comprehensive case study, you'll take what you've
learned and apply real-world practice!

1 Information Governance in the Real-Time Enterpri se . . . . . . . . . 5


1.1 Real-Time Enterprise..... . .. . ........... . .. . ..... 5
1.2 SAP Information Steward . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2 Real-Time Governa nce with Data Insight . . . . . . . . . . . . . . . . . . 10
2.1 SAP Information Steward Validation Rules
and Scorecards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 Connecting SAP Information Steward to an
SAP ERP Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.3 Building an SAP Information Steward Scorecard.. . . . . . . . 19
3 Meta data Ma nagement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.1 Con necting to SAP Systems . . . . . . . . . . . . . . . . . . . . . . . . 50
3.2 Setting Up and Runn ing Collection Tasks . . . . . . . . . . . . . . 57
3.3 Examin ing Results in SAP Information Steward. . . . . . . . . . 59
4 Build a n Enterpri se Data Dictionary with Metapedia . . . . . . . . . 63
4.1 Setting Up Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.2 Setting Up Categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
4.3 Exposing Metaped ia Content to Other Systems . . . . . . . . . 72
5 Case Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.1 Building Content in Data Insight. . . . . . . . . . . . . . . . . . . . . 74
5.2 Extracting Metadata with Metadata Management. . . . . . . . 85
5.3 Creating a Data Dictiionary w ith Metaped ia . . . . . . . . . . . . 86
6 What's Next?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

4
1 Information Governance in the Real-Time
Enterprise
Information governance is a core business process that ensures data is
treated as a corporate asset and formally managed throughout an enter-
prise. When executed properly, this information governance paradigm
ensures data can be trusted. Defined like this, it is obvious that informa-
tion governance brings many benefits to an organization.
Information governance has always been a puzzling topic for organiza-
tions and has gained more ground in recent years, with many organizations
embracing information governan ce as a top strategic priority. Without
information governance, issues such as data silos, repetitive work, and
sacrificing long-term maintainability for short-sighted, short-term appli-
cation and data solutions can arise. Although there are numerous other
advantages to information governance, there is one looming reason why
it is now more important than ever: The dawn of the real-time enterprise.
Being able to see the effects of data generated in real time creates exciting
new opportunities and obstacles that must be addressed. This section will
discuss the need to govern information and data quality in a real-time
enterprise and the effects of failing to consider these challenges.

1.1 Real -Time Enterprise

A real-time enterprise focuses on the responsiveness of an organization,


bringing formerly discrete business systems into cohesive union by lever-
aging data in real-time. In this model, business systems are designed in
such a way that greater transparency can be achieved by reducing redun-
dant datasets, accomplished by finding data at the source to support
either analytical or operational support decisions. Consider how a plat-
form like SAP S/4HANA increases the capability to use one data-centric

5
Information Governance in the Real-Time Enterprise I 1

platform to not only control business processes, but also extract analytics
from the same dataset. This capability supports many goals that a real-
time enterprise sets out to fulfill, such as:
Reduced turnaround times for customers
Increased transparency straight to core data structures
Ability to share information from a central source across departments
Transactional reporting available at the time of record creation
Reducing overhead of systems and support staff
There is tremendous potential for an organization that embraces this
shift, as well as many new challenges. We will discuss both opportunities
and challenges in the following sections.

Opportunities
Real-time governance and attention to data quality is more important
than ever when considering an in-memory technology like SAP HANA.
With SAP HANA, data can be reported on directly from the source appli-
cation, and this is especially true for operational reporting. This is only
now possible because SAP HANA allows access to sources that tradition-
ally would not lend themselves to direct reporting structures. This is
especially true in cases in which a central SAP ERP system is the primary
system of record. Figure 1 shows the simplicity possible with SAPS/
4HANA in regard to operational reporting.
This makes a legacy concept of a latency-driven external operational data
store somewhat redundant, causing management and architects to wonder
whether the additional overhead and complexity of an external opera-
tional data store is needed to support the operational reporting paradigm.
Although there is no longer a need for redundant data, data quality is still
an important issue.

6
Information Governance in the Real-Time Enterprise I 1

Reporting Reporting
Int erface Interface

OD S LAYER

ETL processing
t ransfo rmations and
data quality enrichment

Conven t ional SAP ERP source SAP S/4HANA ERP source

Figure 1 Conven t ial SAP ERP Reporting Compared with SAP S/4HANA Reporting

Challenges
Figure 1 shows a simplified reporting method without the ETL transfor-
mational layer and ODS. However, you must consider data quality up
front in an SAP ERP system. Without quality data, attention to data qual-
ity, and proper governance and monitoring, these appliances will only
propel bad or incorrect data in reports. In the conventional SAP ERP
model shown in Figure 1, an ODS would have provided cleansing and
enhancements via an ETL process. However, in the real-time enterp rise,

7
Information Governance in the Real-Time Enterprise I 1

the fact that you are using transactional data for analytics makes a latency-
driven process useless. This is important because organizations already
have mechanisms for this in business intelligence (BI) constructs and the
ODS layer. From this legacy perspective, data quality issues are corrected
and data is prepared in the extract, transform, and load (ETL) layer. These
correction mechanisms must be accounted for or at a minimum properly
understood in this new "real-time enterprise" before an in-memory appli-
ance can fill all of these gaps. This is where real-time governance comes
into play.
It may seem obvious, but real-time governance happens in real time!
Straightforward enough- but think of the challenges this introduces.
Many master data management activities, like matching and cleansing,
are based on transactional latency. To match and cleanse data, data
must be collected and processed to be placed into cleansed containers
with quality deduplicated data. That is not to say the matching and
cleansing process goes away, but thes e types of things must be thought
through. If you are going to report on transactional data in real time
with SAP S/4HANA, you must deal with data quality in real time in the
transactional system. Much thought and design must be placed into the
real-time enterprise before bad data begins driving business processes
poorly in real-time. This is not an overnight shift, so do not expect too
much up front without proper consideration of going "straight to the
source" for the data with an in-memory solution.
Now, how can an organization begin this conversation about real-time
governance? It begins by examining the real-time data quality monitoring
and data quality socialization functionality of SAP Information Steward.

1.2 SAP Information Steward

SAP Information Steward provides a single platform to discover, assess,


define, monitor, and improve the quality of data. Users can do any of the
following tasks:

8
Information Govern ance in the Real-Time Enterprise I 1

Profile data with complex profiling options


Create and run validation rules embedded in scorecards
See relationships of metadata from sources all the way to fields used in
reports
Manage a data dictionary
Create and develop complex data cleansing rules and dictionaries
SAP Information Steward benefits from being part of the SAP product
stack and sharing close API ties to the SAP ERP platform. SAP Information
Steward can be directly connected to a production SAP system in a safe
manner, allowing unprecedented access to an overarching view of data in
SAP. A detailed view of how this is accomplished can be found in Section
2.1.
SAP Information Steward allows the user to interact with data from a data
validation standpoint that can be modeled by a master data domain or by
a process flow for the organization. Having this organized, business-cen-
tric visibility is crucial to a successful post in, for example, an SAP HANA-
enabled SAP ERP platform, and is a requirement for governing data in a
real-time enterprise.
Tactically, governing data in real-time takes many forms in SAP Informa-
tion Steward, and we will examine a few of these in the next section. SAP
Information Steward allows you to create complex quality validation
rules to check whether data complies with business constraints and
requirements. These rules generate passing or failing scores that are con-
figurable to a variety of situations and use cases. Rules are reusable and
illustrate individual business scenarios and objectives. From these rules, a
developer can create visualizations based on positive or negative results.
These different rules can be used together to create a complex data quality
scorecard.
In this E-Bite, we will walk through these rules, along with the three pri-
mary modules in SAP Information Steward in each individual section:

9
Real -Time Governance with Data Insight I 2

Data Insight, Metadata Management, and Metapedia. Finally, in Section


5, we will take what we have learned and apply it to a comprehensive
case study.

2 Real-Time Governance with Data Insight


Many customers are aware of SAP Information Steward's capabilities
within the Data Insight module to rapidly build complex data scorecards,
but miss the fact that they can do so safely and effectively against a live
production of SAP ERP or SAP CRM. In Section 1, we discussed the busi-
ness case and needs for monitoring data quality in real time. Now, we will
begin to see how SAP Information Steward enables such monitoring as an
option for an enterprise.
In this section, we will explore the scorecard and rule creation processes
to create the foundation for governance in a real-time enterprise. We will
also look at best practices for SAP application connectivity and the inter-
action between SAP Information Steward and SAP ERP to ensure both
quality performance and safety for the SAP ERP transactional system.

2.1 SAP Information Steward Validation Rules and


Scorecards

SAP Information Steward has many features, but one of the tool's greatest
strengths is its ability to track the quality of data over time in a graphical
and quantitative way. The heart of this functionality is the SAP Informa-
tion Steward scorecard. The scorecard is a data socialization tool that vali-
dates data by using custom validation rules to ensure that data conforms
to given corporate standards. The scorecard then tracks the effects of data
conformity over time by plotting that information with a graphical trend
line. The scorecard example shown in Figure 2 shows a relatively flat
trend and scoring of data.

10
Real -Time Governance with Data Insight I 2

-----------------------------------------------
SAP SAP Informat:Jon Steward Welcome:

Oat.1Insoght ~IIJilZI~II!I:IIfll
Projects ~ OJstomer

Show score as of: No~ Sort By: Name -~. Views: {];!][QJ _ $_ Q!! Share

Show O..tllil

Quarotv 9 .21 Cost $1.17K

Acom<y
Quality Trend Cost Tr end

Date Time: Date Time:

Th~: La.<~ s HiQ:h . a

Figure 2 Example Customer Data Domain Scorecard

This scorecard tracks customer data and shows a quality trend that is
mostly flat, which would not be the case if either the data or the rul,e had
changed considerably over time. 'fhe customer example scorecard reports
a quality score of9.21, and this quality score is comprised of two quality
dimensions: accuracy and completeness. There are many other data qual-
ity dimensions that may be utilized to group and order the presentation
of data quality for socialization throughout the enterprise.
Data quality dimensions are a useful tool for a high-level grouping or for
the organization of rules and measurements; however, these lead quickly
to what rules and measurements comprise accuracy. To see this level of
detail, click the SHow DETAIL button on the main scorecard screen (see
Figure 2) to show the details of the scorecard quality dimensions, as
shown in Figure 3.

11
Real -Time Governance with Data Insight I 2

---------------------------------------------------------------------
SAP
"""T SAP JnformatlOn Steward w<komc. ......, ..,. - - 11<1> too Off

O.talnsoght ~~~~ -----------------------


ll
Show Kore of: Now Sort 8y: ~qme

Key Data Oomai"l


ASu:i OJ:stomer The$c: ore 1'\1.. . 9.12 Qi Ad<tt_~ttc<ns IWefi><S...cc.cl>o.. . 8.83
9.41 ~ erntoote ...,.....,,.,... IWe r;. s...cc.cl>o .. .
Cii Otvcamotbeblanl< IWefi><S...cc.cl>o... 9.76
'-l Phont carnot be blank ~ 00.. Scuce_SQ... 8 .2S
{J! nJ_ISN..ll_Adess Test 1f acustorntra... 9.41

ASUG Custome r

lastRo-1: 10 SO Score Range: ~ Ttn shold: low S ~ -~dota ... Yiewltnpac:t .


10-
-~
So<.re<
So<.rce,;Ql
So<.rcc,;Ql
S...ce,;Ql
-
d>o
cl>o
cl>o
T-
usa_OJStomtrs
uso_customers
U$6_MtomtrS
CoUms
Adchssl
Adchssl
6i'ttotte
Scor
8.83
9.U
6.97
S...CA!,;Ql d>o US6_CU$tomefS Oty 9. 76

O.tte Time
So<.rcc_SQL d>o usa_OJStorMrs
""""" 8.2S

Fi gure 3 Details for Rules behind the Scorecard to Show Organization of Quality Dimensions

On the DETAILS screen, we can see that under DATA QUALITY DIMENSIONS
there are the AccuRACY and COMPLETENESS areas. These rules make up the
core functionality of the scorecard. Each rule validates a particular busi-
ness scenario and either passes or fails the data being evaluated. This eval-
uation creates a score for a given connection , which is illustrated as a rule
binding. Individual rule binding scores for each connection that a rule has
"rolled up" to an overall rule score. Each rule score rolls up to a composite
score for its respective data quality dimensions. The data quality dimen-
sion composite score also rolls up to the key data domain score, which
represents the highest-level score for the scorecard. Scoring is a crucial
concept for a scorecard business scenario and can be adjusted to properly
measure particular business conditions. We will examine this concept in
greater detail later, in the section Assess and Set Scorecard Weights.
Scorecards are essentially a presentation layer for the various validation
rules in SAP Information Steward and a means to dial in their measures in

12
Real -Time Governance with Data Insight I 2

order to tell a story of business relevance. It is important to note that val-


idation rules can stand on their own as discrete operational measures, and
they can range from very simple completeness checks to extensive and
complex designs . To design and construct a rule, you might think that you
would need to opt exclusively to code this rule in a scripting- or SQL-type
interface. However, in SAP Information Steward this is not the case. This
tool is designed with the business user in mind, so there is a graphical
user interface (GUI) used to define and construct the validation rule.
The Rule Editor in SAP Information Steward is the heart of Data Insight.
These topics present an overview of how validation rules and scorecards
work together to produce a cohesive business story in an SAP Information
Steward Data Insight scorecard. We will fully explore the scorecard cre-
ation process in Section 2.3. Let's first examine ways to connect SAP
Information Steward directly to tihe SAP ERP system. Only after this con-
nection is established can a user achieve real-time predictive governance.

2.2 Connecting SAP Information Steward to an


SAP ERP Application

The SAP ERP application is the solution that global enterprises rely on to
run their businesses. However, seeing the data quality and relative rela-
tionships as SAP GUI screens can be challenging. This is especially true
when a business user needs an overall picture of how data is intertwined
to tell the full story of how a particular business process functions . SAP
GUI's purpose is to provide input and lookup screens in order for mem-
bers of an organization to do their respective jobs. This requires informa-
tion to be compartmentalized and effectively spread throughout the
application on a multitude of SAP GUI screens. There are many cases in
which organizational constructs that depend on each other may be
entered and maintained on separate transaction screens.

13
Real -Time Governance with Data Insight I 2

What Is Required
SAP Information Steward uses functions that support the use of ABAP,
BAPI, and !Doc interfaces on SAP servers. You will need some or all of
these functions in the normal operation of the software in an SAP envi-
ronment. Typically, you will focus on the function modules deployed
with the SAP Information Steward software. These functions perform
such operations as dynamically loading and executing ABAP programs
from the application server, efficiently running preloaded ABAP pro-
grams, allowing for seamless metadata browsing and importing from SAP
servers, and reporting the status ofrunningjobs. Some of these functions
read data from SAP Business Warehouse (SAP BW) sources. It is import-
ant to note whether you need to load the functions onto your SAP appli-
cation system or whether the f111nctions already exist. This is usually deter-
mined by what SAP application system version you have deployed in
your environment.
For SAP NetWeaver 6.0 and later, SAP functions for SAP Data Services
and SAP Information Steward are included in three SAP components: PI_
BASIS , SAP _APPL , and SAP _B ~J. If your system does not contain these func-
tions or you plan to upgrade SAP systems , see SAP Note 1919255 for
information about SAP Data Services and SAP Information Steward trans-
port functions. If your SAP NetWeaver system does not contain these
functions, please contact SAP support and reference SAP Note 1919255.
As noted, some SAP NetWeaver systems already contain these supplied
functions from SAP and you should check your system. If these functions
are not available, then you will need to install the transports. If they are
available, then you are ready to begin a connection to SAP Information
Steward.
SAP Information Steward makes a connection to SAP NetWeaver and calls
functions that exist in the SAP application functions construct. What SAP
Information Steward can call and utilize depends on the security permis-
sions and authorizations that are granted to the non-dialog user making
the connection from the SAP Information Steward system. Note that

14
Real -Time Governance with Data Insight I 2

although SAP application functions may not be required, depending on


which version of the SAP NetWeaver stack you are running, SAP custom
security will always be required as a custom setup option, which requires
a design by either SAP Basis or the customer's security team. We will
explore the setup and design of t hese components in the following sec-
tion in much greater detail and also will outline the workflow of the setup
process implementation.

Implementation Workflow
The setup process for the SAP application server can be intimidating, but
there is a relatively predictable process workflow that can be utilized to
guide setup activities. This section will walk through each step in this
workflow.

Install SAP Application Transports if Required


The easiest way to survey your SAP system to see if you need to obtain
and install the SAP transports is to search for the /SAPDS namespace on
the SAP system. To do so, log on to SAP GUI and run Transaction SE37.
The resulting SAP GUI screen allows you to search for the /SAPDS func-
tion group, as shown in Figure 4.

Function Builder: Initial Screen


"' /~ '* m w [(] B:> Reassign.. .

Function Module

f Display II? Change liD Cteate

Fi gure 4 SAP GUI Transaction SE37 w ith /SAPDS Search

If the function modules are not present, consult the readme documenta-
tion on the SAP Data Services server that you used to obtain the trans-
ports (see Figure 5).

15
Real-Time Governance with Data Insight I 2

.. . ,.~=
" -
~
~t:t O.tt(!:) t:'r'cqamFits()t$6) SIP~ O.ta~ <ri"' R3_fl.r'Uons trlSI)Oft

.. ...JQJ2!1
F~ ~ ~!'~> ........ Hfolt>
E This document ident i i es the content o transport i es provided wi th SAP &usinessobjects Data services. .::..
Ttlese fil es use the SAP correction and Transport system (CTS) to instal l the Data servfces provfded
funct1on.s.
!=or detai l ed i nforMati on about install ing SAP functions provided by Data Services, see the SAP
susinessobjects oata services supple~ttnt f Ot" SAP.

E}:Ors/~~taw~~hi~~da~~!~~~l~~l~re!ie~,~s~~~ ~,.~~=~~functions i nto a single funct ion group


1=or SAP BASIS 4.6o or earlier prt Nttwe~ver vers1oos. you can find the necessary oau services funct1oos
in the 900U7 .R22 transport package incl uded i n Data Ser vices Rl_funct.ions/ transport folder .
SAP Nec-.eaver 6.0 and hcer. SAP functions for oata serv1cts are incl uded in three SAP coeponents : PIJASIS, SAP....APPI,. and SAPJ'~ .
If your system dots not contain t~se functions or- 0\1 plan to upgrade SAP systems. see SAP Note 1919255
F for information about Data Service'S transpt functlons .

Figure 5 readme.txt File Path and Contents

Here, there are basically two options: Use the provided transports to
install on a legacy SAP NetWeaver 4.6 system, or obtain the transports
from SAP to install using SAP Note 1919255. If you do have to install the
transports, then please refer to the SAP Data Services supplement for SAP
guide for your version of SAP Information Steward (visit http://
help.sap.com, and look in the DATA MANAGEMENT section).

Design and Implement Security Structures


After the function modules and proper namespace are present on your
SAP system, you will need to ensure that the proper authorizations exist
so that SAP Information Steward connections can be established. Just as
with transports on newer SAP systems, the basic roles may already exist.
You should check your SAP system to see if the roles for SAP Information
Steward are already present.

Roles
Your system may have SAP Information Steward roles SAP_ DS_ DEV and SAP_
DS_PROD if you operate a newer SAP NetWeaver system. If this is the case,
then these roles can be used as templates for defining authorization profiles
for SAP Data Services users working with SAP BASIS/SAP NetWeaver func-
tionality. SAP _DS_DEV is a template for DEVUSER and SAP _DS_PROO is a tem-
plate for TESTUSER/ PRODUSER.

16
Real -Time Govern ance with Data I nsight J 2

In any case, you will need to design security profiles for your service
account that fit each stage of your SAP landscape. SAP Information Stew-
ard needs a variety of authorizations to create content in a development
(dev) system that will not be ne.e ded in a production (prod) or quality
assurance (QA) landscape. You must make sure that your design meets all
of these needs to be successful. Table 1 details the authorizations that are
needed at a high level. but if more information around the details of the
functions accessed in the authorizations is required, please refer to the
SAP Data Services supplement guide for your version of SAP Information
Steward: http://help.sap.com/businessobject/product_guides/sbods42/en/
ds_42_sap_en.pdf.

Service Account Authorization Landscape SAP Authorizations


User Required
DEV_ USER High Development "" S_ BTCH_JOB
"" S_DEVELOP
... S_RFC
... S_TABU_ DIS
"" S_ TCODE
TEST_USE R Medium Test or QA ... S_B TCH_JOB

"" S_ DEVELOP
"" S_RFC
... S_TABU_ DIS
... S_TCODE
PROD_U SER Low Production ... S_ BTCH_JOB
... S_RFC
"" S_TABU_DIS
"" S_ TCODE

Table 1 Typical SAP Information Steward User Authorizations

It is important to note that the users described in Table 1 are not dialog
users, or users that someone would use to access the SAP GUI. These

17
Real -Time Governance with Data Insight I 2

users are strictly for SAP Information Steward to facilitate communication


with the SAP application system. The user-facing security happens on the
SAP Information Steward platform itself in the form of users and roles.
These users and roles are out of scope for this section, as we are strictly
discussing the SAP-related connections that are needed for SAP Informa-
tion Steward to access the SAP system.
It is important to note that SAP authorizations can be managed in two
ways:
Profile generation method
When using the profile generation method, activity groups define and
control all of the allowed authorizations. Each user is assigned to an
activity group that has information about the allowed activities that
each user can perform.
Profiles assigned to users method
The profiles assigned to users method relies on the administrator or
security team first creating the authorizations needed to perform spe-
cific tasks, then creating a user profile to assign the specific authoriza-
tions on the SAP system. After the authorizations and the profile are
both created and activated, the profile may be assigned to users.
Either method is acceptable. The choice should be based on the organiza-
tion and whether the chosen method will fit into existing user mainte-
nance processes and protocols_

Test with SAP Basis and Security to Remediate Issues


The final task to complete before closing out the security work is to test
both the SAP application function modules deployed on the system and
the relative access to the system using the created authorizations to these
function modules. This testing is typically performed by facilitati ng a ses-
sion with an SAP Information Steward subject matter expert (SME) and
both an SAP Basis resource and a security team resource.

18
Real -Time Governance with Data I nsight J 2

The SAP Basis resource is not required if the security team resource has
both the ability and knowledge to run SAP application traces in order to
illustrate distinct processing on the SAP system. The idea is that the SAP
Information Steward SME runs various tests on the SAP Information
Steward system, such as (but not limited to) importing SAP tables, view-
ing data on the tables, creating a view on the SAP tables, and running the
view.
Any one of these tasks may produce errors, which prompts the SAP Basis
and/or security team member to review the errors using the SAP trace, to
see where the system error was occurring and to troubleshoot the error
during an interactive session. If the right people are in the room to trou-
bleshoot any errors, then these sessions go quickly. It should be noted
that any changes made during this process should amend the transports
used to create both the imported function modules and the security
authorization objects and user profiles. By doing so, you can successfully
move all changes at one time throughout the landscape as a unit. This not
only is best practice, but also assures that no valuable work or trouble-
shooting solutions are missed in any of the SAP landscapes.
In the following section, we wil[ first create views of data on mUJitiple
tables, then layer rules on top of these views, and finally place the rules
into the scorecard to produce the end result: a finished SAP Information
Steward scorecard.

2.3 Building an SAP Information Steward Scorecard

One cannot simply jump straight into developing the visualization of a


scorecard. There are many foundational components that must be in
place before this can occur. These building blocks of scorecard develop-
ment start from the ground up. The first of these are the SAP Information
Steward views. You must also create a validation rule, which needs to be
bound to a view and scheduled. Only then are you ready to associate the

19
Real -Time Governance with Data Insight I 2

rule with a scorecard. To begin this process, we will first explore how to
build an SAP Information Steward view in the next section.

Build the View


To have data for a rule to validate, at a minimum you need to have a table
containing the desired data. However, in most highly normalized opera-
tional systems, a table usually will not suffice to provide a proper pro-
ductive data set. The data in most operational systems typically is highly
normalized, or split into segmented tables, and SAP is no different. Take
for instance the material master table in SAP: table MARA. This table is
extremely wide, with over 180 columns for most customers, and one
would think that so many columns should cover most of the data needed
for validation rule processing. However, when you need something as
core to a material as a material description, you need to go to table MAKT
to get it. This is a simple example, but all of SAP is like this. In order to
get data that you need to model a proper business scenario, you must
combine these tables together.
The way to accomplish this in SAP Information Steward is to create a
view. However, with SAP Information Steward, the decision of the user
goes even further. Before creating the view, the SAP Information Steward
developer must decide whether he needs to create a standard view or an
ABAP-enabled application view.

Standard Views

A standard view is a straightforward approach to creating views in SAP


Information Steward. View creation occurs solely in the tool and does not
involve any code creation or management of ABAP in SAP. An example of
a standard view can be seen in Figure 6.

20
Real -Time Governance with Data I nsight I 2

SAP ~ SAP lnformabon Stew.vd w~ .........11:1' ~ ~ '* too Of!'

.... .._, ~1:11::1~~

.............
0 (!Add \J ll"'dlliRW 'hJ C~~oMtieSo:n

- ~ ~ :rt_Gl~_CUST_~..,_'-_..,..._
<.!!! r,ACUiu'otG!Oo.4)
ol' "-Oab :_v.rwii'OI<c tJ Mif'IIOt~
~ - tit Scott "'-Lert Lnt~ 1'* <1
a ..~ x e- .

0 .......
---------
.,; .!!I ~ Otf
.!'! ~Ceo.~~....
.!im~
~ m C!Nli"c
.!'! m Qs!M o;,F.OO.tJ

""1m,.. ~~ r FtWCt~:~cN 4'fJIIX>tto. :t "-M:~te:F*'doe'-

~r" ~
..!> ~ ~,.... 1
.!!~ m~2

Fi gure 6 Completed View in the Rule Resu lts Tab

In this view, there is only data sourced from one table, as you can see in
Figure 7, but you do not need to stop at table KNAl (Customer Master) if
more data is required. For instance, if you need to include mll!ltiple
addresses used over the life of a customer, simply click the ADD button , as
shown in Figure 7.


-
16.., a

EQC-- "6mAt.!W<El
Ouo~T-

,.,dolr(IO)
...~tw(.f)

-dW(3$)
-
a-.-.
o.-~Gteq,

~I.OitTOt

to:~I.AHW)
,.....""
'>dw(IS) ...
01>

_ ...(31)

..-.dw()$) HOoM~.-.::iii'Cfl

Figure 7 View Editor Window, Used to Create the View

The number of tables that you combine is limited only by the business
scenarios you are trying measure with each rule. From that perspective,

21
Real -Time Governance with Data Insight J 2

you really must let the business scenario dictate your design. Just remem-
ber that it is easy to add other tables and join them together. However,
joining these tables also comes with a performance penalty in a standard
view. Taking the standard view in Figure 7 as an example, you may be
transforming the original data in table KNAl with an expression in the
mapping of a field, or processing only active customers as a subset of
table KNAl. The important thing to note is that data must first be extracted
from SAP to the SAP Information Steward application server for process-
ing. This does not mean that SAP Information Steward stores any of the
customer data. The application server processes the data as it is streamed
from SAP. This is something to particularly watch with standard views
that contain multiple tables. For example, if you have two tables and your
processing requires the entire data set from both tables, then both tables
will be extracted from SAP, and the combination of the two data sets will
occur entirely on the SAP Information Steward server. This is fine for
master data tables like KNAl , as they do not contain nearly as much data as
transactional tables. The data will fit into memory on the application
server.
There is a simplicity involved here. The SAP Information Steward devel-
oper just creates the view using the GUI, saves it, and then executes the
view against SAP. There is no involvement with SAP Basis, a security
team, or a team of ABAP programmers. This allows for rapid prototyping
and development, and most importantly places all development control
in the hands of the SAP Information Steward team. This is crucial for
these efforts to have a rapid deployment time. However, as stated before,
there is a limit to how much data you can fit into memory on the applica-
tion server. When you run out of memory, the SAP Information Steward
application server will start to page the data to the disk, and performance
will all but grind to a halt. There is no danger to the SAP NetWeaver sys-
tem, as the data is extracted only in tiny, 10,000 record segments and
compiled on the SAP Information Steward server. The problem is that
your processing in SAP Information Steward will essentially stop when

22
Real -Time Governance with Data Insight I 2

the memory limit is reached. When you encounter problems like these, it
is time to consider creating ABAP-enabled SAP application views.

ABAP-Enabled SAP Application Views


ABAP-enabled SAP application views are exactly what they sound like .
ABAP is created on the SAP NetWeaver system, and processing occurs
entirely on the SAP system before the data set is streamed back to the SAP
Information Steward application server. This is extremely important for
combining very large transaction tables. Creating an ABAP-enabled view
is simple. The only thing that the SAP Information Steward developer
needs to do is to select ABAP from the DATA TRANSFER METHOD drop-
down menu, as shown in Figure 8.

'"""
-
co"' a
.... _-
~rctw(JO)

-..rctw(-'9
0...~~ l

O..~Acr;oo.ntCiroo.o

-N-()$) (My

-dw(1SJ Tilll
\ortJW(lS) ,._ 2
. . . . .OS) ~IV!W~J~ffl

.... -
- """"

Fi gure 8 View Editor W indow with Data Transfer Method Dropdown

Then, just select the processing option from DATA TRANSFER METHOD.
However, this action only begins the process of managing the generated
ABAP code through the SAP NetWeaver landscape. After generating the
ABAP, it must be transported from the development system to the test
system, and after testing it must be transported again to production. Both
of these SAP transports must occur, because the generated code is now
SAP NetWeaver code and must be managed just like any other SAP appli-

23
Real -Time Governance with Data Insight I 2

cation development. This is not only additional overhead to a proj ect; you
also affect other teams with the introduction of the SAP Basis team at a
minimum and sometimes the SAP Security team. These teams will have
different priorities from the core SAP Information Steward development
team and therefore can significantly slow the SAP Information Steward
development process.
The following four phases are typical for application development:
1. In the design phase, a high-security profile user designs the data and
work flows and generates ABAP programs. The ABAP programs are
pushed to the development SAP landscape and executed.
2. In the consolidation phase, developers upload generated ABAP pro-
grams into the test SAP system with predefined program names and
preregistered connections. A user in this phase can run these programs
with a lower security profile- TESTUSER, for example.
3. In the test phase, the SAP Information Steward views must be exported
to test the SAP Information Steward landscape, and the generated ABAP
programs must be transported to the SAP test system. This process is
usually performed by an SAP Basis resource in the organization.
4 The production phase begins when no additional program modifica-
tions are required. The user involved in the move to the production
phase has the lowest security profile or fewest permissions.
Now that we have a good understanding of what is involved with view
creation, we can move on to the second phase in building an SAP Infor-
mation Steward scorecard: building a rule.

Build a Rule
Rules provide the quantitative foundation to demonstrate whether your
data conforms to your business scenarios. Rules can drive operational
behavior and can fit together to tell a greater story in a scorecard. At their
core, rules are pass/fail conditional objects. Failure records are reported

24
Real -Time Governance with Data Insight J 2

in scores that display next to the columns to which they are bound, as
shown in Figure 9, by the red and green rectangles holding blue numbers.
When you click on the blue numbers, if there are failed data records they
will be displayed in the FAILED DATA section shown at the bottom right of
Figure 9. This is an operational view allowing a user to quickly see how
various fields are performing according to business rules that are bound
to the table. You can also quickly share this data with others in the orga-
nization by exporting to Microsoft Excel. Doing so helps drive data qual-
ity in the organization by quickly elevating and allowing access to the root
of the problem so that users can correct the data quality issues back in the
source system.

SAP----. SAP lnfotm.JtJon Stew.ard w~ ...._ o- lW>IOf vw. ~ l~ oa

......- ~11:::!!:::1~~

- ()' ... -
U C.:: Zli.C ISftlM.~:J
--
, LJ C.... ZB.C1S~"M.~
<t> U ~ l9.Gt4..0JST.~t1~
..to u O za.r.H_OJ>T_~.,__o,.~
"-' W C: ZI.GH.OJ>T.~tl~.-.ot
'1l .
li LJ
IJ E ze_cm_o..tn_~t~p-.-.m--.,
t: Zl..'l'\P.$T.Jicrolr.O.tt.,.Adlte.
"~'
t/14t'l '7 ,..-.to-w
.u ~AIXOo.tii:C)G,C~ ~c.- HtwO'oecrll -~~~ .l YoewMe!cl'lllirdo..r.t

- U ~""
\:) zt.GH.a..os-.Ot'!f$:15
_,; LJ ~~

Figure 9 Validation Rule Scores in the Rule !Results Tab

In combination with the SAP application views discussed earlier, this


complex and fully customizable data quality monitoring can occur in real
time against the SAP system in a holistic manner. This is an important
operational activity in the SAP S/4HANA world. If the SAP ERP system is
on SAP HANA and reporting is now in real time, then it is more important
than ever not only for the data in SAP to be of high quality in the source,
but also that issues be remediated as quickly as possible.

25
Real -Time Governance with Data Insight I 2

The operational view of the rules shown in Figure 9 are a result of the
designed rules. To code and develop a rule, you must navigate to the Rule
Editor, as shown in Figure 10.
The Rule Editor is the GUI in which rule development occurs, to both
design and compose the rule. Note the relative lack of a normal coding
interface. After you give a rule a name and description, you need to set up
its parameters. Parameters are required; they are the conduit for connect-
ing, or binding, the rule to columns in views and tables. The rule on its
own is just a set of instructions. Only when it is bound to a table or view
does it take action and produce scores and failed data. Therefore, estab-
lishing parameters is the first step.

Properties C~tom AttriiMrt~

Status: Edrtmg

Aulhot:"' AdrnirisiJotof

~lmpoc.tPttFabe: s 0 Edt.. .

X "'J _CXV (Snoli'IIJI

X SP_I_OA.y

AddelrHSIOn

SEGJN Rrn.R.H
SPJ ..Cttv IS NO.. tut
/In) soJ ..Otv 1 ~:

Figure 10 Rule Editor GUI Window, Used to Develop Rules

Figure 10 shows the rule ZB_G l 4_Cus t omers , which has an assigned
parameter called $P _ l _ City in the PARAMETERS section. This parameter is
merely a placeholder for the city data that will be met when you bind the
rule to the table or view containing city data. The evaluation of the city

26
Real -Time Governance with Data Insight J 2

data will occur based on what is specified in the EXPRESSION section. In


this example, parameter $P_I_Ci t y is used to evaluate a NULL condition
and not equal to blank values. Notice that the expressions are developed
using the GUI screens and the foUowing "code" is generated into the sec-
tion you see in Figure 10:
BEGI N RETU RN
$P_I_C ity I S NOT NUL L
AND $P_I_C ity ! = ' ';

A nice aspect here is that you did not have to write this code as a devel-
oper. The development occurred using the tools in the GUI, which greatly
enhances the opportunity for less technical resources to develop rules.
There are times when rules will not be this simple or straightforward and
traditional coding will be required, which is why SAP Information Stew-
ard offers the ADVANCED RULE EDITOR perspective shown in Figure 11.

Advan<led Rule Edtor X

Templote Keyword Operotor C.,_._ Dote Lodo.!> Moth Stmg Volidotlon Por"""'te<

1 BEGIN RETURN
2 $P_!_City IS NOT NULL
3 ANO $P_I_City =..;
4 END

el Volidote S)'ntax Pr'1 Test =


Desaiptlon U>e l'lJmbe<

OK cancel

Figure 11 Advanced Rule Editor Used for Complex Logic

In this perspective, the developer can use sophisticated templates for


proper best practices code and GUI-driven functions or parameter value
assignments . The functions are grouped into the following types in the
Advanced Rule Editor:

27
Real -Time Governance with Data Insight I 2

)} CONVERSION
Functions to convert data types from one to another.
)} DATE
Good support for traditional date-based functions, such as formatting
and date parts.
)} LOOKUP
Functions used to iteratively look up values from external files or tables.
MATH
Wide array of built-in mathematical functions.
)} STRING
Many standard string functions to ease comparison and parsing of
string values.
)} VALIDATION
Functions structured around pattern validation.
The Advanced Rule Editor shares many characteristics with conventional
programming tools, so a seasoned developer can feel right at home.
Another benefit is that the syntax of the scripting language in SAP Infor-
mation Steward is actually the same as that of SAP Data Services. This is a
great benefit for organizations that are choosing to standardize on the
SAP toolset, because there is a great deal of overlap both in terms of
functionality and syntax. The Advanced Rule Editor is a great platform
to create even the most complex rules. However, until a rule is bound to
a view or table, the rule is in a useless state. You have designed, devel-
oped, and created a rule, and now you must bind it.

Bind a Rule
Binding a rule is a straightforward task - and incredibly important.
Without a connection, the rule is useless. Now, let's bind a rule to a
dataset. To bind a rule to a view or table, click the BIND button high-
lighted in Figure 12.

28
Real -Time Governance with Data I nsight J 2

I ~ ....

100 Rulos

tt- (} ... ""*"' ~ CCOY ~


X o.<o" If> :. ft!
Q -'"''
~ -"' ..... IJ litO. 8 '
SttU l\.ll;llit
O'Mt'entWf\Mbr'ldtlos l ..CIIt\'tldSU
DHol>*: ~tov..W.ttifOtyfot~P~/0..

lll ~ ZB,.G14,.0JST..OitvEJ6t:s E6.,.


Author: AdminiStratOr At:Jct(1oo':
~ ZB,.Gl4,.CUST..~o...
Jo ~ Z8..G14..CUST,.Ccu\ttyCod...

~ ZB,.C14..0JST.,Ccu\t'yl(ey...
CB ~ ZB..Gt4..0J!>T..Cus-tcmereo...

,,
~ ZB..G14_0JST_Cu$10tlletGI>...

ZB..Gt..CU$T_(;115~1:10nC...
ZB..GJ4:..0JST~U

,~ Z8..G14:..CUST..&l'lailAckhf, ..

!!!
ZB..GJ..CUSTfttT~..
ZB..G14..CUST~...

l:t
.
ZB,.G14,.CUSTJ.IC~..

.'Ill 1fl <a nm J. . _ \'*1 ...._

Figure 12 Click the Bind Button to Anchor a Rule to the View Column(s)

After clicking the BIND button , the RuLE BINDING EDITOR screen opens, as
shown in Figure 13.

Ruk Binding lditor X

._. ZB,.Gl<\_asT..Ot)E*ts s-.- D Vlews..lB_Gt<t..OJST..Gcncral>at.t,..Adctcs:5


P".-..-nctet:

-
""""'
~ Oty

Figure 13 Rule Binding Editor GUI W i ndow to Select Bound Column(s)

The Rule Binding Editor is a straightforward screen used to map the phys-
ical City field from the ZB_G14_CUST_Gene ral Data_Add ress view. After
that relationship is set, you can save the rule binding. You can also set a
threshold under the THRESHOLD section. This will change the color of the
display based on the settings. This way, the rule behavior and display can
be altered based on the severity or impact of the business scenario. After
the rule is bound to the view, you are ready to collect scores by running
the rule task and setting up a schedule.

29
Real -Time Governance with Data Insight I 2

Run the Rule Task and Schedule


Now that you have bound a rule, you need to calculate its scores. This is
required to move forward in the scorecard process and to activate the rule
and promote it into a useful state. For a rule to be useful and measure any-
thing, you need it to derive a score. The first step in this process is to run
a rule task in an interactive mode to provide scores to review in SAP
Information Steward.
After review, the final step will be to schedule the rule tasks in the SAP
Information Platform Services Central Management Console (CMC). This
way, scores are collected at regular intervals to provide checkpoints of
quantitative rule and data performance that drive governance activities
and underpin the SAP Information Steward scorecard. Let's examine
what tasks look like in SAP Information Steward. Figure 14 shows a series
of tasks, including both task history and an actively running task.

Adltn lOf 1/t<YLSl:OINol Al..t'rio"'(6tl!6~

.ldlirin'ftlf 8/I2QLSl:S1fiM ~ &/120l.Sl:"PM 00:01!<40


....,.,..,.lOr I/IV2lJLSl:~_,.. ~ 8/li'I(:IJ I.S l:Uill'tl OO:OI:rt
............ f/14/}01$2:"''" ~ fii (11-S l:.. PM OO:OI:U
~.- l/1ll)lS 2;4) fOM ~ lfl'l(li)JS :t<~SPM 00:01; ..
. . . . . .. !Of l'Ml01~12l-.sfiM ~

Fi gure 14 Tasks Tab Highlight ing Running Ru le Task

Although task history is visible on the TASKS tab, the tasks are created by
calculating the score for a particular table or view. This is done on the
RuLE RESULTS tab by selecting the table(s) or view(s) you wish to calculate
and clicking CALCULATE SCORE, as shown in Figure 15.

After you click CALCULATE SCORE, the DEFINE TASK: RULE screen appears,
as shown in Figure 16.

30
Real -Time Governance with Data Insight 2

W~ Home

. t!l lWIIOr"'-"
[}Add

-
~ \.!1
\. andiiO~ !ln c.&cu.t.e ~

~ Zli.C!~.CUST.C~~
~.,. 91
q """0.:.. :. v..~

fSCIOI'Iden
Sa:ltt .-nmLMt
-
t.astRIII
S/19/lOlS
f*d
1
b ...~ )(

Totll
281~
OH> ----------------"'1
'-! .


.jj U O .zs.c:..OJST..c~ea .-.:e CIA-lOf'l "' rren::~ Od:onSoore to-trW.
~ tJ f! ZB.G:<I,.OJST.C~~.}'a ~~- 8/1<001S 0

@ U C) ZB..G:. OJST..~.C.~.Adlhu 8/:"/lllS 5596 S596 0...*


-ll lJ t:J ze.G:'I.CUST..~.O.'-.Gcnt.ciPwW> t/t~tS <UtO....
.t 1!J C ZB..Ct'I. OJST..Genet.O..~..CO'wtlol 0 0$:1n
-ll lJ (J 2li.Gt4. CUST.Generllh:..,tloorJe:-.a

ii) (,] 0 ZII,.G!-l,.OJST,.GetwriiiDe.:..fa,_,..,Hr~ 8/19/2015

U C m..c:..OJST..MIM"f
~ U ~ lB..G:..OJST..SIItiA'~~~
..t~ (J CJ 28..G!'I..OJST_$*W~~ 0 12236~

U L?) li..Gt'I..OJST~~_s.e,.
.i)
""""
.
..tJ U [ l ZII..G!-I..OJST~t..O..:.Jhoono

..n_m G!S..'M)ILC<In'oltJ'(~tl~nf..
'""'"
258AYtr'Cb "'

Fi gure 15 Click Calculate Score to Create a Ru le Task

)(
a \f1tw4.m_ct..osr..~..Got~
Nne lilt ~ loWIIrlluttUt ........
)( 111 ....
"" u
)( w tJ V1f:wos.ZII..<it~Q.IST-~.oot.t..~ ... u
X t1 0 ~.li..Gt~OJST..Gele.O.C._fltc)orC.&t ... ""' u
J( \t) a ~.m_ca~_OJST_Ge'ler~ymtf'l(f(~ .... u
)( J 1;8 Y'l!wJ,Z8_GI~OJST~ u
...""
AI
X \tl ~~ ~.ZII_COt~o.&r~~~ AI u
X .l.l Ill ~.li_<OI~_QJST_::.b~~-- AI []
X tl Ill ~.Zli..GI~CUST_$11tsNNOrec;t_Utt AJ u
.tl III Y~twt.ZB..GtS_'tM)IL~t.t~lfiMO"'
...""
[]
X
X. t1 s::l ~s.ZB..Gt5..\tCliL~tt..Ccr~
AI
AI u I
""
----
.... c..

Fi gure 16 Define Task: Rule Window to Specify View(s) or Table(s) to Process

However many tables or views you selected from the RULE RESULTS screen
will display on the DEFINE TASK: RULE screen. From this screen, click SAVE
AND RuN Now. This will create all of the scoring that appears in the RULE
RESULTS screens. This is one example of running the rules interactively
against the source system.

This process is fine from an operational standpoint, but to make the rules
available to underpin a scorecard as a foundation for governance you

31
Real -Time Governance with Data Insight I 2

want to schedule task processing so that scores can be calculated at recur-


ring intervals. The recurrence will be crucial to produce a scorecard with
proper and timely checkpoints for data quality.
Scheduling the rule task is something that would seem likely to be accom-
plished in the SAP Information Steward application, but this is not the
case. Scheduling instead occurs in the CMC, which is an SAP Business-
Objects legacy component that controls both security and scheduling.
Access the CMC by using the URL http://<servemame>:8080/BOE/CMC.
From the initial CMC screen, nog in with your user name and password.
You can use a variety of methods to administer security for SAP Informa-
tion Steward, but to keep the examples simple for this publication we
have chosen to use out-of-the-box Enterprise CMC authentication. All
user interaction for the following examples is performed with the Admi-
nistrator account; this is something that would need to change for a pro-
duction-ready scorecard or project.
After you log in to CMC, you will see the CMC home screen. To get to SAP
Information Steward-relevant content, click the INFORMATION STEWARD
link. as shown in Figure 17.

Central Management Con1-ole

CMCIIO.,. Welcome: Ad"*'ktrator I Preftnees IH.-, I Log Off

Organize Ocr...
,_,. n Ac<:ess LE'WIS
..li
~
Per1otlal Foldtts
c.._.., , .......
Qlllf'IISors AppllcatiOtls
~ s.ttlogs
P ~a1Cetf90rits .II> S..Ons
&; UW'S and Croups A AuthcnbtabOn
C. rtlboxf's
t "'"'"..,..
!i'J s.n..,. '9 PromotiOn Mo~I'C
e QueryRt:sukS IE VetSiOn ~t
r..._..,s...g.
{f OMa StMcts . ...........
Q, AUd"*'9

Fi gure 17 SAP Information Steward Lin k to Navigate to Scheduling Tasks in CMC

32
Real -Time Governance with Data Insight I 2

After clicking the INFORMATION STEWARD link, navigate down the INFOR-
MATION STEWARD tree to DATA INSIGHT and select the PROJECTS folder, as
shown in Figure 18.

9 1'9 ht1P:/ Iocallo<t:SOSOJ80E/CMC/150716t44S,acklwvApoft>oMe.faces>servoce=' :.:J ~~ X


~====~-----------=
I 61o
~~P
'lof Favorites It" 1.!1 :>U99e>'<o 5< es ~\ oo S'<o Gal<<y

-f!Central Management Console

Central Management Console

Information Ste\1/ard 3 Welcome: Administrator I Preferences I Help I Log Off

A: ~ Acton .

(JJ j,~ iJ. td ,It 0


0 '" "* I oft ~ ~

~ IS
o'fi '"
l)l' tnloonation Steward ...
Name Description Created
Projects Projects Sep 20. 2014 8:58:36 PM
'"11! Iii' (',. ~1etadata Management ....

:1' e f! oata ~~
~I ll:l- ~ Projocts

<i2l !if im Data Review


:a.< 9 .tl cleansing pac:lcage$
~
~
IJi1
~
~

Fi gure 18 Data Insight Projects Section in CMC

Then, browse the PROJECTS folder and navigate to the IS_RDS_MATERIAL


project, as shown in Figure 19.

This project was shown earlier in SAP Information Steward and is where
all of the rule and view work is stored. You will notice that the rule task
CUST_ Remai nder _ Rules shown in Figure 19 is the same rule task that was
run interactively earlier in the section. Right-dick CUST_REMAINDER_
RULES and select SCHEDULE from the popup menu, as shown in Figure 20.

33
Real -Time Governance with Data Insight 2

" x t---====~-----------=~~
e . -.o p

(.tr ~ ""' Pooe Safety Tools fl

Central Management Console

tnformetion Steward ..:J Welcome: AdmJnlstrator I Preferences I He" I Log Off

'"''"'
'c o ; I of I
l.,.

Name Task Type Profile Task Type Created

Ill
r8
CUST_Remaonder_Rules
pro_CUST_ROS
Rule
Rule
AdmmtStrator
Administrator
mm
Mar 9, 2015
(il I'IA_CUST_CompanyCodeOeUI_ Rule Administrator Aug 141, 201
('Q rlA_CUST_ComponyCodeOoto_ Rule AdminiW"ator Aug 14, 201
C& rlA_CUST_Contl>ctf>erson Rule Admlnlstretor Aug 14,201
r8 rlA_CUST_Generai..Address Rule Administrlltor Aug 14, 201

(f)-- r:! Data Review


tB ~ o..-.. -

Figure 19 Rule Task Shown in the IS_RDS_Material Project in CMC

~ I"P "''P' ~Dirl,ecJE.OICJton7!4144~...,..~.~~-'11.3'...,.....,....,.~~~ :3 ,,


f-- -9~-~teo.::.t!

Central Management Console


Wtlcome: Adhlstrator I Prefer.nus I Httl I l og Off

.._ t.,:k Type: 1'.-olie Tti! Ty"


~ <4 <I l el l

l e:atii.UIIShtw

131''H'f$.Y 4
~ -~~ ~
8 o.w~
IB pt'O_CUST_RO! PI'~ ,._,,., Mar 9, 2015 l2:4S; 37 PM ......
IJl nA_CUST_Com Export EXiea1tk:f1 Commond Adnunisttator Aug 14, 2015 2:S7:$4 PM Compltd

...,_
e ~o~ .._,.
1B nA_cusr_eom Aug 14, 201S 2:46:20 PM complr.t<l
lUQa- ra
HI!Of)'
n.<_cusr_c.o,.,...-;;-=c-:..,..-------' Adrnir.stretor """""""'" Aug 14, 20t S 2:43:19 PM Compltetd
[n~Ptoject
ra n.<_cusr_ce ~ ,._,,., Aug 14, 2015 2:52!19 PM comple-:e<l

-
Lj.,_.t.Tcst
usersewnry
lt.l~
... ~
......

.. .. ~.

Figure 20 Scheduling Link on Rule Tasks in CMC

34
Real -Time Governance with Data I nsight I 2

After clicking SCHEDULE, the SCHEDULE: CUST_REMINDER_RULES dialog


box opens, as shown in Figure 21.

Schedule: aJST Remainder Rules


Hide Navigation
-
Export Execution ColT Recurrence
History I
Run object: Now 3
Properties Object will run now.
... Schedule Number of retries allowed: 0
-- I
Parameters
Events
Retry interval in seconds: 1800 I
Instance Title
Notification

user Security

Figure 21 Rec urren ce Options for Rule Task Schedule in CMC

This screen displays the available recurrence options to create the Sched-
ule for the rule task. Select DAILY from the RUN OBJECT dropdown menu
to run this rule daily per your business rules (see Figure 22).

is<ne<tule: aJST_Remainder Rules ?ClX


~ide Navigation
Co,) Recurrence
Export Execution
History Run object: Now .
Properties Object w ill r Now
... Schedule
Once
Number of r Hourly
--
Parameters Retry inte
Events
Weekly --
Monthly
Instance Title Nth Day of Month
Notification 1st Monday of Month
l ast Day of Month
X Day of Nth Week of the Month
User Security calendar
i
~I I .!.]
Schedule! <:arell I
Figure 22 Recurrence Opt ions f or Rule Task Schedule in CMC

This adds the START DATE/TIME and END DATE/TIME fields to specify
when you wish to start and end the schedule (see Figure 23). Clicking
ScHEDULE will instigate the task and start it running in the CMC, as
shown in Figure 24.

35
Real -Time Governance with Data Insight I 2

Schedule: CUST_Remainder_Rules ? 0 X
Hide Nrwig~tion

=~Exeootlon Corr :::~:~r:lO--::&ll:y--------:.:J'~


Properties Object will run once every N d&yS.
"' Sclledule D&'(S(N) =1
Parameters s tart Date/Time: f0s31 12 :.:J lAM :.:J ~/15/2015 1EJ
Ewnts End Date/Time: fOs3 [3i":.:J lAM :.:J "'"~/:-:-:15:-::/2"'02:::5,....---- .EJ
Instance Title
Number of retries allowed: 0
Notification
Retry Interval in seconds: 1800

User Security

Figure 23 Daily Opt ions Detailed

Data Insight Ta sk lfostory


Hide Navi ation

..____
Export ExeOJtion Corr
Actions II) . -1:' ~ 1 of 1 ~
Properties Sdtedule Status Start n me End Tme
Sdled u~ Name ...
Sclledule
[i CUST_Remainder_Rules Ft~iled Aug 15, 2015 5:02:51 AM Aug 15, 2
user Security
~ CUST_Remamder_Rules Recurnng
00 CUST_Remainder _Rules Running Aug 15, 2015 5:36:00 AM

Figure 24 Created Recurring Task and the Running Task

The task will immediately run, but more importantly, a recurring task is
established to run the rule at the specified interval (in this case, daily).
Scheduling any other rule task is accomplished in the same manner and
must be repeated whenever schedules are needed. After the schedule
completes, you will need to log back into SAP Information Steward to
view the score results on the connection, as shown in Figure 25.
It is important to note that the resource responsible for scheduling the
rules and scorecard tasks detailed in the section Schedule Scorecard
Application Component may not be the same resource that creates the
rules and views in SAP Information Steward. We find that typically sched-
uling- and CMC-related work is relegated to an IT resource rather than a
business-focused, technical resource that creates SAP Information Stew-
ard content.
Real -Time Governance with Data Insight J 2

SAP-,. SAP!n~St-.~rd w-.... ~-~ - - - ._ t~ott


........... ~IIZ:ll~.:::r:::::ml

LJ c:J a~c;Jt~CUST,.,...N!M"..~-!VltlOI 1(11i())U

U () D.f.H.CMT~,.jllt$
. u (l a _c.._cu;r~....,_~
u CJ ..Gu.~..~~ t11~
u tJ za_ca~-~~-CI:In'~ U1'\'1S
. u C] a_,,s_~~.J.,_,.rr, ..__..

~ u O a.con_~(;eroer-=-~

u '-~
Ll ~""
,.:s zs_.- 1-S_IIMlll_~

LJ t, (ol.nlly
'"' "
u m&t.th '"' "

Fi gure 25 Viewing Failed Data in SAP Information Steward Rule Results

Associate Rules with a Scorecard


Compared with rule development, associating rules with a scorecard is
easy and straightforward. Scorecards only consume content already cre-
ated, so they are much like a reporting presentation layer. You will see as
we step through the examples in this section that very little of the score-
card is created as part of this process; it simply repackages existing con-
tent. The scorecard is assembled in the ScoRECARD SETUP screen shown in
Figure 26.

SAP .. SAP JnfllWWfl Stt-d ........._ ~ ~ ~ "b woOl

...... - ~~~ICI:I::EI

~ SOO.~Sfbop

Ill
(D~~ t.e ~ ...... ~-t>t-~~-"'*~~

--
"
-
r

--
(!I

Fi gure 26 Click Add to Create a Key Data Domain

37
Real -Time Governance with Data Insight I 2

Click ADD in the KEY DATA DOMAIN top-left section, and the KEY DATA
DOMAIN DEFINITION screen will popup, as shown in Figure 27.

Kev Data Domain Definition )(

Name' ERPCusb>met

Desal>llan: Coleci!On of rules that mon;tor and me.,.. tho relauve q.Jality of data for tho
ERP Cuob>met data domain.I

Sov Cane.!

Figure 27 Define the Key Data Domain w ith a Name and Description

Define the key data domain by first providing a name-in this example,
"ERP Customer"- and then providing a description for the name that you
chose. It is important to note that the key data domain will beco me the
graphic that most users will associate with the scorecard, so it is very
important that both the name and the description be both concise and
accurate. Now that you have the key data domain defined, click ADD
under the QUALITY DIMENSIONS top-middle section (see Figure 28). This
will open the popup screen ASSOCIATE DIMENSIONS FOR: ERP CUSTOMER,
shown in Figure 29 .

.;;: m...~"-""to,tT(~-....,__.o~-"""'~- o
c.,..o.~.,.,._ ~.,.._...

--
Figure 28 Add Relevant Quality Dimensions to Key Data Domain
Real -Time Governance with Data Insight I 2

Associate Dimensions for. ERP Custon>er

U Name

0
~ Acru:acy
~ Completeness
ba Conformity

0 Consistency
0 Integrity

r 1 Tl-"-
Fi gure 29 Quality Dimensions Possible for Key Data Domain

For this example, select the ACCURACY, COMPLETENESS, and CONFORMITY


quality dimensions from the ASSOCIATE DIMENSIONS FOR: ERP CUSTOMER
popup screen. After clicking SAVE , you will see the quality dimensions in
the SCORECARD SETUP screen (see Figure 30).

ll
Sclore 1.6. 1'10.
le_GI~-~

lO.i.GI..__CJST~IS
-
-- \
Fi gure 30 Add Ru les to t he Scorecard by Clicking Add

With both a key data domain and quality dimensions in place, you are
ready to add rules to the scorecard. To select rules, click ADD in the RULES
top-right pane. The ASSOCIATE RULES FOR: ERP CUSTOMER popup window
will open (see Figure 31).

39
Real -Time Governance with Data Insight 2

Associate R.ules for: ERP Customer> Completeness X

LJ Nom< ~-
u ZB_GH_CUST__ yfJdsts Rule to che<k ifBorl< koy exists forBusllessPortner / Custom
~ 2B_GI4_CUST_Cotyfxists Rule to validate if Oty for Busine:;s P,..tner / OJstner /Ver
0 ZB_G 14_CUST_Compan)<:odeexists Rule to ched< if Company code exists for Business Partner 10
LJ 2B_GI4_CUST_COU'ltryCodeEldsts Rile to validate ifBusW>ess Partner /Customer /Vendot CO<JrY
LJ 2B_GI4_CUST_COU'ltryl(.eyl:xists Rule to check if Coultry exists for Business Partner /OJstne
U ZB_GH_CUST_customtreontactPersOf"'[)!patt:rneJ'ItBd RtM! to validatt ifO.Jstomtr contact ~son Otpartmtnt EXiSt

Save cancel

Figure 31 Select Rule(s)

With rules added to the scorecard, you can select the rule binding by
clicking ADD in the bottom RULE BINDINGS screen (Figure 32). Then , select
the view(s) or table(s) you wish to bind, as shown in Figure 33.

Scrllr. 1.0.. 1"10


m_,14_cu;r_~

a.,I4.Mf~~

-- ....

Figure 32 Click Add to Select Rul e Binding

AJ:sociat~ Rule Bindings for. ERP Customer> CompletenHS > ZB_G14_CUST_(jtyExists X

0 Comection Schema Tobie Col.rlm


~ Views IS_ROS_Materal 2B_GI4_CUST_General>ato_Adcl-ess City
1
Save COncel

Figure 33 Select View Binding to Place in Scorecard

40
Real -Time Governance with Data Insight I 2

Repeat the previous steps until all rule warnings go away and green val-
idation checkboxes appear, as shown in Figure 34. It is important to
remember to not only repeat the previous steps, but also to work in the
same left-to-right and top-down manner to add the rest of the rules and
bindings. You will end up with the completed scorecard shown in
Figure 35.

SAP-. SAP fl'lform;lfDn S.tf'W.wd .,..._ ~~ ~ - ~ loOOIJ

......_, ~11:::1!:!:11~~

......
a. I.OJSt.~

l3.J' !<I.,.CU$t.)-ot.-.dlt"~
-
-
Fi gure 34 Completed Scorecard Binding, Still with Warn ings

-----------------------------------------------------------------------------------
SAP r SAP lnform.ltl)n Sltwill'd ~ " * - ....__ _...,.. . - . 1.00011"

......._ ~IC!::ll~~

WC~.Aoonw ... s l8. r.l4. CUST. O!)etillll

-
II D.f.H.<:UP~~

.... - -
-
-
.....

Figure 35 Completed Scorecard

41
Real -Time Governance with Data Insight I 2

After the scorecard development in the SCORECARD SETUP tab is complete,


you can browse to the SCORECARD link on the SAP Information Steward
homepage to see the scorecardl results (Figure 36). Then, you can explore
the detail of the scorecard (Figure 37). This way, you will ensure that you
have the scorecard properly designed before you assess the weights that
you will assign if needed.

Projects ~ IS_RDS_Materal ~

Showscor~asof: [l ast"RUnJ ! SortBy: [Na~ ~ V"oews: W~ _$_ ci'!' Sha~

ERP Customer Show DetaH

Quality 9 .98
Co<nplet...

Confonn ...

Quality Tr~nd

O~ te Time

Thrahold: Low 5 High 8


No cost infonnotion oclded. ?

Figure 36 Vi ewing t he Scorecard Preview

42
Real -Time Governance with Data I nsight I 2

SAP-- SAP lnformaoon Stewacd wdamr ,.....,....ll:t" ~ ..._ IE.i3 lot Of't

..... ..;-..,.,l ~ICC:II~II:I!::IIIill

,_....
9.97
10.00
~

.t
za_GI1_CUST_~t:occef...

za_<a,._o.m_~tf
Al-'tiOdecloftatl'l>fWCoo:te:fo,
~-~~ow,_ .._.,. ...
es_.ROS_,..,.tl :e_<~:.o.IST.'-'-111 oey
"'"
':S.PJ&)'W".d~ 28.G~4,..ClT..~.. ~I

':S.}U:JSJIIW:uJ 28,.Gt._o.T..,~.. footiiiCbck,~

Figure 37 Viewing Scorecard Detail

Having the scorecard designed and processed is very important and the
end result for scorecard creation, but you are most likely not ready to
move to production until you assess whether or not you need to be con-
cerned about assessing the weights of the key data domain or rules.
Weighting a scorecard is a powerful way to tell a business story with your
data. In the next section, we will discuss weighting and show examples of
how to apply it to a scorecard.

Assess and Set Scorecard Weights


We used all of the default weights on the scorecard created in this section,
but now we will explore how to change those weights and what it means
to do so, both from a logical and a technical perspective. First, Figure 38
shows your finished scorecard.
Use the section to alter the weight of the rule ZB_G14_CUST_
RULES
CITYEXISTS. Set it as a fixed value of 70 percent. The effect of this change
is shown in Figure 39.

43
Real -Time Governance with Data Insight I 2

SAP~ SAPinforrnaOOnStfW.Yd ~..,..,_,Mer ~ l'lr'll' - ~ ~Off

.......... ~a:::!l~ll:l.ll'l!::Eil '

....
L
-
............
-- ....

"" '"

Figure 38 Alter Weights from Defaults to Fixed Amounts

-------------------------------------------------------------------------------
~ SAP lnfonmtl:ln Stew.Yd w~ ~ Aannls:IJIDr Vtew Ml$ lo;Off

,... ,_ ., ~11:1!::1~~

Q SCOrecard Setup

.... ....
j .J6
-.....
ze_G t1_CUST_~
-
..... 10

...
"""
9.95

'''"
us

Figure 39 Scorecard after Weighting Activities

Now that you have declared that the weight of this particular rule should
be 70 percent, the other respective rule, ZB_G14_CUSTNAME0FADDRESS-
Exisrs, automatically shifts to 30 percent. This is a nice time-saving fea-
ture, and the results cascade to the roll up of the scorecard. This weighting
activity is important from a logical perspective, because we are illustrat-
ing that having a city value is much more important from a business con-
text than whether or not you have the name of address values. This is a

44
Real -Time Governance with Data Insight J 2

simple example, but an important concept. The weight of a measure


drives business relevance.
Rule results are very important, but they will never break out of an oper-
ational perspective. Only through scorecard weighting can you tell an
effective business story of data quality compliance. After assembling and
organizing the weights for business content, the scorecard development
is complete and ready to be scheduled. We will illustrate scheduling activ-
ities in the next section.

Schedule Scorecard Application Component


Scheduling the scorecard is much like scheduling rules, as covered in the
section Run the Rule Task and Schedule, but with a couple of important
differences. First, the scorecard will only ever have one task. Rules are
custom-developed objects and can have multiple connections to schedule.
You have the option of whether to roll all scheduled collections into one
task or to schedule multiple tasks at various intervals. With scheduling a
scorecard, you do not have that option.
The other important distinction is that a scorecard calculation will only
run once to calculate the entire scorecard. Because this calculation rolls up
the entire rule result scores at one time, it makes sense that all key data
domains for all rules process at once. This is true whether you have one
key data domain with a few rules, as in the current example, or hundreds
of rules with ten key data domains. The process works the same way with
one calculation regardless. We will now examine the scheduling process
in detail by working through the necessary steps.
First, log in to CMC. Then, click the APPLICATIONS link, as shown in Figure 40.

45
Real -Time Governance with Data Insight 2

Central Management Console

&M=!utmmm-1111111~ welcome: Administrator I Preferences I He\> I l~ Off

.... Organize Define


Folders tilT Access Levels
IIQj Personol Folders C Ollendors
Cot~ries 11 Events
a Personol Clltegories
Manage

"'c
Users ~nd Groups
Inboxes ~ lnstllnce Monoger
@J Servers Ll Applia.tions

G!l Query Resu~s ~ Settings


Temporory Sto111ge ~ Sessions
[ i Data Services ~ Authentication

0~
'
Informouon Steword Ucense Keys
i'> Promotion Management

ii!I Version Management


II}, Auditing

Monitoring
Oyp t~111phic Keys

13 System Configurlltion Wiurd

--(Ta7f*, too% d

Fi gure 40 App lications Link in CMC to Schedule Scorecard

Next, click the INFORMATION STEWARD APPLICATION link from the APPLICA-
TIONS section of the CMC. It is important to note that this is different from
the main INFORMATION STEWARD link shown earlier. The link location is
shown in Figure 41.
Real -Time Governance with Data I nsight 2

fO: Ct!ntrdl Mdndqement Con~le - \Vtndows ln t~met [Xplon:-r


~~~~~--------_:~~
g-y <> li' htll>'l,lo<oho<t:aoao~'CMC/150716!445/""""I"""o,.._facs""'::J ~ X ~~ Sooo P
'{,i F...,Ites -9 c.nv.. _teon.oie o IJ!I!l P090 Safety Tools <&

Central Management Console

Applications Welcome: Adrwinist rat or I Preferences I Het> I Log Off

Findlil:le:

Apt)lic;atlon Name
Alerting Application
Bllaunch pad
central Management console
--
Modify settings for alert notifications
Modify settings for Bl iaundl pad
~ 14

Modify settings for the Central Management console


~ 1 of t ~ .,

~~ If' Collaboration The object used to conRgure collaboration


't V Cystlll Reports Configuration
~ li' Oatll Services Application SAP Dam Services Application
[}! ~ Discussions
~ ,.. HAllA Authentication Used to configure 81 plolform for 550 to HANA

~ (2 Informauon Steward Application InformatiOn Steward ApplicatiOn

.... Monitorinq Application Modify settinqs for the Monitorfnq Appfiution

Figure 41 Application Link for Scheduling in CMC

The U TILITY CONFIGURATIONS page will open, and you will see CALCULATE
SCORECARD, as shown in Figure 420 When you right-click CALCULATE
ScoRECARD, you will see the popup menu shown in Figure 43 0

Utilty Configurations ? 0 X
Hide Nevi &tion
Configure Data aean
Monoge Adioos
Configure Repository

Configur e Application
Name Ty pe Last Run Description
Configure Web Servi<
C&lculate Scorecard Scorecard C&lculator Aug 15, 2015 5:04:16 A '*tili11flifii
View Dat a Services l ) Compute Report une&ge Report l ine&ge Utility oefilult report lin
BI launch Pad Integr Email Notification Emeil Notification Aug 15, 2015 5:03: 18 Af' Defilult inst!!nce
user Security Pllrge Pur ge Utility Aug 13, 2015 9:37: 17 PM Defilult inst!!nce 0

U d&te Se&rch Index Search Index Utili 15, 20 15 5:05:26 Af' Default se&rch in

Figure 42 Righ t -Cli ck Calculate Scorecard to Schedule Scorecard

47
Real -Time Governance with Data Insight 2

ut:iity Configurations ? 0 X
Hide N ~vi g~ti on

Configure D~ta Cle~n


Manage Actions
Configure Repository

l
Expo<t Execution Conmand
~~ l of t ~
tis lory
Configure Application Last Run
Name "" Description
Configure Web Servic
View Data Services Jc
81 Launch Pad Jntegr;
Mf!!iMS
Compute fi :Q

Email Notification
~
Run Now
Email Notification
!- Aug 15, 2015 5:04:16 A Default scorecar
Default report lin
Aug 15, 2015 5:03: 18 Atl Default instance
User Security Purge Purge Utility Aug 13, 2015 9:37: 17 PM Default instance
Updat e Search Index Se~ rch Index Utility Aug 15, 2015 5:05:26 Atl Default search in

Figure 43 Scorecard Schedule Popup Menu

Select DAILY for the frequency from the RUN OBJECT dropdown menu,
and click SCHEDULE (Figure 44) to establish the schedule and the recur-
ring task. Both the recurring and executing task are shown as a result
(Figure 45).

schedule: calculate SCx>recard ? O X


Hide Novigotion
Export Ex<!cution COO Recurrence --
HLSIOI)' I
Run objed: Doily :::1
.,. Schedule Object Will run once f!'lery N dii)'S.
Events OIJYs(N) =It
lnstllnce TIUe StartDate{Tlme: lo6::J 137::J IAM::J ~/15/2015 ..!!]
Notification
End Dote/Time: I06 ::J 137::J I AM ::J ~/15/2025 J!J
L I
User Security
Number or retries allowed: 0 _j
Retry interval In seconds: o I

t J
~ sct.o<lliel CM<ell

Figure 44 Ti ming Options for Daily Scorecard Scheduling in CMC


Metadata Management I 3

utilty Histo ry ?CJX


Hide Navigation
Elcport Execution corr X " , ;.,- ~ I of 2+ H

Schedule Name & Schedule Status Startrme


Schedule l.=J \...01 \..I.IIOU: ~\..U I 11: \..101 U 1\.'I:I.. UI I III~

User Security m~ Calculate Scorecard


Runmng
Recurring
Aug 15, 2015 6:39:31 AM

~ Calculate scorecard Success Sep 20, 2014 9:36:42 PM 5


~ Calculate Scorecard Success Sep 21, 2014 9:37:40 PM 5
~ Calculate Scorecard Success Sep 23, 2014 9:51:19 AM 5
~ Calculate Scorecard Success Sep 24, 2014 7: 15:34 AM 5
~ Calculate Scorecard Success Sep 26, 2014 4: 12:27 PM

Fi gure 45 Calculate Scorecard Task in Recurring and Running Form

This completes the development of the scorecard with Data Insight. In the
next section, we will look at organizing metadata with the Metadata
Management module.

3 Metadata Management
Metadata Management is a powerful tool that allows organizations to
bring insight and governance to an enterprise, but unlike Data Insight, it
is not development-centric. Metadata Management brings transparency
to the relative path of data for an organization and helps organizations
untangle their respective webs of data to support information governance
for an enterprise. This module is built to compile information about the
various systems in an enterprise and expose the interrelationships among
them.
In this section, we will looks at how Metadata Management collects data
and exposes relationships with other SAP systems. We'll look at two spe-
cific examples: connecting with SAP HANA and SAP BusinessObjects
Business Intelligence (BI). From there, we will set up and run the meta-
data collections tasks for these two connections. Finally, we will examine
the results of this collection using SAP Information Steward.

49
Metadata Management I 3

3.1 Connecting to SAP Systems

Metadata Management capitalizes on the development work performed


on other platforms to depict the relationships of different development
environments on one platform. This shows what can happen if a develop-
ment change is made without oversight and how that change may impact
other platforms and development teams. For example, Figure 46 shows
how Metadata Management collects the relative metadata of an SAP
HANA system.
------------------------------------------------------------------------
SAP SAP Jnforrnatlen Stewad wetome donlodM M&nooc v.w Hetl toot

lml:!'%l :"1e-tad<~ta ~.anal]enlent - - - - - - -

;ect ~ Export li$t l::::[

lJ, OfT HANA r-.-...?


l).t~lt)st: ~~.4t0sior/irst.toc.l

Path: &Jsir'oessl~l KANA)

Server lnstonces (1) SchemoJ (67)

llll _S'OS..AI'l
T4bb(S94) ~n(116)
0~(58) Pa6.60"(1 1891)
!Ill ..S'OS_AI.()ll
T-(1)

llll ..S'OS..$1
'""'(Z:l) - ( 3 )

0 ....... (18'17) 0

Cl1 $TA_5TATE_FTXTS
Sct..m. 1)-W.N ~~~YS,..&.JC
o~~ :JHA.utl Da : _$YS_liC
""""(12) ~~
'"""'(17)
lUI STA_VOC W AO<__ Hy_'-<ly_ _AO<_AV
Sc....,.... : PA_otMO
Oloi~:PAj)EMO ~ : _.$Y'S_IHC

C~( l 2) O.ab.-~ I,..SYS_IJC

~ ~ ~
llli STA_VOC2 '"""'(<6)
$('-w, 1PA..)>MO
O.~otab-:PA..,O(MO

" " " " ( 12)


C>d~ : VSUt

sqt. aSElEct OOUHT(boNSPEC_C100ART141'). COUHT(boN.5PEC - .


C"""'(2)

Fi gure 46 SAP HANA Metadata Collection in SAP Information Steward

Alone, this information is powerful , presenting an organized catalog of


available SAP HANA objects. However, this is only a portion of the story.
Let's look at another example of this module collecting metadata rela-
tionships from a reporting system such as SAP BusinessObjects Business

50
Metadata Management I 3

Intelligence (SAP BusinessObjects BI), which consumes data from SAP


HANA (see Figure 47).

SAP SAP lnformaoon Stewd wo~<ome don"""' ""- """ Hdo l090ff

IIZII!ll Mct~dilt.-t""1.an.:~gcm~nt ~-II:IID


,!... Directory BuSiness lnteii!Joence BOE'U

~user: ~

Al.thetltie4ti0r1Mode: secfntPriSe
Ph: &niness Int.e19cnce(DOE41)

UntYet-ses(l47) Re ports (7U) c

~ ..<~.Jl .i) _fnoii'U.TIVI\lU'fxOQIIIe


F'AttWM:A<<~~ R~ TyPt :Wrtblt'II.~Oo<~
Ptth : /.Jfi'tt11:tl/SAPh.hbll'.-~4t< l,.1 ~:2014-0111 1 5.:l':ll
O..sttr :~oll~.hc.!"-400 Fekltr Pitt~: AMtofc.tn c.-:.. S*y~ CNSI.
Repcwtfie6S(6) ~~(2) Val'i~s(2) More

I 01AcctPI1f~e<841-~Doto
~ lYPt :w.b It~~~ Doc~
W.l~ t ttii..OtoOlOS~M

I='...WP.ad>eSAPIPjtR~RP t.oob~<~Py~

l.Wvet"se CJ.Mses(l) L.Wrttse Cornectlons (I) R$0rt:Ftetis(26) ~(S) I.Wvefse0bit:s(26) Mofe

ii 101_t'NJ_Ff_81. .)) 01 ACCT PAY REC 8Al. tADER staglnl;} Data


,iit IWnt I AH..YtAI-.JJ'~
P_.. I Mi>t~~ Lr.tMNfitcl e Z01...0101fltl'l5140
~t. . ;.e.o41~.hc.r~ F~P-:SAPA:RPR~it.).E:RP~~-PAYAil.EIJI ...
UWets. Comecbons (I) Reportfieldi(tOO) Queries(4) Uwerse0bje<:ts(35) More

D~hbo.trds (24) 0 F~(68)

(I AQ(~d o .,.,..,
R~ TyPt :Dr.N>o.ll'lk Ob,.ce
Ut:t Modfltd 1 20 1 ~2'9 09e 1S~ Folders(!)
PW1 10f!TC>trao

(t ASUG2014
It~ fyPt eowt.o Ob)t
.-s(2) R""'ts(<)
~l4odflt,f: ~1+0).21 r.G:.U144

Figure 47 SAP Busin essObjects Bl Metadata Collection in SAP Information Steward

Again, this is useful information, but only a piece of the story. A user
can access some of this information inside SAP BusinessObjects BI , but
the real value here is the ability to consider such systems together with
Metadata Management. Seeing the impact of which reporting objects in
SAP BusinessObj ects BI will be affected by a change to a field in SAP
HANA empowers the development teams of both platforms to see what
will break before any break occurs. This insight will help teams make
better decisions with access to real data.

51
Metadata Management I 3

Consider the consequences of not knowing the impact of changes to a


source field such as Di sc oun ta mount in SAP HANA and the effects it could
have on both the SAP BusinessObjects BI universe and report definitions
of fields stemming from SAP HANA objects. Even before SAP Business-
Objects BI is affected, you want to see the SAP HANA impact as well, as
shown in Figure 48 for the Di sc ou nt amoun t field.

DISCO UNTAMOUNT (Relational_Colwnn) X

SAME AS RELATED TO IMPACT LINEAGE USER DEFINED

- - Zoom: 50% J:;> (J

,..........~.

r--
,_....._.
r--
r-.....-....

,_.....,..
( _...._.
_.
r-..........-- I
r-...-
( onc=ouo..-...

............-....
,_....
(
.........
(-.....-....

~ --
-,_
( oncDUO-

,t-- _.
..........
, ___ .

Fi gure 48 Impact of the Discount Amount Field from SAP HANA

It is apparent why this type of information provides a great deal of value


to an organization. It is vital to note that SAP HANA and SAP Business-
Objects BI are not the only systems from which data can be collected via
Metadata Management. Table 2 presents a full list of systems supported
for metadata collection.

52
Metadata Management I 3

Data Source Version


Data Federator ~ XI 3.0
~ XI 3.0, SP 1
Meta Integration Model Bridge 7.3 (Used for non-SAP system sources)
SAP BusinessObjects Bl ~ XI 3.1, SP 2 or higher
~ 4.0
~ 4 .1
SAP Data Services ~ XI 3.2
~ 4.0
~ 4.1
~ 4.2
SAP BW ~ 7.0
~ 7.3
~ 7.4
SAP Sybase PowerDesigner ~ 16.1
~ 16.5
Data Federator ~ XI 3.0
~ XI 3.0, SP 1

Table 2 Supported Systems for SAP Information Steward Metadata Collection

A number of organizations use SAP HANA together with SAP Business-


Objects BI for a fully capable enterprise-reporting solution. This by no
means is to say that your organization should stop or pause using at this
solution. Ideally, you would capture metadata lineage and impact infor-
mation from any of the systems listed in Table 2.
In this section, we will explain how to configure connections to both SAP
HANA and SAP BusinessObjects 81.

Connection to SAP HANA


Connections to external applications and systems from SAP Information
Steward are made through the SAP BusinessObj ects BI platform that

53
Metadata Management I 3

underlies SAP Information Steward. Most organizations roll out SAP


Information Platform Services (IPS) for the BI platform component per
SAP best practices. In IPS, many administration tasks are performed, such
as security, scheduling, and connections to external systems.

To configure a connection to SAP HANA for metadata collection in SAP


Information Steward , you must first login to CMC on the IPS system. You
can log on to CMC in a variety of ways. We are using Windows Active
Directory (Windows AD) as the login mechanism, but if Windows AD is
not configured in your environment, you may need to choose ENTERPRISE
under the AUTHENTICATION field and use your enterprise login. Enterprise
logins are the out of the box method of communication with SAP Infor-
mation Steward. Regardless of how you log in to CMC, you will see the
CMC home screen. From here, click the INFORMATION STEWARD link.
Clicking INFORMATION STEWARD will take you to the SAP Information
Steward configuration screen (see Figure 49).

Central Management Console

ltnto-mation Stewaod wttomt: dOnJOden I Pri~tl I~ "' I Log Off

"'1- "'-.
.: .....
L-l. ~ User Seo.Jrty
~t(OI'So.lf(.
~ Scu.:e GrOJP
Oe:!iCript.ic)n ere
...
r~ Refre!h !o 0.. 1~ Pro)f(t
rrai'l '""'
SN~Butrwmobjeds&Y.erpr1$19IA:hes$ Intelligence
l;)st A.U fl

l..d 29, 2015 6:39:53 PM 6CE-tl Trahi'lg envhlrlrTGnt l.JI


~ CQMiitO&ltiMJ. .Ik CC!m~ _Trfi'lrq)l. "' !Mi"lmtC.'C)jectsEMI!rpr MheftlnWII~ l.ll ~ 201510:49 16.6M Tetti'lgVRr.-cl~i"ll'''"l ).II
U mt
3
~ roe_'1lWNlrGJ:: SAP eushess<Jbjeett En'a'P"tSI &.etii?SS Jn~elt~ l.JI30, 201'5 6 : .. 9:06 PM 5eocn'J test iteratbl ofacE lrah" lJI
... ........ ~ OOE<OJ<X SAP ilu<r>ma>JOCl!Emlrpr"'M"""Jnll!lll<jenet lJI 31. 2015 4:~:0 1 PM CFT eoe L.h.CII rwrtnl'l'lef"(. ACOJ< lJ1
Solsa&"OI..PS fli eoE<Il SAPBI.It~jKCI~f)"iiiBIAhatlrltell~ Mar~. 20lS 3:15 JO PM
- f!l o.tfnSidlt t:J 6W74R2 5PP Ne~ &.nhess WE Bushes$ Jnt.ellk)ance Mar 30, ailS 4 :32 16 PM Jn3"na1CFT f,W 74 R2 system Mal
"" ol.comecticln5 ~ O..taServt:es4.:S/IIl DataJServtes Oata:lrlteq.-tbn )..-,

=j fo.l ;. Oa Review a_ OFT MANA. SAP MANA Bushes$ Jnell~ M:r 28, 2015 2:07 21 PM Fet
.--, fil CJ ~ Poci<4Qos tJ1 OFT HANA. USER SAP 1-W-lA Bustles$ Jntellk)enc.e Fet
0 ECC76 SAPW<on<rIC.- S.. ...... ln..lll<)o<"<e In~1 eFT ECC76 $}'$18m ,.,......
~ RIOi_()S42_REPt SAP Oillta 5ei'Vbi Oiti lnti9"attln l.l1~ 2015 12:04 16 PM Rkh"s Oit.i SrlniCe$ 42 RepoiltOI)I'Y'oil

Figure 49 SAP Information Steward Configuration Screen

Here, you need to navigate to INTEGRATOR SoURCE, located under the


METADATA MANAGEMENT node. Right-click on INTEGRATOR SOURCE and
select NEw INTEGRATOR SouRCE from the popup menu, as shown in Fig-
ure 49. This will bring you to the INTEGRATOR SOURCE PROPERTIES screen
shown in Figure 50. Here, you will configure the connection for SAP
HANA.

54
Metadata Management I 3

Integrator Sotce Properties ? 0 X


Hde Na>lgotion
Histxry

SChe<I.Jie
lr'll84)'81tz:ll' Type'": SI>PHANA .
Nal'r'IG: OFTHANA
USE< 5ec<.rity
oe.cr~>UOn :

Computer Name'": sap-h;na .clocisionfrst.local HANA tepostory mhMMme

Database""''""-: 30015 Dat4base port rurber

O.ta~>oseuse.- : Dat~LISernatl'le
use<
Database P.l$Sword.. : ..................... ...... o.t~ I)MSWOfd

--
Table SChema: Table sc:hetM. Set the name <01 the schema to
restrict the tJes

Package>: Set: the NJ'I'Ie d ~ to restrict the Jriormation

~ Test comectionl ~ Ccell

Figure so Integrator Source Properties for SAP HANA Configuration

Configuring this connection is relatively straightforward. Table 3 pro-


vides the fields and reference values to use as a guide.

Field Value
INTEGRATOR TYPE SAP HANA
NAME Name of your connection in Information St eward
DESCRIPTION Mean ingful description here if desired
COMPUTER NAME SAP HANA host
DATABASE PORT NUMBER SAP HANA port for connection
DATABASE USER User used for metadata collection
DATABASE PASSWORD Password
TABLE SCHEMA Not required; only supply the schema name t o
restrict col lection if needed
PACKAGES Not required; only supply package names to
rest rict col lection if needed

Table 3 Reference Values for SAP HANA Integrator Source Connection

Click SAVE to complete the configuration of the SAP HANA system for
metadata collection. The metadata integrator source connection in SAP
Information Steward for SAP HANA is complete and ready for metadata
collection.

55
Metadata Marnagement I 3

Before you collect metadata from SAP HANA, you need to set up a similar
connection to SAP BusinessObjects BI, which we will discuss in the fol-
lowing section.

Connection to SAP BusinessObjects 81


Connecting to SAP BusinessObjects BI is similar to connecting to SAP
HANA. Therefore, please refer to Connection to SAP HANA for detailed
information, but for reference the basic steps are as follows:

1 Log in to CMC.
2. Click INFORMATION STEWARD on the main CMC screen.
3. Click INTEGRATOR SOURCE from the popup menu.
After clicking INTEGRATOR SOURCE from the popup menu, select SAP
BUSINESS0BJECTS ENTERPRISE in the INTEGRATOR TYPE field. This will bring
you to the INTEGRATOR SOURCE PROPERTIES configuration, as shown in
Figure 51.

lnt(9"ator SOui"Ce Properties ?O X

Integatcr Type':
Schoci.Jie
user 5ec:IK 1ty

boe4t.dec:isbnftst.local
Js_.-
Pas.'SWO'd:
.......
Looon Password for comedk:n to CMS

Enterp,..se Mettlod to I.M fet loQon ~ion

Bl klu>:h pad ln"Vati:n . - :

Passwad: --
User for 81launch pad "t~ion \Mth

Password IOf' IN: above use.

I
Figure 51 Integrator Source Properties for SAP BusinessObjects Enterprise Configuration
Test Comecbonl ~ Clncell
Metadata Management I 3

On the INTEGRATOR SOURCE PROPERTIES screen shown in Figure 51, use the
values shown in Table 4 as guide]ines for configuration.

Field Value
INTEGRATOR TYPE SAP BusinessObjects Enterprise
NAME Name of your connection in SAP Informa-
t ion Steward
DESCRIPTION Meaningful description here if desired
CMS SERVER NAME SAP BusinessObjects Bl CMS to collect
metadata from
USER NAME User used for metadata collection
PASSWORD Password
AUTHENTICATION METHOD Method to use for logon authentication
Bl LAUNCH PAD INTEGRATION USER Use for Bl Launch Pad authentication; not
required
PASSWORD Not required; password if you use Bl
Launch Pad authentication

Table 4 Reference Values for SAP BusinessObjects Bl Integrator Source Connection

Click SAVE to complete the configuration of the SAP BusinessObjects BI


system for metadata collection. Now that you have connections in place,
you need to set up and run the metadata collection tasks for the SAP
BusinessObjects BI connection and the SAP HANA connection to gather
the metadata for the SAP Information Steward system. We will diiscuss
how to do so in the next section.

3.2 Setting Up and Running Collection Tasks

Setting up and running metadata collection tasks in SAP Information


Steward is performed in CMC. Metadata collection tasks and scheduling
for both the SAP HANA integrator source and the SAP BusinessObjects BI
integrator source work exactly the same way. Therefore, we will use SAP

57
Metadata Management I 3

HANA for the example in this section to set up the tasks; the tasks for SAP
BusinessObjects BI are the same, except that you will select a different
connection for the SAP BusinessObjects BI integrator source.

To set up, run, and schedule the collection task for SAP HANA, first log in
to CMC, just as you did to set up the connection. Then, click the INFOR-
MATION STEWARD link to take you to the SAP Information Steward home
screen, as shown in Figure 52.

Central Ma_na,gement Console


welcome: don .Ioden I Preferences I Hetl I Log Off

.
~ ~~

~... - J ltd ~:

...l
~ c
. . .. a o.lttoriMtion steYtd
B C1; ,...,.,... _
/'l'.ame Type C.teqcwy
~ acE_Tr.1hi"lg0l SAP &.rli"IK$Ct)Jkt$ Enterpri$19c.ls._. lMelliget'Q
~ OCE_Trai'l~l- SAP eusnessc:t;,je(t:s Et\terl)'i$1 Bushm tntelr. gence
l~ R.oo
).1129, 2015 6:39:53 PM
1.113), 2015 10:~:16 Alii
:;::-L:::.::1
l.Sthg uw aM 9'0-4) in"4)CII't )J
llJ e if'tel)atSOI.ruos
~ BCE_lRAINII'Q)! SAP MhesSCOjeets Enter"p'i$1 BI.IShm !ntelllgern l..IIZO, 2015 6 :43:06 PM SEcord test atler'l ofeoe ~at'!.. .u
(J] loii- @I BCE40..NX SAP l!usi'les'SCtljeCts EnterpriSI Busl'less IntelligenCe l.ll 31, 2015 4 :53:01 PM eFT 8CE L..._. E'fflronment A11.1< lJ
MiSQlsu Gr<M.C~S Ji 8CE41 SAP Bushes'SCbp:ts &ltl.>rprlso 8usiless Intelligence Mar 30, 2015 3:1!:30 PM
$ o.t lMt't 11 ewNR2 SAP~ Busi'less W eusnm Intelligence Mar 30, 2015 4:3216 PM .,~erN, CFT ew 74 R2 rs:~m M-.
....,.,.,_ l1 ~Q$GnC0$4.:SAP~SOr'vicos O,t.'I!Mog~ b\
fB ;Jt C>.!U~ ltll-"i~+ltu!!!!.IIIIJer~. .;_: ...:.~~--~~~~t!;.!J~sm&l1='-!Zl'IMIJII#'&I*::!:FE!"Il!l*iBi!!iJiBdli~l IZ!!
~
!8~T HANA USER 5I Bushm !ntelligern FEt
Ill .,)"""-'"'-' ~ ECC76 SJ History nent Busnm IntelligenCe Jnt.emal CR ECC76 system Mat
\! RICH_OS42~ Sdal.l~ Data lntegatkln l.JI29, 2015 12:04:16 PM Rich's Oata Servkes 42 R.epositor) Mat
Ru>-

-
\M'Sec\r;ty

" '9"
Ooolr.l>

Fi gure 52 Click Schedule on the Popup Menu to Schedule Collection Task

At the SAP Information Steward main screen, click the INTEGRATOR


SOURCE link under the M ETADATA MANAGEMENT node (see the left side of
the screen shown in Figure 52) and select the integrator source. For this
example, select the DFT HANA integrator source. Right-dick the integra-
tor source and select the SCHEDULE option to show the SCHEDULE: DFT
HANA screen (see Figure 53). Then, select DAILY under RuN OBJECT on the
schedule for collection.

The finalized screen is shown in Figure 54. When you are done, click
ScHEDULE to implement the changes.

58
Metadata Management I 3

Schedule: OFT HANA ? Cl X


Hide NavigatiOn
History
Properties
Recurrence
Run obj3ct: Now .
SChedule Object will r Now
Once
Parameters 1\tJmber ofr
Hourly
Events Retry 11181 I .

lnst.n:e T itle Weelcly


Monthly
Notifocation
Nth Day of Monlh
1st Monday of Month
user Security
I Last Day of Month
X Day of Nth Week of the Month
Caleo:lar

I
SChedule! cancel!

Figure 53 Set the Frequency as a Daily Interval

~neau1e: OFT HANA

~ld~gatlon
History Recurrence
Properties Run obj3ct: Daily

Schedule Object w ill run once every N days.

Parameters Daysi!'l) = 1

Events Sla't Date/Time: ~ 48 AM 9/7/2015


Instance Tide End Date/Time: I08 48 AM 9/7/2025
Notification
lltlmber o f retries allOwed: 0

Retry nterval in seconds: 1800


user Security

Figure 54 Completed Daily Schedule Screen Ready for Collection

With this step accomplished, and once the schedules run, you will now
collect metadata to review in SAP Information Steward for both integra-
tor sources that have produced data!

3.3 Examining Results in SAP Information Steward

Examining the results of the metadata collection in SAP Information


Steward is a decidedly non-development activity. When examining the
results, each collection type is broken down by objects. For instance,

59
Metadata Management I 3

with SAP HANA, you have collections of tables, views, schemas, and so
on. For SAP BusinessObjects BI, you have universes, reports, connec-
tions, and so on.

Although this is not a development activity, the user of the system must
have enough knowledge of the platforms he/she is exploring to success-
fully navigate the metadata and relationships collected in SAP Informa-
tion Steward. This is an important point, and for the casual business user
with only functional knowledge of the data, it can be a bit daunting. How-
ever, with the proper technical knowledge, the ability to examine results
can be incredibly powerful. Consider an example (see Figure 55): table
FACT_ INTERNET SA LES in the BOOK_USER schema in SAP HANA.

~ SAP irlorf"'\Zloon Stew<rd W'*- don.bcMn ~ ..._ "*' LooOff

lll:!lll:'.:ll - :,...;_-:;;;;;;.,l !IZ:C:II~I:.'I::l:l

T"'*'(Z2-I)

-
....
'AC1_,ntAN[IJo1U$
._
....._
tl ,."(''.)JI1tftf'.t1_SAI.(j_lk.()Qff
u-IOOI<.USOt
O...._ oao00t:J.1$11t
....... _
Ill ~ JNTWt_$At.tS.~
u-. ,I()(IK_,su
D MCUNTD='.O,C1_$toi.CS.ttl*
Sch.Mo loOOf:JSft
~.. oiOQ(,JJVI!
1: -
M(t~ts
u-.toOt:,.usu
Doi._<IIOOIC~
.... .!!. ~ . - !.. !.. "

--
Ad:ltoOb.)e<ltr.,
eollllns(~) (~(23) cct.rms z~>
""'"""'"'
Ql _..,..,. Cl ,~._.S.I(.CZ
~ &001<...~
o. ...... eoot:J,I!VI
1m :nM.l'IW.floS!1t.J
s..cNMo !.OCXJ,ISIEJ'
o....... ~U".Cit
II" 'rfM_t~ft.Sifo!.J
sa-.. aocx._ustR
o.-6001(.U'.Cit
II" J-cM.\)C*_,i\S:ICII.f
so-.,t,OCX_USQ
o......_,OOCII(.~

~~(<10) "'-<("1 , ....... (!<) '""""(!<) (~l.t)

Gl ~..t"fttCJAS1119J Gl ~~-~.J>ASl! 0,..2 ; ; ~t'yt!e.}'J.sl'Zf).; IE OUI'.fi.S!O),.!,.rlft: a:: OUJ.fASZ..t,.l'l'f'E


U.... OtoQ"\.I.SQ ""- Nl<..I.GO' ~ ..o<)le..lla.'P u-.o otoOt;.UCU u-.o~...-:R

o ..,., .ocx__usu
,......,.,
()ol._ , tQOt:_vstR OoM~~ Oot._oe<Xli(_USU ~otoOI<_USOt

eou-(.."'4) ~(Z..) ,___,(:-t) (Git..JMt($)

WTJ'AS201..1.f'l'ft II CIUT..Mt.J't.Sl 4U II o .n_m(JASt1U Ol.!f..nf'IJidl9of_Z m: OUIJYFt.FAS20U


W..WtiOCIC,_UKit W... IIOOit,.USOI: w-- ..oco:J.IIfO S<hwfto o.oot:.U$U so-.toOOt;.,U!U
o.o ... . t()Qt(_VSI(Jt o~ ~ CNII~!IOO':,.VKR ~IQOI(_ustt l)oo. . . . !ltOOIC..~

C~(n')

""'"""'"'
Cd.Jirn5(S)

II
""""'"'
fNf.f'f'f..~.J Ill o.n_Nt._Pt.$:10.) Dl QJI_1YP(_PA$ti.J r ovr_rrfCJA.Sm..J I'
CCUMs
___ !Z7)
_;tat

~ l loO<*J.I!ll' ~ 1 .0CXJ,I$(R
u.-oi&OOI(.ustft
,...._,IIO()I(J,alt
S... ! &OOIC_UStt

.,._,,,
0 "'-"'- ~ ~........ ~ o..-.IIOCI(JJV..
u-1to(lelUSU
o.......... IIOCte:J.II"A
.,.....(e)
""""'"' '""'""" (~!3)

Fi gure 55 Menu for Navigating Table BOOK_USER.FACT_I NTERNET_SALES

The bread crumbs at the top of Figure 55 show how we navigated to the
table DIRECTORY BUSINESS INTELLIGENCE DFT HANA (an SAP HANA
metadata collection we ran) SCHEMA$ BOOK_ USER TABLES.

Here, right-click FACT_INTERNET_SALES to produce the popup menu


shown in Figure 55.

60
Metadata Management I 3

From the popup menu, select IMPACT to show the relative impact of a
change made to the source table FACT_INTERNET_SALES , as shown in Fig-
ure 56.

FACT_IHTERNET_SALES (Rdadonal_Table X

SAME AS RELATED TO IMPACT UNEAOE USER OEFINEO

IJNfVERSE,.OIJICT

CUSTOMER_STATECOOE
~ ==

a o f.

Figure 56 Impact ofTable FACT_INTERNET_SALES

This impact screen depicts all of the dependent obj ects downstream that
will be affected if a change is made to the table. The object to the far left
is table FACT _INTERNET_SALES, and the column of objects to its right with
the orange icons are analytic views in SAP HANA that use the table. As
you move to the third column, many of these objects are aggregations in
SAP HANA. The fourth column shows the SAP BusinessObjects BI uni-
verse information that depends on one of the analytic views as a data
source. Figure 56 highlights a particular field in the universe called CUS-
TOMER_STATECODE, which will be impacted. Hover over any of the
icons shown in the columns in Figure 56 for a summary of details. This
powerful information provides a complete picture of what wiill be
affected by a change to table FACT_ I NTERN ET_SAL ES.
You can also dive into the table to the field level to see the direct, field-
level impact. This is the level of granularity that most organizations use to
see the finite impacts of development choices. The field-level detail will

61
Metadata Management I 3

also surface formulas or transformations of data by revealing them in


popup windows when transformations occur. This is the case whether
you are in SAP HANA or SAP BusinessObjects Bl.
If you set up a connection for SAP Data Services and wanted to see the lin-
eage of where the data came from for table FAC T_ I NTERNET_SALE S, you
could do so by setting up a connection to SAP Data Services and running
a similar collection task for either SAP HANA or SAP BusinessObjects Bl.
If this metadata integrator source connection was collected for SAP Data
Services, you would see the lineage information from the ETL job that
made table FACT_ INTE RNE T_SALE S (see Figure 57).

f ACI _INTI::RNET_SALt'S (Rtlatio:Ml_Table) X

SAME AS RELATED TO IMPACT LINEAGE USER DEFINED

Figure 57 Lineage ofTable FACT_INTERNET_SALES

This linage information direcdy from the source system shows exactly
where the table data came from and can be examined at the field level as
well. With this level of clarity, you can see the following objects from
source to final destination:

Source tables
ETL transformations
SAP HANA tables
SAP HANA analytic views
Universe that consumes the analytic view
)} Universe field

62
Build an Enterprise Data Dictionary with Metapedia I 4

This completes the technical view of the Metadata Management module.


As previously mentioned, this data is quite technical in nature. To take
some of the technical edge off, you can use the Metapedia module to cre-
ate a business-term-driven data dictionary and relate such technical
objects to business-centric terms in order to communicate with a wider
audience. We will explore this process next.

4 Build an Enterprise Data Dictionary


with Metapedia
Complete business terminology is something many organizations struggle
to compile. Even with a complete list of terms, companies encounter chal-
lenges as to where and how they will store such information.
Metapedia allows you to create a compilation of data definitions and
terms in a format that can be both governed and shared as a hub to
expose them to various systems. Metapedia provides a full history of any
term or category changes, and it offers the ability to differentiate who can
make changes and how. Finally, Metapedia provides a secure platform to
guard against any loss of information via deletion.
As you can see, there are numerom reasons that Metapedia is an ideal op-
tion to manage the term and category creation process. In this section, we
will now explore how to create terms and categories within Metapedia.

4.1 Setting Up Terms

The first step of creating content in SAP Information Steward is to set up


terms. You can see an overview of the Metapedia module in Figure 58;
this is where you will create the terms.
Build an Enterprise Data Dictionary with Metaped ia I 4

C' Dlocalhost:SOSOfBOE/InfoStowaodApp/1505151336/ICCExplooer/MalnUI.jsp

..

~ 4 l ofl ,.

Fi gure 58 General Metapedia View of Terms in SAP Information Steward

In the sections that follow, you will learn how to create, approve, and
associate terms and how to show term activity history.

Create Terms
To create both terms and categories in the Metapedia module, you use the
GUI. Unlike the Data Insight module, there is no coding or special knowl-
edge required here. To begin, dick the NEW button (see Figure 59).

-
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ , _ ,, _ , Q

- - -
... ~ -

Figure 59 Click New to Create a New Metapedia Term

The METAPEDIA TERM dialog box will open (see Figure 60). Here, you will
enter all of the term's details.
Build an Enterprise Data Dictionary with Metaped ia J 4

Propcrtiol!s Custom Att:ributH

Status: Hew

Description
Data cap~ and post!ontd aret.nd corporate rntemtt sales. Data h this table ccnsists of
menses tM; t uptu'ed dally .Y'Id related ~o items sdd by o.astetners bv day. Internet sales....,.
be fromal arus of the~ ard not JUSt rmt~ to fqlh A.tnerica.J

~ cot'IT'I\4S(,} to separate entnes)

Keywords: Safes, h ternet

Associations GJ
Related Terms:

Figure 6o Metapedia Term Dialog Box to Edit and Create Terms

In the PROPERTIES tab, enter the term name in the NAME field. Use a func-
tional name that is not technical and that will make sense to an end user.
The purpose of a Metapedia term is to provide a business context and
description for technical content, therefore a Metapedia term must be
business-centric.

After you enter a term name (in our example, the term is called "Internet
Sales Data") , add a description for the term and an APPROVER (see Figure
60). This information forms the business description of the Metapedia
term, with as many details as necessary to fully qualify the term from a
business perspective. The approver concept is the first step of the
approval workflow that we will discuss in the next section. After you fin -
ish entering the term details, click the SAVE button, and the term will be
created.

Approve Terms
The next step in the term workflow process is to approve the term for use
in SAP Information Steward. To do so, click the SUBMIT FOR APPROVAL
button.
Build an Enterprise Data Dictionary with Metapedia I 4

A popup screen will open so that you can submit your comments and
specify a due date for the approval (see Figure 61).

Subm1t for Approval Comments

Due Date: 9{9/ 20 15 liiil


Comments:

Please approve my term for Internet Sales Data. 1


OK Concel

Figure 61 Submit for Approval Popup Screen to Enter Comments

To complete this step, click OK. After completion, the Metapedia admin-
istrator will approve the term if it is appropriate, and your term then can
be associated with other metadata that has been collected in SAP Informa-
tion Steward. It is important that the term is approved; otherwise you will
not be able to associate the term. We will step through the process of
associating an approved term in the next section.

Associate Terms
To associate a term in Metapedia, you "match" the term to a metadata
object that has been collected in Metadata Management. Much like creat-
ing the term and approving the term, there is no coding required when
associating a term. This process is performed at a high level by finding the
metadata object you wish to associate and using the Metapedia GUI to
associate the Metapedia term with the object. Use the same M ETAPEDIA
TERM screen that you used to create the term and submit the term for
approval. To associate your term, open the ACTIONS dropdown menu and
select ASSOCIATE WITH OBJECTS (see Figure 62).

After selecting ASSOCIATE WITH OBJECTS, you will see the ASSOCIATE
OBJECTS (INTERNET SALES DATA) screen appear (see Figure 63).

66
Build an Enterprise Data Dictionary with Metapedia 4

............
O.ta ~td and POSitiOnedtrOU"'d corwtt t-lternet Hits. O.t. r. ltis tab6t ~Uof ~: AO!wlslrators
II'INSU"H ltlatltii!UC)U~ daly aM related to i'.ems sddb'(o.storn!rsby& y. lntemttuls ...t
bt fi'01 el .veas; of flt globe ..-.d not ).1st '"'ltd to t:wth Atnct~cA~. $)nOnyJM: $61es,t\temet

{Us>! cotnmM(,) to ~ateentriH}

Kt'f\\'Ofc:b: Seles i'lttmtt

....... --
~ ActiOnS

A<tl toC.tt9QfY
:D Rdo.:c terms
.... ~
Lli) A$$000tt'M't1objc(:t$

f! Modfy ~

Figure 62 Associate Object Selection in t he Metapedia Term Screen

Q Jri.1 0SC.d'I: Fn:lob}tlca; N idWIQ 1'is lltrii'I'J~, Sfi'IOI'I~. Otb.,wotds.


(!} s-m ftt~.,.,....l .., xP

9loooorv 1 10oi:OJte,oJb of 2 M
" "- Mtt.dl110~(16~ ~~
.,.,~CU ~II MiiK or6tt!r~fo'r\fiQI'I.

Cotrr.{l'll) 8 ~ACT wtS l't.IOtR


Dilbo~(q rACT_slll.CS)'CAOCJt
~Irliqfllorl ~-l\.t.J'EMO)\ ~O)OH} \ Ttbtn~C_$AJ.!$_~
I)! S,I.('T ~f'
., ._ oet.t~tOO FACT..,SAI.E$

D FACTJ.ItE:"_<l'ln:ct...PETAil
FACTJAI,ES_OitOEfUETAD.
~Uolroca-tliCil'I.JDIS AA..IXMOl l$Ct!tfMI$ti)OH\llablrJII'".ACT ~ c:KlfR DfT~

Figure 63 Associate Objects Screen in Metapedia

Use the AssociATE OBJECTS screen to search for metadata objects that you
have collected in SAP Information Steward (as described in Section 2).
Continuing with the Internet Sales Data term example, find all of the "fact
Internet sales" related tables. The results will tell you that the following
tables relate to Internet sales:
Build an Enterprise Data Dictionary with Metaped ia I 4

FACT_SALES (from the context of the SQL Server database connection)


FACT_SAL ES (from the context of the data services development reposi-
tory; DS_RA_DEMO is the source object in this case)
FACT_SALES (from the context of the data services development reposi-
tory; DS_ RA_ DEMO is the target object in this case)
As shown in Figure 63, select all returned entries and click AssociATE
WITH TERM to perform the association. You have now provided a business
context for the raw metadata by implementing a relationship in Metape-
dia. Figure 64 shows the resulting relationship information.

HdaPt:diahrm )(

Properties Custom Attrib\ltes Lastmoclfltdby Ac:triiistrat on 9/9/2015 l0:37:SSAM

Status: APi)roved

De$c:ripli0n /w1ho(, Admiristrator


06t6eap~ed-positiontdarou:ldCIOI'POI'ate internet sales. Data in tiNs taJitconsists of /4flrAO'I: AdriW'istrbtors
rne!)SVn thotc c.apbsed cWy .v-drd4ted to items solclbywstomers.by&y. lntttnet soles wl
~ fromalarcasof tht ~and notj.Jst lmted ro North America, Synonyms: Sales,interntt

~a:li'M'\M(.)to~atetntrlts)

Keywords: SaJes i'lttrnet

Associations III <'4 Actions ...

R.NtedTerms:

I -
1l'lJ fACT,.SAlES
..,
Sve< lns.....,~VlN~ 10..-.s(INoct) 1-...,(080) I Tablos(FACT.,$AI.ES) X
1l'lJ f ACT_SI.LES Sve< lnstances(soc<eo) I O.~(s<u"') I Sch<m.ls(cl>o) I Tablos(FACT.,$AlES) X
1l'lJ fACT _SAlES Sve< lnstanc<i tVlN~ 10 . - . ,(seu"') 1..,._.,(080) I T.....(FACT_SALfS) X

Figure 64 Resulting Relationship Information in the Metapedia Term Screen

This completes the association process. As you might expect, there is


quite a great deal of churn that can occur in this process, so it may be
helpful to view the workflow history captured in the tool. We will discuss
how to do so in the next section.

68
Build an Ent erprise Data Dictionary with Metapedia I 4

Show History of Term Activity


Business activities often evolve and change, which can affect an organiza-
tion's terms list. Terms often mean different things to different groups
within an organization. For example, a "product sale" might be very dif-
ferent for a merchandizing group than it is for an operational controller.
For such reasons, there will be a reasonable amount of churn (activity) in
the creation and maintenance of terms in Metapedia. Therefore, it is
important to see the history of a term's evolution in order to put changes
into context both from date and approval perspectives. Fortunately, SAP
Information Steward tracks all of changes to an evolving term. Figu re 65
shows the history detail of our Internet Sales Data term.

Intemet Sales Data - History X

.. ,.,.,
Name Stab.Js Updated By Updattd On Corrments
Jnt.met Sales Data Approved AOO>iristrator 9/9/ 2015 10:37 AM !approve tns term for use.
Internet Sales Data Submitted for Approval AOO>iristratoc 9/9/ 2015 10:37 AM Please ~ove my term for internet Sales Oa~ .

Internet Sales Data Editing AOO>iristratoc 9/9/2015 !0:34AM

Close

Fi gure 65 Internet Sales Data Term History in Metapedia

This detailed history is a useful tool and includes the following informa-
tion:
Term origin
Who approved the term
When the term was approved
When the term was updated
Rich comments at each level
Term current status
In addition, the term history tool displays history of all terms created and
maintained, which safeguards the workflow process and the history of
what occurred at the term level.
Build an Enterprise Data Dictionary with Metaped ia J 4

Now that you have set up your terms, next you need to set up categories
to organize and catalog terms into groupings.

4.2 Setting Up Categories

Terms grouped together in Metapedia are called categories. Categories are


quite flexible, but they have one drawback: There is only one level of
hierarchy within a category. For instance, you can have a Customer cate-
gory and place customer terms (such as Customer First Name and Cus-
tomer Last Name) within it. However, you cannot have a secondary level
of grouping under the Customer category. You may wish to segregate cus-
tomer address data from customer name data, but you can only do so
with separate categories currently (as of SAP Information Steward 4.2).
You cannot have a Customer category with subcategories of Customer
Address and Person. Therefore, you must be specific and deliberate when
choosing category assignments in Metapedia. In this section, we will look
at creating and associating categories in Metapedia.

Create Categories
To create a category in Metapedia, click NEw CATEGORY, as shown in Fig-
ure 66.

Figure 66 Create a Category in Metapedia

Next, the METAPEDIA CATEGORYscreen will appear, as shown in Figure 67.

70
Build an Enterprise Data Dictionary with Metaped ia J 4

Here, you will enter the category name, category author, category
description, and any keywords you wish to use to search for this category
later. All of these configurations and field entries are shown in Figure 67.

Httapedia Category X

Properties Custom Atlributes

Fi gure 67 Metapedia Category Screen

Associate Categories
To use the created category with a Metapedia term, open the Internet
Sales Data term created in Create Terms and click ACTIONS. Instead of
associating the Internet Sales Data term with a metadata object as you did
previously, you will now add the term to the sales category that you just
created. Therefore, choose ADD TO CATEGORY from the ACTIONS d rop-
down (see Figure 68).
X -

PropettiH Custom Attrib\ltu lastmocl&ed by Adnwisl7atorM9/9/7015 t0: 37:ss, . , ~

StatuS: ~

06(ription Aulftor: Actnnstr6b:lr

Oot. C4Pb.rc:d .-dpoWoned OU'Id CJOrpotoD~e i-lto'net s.*s. Oo!4h INs t4tlle consists of ~= AdtTW'rc1rtcrs
fl'lebU~ that t capii.Ud &ly and rdated to it~ sdd by CUStotnfer'S by day, lnttmet salts WI
be fi'Qnll II tM of lt1e 9klbc: ond rot j.lst bted to North Antrb. $)orw;m'mS: Sall!s.ll'lterl'l!t

(Use cOI'II'IIas(.) to ~att entl1ts)

Keywofds: Soles hternet


ion' -=--

,....- ..... ......._


<J\ ~tt Ytith objects
V!Nttft:ory
- -- .8 Mo<ll) ~
=::J

Fi gure 68 Add the M etapedia Term to t he New Category

71
Build an Enterprise Data Dictionary with Metapedia I 4

The ADD TO CATEGORY popup screen will open (see Figure 69).

Add to Category X

- ct a category to assodate -""'the term(s)

OK CMcol

Figure 69 Add the Metapedia Term to t he Sales Category

This screen currently only shows one category. If there were more cate-
gories, they would show up as part of a potentially lengthy list in this
dialog box. It is best practice to consider your category naming conven-
tions carefully to avoid unwieldy lists. After you select the appropriate
checkboxes for the category or categories you wish to associate, click OK
to complete the process. The completed Metapedia term is shown in Fig-
ure 70.
- - - ---- - -- -- - - - - - -

SAP" SAP Jnlonn.Jtlon Sh~.atd """'*"- ..,.,_...,. " - - ..._ ~ twO"f

~~ - ~cz::mil _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __

" .._~r I :I' NtC.~ X OI!Ie:t

....
il Mi~

,
fi e.~ ..
a...~n~e~o..nJooorporta~:Nemtt,.._O...*'"._.~bflf-htn~tciO.....,,..,. .. ~-. . . br~' ., .., ~'*'
on offw~n""",...~IIOHDt.,.--w..
.. k t .-..

Figure 70 Finished Internet Sales Data Term in M etapedia

4-3 Exposing Metapedia Content to Other Systems

After you have created content in Metapedia, you can expose this infor-
mation to other environments. In this way, all terms and categories cre-
ated can be leveraged by other applications. This process is accomplished
through SAP Information Steward hosted web services, which can be
deployed and configured in the SAP Information Steward system. This
process requires additional configuration in SAP Information Steward,

72
Case Study I 5

which we will not cover in detail here. The purpose of this section is to
discuss the option to deploy such services, and why doing so can be desir-
able for end users.
After utilizing SAP Information Steward's web services, the workflow to
share a data dictionary is as follows:
1. Metapedia terms and categories are created, maintained, and governed
in SAP Information Steward.
2. The SAP Information Steward workflow controls rights, processes,
updates, and activities.
3. External applications use SAP Information Steward deployed web ser-
vices to query the repository of Metapedia terms and categories.
In this way, SAP Information Steward becomes the system of record for
business glossary terms, and other applications merely consume the
content.
Next, the final section in this E-Bite will round out what you have learned
thus far with a comprehensive case study using all three SAP Information
Steward modules.

5 Case Study
This section will take the knowledge we have gathered thus far about the
different SAP Information Steward modules and apply it to a real-world
scenario. In this case study, we will examine the AdventureWorks Cycle
Company, which has recently implemented a new BI platform based on
SAP HANA, SAP Data Services, and SAP BusinessObjects BI. Through SAP
Data Services, the company's BI resources were able to successfully
extract, translate, and load the sU!pporting Internet sales dimensions and
fact tables into an SAP HANA schema using a batch approach. Adventure-
Works will use SAP Information Steward to manage and govern master

73
Case Study I 5

data by first building content in the Data Insight module and then extract-
ing metadata through Metadata Management. Finally, the company will
create a data dictionary with Metapedia.

5.1 Building Content in Data Insight

AdventureWorks will use Data Insight to mine the customer master data
for potential rules and to perform some discovery on the customer master
data by using the Data Cleansing Advisor (DCA) functionality. Using the
DCA tool, the AdventureWorks staff can see what they need to measure
and examine some sample rules that can be implemented with SAP Infor-
mation Steward.

Syst em
The examples in this section use a Microsoft SQL Server CRM system. Many
SAP customers wou ld connect directly to SAP, as we discussed previously,
but in this example, AdventureWorks uses SQL Server to host its in -house
CRM system. Therefore, we will use SQL Server as our connection for custo-
mer data profiling.

Import Tables and Build a View


The first task for AdventureWorks in SAP Information Steward is to
import tables into Data Insight. To do so, browse to the import screen
shown in Figure 71 and select the tables you wish to import.

Next, the AdventureWorks staff need to examine contact address infor-


mation in the CRM system for a closer look at any data quality issues.
They select the PERSON.ADDRESS, PERSON.CONTACT, and PERSON.STATE-
PROVINCE fields in order to gather tables to construct a complex view (see
Figure 71). Then, they import the SALES.CUSTOMER, SALES .CUSTOMERAD-
DRESS, and SALES.INDIVIDUAL fields in the same manner until they have all
of the table metadata definitions needed to support the CRM view. The
completed tables are shown in Figure 72.

74
Case St udy 5

View: (:) External Metadata 0 l~ted Metodota

s~rh .P ~ St Altributes

8 0 Advent\lreWorks
D dbo
D HumenRe<O\I'ces
1:1 D Person
liJ !Ill Address Street address Information few customers, en'C)Ioyees, and vendors.
U !Ill AddressType Types r:l addresses stored in the Address table.
IE liJ !ill Contact N-emes of each efll)loyee, customer c0f'lt4ct, .erd vendor cortt.
IE U f!ll ContodType looN.Jp tM>Ie containhg the types of cortacts staed i'l Cont:ad.
U !Ill CountryRegion Looio4> tal>le oontoH'lg the ISO stondord codes for couies ond re!jons.
& liJ llil StateProvlnce State and po-ovloce ~table .
U Wl vAdcjtjonaiCootadlrio
IE U !!ll vStateProvil<eCountryRegion
D Production
D l'u'cha.ing
l'il D sl!les

Figure 71 Import Tables into SAP Information Steward

SAP SAP Informaoon Steward

~ III!IIII!BIIIIIIIIIIZI
Projects Info_Steward_6ook

~ Workspace Home

(j Add of

Tables
Advisor
.p ~ St

8 0 Advent..-eWorks
U !!ll Person.Ad<tess
U !ill Person.Contoct
U ID; Person.statePrcMlce
U Wl s.les.Customer
U Ill: s.les.CustomerAddress
U Ill: s.les.In<Miual
r Views

Figure 72 Imported Tables in Advent ureWorks' Data Insight Connect ion

Now they begin to build a view. AdventureWorks staff use the VIEW EDI-
TOR to construct the V_ADVWRKS_CUSTOMER_ADDRESS_UI view, as shown in
Figure 73.

75
Case Study I 5

-
~ o ~~ ......... ~e'Nolb.~son.Contett.ft-~
....,. --
fi'itiVJII'Iedthepet11(1n.

-
4td\er(50)
I; Atti"~ ,_ ~aWo!b.Pertor~.COI'Utt.~ .,..,ctw(SO) l.st~W~~edtheoeuon.

"' Ill"""' ~....wo.u~.COI'Q(t.~ ....<Nr('!iO) tWclti'IIIIWOrltWd!Jt~dhl*l


lmo..stor:.
...........
.._
~~..ld7-..u7~1 .....dw(GO) R-stS~Jcot*'essWie.
ltl lleu.ton.Adhft
. g ........, ....<hor(60) SewvJ We .dcl'e h .

~e.WO!ts.Pertot~.I06tfllf.,Cty .....cJ"''(30) Mmedthe~.


lti ii SWW'r~
~twori$.Pertot~.l.dltrtfif,~e Ot tl"'d tWtt "".oord wtf .... \06
~.wou~.Adlt-~.PoCil.lleodt ....(bet(l'S) ~codt fortt. itr... .xltesf..

sttPr<PYI"<Codt ~~.~.st.r;eProWocec. ...,(ho,o(*) tsOst.,..<lst.et~~codt.

~ode ~e.Wo!b.Pertot~.~~owtn..<~l9(:1nt ...(her(') l'SO~U'try(lft~oode. l

Fi gure 73 Build View in Data Insight to Prepare for Profiling

The tables for the view are found under SOURCES on the left sidle of the
screen shown in Figure 73, and they are joined in the VIEW EDITOR. The
Adventure Works staff have selected the output columns under COLUMN
NAME on the right-hand table shown in Figure 73.

There is now a dataset to examine in Data Insight. The next step is to pro-
file the data for more information on the rules that should be enacted.

Profile View
Profiling data in Data Insight is an easy task that provides great visibility
for data quality challenges and exposes rules that the AdventureWorks
staff should consider based on the data profile. To start this process, click
V_ADVWRKS_CUSTOMER_ADDRESS_UI (the view built in the section
Import Tables and Build a View) to select it. Then, click PROFILE to expose
the dropdown list. From the dropdown list, select COLUMNS to set up the
column profile task, and then select CONTENT TYPE to expose the com-
pleted profile tasks shown in Figure 74.
Case Study 5

SAP .. SAP lnformo:oonStt-wd w-.,. tklnloc*t ~ "- Help too ott

~~.... ~II:I:C:ll~~
~' lrlo.,.st~

0
c...... ......
9/t21201$$;44ut ~ 9/1~1$$>4<6AM

9/!Ub) ISS:UAH ~ 9/IUZDISS."<f3A.M

Fi gure 74 Completed Profiling Tasks

The profiling tasks are now complete, and SAP Information Steward
shows results for the columns (see Figure 75).

Prolk R . .i R1.l1e: A.~

......: re:;;J Aclv..ad ! ~

ce
-L!j 0 v~.a.rst~
m AdchUlhfl
m Adl;t-,,~
r
Alb ......... 081, ~ ~,.,. . . Z S464M.rrerd!
,...
..,, 11.20

" ,.,
moo,
:oncb-t~c
.....", ~HIO)

......... '"
"'""us

'i
!' Cty
,..,
m ~ 1-'
.........
"""" us
,., ......us ...
m ,..,._
m.........,
m-
m ~.
1.! ...._ ---
2001 07 01 201)4 .01.31 ~IZ.IOOO
""' .. 1.01

.,,,

m""""""'
m ~.,""~
!'
~~
-
""""" CA ,..,

Fi gure 75 Completed Column Profiling Results

As shown in Figure 75, there is a great deal of information exposed in this


window. There are metrics concerning NULL values, patterns of data, and
completeness of entries. All blue icons are clickable, to provide sample

77
Case Study I 5

data for the end user. From here, you can click the gear icon highlighted
in Figure 75. Doing so allows you to examine the suggested validation
rules for data metrics. We will examine these rules in the next section.

Examine Suggested Rules


After you click the gear icon shown in Figure 75, you will see the screen
shown in Figure 76. This is the DATA VALIDATION ADVISOR, in which you
can examine rules the tool suggests .

- ..... 1 ---- l....L-


-------------
Data validation Advisor )(

....
,,..
I"' s H"""""""'
"'"'"'
}(, RnnVe
I

w
1
e Mdclef"ne a~owoc~ patterns
0 "''""
r- s H""'"'""' J(. ~
r,
~ ~~ p.&tt~ f) Aeot

Rule:~IUon DIStribuUon

8E<i!N
,,.,
R11.RNrn4tth_pottern($Post41Ccde, '99999');
0. '31~(1 v

Figure 76 Suggested Rules Based on Column Profiling Data

After examining the DATA VALIDATION ADVISOR a little closer, you will see
validation rules that can be accepted or rejected in the AcTIONS column at
the top right of Figure 76. If you select the rule for PosTAL CODE, you will
see that the distribution of postal codes is wrong for AdventureWorks'
business requirements. AdventureWorks does business by shipping the
majority of its products. Therefore, zip codes should be able to be entered
as nine-digit codes rather than only as five-digit codes. Here, you want to
accept the validation rule. Click YES to see the rule in SAP Information
Steward (see Figure 77).
Case Study I 5

Rule Editor X

Propertte:J Custom Attributes

Name: P~ alowed patterns st~: New

Description: Rule for Views.V_ADVWR.KS_CUSTOt.R_AOORESS_US.Postaleode:Pattern Distribution

Approver:*

Edot...

-
Par<NT~c:tc:rs:

X $Postoleodc
-
ExpressiOn:

OefWlitioo filters

BEGIN
RETU<N match_patterr(sPoSWICodc, 99999');
EN>

~ Validate "") Test .. Save Close

Figure 77 Ru le Editor

Note that this is exactly the same RULE EDITOR screen as used in Section 2
for creating rules to support scorecard development. The DCA process to
generate these rules is much faster when the rule is generated to specified
requirements. Using this feature will allow Adventure Works to jumpstart
the rules monitoring process. The company can still take the rule and use
it in a scorecard for trending and any other purposes. They are still rules
like any other SAP Information Steward rules. This process is just a faster
way to get to the developed rule.
At this point, AdventureWorks needs to see a greater level of detail for
both potential data cleansing and matching opportunities. To do so, the
company will use DCA on the table.

Data Cleansing Advisor


To start DCA, click the broom icon shown in Figure 78.

79
Case Study 5

Ptofllt ltHulb fbM M.~

-
......,r-1 ~~.d I !::...;.

P "' ......
ill
r

cs
..o-.,--.
"'w i!J -
~;::::--~
m-""""
mav
m.,..,.-
..\
r--
!-'
Ao6tl.o"l
S~.locloi"c

'"'
,.....,
081,-.....~~2

...., ..,...,.,
v-
~M.rr..-dl
.,..,
,..." -
.,
"
11.20

'"

" ,.,

.......
- -- ..
-l
m...- "' ,."' ......"'
..... .. ....,
2.00

m. - .,,
m-
m ~e
!' .......
....
" .. 1
_,., 2001.07012004.07.31
..,.,
zcm t2.toco
....
m"""'""
m,...,.,_ !-'
!-'
- .. ""' ""'
"'
" ,...

Figure 78 Broom Icon Starts Data Cleansing Advisor

The DCA Wizard will open, as shown in Figure 79.

Data Cleansing Advisor Wizard X

Specify Data Cleansing Solution Oetaitls

Name and describe yOU' data cleansi:lg soUion to help you and others understand ls
purpose. The rwne and desc~n are shar'ed with Data 5ei"VVces WOrl<benctl when you
2 select Coi.Jmns pubish the sol~n .

3 Set uP Matct't"JQ
""""e: OCA_ADVWRKS_CUST_ADDR
Set uP Transformatbns
Oesaiption: Ollta cleaMino soUion to JYdile custOtner address data in
AdventureWorks
don.lodenC>declslonfirst

"'ReqUred fields

Next> C.ancel

Fi gure 79 DCA W izard Step 1: Name the Solution

8o
Case Study I 5

The AdventureWorks staff can now begin to create the data cleansing
solution. After providing a name and business description, click NEXT to
get to the screen shown in Figure 80.

Data Cleansing Advisor Wizard X

Select Relevant Data Quality Columns


1 Name the SOlution
Include columns that are relevant to cleansino and matctw'IQ in this data cleansing soUion.
You c.v. Rlxle cohsms representinQ ooe person~ one address, ooe fi m, and other data.

3 set up Matchi"lo
Cokm\Nome C<Wltent Type Staws
4 set up Transformaoons 13 0 i Peron v
U1 ~ FirstHame First Name

U1 ~ lastName Last Name

u ~ l~ido:leN"""' f ir'stName
13 ~ I!!) Address
U1 ~ Addressline1 Address l.i"le
"'
U1 ~ Addressline2 Secondary Add ..

U1 ~ City City

U1 ~ Post aiCode Postcode

U1 ~ Stat el'!ovlncecode Re<;~lon

U1 ~ Ca.rtryROQionCode Coortry

<Back Next> nsh Cancel

Fi gure So DCA W izard Step 2: Select Columns for Cleansing

Next, select columns for cleansing. Include the fi rst and last names,
because you need to see how bad the relative qualities of the name data
fields are within the CRM system. However, you are primarily concerned
with the address fields, which you know are bad based on the basic
column profiling and rule suggestions in the previous sections. Click NEXT
to move to the third screen (see Figure 81).
This is screen is important from a matching perspective, because it deter-
mines what you will be matching on. Because you are focusing on deans-
ing the person and address columns , try to see if there are person and
address duplicates using the matching functionality within DCA; select
the PERSON AND ADDRESS checkbox. Click NEXT to move to the final con-
figuration screen (Figure 82).

81
Case St udy I 5

Data Cleansing Advisor Wizard X

Select Match Theme and Rules


1 Name the SOlutiOn
If you want to incUle motchin<) in your data cleansing soiJtion, tl'oen select match tlleme
and at least one match nAe.
2 Select Cwmns

Match tlleme: IndM:lual


4 Set uP Tr;nsformatms r>\atch Rules
1!!:1 PerS<>n and Address
0 PerS<>n and ID

<Bad< Next > flniltl Cancel

Figure 81 DCA Wizard Step 3: Set Up M atching

Data Cleansing Advisor Wizard X

Add Basic Tr ansformations


1 Name the SOlution
If your d.Ma needs simple text de~, such as ~rch and rcpl8ce, Of removino SJ)8ces or
QUOtation marks., add transformations below. This step is optional.
2 Select C<iJmns

3 Set uP Matchhg
Transformations

Desaiption ColurmName

<Back rr~e t Flniltl C.on<el

Figure 82 DCA W izard Step 4: Set Up Transformati ons

Here, the AdventureWorks staff has the option to transform the data if
required in the data cleansing solution. We typically recommend not
doing this, and instead taking the output given with the tool, because
transformations are very limited and can be problematic when using data
from w ithin SAP Information Steward. This is especially important when
you are going to use the DCA output to generate code for SAP Data Ser-
vices. For these reasons, AdventureWorks staff choose to keep the
options set to their defaults and simple. After this screen, click FINISH to

82
Case Study I 5

close out the DCA Wizard and run the solution. The process completes
the execution, and you will see the high level output shown in Figure 83.

SAP " SAP InformabonStE-A.Yd ,...,.... Ocrl..bden ~ Vltw . , LooOff

............ ~ll::l::l\I~II.'I:ICI

~- I
~-
~ . I l
CCrredoclchssesl#tllt dNnse:
lrw)(ll:reotttdcttHeS titer <~Nt!Se: ,.." ,..,

Figure 83 High Level DCA Resu lts

A more detailed representation can be achieved by clicking on the DATA


CLEANSING tab (broom icon), as shown in Figure 84.
Looking at Figure 83, you immediately can see that duplicates are not an
issue by examining the graph on the right side of the screen; the tool does
not detect any duplicates. Therefore, this is not something Adventure-
Works needs to deal with for matching purposes. However, the cleansing
results are more interesting and would lead AdventureWorks to look at
the details in Figure 84, which show that almost all of the postal codes
were corrected from the rule suggestion. The details also illustrate a great
deal of problematic street data. This result necessitates further investiga-
tion of the data before and after address correction (see Figure 85).
Case Study 5

~ SJIP lnforrnaoon Stew.Md ~ don.bden Yoow~q v-. Hlltl LOOotf

......- , ~~~ll:'l\'l:lel

:a-- . !;I <!. ll


.,.,_ t iSl-a- I m- ... I

Vaiclacbes...

- I
Clx '"*" q !XII

...,_,

..
Ccn.u.dc:ty:

.........
Cc:rttedreQon:
V<lkl.otes~ Cotr.ctedil:reet~-~

),.,.,. : ,., Ccn.cttdMCOndlr)' ~:


C#tett.d~
"
Ccne<ted~:
C~edto62--t
" Cotr.ctedd.y,re90n.crpo:os.toodt:
"

Figure 84 More Detailed DCA Results

The <k.tMs ~below are aiPMsl* ltefere at'ld After dMnse ook.trlns

-...
~: t; ~retdSQitirto8ofor.c:l/lltetcoll.m'l$

CcMnnomc ik!OfO

Bel...
Adchmu.. .
AdlhSJSLI... '134146ttl St.

c-..
StePrcw..
~

l>it"
CCU'ttyC ..
(OU'Uy( ...
w
9&<03
us

,..,.,.,
BokhJ N...
............
Ad<tess Lhe 13'tl <l6thStW

s.ww...
..... -
Str eet Ad...

PontdR
...
1'3<4146thSl w

.........
Pont r:l R...

Figure 85 Record by Record, Before and After Cleansing View


Case Study I 5

This valuable view allows you to see exactly what the tool did to the data.
In this example, we can see that the "W" for "West" was added to the
street address to make it correct for postal delivery.

5.2 Extracting Metadata with Metadata Management


After using the Data Insight module, AdventureWorks has greater visibil-
ity into predictive data quality monitoring. The next step to support
information governance will be to extract metadata using Metadata
Management. We will now discuss a high-level approach for this step.
At AdventureWorks , IT uses SAP BusinessObjects BI for reporting
against CRM data. Using the Metadata Management module, Adventure-
Works can gain greater insight into all of the relationships of the BI
reports and into the lineage of where the data is sourced from CRM. To
accomplish this, the AdventureWorks staff will essentially perform all of
the steps described in Section 3 of this E-Bite. First, they will establish a
connection to the SAP BusinessObject BI system in SAP Information
Steward. Then, they will run a metadata collection task to collect all of
the metadata on the SAP Information Steward server. The Adventure-
Works analysts will use the resulting information compiled from the SAP
BusinessObject BI system to answer questions such as the following:
Where did the customer name data come from in the customer sales
report?
Was the customer name data transformed in any way?
How many reports in SAP BusinessObjects BI use the customer name
field?
These are simple questions, but they offer insight into completely differ-
ent aspects of the CRM data on top of the powerful information already
compiled by the Data Insight module.
Next, to complete our governance story, we will set up a data dictionary
in Metapedia.
Case Study I 5

5.3 Creating a Data Dictionary with Metapedia

In the previous section, Metadata Management rounded out the insight


to ensure that you know where data is coming from and how it is being
transformed. Now, it is time to bring business relevance to technical
items by creating a data dictionary in Metapedia.
The AdventureWorks governance team members need to quickly provide
business relevance for the technical term names they have defined. Luck-
ily, AdventureWorks currently has a data dictionary maintained in Excel,
so team members do not have to key in individual terms. This provides a
much faster route for getting started, as there is no need for approvals. In
the data dictionary, AdventureWorks has terms that have been approved
and are used currently against production data. In this case, it is much bet-
ter to perform a mass upload that includes all of the Metapedia terms.
Then, the company can begin to govern additional terms or edits to terms
through the Metapedia GUI one record at a time, as discussed in Section 4.
To see this import in action, first log into Metapedia and click the IMPORT
button (see Figure 86).

Fi gure 86 Import Data Dictionary File from Microsoft Excel

Then, browse to and select the sample import XLS file (see Figure 87).

86
Case Study I 5

Met apedia Import X

II ~,,r;; Import XLS file path:

Metapedia_20 13100ZT 131207.xls 8rO'NSe


Term Mapping
Import Options:
Citegory Mapping ~ ~rt categories
U Ovem<it~ existing tenns ond categories

Deta.Jit Author: Adrriristra tor IIJ


Default Approver: Metodoto Ma - t Dato Steward IIJ
0 Automaticoly approve ~ted terms.

Import Excel Sche ma: Information Steward Format

Figure 87 Import Process for M etapedia: Automatic Term Creation

Finally, review the information imported into Metapedia in the applica-


tion (see Figure 88).
-----------------------------------------------------------------------------------
SAP.,. SAP lnlofmrtton Strward "'"*"-' ......._....,. Klr'"O"" ~ ~ WJOff

lm':'!3~ - ~ll:m'::l!!!l

__..
--
__..
Figure 88 Completed Terms Import

This concludes our SAP Information Steward journey. This last section
rounded out our discussion of the three modules in a comprehensive case
study. You should now be able to move forward and monitor your data in
real time with SAP Information Steward.
6 What's Next?
So you've monitored, cleaned, validated, and defined your data using SAP
Information Steward's three pr imary modules. Now what?
SAP Information Steward is just a piece of the Enterprise Information
Management (ElM) puzzle. Therefore, it's important to know all the tools
at your disposal to ensure optimal data quality. From bigger solutions like
SAP Data Services to tools such as SAP Data Quality Management .and SAP
Master Data Governance, ElM provides a plethora of functionality to
manage the entire lifecycle of your data.

Recommendation from Our Editors

Data quality and monit oring is a critical business task in an


w-r::;:,v.M~ enterprise. Study up on t he latest tools of t he t rade: Learn
~--..--_, more about using ElM with SAP and further information on
SAP Information Steward by visiting www.sap-press.com/
3666 and checking out the SAP PRESS book, Enterprise Infor-
mation Management with SAP!

In addition to this book, our editors picked a few other SAP PRESS publi-
cations that you might also be interested in. Check out the next page to
learn more!

88
SAP PRESS E-Bites
SAP PRESS E- Bites provide you with a high-quality response to your specific project
need. If you're looking for detailed instructions on a specific task; or if you need to
become familiar with a small, but crucial sub-component of an SAP product; or if you
want to understand all the hype around product xyz: SAP PRESS E- Bites have you
covered. Authored by the t op professionals in the SAP universe, E-Bites provide the
excellence you know from SAP PRESS, in a digestible electronic format, delivered (and
consumed) in a fraction of the t ime!

Hi llary Bliss and Bruce Labbate


Text Analysis w it h SAP
ISBN 978-1-4932-1343-6 1 $12.99 1 102 pages

Brogden, Sinkwitz, Marks, Orthous


Creating Documents and Queries in SAP BusinessObjects Web Intell igence
ISBN 978-1-4932-1354-2 1 $9.99 I 56 pages

Chen, Hanck, Hanck, Hertel , Lissarrague, Medail le


Data Integration w ith SAP Data Services
ISBN 978-1-4932-1309-2 1 $9.99 I 56 pages

The Author of this E-Bite


Don Loden is a principal consultant at Decision First Technolo-
gies with full lifecycle data warehouse and information gover-
nance experience in multiple verticals. He is an SAP Certified
Application Associate on SAP BusinessObjects Data Integrator,
and an active member in the SAP community. In add ition , Don
has spoken globally at numerous SAP and ASUG conferences
and events. Learn more about Don at http://www .sap-
press .com/sap- information -steward - mon ito ring-data- in - real -
t ime_4022/author/.
More from SAP PRESS

SAP Data Services - The Comprehensive Guide: Extract, transform, and


load your skills on managing enterprise data with this book on SAP Data
Services! Get the skills you need, from basics like designing objects to
advanced tasks like analyzing unstructured text.

524 pages, p ub. 02/2015


E- book: $69.99 I Print: $79 .95 I Bundle: $89.99
www.sap-press.com/3688

SAP BusinessObjects Web Intelligence- The Comprehensive Guide: Work


smarter in Web!! Get the basic concepts and the actionable details to
advance your work with SAP BusinessObjects Web Intelligence!

691 pages, 3 rd edition, pub. 08/2014


E- book: $69.99 I Print: $79.95 I Bundle: $89.99
www.sap-press.com/3673

Implementing SAP HANA: Explore the steps in a complete SAP HANA


implementation with this book. Become an expert in data provisioning
with SAP Data Services , data modeling, and connecting to the BOBJ plat-
form. Take your SAP HANA knowledge to the next level!
860 pages, 2nd edit ion, pub. 12/2014
E- book: $69.99 1 Print: $79.95 1 Bundle: $89.99
www.sap-press.com/3703
Usage, Service, and Legal Notes

Notes on Usage

This E-Bite is protected by copyright. By purchasing this E-Bite, you


have agreed to accept and adhere to the copyrights. You are entitled to
use this E-Bite for personal purposes. You may print and copy it, too, but
also only for personal use. Sharing an electronic or printed copy with oth-
ers, however, is not permitted, neither as a whole nor in parts. Of course,
making them available on the Internet or in a company network is illegal.
For detailed and legally binding usage conditions, please refer to the sec-
tion Legal Notes.

Service Pages

The following sections contain notes on how you can contact us.

Praise and Criticism


We hope that you enjoyed reading this E-Bite. If it met your expectations,
please do recommend it. If you think there is room for improvement,
please get in touch with the editor of the E-Bite: Sarah Frazier (sarahf@
rheinwerk-publishing.com).
W e welcome every suggestion for improvement but, of course, also any
praise! You can also share your reading experience via Twitter, Facebook,
or email.
Supplements
Supplements (sample code, exercise materials, lists, and so on) , if avail-
able, are provided in your online library.

Technical Issues
If you experience technical issues with your e-book or e-book account at SAP
PRESS, please feel free to contact our reader service: support@rheinwerk-
publishing.com.

About Us and Our Program


The website http://www.sap-press.com/ provides detailed and first-hand
information on our current publishing program. Here, you can also easily
order all of our books and e-books. Information on Rheinwerk Publishing
Inc. and additional contact options can also be found at http://www.sap-
press.com/.

Legal Notes

This section contains the detailed and legally binding usage conditions for
this E-Bite.

Copyright Note
This publication is protected by copyright in its entirety. All usage and
exploitation rights are reserved by the author and Rheinwerk Publishing;
in particular the right of reproduction and the right of distribution , be it
in printed or electronic form.
2016 by Rheinwerk Publishing, Inc., Boston (MA)
Your Rights as a User
You are entitled to use this E-Bite for personal purposes only. In particu-
lar, you may print the E-Bite for personal use or copy it as long as you
store this copy on a device that is solely and personally used by yourself.
You are not entitled to any other usage or exploitation.
In particular, it is not permitted to forward electronic or printed copies to
third parties. Furthermore, it is not permitted to distribute the E-Bite on
the Internet, in intranets, or in any other way or make it available to third
parties. Any public exhibition, other publication, or any reproduction of
the E-Bite beyond personal use are expressly prohibited. The aforemen-
tioned does not only apply to the E-Bite in its entirety but also to parts
thereof (e.g., charts, pictures, tables, sections of text). Copyright notes,
brands, and other legal reservations as well as the digital watermark may
not be removed from the E-Bite.

Digital Watermark
This E-Bite copy contains a digital watermark, a signature that indicates
which person may use this copy. If you, dear reader, are not this person,
you are violating the copyright. So please refrain from using this E-Bite
and inform us about this violation. A brief email to info@rheinwerk-pub-
lishing.com is sufficient. Thank you!

limitation of liability
Regardless of the care that has been taken in creating texts, figures, and
programs, neither the publisher nor the author, editor, or translator
assume any legal responsibility or any liability for possible errors and
their consequences.