Mastering SAP NetWeaver Master Data Management
Bernd Schloemer
Contents
1 Introduction ................................................... 3
1.1 Contents of the Individual Chapters . ...... 3
1.2 Acknowledgments .................................. 4
2 The Sample Project . ....................................... 5
2.1 Process ................................................... 5
2.2 Consolidation and Harmonization ........... 5
2.3 Importing the Sample Repository . .......... 6
2.4 Summary ................................................ 7
6 Data Maintenance Using the Data
3 The Repository ............................................... 9
3.1 Repository Structure ............................... 9
3.2 Creating a Repository ............................. 9
3.3 Loading a Repository .............................. 11
3.4 Creating the Necessary Tables ................. 11
3.5 Creating the Client Systems .................... 13
3.6 Creating Users and Roles ........................ 14
3.7 Configuring Change Tracking . ................. 16
3.8 Summary ................................................ 16
4 Preparatory Data Maintenance ...................... 17
4.1 Data Manager: Startup and Overview ..... 17
4.2 Data Maintenance in Tables .................... 18
Flat Table ........................................... 18
Hierarchy Table .................................. 18
Image Table ....................................... 20
Products Table ................................... 21
4.3 Summary ................................................ 23
5 Importing Master Data .................................. 25
5.1 Loading Data from a Microsoft
Excel File ................................................ 25
5058_BOOK.indb 1
Import Manager . ............................... 25
Assigning a Source and a Destination . 26
Value Mapping . ................................. 28
Performing the Import Process ........... 30
Checking the Import in the Data
Manager ............................................ 31
5.2 Batch Import .......................................... 31
5.3 Importing an XML File ............................ 32
5.4 Summary ................................................ 34
 
Manager ......................................................... 35
6.1 Searching . .............................................. 35
Limiting the Data ............................... 35
Free-Form Search . ............................. 35
Operator . .......................................... 36
Reset Search ...................................... 36
Saving the Search ............................... 36
Searching in Hierarchy Tables ............. 36
6.2 Comparing Items .................................... 36
6.3 Protecting Entries ................................... 37
6.4 Check-In and Check-Out ........................ 38
6.5 Validations . ............................................ 40
Grouping Validations . ........................ 42
Extending the Encoding ..................... 44
6.6 Relationships .......................................... 44
6.7 Masks ..................................................... 48
6.8 Attributes ............................................... 49
6.9 Modeling the Workflow . ........................ 51
Start Step ........................................... 52
Process Step . ..................................... 52
Validation Step . ................................. 52
Process Step (2) ................................. 53
www.sap-press.com  1
3/7/08 4:32:46 PM
 Contents

Validation Step (2) ............................. 53 8 Exporting Master Data . ................................. 67

Approve Step ..................................... 53 8.1 Syndicator GUI ....................................... 67
End Step ............................................ 53 Export into a Flat File ......................... 68
6.10 Executing the Workflow ......................... 53 Export into an XML File ..................... 69
6.11 Summary ................................................ 56 8.2 SyndicatorBatch . .................................... 71

7 Consolidation ................................................. 57 9 Summary and Outlook ................................... 73

7.1 Consolidation with the Import Manager . 57
7.2 Consolidation with the Data Manager . ... 60
Index .............................................................. 75
Matching Based on a Search . ............. 60
Matching in the Data Manager ........... 63
7.3 Summary ................................................ 66

2  © Galileo Press 2008. All rights reserved.

5058_BOOK.indb 2 3/7/08 4:32:46 PM

 6 Data Maintenance Using the Data Manager

This chapter discusses the various Data Manager func-

tionalities that are required for data maintenance. At first
you will become familiar with the different possibilities
of searching data or managing searches within the Data
Manager. Additionally, we will explain other function-
alities such as comparing data records or check-in and
check-out functionalities. Using the examples, you will
also learn about the concept of attributes as well as vali-
dations as a prestage to the workflow.

6.1 Searching
The Data Manager supports various procedures for
searching for data in the different table types. In addi-
tion to the free-form search, you can also use restrictions
for the referenced tables (Colors, Category, etc.) to
limit the view of the Record area. As a first step, we will
use the free-form search for searching for entries in the
Products table. For this purpose, switch to the Record
Mode and select the Products table from the toolbar.
Figure 6.1  Selecting the Category
Free-Form Search
In the table view, click on the Free-Form Search tab. You
will see a view similar to that shown in Figure 6.2.
In the entry field to the right of Name, enter “Hard
drive” in the Value column and note how the number of
rows changes in the Record area.

Limiting the Data

To limit the data displayed in the Record view according
to your own criteria use the referenced tables, for exam-
ple, Category, as a selection criterion. To display all data
records of the Products table that have a value of PC in
the Category table, proceed as follows:
1. Change to the Record Mode.
2. In the list box of the menu bar, select the Products
table.
3. In the tree structure of the Category tab, click on the
PC entry (see Figure 6.1).
Note how the number of rows changes in the
Record area when you click on different nodes of
the tree structure.
4. Select the Color tab and repeat the procedure. Note
that in this view, Color only displays the values that
Figure 6.2  Free-Form Search
are actually referenced in the Products table.

www.sap-press.com  35

5058_BOOK.indb 35 3/7/08 4:32:57 PM

 6    Data Maintenance Using the Data Manager

Operator
For every search, you can select the operator for every
field to be searched from the list box. (See Figure 6.3.)

Figure 6.5  Saving and Managing Searches

Searching in Hierarchy Tables

Figure 6.3  Changing the Operator Hierarchy tables can be searched in a similar way as the
free-form search. First change to the Hierarchy Mode
By combining individual search operators with the fields and then search for all rows that contain the string “PC”
to be searched, the Data Manager provides an effi- (see Figure 6.6).
cient search tool. The following search operators are
supported:
EE contains
EE starts with
EE ends with
EE equals
EE excludes
EE sounds like
EE language layer
EE is NULL Figure 6.6  Searching Hierarchy Tables

Reset Search Tip

An active search—and thus the display of data in the
Record area—can be reset at any time by clicking on the
Reset Search button in the toolbar (see Figure 6.4).
Note that the methods for searching and restricting
data shown previously can be combined. For this pur-
pose, you can first limit the number of data records in
the Record area, for instance, by selecting a category.
Then you can further limit the result set of the data re-
cords using a free-form search, for example.

6.2 Comparing Items

Figure 6.4  Resetting the Search
For the comparison of several items, MDM provides the
compare function, which enables a simultaneous presen-
Saving the Search
tation of the selected items. To use this function, change
A search can be saved via the Search menu. Additionally,
to the Record Mode and from the list box, select the
you can use the Search menu to delete or call existing
Products table (see Figure 6.7).
searches. This is a useful feature, particularly for recur-
ring searches with search parameters in several fields (see
Figure 6.5).

36  © Galileo Press 2008. All rights reserved.

5058_BOOK.indb 36 3/7/08 4:32:57 PM


Figure 6.7  Selecting the Products Table
In the table, select several products of the same type, for
instance, all hard drives, and then in the right-click con-
text menu select Compare Records... (see Figure 6.8). As
a result, you are presented with a view in which you can
compare the selected entries (see Figure 6.9).
Figure 6.8  Selecting and Comparing Products of the Same Kind
Figure 6.9  Comparing Products
5058_BOOK.indb 37
6.3  Protecting Entries
6.3 Protecting Entries
Depending on the business process, it makes sense to
protect individual entries in the Products table, for
example, against changes. For this purpose, switch back
to the Record Mode and select the Products table from
the list box. Select several entries, and in the context
menu go to Remove from Mask • Protection • Protect
(see Figure 6.10).
Figure 6.10  Protecting Entries against Changes
As a result, the selected entries will be displayed with a
padlock icon in the first column; these entries are now
locked (see Figure 6.11). Select one of the items marked
with such a padlock and try to change individual fields in
www.sap-press.com  37
3/7/08 4:32:57 PM
 6    Data Maintenance Using the Data Manager

the Record Detail area. As can be expected, you will not
succeed because all fields are protected against changes.
Figure 6.11  Locked Entries
Individual or all protected entries can also be unlocked
again via the context menu (Protection • Unprotect)
(see Figure 6.12).
records against being changed immediately after their
creation.
A record with a check-out is identified by the yellow
icon in the second column of the Records area (see Fig-
ure 6.14).
In the Record Detail area, now change the Manufac-
turer from ATI to Dummy and click in the Records area
to save your change. This means you check out the data
and try to change it in the second Data Manager. Open
the Data Manager a second time and log on as the Copy-
writer user.

Figure 6.12  Unlocking Entries

6.4 Check-In and Check-Out

Similar to the Protect functionality, MDM also provides

Figure 6.13  Selecting Check-In and Check-Out
a check-in and check-out mechanism that enables you to
protect one or several entries against changes by other
users. This functionality is applied, for example, when
several people simultaneously work in a repository and
make changes. An entry with a check-out cannot be
changed by other users until the check-in. To test this
functionality, change to the Record Mode and from the
list box, select the Products table. Mark an entry in the
Record area, and in the context menu select Check In/ Figure 6.14  Record with Check-Out

Out • Check Out Exclusive (see Figure 6.13).

As you can see, there are other options apart from
the exclusive check-out. The check-out for new records
is particularly interesting. It can be used to protect new

38  © Galileo Press 2008. All rights reserved.

5058_BOOK.indb 38 3/7/08 4:32:58 PM

 6.4  Check-In and Check-Out

Note
It is important that you log on as another user in the
second Data Manager instance instead of the one you
are currently using.

As you can see in Figure 6.15, the record also has the
check-out icon here and is also marked light blue. It is
therefore not possible to change the fields for this record
in the Data Manager.

Figure 6.15  Record with Check-Out Icon

Change to the Data Manager with your Admin user. The

Manufacturer field still shows a value of Dummy (see
Figure 6.16). Figure 6.17  Selecting the Roll Back Option

Figure 6.16  Dummy Value in the Manufacturer Field

In the Check In/Out context menu, now select the Roll Figure 6.18  Original Value

Back menu option (see Figure 6.17). This function resets

the changes to the Manufacturer field to the original
value. Additionally, the check-out icon has been removed
(see Figure 6.18). You could have used the Check In menu
option to accept your change and to check the record
back in, that is, release it to be edited by other users.
The Modify Join Permissions context menu option opens
another window (see Figure 6.19), in which you can use
Add to allow other users to edit one of the checked-out
records.

www.sap-press.com  39

5058_BOOK.indb 39 3/7/08 4:32:58 PM

 6    Data Maintenance Using the Data Manager

within the area below Validations and select Add Valida-

tion from the context menu (see Figure 6.21).

Figure 6.21  Creating a Validation

The first validation is to check whether all entries in Prod-

ucts have a price. As the name of the validation, enter
“Check Price” (see Figure 6.22). In the Table field, enter
“Products” as the table name.

Figure 6.19  Modify Join Permissions

When a record is edited by several users, to ensure that a

field cannot be edited simultaneously by multiple users,
an error message as shown in Figure 6.20 is displayed
when other users are trying to change the same field.

Figure 6.22  Entering a Name for the Validation

Figure 6.20  Error Message

You can start the Code Editor for the validation by click-
6.5 Validations ing on the [Validation Expression] button in the Valida-
tion field (see Figure 6.23).
With validations, the Data Manager allows you to check
the contents of individual or several records at a time.
A validation always returns a boolean value (true or
false). This value is indicated in the Records area as a
Figure 6.23  Starting the Code Editor
new column with a red or a green icon (red for false,
green for true). To create a validation, in the Record
The Code Editor is now displayed (see Figure 6.24) and
Detail area go to the Validations tab. Now right-click
enables you to use the list boxes (Fields, Operators,
Functions, etc.) to conveniently access predefined func-
tions and the fields of your tables.

40  © Galileo Press 2008. All rights reserved.

5058_BOOK.indb 40 3/7/08 4:32:58 PM

 6.5  Validations

Figure 6.24  Functions of the Code Editor

To check the contents of a field, you can use the Is Null

function. For an empty field, this would return true
(green icon). However, it makes more sense to have a red
icon in our case; therefore we will use the Is Not Null
function, which will return false. Now select this func-
tion as shown in Figure 6.25.

Figure 6.26  Field Selection

Figure 6.25  Selecting the Is Not Null Function

The Editor window now displays the inserted function.

In the Editor window, place the cursor between the
two parentheses of the function, and from the list box
select the Price field (see Figure 6.26). Your Editor should
now display the entry IS_NOT_NULL(Price) (see Figure
6.27). Figure 6.27  Entry in the Code Editor

www.sap-press.com  41

5058_BOOK.indb 41 3/7/08 4:32:59 PM

 6    Data Maintenance Using the Data Manager
Exit the Editor by clicking on the OK button. Before you
test the next validation, in the Products table add a data
record without a value for Price. As shown in Figure 6.28,
use the Add menu option from the context menu.
Figure 6.28  Creating an Entry
In the Products table, select all entries by pressing
[Ctrl-A], and then in the context menu, go to Valida-
tions • Execute • Check Price as shown in Figure 6.29.
Figure 6.29  Checking the Price
As a result of the validation, a new column, Check Price,
is created in the Records area, and all entries except for
the new data record have a green icon (see Figure 6.30).
Figure 6.30  Entries with Checked Price
42  © Galileo Press 2008. All rights reserved.
5058_BOOK.indb 42
Proceed in the same way to create the validations Check
Image (see Figure 6.31) and Check Desc (see Figure 6.32)
that will check the contents of the Image and Descrip-
tion fields.
Figure 6.31  Validation Check Image
Figure 6.32  Validation Check Description
Once you have entered these validations, your Data Man-
ager should display the entries shown in Figure 6.33.
Figure 6.33  Validations in the Data Manager
Now check your new validations as described previously.
As you might have noticed, you can only run one valida-
tion at a time. To run several validations simultaneously,
SAP NetWeaver MDM provides two options:
1. Group the validations.
2. Extend the encoding.
Let’s first have a look at grouping validations.
Grouping Validations
To create a validation group, right-click in the Validation
area and from the context menu, select Check Price •
Edit Validation Groups... (see Figure 6.34). Then right-
click on Validation Groups and select Add Child (see Fig-
ure 6.35).
3/7/08 4:32:59 PM

Figure 6.34  Edit Validation Groups
Specify a name for your new validation group, for exam-
ple, “CheckProd,” and close the window by clicking on
the OK button (see Figure 6.36).
Figure 6.35  Add Child
Figure 6.36  Validation Group CheckProd
Change to the Check Price validation and then open the
list box in the Group field. Use the Add button to add the
CheckProd group to your validation (see Figure 6.37).
5058_BOOK.indb 43
6.5  Validations
Figure 6.37  Adding a Validation to a Group
Repeat these steps for the Check Images validation and
add it to the CheckProd group as well.
Test the validation group by selecting all entries in the
Records area by pressing [Ctrl-A] and selecting Check-
Prod from the context menu, as shown in Figure 6.38.
As a result, you will see two new columns correspond-
ing to the two validations in the CheckProd group (see
Figure 6.39).
Figure 6.38  Testing a Validation Group
Figure 6.39  Validation Result
Let’s now take a look at the second option of running
several validations simultaneously: the extension of the
encoding.
www.sap-press.com  43
3/7/08 4:32:59 PM
 6    Data Maintenance Using the Data Manager

Extending the Encoding
Another option for merging several validations is to join
the validations in the Code Editor. Create a new valida-
tion named “Check All” and call it in the Code Editor. Use
the list boxes to create the code shown in Figure 6.40.
The AND can be obtained via the Operators list box.
Figure 6.40  Code in the Code Editor
between different products. In real life, relationships are
used for the following purposes:
EE To illustrate that a material belongs to an assembly
EE To define alternative materials for a material.
Assembly is a term used for grouping materials on dif-
ferent levels. For example, a car engine consists of vari-
ous individual materials that are grouped in the engine
assembly.
Before we can use relationships we must create the
appropriate tables in the MDM Console. Close the Data
Manager and change to the MDM Console. First unload
the current mdm_book repository by going to Unload
Repository • Immediate so that you can make changes
(see Figure 6.43).

Save this validation and check it. Now select the new
validation from the context menu (see Figure 6.41). This
results in a new column [Check All], the rows of which
should each display a red icon as the validation result
(false) (see Figure 6.42).

Figure 6.43  Unloading a Repository

Change to the Relationships table and right-click in

the Records area. Select Add Relationship (see Figure
6.44).

Figure 6.41  Selecting Check All

Figure 6.42  New Column [Check All]

6.6 Relationships

In SAP NetWeaver MDM, a relationship is an option of Figure 6.44  Adding a Relationship

expressing dependencies between entries, for example,

44  © Galileo Press 2008. All rights reserved.

5058_BOOK.indb 44 3/7/08 4:33:00 PM

 6.6  Relationships

You will implement the mapping of an assembly for PCs Reload the repository (Figure 6.46) and restart the Data
as a relationship. All values that are relevant for this pro- Manager (see Figure 6.45). A new Relationships entry
cess are contained in the Products table; that is, the field with the fields PC <parts> and parts <PC> is now
Products table is the parent and child table for this rela- contained in the Record Detail area (see Figure 6.47).
tionship. The relationship should be named PC. Create
the relationship using the following values (see Figure
6.45):

Name PC

Name Is Parent

Name 2 parts

Has Position Yes Figure 6.46  Loading a Repository

Has Quantity No

Parent Table Products

Child Table Products

Figure 6.47  New Relationships Entry Field

In the next steps, you add several parts to each of the

two PCs in the Products table. Start by clicking on the
PC AMD Sempron row (see Figure 6.48). In this way, you
load the Record Detail area for editing.
Open the Relationship Editor by double-clicking on
the PC <parts> row in the Relationships field (see Fig-
ure 6.49).
Figure 6.45  PC Relationship

Figure 6.48  Loading Record Detail Area for Editing

www.sap-press.com  45

5058_BOOK.indb 45 3/7/08 4:33:00 PM

 6    Data Maintenance Using the Data Manager

Figure 6.49  Relationship Editor

Figure 6.51  Assigned Children

Select the parts <PC> tab and click again on your Data
Manager to select the following rows in the Products Now, close the Relationship Editor and select again PC
table: AMD Sempron in the Records area. As shown in Figure
EE Hard drive 300G 6.52, the Record Detail area shows that the parts <PC>
EE Mainboard AMD entry has four relationships with other entries.
EE Power Supply
EE VGA card

Then select Add to Group in the Relationships menu

(see Figure 6.50). Figure 6.52  Entry Including Relationships

In this example, you added the selected parts by selecting

the assembly (PC AMD Sempron). You can also select a
part directly and assign it to an assembly by using the PC
<parts> tab in the Relationship Editor (see Figure 6.53).
In addition to this manual method, you can also
import relationships from a file. Such import files are sim-
ple text files that contain two fields per row. These fields
are separated by tabs. The following listing illustrates the
setup of such an import file:
Name <PC>[tab]Name <parts>
PC INTEL CELERON[tab]Power Supply
PC INTEL CELERON[tab]Mainboard AMD
PC INTEL CELERON[tab]Hard drive 300G

Figure 6.50  Selecting Parts

To import relationships, select Import from File in the
Relationships menu and select the relation.txt file (see
The selected rows are transferred to the Relationship Edi-
Figure 6.54).
tor and listed as PC AMD Sempron children (see Figure
6.51).

46  © Galileo Press 2008. All rights reserved.

5058_BOOK.indb 46 3/7/08 4:33:01 PM

 6.6  Relationships

Figure 6.53  Direct Selection of a Component and Assignment to an Assembly

Figure 6.54  Importing a Relationship

A status report is displayed after the import has been com-

pleted (see Figure 6.55). The status report enables you to
determine whether all relationships can be created.

Figure 6.55  Status Report with Successfully Imported Relationships

www.sap-press.com  47

5058_BOOK.indb 47 3/7/08 4:33:01 PM

 6    Data Maintenance Using the Data Manager

6.7 Masks

In SAP NetWeaver MDM, masks enable you to create

one or more subsets of the current repository without
having to store the master data in duplicate. To create a
new mask, select the Masks table in the list box of the
menu bar (see Figure 6.56).

Figure 6.59  Context Menu: Add to Mask

Figure 6.60  Demomask in the Record Detail Area

Figure 6.56  Creating a New Mask

Right-click in the Records area and select Add in the con-
text menu. Name the new mask “Demomask” (see Fig-
ure 6.57).
First, delete possibly active searches using the Reset
Search button (see Figure 6.61). Then, select the Mask
tab and switch between both entries [None] and Demo-
mask. Note how the number of the data records changes
(see Figure 6.62).

Figure 6.57  Naming a Mask

Figure 6.61  Resetting a Search

Having saved the mask, change to the Products table

and select the tab for the free-form search. Search for
entries that contain the VGA value in the Name field (see
Figure 6.58).

Figure 6.58  Free-Form Search for VGA Value Figure 6.62  Selecting a Mask

Select the two entries found and select Add to Mask
• Demomask in the context menu, as shown in Figure
6.59. You can now see that your demo mask was entered
in the Masks field in the Record Detail area (see Figure
6.60).
The context menu provides other functions, such as
Remove from Mask to remove masks and Replace in
Mask to replace masks (see Figure 6.63).

48  © Galileo Press 2008. All rights reserved.

5058_BOOK.indb 48 3/7/08 4:33:01 PM

 6.8  Attributes

Figure 6.63  Other Functions in the Context Menu

Using the MDM Console, you can assign masks with the
appropriate authorizations to a role. This enables you to
easily set up different authorization concepts within a
repository.

6.8 Attributes

In the case study, we used the taxonomy table, Cate-

gories, that is already defined to divide the products Figure 6.65  The Attribute Detail tab
into different areas (office supplies, PC, etc.). Using the
attributes concept, SAP NetWeaver MDM enables you Now, click on the Add button and enter the following
to divide the products into other categories based on the values in the following order (see also Figure 6.66):
taxonomy tables. This case study provides a category for Text:
PC hard drives. However, another classification of the EE < 100 GB
hard drives into capacities would be useful. To imple- EE 100 – 200 GB
ment this requirement, create a Size attribute as well as EE 200 – 300 GB
different areas for capacities. The new attribute is pro- EE > 300 GB
vided for entries in the Products table that are assigned
to the PC Hard drives category.
To create a new attribute, change to Taxonomy Mode.
Right-click in the Records area and select Add in the con-
text menu (see Figure 6.64).

Figure 6.66  Selecting an Attribute

The attribute can be saved by clicking in the Records

Figure 6.64  Creating a New Attribute area. In the next step, you must link the attribute with
one or more entries of the taxonomy table. In our case
Enter the following values in the Attribute Detail area study, you should only link the attribute with the PC
(see Figure 6.65): Hard drives value. Thus, select this value and then Link
in the context menu, as shown in Figure 6.67.
Name Drive capacity

Alias Capacity

Definition Capacity for hard drives

www.sap-press.com  49

5058_BOOK.indb 49 3/7/08 4:33:02 PM

 Index

A Record, 17 I
Record details, 17
Action item, 27, 30, 59 Images, 20
Record infos, 17
Adapter, 6 Image table, 20
Tables, 17
Approve step, 53 Import, 25, 30
Data, restrict, 16
Assembly, 44 Check, 31
Demo mask, 48
Attribute, 22, 49 Perform, 30
Description, 22
Link, 50 Processing steps, specifying, 26
Destination
Select, 49 Start, 26
Assigning, 26
Using an XML file, 32
Import action, 30, 59
B Change, 30
E Create, 59
Batch import, 31
Editing modes, 18 Replace, 59
Batch Import Manager, 25, 30
End step, 53 Skip, 59
Boolean value, 40
Ends with, 36 Update (All Mapped Fields), 59
Equals, 36 Update (Null Fields only), 59
Excludes, 36 ImportBatch.ini, 31
C Import format, 25
Execute import, 59
Categories, 18, 19 Export, 67 Import Manager, 5, 9, 25, 26, 32, 57
Changes Into an XML file, 69 Consolidation with, 57
Protection against, 37 Into a flat file, 68 Import status, 27
Change tracking, 16 Into an XML file, 71 INI file, 31
Check-in/Check-out, 38 Expression Editor, 61 Is NULL, 36
Child, 19 ItemCode, 22
Client systems, 13, 25 Item Editor, 68
Code Editor, 41, 44 F ItemName, 22
Color, 18 Items, 68
Family mode, 18
Command line, 31
Field mapping, 26, 28, 33
Compare function, 36
Flat table, 18
Comparing data records, 35
Free-form search, 35, 48, 61
L
Consolidation, 5, 57
Language layer, 36
Contains, 36
Limiting the data, 35
H Log file, 31, 32

D Harmonization, 5, 6
Hierarchy, 10
Database account, 10
Hierarchy mode, 18
M
Database server, 10
Hierarchy table, 18 ManufacturItemCode, 22
Data group, 20
Searching, 36 Map, 30, 31, 34, 60, 69
Data maintenance, 35
Mapping, 31
Data Manager, 5, 9, 17, 31, 35, 57
Mask, 48
Consolidation with, 60

www.sap-press.com  75

5058_BOOK.indb 75 3/7/08 4:33:11 PM

 Index

Matching Reference, 20
T
Based on a search, 60 Relationship, 44
Check, 20, 59 Import, 47 Tables
Field, 58 Relationship Editor, 46 Create, 11
In the Data Manager, 63 Repository, 6, 9, 11 Taxonomy mode, 18
Matching field, 34, 60 Being loaded, 11 Transformation, 63
Matching mode, 18 Create, 9, 10 Trigger, 52
Match records, 65 Load, 11, 45
MDM, 5 Must be updated, 11
MDM Console, 5, 7, 9, 44, 49 Selection, 17 U
MDM server, 7, 9, 10 Stopped, 11 Unarchive repository, 7
Logon, 17 Unload, 44 User, 14
Startup, 17 Reset search, 36
MDMWorkflowInstall.exe, 51 Role, 14, 16
Merge, 66 Assign, 16 V
Merge Editor, 62 Create, 14
Validate step, 52, 53
Microsoft Excel file, 25 Roll back, 39
Validation group, 42, 43
Mount, 10 Rule, 64
Validations, 40, 43, 52
Running simultaneously, 42
Value mapping, 28, 29, 33, 58, 59
O S Visio, 51, 52
Operator, 36, 44 Sample project, 5
Change, 36 SAP NetWeaver Exchange Infrastructure
Contains, 36 (SAP NetWeaver XI), 5, 67 W
Ends with, 36 SAP NetWeaver Master Data
Weight, 22
Equals, 36 Management (MDM), 5
Workflow, 5, 51, 53, 54, 56
Excludes, 36 Scheduler, 71
Workflow tasks, 54
Is NULL, 36 Search
Language layer, 36 Saving, 36
Sounds like, 36 Search expression, 61
Starts with, 36 Search operator, 36, 60 X
Sibling, 19 XML file, 25, 32
Sounds like, 36 Import, 32
P Source Structure, 32
Assigning, 26 XML schema, 70
Port, 11
Source preview, 26
Price, 22
Start step, 52
Process step, 52, 53
Products, 21
Starts with, 36 Z
Strategy, 64
Zip file, 6
Syndication, 67, 71
Zoom, 23
Syndicator, 6, 9, 67
R SyndicatorBatch, 71
Read/Write, 15 Syndicator GUI, 67
Record, 18 Syndicator Server, 67
Record mode, 18

76  © Galileo Press 2008. All rights reserved.

5058_BOOK.indb 76 3/7/08 4:33:11 PM